Update EISY and not cant launcher cant find it

[polo2883]

I updated the EISY, and now the IoX launcher cannot find it.

I tried adding https://eisy.local:8443/desc and it says not found.

I can ssh to the IP and login with the admin account so I know the device is up.  But I am lost where to go from here.

[polo2883]

Wow, ISY support is quick. 

All set

[Techman]

Can you post the steps taken to resolve the issue, it will be helpful to others

[OverDale]

I would also love to hear what you did to fix it. I have my own ticket in, but assuming I wont hear back until Monday

 

[mmb]

Personally, I've always found eisy.local never works.  I've never bothered to understand why.

Using IP always works.

Edited March 15 by mmb

[Guy Lavoie]

On 3/9/2025 at 6:03 PM, Techman said:

Can you post the steps taken to resolve the issue, it will be helpful to others

Not what he did but if he could ssh to it with the IP address, then 

https://<ip address>:8443/desc would certainly work. That's the way mine is set up.

 

[kcrimson]

I am having the same issue - I used the IP address via https://<ip address>:8443/desc and it said "Not Found".

Not sure where to go from here. 

Thanks!

 

[kcrimson]

ISY Portal does not appear to find device either. I can ping the IP address from my computer however. 

 

[Guy Lavoie]

3 minutes ago, kcrimson said:

I am having the same issue - I used the IP address via https://<ip address>:8443/desc and it said "Not Found".

Not sure where to go from here. 

Thanks!

 

This started just randomly? Or after a version upgrade? Can you see your eisy in your router's device list?

Just now, Guy Lavoie said:

This started just randomly? Or after a version upgrade? Can you see your eisy in your router's device list? If it's after e version upgrade, you'll have to open a ticket. 

 

[kcrimson]

After the version update. 

I will open ticket. 

Ticket # 26604

Edited March 16 by kcrimson
Added ticket number

[TriLife]

Same issue here. upon upgrade the router didn't recognize the eISY and assigned it a new IP. But even after reassigning it to the original slot, IoX refuses to connect, even with entering the IP address. SSH connects (no change in password) and shows that OS was upgraded to 14.1-p6.

The odd thing is that I did the same upgrade on my development eISY a couple of weeks ago and it happened without a problem. Came right back up.

Filed a ticket #26607

Cheers.

Edited March 16 by TriLife
added missing information

[TriLife]

On 3/9/2025 at 4:04 PM, polo2883 said:

Wow, ISY support is quick. 

All set

Hi @polo2883,

can you enlighten us on what the issue was? Trying to fix the same issue here. Thanks

[OverDale]

EDIT: To be clarify. My issue was that the IoX Launcher and Home Assistant could not find  my EISY after the latest package update. I had already restarted it, I could ping it on my network, and I could log in via SSH. But I didnt know what else to try. THEN I followed the instructions below which I recieved after getting a response back from my own email to Support.

 

Posting here for others that may find it.

The email back from support gave me the following instructions. I followed them and everything was better. I refreshed my IoX Lancher and my EISY showed up. I reloaded my plugin in Home Assistant, and everything was reconnected.

huzzah!!!

Quote

 

1. On Windows, use Command app
2. On Mac, use Terminal app
3. Type ssh admin@1.2.3.4 (replace with the actual IP address of eisy)
4. When prompted for password, type: admin
5. When logged in, please type the following commands. If at any time you're prompted for password, please type admin. Here's a list of the commands

sudo service udx restart

wait 2 minutes and do not type anything

sudo service isy status

... if it shows "running", you are good to go. If not, please submit a ticket (https://www.universal-devices.com/my-tickets)

 

 

Edited March 16 by OverDale