Setup error: Config flow could not be loaded: {"message":"Invalid handler specified"}

[eelcohn]

trafficstars

The problem

Setting up the Telegram Bot integration through the GUI (Settings -> Devices & Services -> Add Integration) fails: Config flow could not be loaded: {"message":"Invalid handler specified"}

What version of Home Assistant Core has the issue?

Hone Assistant Core 2022.11.1

What was the last working version of Home Assistant Core?

Unknown

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Telegram Bot

Link to integration documentation on our website

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

Diagnostics information

Not available since I could not set up the Telegram Bot integration

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Details from the logger:

Logger: homeassistant.config_entries
Source: config_entries.py:809
First occurred: November 5, 2022 at 10:27:27 PM (3 occurrences)
Last logged: 10:23:06 AM
Error occurred loading configuration flow for integration telegram_bot: No module named 'homeassistant.components.telegram_bot.config_flow'

### Additional information

Currently I've set up the Telegram Bot integration by using a yaml file, but I want to switch to the GUI installation. I've already tried to remove that part of the yaml config, restart Home Assistant and then add the Telegram Bot integration in the GUI, but it throws the same error.

[home-assistant[bot]]

telegram_bot documentation telegram_bot source

[LordNex]

I'm getting this same error with a lot of the new integrations. Such as Cisco iOS, Aruba, and a few others I've tried adding from the integrations page

[GuyKh]

Getting it for OpenWRT

[eelcohn]

I've changed the title since multiple users reported this issue on multiple integrations.

[LordNex]

Ffmpeg as well. Everyone I've tried so far has failed

[keithellis74]

I'm getting this on the Radio Browser integration on HA Core.

[eelcohn]

I just tried the LG WebOS TV integration, and that one worked fine.

[alabammaham]

I get the same error on many integrations, Telegram, Google tts Running in Docker on rpi4

[philou669]

same thing here

[GuyKh]

Few things to mention:

1. Restart to the HomeAssistant instance doesn't help
2. Trying from different browsers (in case something is dirty in the web browser cache etc), also doesn't help

[eelcohn]

same thing here

Can you give us the name(s) of the integrations that you've tried?

[philou669]

Lidarr here

I try to restart and different browsers nothing works :(

Home Assistant 2022.11.1 Supervisor 2022.10.2 Operating System 9.3 Frontend 20221102.1 - latest

[LordNex]

This is getting bad. Some updates I can do but anything that is an addon like Node Red I'm getting the message that there is "No Supervisor Internet Connection" when I know it has one and existing integrations and Addons are still working. But adding or updating anything fails

So far not including the 3 I've mentioned is NodeRed, go2rtc, SSH & Web Terminal, and Exedel CompreFace. Mushroom from HACS updated correctly after several reboots but other things from HACS won't so it appears to be affecting that too.

[eelcohn]

Interesting detail: I've just tried installing Radio Browser, and that worked just fine for me. This might suggest that the affected integrations differ between users/setups.

[eelcohn]

Upgrading the docker container to version 2022.11.2 did not fix the problem for me

[RoganDawes]

I'm experiencing the same problem. OpenWrt Luci and Apple iTunes plugins fail, but I was able to add a generic camera feed successfully (my first one).

Latest x86_64 HAOS in KVM.

[LordNex]

Upgrading the docker container to version 2022.11.2 did not fix the problem for me

Same. 2022.1.2 did not resolve this issue. Same error when adding or modifying integrations

[LordNex]

Additional troubleshooting

I have a multi-VLAN network setup in an enterprise grade collapsed core environment. Everything is Routable via layer 3 as well as layer 2 direct trunks. If your like me and need multicast over more than one VLAN/subnet, you end up unchecking the Autoconfig in the Network CP and individually. I ended up having to remove all my adapters from the VMWare VM one by one until I got it to accept the proper default adapter to use (denoted with a ⭐️ beside it). After that I was able to slowly readd my adapters but who knows when that'll break. Have a PR in core about it

[GuyKh]

Getting even more technical.

Looking in Chrome DevTools -- it looks like the call to .../api/config/config_entries/flow (with payload: {"handler":"ubus","show_advanced_options":true}) returns HTTP 404 - with content: {"message":"Invalid handler specified"}

Looking at HA debug logs:

2022-11-09 11:58:27.328 DEBUG (MainThread) [homeassistant.components.http.auth] Authenticated [My-IP] for /api/config/config_entries/flow using bearer token
2022-11-09 11:58:27.328 DEBUG (MainThread) [homeassistant.components.http.view] Serving /api/config/config_entries/flow to [My-IP] (auth: True)
2022-11-09 11:58:27.333 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration luci: No module named 'homeassistant.components.luci.config_flow'

and indeed - I don't see config_flow.yml in https://github.com/home-assistant/core/tree/dev/homeassistant/components/luci

[klmi]

exactly the same here

[eelcohn]

exactly the same here

What integration(s) have you tried?

[louisguiot]

Just adding my voice, I am having this issue with the OpenWRT integration.

[klmi]

exactly the same here

What integration(s) have you tried?

sry, didn't mention, mostly qnap and cisco_mobility_express