Conbee Zigbee network not functional after upgrade

[csawicki]

The problem

2023-01-29 10:05:10.254 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xE20F:3:0x0008]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>'), DeliveryError('Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>'), DeliveryError('Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>'), DeliveryError('Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>')]

What version of Home Assistant Core has the issue?

2023.1.7

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

conbee2

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @dmulcahey, @adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `zha` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zha` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

zha documentation zha source _{^{(message by IssueLinks)}}

[relaxmax92]

Exact same issue since the HA update to 2023.1.7 - all Zigbee devices are in status Unavailable. Was working fine with 2023.1.6

[MiteZZ]

Exact same issue since the HA update to 2023.1.7 - all Zigbee devices are in status Unavailable. Was working fine with 2023.1.6

As well as here. No zigbee devices available and a error:

at the end of the log:

"sqlite3.DatabaseError: database disk image is malformed"

[puddly]

There have been zero ZHA changes between 2023.1.6 and 2023.1.7 (you can read the diff, it's only 147 lines long): https://github.com/home-assistant/core/compare/2023.1.6...2023.1.7

If your database is malformed, this will prevent ZHA from functioning properly. What hardware are you running Home Assistant on?

[relaxmax92]

If your database is malformed, this will prevent ZHA from functioning properly. What hardware are you running Home Assistant on?

I'm running on an RPI 4 with Home Assistant OS. Funny thing is restoring 2023.1.6 from the backup fixed the issue for Zigbee devices.

[parkervcp]

I have this issue as well I am running Hass OS on a NUC5i3RYH. When I roll back to 2023.1.1 zigbee works again.

It states that is unable to locate my conbee device at the /dev/serial/by-id/conbeed-device-name but the device was there and I could see it.

[llamafilm]

I've been seeing these warnings several times a day, for the past few weeks. I always keep my system up to date, and I'd guess this started sometime in December. ZHA still works, but I get occasional glitches where one bulb in a group doesn't respond. I'm running HAOS on a Raspberry Pi with Conbee II.

1139:2023-02-02 09:13:30.438 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xF86A:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>'), DeliveryError('Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>'), DeliveryError('Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>'), DeliveryError('Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>')]

This is usually followed by a few lines like this: 9631:2023-02-02 09:38:07.105 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x1c' 9653:2023-02-02 09:38:10.176 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x1f' 9686:2023-02-02 09:38:13.244 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x22' 9737:2023-02-02 09:38:16.477 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x25'

[Snail546]

yes, I rolled back to 1.5. v1.7 caused problems. didn't recognise zigbee devices. lost all the names or my radiator valves and couldn't connect to them

[pabes74]

I'm having the same issue while upgrading from 2023.1.7 to 2023.3.2. The ZHA integration is unable to start after the update.

Logger: homeassistant.config_entries
Source: components/zha/core/gateway.py:185
First occurred: 16:02:28 (4 occurrences)
Last logged: 16:08:04

Error setting up entry ConBee II, s/n: DE2426814 - dresden elektronik ingenieurtechnik GmbH for zha
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 383, 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 200, in async_initialize
    raise exc
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 185, in async_initialize
    self.application_controller = await app_controller_cls.new(
  File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 165, in new
    await app._load_db()
  File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 80, in _load_db
    await self._dblistener.load()
  File "/usr/local/lib/python3.10/site-packages/zigpy/appdb.py", line 581, in load
    await self._load_unsupported_attributes()
  File "/usr/local/lib/python3.10/site-packages/zigpy/appdb.py", line 634, in _load_unsupported_attributes
    ep = dev.endpoints[endpoint_id]
KeyError: 2

Logger: homeassistant.components.zha.core.gateway
Source: components/zha/core/gateway.py:185
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 16:02:22 (15 occurrences)
Last logged: 16:28:55

Couldn't start deCONZ = dresden elektronik deCONZ protocol: ConBee I/II, RaspBee I/II coordinator (attempt 1 of 3)
Couldn't start deCONZ = dresden elektronik deCONZ protocol: ConBee I/II, RaspBee I/II coordinator (attempt 2 of 3)
Couldn't start deCONZ = dresden elektronik deCONZ protocol: ConBee I/II, RaspBee I/II coordinator (attempt 3 of 3)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 185, in async_initialize
    self.application_controller = await app_controller_cls.new(
  File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 165, in new
    await app._load_db()
  File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 80, in _load_db
    await self._dblistener.load()
  File "/usr/local/lib/python3.10/site-packages/zigpy/appdb.py", line 581, in load
    await self._load_unsupported_attributes()
  File "/usr/local/lib/python3.10/site-packages/zigpy/appdb.py", line 634, in _load_unsupported_attributes
    ep = dev.endpoints[endpoint_id]
KeyError: 2

Updating the configuration or migrating the radio doesn't work. Migrating the radio results in an "Unknown error occured". Are there any known work arounds? (Besides rolling back to 2023.1.7).

[awsgeoff]

So I have 2023.3.1 as a fresh install and I am seeing this with my Conbee 2. Just the

'Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>'

Over and over again. Happy to debug as I've set my system aside since it's non-functional for me.

[puddly]

@pabes74 Can you ZIP up and post here (or email me) your /config/zigbee.db file?

[pabes74]

Hi @puddly this is my zigbee.db file. zigbee.zip

[melgrech8]

Any updates on this? Having the same issue.

[pabes74]

@melgrech8 I've recently upgraded to version 2023.4.6 and OS version 10.1. This seems to solve all issues I had before with the ZHA integration.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.