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

Question: account used to #312

Open
jokerigno opened this issue Mar 21, 2022 · 3 comments
Open

Question: account used to #312

jokerigno opened this issue Mar 21, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request v5 Will be worked on in v5

Comments

@jokerigno
Copy link

Hello,

I was wondering if there is a way to store account used to trigger spotcast service. Let me explain my usage:

I have some tts notification based on things that happens at home (dishwasher, washer, etc).

So IF this happens while music is streaming I ( actually a guy I know) found a way to restart streaming using spotcast service. This is great if I started the streaming while it doesn't work if my wife is the one using spotify.

Is there a place where this info is stored?

Thank you in advance

@hmmbob
Copy link
Contributor

hmmbob commented Mar 21, 2022

Maybe you can use the information provided by media_player.spotify_xxxxx for this?

@TheFes
Copy link

TheFes commented Apr 26, 2022

That's indeed how I solved it in my script to resume Spotfy after a TTS or other interruption.

I compare the source of the media_player.spotify_ entity to the friendly names of the speakers.

To make sure this runs without errors, it would be nice to have some information on which accounts are set up in Spotcast though, would it be possible to expose those in a sensor?

@fcusson fcusson added the enhancement New feature or request label Mar 7, 2023
@fcusson
Copy link
Collaborator

fcusson commented Nov 19, 2024

Now available in v5. There will be sensor.<spotify_id>_spotify_profile sensor. Filtering sensors for entities part of the spotcast domain will let you have access to that information.

@fcusson fcusson added the v5 Will be worked on in v5 label Nov 19, 2024
@fcusson fcusson self-assigned this Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request v5 Will be worked on in v5
Projects
None yet
Development

No branches or pull requests

4 participants