I've had an ISY-994 forever and bought an EISY some years ago to replace it but never did, though I did access the UI once or twice and upgraded the software on occasion. I finally started the process yesterday but forgot about the eisy web ui.

First I "restored" the backup I created on the ISY-994i (from the admin console). Then i noticed that new packages were available so I upgraded from the admin console . I think the eisy had been on 5.9.0 or maybe 5.9.1.

16 hours later I couldn't access the eisy.ui either by eisy.local or [ip] IOX finder did not find it. (it did before the upgrade)

I attached to the EISY via SSH-- according to ps -aux, no named processes taking any CPU time. I rebooted eisy and -- same result (after a short period where there were some processes doing things)

I referred to this document

https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide

and was able to add the eisy to the finder -- it shows up as ISY rather than IoX though, -- type eisy and version 6.0.4, so that's progress. SSH works. Admin console is accessible. But I can't access eisy ui by any of the suggested methods (from the same wired LAN)

I have a Unifi edgerouterX but can't imagine it's a firewall issue. I tried to connect to eisy ui with both a windows 11 machine and a mac. Firewall was off on the Windows machine.

From the finder I found I could load the polyglot 3x dashboard (eisy.local:3000/dashboard). This connected to the portal and authenticated. After doing that I got different responses from Chrome on the PC -- eisy.local didn't send any data or refused to connect rather than not being found. Is there a page name I should use (like eisy.local:80/ui ?

There is something I am missing! Is there some setting in the admin console or that i can access by SSH to turn on EISY-UI? Should I do a factory reset on the EISY and start over??

Clear your java cache, be sure to check all 3 boxes, then download a new version of the IoX Launcher from here:

https://isy.universal-devices.com/start.jnlp

If you still having issues try removing power from the eisy for about 1 minute

It will show up in the finder as an ISY

To access eisy-ui from your browser http://eisy.local/

Edited 5 hours ago5 hr by Techman

Thanks but I can get to the admin console using java the old fashioned way using the launcher.

I wanted to look at the new eisy.ui. The instructions say to use point a browser to eisy.local or to the IP adress of the EISY. This doesn't work.

ALso http:eisy.local:8080/desc (referred to in the pinned post at the top of the forum) just gives a page of xml

@stillwater Since the IoX finder window seems to indicate the device is updated to 6.0.4 it's possible you need to perform another reboot/power cycle to the device to bring things up again.

Are you able to get information if you browse to this page: https://eisy.local:8443/WEB/sysconfig.txt (If you get a security message click advanced and click continue to site - it's local so it's fine to access)

If after a power cycle you're still unable to get eisy UI to come up at https://eisy.local/ then I would suggest opening a support ticket before you go any further. Certainly don't get into SSH and run any random commands. During this time of development it helps UD more if users file support tickets before random attempts of repair that might make things worse. It helps them learn what happened to a system, but is also easier for them to correct what has happened to this point.

Open a support ticket here: https://www.universal-devices.com/my-tickets

4 minutes ago, Techman said:

It will show up in the finder as an ISY

Where will it show as "ISY"? On mine the "Name" is my personalized name given to the top item in the node tree and "Type" shows as "eisy".

1 minute ago, stillwater said:

This doesn't work.

What's the result when you got to https://eisy.local/?

@Geddy

ISY was the default assuming you didn't rename it.

Thanks!

@Geddy you have explained why the Finder designation of my EISY changed from IoX to ISY -- it's because the "restored" IoX top node is named ISY. Except I changed the name and it's still ISY in finder...

I tried accessing the sysconfig.txt file and the eisy either refused to connect or did not provide any data,.

Then I power cycled EISY. Still no luck with eisy.local. The finder finds it but now with no type or version listed. EISY still at version 6.04.

Upgraded Packages again. After a very short time it said packages upgraded successfully. I did not "Install Dev. Packages" at this point or previously.

I power cycled the eisy again. I also rebooted the PC, mostly because I hadn't done that in a while. EISY still at 6.04. Otherwise no change.

If it matters, the EISY is not connected to a PLM.

FYI I did not execute any "random commands" via SSH.

Also after each reboot the settings in configuration change -- Insteon support is turned off. Matter is turned on, and Zigbee and Zwave are set to auto (I had saved them as OFF). There is also a new box that says Migrate to Zmatter Zwave that I can't get rid of -- I don't want Zwave, Zmatter or any other Zs.

I will set up a ticket. (But I'm tempted to just keep the 994i and wait another year)

If I wasn't clear, the response to https//eisy.lcoal/ is ERR_CONNECTION_REFUSED

It's possible your browser seecurity settings are blocking access.

Arey ou on a PC or MAC, what version

29 minutes ago, stillwater said:

Except I changed the name and it's still ISY in finder...

If you clear your java cache or look in the windows (I assume you're on Windows) temp folder for UD*.state files and clear one that might say finder or list or something (I forget the actual name and not local to my device currently) it might change the name the next time IoX Launcher is run. I think the name of the device is a cached value. If it didn't change on the following launch.

30 minutes ago, stillwater said:

I will set up a ticket. (But I'm tempted to just keep the 994i and wait another year)

Best to use the ticket option. My guess is something didn't update correctly and UD will look through the logs and probably give you a few commands to run. Since you ran the update packages again in admin console that would be the first suggestion to try an update process again.

Odd that the web didn't give you anything on the sysconfig page. That could be a web issue. I would suggest trying a different browser.

Also, you mentioned you use the Unifi edgerouterX. Do you run vlans? Are you running any antivirus, firewall clients, or VPNs on your computer? If so make sure you are on the SAME vlan as the eisy. Turn off antivirus, firewalls, and VPN clients.

I have submitted a ticket. Michel asked me to boot and send him a shot of the end of the boot sequence. There were two warnings about /var/polyglot/.cache/pip or its parent not being writable and serial package not found.

Then there was no /var/udx/.udx_install_cleanup

Then "isy service failed since no process with id 3637 exists"

But for the record, no vlans, vpns, firewall, or antivirus. I tried Chrome on Mac, Chrome on PC, Safari on Mac, and Edge on PC. I do have malware bytes on the PC but I don't think it does anything -- realtime protection is "inactive."

I cleared java cache and started finder and it still lists the eisy NAME as ISY. even though I had renamed the root names (NETWORK and ISY) . I will search for ud*.state file(s)

The PC is windows 11 and the Mac is Tahoe 26.2/. I can't imagine why browser would allow access to the PG3 dashboard (eisy.local:3000 .... ) and not the normal http or https ports.

Edited 1 hour ago1 hr by stillwater

Renaming the launcher and finder temp files to .statx (equivalent to deleting them) did indeed cause finder to show the 2nd root name (what was ISY) in the finder. Also seems to have fixed the problem about the configuration settings being reset on reboot. (this seems odd but I'll take the win)

Just for the record it appears that the eisyui package was not installed on my eisy. This explains why I was able to access the PG3 dashboard but not the eisy-ui.

I now realize that eisy-ui is new and that what I am vaguely remembering from when I first got the eisy (or maybe polisy before it) was that there was a system dashboard that was separate from the polyglot dashboard. I'm not sure what I would have used that for but that's what i thought I would find in addition to the new eisy-ui, which is sort of a preliminary version of a replacement for the java admin console.

I'll go look for more documentation but in the meantime I can use eisy exactly as i used the isy994i.