Skip to content
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

Home Assistant has new authentication methods and Legacy API Passwords will be removed #1098

Closed
Cardy165 opened this issue Jun 7, 2019 · 4 comments · Fixed by #1115
Closed
Assignees
Milestone

Comments

@Cardy165
Copy link

Cardy165 commented Jun 7, 2019

Hi I have just been linking my habridge to Home Assistant but I had to add an API key to home assistant.

It appears from documentation located on this page https://www.home-assistant.io/docs/authentication/providers/ that the current API method of authentication is going to be removed.

From the above page: "LEGACY API PASSWORD: Warning: This is a legacy feature for backwards compatibility and will be dropped in a future release. You should move to one of the other auth providers."

I looked for another issue relating to this but couldn't see one. I am guessing at the point Home Assistant removes the Legacy API support habridge will no longer be useable with Home Assistant.

@bwssytems
Copy link
Owner

Just need to add the bearer token login for the new authentication.

@bwssytems bwssytems self-assigned this Jun 13, 2019
@bwssytems bwssytems added this to the V5.3.0 milestone Jun 13, 2019
@bwssytems
Copy link
Owner

There will be a switch to select legacy login with the password and the default will be the bearer token.

@Twit123
Copy link

Twit123 commented Jun 26, 2019

Hi,

Just a heads up for anyone trying the new long lived token. I first had to go in and tick the legacy password box and save. HA Bridge then connected as it always has. I then pasted in my long lived token and unticked the box to get the new way to work.

Just going straight in and pasting the token in caused errors and it would not connect.

Thanks for the great work.

Simon

@bwssytems
Copy link
Owner

Interesting, I had no issues when I setup HomeAssistant to use the token only. But if it works, it works!

bwssytems added a commit that referenced this issue Jul 29, 2019
Fixes #670 Execute select Device when bridge loads [Enhancement Request] enhancement
Fixes #877 Color in Hue/Sat enhancement
Fixes #917 lock device ID #s enhancement
Fixes #1032 Support for HomeGenie enhancement
Fixes #1033 Backup & Restore enhancement
Fixes #1060 Voice command colour change bug question
Fixes #1077 several somfy action in a same Row ID doesn't work bug question
Fixes #1084 Add Mozilla IoT gateway Helper enhancement
Fixes #1092 ha-bridge incompatible with Amazon Echo Dot Gen. 3? enhancement question
Fixes #1093 Alexa Issue : ID conflict between HA Bridge an Hue Bridge enhancement question
Fixes #1094 issue with 5.2.2 and Harmony enhancement question
Fixes #1095 issue with 5.2.2 and fhem enhancement question
Fixes #1098 Home Assistant has new authentication methods and Legacy API Passwords will be removed enhancement question
Fixes #1103 Have single scroll bar for Bridge Devices page. enhancement
Fixes #1108 Add mDNS Discovery to ha-bridge
Fixes #1109 Add HTTPS to ha-bridge
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants