Skip to main content

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.

Please post the url you are having trouble with.


Actually, all of them.
Two examples:
https://streams.egofm.de/egoFMBW-hq
https://play.adtonos.com/thisisprimordial
(And another one that contains personal login data which I’d rather keep, well, personal.)

When trying to play one of those on the OneSL, it blinks white once and orange twice. That is the only maybe meaningful error message I got.

When trying to play through the S1 app, the “play” button turns to the square stop and immediately back to play. No waiting circle, no buffering time, nothing. It's different than when internet is choppy or the station is down…

My current solution would be to hook an old phone up to the line-in and stream on the phone, but oh my...


Sonos plays audio streams: these are not streams, they are web pages. Sonos is not a web browser.

The first one uses a stream of https://cast.egofm.de/egofmbw.mp3?ar-distributor=ffa0&aw_0_req.gdpr=true

The second one is https://fr1-play.adtonos.com/8108/thisisprimordial

I have checked neither of these in the Sonos app, there may be other reasons they don’t play (headers missing, auth, codec, streaming format), but they stand a better chance than a web page.


Funny thing is - exactly these webpages worked before just fine. Also I think that they're just redirects, not actual webpages, but that's semantics.

Also, they still do work in tunein, vlc, basically anything else that plays streams.

And, the actual stream that I'm having trouble with is not a redirect URI or a webpage but that is the actual URI of the stream that has worked for the last ten years with Sonos (via tunein). Nothing about that stream changed. It’s 32bit stereo 44,1KHz MPEG AAC Audio stream (or so VLC tells me), so Sonos should be able to handle that (like it always did).

Do you happen to know a streaming URI that 100% works that I could test? I'm pretty sure that it's not an issue with my network, I still think the March 9th update of the Sonos hardware broke something (funny that the old hardware gets updates at all).


Both stations play fine for me on S2 with the links originally provided by Stefan so I don’t see why they shouldn’t work on S1, especially if they worked before. I don’t have an S1 system to test though and the only thing I could imagine being the culprit here is an SSL issue, because S1 doesn’t support the same things as S2.


Today I’ve had a long and actually quite pleasant conversation with Sonos support, and after ruling out any problems on my part (network configuration etc), they said that there is an issue with tunein-streams they're aware of and trying to fix (understandably, they didn’t give me any nitty-gritty details).


… and the only thing I could imagine being the culprit here is an SSL issue …

That may well be the issue. I haven’t checked all of them, but one stream that no longer works is an http link, whereas one that still works is https. (I also have a Sonos One SL.)


Interesting, I would it expect the other way around but maybe the station has shutdown the http stream all together. 


Interesting, I would it expect the other way around but maybe the station has shutdown the http stream all together. 

Although the original poster specified the S1 app, I use the S2 app with my Sonos One SL. Involvement of TuneIn is a possibility as well, since that became required for custom URLs.

In my case, the http streams are still online and working.


Update of the Sonos Controller (S2) for Mac today, to 17.0: Under the Manage menu: Add Radio Station! It goes into My Radio Stations at TuneIn (not “TuneIn (New)”). I added an http stream and it worked: http://s6.voscast.com:11312/listen.pls. Also an https stream worked: https://mediaserv73.live-streams.nl:18058/stream.


Notably, however, the Sonos 2 app for iOS does not reflect this (yet?), and the added stations are not available from there.


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.

Hey Stefan, I’m in a similar situation. Old Play5 Gen1 with S1 app. until semi-recently, when playing my favorite internet radio station Radio Paradise, there was a stream of “My Favorites” available. Now it’s solid gone. Tried following Sonos’s advice to add it via TuneIn but that didn’t work. This is so frustrating so I guess I’ll go back to streaming my favorites on my little Bose speaker. 


oopsie, posting as a reply:

I’m in a similar situation. Old Play5 Gen1 with S1 app. until semi-recently, when playing my favorite internet radio station Radio Paradise, there was a stream of “My Favorites” available. Now it’s solid gone. Tried following Sonos’s advice to add it via TuneIn but that didn’t work. This is so frustrating so I guess I’ll go back to streaming my favorites on my little Bose speaker. 


I’m curious, not having any experience anymore with S1, but what did Sonos Support say, when you called in with this issue?


haven’t had the time to call them yet. kinda busy season at work!


Just a quick update, I was away from home for a couple of weeks, came back and the custom streams are working again in the S1 app and on the old hardware. I didn't do anything, just tried to start the stream and - voila - it worked again.

All my custom streams are (still) available under tunein - my radio stations.

So anyone having the same issue - you might want to give it a try again.


@Stefan Max Glad to hear this is working for you now.

For anyone else who runs across this, there’s some older encryption suites that we had to drop support for, which is leading to some stations which haven’t been well-maintained to become unavailable. That’s not the only reason stations won’t play, but it’s the root cause behind a a lot of them right now, especially if you notice a difference between S1 and S2.

If it’s a TuneIn stream (or another radio service we natively support), I’d recommend contacting our support team. Once they confirm that’s the issue, they’ll take a report so we can advise the station to upgrade their cipher suite. If you have the URL (and/or it’s a custom station), try using “http://” instead of HTTPS. If the stream supports this, it should allow you to bypass the unsupported encryption until they get around to fixing it.

 

Reply