One subprocess per speaker
The bridge uses a multi-process runtime: the main app handles Bluetooth, API, and UI, while each speaker runs in its own Sendspin daemon subprocess with dedicated audio routing.
Sendspin Bluetooth Bridge
Turn Bluetooth speakers into Music Assistant players — local, headless, and multiroom-ready
What is it?
Section titled “What is it?”Sendspin Bluetooth Bridge turns Bluetooth speakers and headphones into native Music Assistant players by bridging them to the MA Sendspin protocol.
Each configured Bluetooth device shows up as its own player in Music Assistant. You can keep playback local, group rooms together, manage Bluetooth from the web UI, and run the bridge on Home Assistant, Docker, Raspberry Pi, Proxmox VE, or OpenWrt.
Why the current release line matters
Section titled “Why the current release line matters”Flexible port planning
Top-level WEB_PORT and BASE_LISTEN_PORT overrides make it easier to run multiple bridge instances or parallel HA addon tracks on one host.
Per-device listener overrides
Advanced setups can pin a player to its own listen_port and override the advertised host with listen_host when needed.
HA addon tracks
Stable, RC, and beta addons use separate ingress and player-port defaults so they are easier to distinguish and safer to test side by side.
Guidance + diagnostics
Onboarding checklists, recovery guidance, diagnostics, and SSE status updates keep headless deployments manageable.
Web UI + API
Use the dashboard for scan/import, release or reclaim, Music Assistant reconfigure, bug reports, diagnostics, logs, and config backup/restore — or automate it through the REST API.
Deployment options
Section titled “Deployment options”| Home Assistant Addon | Docker / Raspberry Pi | Proxmox / OpenWrt LXC | |
|---|---|---|---|
| Install | Addon Store | docker compose up -d | Host bootstrap script |
| Web UI | HA Ingress (port assigned dynamically by Supervisor); the addon’s own web_port field is ignored | Direct WEB_PORT listener (default 8080) | Direct WEB_PORT listener (default 8080) |
| Player ports | Channel default BASE_LISTEN_PORT (8928+, 9028+, 9128+) | BASE_LISTEN_PORT (default 8928+) | BASE_LISTEN_PORT (default 8928+) |
| Bluetooth stack | Host bluetoothd via Supervisor/runtime mounts | Host bluetoothd via D-Bus | Host bluetoothd via D-Bus bridge |
| Audio | HA audio bridge | Host PulseAudio / PipeWire | PulseAudio inside the container |
| Best for | HAOS / Supervised users | General Linux hosts and Raspberry Pi | Proxmox VE, routers, appliances |
Multi-bridge deployment
Section titled “Multi-bridge deployment”Run multiple bridge instances against the same Music Assistant server to cover every room — each bridge handles the speakers within its Bluetooth range.
Start here
Section titled “Start here” Install in Home Assistant Stable, RC, and beta addon tracks; ingress and direct-listener behavior explained
Install with Docker Generic Linux host install with WEB_PORT and BASE_LISTEN_PORT overrides
Install on Raspberry Pi Pi-specific Docker guide, pre-flight checks, and one-liner installer
Install in Proxmox / OpenWrt LXC Native LXC deployment using the host Bluetooth stack over D-Bus
Configuration Bridge settings, device fields, adapters, auth, and update behavior
Architecture Process model, IPC, audio routing, Bluetooth lifecycle, and HA ingress behavior
API Reference REST endpoints for status, diagnostics, Bluetooth, Music Assistant, and updates
Release history Current release notes, including recent UI guidance, MA auth, and Bluetooth workflow changes