-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Grouped speakers get the status "playing"? #62
Comments
If your group a player with another, there is one “coordinator” that controls the playback, and the queue. The other player (the one listening to the coordinator) is actually playing the empty stream from the coordinator. I’m not sure on how to solve this, maybe group playback status is a nice feature, what’s your opinion about that? |
It would be fine, but I'm not sure if this is the most suitable solution. I installed node-sonos-http-api (https://github.com/jishi/node-sonos-http-api), where the grouped speaker shows the status of the coordinator. What do you think of this solution? |
Why not just "disable" the player in the ui if it's grouped? You can see the group events. In the official sonos app you can also not interact with the "child" players. You first have to ungroup them. What is the use case you're trying to solve? Maybe an extra |
Sorry for my late answer. I have a somewhat complicated setting. In the living room I have a PLAY:5 and a One. Unfortunately, you can't assign these two speakers to one room, so I usually (not always) grouped them. If a radio station is played in the kitchen and the two loudspeakers in the living room should be added by a button (via node-red), then this doesn't work so easily/it often fails because I don't know if the two loudspeakers are already grouped or not. |
Closing this stale issue, if someone wants to fix this, please re-open and create a PR. |
Hello, I have observed a behavior that I do not understand. When I group a player (player 1) with a second player (player 2), the status of player 1 is "playing", although both players are not playing anything (they are stopped or paused).
Is this behavior intended?
The text was updated successfully, but these errors were encountered: