ekutner / home-connect-hass

Alternative (and improved) Home Connect integration for Home Assistant
MIT License
491 stars 53 forks source link

Broken in core 2024.2.2 #347

Closed timoverwoest closed 4 months ago

timoverwoest commented 4 months ago

Integration does not load anymore:

Core 2024.2.2 Supervisor 2024.02.0 Operating System 11.5 Frontend 20240207.1

BR Timo

Cook23 commented 4 months ago

Logger: homeassistant.config Source: config.py:1293 First occurred: 09:29:40 (1 occurrences) Last logged: 09:29:40

Invalid config for 'home_connect_alt' at configuration.yaml, line 59: '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 60: '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

Eckart0 commented 4 months ago

Same here. When I remove the YAML lines 'client_id' and 'client_secret' a new configuration is demanded, Link to external config page is broken. { "error": "unauthorized_client", "error_description": "client or redirection URI not authorized", "state": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx..." } Regards, Eckart

rudizl commented 4 months ago

Remove everything:

home_connect_alt:
  client_id: 
  client_secret: 
  language: 
ekutner commented 4 months ago

as @rudizl said, and noted in the release notes you should remove the entire "home_connect_alt" section from configuration.yaml

timoverwoest commented 4 months ago

I removed all the stuff in my configuration.yaml but the integration still does not load.

ekutner commented 4 months ago

Then it's not the same error. Upload the log file please.

On Thu., Feb. 22, 2024, 23:18 Timo Verwoest, @.***> wrote:

I removed all the stuff in my configuration.yaml but the integration still does not load.

— Reply to this email directly, view it on GitHub https://github.com/ekutner/home-connect-hass/issues/347#issuecomment-1960329003, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABK6B52KJ2KREBCVAVC6EI3YU6YYZAVCNFSM6AAAAABDUOIYM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRQGMZDSMBQGM . You are receiving this because you commented.Message ID: @.***>

makavelli20 commented 4 months ago

same here.not loaded since HA update...

ekutner commented 4 months ago

I can't help without the debug logs, which is what the issue reporting instructions clearly say.

Eckart0 commented 4 months ago

Here ist the debug log. 240223 home-assistant_home_connect_alt_2024-02-23T19-39-06.190Z.log

What is peculiar is that the home_connect_alt entities are filled, but a new configuration is still required.

ekutner commented 4 months ago

@Eckart0 you have two config entries, is that on purpose? Anyway, the first one is not working because it didn't properly authenticate with the Home Connect service, you can probably just delete it.

Eckart0 commented 4 months ago

Thank you. Deleted the first config entry. All ok.

Von: ekutner @.> Gesendet: Freitag, 23. Februar 2024 21:16 An: ekutner/home-connect-hass @.> Cc: Eckart0 @.>; Mention @.> Betreff: Re: [ekutner/home-connect-hass] Broken in core 2024.2.2 (Issue #347)

@Eckart0 https://github.com/Eckart0 you have two config entries, is that on purpose? Anyway, the first one is not working because it didn't properly authenticate with the Home Connect service, you can probably just delete it.

— Reply to this email directly, view it on GitHub https://github.com/ekutner/home-connect-hass/issues/347#issuecomment-1961932157 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AHCXC4PXHZDIJZEDJIOYMATYVD2IVAVCNFSM6AAAAABDUOIYM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRRHEZTEMJVG4 . You are receiving this because you were mentioned. https://github.com/notifications/beacon/AHCXC4JBKVBZLGSL37B5LULYVD2IVA5CNFSM6AAAAABDUOIYM6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTU6C2X2.gif Message ID: @. @.> >

timoverwoest commented 4 months ago

After update to 1.1.3 everything ok, thank you.