Deconz + Conbee, have to setup integration at every restart

It works great, and is relatively easy to integrate again, but having to do it at every restart (unfortunately HASS needs to be restarted very often: a minor automation change, a bug fix, an update, and so on) is a bit of a pain

Can you go into a bit more detail why you need to set it up every restart?

Because the entities disappear after every restart

Ok. Do you have any logs to share?

I am with my smartphone now, looked in the log, the below seems the only lines about deconz

2018-11-08 21:06:12 ERROR (MainThread) [pydeconz.utils] Timeout getting deCONZ data from http://192.168.1.238:80/api/949ADCxxxx.
2018-11-08 21:06:12 ERROR (MainThread) [pydeconz] Couldn’t load data from deCONZ

Ok. Possibly this issue then.

Possibly, but my settings looses the integration ALL the time there is a restart, not just some time as posted by other users.
Maybe because my host is faster? I do run HASSIO on a NUC

Lets wait for 0.82 to see if the retry mechanism solves this issue.

I also have this problem, even after 0.83.1. Every time I restart deconz on my ubuntu host, the integration in HA must be deleted allow 3rd party in Phoscson, and then added again. Pretty annoying.
Is there some way to add the deconz gateway more “permanently” and not through the “automatic” integrations in HA?

The integrations is as permanent as you can get.

Can you share logs?

What version of HassOS are you using?

Then, after deleting the integration, add it again and and restart Hass, this is in the log, pretty right I think?
018-12-02 15:06:19 INFO (MainThread) [homeassistant.loader] Loaded deconz from homeassistant.components.deconz
2018-12-02 15:06:19 INFO (MainThread) [homeassistant.setup] Setting up deconz
2018-12-02 15:06:19 INFO (MainThread) [homeassistant.setup] Setup of domain deconz took 0.0 seconds.
2018-12-02 15:06:19 DEBUG (MainThread) [pydeconz.utils] Sending {} to http://192.168.1.111:80/api/DEE8C5E427

Maybe I solved it now, I had an old deconz.conf file in /.homeassistant-directory since april, could it have been that file that were ghosting it. Did one restart now and the integration worked.

1 Like