Looks like the Polisy won't getting this update. I just thought I'd try it on one of my test units and the upgrade log file says: Upgrade failed: field upgrading of non-eisy devices no longer available ...

@Guy Lavoie Thanks for trying. I tried on my Polisy, too, and it didn't appear to do anything, but I didn't know how to check status. Where is this upgrade log file located?

-Tom

I, along with chatGPT, found and fixed my issue, the eisy-ui is now running, the PG3 dashboard is now also looking good, and the online connection is green too.

It seems there is a bug in the "pluginConnections.js" file. If you have MORE THAN 1 plug-in installed, it will work fine. If your have 0 or 1, it will fail.
"If so, eisy-ui 1.2.0 has a clear empty-list programming bug: this line assumes connection always exists:" on line 27.

ChatGPT supplied a fix, I installed and ran it. All good now.

2 minutes ago, xlurkr said:

@Guy Lavoie Thanks for trying. I tried on my Polisy, too, and it didn't appear to do anything, but I didn't know how to check status. Where is this upgrade log file located?

-Tom

you ssh into it and watch the log file as it grows:

tail -f /var/udx/logs/debug.log

This is handy for observing the progress of upgrades as they happen.

@Guy Lavoie Thanks for the tip! Will add it to my box o' tricks.

-Tom

Been three hours now and no EISY

Will manually reboot and then open a ticket if it doesn’t come back up

After manual reboot, appears all is up and running. Two notes:

-EISY was so hot, I couldn't hold it.

-UDI fixed the single plugin issue above as I have to upgrade again to get the latest UI.

Will see what happens next!

Runtime from upgrade button in AC to reboot: 24 minutes

Runtime from reboot button in AC to

• AC accessible: 5 minutes

• eisy-ui accessible: 13 minutes

• PG3 accessible: 18 minutes

Total upgrade time ~42 minutes.

Once the PG3 dashboard was up I found that my 3 hue node servers (still running old version 0.1.11) and ratgdo (4.0.8) all would not start. I had to re-install each of them into their same slot from the plugin store screen. These 3 hue node servers have notoriously been problematic for me over the years, likely due to the number of devices (hence the need for 3 hubs). I've been slowly moving my programs that reference them to Home Assistant so I can get Hue off the eISY.

All appears to be working after above steps with one exception: Ratdgo did not restart correctly. Restarted the plugin, seems to be working.

Upgrade appears to have completed successfully. ~30 minutes start to finish

5 hours ago, RRalston said:

@aeroRC did you delete files and apps from the java console first? that should clear up that problem.

I upgraded this morning. pretty much every program within the updated eisy-ui shows "Error loading data". However, the same programs appear to be fine within the AC. I have submitted a new ticket for guidance.

Rob

Javier from UD support identified my issue so it is now corrected. I had an "&" in two email group names that was causing the issue.

Upgrade completed with out issues... Great job UD Team.

Upgrade now working for all items. Something hanged up durring the upgrade. Opened a ticket and after Michel checked a few things just said to reboot. After three reboots all systems now working, IOX, PG3, UDX and connection to home assistant. Somehow even though I thought I setup the system with a fixed IP address it changed it after the update. Once I fgured this out got PG3 and home assistant working.

Now that I can update and change programs in UDX will start switching over to using it rather then the admin consule.

That program editor is going to take some getting used to...

Yes, to many drop down boxes in UDX for each step of writing a program.

In IOX everthing you need is on the program creation page and you just need to move to it with your mouse to create each part of the program.

Upgraded packages this morning and left for eight hours. After returning home, the state of my lighting was such that I could tell things were not working as they should, and I could not access the Java interface or the EISY-UI, or polyglot. I could get to the portal, which indicated it was connected. I could see from my router that it was connected to the EISY. UDMobile seemed to be working.

I physically unplugged the EISY and waited a few seconds to plug it back in. Now (after a whole minute of inspections), I can get to the java interface and EISY-UI. The upgrade seemed to have concluded successfully. If I find more, I will report back.

Edit: at it I think the update may have broken my Roomba plug-in

Edited 16 hours ago16 hr by oberkc

I saw somewhere that AI is going to do all our future programing for the eisy. Just tell it what you want and it does the rest.

Upgrade went smoothly. After 3 hours EISY did not send notification of being back on line.

-- Unit pings
-- Portal says the device is online
-- Opens EISY-UI to login page and then redirects to port 3000 which does not connect
-- No interaction with mobile app
-- Unit appears in IoX Admin Console list, but does not present link to open actual console

SO: I did a reboot from the hardware console CLI.

Everything came up, uname -a reported the correct FreeBSD version
-- EISY-UI reverted to HTTP only. HTTPS will not connect
-- Listing and editing programs in the UI works well
-- Admin Console works great
-- UD-Mobile appears to work, however after syncing the app the following screen appears:

I was able to update to 6.1.1 with no issues.

Not sure where I would see the OS 14.4?

3 minutes ago, atomicboy said:

I was able to update to 6.1.1 with no issues.

Not sure where I would see the OS 14.4?

The raw method is to ssh into it and do:

umame -a

Otherwise it should appear in the sysconfig.txt file that is accessible as shown in the release announcement

6 minutes ago, Guy Lavoie said:

The raw method is to ssh into it and do:

umame -a

Otherwise it should appear in the sysconfig.txt file that is accessible as shown in the release announcement

Thanks. I will check it out.

That worked.

Edited 17 hours ago17 hr by atomicboy

Oops its:

uname -a

4 hours ago, Guy Lavoie said:

Looks like the Polisy won't getting this update. I just thought I'd try it on one of my test units and the upgrade log file says: Upgrade failed: field upgrading of non-eisy devices no longer available ...

I'm still waiting for some arithmetic bugs to fixed from v5.0.1. Polisy was always tooted to be the same basic hardware as Eisy and compatible. Guess not.

However I am using my polisy as a LAN switch due to a shortage of ports on my secondary router.

Edited 17 hours ago17 hr by larryllix

I will do the upgrade this weekend. Can anyone comment on the enhancement to scenes?

1 hour ago, larryllix said:

Polisy was always tooted to be the same basic hardware as Eisy and compatible. Guess not.

I'm sure you meant "touted", but I agree and am in the same boat. @Michel Kohanim perhaps you could at some point let us active Polisy users know if the current exclusion is temporary or permanent. And maybe also if you are willing to let us in on the discount deal being offered to 994 users, since some of us have actually invested in more generations of your products than those who are still on 994s.

-Tom