-
Notifications
You must be signed in to change notification settings - Fork 29
Config flow not working #37
Comments
Have you been able to install it in HACS without changes? I just tried it out and the INSTALL button is greyed out (this is HACS 0.17.3 on HA 102.0b2). |
Nevermind. Thhe initial load of HACS just took very long, then the button appeared. |
So, for me it's working, actually. Can you please try the newest commit? There was an unhandled error that you might have hit. |
This was PEBCAK on my part, I assumed that if I was using the new Config Flow integration then I wouldn't have to still add It now works for me when I follow the instructions 🤦♂, I added the below to my configuration.yaml file and then when I try to add the integration I can follow the link to the Home Connect API site and authorise the integration
Is there a way to remove the requirement for amending the configuration.yaml file and adding this in its entirety through the config flow? |
Good question, not sure. I was following the instructions of the new native HA OAuth2 flow: |
Hi, thanks for all the recent work which you've put into this.
I'm unable to authenticate via the the new config flow integration, I get the following error when I try to add the Home Connect integration.
I'm running home assistant 102.0b2, have your component installed via HACS (the current code in the master branch) and have updated the callback URL in the home connect developer site as per the docs.
I'll enable more verbose logging, as I currently have no more useful information to look into this.
The text was updated successfully, but these errors were encountered: