I own roughly $2,800 worth of current-generation Sonos hardware:
- 9 × Sonos One SL
- 1 × Sonos Sub
- 1 × Sonos Play:3
All on the same LAN as a self-hosted music server (Navidrome, which
speaks the Subsonic API). Every one of these speakers is physically
capable of streaming HTTP audio from that server, and Sonos used to
support exactly this through the custom music service / SMAPI
mechanism plus the Sonos Desktop Controller.
I would like a supported, first-party way to add my local music server
as a music service on these speakers, without:
- exposing my private music server to the public internet,
- paying for a third-party iOS controller app to do the registration,
- or running discontinued Sonos Desktop Controller software.
Here is what I have already tried and why each path is currently blocked:
1. Auto-register via SMAPI from a local bonob bridge on my LAN
(10.0.1.204): the speakers' /xml/device_description.xml is
reachable, but the SOAP registration call to port 1400 is
rejected with HTTP 403 Forbidden by current firmware
(Sonos/95.0-77060). This used to work on older firmware.
2. Use the Sonos mobile app to add a custom service: the iOS and
Android apps do not expose any UI to add a non-Sonos-curated
music service. Only services from your service directory appear
under "Add a Service."
3. Use the Sonos Desktop Controller's Customize panel (Ctrl+Shift+C):
Sonos discontinued the desktop controller in May 2022 and no
longer distributes the installer. Even archived binaries appear
to be rejected by current firmware.
4. Use the new mobile app (post-May-2024) with an HTTPS-served
local service: based on Sonos community forum posts, the new
app additionally requires the service to be callable from
Sonos's cloud, not just from the LAN. This requires exposing
my private music server to the public internet, which I am
not willing to do.
Specific questions I would like answered:
A. Is there a currently-supported, first-party way for an owner
of S2-compatible Sonos hardware to register a local SMAPI
music service against their household, that works on
firmware 80+ and does not require exposing the service to
the public internet?
B. If not, what is Sonos's plan for owners who bought hardware
specifically for its advertised support of local libraries
and third-party music services?
C. If the answer to (A) is "no" and to (B) is "we have no plan,"
can you confirm in writing that current Sonos firmware no
longer supports local-only third-party music services so I
can make purchasing decisions accordingly? I will not be
purchasing additional Sonos hardware until this capability
is restored.
Hardware firmware version (from /xml/device_description.xml on each
unit): Sonos/95.0-77060 across the fleet, including the Play:3.
Network detail: speakers and music server share a /24 subnet, no
NAT between them; all relevant ports (1400, 4534, 5005) are open
on the LAN. The problem is the speakers' refusal to accept LAN
SMAPI registration, not network reachability.
Thank you. I would prefer a written response that I can keep with
the purchase records for these speakers.
- Ashton Honnecke