core: Config flow could not be loaded: undefined (Deconz)

The problem

I am continually getting the following error after any system update to the HA system.

image

Then when you click on configure it says

Config flow could not be loaded: undefined

Logs show

image

I’m using DeConz installed as an addon

image

the only way I can fix this is to remove the integration and reinstall it again, which is a pain as it removes all my devices and all of the settings in DeConz 😦

What version of Home Assistant Core has the issue?

core-2022.3.4

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

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 45 (16 by maintainers)

Most upvoted comments

Hi All

I also use a Conbee2 with Deconz and am experiencing issues now with the 2022.3.x upgrades causing the Deconz device to screwup after a host reboot (same screenshot from original bug lodgement). The system seems to be stable after a Deconz addon reboot, a supervisor reboot, and also a core reboot. But when a Host Reboot occurs i have to re authenticate and re add the deconz device and reassign all of the sensors and lights to their respective rooms.

My current build:

  • RaspberryPi 3b
  • core-2022.3.7
  • supervisor-2022.03.5
  • Home Assistant OS 7.5 (HassIO)
  • Deconz Addon v6.12.0
  • Conbee2 Version 2.14.01 / 06/02/2022, Firmware 26660700

No errors in the system logs of HassIO, no obvious errors in the Deconz addon logs, however there is a error log against the actual Deconz device:

Logger: homeassistant.config_entries
Source: components/deconz/gateway.py:276
First occurred: 9:50:21 PM (1 occurrences)
Last logged: 9:50:21 PM
Error setting up entry 00212E05A8CF for deconz

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 335, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/usr/src/homeassistant/homeassistant/components/deconz/__init__.py", line 40, in async_setup_entry
    api = await get_deconz_session(hass, config_entry.data)
  File "/usr/src/homeassistant/homeassistant/components/deconz/gateway.py", line 276, in get_deconz_session
    await deconz_session.refresh_state()
  File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 124, in refresh_state
    data = await self.request("get", "")
  File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 144, in request
    return await self._request(
  File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 163, in _request
    raise ResponseError(
pydeconz.errors.ResponseError: Invalid content type: text/html

I suspect its to do with the Phoscon app having to reauthenticate to Home Assistant with every host reboot. When i manually reauthenticate in the Phoscon app advanced settings and re add the device into Home Assistant everything runs great again with the new deconz registered device (i delete the older faulty deconz device).

This happens reliably after every Host Reboot in core-2022.3.7 or 2022.3.6 or 2022.3.5 (and potentially earlier versions of the March releases). But this issue has never occurred in the past 18 months of using Deconz. Last known version it was stable was core-2022.2.9.

IP Address of the Deconz Gateway remains consistent, and the actual Phoscon App still works fine after a host reboot, but the Home Assistant Deconz device becomes screwed up.

Hopefully that information sheds a bit more light on the possible cause of the issue.

Thankyou for the devs maintaining this addon, its been fantastic over the past few years and this is the first hiccup ive encountered with it.

@Kane610 , I’m happy to help more, just let me know what you need me to supply or test out.

Its probably the IP address that has changed. This is something that happens sometimes with the add-on, since I don’t run HASSOS I have never been able to debug it. I would really like to understand why discovery isn’t updating the address properly.

I am using Home Assistant OS for ~3 years, never had a problem with Deconz discovery

That’s nice to hear! Typically I only see the issues. Not the ones without issues 😉

Well I deleted it and reinstalled deconz . it totally crippled my house. This is only way to get it working again. Not sure if historical logs are kept somewhere…

Next time it happens download the diagnostics data for the integration and enable debugging for integration and restart system.