core: Home Connect - unauthorized_client

ahhh ty, trying 😃

OMG IT WORX! FINALLY…

So for everybody else that was trying and trying and trying here a summarize:

1. Do everything as it is described here
2. on the creation of the Application never use the callback thing for any installation you have on your homeassistant (with or without nabucase, doesn’t matter) => always create it like this:
3. On this page choose the SingleKey thing
4. Create an account with the same Mailadress you used for creating the app in home-connect
5. DONE

@nicedevil007 and @controlcde : did you delete any home connect old application credentials at Settings / devices /… Top right / Application Credentials? I deleted the integration but my old application credentials were still hanging around…

Well I do - but now I delete in file system under config/.storage/ the file application_credentials. Now it works!

Drop cache from the browser to trigger new login to the site and it will ask to do it old fashioned or via single key

On Tue, 16 Aug 2022, 17:23 nicedevil007, @.***> wrote:

For me it did only work after changing the login method to the ‘new’ suggested SingleKey setup. Now everything works, with the https://my.home-assistant.io/redirect/oauth link.

where did you enable the single key thing?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/75782#issuecomment-1216787661, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACM4A6ATBVCNROY33KVW3MDVZOW5RANCNFSM54W7UJDQ . You are receiving this because you commented.Message ID: @.***>

For me it did only work after changing the login method to the ‘new’ suggested SingleKey setup. Now everything works, with the https://my.home-assistant.io/redirect/oauth link.

Edit: I’m sorry I did not see that you disabled the “my” plugin. I did not know that was an option.

Edit 2: It just works for me on a fresh install with the “my” plugin disabled, sorry.

# configuration.yaml used for testing
config:
frontend:
history:
image:
input_boolean:
input_button:
input_datetime:
input_number:
input_select:
input_text:

# Text to speech
tts:
  - platform: google_translate

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

Original:

I see there’s an issue, but I think it’s mostly the docs that need to be changed. Adding the redirect URI https://my.home-assistant.io/redirect/oauth will allow you to set this up without the need for a nabu casa account.

When you reach that URI you can choose your instance URL.

After that I got a blank screen, but in the original window it had already found my home connect devices. You can close that blank window.

I hope this helps you!

(There is no need for dyndns by the way, as all information is passed through your browser window.)

Link changed. The result is the same. Does not work

@nicedevil007 and @controlcde : did you delete any home connect old application credentials at Settings / devices /… Top right / Application Credentials? I deleted the integration but my old application credentials were still hanging around…

yep I already did this.

Here are the things I tryed so far:

1st - remove the credentials, restart HASS, try to connect again => fail 2nd - remove the credentials, remove the app in homeconnect, recreate a new app in homeconnect, restart HASS => fail 3rd - did 1st and 2nd with the Coffee Maker switched over to the same VLAN as my HASS is connected to => fail 4th - did 1st and 2nd and 3rd with my dyndns => fail (and yes it is configured right, otherwise other applications won’t work right 😛 alexa is working f.e. or my LG wasching machine) 5th - did 1st and 2nd and 3rd with my local IP address of the HASS installation 0> fail

Thats why I’m posting here, seems to be a problem with home connect integration that is not used with nabu casa in my opinion.