Not sure what has happened but after a recent update, my zigbee device has stopped working. Running HA core in a VM. Any ideas?
- Check if the current “/dev/serial/by-id…” is actually gone
- Check if if there is another one because your zigbee device address changed for a random reason
- Do a
lsusb -v
to assess whether your device is still recognized at all
where would I run lsusb -v?
In your VM, quite obviously
~ $ lsusb -v
Bus 001 Device 001: ID 1d6b:0001
Did you do point 1) and 2), or are you clueless in Linux?
Just an example of what lsusb -v | head -n 25
should return:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 3
bMaxPacketSize0 9
idVendor 0x1d6b Linux Foundation
idProduct 0x0003 3.0 root hub
bcdDevice 5.10
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x001f
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
If by “HA core in a VM” you actually mean Linux - Home Assistant (home-assistant.io) , that’s HassOS and I am clueless
Did you try unplug the adapter and plug it back in?
Figued it out in the end, had to shutdown the vm, detach the USB devices. Re-attach and and restart the vm
@koying what a toxic attitude you got. Please stop trying to help people, if you can’t do it in a non-condescending way.
Really? You decided to post after 3 month on a 1 year old thread to insult me?
But rest assured. I’m not helping that much anymore. Too many clueless people around here, recently…
It is a shame if an idiot with 10 posts (none of them helping someone else) and not one heart recieved before trys to tell a member with 3.5k posts and 852 recieved hearts how he should help others (or better: that he should stop helping others).
@koying Thank you for your posts here, I try to solve my issue with your suggestions!
My zigbee devices have been missing at the list given by
lsusb
I solved the problem by the instructions of this post:
sudo umount /boot
sudo mount /dev/mmcblk0p1 /boot
sudo apt install --reinstall raspberrypi-bootloader raspberrypi-kernel
sudo reboot
I had the same issue with proxmox.
All USB had these ids :
- 1d6b:0001
- 1d6b:0002
- 1d6b:0003
- 1d6b:0004
I upgraded proxmox and holding on reboot for too long i think.
I fixed it with this :
- remove USB mapping in proxmox
- shutdown proxmox with all VM
- restart proxmox
- remap USB on home assistant VM
- restart home assistant VM
Personally need to extract and reconnect both bluetooth and zigbee usb donglers after booting HA
~ lsusb
Bus 002 Device 002: ID 10c4:ea60
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 003: ID 0bda:8771
Bus 002 Device 001: ID 1d6b:0001