-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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
New Spotify Integration can't handle multiple account config #31666
Comments
Use the integration screen instead of yaml it should work by just creating new entries there. |
Well, yes. But only for the "active" account, specified in configuration.yaml. I don't get any option to input next account's credentials or to choose which account to activate the integration for. If I "edit client & client_secret to ..account_1" in configuration.yaml + restart + add the integration it works fine. Then I can "edit client & client_secret to ..account_2" in configuration.yaml + restart + add the integration, then I get the second account's integration. And so on. But in a few minutes, the accounts not specified in the loaded configuration.yaml will time out and leave behind dead integrations. Probably I'm just doing it wrong: |
You just create another integration, remove the yaml completely and keep adding new ones from configuration > integration. One for each account. |
Found out why - something with the information being cached.
|
@BoneheadFraggle Sorry to post this again after it has been closed. I have managed to get 3 accounts to be available for integration following your instructions above. However, after sometime, the first two accounts will present themselves as "unavailable" after some time. Only the last account whose client id that remains on configuration.yaml will remain available. Have you come across the same problem or have found a resolution to the above problem? |
You should not add multiple entries to your Adding in multiple to your |
Just follow my steps and it should work.
|
Thanks @BoneheadFraggle and @frenck. As you both pointed out, the correct way is to only add one client id and client secret once, and there no need to amend the configuration.yaml any more. Instead of using incognito mode, I went to https://accounts.spotify.com and logged out after adding each intergration. |
I cannot for the life of me add another account. I am prompted with two options when I got to auth. Configation.yaml or Home assistant cloud. I choose cloud and then choose my wife's login which is through Facebook, which might be an issue? anyways it spins and spins then aborts. I've tried incognito, different browser, nothing will get the other account to link I'm going mad. |
@Mucka911 - I'm seeing the same thing. Tried via My wife's spotify login is via Facebook as well and I'm wondering if that is the culprit as well. Were you ever able to solve this problem? Edit -> Confirmed that it wasn't the login via FB as I created another account with email/password and saw the same behavior...Anyone find any solutions to this? |
The problem
I have five Spotify accounts, all worked fine to integrate at the same time in the old integration.
After upgrading to 105.2, I changed the config and the Spotify Apps to the new syntax, and it works fine - but only for one account at a time.
The config won't allow several accounts specified at the same time. Or, I am doing it wrong and then I'd like to suggest an update of the documentation to make it easier to follow for multiple account config.
Environment
Problem-relevant
configuration.yaml
Old config that worked fine:
New config that works (only one account):
But it won't accept more accounts.
Expected config would be something like this:
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: