Closed rdvanbuuren closed 3 years ago
I have the same problem. My deconz is on a raspberry pi with home-assistant and deconz as an add on.
I think I know what is going on here. The app now features an "auto-repair connection" feature which will automatically attempt to repair the connection if it fails. This is targeted at dynamic ip's, for example your router might assign a different ip address to your deconz instance. I assume you have not setup your docker image with --net=host? This by default prevents that the discovery works correct! As already mentioned in the homey community this is not something that can be fixed in either the docker image or the app, by not setting this param you intentionally break the autodiscovery.
To solve this there are two possible options:
Unfortunately I don't see this option in Homey. There are only two possibilities: automatic config and manual config.
You are at the wrong place:
in only see this, there is no top menu
Describe the bug: Homey deCONZ app suddenly alters ip address. After that I can't connect to any of my devices. I'm runnig deCONZ in a docker container and what I see is that, after some time, the ip address gets altered to the internal one of the docker container.
How to reproduce: Steps to reproduce the behaviour:
How it should work: Just keep the manual ip address / domain name that I've entered in the configuration.
Additional context: It looks like this has something to do with the autodiscover function?