/
/
# What does this implement/fix? Spotify's Soloist playback engine always announces itself as a Spotify Connect device and offers no way to turn that off, so while Music Assistant is playing Spotify the device shows up in your Spotify app. Touching it there ended badly: a pause was undone in a loop, and playing something else on it or moving playback to your phone left Music Assistant silent for 30 seconds before failing with a generic error — after which the next song grabbed the device straight back off you. It did not help that the device was called "Music Assistant", exactly what the Spotify Connect plugin calls its own device by default, so there were two identically named entries to choose between. **Related issue (if applicable):** - n/a ## Types of changes <!-- Tick exactly one box. CI (.github/workflows/pr-labels.yaml) derives the label from the ticked box and applies it automatically; the release-notes generator uses that same label to slot this change into the next release notes. --> - [ ] Bugfix (non-breaking change which fixes an issue) — `bugfix` - [ ] New feature (non-breaking change which adds functionality) — `new-feature` - [x] 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` - [ ] Maintenance / chore — `maintenance` - [ ] CI / workflow change — `ci` - [ ] Dependencies bump — `dependencies` ## Changes - The playback device is now called "Music Assistant Playback", so it is easy to tell apart from the Spotify Connect plugin's device. - Moving playback to another device from the Spotify app ends the Music Assistant session right away, with a message saying what happened. - Starting a different song on the device from the Spotify app is treated the same way. - A pause from the Spotify app is undone twice, in case it was a mistap, and then respected. - For half a minute afterwards Music Assistant will not start a new session, so it does not take the device back off whatever you just moved to. ## 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.