Applied the update and now my zwave JS will not connect.
have tried a server reboot, poweroff/on… seems to be toast now.
Oddly enough, the zigbee portion is online and active.
1 Like
Is there a way to revert a version?
Mine is also toast after last update. I am going to attempt to restore from a backup.
do you think it is HA or something on the zwave stick itself?
maybe a reset on the zwave stick?
gonna try a restore I had from last night (partial restore), which has the older version of zwaveJS on it)
Partial restore of Z-Wave JS solved it for me. I had to reboot the whole server afterwords, though. Home Assistant definitely needs to pull this update ASAP
1 Like
same here… worked for me, just need to reconfigure the devices, they seem to have all gone back to original names
what a PITA… would think they would do more testing before pushing this out
STAY AWAY FROM THIS UPDATE
Same issue. After the partial restore (Settings > System > Backups), restarting HA from the GUI didn’t bring it back - I had to reboot the server.
1 Like
Same thing. I think the backup restore process should be smart enough to reboot the server.
Looks like it was not tested. Offline are all devices. Had to restore from the latest backup and unfortunately lost all of the history as usual.
could be worst… I was in the middle of adding devices and troubleshooting keymaster, had to factory reset all my devices.
Same problem here… wondering how quick before a fix or if I should go the partial restore route. I’ll be upset I lost the history if they push an update tonight.
Do a partial restore and check all the boxes, then restart the whole server. I didn’t have to reconfigure anything.
1 Like
This update, some how, takes all USB connected devices down with it (HA no longer sees the devices (ZHA, NUT and Zwave)) on a Windows 10 hosted vBox VM.
It’s the craziest thing I’ve ever seen a addon do. This is Crazy…
Nothing, short of VM recovery works.
I’ve performed the same update 3 times, with not only VM restarts, but full server reboots. Results are the same each time.
Thank goodness for VM backups.
Restored from backup, rebooted and it’s working now. Great job on the backup tool, works exactly like it should.
1 Like
HA supervised on dedicated machine, no VM’s and things.
Same problem, after update Zwave went dead and took RfxCom (which also is a USB controller) with it.
Restore of the partial backup made by the update and machine restart solved it. Nothing is lost, just back to normal.
This update needs an first responder 
GitHub issue to be found here:
1 Like
Hi all,
This is on me, apologies for the mess this has created. Thanks to @freshcoast 's issue Z-Wave JS 0.1.59 fails to start · Issue #2494 · home-assistant/addons · GitHub I was able to find the root cause which was a change in the build system. I did test the addon before I submitted the PR, and ran into this same issue, but because I didn’t touch any of the files listed in the failure logs, I assumed I had created the permissions issue when transferring the files from my repo to my HA server, and once I resolved it locally I moved on. That was clearly a very poor assumption.
I have a fix incoming: Fix zwave_js file permissions issues by raman325 · Pull Request #2495 · home-assistant/addons · GitHub I am waiting for one other tester to confirm that the add-on functionality is restored before we merge. Fixed in 0.1.60. I’ve seen reports that if you run into issues with 0.1.60 you may need to do a full reboot of your system before it will start. Can’t explain why…
5 Likes
rolled back to 0.1.58 and all is well.
Is this only affecting supervisor installs of this? I have it running in a separate docker from HA core and wondering if I should suspend auto updates as well. Thanks.