deCONZ integration demands recongifuration on each reboot

The problem

at some point this spring (february estimate). my deCONZ integration started failing on restart. By failing I mean, I would get a notification that an integration needs to be reconfigured.

I can currently solve the issue manually, but it needs to be done after each reboot:

1. enter deconz -> phoscon and allow app authentification for 60 seconds or whatever timewindow it is
2. go to configuration -> integrations and click “reconfigure”
3. I now get a “integration is already configured” type message. At this point it is still NOT working.
4. Now I press disable the integration.
5. Then I re-enable the integration
6. Then I click the configure button and ok in the pop up
7. NOW it is working (reliably if steps above are followed).

(yes I came up with this in solution in last-resort-frustration mode. I have tried some variants of the above without success).

I have googled around and read some threads, not found anything directly comparable. If anyone knows how to solve, by all means enlighten me, it not it may well be some bug in the integration happening for some reason.

What version of Home Assistant Core has the issue?

core-2022.4.7

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

deCONZ

Link to integration documentation on our website

No response

Diagnostics information

config_entry-deconz-2d69584f745cc13c978ac5e26dad046d.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.deconz
Source: components/deconz/gateway.py:286
Integration: deCONZ (documentation, issues)
First occurred: 11:35:34 AM (1 occurrences)
Last logged: 11:35:34 AM

Error connecting to deCONZ gateway at core-decon

Additional information

No response

[basecore]

It is possible to edit the IP of the Deconz in the file core.config_entries manually. You have to login to your home assistant via ssh (for e.g. with the terminal from the Add-on “SSH & Web Terminal”) and write:

cd /config/.storage vi core.config_entries

There you find somewhere the entry of deconz with the wrong IP (something like this):

    "entry_id": "c195c9a63c3b23b05200538f5f7def71",                                          
    "version": 1,                                                                            
    "domain": "deconz",                                                                      
    "title": "00212E02A4BD",                                                                 
    "data": {                                                                                
      "host": "172.30.33.4",                                                                 
      "port": 40850,                                                                         
      "api_key": "7CY7X44B7B"                                                                

The host IP has to be edited to the IP which is shown in the upper right corner in the Phoscon app.

The commands for the vi-editor are little specific: To save the file in vi, press Esc key, type :w and hit Enter key or save the file and quit vi by pressing Esc key, type :x and hit Enter key.

Then you have to reboot the Home Assitant and I hope it should work again. 😉

For me I could also reboot and everything. Just if I update Home Assistant again I have also to do the loop again.

[allexoll]

I don’t think this should be closed, as the automatic setup still has that issue.