I applied recent z-wave JS UI update to 1.6.0 and now I can no longer access the UI. I attempted ro roll back using restore from backup, and now z-wave JS has an error Retrying setup: Failed to connect: Cannot connect to host xxxxxxxx-zwavejs2mqtt:3000 ssl:default [Connect call failed ('172.30.33.0', 3000)] This error is in the devices and services page.
If I click configuration I get the following error Failed to connect: Cannot connect to host xxxxxxxx-zwavejs2mqtt:3000 ssl:default [Connect call failed ('172.30.33.0', 3000)]
If I try to go to the zwav JS UI then I get a bad gateway error.
All I did was apply an update? Any help in resolving this is much appreciated.
Exactly the same thing caught me out last week, and I lost days restoring backups and reconfiguring my z-wave network. I then discovered that the only way to get z-wave back was a cold start. Unplug the power from the pi, wait a couple of minutes, then power back on. This worked after the last update yesterday as well
The root cause was that the configured port for the zwave stick was changed during an update. Not sure how that happened? Your trick of yanking the power allowed me to get the Z-wave JS UI back. This allowed me to see that the port was changed by an update from the correct USB port to a different one. Once I configured the correct port everything works. Now I know to check this first. Thanks again!
I have had this issue multiple times when doing upgrades. It is a big gamble to get it up and working again.
The routine that seems to work best, but I guess it is more of a random chance, is this:
unplug Z-Wave stick from USB
Restore last full (FULL!!!) backup, and just to make a note here: I normaly nowdays does a full backup every night and every time before upgrad since the so called “make backup before update” never works, or is not even done…
Restart everything, which is normaly done by the restore above - but just to make sure, unplug the power cable and restart it again
Now it is time to plug in the Z-Wave stick again…
At you own risk, try the upgrade again… There is a risk of repeat of the above though…