I think it does!
It looks like I could access that .storage config file to change from the IP to core-deconz there, which I will do if this occurs again.
Reading thru that thread, though, it really does seem like this situation shouldn’t be happening anymore, so maybe it was a one-off (I have restarted the machine various times and never came across this issue, so maybe its mentioned auto-healing just failed for some reason this one time today).
In any case, thank you all 
Well, 3 months later, I upgrade HA OS, the machine restarts, the DeConz addon gets a different IP and once again breaks the integration.
Thus, I decided to dedicate a Raspberry Pi to DeConz+Conbee. It has a DHCP-reserved real IP instead of this Docker internal IP nonsense, so I will have hopefully solved the problem for good.
A nice bonus is that with a separate machine for DeConz, I will be able to play with some high-availability setups via another instance for HA 
@johnflorin
Did you ever solved the issue without running deconz on an dedicated PI?
Currently i am migrating all to my odroid with HA and dont want an deticated PI anymore.
Nope, been happily running DeConz on the separate Pi ever since, with 0 issues. Highly recommended!
Thanks for your update. It would be nice if that dont happen
@Robban Can you bring light in here why the deconz IP of the integration get’s not updated when there will be assigned another IP to the docker container?
Now i have changed the config, as stated above, to the host core-deconz, and it survieved a few reboots. But my feelings, and @johnflorin experience is, that after an update it get’s messed up again.
thx
If you use default_config which enables discovery protocols the address should automatically update if it matches the conbee serial number to what is registered in the config entry. I know people are having issues with the addon from time to time but I don’t know why. Partially because I don’t have a setup using the addon so a bit harder to debug
I think you got me wrong, not the conbee serial connection get’s lost.
The internal 172 docker ip of deconz changes but the HA integration has the old one.
That was the issue in my case, just after an update/reboot.
So my question is: Will the integration IP get’s updates when the docker ip changes?
Ps.: i can understand that without that setup it’s hard to debug.
thx
Right back at ya! 
The Conbee serial number is used as the unique identifier of the integration. In order to automatically update the IP address of the integration the started container needs to be discovered by home assistant and during discovery the Conbee serial number must be matched to the one registered in the integration.
ok, now got ya
If that discovery matches the conbee identifier, will the host in the file config/.storage/core.config_entries be updated with the correct internal 172… IP, which could be new?
In my case:
{
"entry_id": "xxxxx",
"version": 1,
"domain": "deconz",
"title": "xxxx",
"data": {
**"host": "core-deconz", <-- this one**
"port": 40850,
"api_key": "xxxx"
},
"options": {
"master": true
},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "user",
"unique_id": null,
"disabled_by": null
},
thx
Yes that is the expected outcome when everything works
ok, thanks for the confirmation.
Maybe i had setup the conbee before my update and that was the issue.
Because i had installed deconz before bu migrated my deconz installation before the update.
Now it makes sense to me and i hope the issue does’nt come up again.
thx