Regression of previously fixed 'Muted Sendspin player unmutes when group volume changes'

[rdkr]

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?

This appears to be a regression of the fix made for #5098. A sendspin player that is in a group and muted will unmute if the volume of the group is changed.

How to reproduce

Have Sendspin players in a group. Mute one. Change the group volume. Observe the muted player unmuted.

Music Assistant version

2.10.2

How do you run Music Assistant?

Home Assistant add-on

Diagnostics report or log file

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

Anything else?

No response

[musicassistant-bot]

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

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

I went through the attached diagnostics and didn't spot any obvious problems in the automated checks. A maintainer will take a closer look.

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

Reporter states that muting a Sendspin player in a group, then changing group volume, causes the muted player to unmute — this behavior was previously fixed in #​5098 (closed) and now recurs on version 2.10.2.

Likely cause: Regression of the fix landed for #​5098, where group volume-change logic apparently re-propagates/recomputes member volume and mute state without preserving an individually muted member's mute flag. No code excerpt in the supplied evidence shows the group volume-sync path, so the exact regressed function cannot be confirmed from what was retrieved.

Evidence considered:

• Issue references RELATED #​5098 'Muted Sendspin player unmutes when group volume changes' (closed) with 0.8552 similarity, describing the same reproduction steps
• Diagnostics confirm official Home Assistant add-on install, version 2.10.2, ruling out a manual-install packaging issue
• Provided server code excerpts (Dockerfile, Dockerfile.base, sendspin README/manifest, bridge_manager.py) do not include the group volume/mute synchronization logic, so the regression point in code could not be directly verified from retrieved evidence
• Sendspin official docs (player-support/sendspin) do not mention group-mute-volume interaction behavior, so no documentation contradiction exists to reclassify this as expected behavior

Maintainer next step: Locate and diff the player group volume-change handler (the code path that was patched for #​5098) against the current 2.10.2 source to identify what change reintroduced the mute reset, then add/restore a regression test covering 'set group volume while a member is muted' to prevent recurrence.

category: bug · confidence: 45%

📖 Provider documentation

• Sendspin

🔁 Similar past reports

These earlier issues or discussions look related and might already have an answer (or indicate a duplicate):

• #5098: Muted Sendspin player unmutes when group volume changes (closed)

---

🤖 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!