feat(beefcake/mass): open TCP 8927 (Sendspin) for MA companion-app players #731
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "sendspin-8927"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Opens TCP 8927 (Music Assistant Sendspin player WebSocket) on beefcake's LAN so the family's tablets running the MA Companion App register their native local player.
Why
The MA Companion App's native player is Sendspin, connecting directly to MA's
:8927. beefcake's lan-lockdown allowlisted only:3483(squeezelite) +:8097(stream), so tablet players never registered — blocking the kids'-tablet half of the Hearth audio rollout. Confirmedmasslistens on 8927 and it was absent from the allowlist. (The MA web player still worked via WebRTC fallback; the native app has none.)Change (2 files)
music-assistant.nix:allowedTCPPorts[8097 3483]→[8097 3483 8927]lan-lockdown.nix:lanMediaTcp"3483,8097"→"3483,8097,8927"(+ comment updates naming Sendspin/companion-app players)Posture
:8927is the same media-data-plane class as:3483/:8097already LAN-open for this exact purpose — this completes that allowlist rather than loosening it. LAN-only (eno1), no new auth exposure. Admin/API:8095stays off the list (Caddy TLS vhost only).Deploy
Config-only firewall change → applies live via a no-reboot switch (#727 boot fixes only matter on next reboot, and #727 is in main). Handed off ready-to-apply by the hearth agent (w2:p1).
🤖 Generated with Claude Code