Local Devices Music Library & 48khs audio

The claim that Apple and Android restrictions forced the removal of local playback oversimplifies the situation. While these restrictions introduced challenges, they didn’t make local playback unworkable—other apps, such as VLC, successfully implemented solutions like sandboxing and temporary file caching, which are widely adopted practices in modern app development. The Sonos app’s previous support for direct local playback proves it once delivered functionality far beyond being just a controller. Sonos made a deliberate decision to shift its priorities, investing in SMB sharing and streaming services instead of exploring feasible options to retain local playback. This strategic shift was a choice, not a necessity, and to suggest otherwise misrepresents the app’s history and the technical possibilities that were clearly within reach.
 

You can assume all you like about this being a deliberate decision, which it wasn’t, but the fact remains playing content from these devices is not possible via Sonos the reasons have been given. 

Sonos disabled it as it was the only thing they could do as it would stop working.  It likely will never be restored as there are perfectly good alternatives.  Your use case is also quite niché and would likely feature low in any Sonos enhancements, even if it was possible..

Did you even read my post?  The fact you keep comparing the Sonos CONTROLLER app to a MEDIA PLAYER app like VLC is proof you either didn’t read, or don’t understand the difference between the two. Furthermore, there was never any “previous support for direct local playback” from the Sonos app.  Every Sonos app ever released PLAYS NOTHING, so any point about local access means nothing.  Just the same as every other source - SMB libraries, streaming services, radio station URL’s, etc. - the previous Sonos apps told the Sonos hardware to play files on the controller device via outside access, something the OS manufacturers have now banned due to security issues.  

​@Scott Campbell 

And just to answer your question… Sonos music library playback via smb2 share from my usb device that is used as routers nas storage workes absolutely fine. 

As further proof that this was the fault of the OS manufacturers and not Sonos, if Sonos made a “deliberate decision to shift its priorities”, why would it end playing from an iOS device back in 2019, but kept the function going for Android until 2023?  Four years is a pretty long time to “deliberate” a shift in priorities.

Your explanation hinges on a misrepresentation of my points. I did not compare the Sonos controller app to VLC as a media player. I referenced VLC to demonstrate the feasibility of technical solutions, such as sandboxing and caching, which could have been implemented to retain local playback functionality despite platform restrictions. Similarly, I cited BubbleUPnP and X-plore File Manager to show that local file access is entirely achievable within Android's policies—not as functionality comparisons to Sonos.

Your claim about ‘direct local playback’ is semantic nitpicking. While the Sonos app didn’t play files itself, it facilitated playback by accessing media stored locally on the controller device via Sonos hardware. This constitutes local playback in practice. Furthermore, the argument that platform restrictions rendered this feature impossible is demonstrably false—other apps have successfully maintained similar functionality within the same constraints. Removing this feature was a decision, not an inevitability, and reflects a choice not to prioritize a solution.
 

Your assertion that local playback is a niche feature ignores clear evidence to the contrary. The removal of this feature sparked backlash across forums, including the Sonos Community, where users repeatedly emphasized its essential role in their experience. Local playback allowed users to directly access their media libraries without relying on streaming services or cloud storage, delivering autonomy, simplicity, and reliability. For many, this feature wasn’t a secondary convenience—it was a core component of the system’s functionality.

Sonos’s proposed alternatives, such as NAS or SMB protocols, introduce unnecessary complexity and fail to replicate the immediacy and ease of direct local playback. Technically, retaining this functionality was feasible—other apps have successfully implemented sandboxing and user-managed file access to comply with platform restrictions. Removing this feature without offering a comparable replacement dismissed its clear value to the user base and overlooked its demand.

Your framing of the timeline distorts the realities of platform restrictions. While Apple introduced stricter policies in 2019 that blocked local file access, Android maintained flexible mechanisms for an additional four years, enabling Sonos to retain local playback on Android devices during that time. Even after those four years, Android’s policies did not impose a total block on local playback functionality. Apps such as VLC and BubbleUPnP demonstrated the feasibility of local playback by utilizing compliant frameworks like user-managed file access and sandboxing.

This timeline reflects missed opportunities. Sonos had the technical capability to adopt similar solutions to preserve local playback across both platforms, as other apps have done. The removal of this feature was not dictated by platform manufacturers but was instead a deliberate choice made by Sonos to shift priorities away from retaining this functionality. The availability of feasible solutions underscores that this decision was avoidable.

You say semantic nitpicking, I say actual rules laid down by the OS manufacturers that, when broken, will get your app removed from their respective stores.  Tomayto, tomahto. 

Whatever.  I wasted way too much time on this.  Keep hoping you are right, though.  But you know what they say “Wish in one hand . . .”