All Activity

Thanks for the update. I have tried to update the plugin but it never really updated the roomba plugin. Finally just deleted the old one and reinstalled. that worked and now I am running 2.0.8. However when trying to connect the Roomba device I still see the following error in the log: 2025-10-09 22:01:25.678 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:getPassword: start password discovery 2025-10-09 22:01:25.679 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:getPassword: Connecting to 10.100.100.142 on port 8883 2025-10-09 22:01:26.150 Thread-5 (handleConfigDone) udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:1016)

Is there documentation available that details how to create a local plugin store (in addition to the web based production and non-production stores) and post plugins to that store?

Just an opinion on the Watchdog, I'd argue that restarting the node and taking it out of commission for a minute, even once a day, is undesirable unless an actual error is confirmed. Is there a way this check could be replaced by sending a short ping or dummy command to confirm the connection if no other events have happened in the interval? I assume sending a command and not getting a response would trigger recovery, but in that case, it would be justified. Then, assuming no errors, the node would be more responsive with 100% uptime.

I know it's turned on. I haven't played with it yet. Let me look into it. I'll get back to you.... Also, I noticed that in the tree, I cannot drag the all off buttons into a folder like I have with the hue in the node folder. It will not allow me to move it with the rest of it no matter what I do.. just a FYI Screenshot 2025-10-09 at 7.13.46 PM.heic

Not yet, as soon as I’ll get some hardware with motion :) Interesting, it’s a watchdog that checks last time bridge sent us any event, I may bump that to 24 hours

I’m also having sync errors since upgrading to 6.0. These 2 errors occur during sync when “Getting family Nodeserver” (running UDM 1.3.4 on iOS).

I'm checking out the various modes. This will be important for your documentation. Let me know if I have it figured out right so far: ondelay switch: The virtual ondelay switch has three possible statuses: Off, Timer, or On. The status of the switch will be updated to "On" after a set delay when it is first turned on by a On command (from a program or scene). During the set delay, the status will be "Timer". The delay in seconds is set by the onDelay parameter, and can be set as a fixed value, or from a variable value. The On trigger is control event based, and will retrigger the delay from zero if a new On control event is received while the timer delay is underway. So a series of On control events will delay the transition from Timer status to On, until the timer is allowed to run out without a new On control event. A forced off (FOff) control event will immediately cancel a ondelay switch that is in the timer phase to Off, or turn it Off if it's On. A Off command will turn the ondelay switch to Off if it's On. An Off command during the timer phased will be ignored. offdelay switch: has the same characteristics as ondelay, with the following differences: It has no On status. It will go from Off to Timer status if triggered with a On control event, and the timer can be retriggered just like the ondelay switch. Once the timer phase expires, it will go back to Off status. This is meant to be used to trigger the detection of it's status going to Off. I'll have to experiment more with the toggle to see exactly how it works.

Keeps happening, at least once every other day. Is this expected behavior?

I get notified of a disconnect/reconnect every 61 minutes. The log gives this reason.. 2025-10-09 16:55:42.303 Thread-120 (poll) udi_interface ERROR hue:_check_streaming: No updates from streaming thread for >60 minutes, streaming hung up? Restarting the node server... 2025-10-09 16:55:42.303 Thread-120 (poll) udi_interface.interface INFO interface:restart: Asking Polyglot to restart me.

I was also having this problem and removing the ssl directory and restarting udx worked for me

After updating did you clear your java cache, checking all 3 boxes, then download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp

I have finally upgraded and had to rebuild my system from scratch. However, when I launch IoX finder I get the following. It does not seem to cause any trouble with the admin console or with logging in. I click OK and it goes away? Thoughts anyone?

My other eisy works with its current configuration already in place (different wireless tag account as well), but it sounds like if I ever lost that and need to reconfigure it, I will lose that as well.

@apostolakisl nope, doesn't seem like you're the only one...from the sounds of it from @Jimbo.Automates it might be a bigger issue with the company that hosts the product.

ok @Guy Lavoie, @hart2hart, fixed the simple issue. Please keep trying to break this. I also, to @hart2hart, thought that it might be useful to be able to define in the json or yaml starting numbers. I have not pushed the commit, but will test a bit and roll that as a minor change to the beta. The docs are also being written as I go here. Please take a look and give some feedback with the hat of a new user.

Am I the only one? Has anyone else successfully authenticated wireless tag recently? I tried creating a new username and associated the same tag manager to that username and still get the same errors. Wireless tag shows it is connected and has the correct LAN address of my PG, so it is receiving the correct info from PG authentication, but on the other end, PG is not receiving the correct info or is failing to accept the info despite it being correct. I have tried this on both PG2 and PG3x running on different machines.

I managed to find a couple of things and it seems to be working for me now. First, it looks like the newer OpenSSL liibs now being used on eisy/Polisy block the security methods Roomba uses and I wasn't able to get a connection to the Roomba. I found a workaround for that overrides the block and that allows it to connect and I was getting data from the Roomba. At some point the external library being used switch to an asyncio based library but plug-ins are not asyncio. This means you have to some modifications in the plug-in to properly call the asyncio based functions in the library. I had already make most of those changes. But there was one place I didn't have it right and it was hanging in the initialization code where it waits for the Roomba to send out the updates to get the full state of the Roomba. Once I fixed that, the node was created and I think it's working. However, there still could be places where I don't have proper code in there to access the asyncio functions. Version 2.0.8 should be in the store now.

Sorry, I’ll fix the simple version tonight. My bad. the colon is being stripped by the polyglot device name function. its newish & must not like colons, I hadn’t back factored to the earlier devices. I’ll check with udi and see what they think on this.

Thanks, I’ll add that tonight. as well need to add more to my testing routine 🫢🙈

Thanks , good to hear all is well, looks like the install.log is happy as well. I might have over engineered the solution and just needed to peg the version so it doesnt try to compile a new one.

Ok I figured out where the bug is. In the Controller.py file, the new options need to be added to the parameter validation routine: I now have it all working. 😀 Nothing like having new options. Thanks for keeping this great plugin up to date with new features! With the toggle option, we can now add turn signals to our eisy!

Receiving the same Server Error / in Application trying to authorize wirelesstag node server Both when I attempted the trial version as well as the full version I just purchased $30 but cannot get working due to this error. Any progress on this @Jimbo.Automates ? Odd thing is mytaglist.com shows PG2 for the authorization while I'm running PG3x on a new eisy. I did have wirelesstag node server running on a PG2 on a rPi but have shut it down. Could not remember the password so i could not backup the PG2 and restore to PG3x Any ideas? Purchasing again sounded easier to get everything working again after upgrade to eisy from -994iz thanks

You also have to move the existing motion sensor up to the root level folder of the first iox tab. You can move the new back to it's location after the replace finishes. Trice can be quicker/easier, especially if scenes are involved

You have to wake up motion sensors before you can access them to make changes. As they go into power saving sleep. If you have the motion sensors model number and need the users manuals. Post them and we maybe able to help.

Does the hue v2 plugin support Motion in bulbs or that something that’s coming?