Zigbee devices unavailable after reboot VM

[HammerNL89]

The problem

I run HA in a VM on Unraid, with the deCONZ add-on with an Conbee 2, all with latest version/firmware. If I reboot the VM, the zigbee devices become unavailable. I noticed that when I disable auto start of the deCONZ add-on and manualy/automate the start of the add-on with an one minute delay, the problem doesn't occur.

Environment

• Home Assistant Core release with the issue: Home Assistant 0.111.2
• Last working Home Assistant Core release (if known): Not sure, I have this problem for at least 3/4 months now
• Operating environment (Home Assistant/Supervised/Docker/venv): Home Assistant
• Integration causing this issue: Don't know if it's the integration, but it's related to deCONZ
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/deconz/

Problem-relevant configuration.yaml

Traceback/Error logs

Already created an issue on the dresden-elektronik-deconz-rest-plugin github page with more detailed information. On the deCONZ side things look good, VNC view looks okay, and no alarming errors in deCONZ log at the time the devices are unavailable in HA.

In the HA core log sometimes after a reboot when the Zigbee devices are unavailable I get the following error (But this seems random, in other cases I see no errors in HA core logs related to deCONZ, but devices are still unavailable):

Error connecting to deCONZ gateway at 172.30.XX

Additional information

[probot-home-assistant]

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

[Kane610]

Have you tried using the service deconz device refresh one everything has booted up?

[HammerNL89]

Have you tried using the service deconz device refresh one everything has booted up?

No, didn't try that one before. When I call that service, the Zigbee devices become available again, that's nice, but that doesn't change my current situation:

Basically I would change my current automation from: start add-deCONZ with 1 min delay to --> call service deconz.device_refresh

Both would work i guess, but still are some kind of workarounds, I was hoping for a more long term solution/fix if that is possible. I don't know the root cause of the issue.

[Kane610]

The one thing I can see that I can do is if there are events of unknown devices and do a refresh. A part from that there is no way for the integration to know whether to expect devices or not.

[HammerNL89]

Okay, thanks for looking into it.

[thecode]

I'm running a similar configuration, also using Unraid, but I don't think the issue is related to Unraid. I have noticed that if I reboot the VM, light entities show as unavailable, but Xiaomi sensors for example are OK.
If I restart home assistant after the reboot, than the light entities become available.

It looks like the machine boots up very fast and home assistant is ready before the Deconz has fully detected all entities.
I have tried to call the device refresh service few minute after the machine is up, while the entities are available and controllable from the Phoscon UI they still appear unavailable in HA.

I'm also using Node-Red that is directly communicating with the Deconz and in Node-Red it is working OK.
It looks like the HA integration is not updating the availability status from Deconz.

Note that I'm passing a USB controller directly to the VM and not using USB device passthrough.

Hope that this extra information can help, If there is anything I can test to help with this let me know. Thanks for the support.

[stale]

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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[thecode]

This issue is still not resolved for me (0.115.6)

[HK-Moebius]

Same here, running HA on Proxmox. When restarting the machine I´ve to re add the integration to get it running again.
Invalid key for deCONZ at 172.30.33.2

The IP address is always the same. HA and deconz on latest stable version.
Also tried to install deconz on a seperate vm. It works till reboot...

[Kane610]

Brought it up with deCONZ dev and it will be fixed with next release 🎉

[Kane610]

Closing this issue as deCONZ 2.9.0 is on its way out. Use dresden-elektronik/deconz-rest-plugin#2473 for feedback on the fix