After update Home Assistant, Error connecting to deCONZ gateway

I’m hassio running in a virtual machine and using deCONZ as intergration. It worked fine for several moths but, after latest update, both hassio and homeasistant. Home assistant can’t connect to the deconz gateway anymore.
I think it is trying to connect to the wrong IP address

The error gives:

Logger: homeassistant.components.deconz
Source: components/deconz/gateway.py:282
Integration: deCONZ (documentation, issues)
First occurred: August 2, 2021, 10:43:30 PM (862 occurrences)
Last logged: 5:47:39 PM

Error connecting to deCONZ gateway at **172.30.33.2**

And in Phoscon the IP Address is:

RdJ-Zigbee 172.30.33.1

In phoscon it al works fine but I can’t controle anything from homeassistant.

Any suggestions how to change (correct) the Ipaddress?

Did you try removing the deconz integratiom amd setting it up again with the correct IP?

Thank you.
No not yet. Almost though. But stopped because I’m afraid losing my deconz configuration.
Can I do it without loosing the configuration?
I prefer to change IP address somewhere in a configuration file if possible.

As far as I remember you won’t lose any config, but no guarantee. You could edit the files in the .storage directory, if you know what you are doing.

Most likely I don’t know what I’m doing. But that hasn’t stopped me trying before.
I think will try to find the config file first. And change the IP address.
If it breaks the config, plan B will do. Hopefully :wink:

Will give feedback

Yup changing the IP address was enough to make it all work again.
In “/config/.storage/core.config_entries” with Studio Code,
Found the part that handles “domain deconz” and changed:
“host”: “172.30.33.2”, to “host”: “172.30.33.1”, and everything back to normal.

5 Likes

Thanks for sharing your process.

I think this really highlights one of issues with HA moving towards a GUI-only integration config approach.

I had this same issue again.
I do not know what trigged the Ip address change There where to updates and restart of the VM where hassio is running on.
Is it possible to point to the docker name?