I had not updated my Eisy yet. Yes, I am very late on that. Family things and house things needed fixing and Eisy was working just fine.

So tonight, I noticed some things not working. They are through the Eisy. Usually, this is just the Eisy losing connection to HA and HA can't turn on a light when I attempt a voice command.

As I checked the Eisy, it says it is updating. And that update never finishes.

So it's no longer available, it still has a nice blue on/off button on the front though.

I did just open a ticket.

Any ideas how to proceed? A wiki that I haven't found or just wait for a ticket response?

This kills a lot of stuff in my house. Eisy is integral.

3 hours ago, Bladerunner said:

As I checked the Eisy, it says it is updating

How do you "check" the EISY? Are you able to log into the admin console? If so, I would be very tempted to reboot it from there.

Otherwise, I tend to look for clues (or at least data points). Is the EISY connected to the network? Do I know the IP address? Can the IoX Launcher find it? Can I reach it from UDMobile or from a browser (requires v6.0). I know one can also attempt to log in from a computer terminal app, but I don't do this often enough to remember how to do this.

In the end, however, it is a computer. If I run across computers in any form that seem to be stuck in some perpetually unusable state, I reboot them. I believe that this can be done from the button on the front, but I am usually too lazy to look up how to to this with the button, so I simply unplug it, wait a few seconds, and plug it back in.

You can try using ssh to log into the eisy and reboot it from there. I use putty. You enter the ip address of eisy and it should give you a login screen. The login should be admin/admin. If eisy has been told to update and hours have gone by, it is not going to succeed. Eisy can take many minutes to update, but not hours.

This command will reboot.

sudo shutdown -r now  

I wasn't able to get to eisy at all. No network connect.
I created a ticket and Michel responded! I didn't expect that, it's Christmas Eve.
I dug up a monitor and keyboard and he gave me the entries to complete what appeared to be an incomplete update.
It's back up and running.
Thank you Michel!
I'm not sure why it was updating but it appeared to have started one. And it had gotten to a couple of hours so it wasn't a completed update.
I first noticed it when I finished a brisket in the smoker at 5am and walked up to the back door with a hot brisket in my hands and the lights didn't turn on.
There will now be a monitor, keyboard, and mouse mounted in my network/home automation area and with KVMs to systems.

Oberkc,

Yeah my usual would be unplug and plug it back in.

I did try that at first but nothing worked. The blue light was lit so the box was operational just not in a usable state.

Michel had me connect up the monitor and keyboard and press the power off and then back on. That final screen gave him enough info to help me.

The 994i and the eisy have been so reliable that I really don't mess with it at all. I use the java interface to code devices etc and backup, and UD Mobile to activate lights manually when I need to.

I should mention.

I don't know why but in Home Assistant, all of the helpers that I created to convert switches to lights were gone. I had to recreate them.

7 hours ago, Bladerunner said:

Michel had me connect up the monitor and keyboard and press the power off and then back on. That final screen gave him enough info to help me.

Thanks for the update. I have certainly had my share of tickets, but never had I needed to hook up a monitor and keyboard. I am glad it is working for you.

On 12/25/2025 at 4:45 AM, oberkc said:

Thanks for the update. I have certainly had my share of tickets, but never had I needed to hook up a monitor and keyboard. I am glad it is working for you.

LOL, neither have I. With all the interaction between the Eisy and other devices, it has been just running. I do updates on devices, etc and always gen a backup. When we lived with my dad caring for him for 11 months in another city, I was able to access Eisy and use it to make our house look lived in, and check on house heat/cooling, etc. I still find that pretty remarkable.
A monitor mount is on its way from Amazon. It will stay there and there will be ready.

Michel just helped me too. Mine was prompting me to update packages, so I did... and then it went offline. Unfortunately, I ended up having to re-flash it, but that's an easy process. My backup was a couple of years old, though, so I lost a few minor changes to my setup.

Note to self (and everyone else): Every time you change anything, be sure to create a backup!!!

My first aid kit is always ready: a usb drive with a recovery image, a screen and keyboard, and several types of backups.

Remember, there are two groups of computer users: those who have lost data, and those who will.

Bladerunner, I believe I have the same situation. Tried to follow all the Migration from Polisy instructions. The new EISY r2 was initially accessible from the Admin Console, but is now essentially dead.

I can see that the Eisy is wirelessly connected to my network, and the Web Portal shows both the Polisy (which is powered off) and the EISY, but when I click Select Tools: ISY Web Access, it reports ISY is not online.

Could you forward me Michael's instruction?

