Closed object closed 1 year ago
Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
zwave_js documentation zwave_js source (message by IssueLinks)
I am experiencing the same exact issue after the update last night (On Zooz 800LR stick)
I am experiencing the same exact issue after the update last night (On Zooz 800LR stick)
Do your logs look like mine? Did you also try to re-insert the stick. I saw another issue when the issue was resolved by re-inserting the USB stick followed by the system restart. But it didn't solve my problem.
Embarrassingly, I don't have them, as I restored the snapshot from before the ZWaveJS update. It DID, however take a hardware reset, even after the restore (unplug/re-plug the USB stick), so that definitely indicates a hardware lockup.
Embarrassingly, I don't have them, as I restored the snapshot from before the ZWaveJS update. It DID, however take a hardware reset, even after the restore (unplug/re-plug the USB stick), so that definitely indicates a hardware lockup.
How do you restore snapshots? I have full backup (using Home Assistant Google backup add-on) and it contains Z-Wave JS backup for 0.1.85. But I never ran any restores for a specific add-on.
From Settings->System->Backups: Select the "addon_core_zwave_js_0.1.85" backup entry (will be there as long as you left "Create backup before updating" checked when you updated the add-on). Select both check boxes on the add-on restore pop-up, and click "Restore". I'd say reboot, but power the machine off and re-seat your USB dongle, then power up and boot.
HA should come back to the snapshot point prior-to the upgrade that locked it up.
Thanks a lot! I'll give it a try.
I was having this issue; finally resolved it by restoring 0.1.85, shutting down my HA VM, rebooting my host, unplugging and replugging my Z-Wave stick, and starting the HA VM back up. I'm guessing it was something with the 86 update so I'll hold off on updating again until there is a new update.
phyiscally removing the z-wave stick and rebooting the ha vm worked for me to get it working again.
phyiscally removing the z-wave stick and rebooting the ha vm worked for me to get it working again.
Does that persist through VM reboots?
I was having this issue; finally resolved it by restoring 0.1.85, shutting down my HA VM, rebooting my host, unplugging and replugging my Z-Wave stick, and starting the HA VM back up. I'm guessing it was something with the 86 update so I'll hold off on updating again until there is a new update.
After doing the above I reinstalled the latest JS update and everything seems to be working now.
Mixed Test 1: did a HA restart, Z-Wave is still working Test 2: did a reboot of the host, Z-Wave is not working. Had to phyiscally pull out the stick and plug back in, restart HA to make Z-Wave work again
I have the same problem with Zooz 700 Series (ZST10). Following.
@AlCalzone any ideas here? Here's the PR for the addon bump to 0.86. We could try to update zwave-js in the addon to 11.10.0 and see if that resolves it but I'm not really clear on what's happening
Have a Zooz 700 Series that also locked up after 0.186 update. Rebooted the Proxmox VM twice, then unplugged and replugged the USB Z-Wave stick, "reloaded" the Z-Wave JS service, then "restarted" HA and everything is working again for now. I have not tired to "reboot" machine, but do have a working back-up copy of VM if I need to resort to that.
It seems that the sticks are still in 16-bit node ID mode when that happens. The driver automatically soft-resets if that is enabled, which fixes the issue. But AFAIK, HA has disabled soft-reset altogether.
Workarounds:
Looks like it's time to migrate to ZWave JS UI. BTW unplugging the stick didn't help me.
I have this problem too. HA 2023.8.2. ZwaveJS 0.1.86. Aeotec Z-Stick 7, ZWA010-C, 700 series.
Logs look similar to above (Controller identification returned invalid node ID 0)
Downgrading to 0.1.85, rebooting host, unplugging / repluging stick worked to fix it
Needless to say that downgrading to 0.1.85 solved the issue.
downgrade, unplug & reboot resolved issue for me.
Will be fixed by node-zwave-js
version 11.10.1
(releasing now).
@AlCalzone , thank you! I just applied the update and tested with a full reboot of the host to make sure everything came up clean. All is well again.
@AlCalzone I confirm that the version 0.1.87 resolves the issue. Thank you for the quick response. I am closing the ticket.
The problem
After upgrading Z-Wave JS from version 0.1.85 to 0.1.86 z-wave js add-on no longer starts. It shows "Failed setup, will retry" status in Z-Wave page.
I am using Aeotec Z-Wave Gen 7 USB stick. Device path seems to be corret: /dev/ttyUSB0 ID: /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_30e744e60555ed11b47c99131d62bc44-if00-port0
I tried to follow various suggestions (re-insterting the USB stick, restarting the plugin, rebooting hardware), nothing helped.
UPDATE: Downgrading to 0.1.85 and restarting the add-on made it work again.
I submitted the logs below.
What version of Home Assistant Core has the issue?
2023.8.1
What was the last working version of Home Assistant Core?
2023.8.1
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Z-Wave JS
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zwave_js/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?