mkohanim
commented
2 years ago The node export is bi-directional:
-
We send a ‘pc’ (lowercase) X10 message to Elk when the status of the node changes (i.e. whenever ST changes for the node)
-
When we receive a ‘PC’ (uppercase) message from Elk, we send a DON or DOF to the matching node (if there is one) depending on the lightLevel in the PC command o If the 4th value in the PC message (the ‘transaction ID’) is 10 then we do not send a command because it is just a status response from Elk. o We do NOT send the command if the target node has an ST value and it would be different than what the command would be sending (i.e. if the command is DON 100 and the node ST value = 100 then the DON would not be sent)
Here is an example of an Elk export file (in the ISY the file is always /CONF/ELKXPRT.XML):
id – Maps to an X10 address (e.g. id=3 is “A03”)
name – The address of an ISY node or groupThis is the function we use to convert an id to an X10 address:
/**
- Converts the given index into an X10 address
- @param elkId The elk ID, such that 1 = "A01", 2="A02", 17="B01", etc.
- @param elkX10Id (output) The X10 address
-
@return True if successful, False if ix not in valid range of 1..256 / bool udElkConvertToElkX10Id(int elkId, char elkX10Id) { if (elkId < 1 || elkId > 256 || elkX10Id == NULL) { if (elkX10Id) *elkX10Id = '\0'; return false; }
char hc = ((elkId - 1) / 16) + 'A'; int uc = ((elkId-1) % 16) + 1; sprintf(elkX10Id,"%c%2.2d",hc,uc); return true; }
jimboca
cfaith
From: Michel: The main question is whether or not you can translate their commands into ISY commands. In short, the issue is not an export. The issue is converting their direct lighting commands to ISY.