Help catching up the latest changes

[smorgasbord]

I'm an EISY user (previously 994i) using a mix of Insteon and YoLink modules. I haven't done anything with the system in over a year, since everything is working. I just had to replace a bunch of Velux skylights, and so now have new items to control. 

In the interim, it appears from my reading:

https://www.universal-devices.com/2025-liftoff/

That there's a new non-Java Admin UI as well as HomeKit support. I've looked but can't find the how-to/getting started pages for those features. Can someone point me at documentation for both? Oh, and I guess updating my software as well.

thanks!

[paulbates]

Both eisy-ui and HomeKit support are in ongoing development & testing. If you search the main forums page you can find each of those.

eisy-ui is in early stages and beta, so many things are not supported yet.

Edited Thursday at 11:53 PM by paulbates

[DennisC]

2 hours ago, smorgasbord said:

That there's a new non-Java Admin UI

While still in beta, you can catch up here:

 

 

[Geddy]

22 hours ago, smorgasbord said:

I haven't done anything with the system in over a year, since everything is working.

Since you haven't done anything in over a year your best shot is to check the wiki for the update process. Although, there was an update to 5.9 that required an updated operating system in the eisy. I'm not sure if that's been overcome and installed at the same time. It might be best to open a support ticket if your device is out of date for updates to be sure that it will update "easily".

You can open a support ticket here: https://www.universal-devices.com/my-tickets

What I would suggest first is try to go to this page in your browser: https://eisy.local:8443/WEB/sysconfig.txt

See what ISY version you're running as well FreeBSD

Maybe looking for FreeBSD:  FreeBSD eisy 14.1-RELEASE-p6   
(should be the top line of the output of the sysconfig.txt page)

A little ways down you should see:

************ IoX ************
isy-5.#.#
Name           : isy
Version        : 5.#.#_##
Installed on   : Date & Time 

 

You can look at the past (or current) release notes in the release area of the forums to see when the OS updated to FreeBSD 14. If you don't have that then you'll need help getting that installed before you can update to 5.9.x.

Be sure you read the release for 5.9.1. Pay special attention to item #3:

Quote

3. If you have never upgraded your unit, it's best to make sure you have release 13.1 or 13.2 of the OS (https://eisy.local:8443/WEB/sysconfig.txt). If you do not, please do not upgrade.

Lastly, be sure you backup your IoX (if you have z-wave back that up first then back up IoX). Then also run a backup of PG3x (just to be safe). I would also suggest you make a text copy of all your programs.

Right click the root program folder and select "COPY folder to Clipboard". Then paste that in a text editor (not a word processor!). That way if your system does not come back correctly and you have to rebuild or start over and you have problems with your programs you have a "hard copy" to reference and not having to go from memory of what items were in what programs.

Good luck if you proceed. It is a good idea to keep the system updated as releases are announced as they incrementally improve the system and take care of bugs along the way.

[smorgasbord]

Thanks, this is what I'm running now:

************ IoX ************
isy-5.9.1_7
Name: isy
Version: 5.9.1_7
Installed on: Thu Feb 27 14:25:50, 2025 PST
Origin: misc/isy
Architecture: FreeBSD 14:amd64

later on it says:

FreeBSD_version: 1401000

So, I don't think I'm too out of date.

[Geddy]

11 hours ago, smorgasbord said:

So, I don't think I'm too out of date

Cool….yeah, at least you’re already on 5.9 so you should be good with a standard backup before pressing the “upgrade packages” button. I would probably still make a text copy of programs (it’s just something I do now and then to have in case something fouls up). Allow a good bit of time to pass and watch the admin console screen for when a reboot is needed. 

Just also wanted to ask if you’ve reserved an IP address in your router. This way the eisy will come back to the same internal IP. 

When done with the reboot I would perform another power cycle to fully reset everything. Make sure you allow the device to fully restart from the first reboot. If you have access to the eisy check the wiki for the button presses for a shutdown or just press and hold the power button until it changes color. (I think the on is blue and off is red)

Clear your Java cache (check all 3 boxes), and possibly download a new start.jnlp file (not required, but good practice). Run start.jnlp to return the shortcut to your desktop.

I have run an update in a month or so and think my system is at 5.9.1_19. Check the sysconfig link again to confirm update.

Good luck!

[smorgasbord]

OK, so did the backup, and upgraded Java as well. Rebooted and things looked fine, so I did the update, got a prompt to reboot and did so. Logged in and looked around a bit, then rebooted manually as you suggested.

Seemed fine, but when I went into Polyglot, I had some trouble logging in, eventually did but then got logged out right away with this message:

Retried it a few times, and eventually got in. So far things seem to be working normally again now, but that was a little bit weird.

[Geddy]

@smorgasbord glad you got it sorted out. It is an odd error though and one that has shown up before, but not commented on recently. If it happens again (soon) try running the upgrade packages again and reboot then power cycle.

Are you using UD Mobile? Is it up to date?

If it happens again start a ticket before doing too much self troubleshooting or “repair” (other than update process or power cycles). As it would be beneficial to UD to see what is happening so if it’s a bug they can repair for the rest of us. 

[smorgasbord]

I am using UD Mobile on my iPhone and it is up to date. Don't see anything in Notifications that isn't from my debugging set ups. The UD Web Interface seems OK, too. Polyglot is fine now, too.

It seemed that maybe something was going on after the update/reboot that consumed the CPU and so I got that message. Eventually the something ended and all seems just fine now, thanks.