Add token authentication support for the google home api #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since June 2019 the Google Home Local API requires authentication using a "local authorization token" for most requests. This commit changes the affected api requests to send a user-provided authentication token and switch to the now used port 8443 for the api. A special case is the eureka_info endpoint, that can still be accessed over the old port without authentication, but provides more information, when accessed over an encrypted and authorized connection. The method thus supports calling with AND without a token.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since June 2019 the Google Home Local API requires authentication using a "local authorization token" for most requests. This PR changes the affected api requests to send a user-provided authentication token and switch to the now used port 8443 for the api.
A special case is the eureka_info endpoint, that can still be accessed over the old port without authentication, but provides more information, when accessed over an encrypted and authorized connection. The method thus supports calling with AND without a token.
All endpoints still work the same otherwise. There are no means added to get such a token. This remains up the library user.
However there exist multiple options since quite some time to get such token.
Recently a new method was discovered, that can be setup without frequent access to an rooted android device. As a result I was able to revive the old googlehome home-assistant integration as a custom component.
I would like to upstream this component eventually and therefor need to upstream my patches to this library at first.
Please tell me, if this approach is fine to you or if you would like to see any changes to this PR.
If merged this would probably fix(?) #44 .