Jump to content

Z-wave dongle not responding, Insteon devices not responding, and UDI mobile cannot connect


DavidV

Recommended Posts

Posted (edited)

Anytime I reboot my Eisy, it takes 10-15 more restarts to restore the Zwave communications (Z-wave dongle not responding), Insteon devices to work, and allow UDI Mobile to connect (ERROR: Requested ISY not online. 503. ...)

Even when it does work it often takes 10-20 minutes after reboot for them to start working. 

PG3 connects and works fine.

This happens anytime the system has to reboot including SW updates and power outages. 

It's taking me 1-2 days of reboots and power cycling (reboot, wait 20-30 min then check) to restore the Eisy to working order every time.

The most recent 5.8.0 update is the worst of all. Not only can I not get the system to communicate but for the short time it did work, it lost multiple devices (Z-Wave, Insteon, and one Node for Hue).

That all said, when it does work, it seems stable and reliable. Getting to work is frustrating. FWIW, I've been using ISY since the ISY99.

I'm almost ready to give up on UDI and ISY. Did I just get a bad Eisy? or is this normal?

___________________________________________________________________________________________________

Edit: It is working for now, but it took 12 reboots via power cycling over 6 hours to get it there.

Edit2: ... never mind. It's only partially working. Unable to connect to PG3 (eisy.local refused to connect.) so my Hue lights will not work.

Edit3: After an hour, I'm able to connect to the PG3 dashboard but my Hue node disconnected and won't reconnect. Restart and Start/Stop has no effect. Oddly, the nodes are sometimes visible and other times not. When they're not visible a browser refresh brings them back for a bit then they disappear again.

Edit4: Was able to get the Hue node by removing it and reinstalling. Took a couple of tries but after it stuck I was able to control the Hue bulbs again. Unfortunately, it meant having to recreate all the routines I had created around them. At this point it appears everything is working until the next time I have to reboot or the power goes out. I'm dreading that and may forgo any future SW updates because they are such a mess to deal with.

Edited by DavidV
Posted

@DavidV I went through this exactly same thing a few months ago.  Opened a ticket, and the suggestion was to migrate from zooz to zmatter. (I had zmatter, just wasn't using it due to migration issues the previous time I attempted it.)  I did eventually migrate to zmatter, but one of the releases prior to that (5.7 maybe) seemed to completely solve it for me.  It was very mysterious, in the end not entirely sure what exactly fixed it.  But like I said, it was exactly the same symptoms!

Guest
This topic is now closed to further replies.

×
×
  • Create New...