DavidV

Thanks @Techman. Ticket submitted.

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.

Thanks for the response! Problem resolved but I can't say exactly what resolved it after multiple package upgrades, reboots, and power cycles.

Resolved now after four reboots and as many power cycles. I'm able to login to PG3 now. Looks like a token needed to be refreshed and was a bit stubborn. Everything seems to be back to normal now. And yes, I'm using the default until I have fully replaced my ISY944i and the system is relatively stable. Problem resolved but i can't say exactly what resolved it.

@DennisC - PG3. I have power cycled three times (after each package upgrade was verified to be complete) and #4 worked! From the looks of it a connection token had expired and needed to be refreshed. After that I was able to successfully login. I'm still having issues with one of the node servers (Acurite) but I can at least get to it now to reinstall it. Thanks!

@Geddy - Thank you for the insights. After the last package update (#4) and a reboot, my nodes partially came back but the node server is showing as disconnected and still unable to login. Thanks for the link to create a support ticket.. will do now. - David

I performed an upgrade from IoX 5.5.5 to 5.5.7 today. After the upgrade, everything works except my Node Servers (Acurite, Hue, and Ping). My assumption was that they need to be restarted as has happened on other package upgrades. However, I am unable to login on the PG3 page from either the Finder or the Console. I have tried multiple browsers (Edge and Chrome) in both standard and private modes with no success. I have cleared the browser cache. I have rebooted and cycled the power on the EISY. I have verified my login credentials. I have upgraded packages 3 times. Repro: Select Polyglot V3 from either the Finder or Console Provide login credentials on the Polyglot Login page Expected behavior: Login accepeted and Polyglot V3 home page should be rendered Observed behavior: Polyglot remains on login page with no activity Anyone have any guidance?

I performed an upgrade from IoX 5.5.5 to 5.5.7 today. After the upgrade, everything works except my Node Servers (Acurite, Hue, and Ping). My assumption was that they need to be restarted as has happened on other package upgrades. However, I am unable to login on the PG3 page from either the Finder or the Console. I have tried multiple browsers (Edge and Chrome) in both standard and private modes with no success. I have cleared the browser cache. I have rebooted and cycled the power on the EISY. I have verified my login credentials. Repro: Select Polyglot V3 from either the Finder or Console Provide login credentials on the Polyglot Login page Expected behavior: Login accepeted and Polyglot V3 home page should be rendered Observed behavior: Polyglot remains on login page with no activity Anyone have any guidance?

Update... another package upgrade (3 now) and I'm able to get to the login page but after entering my login credentials, the page just stops and doesn't go any further. So I still cannot open the PG3x page.

I performed an upgrade from IoX 5.5.5 to 5.5.7 today. After the upgrade, everything works except my Node Servers (Acurite, Hue, and Ping). My assumption was that they need to be restarted as has happened on other package upgrades. However, I am unable to launch the PG3 page from either the Finder or the Console. I have tried multiple browsers (Edge and Chrome) in both standard and private modes with no success. I have rebooted and cycled the power on the EISY. Error message is: (IPaddress) refused to connect. Any ideas?

Looks like the 5.5.3 update resolved the issue. ZWave using the ZMatter Z-wave dongle seems to be working well for me now.

@IPapp The only way I was able to get out of that loop was to do a factory reset. Once that was done, re-added Insteon support and that works fine. Just need to stick with Insteon for now.

@oberkcThanks for the guidance. I did try that route as well and, same as @GJ Software Products, it just drops into a loop. The only way I've been able to get out of that loop is a factory reset. So as the product says: ZMatter USB (beta)... but IMO it wasn't quite ready for customer beta testing. UDI may have rolled out a bit early. Good news is that I have my ISY994i and will continue to run that until the eisy|home and ZMatter is working.

In hopes of saving others bit of time, these are the steps I've taken so far: Disabled Z-Wave support and re-enabled the Z-Wave Support (no change) Done a factory reset on the Eisy Home and re-enabled the Z-Wave Support (no change) Done a factory reset on the Eisy Home, moved the dongle to another USB port and re-enabled the Z-Wave Support (no change) Also looks like my support ticket was closed with no explanation.

I'll be interested to see if there is an answer to this as I'm experiencing the same issue of “Z-wave dongle not responding.” However, in my case it worked fine the first time, then after powering down and restarting it gave the error message. I've opened a support ticket but they marked it as 'Low priority' which suggests that I won't get a response anytime soon. Edit: To add to this, I've also disabled the Z-Wave option, done a factory reset on the eisy|home, and re-enabled Z-Wave support with no change.