Skip to main content

Does anyone know when v11.9 was released on sonos s1?.. there is a bug with this version I discovered and am wondering when 11.9 came out… many thanks in advance 

According to this page, 5/24/23


Many thanks, that date aligns with a “bug” i reported to Sonos.

 

My Sonos S1 no longer plays some live radio stations….They won’t start.

 

Hope they fix it and just leave S1 alone.

 

Cheers


Many thanks, that date aligns with a “bug” i reported to Sonos.

 

My Sonos S1 no longer plays some live radio stations….They won’t start.

 

Hope they fix it and just leave S1 alone.

 

Cheers

You sure the stations are not themselves broken? Can you give an example of a station that fails now?


Yep, I checked and the radio stations work outside of Sonos.

 

Radio.net     - radio ibiza 97.3

 

Won't work in Sonos S1, but works via the website


This particular station works in S2 but not in S1.

The internal error is ERROR_NO_PLAYABLE_CONTENT, but from what I can tell the service is returning the same data to S1 and S2, which would indicate some kind of regression in the S1 code from Sonos.


This particular station works in S2 but not in S1.

The internal error is ERROR_NO_PLAYABLE_CONTENT, but from what I can tell the service is returning the same data to S1 and S2, which would indicate some kind of regression in the S1 code from Sonos.

Sonos support are looking at this issue…was working fine on S1 prior to the latest update in may…


Did some debugging here. The real streaming url for this station is

https://kisskiss.fluidstream.eu/ibiza.aac

but this smtream does not work on S1. Interstingly it does not work in VLC either, and VLC refuses to play it because

Certificate verification failure: The certificate is NOT trusted. The certificate chain uses expired certificate.

From what I can see (I am not an expert in SSL) the cert is not expired, but it uses a “Lets Encrypt” root cert and it appears that S1 (and VLC) do not accept that certificate.

My guess is that this cert was updated and it broke S1 playback, I doubt this is the result of an explicit Sonos code change. S1 supports way less certificate types than S2 (see https://devdocs.sonos.com/docs/security#what-happens-if-your-certificate-fails-in-production for the details).

The fix is easy: add this streaming url to your S1 system:

http://kisskiss.fluidstream.eu/ibiza.aac

(ie drop the https)


Oh and the cert was changed right around the same time as the S1 update, so the fact that the update appeared to break it was entirely coincidental (as such things often are).


Did some debugging here. The real streaming url for this station is

https://kisskiss.fluidstream.eu/ibiza.aac

but this smtream does not work on S1. Interstingly it does not work in VLC either, and VLC refuses to play it because

Certificate verification failure: The certificate is NOT trusted. The certificate chain uses expired certificate.

From what I can see (I am not an expert in SSL) the cert is not expired, but it uses a “Lets Encrypt” root cert and it appears that S1 (and VLC) do not accept that certificate.

My guess is that this cert was updated and it broke S1 playback, I doubt this is the result of an explicit Sonos code change. S1 supports way less certificate types than S2 (see https://devdocs.sonos.com/docs/security#what-happens-if-your-certificate-fails-in-production for the details).

The fix is easy: add this streaming url to your S1 system:

http://kisskiss.fluidstream.eu/ibiza.aac

(ie drop the https)

Thank you so much for spending your time looking into this - legend!.  I’ve added the stream URL to my S1 system and it works!...I’m curious how you found the URL as I searched everywhere for it and could only find https://au.radio.net/s/ibiza973  which didnt work


Thank you so much for spending your time looking into this - legend!.  I’ve added the stream URL to my S1 system and it works!...I’m curious how you found the URL as I searched everywhere for it and could only find https://au.radio.net/s/ibiza973  which didnt work

I write Sonos apps for fun and utiny] profit. If I can reproduce a problem then I stand a chance of figuring the issue out, which is how I did this one. This was a new area for me to dig into, so it was fun to resolve. Normally issues that happen in the players remain “mysterious”, but this one could be investigated in the player code with a few changes.