This worked! Thank you!
Following up on Ashor Benjaminâs post:
I second this. These steps worked for me:
- Go into âSettings>Apps>Z-Wave JSâ (not âZ-Wave JS UIâ). Disable âStart on bootâ, âShow in sidebarâ, and âWatchdogâ then stop it if itâs running.
- Go into âSettings>Apps>Z-Wave JS UIâ. Enable âStart on bootâ, âWatchdogâ, and âShow in sidebarâ then start it if itâs not running (might want to stop and start it anyway just for fun; I didnât have to).
- While you are in the Z-Wave JS UI page look over to the right of Watchdog switch. Youâll see âHostnameâ and under it something that ends in â-zwavejs2mqttâ. Copy that - Iâll be something like âxxxxxxxx-zwavejs2mqttâ.
- Go into âSettings>Z-Waveâ. Itâll probably be broken and complaining that it canât get to the web service. In the main line select the vertical ellipsis and select âReconfigureâ. When it asks if you want to reconfigure or migrate pick reconfigure. Leave the checkbox UNCHECKED and click the button to submit.
- You SHOULD be asked for the server URL. You want to enter âws://xxxxxxxx-zwavejs2mqtt:3000â (put in what your system actually says in Step 3). Click the submit button.
- MAGICALLY all your devices and entities get reconnected and the world takes on a whole new magic sheenâŚ
At least MINE did. ![]()
I donât know how my Z-Wave JS UI got replaced with the other driver. But now I know what to do if it happens again!
I checked all your steps and my Zwave seems to have been setup accordingly.
However, frequently (sometimes once a day) my Zwave goes offline and all 65 Zwave devices are not working.
When I restart HA then everything works again. I have looked in the logs (though I am not very techie) and donât see anything that might be the issue.
Do you have any idea / suggestion ?
I seem to be in a similar position. I had noticed some slowness, but on a reboot today (VM on my server, rebooted for host OS updates) all my devices are offline. about half (ring devices) are unavailable, and the others are shown as provisioned devices. Tried rebooting and restoring from the backups, but no change.
I saw the conversation about JS UI, but Iâm a little lost. Iâve been on JS since I got HA, about 3 months. Currently on version 1.2.0 with a pending update avail. to 1.3.0. From what I understood, JS UI is the one that is eventually going away and I should stay on Zwave JS?
I really donât want to have to reset 40 devices and fix all my automatons.
I checked logs and the antenna is showing it is receiving packets, but drops them with a âNode ## doesnât existâ so it seems to be software, no the devices or the hardware. is there a way to fix it?
I believe that your issue may be a bit different. All my 65 Zwave devices come back after I restart HA, though some are being re-interviewed.
As far as Zwave JS UI vs Zwave JS, my understanding is like yours, that ZWave JS will remain but ZWave JS UI will disappear.
That is why I am wondering if, after I install HA on the new mini pc, I can use Zwave JS without having to exclude/include all the Zwave devices.
I also did the update and all Z-wave devices are down. I have a Zooz USB stick and the light on is off. Z-Wave JS is saying âDriver: Failed to recover from bootloader. Please flash a new firmware to continue⌠(2W0100)
Error: Driver: Failed to recover from bootloader. Please flash a new firmware to continue⌠(ZW0100)â Iâve never seen this before, but it looks like this thing is bricked?
UPDATE: I had to re-flash the firmware. Went into Z-Wave JS UI, went into Bootloader only mode, found the firmware on Zoozâ website and loaded it back up. Then turned off the Bootloader only mode and everything immediately came back up.
I"m having the same issue. I did change it to "Bootloader only" like you. After that I thought the next step would be to click on "Import" from the very bottom row and select the GBL file that I got from Zooz. That didn't work though so can you tell me what the correct method is for updating the firmware inside Z-Wave JS if it's not that?
EDIT: I solved it. I didn't know there was an option on the bottom right side(Managed Nodes) to update the firmware.