small patrol
I got a notification that v2026.02.23 was available for the ZBT-2 on my HAOS VM, so I installed it. Now, I'm getting a failed setup, will retry error for both the Home Assistant Connect ZBT-2 and for ZHA.
Since the ID number in the ZHA failure is the same as the one in the HAC failure, I presume that fixing one will fix the other...
stark tiger
If you have terminal access to your HA, if you "ls /dev/serial/by-id" and see what is listed and if the devices has changed you can get the new name to edit the device and that might get it working again... I haven't had this issue with mine, but YMMV
small patrol
Thanks. Hasn't changed, at least from the host perspective:
root@NAS:~# ls -la /dev/serial/by-id/
total 0
drwxr-xr-x 2 root root 60 May 6 19:40 ./
drwxr-xr-x 4 root root 80 May 6 19:40 ../
lrwxrwxrwx 1 root root 13 May 6 19:40 usb-Nabu_Casa_ZBT-2_DCB4D90F9500-if00 -> ../../ttyACM0
Restoring a backup from last night seems to have "fixed" the HAC ZBT-2 error, but ZHA still won't start 🙁
Tried restarting the VM, that didn't help either.
small patrol
Based on my previous issue https://discord.com/channels/330944238910963714/1467251687994429660 where my config on my old ConBeeII went AWOL, I've attempted to update the adapter settings by hitting the gear icon. I took the steps in the attached images until I got to the adapter type screen where my ZBT-2 isn't listed.
The configuration for my HAOS VM, however, shows that the ZBT-2 is being passed through to the VM
hollow jewel
This is weird… Can you just try to unplug and re-plug in the ZBT-2? You may also need to stop and start the VM after doing that.
small patrol
Tried that, no joy after a VM restart. 🙁
Nabu Casa ZBT-2
Failed setup, will retry: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Nabu_Casa_ZBT-2_DCB4D90F9500-if00'
for improved readability
OK, went to the gear icon to change the settings, clicked Change current adapter's settings, then got this:
Note there's a /dev/tty0, but it's not there by-id.
I'll bet I would have success with the /dev/tty0, but it could change on the next restart, so that's not optimal, though it would probably get me up & running for now.
small patrol
I've just realized that the Z-Wave stick does not appear in /dev/serial/by-id, yet it's in the list of devices that HAOS sees and that the VM config offers for me to pass through to the VM. (See the two most recent screen shots above)
small patrol
OK. It seems that, for some reason, my server decided to not pass the USB device through to the VM.
I was shown a better way of doing it, and this seems to work better now.
Without even having to restart HAOS or the VM, I just told ZHA to reload itself and everything is now working.
For those who run in a VM on UNRAID:
Use the USB Manager plugin by SimonF for USB management & passing things to your VMs
hollow jewel
Interesting... I'm not sure why the previous way would have broken when just upgrading the ZBT-2 firmware though.