spotizerrphoenix/spotizerr-phoenix
spotizerrphoenix/spotizerr-phoenix
10
20
Fork 6
Code Issues 15 Pull requests Projects Releases 6 Packages Wiki Activity Actions
6 releases 6 tags
  • v4.0.17 60a946d14c

    v4.0.17
    All checks were successful
    Build and Push Docker Image / build-and-push (release) Successful in 7m59s
    Details
    Stable

    spotizerrphoenix released this 2026-01-26 17:55:17 +00:00 | 0 commits to main since this release

    Overview:

    • Improves on v4.0.16 by adding logic to store and apply device info from sp auth profiles to new sessions created with deezspot-spotizerr-phoenix
    • Captured rich Spotify device metadata end-to-end: the auth utility now prompts for device profiles, logs the overrides, stores them with each account, and uploads them to Spotizerr so downstream services can reuse the exact identity.
      • stored in data/creds/blobs/{sp_profile}/device.json
    • Spotizerr backend persists device_info per Spotify account, validates it during credential creation/editing, backfills defaults when missing, and exposes helpers so every Librespot session (track/album/playlist flows) replays the stored identity via SpoLogin/LibrespotClient.
    • Deezspot integration now accepts the metadata, applies overrides before session creation (including version/system strings), and logs the applied identity.
    • Startup now runs the backfill (unless SPOTIFY_DEVICE_INFO_BACKFILL=false), ensuring every account ends up with consistent defaults; Docker/README docs explain how to disable it and what happens when it’s off.
    • Added a manual backfill script for existing accounts and re-exported the librerpot helpers for easier reuse.
      These changes mean: capture and store device metadata at auth, persist it with each Spotify account, replay it for every download session, and optionally skip the automated backfill via environment flags when needed.

    How To:

    • Update spotizerr-phoenix to latest/v4.0.17 - docker image: spotizerrphoenix/spotizerr:latest
    • Backfill logic will automatically apply device info overrides to your existing Spotify profiles data/creds/blobs/{sp_profile}/device.json (if missing)
    • The stored device info overrides are used for each session created with deezspot-spotizerr-phoenix to mimic that device
    • To customize the device info overrides it is recommended to delete your existing Spotify profiles from the UI and re-authenticate with the new changes from the new spotizerr-auth-phoenix changes:
      • your spotizerr instance > config > Accounts (spotify tab) > Delete your existing profile(s)
      • reauth using docker run --network=host --rm -it spotizerrphoenix/spotizerr-auth
      • you should now see new prompts for device info overrides with preset defaults based on your selected device type enum (with options to customize that)
        • this will then store the device info overrides for that profile in the same dir as that profile in data/creds/blobs/{sp_profile}/device.json and used for subsequent sessions

    Changes:
    Add logic to apply device info overrides to new sessions created with deezspot-spotizerr-phoenix post initial auth by storing defined device info during auth step. add backfill logic for existing auth profiles

    Downloads