core: Zigbee devices no longer working in 2023.6.2

The problem

This (Zigbee devices stop working/reporting) started to happen as soon as I upgraded to the latest 2023.6.2 and for whatever reason I also can’t revert the setup to the previous to try downgrading it.

Essentially if I reboot the entire VM cold, the zigbee integration works for… under an hour, then stops and won’t until rebooting the VM again. Z-wave is working on the same stick seemingly without issues for now.

Silicon_Labs_HubZ_Smart_Home_Controller_715003AA-if01-port0, s/n: 715003AA - Silicon Labs - 10C4:8A2A for zha
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 122, in async_setup_entry
    await zha_gateway.async_initialize()
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 220, in async_initialize
    raise exc
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 205, in async_initialize
    self.application_controller = await app_controller_cls.new(
                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 219, in new
    await app.startup(auto_form=auto_form)
  File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 193, in startup
    await self.connect()
  File "/usr/local/lib/python3.11/site-packages/bellows/zigbee/application.py", line 131, in connect
    self._ezsp = await bellows.ezsp.EZSP.initialize(self.config)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/bellows/ezsp/__init__.py", line 150, in initialize
    await ezsp._startup_reset()
  File "/usr/local/lib/python3.11/site-packages/bellows/ezsp/__init__.py", line 141, in _startup_reset
    await self.reset()
  File "/usr/local/lib/python3.11/site-packages/bellows/ezsp/__init__.py", line 170, in reset
    await self._gw.reset()
TimeoutError

I think I also see… is any of this helpful? never contributed a bug report before.

Silicon_Labs_HubZ_Smart_Home_Controller_715003AA-if01-port0, s/n: 715003AA - Silicon Labs - 10C4:8A2A for zha
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 122, in async_setup_entry
    await zha_gateway.async_initialize()
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 220, in async_initialize
    raise exc
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 205, in async_initialize
    self.application_controller = await app_controller_cls.new(
                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 219, in new
    await app.startup(auto_form=auto_form)
  File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 193, in startup
    await self.connect()
  File "/usr/local/lib/python3.11/site-packages/bellows/zigbee/application.py", line 131, in connect
    self._ezsp = await bellows.ezsp.EZSP.initialize(self.config)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/bellows/ezsp/__init__.py", line 150, in initialize
    await ezsp._startup_reset()
  File "/usr/local/lib/python3.11/site-packages/bellows/ezsp/__init__.py", line 141, in _startup_reset
    await self.reset()
  File "/usr/local/lib/python3.11/site-packages/bellows/ezsp/__init__.py", line 170, in reset
    await self._gw.reset()
TimeoutError

I built a new VM and installed 2023.6.1 - after a little finagling zigbee is back to stable.

Stability for me looks like this setup:

image

What version of Home Assistant Core has the issue?

core-2023.6.2

What was the last working version of Home Assistant Core?

core-2023.6.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

No response

Diagnostics information

home-assistant_zha_2023-06-16T09-17-07.745Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 5
  • Comments: 61 (11 by maintainers)

Most upvoted comments

I’m encountering the same problem. Since upgrading earlier today, ZHA will not start and just says Failed to set up. I was also encountering a similar problem with Thread based devices connected through Homekit Controller, where they simply would not connect to HA.

After some diagnosing, I found that it stemmed back to the Silicon Labs Multiprotocol addon, which is allowing both Zigbee and Thread to run on my SkyConnect. The problem seems to be that there is some underlying issue with Zigbee and ZHA since this release, which then has a knock-on effect on Thread when the addon is running. If I restart the addon and don’t restart ZHA, then my Thread network comes back up and works fine. But as soon as I try reloading the ZHA integration (Which always fails), my Thread network goes down and I lose control of all devices, requiring another restart of the Silicon Labs Multiprotocol addon.

I can also confirm that neither restoring the backup created just before the update nor restoring a nightly backup fixes this problem. Something in the update has had a permanent impact on ZHA, SkyConnect, and/or the Silicon Labs Multiprotocol addon to the point where restoring a backup cannot fix it.

I found my issue. I run my HA in Qnap virtual machine. For some reason the usb pass through to the VM was turned off. I turned it on and reboot the VM and now it shows up. I don’t know how it got turned off but it did.

Hi All, I don’t mean to be rude, but is someone from HA team looking at this issue? Is there a way to escalate this issue?

You have to submit the debug log, and detailed description of your setup. Half of people in this thread, are getting “no such file or directory” which means the problem is not with ZHA, but with the underlying OS. whether the device file is no longer there, or link to the serial port is not there, etc.

Thanks for your reply, I tried to describe the issue at my best in my first comment: https://github.com/home-assistant/core/issues/94733#issuecomment-1595729683

Some additional stuffs that I tried after I posted that comment:

  • Downgrade the OS to a even older version (where integration was working)
  • Reset the Conbee. Issue persisted so I restored the backup.

Please let me know if the entire log would help (I should have pasted the most critical part). I am also available for a call if could be useful.

Thanks again!

Hi All, I don’t mean to be rude, but is someone from HA team looking at this issue? Is there a way to escalate this issue?

You have to submit the debug log, and detailed description of your setup. Half of people in this thread, are getting “no such file or directory” which means the problem is not with ZHA, but with the underlying OS. whether the device file is no longer there, or link to the serial port is not there, etc.

I am getting that also. Almost like it got uninstalled and nothing I do can get the usb stick to show up anymore. I even tried to roll back and nothing.

I too have SkyConnect and am experiencing this issue since the upgrade. Restarting the HA host recovered some but not all Zigbee devices. I have not yet been able to revert to a previous version.

Could you maybe also look via SSH if your Skyconnect Dongle is missing in /dev/serial/by-id/?

I am using a Conbee II stick and I am able to connect using Deconz addon (which is disabled when I confgure ZHA).

For anyone reading this, try unplugging your dongle and plug it back in and report back if this works please. That fixed it for me, but I’m already back on 2023.6.1. I’m curious if 2023.6.2 will work for others after you reset the dongle or not.

I tried multiple times and doesn’t work.

same problem here!