Lore

To get the brighten/dim to work, I already have the alexa category set to "device/light", setting the category to "scene" seems to ignore everything but on/off. Set room to 50% still gets me 100%. Weird and annoying.

Under program actions you can send X10 commands. It works on my EISY, at least for my legacy BSR X10 on/off module I bought in 1977.

With Alexa+, if I say dim or brighten an Insteon scene it works. If I say "Alexa, Set scene to 49%" it turns it to 0% and if I say "Alexa, set scene to 50%" it turns it to 100%. That seems like odd being that both dim and brighten allow me to get to in between levels, I just can't go directly to the brightness I want. Setting levels directly works with Hue and I swore it used to work with EISY/Insteon scenes.

My serial PLM will stop working after a day and the light is out. I can unplug it and plug it back in, then the light will come back on, however, the EISY still reports communication errors until I reboot. I've had several PLMs go bad, but not in this way before. Could it be the USB to serial cable? Also, why doesn't the EISY auto-recover? I've ordered the newer USB version of the PLM, figuring that will replace both the USB to serial cable and the PLM, but I'd like to know if my current PLM is really toast since I've not seen this kind of failure before.

Zones do show up, at least in my smaller setup. I only have one zone, but it shows up in the hue ISY list just like a room, which looks just like a bulb, but with triangles next to it. I didn't notice it at first because of my poor naming choice.

Current Version: 1.0.7 / Standard [Production] EISY with Hue Bridge Pro The Hue app, as well as the Hue Alexa skill will update a bulb's status even if disconnected. Turns out I find this useful. The PG3 Hue plug-in doesn't seem to do this so I can't script events that monitor disconnected bulbs. I found a work around, to put the bulb in a room or zone, which does work with the plug-in. In the case of a single bulb in a room, setting a disconnected bulb to 100% will set the room to 100%, but leave the bulb status alone. The bulb status will change, for example, on Alexa for routines, so this behavior is inconsistent with both the room status and other vendors that support Hue. Since Hue bulbs draw power, it's not uncommon to power them down with Insteon, or, more recently, to monitor an old disconnected bulb to capture the status of a motion aware zone. Otherwise the current plug-in appears to do everything I need.

Any update? The latest version appears to be retrying too fast, or retrying before disconnecting or something as it's leaving my Roombas in a weird state where I can't get info from the app without rebooting the Roombas. This is new behavior.

I'm not trying to connect with the app until after I stop the plug-in and the Roomba acts like it still has a connection. Is it possible the app is trying to reconnect before the previous try has disconnected? It seems to connect the first time, and if I'm quick on the button, it'll even move on to the next Roomba.

I can't seem to get past discovery. The PG3 Roomba plug-in seems to make the Roombas block connection attempts, even from the app, because it says the Roomba may be on another subnet when I try to display the connection info. If I stop the plug-in and reboot the Roomba, or wait, it eventually recovers. The plus-in is stuck doing this when I stop it... 2025-11-03 13:56:55.260 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.1.211 on port 88832025-11-03 13:56:55.264 Thread-5 (handleConfigDone) udi_interface ERROR roomba-poly:getPassword: Connection Error (for 192.168.1.211): [Errno 61] Connection refused 2025-11-03 13:56:55.264 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:getPassword: start password discovery 2025-11-03 13:56:55.265 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.1.211 on port 8883 2025-11-03 13:56:55.268 Thread-5 (handleConfigDone) udi_interface ERROR roomba-poly:getPassword: Connection Error (for 192.168.1.211): [Errno 61] Connection refused 2025-11-03 13:56:55.268 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:getPassword: start password discovery

From 2.0.17.. 2025-11-02 10:02:30.597 Thread-6 (userDiscover) udi_interface ERROR roomba-poly:getPassword: 'utf-8' codec can't decode byte 0xf0 in position 0: invalid continuation byteTraceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026dfb_3/roomba-poly.py", line 795, in getPassword password = str(data[7:].decode().rstrip("\x00")) ^^^^^^^^^^^^^^^^^ UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf0 in position 0: invalid continuation byte

So it sounds like a need to move all my Roombas (and their chargers) to a line in front of my computer so I can push their buttons and discover at the same time?

2.0.16 log Roomba_10-31-2025_51756_PM.zip

I updated, but I didn't see the version change. Still 2.0.14. Here's the new log. Roomba_10-31-2025_42213_PM.zip

Log File Roomba_10-24-2025_124503_PM.zip

Is it an issue with multiple Roombas? I PM'd you the file as well (at the same time I posted it.)