3 people b0d7e8aae2 feat(spotify): wire preset storage end-to-end via server-centric priming (#302) ...

storePreset on the speaker was failing with "AddPreset - failed due to
invalid SourceID" because the watchdog priming path only pushed ZeroConf
credentials and never registered a SPOTIFY ConfiguredSource in marge.

PrimeDeviceWithSpotify now:
- resolves the device's paired account via live :8090/info
(margeAccountUUID), falling back to ServiceDeviceInfo.AccountID — same
order as setup.populateDeviceInfo;
- writes a SPOTIFY ConfiguredSource under that account (providerID=15,
BoseSecret as credential), mirroring bridgeSpotifyToMarge;
- POSTs `<updates><sourcesUpdated/></updates>` so the speaker re-fetches
its on-device Sources.xml from marge.

Also introduce zeroconf.ErrAddUserNoOp for the narrow firmware quirk
(404 + empty body on ?action=addUser when activeUser already matches).
Recognised only on that exact pattern; real 4xx/5xx still surface loudly
with full response details. Same treatment applied to Amazon priming.

Docs:
- new docs/concepts/spotify-overview.md anchors the topic (mental model,
streamingoauth.bose.com DNS gotcha, token lifecycle, clientId notes,
troubleshooting table);
- spotify-oauth.md drops the removed install-primer endpoint and the
on-device boot-primer install sections, adds /mgmt/spotify/prime;
- spotify-priming-strategy.md and MUSIC-SERVICES.md link to the
overview.

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-16 22:47:57 +02:00

..

service_test.go

feat(spotify): improve Spotify registration flow and speaker notification

2026-04-06 22:39:30 +02:00

service.go

feat(spotify): improve Spotify registration flow and speaker notification

2026-04-06 22:39:30 +02:00

zeroconf_test.go

feat: implement HandleBoseAmazonToken and wire amazonService into Server

2026-04-29 20:30:06 +02:00

zeroconf.go

feat(spotify): wire preset storage end-to-end via server-centric priming (#302)

2026-05-16 22:47:57 +02:00