tazman

The main one I switched over so far was Virtual and I had to basically touch everything it was involved with to get it working.

There was a devfile on my configuration page and things seemed to clear up after deleting that. I worry about trying the migration again, maybe I will give it a try when I have more time. Thanks for all you do sjenkins!

I did the upgrade and it seems there is a problem according to the log file but it seems to me like things are still working. I don't know if this is because I'm still using the old config where I list them within PG3 instead of uploading a file to eisy. 2026-10-17 20:25:05.756 Thread-761 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting 2026-10-17 20:25:08.757 Thread-762 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting 2026-10-17 20:25:11.758 Thread-763 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting 2026-10-17 20:25:14.545 Command udi_interface INFO VirtualSwitch:DOF_cmd: 1:switch 1, {'address': '1', 'cmd': 'DOF', 'query': {}} 2026-10-17 20:25:14.545 Command udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2026-10-17 20:25:14.597 MQTT udi_interface.interface INFO interface:_message: Successfully set 1 :: ST to 0 UOM 25 2026-10-17 20:25:14.638 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2026-10-17 20:25:14.761 Thread-765 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting 2026-10-17 20:25:17.764 Thread-766 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting 2026-10-17 20:25:20.764 Thread-767 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting 2026-10-17 20:25:22.770 Command udi_interface INFO VirtualSwitch:DON_cmd: 1:switch 1, {'address': '1', 'cmd': 'DON', 'query': {}} 2026-10-17 20:25:22.770 Command udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2026-10-17 20:25:22.816 MQTT udi_interface.interface INFO interface:_message: Successfully set 1 :: ST to 1 UOM 25 2026-10-17 20:25:22.858 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2026-10-17 20:25:23.794 Thread-769 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting 2026-10-17 20:25:26.767 Thread-770 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting 2026-10-17 20:25:29.772 Thread-771 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting I also tried migrating the plugin to eisy and the temperature nodes did not work so I migrated back to PG3

I just wanted to say thanks to all for the information! I updated mine and everything went well I only had one timeout on my update path to the 7.46. My network is performing fine although I only have about 6 older zwave devices. I worry about not updating and losing the ability where the steps become difficult for the software.

I never performed this action but from what I've read there should be a replace modem when you plug in a different modem. If that is not present search for the procedure @Brian H post all the time.

UD Mobile has where you can see the history of devices so you could look in there but I don't know if it is available to use in programs yet. I hope it will be coming to eisy ui eventually and that might open thigs up more in the future.

I was having trouble with a sunset program also so I just set it for a specific time.

I was able to update without any problems!

Maybe write the program to toggle the chime at 10 if the value is 0. It might be a limitation that it does not have an on command it just accepts a toggle command.

It kind of sucks but you have to look at it from the developer's perspective when they have to rework the programming because the api keeps changing to try to lock the 3rd party developer's out. I guess you have to decide what is important to you and if you don't want to pay then consider using homeassistant.

If you ever setup the wifi then it is still in there and it will obtain multiple ip addresses. It used to be you press the multi function button 4 times to reset the wifi. You should be able to see in your router what kind of connection an ip address is using so I think this is going to take some investigation on your end to see exactly what is happening.

Is there a chance eisy is switching between wired and wireless or do you have a mesh system where eisy is changing acces points?

@DIYguy after you reset the device you restore not delete it then that will put it back to it's state that eisy thinks it was at before. If you are having communication problems trying to restore then you either have a failing device or noise on the power lines.

Did you try resetting the device before you do the restore?

Thanks for the update I think that is spelled out very well now to make it more clear. I look forward to getting things back to normal when it is all straightened out.