LAN browser dashboard for every BluOS player on the network

The official app is fine on a phone.

It is a pain when you want one screen for the whole house, and especially if you have many devices — 2 or 10+ — what’s playing, which rooms are on that stream, volume, groups, and whether a player dropped off.

Custom Integration API v1.7. It finds Nodes, Pulse, NAD CI zones, and the rest over mDNS + LSDP, then keeps playback, volume, grouping, and presence live.

What it does

• House remote: artwork, title/album/source, rooms on the stream, seek, skip, shuffle/repeat, mute, stop all. Keyboard: space/K play-pause, arrows or J/L skip, M mute.
• If rooms are on different sources, you pick which stream the remote drives.
• Fleet view of every player, live now-playing. Sort A–Z, or by sync group (it switches to Sync when a group forms).
• Separate volume for Bluesound (Node/Pulse) and NAD CI S2. Those amp scales are not the same. CI S2 also has 42 / 50 / 60 / 70 chips.
• Multi-room: group, add/remove followers, group remaining free rooms under a lead, ungroup one set or all.
• Per player: queue (including reorder), inputs / presets / Bluetooth / settings, diagnostics, 12-hour presence, reboot.
• House page: firmware inventory + upgrade check, reboot all, ungroup all, recent poller drops for this process.

What it is not

It is not a music store. You still pick Qobuz / Tidal / radio / library in the official app (or play via whatever you already use). This is the control surface.

It stays on your LAN. Do not put it on the internet. Default bind is localhost. If you bind it to the LAN, set an API token.

Run it

Python 3.10+, Node 22+, same network as the players.

make install make run 

Then open http://127.0.0.1:8765/

Apache 2.0: https://github.com/tbaur/bluos-dashboard

If you try it, send the boring reports: a player it misses, a group that will not break, a CI zone that shows up wrong, skip that blanks now-playing. Issues on the repo are fine.

Then, send the feature request (or PRs) and let's build on.