Interesting problem here that has popped up today. Everything worked yesterday.

Amazon Echo integration failed. So I went to IoX to see what was up. It couldn't find the EISY (I was planning a reboot). When I entered "https://eisy.local:8443/desc", it sees the uuid for the device (matches what shows in the my.isy.io portal). I can't login (it doesn't respond when I click File->Login) and the three tabs are all empty.

I did a power off/power on.

No joy. IoX still can't find it. my.isy.io sees the device and firmware level (6.0.5), but any attempt to connect or do anything yields "ISY is not online" (note, it's an EISY).

UD Mobile says:
System: EISY
ERROR: Requested ISY not online. 503
System not online or not communicating with Universal Devices Portal. Verify your System is connected to the network. Try reboot.

But, I can connect to it directly using my browser, by going to the IP address and logging in. I get the eisy-ui. I can turn nodes on and off using eisy-ui. So it appears the device is working

eisy-ui tells that I'm running:

PG3x Version 3.3.22
Status: Connected
Frontend Version: 3.3.22
IoX Version: 6.0.5 Connected
Uptime <about an hour since I power off and back on>

Suggestions???

In the isy finder, try creating an entry with it's ip address, eg:

https://192.168.0.123:8443/desc

See if that works

You can also try deleting Java files and apps, and then downloading a new start.jnlp from UD. Don't use a previously saved one.

Let's back up a little. The my.isy.io portal says it can't connect when I try anything, such as checking Amazon Echo integration (Message: "ISY is not online"). UD Mobile says it can't connect (Message: "System: EISY, ERROR: Requested ISY not online. 503")

Neither of those can be related to how I enter the URL in the ISY finder, or any cached Java files.

There's something deeper going on here between the ISY portal (and UD Mobile) and the device. IoX not finding it seems to be a symptom, not a cause.