Release 2026.7.0rc1 — upgrade from the UI, and the queue in the player card 🖱️

[b0bbywan]

Fresh release, and a first: 2026.7.0rc2 is the first one you can install without touching a terminal. It also ends a quiet month, heatwaves won that round 💥

🖱️ Upgrade from the UI or from Home Assistant

2026.6.0b2 shipped the upgrade backend, so this one simply shows up as an available update in the odio web UI and in Home Assistant, and applies itself from there. The CLI path still works if you prefer it:

odio-upgrade apply --version="2026.7.0rc2"

The rc in the tag is not decorative, a final version is getting close. What I'm missing is your side of it: what still stands between your install and something you'd call final? Anything that broke, during the UI upgrade or in daily use, belongs in this thread.

🎵 What's new

• Tracklist, end to end: mpd2mpris 0.13.0 exposes the MPRIS TrackList interface (spec 2.2), and odio-api keeps it cached live from the D-Bus signals, served on /players/{player}/tracklist with goto / add / remove when the player allows edits, plus a player.tracklist.updated SSE event. In practice that means MPD today, plus any Bluetooth source whose app exposes the interface. Players that don't expose it keep the cover as before.
• Queue view in the player card: a toggle swaps the cover for the queue, current track highlighted, tap a row to jump, per-track remove. Covers also zoom fullscreen.
• mpDris2 is now mpd2mpris: the fork got a proper name, the unit is mpd2mpris.service.
• Fixes: disabling a user unit is idempotent when the unit is absent, and image builds drop the .wants symlink instead of a global disable.

Full notes in the release, full changelog 2026.6.0b2...2026.7.0rc2.

🙏 Thanks to everyone in the table

odio uses all-contributors, and the table is not reserved for people who open pull requests. Bug reports, ideas, research, docs, tutorials and infra all get an entry, and where it reached me makes no difference: a GitHub issue, an email, a Reddit thread or a post on the Home Assistant community forum all count the same.

Fifteen people are credited besides me today, up from one at the last release: @pbattino, @sm0kingm4n, @kasnder, @matsvitt, @andrum993, @Thomas-O, @voterpublic, @vascoguita and @studioalund on GitHub, Pleasant-Mind-7122, ThisLeedsGuy, Sterkenzz and 2wistd from Reddit, jarny from the Home Assistant forum, and antoinel by mail. Thank you, all of it ends up in the releases one way or another.

Every credit in the table also links to the artefact behind it now, an issue, a discussion, a commit, a docs section or a forum post. If you reported something and you're not in the table, say so and I'll add you.

🧭 Ideas on my mind

Nothing started, nothing decided, three directions I'm considering for what comes after this release:

• 🎧 Qobuz, most likely through qbz, which ships an optional headless daemon (qbzd) next to its desktop player, so there would be something to plug into the stack rather than reimplement
• 🎛️ DAC configuration and overclocking, declared at install time instead of hand-edited boot config
• 🌀 Sendspin, the Open Home Foundation's multi-room protocol: sub-millisecond sync, artwork and metadata carried in the protocol itself. The Go implementation could be embedded in odio-api or mpd-discplayer, next to the existing snapclient path

Tell me which one you'd actually use, and what should be on the list instead.