DeConz

[wifiuk]

I'm using DeConz 6.13 and 2022.4.7, rebooted the physical host and it appears so far to not have the same error message. So looking good. Thanks for the hard work getting this resolved!

Originally posted by @wifiuk in https://github.com/home-assistant/core/issues/68165#issuecomment-1117573300

This issue has returned with the latest version of home assistant.

[wifiuk]

[wifiuk]

have to remove it and re-add it again to get everything to work again

[marvindv]

I had the same problem after restarting my VM host. When I readded the integration I noticed that the internal IP address changed from 172.30.33.0 (as seen in the same error message in my logs) to 172.30.33.2 (as seen as the discovered deconz gateway in the Add Integration dialog).

Interestingly, after I rolled back to a backup I created before readding the integration, everything worked fine again, with the old IP 172.30.33.0.

[mdegat01]

Are you trying to put that IP address in your config somewhere? If so, don't do that. The internal docker IP address isn't static. You can't bank on that being unchanging, you have to use the hostname for the container (core-deconz)

[wifiuk]

Something isn't right with deconz this was fixed before but has recently come back.

Any reboot causes this issue and have to delete and re add to get working.

No manual stuff is being done

[B3nihana]

Same issue here (Baremetal Rpi, no docker). Seems like the DHCP lease for the gateway isn't being released (i.e the previous IP address is still showing as reserved). Agree that this is relatively new, the latest Deconz release (2.18.2) doesn't show any relevant changes.

[JGNi]

Mine refuses. I can see it in the add-on. But inside deCONZ it will not connect to it. So frustrating.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.