brockp

I don't, they are quite old.

Actually just noticed I have some ZWave Multi-Sensors and they also disappeared.

I used to use EZFlora but it blew up in a storm, I sense replaced with PG + OpenSprinkler, but then I came across several of them and EZIO8SA's in a box of used parts. I don't really have a use for them now, I'm slightly tempted to swap out the OpenSprinkler for them as I don't use any of it's features and it's WiFi is flaky on my network but it's working. Ideas how to use them? Being generic relays the EZIO8SA should be good for about anything I just need ideas.

I have over 100 insteon devices, mostly all in the last 10 years and dual band. Everyhting is very reliable, Except for this one wallwart lamplinc we setup for a changing table. It's from my first Insteon setup in an apartment. It responds to the remote in the room and whole house schemes, but the IOX almost always says it's unable to communicate. I messed around with old access points and nothing appears to really resolve issues with it. I know this is not a dual band device, I don't have any other lamp lincs and was trying to avoid as this is a only for a few years things but it bugs me. This device is probably 15 years old, is it just dead? Did those devices have bad caps like the PLMs did? (my PLM from that erra that I moved from Mr. House to ISY also failed still have it, never re-capped). More curious, I can solder so would be willing to sacrifice it.

I am on a current modern PLM on my esiy. I recently got a lot of older parts from ebay which included many USB and Seriel PMLs, some are quite old, all 2413U and 2414U Knowing the future is Insteon is uncerten ( hope not, but not sure they are that popular anymore and their devices cost much more) I'll keep a few of these as spares, but a few questions. Can IOX restore from a newer to an older PML? Is it no issue to go between serial and USB PLMs? (I have never used USB) Is there an easy way to test these PMLs to see if they are good or if some need re-capping or or just dead? Or is it really just wait until it's needed and if it works it works?

We have some Z-Wave locks, I had two of them set up on the favorites page. I go to use them today, and they are missing. I go to Home and they show up with lightbulbs and the lock features are missing. I re-sync ud mobile and they switched back to locks but the favorites are still gone. All my other favorites are still there. Id try using UDMobile for linking some new insteon devices this week which needs syncs. So I'm not sure if something choked during that time. More an FYI report, it appears different than the favorites issues others were having.

Thanks deleted, put the roomba into linking mode, installed the connector, heard the roomba say "thanks your ready to clean" and I even see this in the log even on restart 2025-11-01 22:15:32.487 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2025-11-01 22:15:34.402 Thread-1 udi_interface INFO roomba-poly:addNodes: Create a new node for Main Floor Vac ... 2025-11-01 22:15:34.402 Thread-1 udi_interface INFO roomba-poly:addNodes: Robot name = Main Floor VacBut yet no node is actually created in PG3 it's still blank, and nothing in the java admin console.

I added new devices for the first time in a long time so not sure if this started now or earlier. Also not seeing other reports it's probably a me thing. First when I first log in, the 'New Insteon Devices' window always shows up for whatever the last device I added was. In my case a 2842-222 motion detector. I can close it, but comes right back next time I load the UI. Similarly, devices appear to have shown up 3 times in the UI. It's the same address as the New Insteon Devices shows up every time and I already unlinked it once and relinked. Next time in the admin UI 3 copies and the new devices window. Second, Similar behavior with ZWave The next device I added, I started by excluding one of my Somfy shades that uses the zwave bridge. It was acting weird, said it couldn't connect, so I removed it and added it back. Now every time I connect to the UI the Z-Wave Device Discovery window is always there and clicking cancel doesn't make it go away it's stuck. Similarly, when I added it even if I say 'Group Devices' I now have 3 entries, but only for a subnode 'Binary Switch'. I can do 'group devices' on one of the binary switches and it added it to the shade's main node, but the other two stay. Any thoughts why this would be? It's really cluttered, and having all the windows that never used to be there. I"m worried my install is corrupted.

Updated to 2.0.13 and when I try to discover my vac I'm getting 2025-10-23 20:37:50.484 Thread-8 (userDiscover) udi_interface ERROR roomba-poly:getPassword: name 'roomba_port' is not defined Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026aaf_5/roomba-poly.py", line 779, in getPassword LOGGER.info(f'Connecting to {robot["ip"]} on port {roomba_port}') ^^^^^^^^^^^ NameError: name 'roomba_port' is not defined

