/
/
/
# What does this implement/fix? Volume and mute handling had grown a layer of compensating logic on top of the control resolution: the final state read the control that owns the volume, then quietly fell back to the player's own level when that control had no answer, and rewrote a reported zero it did not trust. A volume command redirected to a protocol player took a different route than a mute, and applied the volume limits twice. This makes both sides follow one rule: resolve which control owns the volume, and read or write only that control. Stacked on #5694. **Related issue (if applicable):** - related issue <link to issue> ## Types of changes - [ ] Bugfix (non-breaking change which fixes an issue) — `bugfix` - [ ] New feature (non-breaking change which adds functionality) — `new-feature` - [ ] Enhancement to an existing feature — `enhancement` - [ ] New music/player/metadata/plugin provider — `new-provider` - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) — `breaking-change` - [ ] Refactor (no behaviour change) — `refactor` - [ ] Documentation only — `documentation` - [x] Maintenance / chore — `maintenance` - [ ] CI / workflow change — `ci` - [ ] Dependencies bump — `dependencies` Changes: - the volume and mute a player reports now come from the control that owns them; when that control has no value, the state is unknown instead of borrowed from elsewhere - a cast endpoint with no app running reports its volume as unknown rather than zero, so it no longer needs correcting afterwards - a volume redirected to a protocol player is delivered the same way a mute is, so the volume limits are applied by one player only - Home Assistant mute controls read the attribute a media player actually publishes, so their mute state is known from the start - unmuting a Sonos no longer re-sends its volume level to work around an attenuated AirPlay stream that no longer happens ## 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.