operating-system: Upgrade from 7.1 to 7.2 Breaks ConBee 2/ZHA
Describe the issue you are experiencing
After upgrading to 7.2 from 7.1 it breaks ConBee2/ZHA integration, others having the issue in the forum: https://community.home-assistant.io/t/deconz-official-thread/100504/2960
This is on qcow2 VM (Unraid) but no errors are showing anywhere so I am not entirely sure whether this matters in the end or not.
What operating system image do you use?
ova (for Virtual Machines)
What version of Home Assistant Operating System is installed?
7.2
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
- Working ConBee 2/ZHA
- Update VM to 7.2 via the built in update mechanism
- ZHA no longer works
Anything in the Supervisor logs that might be useful for us?
Nothing seen in basic supervisor logs. Device is verified still present/mounted.
Anything in the Host logs that might be useful for us?
Nothing seen in basic supervisor logs. Device is verified still present/mounted.
System Health information
System Health
| version | core-2021.12.9 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.9.7 |
| os_name | Linux |
| os_version | 5.10.91 |
| arch | x86_64 |
| timezone | America/New_York |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| Github API Calls Remaining | 4238 |
| Installed Version | 1.19.1 |
| Stage | running |
| Available Repositories | 948 |
| Downloaded Repositories | 21 |
AccuWeather
| can_reach_server | ok |
|---|---|
| remaining_requests | 44 |
Home Assistant Cloud
| logged_in | true |
|---|---|
| subscription_expiration | February 21, 2022, 7:00 PM |
| relayer_connected | true |
| remote_enabled | true |
| remote_connected | true |
| alexa_enabled | false |
| google_enabled | true |
| remote_server | us-east-1-0.ui.nabu.casa |
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | failed to load: timeout |
Home Assistant Supervisor
| host_os | Home Assistant OS 7.2 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2021.12.2 |
| docker_version | 20.10.9 |
| disk_total | 31.3 GB |
| disk_used | 9.3 GB |
| healthy | true |
| supported | true |
| board | ova |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Mosquitto broker (6.0.1), Samba share (9.5.1), Node-RED (10.3.4), Check Home Assistant configuration (3.9.0), File editor (5.3.3), Duck DNS (1.14.0), Let’s Encrypt (4.12.0), Terminal & SSH (9.3.0), Home Assistant Google Drive Backup (0.105.2), MariaDB (2.4.0), NGINX Home Assistant SSL proxy (3.1.0), Z-Wave JS (0.1.52), DOODS (2), room-assistant (2.19.0) |
Lovelace
| dashboards | 5 |
|---|---|
| resources | 12 |
| views | 4 |
| mode | storage |
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 16 (7 by maintainers)
After running for some hours, the Zigbee Network started to show dropouts again with 7.1 So after all it is just a coincidence, that the problems started after the update…
I solved my problem.
I have a second USB serial device for ebusd connected to my NUC. Both devices are appearing as
/dev/ttyUSB*and the ebusd container was configured to use/dev/ttyUSB0instead of the/dev/serial/by-id/[name]. Since the order of the/dev/tty*devices is not deterministic it was accidentally accessing the Slaesh serial device which broke access for zigbee2mqtt. So it just looks like a coincidence that the problem occurred during this reboot.Now that I’ve fixed that configuration, the zigbee2mqtt communication is working fine again. I applied all updates, and now it works again.
Bottom line: My issue was not related to the 7.2 update.
@agners since I will be away the next 2 days, I like to keep it running as is now that it is working for my family. I will have time at the weekend to test.
Can you try to downgrade the OS to see if its really related to the OS?
Use the following command in the terminal: