deCONZ gets rediscovered after reboot

[voydz]

Home Assistant release with the issue:

0.100.3

Last working Home Assistant release (if known):
no know working version

Operating environment (Hass.io/Docker/Windows/etc.):

HASSOS in KVM using unRAID

Integration:

https://www.home-assistant.io/integrations/deconz/

Description of problem:
After restarting HASS the deCONZ integration gets rediscovered even though it is set up already. It seems like a regression of #25863

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

# I have not configured deCONZ in any way. I have even deactivated discovery at the moment.

Traceback (if applicable):

# No trace available.

Additional information:
I tried to deactivate the discovery: component but the entry deCONZ Zigbee Gateway stays at the top of the integrations page.

[probot-home-assistant]

Hey there @Kane610, mind taking a look at this issue as its been labeled with a integration (deconz) you are listed as a codeowner for? Thanks!

[Kane610]

Any difference running release 101?

[voydz]

Hey, @Kane610 just updated to 101, issue still persists in exactly the same way.

Thank you for your work in this guys. If I can help you any further, just let me know.

greetings

EDIT: Nvm, upgrade to 101 fails due to hass crashing upon start. Hass.io did roll back to 100.3, it seems to be an issue with the 101 release according to reddit. So you can ignore what I just said.

[Kane610]

Ok, awaiting a proper upgrade then.

I will add improved debug logs for discovery.

[voydz]

I finally got to upgrade to 101.2.

In the meantime I did not change anything. After updating a brief look into integrations revealed a once more discovered "deCONZ Zigbee Gateway" .

[voydz]

So anything I can do to help with this?

[Kane610]

Hey! Still got issues with this? I noticed I responded to the wrong issue previously, what you can do is enable debug for deconz and look at the logs during startup. You can also enable ssdp logs and see what gets logged regarding deconz and then compare the outcome to your configured deconz integration

[voydz]

@Kane610 thank you for your work on this. 👍🏻