Untitled.pdf

Can you ssh into it? If you're not in a position to wait for UDI support in 2 days, you can try this:

ssh admin@eisy (or ssh admin@<ipaddress>)

Then try:

sudo pkg install -f isy

sudo pkg install -f udx

If it asks you to allow reinstalling packages, respond with yes.

If it completes ok, then wait at least 10 minutes, and then reboot:

sudo shutdown -r now

See if that brings you back up.

@Ray95xxx

Try removing power from the eisy for a minute

You also need to clear your java cache, be sure to check all 3 boxes, then download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp

If you are then able to access the eisy do another upgrade packages

6 hours ago, Ray95xxx said:

Bladerunner, I believe I have the same situation. Tried to follow all the Migration from Polisy instructions. The new EISY r2 was initially accessible from the Admin Console, but is now essentially dead.

I can see that the Eisy is wirelessly connected to my network, and the Web Portal shows both the Polisy (which is powered off) and the EISY, but when I click Select Tools: ISY Web Access, it reports ISY is not online.

Could you forward me Michael's instruction?

Untitled.pdf

If you have a new unit, do yourself a favor and open a support ticket and wait for UD to assist you. They are very responsive.

Techman, Thanks for your suggestions.

Unfortunately, Mac OS won't let me open the start.jnlp because it could not verify it free of malware??

On the other hand, clearing the java cache and power cycling the EISY did allow my original ISY Launcher to find my EISY. However only non-greyed out item in the File menu are Logon and Exit, so I can't restore the EISY from backups.

Suggestions?

@Ray95xxx

Take a look at this link

Admin console not working on Mac - IoX Support - Universal Devices Forum

@Ray95xxx To open the stat.jnlp file on a Mac, click on it, then go to the Apple / syestem Setings/ Privacy a& Security, then scroll down and you will see a spot Security where the file is listed and you can allow it to be opened.

then go back and it will open

On 12/26/2025 at 10:29 AM, mullercentral said:

Michel just helped me too. Mine was prompting me to update packages, so I did... and then it went offline. Unfortunately, I ended up having to re-flash it, but that's an easy process. My backup was a couple of years old, though, so I lost a few minor changes to my setup.

Note to self (and everyone else): Every time you change anything, be sure to create a backup!!!

Every time I make a change, I back it up. At least I am good about that. I should keep a USB drive ready too.

On 1/3/2026 at 2:36 PM, Ray95xxx said:

Bladerunner, I believe I have the same situation. Tried to follow all the Migration from Polisy instructions. The new EISY r2 was initially accessible from the Admin Console, but is now essentially dead.

I can see that the Eisy is wirelessly connected to my network, and the Web Portal shows both the Polisy (which is powered off) and the EISY, but when I click Select Tools: ISY Web Access, it reports ISY is not online.

Could you forward me Michael's instruction?

Untitled.pdf

I'm not sure if this will help but here's the commands that Michel used to get me out of trouble.

"Watch the monitor and then, login using admin (for login) and admin (for password), then issue the following commands. If prompted for password, type admin

sudo rm /var/udx/.upgrade_status
sudo rm /var/udx/.udx_install_cleanup
sudo dhclient re0
sudo service udx restart

Please send me a picture."

19 hours ago, DennisC said:

If you have a new unit, do yourself a favor and open a support ticket and wait for UD to assist you. They are very responsive.

I second that. I can't believe that Michel got back with me on Christmas eve. I expected to wait until after Christmas. It isn't just the device, it's the support behind it.

3 hours ago, Bladerunner said:

Every time I make a change, I back it up. At least I am good about that. I should keep a USB drive ready too.

A good practice is to: back up zwave, then backup Eisy, then go to programs, top folder, right click and copy folder to clipboard --> go to a text editor and paste it / save it with your backups.

Lastly, and less frequently, I also go to PGX and do a backup there.

In UDM, Every time I change something I do a back up to my "files" on my iPhone.

I do this every time I make changes, and also right before AND after any update to the system. The backups are fast and easy now in the AC.

Been burned too many times to not take the time to do this as standard practice. takes about 3 minutes.

V6.0.0 automatically updated to v6.0.3 on my polisy. Not sure what happened as I has some router problems that day but it hung my polisy good. No IoX and my own software would not run.

Michel gave me some commands in ssh to update my polisy, and a command line to see the progress. This took about an hour of constant updating lines and seemed to replace every file in my system, resulting in v6.0.4.

The point here is that 6.0.3 to v6.0.4 update took about an hour and no progress would have been seen without the command to expose the progress.