-
-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Issue: Unexpected Coordinator Behavior When Grouping Players
Description
I have three players in my Sonos setup:
- Kitchen
- Dining Room
- Living Room
I’ve created a group setup called 'Downstairs' with the following configuration:
- Coordinator: Living Room
- Followers: Kitchen, Dining Room
The problem arises when I execute groupPlayers() for 'Downstairs'. If Kitchen and Dining Room are already grouped (with Kitchen as the coordinator), executing the groupPlayers() function does not update the coordinator to Living Room. Instead, Kitchen remains the coordinator from the previous group.
Steps to Reproduce
- Group Kitchen and Dining Room with Kitchen as the coordinator.
- Execute
groupPlayers()for the 'Downstairs' group (with Living Room as the intended coordinator). - Observe the coordinator.
Expected Behavior
When groupPlayers() is executed for 'Downstairs', the Living Room player should always become the coordinator as defined in the group configuration.
Actual Behavior
- The previous group’s coordinator (e.g., Kitchen) remains the coordinator even after executing
groupPlayers()for 'Downstairs'. - This creates issues because:
- The coordinator is not consistent with the group configuration.
- Playing a favorite requires explicitly knowing the current coordinator, which adds complexity.
Impact
This behavior complicates:
- Automating group and playback actions.
- Playing a favorite, since it requires dynamically determining the current coordinator.
Additional Notes
- The issue appears to occur when players are already grouped before executing
groupPlayers(). - I would expect
groupPlayers()to always set the defined coordinator (Living Room) regardless of the prior group configuration.
Any assistance or clarification on this behavior would be appreciated!
Metadata
Metadata
Assignees
Labels
No labels