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.

I've been tempted to plug my fridge into an on/off module. From it's perspective, it's just a random power outage that happens during peak rates.

That's a good idea. I still have a smart power strip I bought at Radio Shack 35 years ago to solve a TV/amp problem. I always see it at the bottom of my power strip box, but I hadn't considered it for power savings. I can think of at least two places where smart strips might help to save a few watts. Most of my vampires, however, are tricky to kill without losing something. My Apple TV is also my homekit hub, for example.

I agree completely, however the new SCE rates (averaging over 50 cents a KWh during peak pricing) and us crazy smart home folks change the math a bit. My Insteon switches, for example, cost me more per month on my electricity bill than my pool and spa filters because the Insteon switches draw power 24/7, right through the peak billing hours and I have 125 of them. All my lights are modern high lumen per watt LEDs and are set to come on dimmed unless I ask for "work lights." My winter average draw right now is 600 watts, 200 watts of fridges, home theaters, lighting, pool filtering, etc, and 400 watts of which are power vampires like Roombas, Alexas, sensors, cameras, alarms, power failure units, GFCI outlets, Insteon switches, and other things that bleed power 24/7. Leaving a 50w bathroom fan on is nearly 10% of my average usage, more if I'm away, and will show up in the bill. My recent tweaking cut 200 watts from my average usage and should save enough to buy an Insteon Module a month, but more importantly, it gets me closer to a practical off-grid system.

I have everything on Insteon switches or modules and have been slowly adding programs to lower my power bill. At sunrise, or if I leave, I turn off any lights left on. My bathroom fans default to 70% which uses half the power and will turn off after 40 minutes if left on. My recirculating pump turns on before I wake up at 60%, which uses less than half the power but still gets the job done. It turns off during peak pricing. I'm looking to add mmWave occupancy sensors as soon as something is supported in PG3. What are other people doing with automation to save power?

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.