All Activity

I’ve been having an issue with my 2 outdoor floodlights. I have a three-way circuit to control them using Insteon DIMMERS. One switch is located in my kitchen and the other in the garage. One of the floodlights is a simple socket with an LED lamp and the other is a new integrated LED floodlight fixture. The problem I am having is that there is occasional and sporadic flickering of BOTH fixtures. That leads me to believe it’s not the fixtures themselves, but something with the circuit or switches. The Insteon dimmers are many years old and I realize it’s probably better if I had used on/off switches instead of dimmers. I wonder if the problem I’m having is the dimmers are failing or the dimmers don’t like the LED fixtures. Not sure how to troubleshoot this so I’m considering purchasing two on/off Insteon switches and swapping them in place of the dimmers. Any other tips and tricks to troubleshoot this before I fire the parts cannon at it? The flickering lights make my house look haunted.

Just recently my Elk plugin has stopped updating the nodes on my Eisy. The controller node seems fine in admin console but no nodes show up in the plugin in PG3. I've restarted the plugin, restarted admin console but nothing. its telling me area 1 does not exist 2026-01-06 21:56:45.846 Command udi_interface.interface ERROR interface:_handleInput: parseInput: node address area1 does not exist. {'address': 'area_1', 'cmd': 'GV11', 'query': {'Beep.uom2': '0', 'Clear.uom25': '1', 'Content.uom145': '+0.0KW 25.4 Sprd'}} Rest error 2026-01-06 21:56:03.316 Thread-9 (handler_start) udi_interface INFO Controller:start_rest_server: ELK Controller: REST Server not running for light_method=NONE and 2026-01-06 21:59:41.906 Thread-1 (send_thread) udi_interface.interface ERROR interface:_send: MQTT Send Error: Object of type ElkRPStatus is not JSON serializable I've included a log package Any help would be appreciated ELK_1-6-2026_95842_PM.zip

Just to double check, there are two ways to add IP to the Launcher. The first is: https://eisy.local:8443/desc. The second is https://xxx.xxx.x.xxx:8443/desc. Replace the x's with your IP address. Be sure to try both of them.

I can confirm that the update status on eisy-ui changes to "A reboot is required" (or something to that effect) when the update is complete. -Tom

Guy & DennisC - I just got it to work. No idea what change was made/what mistake I corrected. Thanks to both of you for your responses. I greatly appreciate the help.

Guy - I do see the eisy in the router device table. The IoX Launcher was working and I can access it with no issues on the UD Mobil. Having said that, I recently installed a new computer with Windows 11. This is my first attempt to access the eisy from the new computer. DennisC - I followed your directions. I could not discover the eisy. I then followed the directions above from Guy and attempted to discover the eisy with the IP address. I still can not use the IoX Launcer. Other ideas?

It's best to update from eisy-ui if you are upgrading from a recent enough version.

When I ran upgrade packages I never got a pop-up saying the download was complete or to reboot. I waited about 15 minutes and rebooted. eisy-ui was upgraded to 0.9.0

Did you ever figure out how to get the temperature device to be recognized as such by Alexa? Just wondering. Thanks.

eisy-ui 0.9.0 is now available. The main feature is related to backup and recovery. The backup includes IoX, ZWave, PG3x and eisy-ui settings. The restore allows to restore everything in one shot, or do a selective restore. For those migrating, you can restore an IoX and/or a PG3x backup. It will detect and restore accordingly.

Bob, As expected the join command is not working... On another note, I missed something as each time I restart the sonos plugin if finds all the speakers. Was there something I needed to add to stop the auto discovery? Im heading out of town for a couple of weeks so wont be able to reply to you after tonight. Appreciate the effort, I will ping you when I return if you are still interested in pursuing a solution

Glad it helped. I had to run it many times to get mine sorted.

You are AMAZING Bob! Thank you for the effort. Will test ASAP...

I've uploaded a version of the Sonos plug-in to the non-production store. This version supports adding specific speakers and doing so, disables the auto detection of speakers. I've added the join/unjoin commands. I've tested it as much as I can by creating a speaker simulator, but that really just allows me to create the nodes, it doesn't allow me to test the join/unjoin commands as I can't figure out the communication needed to do that. To add specific speakers, you use a similar method to adding speakers manually, by adding custom parameters: key = only_<unique> where <unique> will be the unique speaker address. For example: only_living value = {"name": "<speaker name>", "host": "192.168.1.43"} where <speaker name> is the name of the speaker (and will be the node name) You can add as many as you want, but I think only the first 5 will currently work. There are a number of cases that I don't account for and have no idea what will happen if you attempt them. You are supposed to only join a speaker to a coordinator, but that's what causes all the trouble with ST-Sonos, which speakers are coordinators changes dynamically. My implementation in the Sonos plug-in ignores that. It will allow you to attempt to join a speaker with any other configured speaker. If that speaker is not a coordinator, it should ignore the request, but may crash. I believe unjoin will fail silently if the speaker is not currently joined, but again, it could crash. The list of speakers generated for programs should be always be the same (for the same configuration). I think this handles your use case so try it out and let me know.

