Custom radio URL completely broken (Sonos S1 app, legacy system)

Forum|Forum|1 year ago
March 17, 2025
22 replies
456 views

I am a happy user of an old Sonos Legacy system with the S1 app, an old Connect, a Play:1 and :3 (with proper buttons) and an OneSL because I couldn’t find a proper Play:1 anymore.

Mostly, I've been using the system to listen to my local music library or Tidal, or stream a webradio station via the custom URI “hack” via tunein. I've seen that a lot of people have issues with that with the new app, with the S1 app, it still seemed to work fine.

Until now.
I had been away from home for a couple of weeks and when I came back, the custom radio doesn't work anymore. That is, in Sonos. It works in the TuneIn app, it works on the station’s website, the raw URI works fine from all sorts of streaming players.
I tried to get Sonos to directly play the stream via the API (x-rincon-mp3radio), doesn’t work. Tried other streams - don't work. Normal, ad-infected TuneIn works. All my custom URIs stopped working.

Via the support webinterface (:1400/status) of my Sonos hardware, I found out that a software/firmware update was pushed to them on March 9th. That might be the culprit.

Does anyone else have this problem? Was there even anyone else around with custom radio still working? Is there any hope of a solution? Do I need to spent a lot of money to buy new hardware even though the stuff I have could theoretically easily do the job?

So many questions. Thank you for indulging me.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Show previous replies

Airgetlam

Note that most ‘streams’ from Sonos use different ‘endpoints/servers’ than streams from outside Sonos, so that the Sonos system is reaching a server that has SMAPI installed on it. In this way, ‘outside of Sonos’ apps aren’t always a good indicator of connection as what’s going on inside of Sonos.

It could be as simple as a DNS change between you and the endpoint, or something equally hard for you to diagnose without access to that hard data hidden in the Sonos diagnostic. Sometimes, the easiest thing to do is a simple network refresh, by unplugging all the Sonos devices from power, then rebooting the router. Wait a couple of minutes for it to settle down, then plug back in your Sonos. Wait another two minutes before testing.

But, as always, looking at that hard data helps, so I would recommend that you submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it. Don’t post the resulting diagnostic number here, they get sensitive about GDPR.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

When you speak directly to the Support staff, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

Bruce

S

Stefan MaxAuthor

Contributor I

Another update: I tried @Sean M 's advice and the stream I'm using actually works over http. So far it’s playing reliably. So it's probably indeed some black-magic SSL issue.

What's weird is that by now “official” TuneIn streams stopped working as well (even high-profile ones like BBC6 music and the likes). And then again, do work intermittently without any discernible pattern.

Well, as long as the http stream works, I’m happy.
I'm just wondering where I’m going in the future. 🤔

Sign up

Login to the community