Since I updated packages to use the new eisy-ui, I have had a problem for several weeks when I try to use "Alexa" (I mostly loathe Alexa) to turn on a light or other. "She" constantly says that the hub is OFFLINE. I can still turn things on/off locally but when I go to myISY it shows OFFLINE. I have found only a reboot via the U-D app or Admin Console fixes it for a day or two and then it happens again.

Any suggestions why I am having this problem that I've never had before?

On 11/15/2025 at 7:45 PM, Riggins44 said:

Any suggestions why I am having this problem that I've never had before?

@Riggins44 Simple answer might be to open a support ticket with UD to see if they can trace the issue if your portal account isn't staying active.

https://www.universal-devices.com/my-tickets

Since this happened following an update make sure that you've fully rebooted the system. Perhaps even a power cycle (press and hold the power button until it turns red, wait 10 seconds +/-, press the button and allow the system to fully boot before attempting to log in (I would suggest using java admin console).

Is your device (I assume eisy) hard wired to your network or are you using wifi to connect? If wifi, is it possible to get a wired connection to where your device is in relation to your network equipment?

Lastly, make sure your portal subscription is active. (UD Portal -> Select Tool... -> Information -> ISY Portal Access License)

I have had trouble with ISY994 devices and Polisy devices (two) with power line grid reclosers. In an effort to minimise outages the power companies install devices to clear lightning discharge from the overhead power lines by dropping the HV breakers for one second and then reclosing them, the first time. This gets longer each time for worse fault clearing.

This short one second clean outage reboots my router and most equipment OK but my UD boxes have always had a problem with it, either not rebooting or not rebooting properly.

Of course, after years of this happening I have also discovered the Ethernet drivers do not seem to make any longer term attempts at IP recovery with the DHCP servers in my routers. IOW: They try a few times and then just give up forever, leaving your home automation dead without an IP connection to your router. This never heals itself and requires a power off/on with a few seconds of dead time. Mine ISY/PolISYs have always had hardwired Ethernet connections to my routers.

This brings me back to the OP's problem. Do you experience short term power grid disruptions frequently?

48 minutes ago, larryllix said:

This short one second clean outage reboots my router and most equipment OK but my UD boxes have always had a problem with it, either not rebooting or not rebooting properly.

Sounds like you could use a power on delay circuit module, to delay the startup of your controllers for several seconds. Most of these are sold as low voltage devices with relays, but you could install it inline with the low voltage power going into the controller.

11 hours ago, Guy Lavoie said:

Sounds like you could use a power on delay circuit module, to delay the startup of your controllers for several seconds. Most of these are sold as low voltage devices with relays, but you could install it inline with the low voltage power going into the controller.

Before I moved I had a WiFi controllable receptacle running my ISY994 and an Insteon controlled OnOff module controlling my router.
When I was away if Internet or Ethernet signals were found bad it would run a power cycling routine that increased duration with each trial.
Then I could also remote power cycle my ISY994 with the remote controlled receptacle.

I was locked out of my home monitoring too many times while away for weeks.

I never bothered since I moved and moved to a polISY but may have to get back on that track.

I just can't believe, after all these years, UD equipment just gives up, and doesn't attempt to heal it's connections. I have never seen another piece of Ethernet equipment that doesn't heal, even if it takes days.

11 hours ago, larryllix said:

I just can't believe, after all these years, UD equipment just gives up, and doesn't attempt to heal it's connections. I have never seen another piece of Ethernet equipment that doesn't heal, even if it takes days.

Well it might be more a function of the hardware platform or FreeBSD, depending on how far it gets or where it stalls in the reboot after a power glitch. It would be interesting to have a screen and keyboard attached to the controller (though that's not possible with a Polisy, only a eisy) to see what exactly happens.

But an external delayed power on would probably be the best workaround.