Jimbo.Automates Posted March 16, 2023 Share Posted March 16, 2023 I've been working on adding the ability for the Elk node server to handle controlling ISY Lights when Elk Lights are changed. But first a question for all existing users of the ELK nodeserver. Currently when you have a "Light" configured in the Elk, it will create a new node matching that name on the ISY. This was done because I didn't really understand what Elk Lights were used for. So when moving to allow the new way, I plan to have the node server delete these ISY Light nodes that it created. Is everyone okay with that? The way it will work with initial release is you create an Elk Light and make it's Name be the same as the name or address of the ISY node you would like to control. There will be no export/import functionality on initial release due to the effort required, and in my opinion, it's pretty easy to just manually configure the Lights in ElkRP2 so it's not worth the effort. But, I've built in the basics for doing this, so it could be added in the future if the new method is not satisfactory. These changes have been made, and hopefully I can complete testing and get it released soon. - Jim 1 Link to comment
DennisC Posted March 16, 2023 Share Posted March 16, 2023 1 hour ago, Jimbo.Automates said: I've been working on adding the ability for the Elk node server to handle controlling ISY Lights when Elk Lights are changed. But first a question for all existing users of the ELK nodeserver. Currently when you have a "Light" configured in the Elk, it will create a new node matching that name on the ISY. This was done because I didn't really understand what Elk Lights were used for. So when moving to allow the new way, I plan to have the node server delete these ISY Light nodes that it created. Is everyone okay with that? Jim, I for one would welcome the change. Have those extra lighting nodes listed under the alarm zones can be confusing, especially for my wife. 2 Link to comment
Joe Casullo Posted March 16, 2023 Share Posted March 16, 2023 I stopped using Elk lights a long time ago, probably when I got my first ISY. 1 Link to comment
DennisC Posted March 16, 2023 Share Posted March 16, 2023 7 hours ago, DennisC said: Jim, I for one would welcome the change. Have those extra lighting nodes listed under the alarm zones can be confusing, especially for my wife. At the least, may be you could add a toggle to the configuration page of the node server to disable adding the Elk lighting nodes? Programing in the admin console is so much easier. Link to comment
SteveBL Posted March 16, 2023 Share Posted March 16, 2023 Great! Thanks Jim I don't mind not having duplicate lighting nodes at all. I would just like to get back the ability to access, control and show device status from my Elk Keypads. It's 'eisy' enough to manually add devices to the ElkRP2. 1 Link to comment
Jimbo.Automates Posted March 16, 2023 Author Share Posted March 16, 2023 2 hours ago, DennisC said: At the least, may be you could add a toggle to the configuration page of the node server to disable adding the Elk lighting nodes? Having Lights configured in ElkRP2 that do not exist in ISY will not cause an issue, so not sure why I need a toggle to enable this? Link to comment
DennisC Posted March 16, 2023 Share Posted March 16, 2023 3 minutes ago, Jimbo.Automates said: Having Lights configured in ElkRP2 that do not exist in ISY will not cause an issue, so not sure why I need a toggle to enable this? Maybe I am forgetting something. When I first set up my ISY994, my lighting was imported in to my ELK M1. I don't remember if this was a manual operation, (some toggle button?) or done automatically. When I started using the Elk Node Server, all that lighting was imported back to the Node Server without user action. I don't see a way to delete these nodes, either in the Elk Node Server, or M1. In the M1, there is a column for "Show" and the description for this says " An X under "Show" means that device will be visible on the keypad and other user interfaces." I might be able to remove them from the Node Server by unchecking "Show", but never tried that, as I didn't want to break something. Link to comment
xlurkr Posted March 16, 2023 Share Posted March 16, 2023 I haven't moved to your nodeserver yet, but I might in the future. These nodes you currently create: would they allow one to control X10 devices set up on the Elk? This is something I'd like to be able to do, since X10 support is falling away at UDI and Insteon. Link to comment
Jimbo.Automates Posted March 21, 2023 Author Share Posted March 21, 2023 On 3/16/2023 at 1:48 PM, xlurkr said: I haven't moved to your nodeserver yet, but I might in the future. These nodes you currently create: would they allow one to control X10 devices set up on the Elk? This is something I'd like to be able to do, since X10 support is falling away at UDI and Insteon. They would not. There is nothing the NS can do to control X10 devices, it can only happen thru the ISY. Link to comment
Jimbo.Automates Posted April 2, 2023 Author Share Posted April 2, 2023 On 3/16/2023 at 8:05 AM, SteveBL said: Great! Thanks Jim I don't mind not having duplicate lighting nodes at all. I would just like to get back the ability to access, control and show device status from my Elk Keypads. It's 'eisy' enough to manually add devices to the ElkRP2. So is the current method satisfactory our is there still a need to do export/import ? Link to comment
Recommended Posts