Core: deCONZ integration seems broken with 0.106

[Kugelfang666]

The problem

When booting HA 0.106 my aqara magnetic door/window sensors are shown as unavailable although in the phoscon GUI they are connected. Removing and reading the integration fixes this until the next reboot. rollback to 0.105.x immediately fixed this. Hence it seem that this problem was introduced with 0.106

Environment

• Home Assistant release with the issue: 0.106
• Last working Home Assistant release (if known): 0.105.X
• Operating environment (Hass.io/Docker/Windows/etc.): HASS.io on NUC
• Integration causing this issue: deCONZ
• Link to integration documentation on our website:

Problem-relevant configuration.yaml

Traceback/Error logs

Additional information

[coolriku]

I can confirm the same issue, after deleting and adding the integration again it works until rebooting.

[VoyteckPL]

Same here.

[stickpin]

Same issue here.
All binary_sensors not working anymore.

Rolled back to 0.105.5 and everything work again.

[probot-home-assistant[bot]]

Hey there @kane610, mind taking a look at this issue as its been labeled with a integration (deconz) you are listed as a codeowner for? Thanks!

[Kane610]

Thanks for reporting though I can't do anything without debug logs showcasing the issue.

[cyberoida]

I have had problems since 0.103.6 with the deconz plugin, it started with 0.104.x when all sensors got unavailable for some secods every hour, then in 0.105.x the problem got a little bit better, but they still were unavailable for some seconds (even a few hours yesterday) every day. I just upgraded to 0.106 and will look out for problems again, currently everything seems to work fine. I will try to debug the problem when I encounter it next time (it does not seem to be reproducable at will).
This is how it looked yesterday:

[stickpin]

@cyberoida seems like a different issue to me, more related to Zigbee availability.

@Kane610 I will try to collect logs now will keep you posted.

[blackskull182]

Hello,

I just enabled the debug mode. These are the logs:

Addon_logs.txt
hassio_logs.txt
deconz_filtered.txt

Thanks

[Kane610]

@cyberoida I think what you are referring to is a different issue from this one. In this issue there are only sensors that are affected.

[Kane610]

I might have identified the underlying issue here. Can you verify if there is a battery sensor reporting properly for the same device? It might be that I've by mistake blocks on a device id which would be the same for the battery sensor as for the normal sensor thus only allowing one of them.to be created

[Kugelfang666]

Yes, typically the aqara magnet sensors exposed both, a binary sensor and a battery level

[blackskull182]

I might have identified the underlying issue here. Can you verify if there is a battery sensor reporting properly for the same device? It might be that I've by mistake blocks on a device id which would be the same for the battery sensor as for the normal sensor thus only allowing one of them.to be created

In my case the battery sensor of broken device are reporting properly.

[KoltesPunti]

Can't confirm this: Rpi4 with hassio and conbee2 no problems at 106.0! (Door Sensors, Temperature Sensors, Motion Detectors, Osram Plugs.... all working fine! Maybe the newest Deconz update fixed it (i installed it before the upgrade)!

[Kugelfang666]

@KoltesPunti does it sustain a reboot? With time the problem is gone if I reads the integration but returns after a boot

[Kane610]

On a reboot the battery is usually not reported for the first hour hence all sensors would be created

[KoltesPunti]

@Kugelfang666 hard-rebootet twice, after second reboot my Osram Plugs were unavaliable! Made a software reload (only hassio) and the 3 Osram Plugs were here again (so i guess he only forgots them due the reboots). Aqara Sensors are avaliable all the time (tested with automations)!

@Kane610 My sensors are immediately there with all informations!

[Kane610]

Some people have a longer loading time of light resources on a full system restart leading to similar experiences as you mention. Try calling the deConz device refresh service

[blackskull182]

Tried to:

• Upgrade to the last Deconz version;
• Calling the deConz device refresh service;
• Home assistant reboot;
• Full system reboot;
• Remove and re-enable Deconz add-on integration.

But no luck :(

[thecode]

I am having the same issue, can send logs if needed.
After upgrading to 106 some of the devices are unavailable. I did not go through all of the types but I think Xiaomi Door/Window sensors are the only ones which are unavailable.
While they are unavailable in HA, they are still available in the Phoscon UI.
Tried to remove and add the integration again, but they still become unavailable.
Rolled back to 105.5 and all devices are OK.

[anybody84]

Same issue here. Some sensors are not available. E.g. 1 of 12 movement sensor, but only the binary_sensor for the movement detection. It still reports battery level and light level corectly. But for window/door sensors all are unavailable and all still report battery level. I could fix it by disabling and enablick back any of the unavailable entities, but after reboot I got the same issue.

[Kane610]

The Hypothesis here is that there can only be one entity with the id which would be either a main sensor or its battery sensor which sounds from what I can see what you guys say as well

[Kane610]

Can you guys add debug for the library as well?

logger:
  default: info
  logs:
    pydeconz: debug
    homeassistant.components.deconz: debug

[yan14]

Here is my log
log.log

[Kane610]

Thanks!

I have verified that its a timing thing between whether or not the battery sensor entities are created before the other entities. Tests are running and will be merged shortly