8000 evohome: Config flow could not be loaded (invalid handler specified) · Issue #82130 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

evohome: Config flow could not be loaded (invalid handler specified) #82130

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mestiez opened this issue Nov 15, 2022 · 8 comments
Closed

evohome: Config flow could not be loaded (invalid handler specified) #82130

mestiez opened this issue Nov 15, 2022 · 8 comments

Comments

@mestiez
Copy link
mestiez commented Nov 15, 2022

The problem

I followed this article to connect my thermostat. I can control it just fine from the first party app. I am in Europe and this is the European version of the integration.

The device does not show up and the following is logged:

Logger: homeassistant.config_entries
Source: config_entries.py:810
First occurred: 2:34:26 PM (4 occurrences)
Last logged: 2:45:46 PM

Error occurred loading configuration flow for integration evohome: No module named 'homeassistant.components.evohome.config_flow'

When trying to add it from the GUI, this appears:
image

My configuration looks like this:

evohome:
  username: !secret evohome_username
  password: !secret evohome_password

This issue is also mentioned on this forum thread.

What version of Home Assistant Core has the issue?

core-2022.11.2

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

Honeywell Total Connect Comfort (Europe)

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.config_entries
Source: config_entries.py:810
First occurred: 2:34:26 PM (4 occurrences)
Last logged: 2:45:46 PM

Error occurred loading configuration flow for integration evohome: No module named 'homeassistant.components.evohome.config_flow'

Additional information

No response

@home-assistant
Copy link

Hey there @zxdavb, mind taking a look at this issue as it has been labeled with an integration (evohome) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of evohome can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Change the title of the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign evohome Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


evohome documentation
evohome source
(message by IssueLinks)

@zxdavb
Copy link
Contributor
zxdavb commented Nov 15, 2022

I agree that the instructions at https://www.home-assistant.io/integrations/evohome/ are not clear.

Currently, it says:

To set up this integration, add the following to your configuration.yaml file:

What it should say is:

This integration does not support config flow. Therefore, to set up this integration, you must add the following to your configuration.yaml file and restart HA:

The reason for the above lack of clarity is that those notes were written before config flow was a thing.

NOTE: I have tested the evohome integration in 0.2022.11.2 and it behaves as I have described, above.

To be clear, this integration is not added via the Add Integration button in the Settings UI. The fact that the UI allows you to do so (albeit unsuccessfully) is the issue.

@zxdavb
Copy link
Contributor
zxdavb commented Nov 15, 2022

Dear Core Dev,

Note that evohome does not have config flow, and its manifest.json does not have config_flow enabled.

Helpfully, you can reproduce the following without have any evohome kit.

If I restart HA with a 'vanilla' configuration.yaml, and an empty .storage folder, then...

  • Click on the gear (settings) icon, then Devices & Services, then Add Integration, then...
  • Search for Honeywell, and click on it, then...
  • Click on Honeywell Total Connect Comfort (Europe), then...

I can see the integration. It correctly has the icon indicating that it "Needs Manual Configuration", but then if I click on it, it produces an error dialog boxlike so:

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

image

This is unexpected behaviour, or at the very least an unhelpful error message.

In the HA log, we have:

2022-11-15 19:31:03.478 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration evohome: No module named 'homeassistant.components.evohome.config_flow'

@zxdavb zxdavb changed the title Honeywell Total Connect Comfort (Europe) integration does not exist evohome: Config flow could not be loaded (invalid handler specified) Nov 15, 2022
@home-assistant
Copy link

@zxdavb
Copy link
Contributor
zxdavb commented Nov 15, 2022

@bdraco mentioning you, as I am not sure changing the labels is enough - please forgive me if I should have mentioned someone else.

This looks like a bug in core (or lovelace?) - see my previous post.

See also: #82106 (closed)

@bdraco
Copy link
Member
bdraco commented Nov 15, 2022

Fixed via #82038 in 2022.11.3 (unreleased)

@bdraco bdraco closed this as completed Nov 15, 2022
@zxdavb
Copy link
Contributor
zxdavb commented Nov 15, 2022

@bdraco Should I add "config_flow": false, to components/evohome/manifest.json too?

@bdraco
Copy link
Member
bdraco commented Nov 15, 2022

@bdraco Should I add "config_flow": false, to components/evohome/manifest.json too?

Not needed. #82038 will fix the issue

@github-actions github-actions bot locked and limited conversation to collaborators Dec 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2F9E
3 participants
0