/
/
/
# What does this implement/fix? Announcements (TTS, doorbell, alerts) behaved differently on muted speakers depending on how they were grouped: - An announcement to a muted group or a muted synced pair was completely silent — every member stays grouped, so nothing was ever turned up and you heard nothing at all. - A muted single speaker did play the announcement, but was left unmuted afterwards. An announcement is meant to be heard, so it now always overrides the mute — and the speaker is muted again once the announcement is done. Follows on from #5465, which fixed a single muted speaker being released from its group but did not restore its mute afterwards. ## Types of changes - [x] Bugfix (non-breaking change which fixes an issue) — `bugfix` ## Checklist - [x] The code change is tested and works locally. - [x] `pre-commit run --all-files` passes. - [x] `pytest` passes, and tests have been added/updated under `tests/` where applicable. - [ ] For changes to shared models, the companion PR in `music-assistant/models` is linked. - [ ] For changes affecting the UI, the companion PR in `music-assistant/frontend` is linked. - [x] I have read and complied with the project's [AI Policy](https://github.com/music-assistant/.github/blob/main/AI_POLICY.md) for any AI-assisted contributions. - [ ] I have [raised a PR against the documentation repository](https://github.com/music-assistant/music-assistant.io/blob/main/CONTRIBUTING.md) targeting the main or beta branch as appropriate. ## Changes - Muted speakers are explicitly unmuted for an announcement instead of relying on a side effect of the volume change, so a muted group is no longer silent. - The mute state is restored afterwards, for every speaker involved. - Speakers that use volume-based (fake) mute announce at their real volume instead of at the muted zero. - Added test coverage for announcements on muted speakers, groups and fake-muted speakers.