So it's been some time since I've updated my Eisy. I have the original Eisy, whatever hardware revision was current right before the newer version of it was released (bought it within a couple months of that release). Below you will see the screen shot of my versions from the Web-UI.

I guess I don't know if I do "update all" or if I do one then the rest, or if some of the others should be updated BEFORE doing the OS update or vice/versa.

Should I be doing this through the web version, or should I be doing this through the OG admin console?

Obviously I will be backing everything up the config and PG3 config first and also doing a fresh reboot of the system before triggering any updates so I have a fresh OS bootup without months old cache running.

But can someone please help me understand what the best actual update process is in my case? Thank you in advance!

You're good to go. The best way is still probably by doing it through admin console. Just do your backups and upgrade.

@StangManD just read through the latest release announcement from UD:

https://forum.universal-devices.com/topic/46914-os-144-release-is-now-available/

This gives you the information for running backups and the update.

Basically - you want to run the latest update from the Java Admin Console....NOT the web UI.

Thank you for your help.

I reviewed the info and backed everything up. I then performed the upgrade from the Java console and it seems to have gone through just fine. But I'm having issues.

Issue #1: When I load the web UI, I now get this error in the lower left corner. It's clearly talking about one of my ZWave devices, so I'll have to chase that down... that's never been a problem before.

Issue #2: The programs no longer control my Hue lights at all. I can manually control them through the UI but the programs do not trigger them at all. Other things with the programs trigger (insteon lights and switches) but the Hue light bulbs no longer trigger, even when I right click and say "Run Then" to manually trigger a program. I don't get this as I can manually control them from Nodes. This same exact behavior is true from the Java admin console.

Well, now I'm seeing what happened. It basically abandoned the Hue nodes that have been there forever and created new Hue nodes with different IDs. It also dropped the 0-255 light value and is now running on a 0-100 range, so I had to rebuild everything... groups are all a mess too, lots of duplicate "unknown group" entries that seem to be dupes of "All Lights", had to clean that up then go back through all of my programs and re-point everything to the correct nodes/devices. That was super annoying.

Issue #3: Not sure if this is by design or not but I can no longer access PG3 directly from the web URL (https://eisy.local:3000/), I get this error. Wonder if that's intended because it's now forcing me to go through the new UI, because I CAN get to it from there. Is this normal behavior?

Edited yesterday at 01:19 AM1 day by StangManD

Issue #1 and question in Issue #3 remain if someone could please let me know if you have thoughts there. I cannot find anything wrong with the Zigbee device that error is referencing, so I don't know what to think there. Thanks in advance.

Edited yesterday at 01:20 AM1 day by StangManD