Lore

Here's how I fix mysterious problems, and I have a 100+ Insteon network previously plagued with almost every known issue. Make the network more robust against noise by replacing pre-2012 modules. They don't validate messages and can fix up and repeat noise to the entire network, even newer modules. Reduce noise by moving modules away from power supplies, computers, and RF sources. Add Insteon power line filters to equipment with motors or switching power supplies. Restore devices with problems, and devices that might be repeating the signal. If something is turning on often enough, try disabling things that might be causing it to see if that stops it. The A/C, the fridge, the EISY, you can even try disabling just the RF or just the powerline communications in a module to determine which band the problem is on. My whole system acted funny with just one failing module not near where the issues were. It can be hard to figure out. Another crazy issue I had, were modules programed to respond to X10. A restore won't remove that, only a hard reset, followed by a restore. I tested for X10 by writing a program on the EISY to send "ALL LIGHTS ON" on every X10 channel, followed by "ALL OFF" after a delay so I could turn on my non-light devices and see if any went off. False X10 signals are even more likely to be created by noise, but also unlikely to be programmed unless you did it yourself or bought used modules that weren't reset.

Portal appears to have been down for me since about 9:10 PST.

I miss the portal already. No Alexa commands, no UD Mobile notifications, nothing. I almost had to get up to turn on a light when I remembered Mobilinc talks straight to the EISY. Still, what if my arms were full and I needed the lights on?!?!

I just moved from a hardware failed Polisy to an EISY and both my VUE node and Roomba node are getting those same errors. I already had to install the dev. packages for the HUE node which is working fine. I've reinstalled, deleted and reinstalled, rebooted, etc. No luck. I restored from a Polisy backup, but it was current, PG3X, IOX 5.8.4.

The Insteon leak detectors I have latch the wet state. I have to clear the water and quickly tap the little button to send the all clear update.

Any plans on a work around? I'm a C++/Assembly programmer, so my sympathies with Python. My Roombas need light to navigate and it was sort of nice to script it all.

Hue alone drops for 1 minute at midnight with the above debug log and two notifications showing disconnect and connect. Hue Hub V2 is hardwired to the same switch as the Polisy and nothing else drops.

I updated to PG3x and am still getting the Hue drop out at midnight. Polisy running 25 Hue Bulbs, 126 Insteon devices, 3 Roombas, 1 Rachio, 2 Venstar, 1 Vue, Weather, and Notifications. PG3x Version 3.2.13 Frontend Version: 3.2.13 IoX Version: 5.7.0

That worked. All connected. Just waiting for SCE to replace my meter for free because it turns out it wasn't HAN ready.

I installed and entered my login. It's showing disconnected. Rebooted, same thing. The log shows the same errors repeated.. 2023-10-04 20:11:23,106 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-10-04 20:11:23,107 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db953c7c4_6/vue.py", line 10, in <module> 2023-10-04 20:11:23,108 MainThread udi_interface ERROR udi_interface:write: import pyemvue 2023-10-04 20:11:23,109 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db953c7c4_6/pyemvue/__init__.py", line 2, in <module> 2023-10-04 20:11:23,110 MainThread udi_interface ERROR udi_interface:write: from pyemvue.pyemvue import PyEmVue 2023-10-04 20:11:23,110 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db953c7c4_6/pyemvue/pyemvue.py", line 8, in <module> 2023-10-04 20:11:23,112 MainThread udi_interface ERROR udi_interface:write: import boto3 2023-10-04 20:11:23,112 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2023-10-04 20:11:23,113 MainThread udi_interface ERROR udi_interface:write: : 2023-10-04 20:11:23,114 MainThread udi_interface ERROR udi_interface:write: No module named 'boto3'

Same here. Got the email, tried to upgrade, 5 beeps, no change to the version. I assume the entire Polisy update is disabled, IOX 13.2 and ISY 5.7.0, and I'll just have to wait.

I have a Polisy. PG3 Version 3.1.23 Status: Connected Frontend Version: 3.1.23 IoX Version: 5.6.3 Connected No PG3x. I only have what comes down from updating on the ISY screen. Everything has IP reservations and I configured the node with the Hue Hub static IP. The recovery is quick and complete. I have 25 bulbs on my Hue Hub V2, so maybe a longer list causes a brief delay and the time out detection is too short? The Hue Hub really needs a refresh.

Nope. Plus the other nodes stay up, like my thermostat, which will report a drop if I reboot. I suppose the router could do a quick drop at midnight for some reason and it's too quick to be caught by the other nodes. It's not a big deal, it's just that an update to UD Mobile now tells me about such drops.

2023-07-26 00:00:04,272 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message longPoll 2023-07-26 00:01:04,761 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING longPoll 2023-07-26 00:01:04,762 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-07-26 00:01:04,765 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-07-26 00:01:04,766 MQTT udi_interface.interface INFO interface:_disconnect: MQTT Unexpected disconnection. Trying to reconnect in 10 seconds. rc: 7 This is the log. Seems to show some sort of polling, then a disconnect. It's the same every night.

The node goes offline and comes back at 12am exactly every day. Is this an intentional kludge or some clock timer bug?