Sonos chime instead of radio

@Airgetlam I had exactly the same thought when chimes first starting happening to me.

For as I said above “When it fails, I immediately grab my phone (controller) and press play (for the same TuneIn station) and it always works fine.” The first connection attempt seems to prime the second.

I think in a lot of network cases, it can….for instance a duplicate IP address. It’s possible the first attempt, although it fails, is enough to tell the router “no, the Sonos wants that IP address, bump off the other one”. Not quick enough for the first to connect, but clears the way for the second to connect. 

This is all guesswork, mind you. The only real way to know for sure is to send Sonos a diagnostic after that initial failure, and ask what they see.  Those of us on these forums don’t have access to that data, unfortunately.

I’m having a similar issue as being reported here. I’ve tried deleting and resetting alarms. Radio will play normally without issue, except when used as an alarm tone

What did Sonos say when you submitted the diagnostic, and called them about it?

I haven’t been asked to submit a diagnostic yet

Submit one anyway, then call them to ask them to see what’s in it. Best to do so within 10 minutes of it playing that chime rather than the radio station, so that the event is captured in the data in the diagnostic. 

Who is your Internet provider? I am having issues with my Zappiti and occasionally SONOS doing the same thing when attempting to access the Internet to retrieve data. On the first try the connection fails and both SONOS and Zappiti are reporting the error message as being unbale to connect to the respective source which is Internet based. On the second attempt both SONOS and Zappiti make the connection and the system operates normally.

I also noticed the same issue whenever I go to certain sites via any of the current browsers on Windows 10. I have a case open with Xfinity and am currently doing a Wireshark capture on my Zappiti and computer to capture the actual error message being returned by the initial attempt.  I suspect it has something to do with a DNS lookup failing.

I’m aware that individual anecdotes prove little.

However it’s now been 18 days since I changed my alarm time from 08:00 to 07:55 and I’ve not had a single failure since. So I still wonder if the (or perhaps a) root cause of the failures is a TuneIn server getting slammed at popular times (on the hour, on the half-hour, etc). 

It’s possible, but that would be hard for Sonos to diagnose, since that server is owned by the streaming radio station, neither Sonos nor TuneIn for that matter. 

If that were the case, I’d expect that the information you’d get from Sonos would be “the system tried reaching out to the service at that moment, but it didn’t respond”.

I do applaud your troubleshooting, however. It’s an interesting piece of data. 

This problem has been driving me nuts for some time now. I had a one to one on the phone with Sonos support on Wed 18th May. Case No. 03899693. He went through numerous checks over a period of 46 minutes. Changed the primary speaker for the alarms. I have one in every room and they are grouped together. It has worked up until this morning, when instead of the programmed LBC, the bloody annoying Sonos chimes are back again.