I am getting the same results, but I never had the Roomba plugin before to know if it even works. Ours is an S9+ When I press + hold the home button after a few second I get a spinning blue LED circle (there is no wifi light) and the above errors almost identical to Lore. ac","robotid":"046421AC1F41453CA786C42390BAFA01","ip":"192.168.84.228","mac":"50:14:79:1E:FD:42","sw":"soho+22.29.10+2023-10-09-2b3f87f75e8+Firmware-Build+4863","sku":"s910020","nc":0,"proto":"mqtt","cap":{"carpetBoost":1,"binFullDetect":2,"oMode":2,"dockComm":1,"edge":0,"maps":3,"pmaps":10,"mc":2,"tLine":2,"area":1,"eco":1,"multiPass":2,"team":1,"pp":0,"pose":2,"lang":2,"gentle":1,"5ghz":1,"prov":3,"sched":2,"svcConf":1,"ota":2,"log":2,"langOta":0,"ns":1,"tileScan":1}} with irobotmcs 2025-10-20 21:07:05.712 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2025-10-20 21:07:06.230 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2025-10-20 21:07:06.451 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:_get_response: Comparing {"ver":"3","hostname":"iRobot-046421AC1F41453CA786C42390BAFA01","robotname":"Main Floor Vac","robotid":"046421AC1F41453CA786C42390BAFA01","ip":"192.168.84.228","mac":"50:14:79:1E:FD:42","sw":"soho+22.29.10+2023-10-09-2b3f87f75e8+Firmware-Build+4863","sku":"s910020","nc":0,"proto":"mqtt","cap":{"carpetBoost":1,"binFullDetect":2,"oMode":2,"dockComm":1,"edge":0,"maps":3,"pmaps":10,"mc":2,"tLine":2,"area":1,"eco":1,"multiPass":2,"team":1,"pp":0,"pose":2,"lang":2,"gentle":1,"5ghz":1,"prov":3,"sched":2,"svcConf":1,"ota":2,"log":2,"langOta":0,"ns":1,"tileScan":1}} with irobotmcs 2025-10-20 21:07:07.460 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2025-10-20 21:07:07.685 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:_get_response: Comparing {"ver":"3","hostname":"iRobot-046421AC1F41453CA786C42390BAFA01","robotname":"Main Floor Vac","robotid":"046421AC1F41453CA786C42390BAFA01","ip":"192.168.84.228","mac":"50:14:79:1E:FD:42","sw":"soho+22.29.10+2023-10-09-2b3f87f75e8+Firmware-Build+4863","sku":"s910020","nc":0,"proto":"mqtt","cap":{"carpetBoost":1,"binFullDetect":2,"oMode":2,"dockComm":1,"edge":0,"maps":3,"pmaps":10,"mc":2,"tLine":2,"area":1,"eco":1,"multiPass":2,"team":1,"pp":0,"pose":2,"lang":2,"gentle":1,"5ghz":1,"prov":3,"sched":2,"svcConf":1,"ota":2,"log":2,"langOta":0,"ns":1,"tileScan":1}} with irobotmcs 2025-10-20 21:07:08.690 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2025-10-20 21:07:09.039 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:_get_response: Comparing {"ver":"3","hostname":"iRobot-046421AC1F41453CA786C42390BAFA01","robotname":"Main Floor Vac","robotid":"046421AC1F41453CA786C42390BAFA01","ip":"192.168.84.228","mac":"50:14:79:1E:FD:42","sw":"soho+22.29.10+2023-10-09-2b3f87f75e8+Firmware-Build+4863","sku":"s910020","nc":0,"proto":"mqtt","cap":{"carpetBoost":1,"binFullDetect":2,"oMode":2,"dockComm":1,"edge":0,"maps":3,"pmaps":10,"mc":2,"tLine":2,"area":1,"eco":1,"multiPass":2,"team":1,"pp":0,"pose":2,"lang":2,"gentle":1,"5ghz":1,"prov":3,"sched":2,"svcConf":1,"ota":2,"log":2,"langOta":0,"ns":1,"tileScan":1}} with irobotmcs 2025-10-20 21:07:10.045 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2025-10-20 21:07:10.142 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:_get_response: Comparing {"ver":"3","hostname":"iRobot-046421AC1F41453CA786C42390BAFA01","robotname":"Main Floor Vac","robotid":"046421AC1F41453CA786C42390BAFA01","ip":"192.168.84.228","mac":"50:14:79:1E:FD:42","sw":"soho+22.29.10+2023-10-09-2b3f87f75e8+Firmware-Build+4863","sku":"s910020","nc":0,"proto":"mqtt","cap":{"carpetBoost":1,"binFullDetect":2,"oMode":2,"dockComm":1,"edge":0,"maps":3,"pmaps":10,"mc":2,"tLine":2,"area":1,"eco":1,"multiPass":2,"team":1,"pp":0,"pose":2,"lang":2,"gentle":1,"5ghz":1,"prov":3,"sched":2,"svcConf":1,"ota":2,"log":2,"langOta":0,"ns":1,"tileScan":1}} with irobotmcs 2025-10-20 21:07:11.150 Thread-5 (handleConfigDone) udi_interface ERROR roomba-poly:discover: Failed to discover any Roomba robots 2025-10-20 21:07:11.150 Thread-5 (handleConfigDone) udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2025-10-20 21:07:11.150 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:getPassword: start password discovery 2025-10-20 21:07:11.150 Thread-5 (handleConfigDone) py.warnings WARNING warnings:_showwarnmsg: /var/polyglot/pg3/ns/0021b9026aaf_5/roomba-poly.py:769: DeprecationWarning: ssl.wrap_socket() is deprecated, use SSLContext.wrap_socket() 2025-10-20 21:07:11.150 Thread-5 (handleConfigDone) py.warnings WARNING warnings:_showwarnmsg: /var/polyglot/pg3/ns/0021b9026aaf_5/roomba-poly.py:769: DeprecationWarning: ssl.wrap_socket() is deprecated, use SSLContext.wrap_socket() 2025-10-20 21:07:11.151 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: Exception in thread 2025-10-20 21:07:11.151 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: Thread-5 (handleConfigDone) 2025-10-20 21:07:11.151 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: : 2025-10-20 21:07:11.151 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2025-10-20 21:07:11.151 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.11/threading.py", line 1045, in _bootstrap_inner 2025-10-20 21:07:11.151 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: self.run() 2025-10-20 21:07:11.152 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.11/threading.py", line 982, in run 2025-10-20 21:07:11.152 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2025-10-20 21:07:11.152 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026aaf_5/roomba-poly.py", line 869, in handleConfigDone 2025-10-20 21:07:11.152 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: discoverRobots() 2025-10-20 21:07:11.153 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026aaf_5/roomba-poly.py", line 957, in discoverRobots 2025-10-20 21:07:11.153 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: getPassword(robot) 2025-10-20 21:07:11.153 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026aaf_5/roomba-poly.py", line 769, in getPassword 2025-10-20 21:07:11.153 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ssl_socket = ssl.wrap_socket( 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ^ 2025-10-20 21:07:11.154 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.11/ssl.py", line 1473, in wrap_socket 2025-10-20 21:07:11.155 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: raise ValueError("certfile must be specified") 2025-10-20 21:07:11.155 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: ValueError 2025-10-20 21:07:11.155 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: : 2025-10-20 21:07:11.155 Thread-5 (handleConfigDone) udi_interface ERROR udi_interface:write: certfile must be specified

Yeah I'm comfortable with CLI (spend most my day on Unix/Linux CLI). there wasn't a python process. Turns out others found the issue just after and the author released an update that fixed the issue with that plugin. I was just surppised that it didnt' log anything, maybe I needed to find a more central log if the plugin had errors and coudln't start. Anyway it's fixed now, it just doesn't appear to work with my specific roomba which is sad.

Thanks, this was helpful, after a few more reboots restarting the plugins now produces log data (roomba was a bug in the plugin that the author patched) Weatherbit is still weird but if I hit restart it populates now and it didn't before so just a headscratcher for a moment there. It's still showing 429 to many requests but my forecast data is still up to date and I'm using the default settings. If I login to check on my API key it doesn't have any data to show how my API rate is to compare so I guess if not broken just leave it.

I'm trying the Roomba plugin. It needed an update and the author did (linked below) I updated the plugin and now along with the log not appearing it is stuck in disconnected state. If I click restart I never get a notification on the UDI app like I do for all other plugins. The uptime never changes also. If I click stop I will bet the lower right Nodeserver stopped successfully. but uptime and and status stays Disconnected. If I click start I get Plugin Start: Already running. I tried deleting and reinstalling the plugin and behavior stays the same. So I cannot get a log (I even SSH'd in there is no logs folder after re-installing the plugin) but it doesn't really even try to start? Thoughts? Do I have some internal state stuck?

I'm trying to debug two plugins (weatherbit and roomba) but when I go to log viewer it doesn't appear even when set on debug. But for one at least (weatherbit) if I click download log I do get a log file I can look at. This is after updating to IoX 6.0.0 and 3.3.22 I'm on firefox on osx,

Thanks I opened a bug. I Did also try editing the python and it got further log says made a node but no node actually appears. My guess is the plugin is orphaned given the python issue just kinda gives the feeling of nobody is using it.