The module is purchased from UDI and then they add it and it then shows up on the ISY994i. I don't think you can get it elsewhere. Since support from UDI was discontinued It may not be possible but I hope you find a way.

Saw an old thread that there may be a hidden place on UDI where we can still buy this old module .. Anyone have suggestions / guidance ?

Now that's an oldie. Not necessarily a goodie. I didn't realize that Smartlabs was making the Togglelinc back in '06. Insteon devices from that time frame had power supplies based on a Microchip App Note 954 located here: https://ww1.microchip.com/downloads/en/appnotes/00954a.pdf They had a habit of burning up the filter cap/zener due to powerline voltages/spikes. Another issue was with the micro switch contacts themselves. Since the device is a relay switch, I'd guess that the 470uF cap (c2??) is breaking down (power supply drop out). You could open and inspect, but to be honest, these devices are probably at the end of their useful life. The relay units are not bad to open up (no Triac soldered to the heat sink). I still have a number in service, but when they die, will retire them. The good news is that you apparently have very well regulated power as well as rather "clean" powerlines. Later devices incorporated dual band as well as additional simulcasting improvements.

Thanks, that really worked! I first chose the overall Heal Z-Wave Network option and watched it work through the event viewer. Looks like it did a thorough job of stepping through each device, building a connection list, and then deleting the old device neighbor lists and rewriting them, via several iterations. I did see there were some devices that were not reachable on the first iteration or two, but those got better with further attempts. I do think there were a couple of devices that showed as "not awake" even though they are standard Zooz hardwired light switches (and which otherwise work normally). Later I found that each device has a Heal Z-Wave Network option so tried those on individual devices (namely the ones above that didn't get updated with the system-wide procedure), but strangely it looks like the Neighbor list was appended rather than replaced. In other words, those devices used to show Neighbors that I think are incorrect (i.e. neighbors that are very far away from the device). After the Heal procedure, those incorrect neighbors still exist, but there are new entries in the table with (correct-looking) neighbors too. The total number of entries in the table grew. I'm wondering if those old, incorrect entries could cause problems by asking the device to talk with neighbors who are too far away? @Michel Kohanim can you confirm details about how the Heal Z-Wave Network process works differently on a per-device bases vs. the overall network?

I have a security 3.0 garage door opener so I’m not sure if that would work or not but thank you. I picked up an extra one button remote from the big orange store. I soldered on a wire to the button contacts and connected it to my Controller. It’s now working as hoped. Thanks for your advice and tips y’all. I suppose if I was being really fancy. I would try to solder on the 12 V power from the controller to the remote so it never ran out of battery… I have the magnetic contact that came with the garage door kit installed as well, but frankly never figured out how to do the programming to make that useful. So basically I just use basic relay-on commands that open or close the door without any real intelligence or programming.

Wow, just wow!!!! Thanks!

You can also use this button and connect to it. https://www.amazon.com/883LMW-LiftMaster-Button-Control-Security/dp/B07W5RMN56/ref=asc_df_B07W5RMN56?tag=bngsmtphsnus-20&linkCode=df0&hvadid=80401905752479&hvnetw=s&hvqmt=e&hvbmt=be&hvdev=m&hvlocint=&hvlocphy=98088&hvtargid=pla-4584001431278556&psc=1

Try rebooting both your router and then eisy. Followed by clearing all 3 boxes in java when deleting files and downloading a new start.jnlp.

Does the plugin support the latest ratgdo boards? For the disco board, will there be nodes for car entering and leaving? I am thinking of upgrading from my 2.5i board.

The same thing happened with one of my Polisys, updating from 6.0.0 to 6.0.4, upon a reboot (which came after powering it up after I flashed it's SSD with a 6.0.0 image I had made in September). Looks like they're taking a page from Microsoft's playbook, doing upgrades on the fly upon a reboot. I'm guessing that they figured 6.0.0 wasn't stable enough to leave as-is on a running system.

From the lines or reporting I would say every file in the polisy was replaced. A guess would be about 3-4, 000 files were downloaded, unpacked, and installed. After turning on my spare polisy it updated itself from v6.0.0 to v6.0.4 and I wasn't even aware of it. It was only online for about 10 minutes. I must assume we have no control over updates anymore. I also have discovered PG3x is not accessible without online access now. As soon as my Internet was restored PG3x became available again.