After the upgrade Z-WaveJS 0.4.1 no longer works.
I can however operate my Luxaflex curtains.
When looking at the Z-Wave plugin, I see it is not started, when I press start, I get the message: Device /dev/serial/by-id/usb-0658_0200-if00 does not exist in Z-Wave JS core-zwave-js.
Rebooting did not got it going.
R-Pi 3
Z-Wave.me 2 ZME E|A|U|I|X UZB1 version 5.2
Core 2023.11.3
Supervisor 2023.11.6
OS 11.2
Frontend 20231030.2
Quick and dirty hack - unplug, and reconnect the USB Z-Wave co-ordinator.
The serial device might get re-detected by ZHA.
No idea what “Luxaflex curtains” are, nor what their connection method is.
Same here. Tried to reboot, shutdown, unplug, nothing works.
@FloatingBoater thank you for your reply
I took out the USB Z-Wave stick for about 10 seconds and put it back, but nothing happened.
Luxaflex is the same as Hunter-Douglas, they work over Wifi
I have the same issue. And looks like the same hardware. (zwave.me stick + rpi3)
I reverted back to 11.1 and everything is fine again.
“ha os update --version 11.1”
There looks to be an issue detecting the USB controller serial device file which gets mapped from HAOS into the HASS docker container.
In the past, bare-metal installs would likely see something like /dev/ttyUSB0 or /dev/ttyAMA0 but my guess is the update has changed something (there are new Linux features for device naming persistence, but this is via Docker so dunno).
Last dirty hack - remove the USB co-ordinator, reboot, and plug the stick back in. This might increase the chances of it being auto-detected.
My own Yellow has a Aeotec Gen5+, and after auto-detection, appears as /dev/serial/by-id/usb-0658_0200-if00 in ZHA (the longer device is often the one you want):
@FloatingBoater I tried as you suggested, waited until the device was up, plugged the Z-Wave stick, but no result.
Installed the new Z-Wave JS update 0.4.2, but no result
What does your UI->System->Hardware->All Hardware show (should be in the list something like ttyACM0)?
For more advanced debugging, if you can get access to the console on your HA machine (i.e. linux root shell), or you can also use Advanced SSH & Web Terminal AddOn. Plug-in your ZWave stick and enter: dmesg | less . Then type G to goto the bottom. You should see various usb events going on that may indicate what is going on.
@Generated thanks for the tip!!
Since there are no backups made with an OS upgrade, I was wondering how to downgrade.
After the downgrade, it still didn’t work, but after restoring the just upgraded Z-Wave JS back to 0.4.1, everything worked again with the old OS and old Z-Wave JS
I did that, and there is something interesting here:
[155533.767090] usb 1-1.5: new full-speed USB device number 12 using dwc_otg
[155533.867076] usb 1-1.5: device descriptor read/64, error -32
[155533.875290] Bluetooth: hci0: Frame reassembly failed (-84)
[155533.876977] Bluetooth: hci0: Frame reassembly failed (-84)
[155534.087083] usb 1-1.5: device descriptor read/64, error -32
[155534.307086] usb 1-1.5: new full-speed USB device number 13 using dwc_otg
[155534.417057] usb 1-1.5: device descriptor read/64, error -32
[155534.647074] usb 1-1.5: device descriptor read/64, error -32
[155534.767295] usb 1-1-port5: attempt power cycle
[155535.427064] usb 1-1.5: new full-speed USB device number 14 using dwc_otg
[155535.457449] usb 1-1.5: device descriptor read/8, error -32
[155535.473763] Bluetooth: hci0: ISO packet for unknown connection handle 272
[155535.607457] usb 1-1.5: device descriptor read/8, error -32
[155535.827062] usb 1-1.5: new full-speed USB device number 15 using dwc_otg
[155535.857456] usb 1-1.5: device descriptor read/8, error -32
[155536.007453] usb 1-1.5: device descriptor read/8, error -32
Googling around a bit, it does seem like its a kernel related issue. Since it worked in 11.1 and not 11.2, I would recommend creating an issue on this and see what they say.
Here is the same issue for HAOS on Odroid that occurred nearly two years ago, that you can use as an example.
I just had the same issue with Elelabs ZigBee RPi Shield. Reverting the OS worked after nothing else did. I found this issue - possibly related.
Update to 2023.12.0 fixed the problem.
I had the same problem with my zwave usb stick, even with 2023.12.0. Downgrading the OS to 11.1 got it working again. Definitely a bug in OS 11.2.