core: deConz - Light entities unavailable after reboot

The problem

Environment

Home Assistant Core release with the issue: 0.110.3
Last working Home Assistant Core release (if known): unknown - just moved to virtual machine
Operating environment: Home Assistant Supervised within a Virtual Machine under ProxMox
Integration causing this issue: deConz
Link to integration documentation on our website: https://www.home-assistant.io/integrations/deconz/

Problem-relevant `configuration.yaml`

Traceback/Error logs

Additional information

I searched the logs and was unable to find anything useful. It seems to only affect light entities for me as the Motion Sensors and Temperature Sensors all operate fine, lights just become unavailable. This happens every time HA is restarted. A full shutdown of the Host and cold reboot does not resolve the issue. Only deleting and reinstalling the integration will bring the lights back. Note: I do use the deConz add-on from the Supervisor store. I do not need to reinstall this add-on, only the Integration. Edit: I did not have this issue on the Rapsberry Pi when it was running stand-alone. It seems to have only started since moving to the faster Virtual Machine install.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 23 (6 by maintainers)

Most upvoted comments

In case anybody else stumbles upon this, here is the automation source code for the workaround that has been suggested, it works OK for me:
  alias: Refresh Deconz on Boot
  description: This is needed if deconz is running on the same host and certain devices
    are not visible after reboot because deconz needs some more time initializing
    them
  trigger:
  - event: start
    platform: homeassistant
  condition: []
  action:
  - delay: '60'
  - data: {}
    service: deconz.device_refresh
  mode: single
This fixed it for now. Definitely a bug that’s been introduced when the loading of entities changed in one of the releases.

I’ve got verified from Manup at Dresden Elektronik that this is a deconz bug from long ago that has resurfaced. I’ve asked them to fix this so not all client implementations need to add their own work around

Kane610 on Aug 13, 2020

In case anybody else stumbles upon this, here is the automation source code for the workaround that has been suggested, it works OK for me:

  alias: Refresh Deconz on Boot
  description: This is needed if deconz is running on the same host and certain devices
    are not visible after reboot because deconz needs some more time initializing
    them
  trigger:
  - event: start
    platform: homeassistant
  condition: []
  action:
  - delay: '60'
  - data: {}
    service: deconz.device_refresh
  mode: single

OrbitingOcelot on Aug 5, 2020

This is an unfortunate effect of deconz loading lights slower than the rest of the devices, there is no clear solution to this. Suggested workaround is to run the deconz configuration service in hass when everything has loaded

Kane610 on Jun 1, 2020

Closing this since there is no good solution for this yet. Gonna give feedback to deconz to handle this better in their next generation API.

Kane610 on Jun 1, 2020

I know this had been closed, but it still seems to be an issue, albeit intermittently.
Should this issue be re-opened and more thought be put into it?

austwhite on Aug 5, 2020

I’ve been thinking about some logic that reloads data if it gets an event from a device hass doesn’t know. Like when a light state updates but lights have not been loaded data will be reloaded

Kane610 on Aug 4, 2020