Closed jcallaghan closed 3 years ago
Hey there @dmulcahey, @adminiuga, mind taking a look at this issue as its been labeled with an integration (zha
) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)
There's no serial port device file. Zha does not create that file, so the problem is not caused by zha. Check what creates that file (udev), afaik there were reports of udev breaking in the update?
But this is not issue caused by zha
Also, try re-plugging the conbee
Thanks, @Adminiuga. No change when removing and adding the stick. I've reverted to 2021.04.6 as I'm quite dependant on ZHA running particularly with this many devices 🙃
Is it home-assistant core? Or docker? Core on Python venv doesn't do any low level device management and just update shouldn't cause the device to disappear
Apologies yes running in Docker.
I had the same issue. /dev/serial is not present in the docker container for me, even though it's present in the host OS and in the portainer config file.
New docker images are not running udev daemon anymore? Check the release notes for the docker images
Maybe this is related? https://github.com/home-assistant/docker/pull/180
Pretty sure it should fix the problem
Pretty sure it should fix the problem
I was thinking that PR might have introduced the problem.
How are we supposed to map USB devices like ConBee now? (I'm using the Supervised version)
Yes, you are right. That's the breaking change from the release notes https://www.home-assistant.io/blog/2021/05/05/release-20215/#breaking-change
Set the environment variable to enable old behavior. Optionally provide feedback in the docker repo, as the maintainers would like to know how that is being used.
Personally, I'm not fond of running privileged docker, so the options are:
ATM i did the later.
The issue is caused by the breaking change home-assistant/docker#180
Setting the environment variable should enable olde behavior. Closing, as this is not a zha issue.
I tried adding
environment:
- USING_UDEV=1
To the end of my stack configuration file. The re-updated the stack. But still no different
bash-5.0# ls /dev/serial
ls: /dev/serial: No such file or directory
bash-5.0#
All ZHA devices are offline, and I can see /dev/ttyUSB0 etc, but I don't see any way to reconfigure the usb stick to use a different path without deleting the integration. Presumably I have to re-add all devices if I do that.
You could carefully edit .storage/core.config_entries file but removing and adding integration is safer way. But may loose some customizations, haven't tried this in a while
You could carefully edit .storage/core.config_entries file but removing and adding integration is safer way. But may loose some customizations, haven't tried this in a while
Thanks, editing .storage/core.config_entries worked. Feels like a bit of a hack! For anyone trying to repeat I did:
ls -laR /dev/serial
to list which physical USB devices the symlinks are mapped to....
devices:
- /dev/ttyUSB0:/dev/ttyUSB0
- /dev/ttyUSB1:/dev/ttyUSB1
/dev/serial/by-id/xxxxxyyyyy
with the device mapped above e.g. /dev/ttyUSB0
Now zigbee devices all work again.
The problem
ZHA fails to start after upgrading to 2021.05.0 and 2021.05.1. If I revert back to 2021.4.6 ZHA loads fine.
What is version of Home Assistant Core has the issue?
2021.5.1
What was the last working version of Home Assistant Core?
2021.4.6
What type of installation are you running?
Home Assistant Core
Integration causing the issue
ZHA
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha
Example YAML snippet
No response
Anything in the logs that might be useful for us?