Updated HA 2023.9.2 -> 2023.9.3 and now Z-Wave Add-on no longer works

kevin.turcotte · September 28, 2023, 6:45pm

Has this been fixed yet?
After all the updates, I am still stuck with the same error.

hutre · September 28, 2023, 6:49pm

Please state which versions you are using, as there has been a number of updates the last 24 hours.

Have you tried simply removing and re-inserting the z-wave dongle (if you are on 2.0.1)?

kevin.turcotte · September 28, 2023, 6:55pm

I am on add-on Z-Wave JS UI 2.0.1

Home Assistant 2023.9.3
Supervisor 2023.09.2
Operating System 10.5
Frontend 20230911.0 - latest

I tried a few complete system reboot, without any success. Z-Wave stopped working yesterday after 2023.9.3 and the multiple add-on updates.

nechry · September 28, 2023, 8:13pm

try to disabling Soft Reset under Z-Wave JS → Settings (cogwheel) → Z-Wave

freshcoast · September 28, 2023, 8:58pm

Are you sure the USB path is correct? Searching I see /dev/serial/by-id/usb-0658_0200-if00 being used, but not /dev/serial/by-id/usb-0658_0200_if00

kevin.turcotte · September 28, 2023, 11:21pm

Got it working. For some reason after the updates, it would not get my z-wave usb stick passed through the VMware ESXi usb hub. Manually adding the USB device through my ESXi virtual machine config fixed it.

dbs · September 29, 2023, 5:08am

@msa This is why I always wait at least a week or two after any update release before installing. The same type of issues occur for ZigBee and other components (I saw a big one for modbus recently, for example). My take is conservative: make sure every device has a fail-safe physical backup, do a complete SW backup before upgrading, and then only upgrade after each release has been out for 2-3 weeks. Annoying, but so far I’ve avoided many show-stoppers.
Lycka till!

-David

msa · September 29, 2023, 5:20am

Oh yes. And we are also hampered by the time-zones, we are up early in this part of the world
Tack! /Mattias

Oniric75 · September 29, 2023, 7:51am

saved my day. it’s working fine now. thanks for the tips.

the VM detection must be busted because i’m using a VM with home assistant supervisor and it doesn’t seems to be detected by the plugin.

anyway, still a great plugins, and thanks for the tips

J_IO_B · September 30, 2023, 1:06pm

Dude you just saved me at least a few days of trail and error! Thanks!

littlemaui · September 30, 2023, 4:26pm

I was having the same problem after most recent z-wave update. I unplugged the z-wave ubs stick and plugged back in, which fixed my problem. Running HA on a Virtualbox on Windows 11.

NOsen · September 30, 2023, 5:23pm

Fresh install

           riable.
2023-09-30T17:22:09.742Z DRIVER   Recovering unresponsive controller failed. Restarting the driver...
Error in driver ZWaveError: Recovering unresponsive controller failed. Restarting the driver... (ZW0100)
    at Driver.destroyWithMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2769:17)
    at fail (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:3484:14)
    at /usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:3533:5 {
  code: 100,
  context: undefined,
Shutting down
  transactionSource: undefined
}
Closing server...

hutre · October 1, 2023, 10:22am

I just managed to crash z-wave by trying to add a device config via settings. The moment I hit save the driver threw an error that it’s not able to find the device, which was fine just a second ago. Is there an issue regarding ownership of the device path or is this related to soft-reset?

dinth · October 1, 2023, 5:11pm

Thank you, this also worked for me.

strongtrond · October 2, 2023, 5:08pm

This is the way. Thank you very much

Kingy444 · October 4, 2023, 5:03am

Out of want of understanding - what is the flow on effect of this / why does it resolve this issue?

More so, should we re-enable this setting later / losing anything having it turned off

Like some of the others here - also running HA as an ESXI VM

freshcoast · October 4, 2023, 5:11am

Explained here:

github.com/zwave-js/node-zwave-js

⛑️ Version 12: Problems communicating with the controller ⛑️

opened 09:39AM - 29 Sep 23 UTC

AlCalzone

Restarting (aka. soft-resetting) a Z-Wave controller is automatically done at st…artup of Z-Wave JS to start from a clean state where the controller isn't doing anything weird. This is also necessary in certain situations, e.g. to apply configuration changes, or to work around firmware bugs. Simply put, for **700 and 800 series** controllers, restarting is **required** from time to time. For **500 series** and older, it is strongly **recommended**. Unfortunately, 500 series controllers may reconnect to USB when restarted, which can cause issues in certain setups. This is especially true VMs, where the USB passthrough stops working unless the VM is configured correctly. Until the update to v12, Z-Wave JS would detect these situations where the controller stayed unavailable after restarting and would disable soft-reset going forward. However this feature caused false negatives that could be nearly impossible to recover from, aside from manually editing a file that can be hard to get to. As a result, it was removed and the burden is now on the user to ensure their environment is set up correctly. #### There are a few known solutions to this: 1. Prefer `/dev/serial/by-id/...` paths over `/dev/tty...` in case the path changes after reconnecting 1. When using the Aeotec Gen5 or Gen5+, [updating the firmware to 1.2](https://aeotec.freshdesk.com/support/solutions/articles/6000252294-z-stick-gen5-v1-02-firmware-update) can help, plus you get SmartStart support for free. 1. If you're using ESXi, [updating to 7.0u1](https://community.home-assistant.io/t/vmware-esxi-7-0-usb-compatibility/185939) can help. 1. For some other VMs, [this document](https://github.com/AlCalzone/ioBroker.zwave2/blob/master/docs/en/vm-usb.md) contains instructions for properly setting up USB passthrough. 1. [Expose the serial port via TCP](https://zwave-js.github.io/node-zwave-js/#/usage/tcp-connection), either from the host or a different device. 1. As a last measure, [soft-reset can be disabled](https://zwave-js.github.io/zwave-js-ui/#/usage/setup?id=z-wave) in the Z-Wave JS UI settings. The stick may need to be re-plugged before it starts working again. It is preferable to try the other solutions first, since being able to restart the stick has the aforementioned upsides.

nechry · October 4, 2023, 6:03am

In my case, I’m unable to re-enable the setting despite trying all the recommended options within my context. Both my dongle and ESXi are already at the recommended versions, and I’ve attempted to use the serial ID method, but I still encounter the same error.

It’s clear that this is merely a temporary workaround to make it function. I’m uncertain whether future versions will bring improvements to the soft reset for VM users.

wbravin · October 4, 2023, 6:09am

Hello all

I had the same problem

I ma running HAOS as a vm on proxmox and i passthrough the zwave usb stick to HA

I did a back up of HA an zwave
i uninstalled and reinstalled zwave JS

i then restored from the zwave backup … it did not work

i re pairred my 10 z-wave devices now all works fine

Than you all for your help

mike31 · October 4, 2023, 10:41am

Wow, so for my first month with HA.

MyQ = Broken
Z-Wave = Broken