temporary grouped sendspin players cant be joined again after announcement to only one of them

[LaneaLucy]

Before you begin

• I have searched the open and closed issues and this hasn't been reported yet.
• I have read the troubleshooting guide and it did not solve my problem.
• I am running a supported installation (Home Assistant add-on or Docker container).

What happened?

when i join two sendspin players (my amplifier and the web player for example) and i play a announcement on only one (the web player for example), they get unjoined (normal), the announcement is played on the player (normal too), but then they dont join again automatically (strange), and when i try to join them manually again, i cant (the group button is gone) until i skip forward, skip to next song, start song from begin again, or pause.
that its not be able to be grouped/joined again also explains why it isnt done automatically.

How to reproduce

join/group two sendspin players
play something on them and make sure, the same track plays continuously, without changing anything
play a announcement on one of them (for example home assistant action: music_assistant.play_announcement)
after announcement finished, try to join them again
joining isnt working until something about the track is changed (other track, play from beginning again, pause, ...)

Music Assistant version

2.10.1

How do you run Music Assistant?

Home Assistant add-on

Diagnostics report or log file

music-assistant-diagnostics-2026-09-05-163833.json

Anything else?

No response

[musicassistant-bot]

Hi, and thanks for taking the time to report this! 🙏

Version: 2.10.1 · Install: HA add-on · Python: 3.14.7 · Platform: Linux-6.18.37-haos-x86_64-with-glibc2.41 · Players: 7

Here's what I found in the attached diagnostics:

🟠 Outdated version

This report is from 2.10.1, but the latest stable release is 2.10.2. A number of issues are fixed in newer releases — please update and check whether the problem persists.

🤖 AI assessment — possible root cause (for maintainers; may be wrong)

After grouping two Sendspin players and playing an announcement on only one, the temporary ungroup performed for the announcement is not reversed: the players are not automatically rejoined afterward, and the group/join button becomes unavailable until the user manually changes track state (skip, restart, pause).

Likely cause: The Sendspin provider's announcement flow temporarily removes a player from its group to play the announcement (expected), but the code path that restores group membership afterward appears to not fire or not correctly re-evaluate group state until a player state-change event (e.g. play/pause/next) triggers a group-state re-check. The excerpt shows '_on_group_changed' in player.py and group-command handling, but no visible code confirming a post-announcement rejoin call, consistent with a missing or broken restore step in the announcement/group lifecycle rather than a user configuration issue.

Evidence considered:

• Issue repro: grouping two Sendspin players, announcement on one player un-groups them but no auto-rejoin afterward and manual join button disappears until track state changes
• music_assistant/providers/sendspin/player.py L730 '_on_group_changed(self, new_group: SendspinGroup)' — group-change handling exists but excerpt doesn't show it being invoked/completing correctly post-announcement
• music_assistant/providers/sendspin/player.py L124-126 SUPPORTED_GROUP_COMMANDS includes PLAY/PAUSE, consistent with reporter's observation that pause/play triggers a state re-check that unblocks joining
• music_assistant/providers/sendspin/README.md L193-195 documents 'Synchronized playback' as a supported feature, implying group restoration after interruption (e.g., announcements) is an expected, intended behavior
• No excerpt shown of the announcement handler that removes/restores group membership — insufficient evidence to pinpoint the exact faulty function

Maintainer next step: In music_assistant/providers/sendspin/player.py and the announcement/play_announcement flow, trace what happens after 'play_announcement' completes for a grouped player: verify whether a rejoin/group-restore call is issued, and whether '_on_group_changed' (L730) or the group-state cache is stale until the next MediaCommand (PLAY/PAUSE/NEXT) forces a refresh; reproduce with two Sendspin players in HA add-on 2.10.1 and inspect logs for group-state transitions around the announcement lifecycle.

category: bug · confidence: 45%

📖 Provider documentation

• Sendspin

---

🤖 I'm an AI-powered triage assistant. I can make mistakes, and a human maintainer will still review this issue. This automation helps the small Music Assistant team keep up with the high volume of reports on this open-source project — thanks for your patience and for helping us help you!

[MarvinSchenkel]

This will be fixed in 2.10.3