Just upgraded and configuration is broken

[plattze]

Had a previously working system. Only change was to upgrade to 1.1.3 in the HACS UI. UI showed 4.x to 5.x something, but now that it's broken I cant see the exact version sorry.

I can't see any documentation which is suggesting the configuration.yaml config has changed?

Logger: homeassistant.config
Source: config.py:1293
First occurred: 5:03:43 PM (1 occurrences)
Last logged: 5:03:43 PM

Invalid config for 'home_connect_alt' at configuration.yaml, line 34: 'client_id' is an invalid option for 'home_connect_alt', check: home_connect_alt->client_id, please check the docs at https://github.com/ekutner/home-connect-hass Invalid config for 'home_connect_alt' at configuration.yaml, line 35: 'client_secret' is an invalid option for 'home_connect_alt', check: home_connect_alt->client_secret, please check the docs at https://github.com/ekutner/home-connect-hass

Configuration.yaml (which hasnt changed):

home_connect_alt:
  client_id: C8XXXXXXXXXXXXX
  client_secret: D8XXXXXXXXXXXXXXX

[moerpel]

Same here. Just check the release notes. There was a breaking change that affects configuration in configuration.yaml.

1. Go to --> Settings --> Devices and Services --> hit the ... in the upper right corner.
2. Select "Application credentials".
3. Check if a credentials pair for the Home Connect Integration exists. In my Home Assistant it was called imported from configuration.yaml
4. If yes, go to your configuration yaml and delete or comment the clientID and secret out, check configuration in Developer Tools and restart Home Assistant.
5. If no, Add one with the clientID and secret from configuration.yaml and comment it out or delete it from configuration.yaml once you have added the new credentials to Home Assistant.

[ekutner]

As @moerpel said, there was a breaking change which was noted in the release notes. You should just remove the home_connect_alt section from configuration.yaml. Everything is not configurable in the UI. In procedure @moerpel mentions should not be necessary, the integration will ask for the credentials if they don't exist.

[LucasHokerberg]

Mine is also broken, even if I have read the release notes and removed the YAML configuration.
I have verified that the application credentials are indeed imported. I have even removed and re-added them.
Still no joy.

Logger: homeassistant.config_entries
Source: config_entries.py:444
First occurred: 22:24:57 (2 occurrences)
Last logged: 22:30:25

Error setting up entry Home Connect Appliances for home_connect_alt
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 444, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/home_connect_alt/__init__.py", line 121, in async_setup_entry
    implementation = await config_entry_oauth2_flow.async_get_config_entry_implementation(hass, config_entry)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 420, in async_get_config_entry_implementation
    raise ValueError("Implementation not available")
ValueError: Implementation not available

[ekutner]

Delete any credentials associated with the home connect alt integration then delete the integration (which actually means you need to delete the config entry) and then add the integration back again.

[LucasHokerberg]

Delete any credentials associated with the home connect alt integration then delete the integration (which actually means you need to delete the config entry) and then add the integration back again.

Yepp, that did the trick. Thanks!

[jatty]

Same here. Just check the release notes. There was a breaking change that affects configuration in configuration.yaml.

Thank you, I had the same problem and solved it this way by reading the release notes.