Fixed Issue with devices registered on different accounts in an Alexa Household #20
Conversation
This file contains hidden or 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
…te-control@f05854f this allow devices accross multiple accounts to work in an Alexa Household
|
Awesome, thank you! |
|
@TactfulElf I'll release a new version tomorrow with your fix 👍 |
|
I couldn't test it due to only having one connected account. I noticed that a full redeploy was necessary to pull the customerId. Thank you for your contribution @TactfulElf, 5.0.7 is out |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Ported changes to customerId handling from thorsten-gehrig/alexa-remote-control@f05854f this allow devices accross multiple accounts to work in an Alexa Household.
CustomerId from devicelist is the Customer that initially registered the Alexa device, however the customerId in the payload for the command needs to be the Customer issuing the request.
Pull the customerId of the logged in user from the same URL used to check authentication.