dss Posted October 4, 2009 Posted October 4, 2009 When I import the device list form the ISY to the ELK am I limited by the 256 device limit of the ELK? Most of the devices I don't even need to have imported into the ELK only the ones with loads but it imports everything controlince buttons, keypadlinc buttons that I don't need displayed in the ELK. Is there a way to only import the devices with actual loads? I'm up to 370 devices.
Michel Kohanim Posted October 5, 2009 Posted October 5, 2009 Hello dss, Unfortunately not at the moment. We do have plans for more extensive ELK integration in the 2.7.8 timeframe. 2.7.7 should be out by mid November. With kind regards, Michel When I import the device list form the ISY to the ELK am I limited by the 256 device limit of the ELK? Most of the devices I don't even need to have imported into the ELK only the ones with loads but it imports everything controlince buttons, keypadlinc buttons that I don't need displayed in the ELK. Is there a way to only import the devices with actual loads? I'm up to 370 devices.
dss Posted October 5, 2009 Author Posted October 5, 2009 Hello dss, Unfortunately not at the moment. We do have plans for more extensive ELK integration in the 2.7.8 timeframe. 2.7.7 should be out by mid November. With kind regards, Michel When I import the device list form the ISY to the ELK am I limited by the 256 device limit of the ELK? Most of the devices I don't even need to have imported into the ELK only the ones with loads but it imports everything controlince buttons, keypadlinc buttons that I don't need displayed in the ELK. Is there a way to only import the devices with actual loads? I'm up to 370 devices. Is it possible to at least sort the export file so that the load devices are on top. Or be able to manually sort the file so I can put the ones I want on top. So when it cuts off at the 256 device limit, I wouldn't care about those.
Michel Kohanim Posted October 6, 2009 Posted October 6, 2009 Hello dss, Unfortunately not. The mapping is one to one based on the node index. So, if a device have a node index of 0, then the ELK address would be A1 and so on and so forth. I do apologize for the delay in getting the ELK enhancements out ... our schedule is based on ROI and ELK has medium priority (based on the total number of users). With kind regards, Michel Hello dss, Unfortunately not at the moment. We do have plans for more extensive ELK integration in the 2.7.8 timeframe. 2.7.7 should be out by mid November. With kind regards, Michel When I import the device list form the ISY to the ELK am I limited by the 256 device limit of the ELK? Most of the devices I don't even need to have imported into the ELK only the ones with loads but it imports everything controlince buttons, keypadlinc buttons that I don't need displayed in the ELK. Is there a way to only import the devices with actual loads? I'm up to 370 devices. Is it possible to at least sort the export file so that the load devices are on top. Or be able to manually sort the file so I can put the ones I want on top. So when it cuts off at the 256 device limit, I wouldn't care about those.
dss Posted October 6, 2009 Author Posted October 6, 2009 Is there a way to shuffle the node index number putting the load devices at the top of the list? Otherwise it appears that they are listed in chronologic order the most recently added device the last on the list. So if I started from scratch I would have added all the single node devices like switchlincs in first, then the keypadlincs next then lastly the controlincs I could get more in under the limit that the arbitrary order they are put in now. How will the ELK enhancements address this as I assume the device limitation is hardwired into the ELK. Hello dss, Unfortunately not. The mapping is one to one based on the node index. So, if a device have a node index of 0, then the ELK address would be A1 and so on and so forth. I do apologize for the delay in getting the ELK enhancements out ... our schedule is based on ROI and ELK has medium priority (based on the total number of users). With kind regards, Michel Is it possible to at least sort the export file so that the load devices are on top. Or be able to manually sort the file so I can put the ones I want on top. So when it cuts off at the 256 device limit, I wouldn't care about those.
Michel Kohanim Posted October 6, 2009 Posted October 6, 2009 Hello dss, You are very much correct: they are in chronological order. So, the first added device has lower index than the most recent device UNLESS something was removed in between (the index was free to use). ELK enhancement will address these issues by: 1. Having a user defined MAP between ISY nodes and ELK addresses 2. The ability to add/remove nodes from the ELK export 3. Integration with other events coming from ELK With kind regards, Michel Is there a way to shuffle the node index number putting the load devices at the top of the list? Otherwise it appears that they are listed in chronologic order the most recently added device the last on the list. So if I started from scratch I would have added all the single node devices like switchlincs in first, then the keypadlincs next then lastly the controlincs I could get more in under the limit that the arbitrary order they are put in now. How will the ELK enhancements address this as I assume the device limitation is hardwired into the ELK. Hello dss, Unfortunately not. The mapping is one to one based on the node index. So, if a device have a node index of 0, then the ELK address would be A1 and so on and so forth. I do apologize for the delay in getting the ELK enhancements out ... our schedule is based on ROI and ELK has medium priority (based on the total number of users). With kind regards, Michel Is it possible to at least sort the export file so that the load devices are on top. Or be able to manually sort the file so I can put the ones I want on top. So when it cuts off at the 256 device limit, I wouldn't care about those.
WayneW Posted October 22, 2009 Posted October 22, 2009 ELK enhancement will address these issues by: 1. Having a user defined MAP between ISY nodes and ELK addresses 2. The ability to add/remove nodes from the ELK export 3. Integration with other events coming from ELK Will these enhancements be available to the ISY-26? I know the ISY-26 is obsolete, but I couldn't find a clear cutoff. It seems to get the new firmware versions, but not the new folders or the add-on module capabilities. Do I need to upgrade?
Michel Kohanim Posted October 22, 2009 Posted October 22, 2009 Hi WayneW, Unfortunately no since the enhancements will come in the form of a module and which 26 does not support. With kind regards, Michel ELK enhancement will address these issues by: 1. Having a user defined MAP between ISY nodes and ELK addresses 2. The ability to add/remove nodes from the ELK export 3. Integration with other events coming from ELK Will these enhancements be available to the ISY-26? I know the ISY-26 is obsolete, but I couldn't find a clear cutoff. It seems to get the new firmware versions, but not the new folders or the add-on module capabilities. Do I need to upgrade?
brad77 Posted October 23, 2009 Posted October 23, 2009 ELK enhancement will address these issues by:1. Having a user defined MAP between ISY nodes and ELK addresses 2. The ability to add/remove nodes from the ELK export 3. Integration with other events coming from ELK This module can't come out soon enough, as far as I'm concerned. You'll have my money on day one!
Michel Kohanim Posted October 23, 2009 Posted October 23, 2009 Hello brad77, I just wanted to say that this statement of yours just brightened up my night! With kind regards, Michel ELK enhancement will address these issues by:1. Having a user defined MAP between ISY nodes and ELK addresses 2. The ability to add/remove nodes from the ELK export 3. Integration with other events coming from ELK This module can't come out soon enough, as far as I'm concerned. You'll have my money on day one!
jsf Posted October 23, 2009 Posted October 23, 2009 ELK enhancement will address these issues by:1. Having a user defined MAP between ISY nodes and ELK addresses 2. The ability to add/remove nodes from the ELK export 3. Integration with other events coming from ELK This module can't come out soon enough, as far as I'm concerned. You'll have my money on day one! DITTO!
dss Posted October 24, 2009 Author Posted October 24, 2009 Count me in to. Will order as soon as it's available. ELK enhancement will address these issues by:1. Having a user defined MAP between ISY nodes and ELK addresses 2. The ability to add/remove nodes from the ELK export 3. Integration with other events coming from ELK This module can't come out soon enough, as far as I'm concerned. You'll have my money on day one!
Recommended Posts
Archived
This topic is now archived and is closed to further replies.