removed ConBee2 controller showing as unk_model in devices list

[shahms]

The problem

After replacing a ConBee2-based ZigBee controller with a HUSBZB-1 controller, an "unk_model" device appears in the device list as a controller with the IEEE of the since-removed USB stick. Adding new ZigBee devices works fine, but from the confusion over which device is the actual coordinator, it's clear something odd is happening.

What is version of Home Assistant Core has the issue?

core-2021.2.2

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

zha

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Example YAML snippet

# Put your YAML below this line

Anything in the logs that might be useful for us?

# Put your logs below this line

[shahms]

Happy to include relevant logs, but as I'm very new to this I'm not sure what logs will be relevant :-)

[MattWestb]

I was having the same problem then doing one "hot swap" of my EZSP then doing firmware update for 3 weeks ago (Was putting the wrong module back and starting AH).

I was stopping AH and deleting the record of the "old" coordinator in the /HA_config/.storage/core.entity_registry and other files in that directory.
Starting HA and its away.

[Adminiuga]

Until recently, it easy very common for zigpy to expect differ coordinators, so it is not equipped for such scenarios atm.
Need to add a cleanup if coordinator changes. For now the only option is to clean zigbee.db manually

[shahms]

Not sure if there's a less brute-force method, but after removing the zigbee integration, deleting zigbee.db and re-adding things the mystery entry is gone, thanks!

[Adminiuga]

that is one way to solve it :D Some devices could be re-added just by power cycling them, as technically they are still in the network, just with zigbee.db deletion zigpy is unaware of them. But on power cycle, most devices would send an anouncement message which would trigger rediscovery.

[shahms]

Thankfully I'm still in the process of setting things up and only had a single device paired for testing :-)

[MattWestb]

@shahms I was thinking you was having one 150 ++ devices network and did like destroying your setup ;-))
Deleting all in the .storage and the zigbee.db = all its away but also some not ZHA things 2 but its little brutal and workingg well :-))

[tnTano]

i'm in a similar situation, ihave that problem but it's a first installation and integration...
my log prompt a warning:

WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: zha
WARNING (MainThread) [zigpy.device] [0x0000] Failed to discover active endpoints
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/zigpy/device.py", line 119, in _initialize
    status, _, endpoints = await self.zdo.Active_EP_req(
  File "/usr/local/lib/python3.8/site-packages/zigpy/util.py", line 110, in retry
    r = await func()
  File "/usr/local/lib/python3.8/site-packages/zigpy/device.py", line 225, in request
    result = await asyncio.wait_for(req.result, timeout)
  File "/usr/local/lib/python3.8/asyncio/tasks.py", line 501, in wait_for
    raise exceptions.TimeoutError()
asyncio.exceptions.TimeoutError

and i cannot use ZHA...

[github-actions]

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.

[MattWestb]

@tnTano Have you trying the latest HA its have one fix for if the coordinator is broken in the DB that perhaps can helping in your case.

[tnTano]

@tnTano Have you trying the latest HA its have one fix for if the coordinator is broken in the DB that perhaps can helping in your case.

Hi Matt, i change the usb key and works... i take the conbee key and put in the drower :D

[MattWestb]

Great that is working for you !!

The fix is if you doing one "hot swap" (not deleting the integration and changing the coordinator) the system was having problem with 2 coordinators in the db and was using tie first one (not working one).

[github-actions]

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.