sonos play: 5 Gen 1 constantly stopping for 10 sec.

If this is happening only when you stream Spotify - then it is because your Play 5 Gen 1 dont have enough memory to handle Spotify Streaming. It is a Known-issue at Sonos - but they dont want to spend time on fixing it in their software for S1 - so leaving old legacy customers in the dark :(  I have two Play 5 Gen 1 - they play perfectly fine  when streaming ie radio and other streaming services - only a problem with Spotify.  Its hard to believe that Sonos and Spotify could not solve this issue for our devices - if they wanted…..

Good to actually see some confirmation that I’m not alone on this. Support was telling me that all my Play:5 had a hardware fault, occuring at the same time. But it’s beyond me why they can’t fix this, what could possibly have changed that makes ONLY spotify stop working like this? 

What you can do, is actually play Spotify from another, newer player (Play:3, Play:1) and then group your Play:5 to it. Then it will probably play flawlessly. 

Which is also kind of mind blowing, seeing that I believe it is still playing the same stream (albeit, the coordinator player might deal with some decryption which might be the culprit). 

But it’s a bit of an outrage to just drop support on legacy speakers without any information. Or rather, break a streaming service implementation beyond repair and leave it like that. 

I’m not sure how connecting your phone to the same router does anything at all to rule out wifi interference , as certainly a large amount can come from outside the network. 

Assigning reserved IP addresses in your router can sometimes help, especially if the router frequently loses where it is in the DHCP table, and assigns a duplicate IP address to Sonos, when it reboots after a software update. 

For most purposes, your routers speed for up and down has almost no impact, the area you should be paying substantially more attention to is the speed between your router and the Sonos devices. 

Are you still using SonosNet? If at least one device is hardwired to your router, you should be able to adjust the SonosNet channel in use on the controller. However, if you’re no longer using SonosNet, but instead have everything connected to your WiFi signal, then the option to change SonosNet channels is greyed out. 

Have you contacted Sonos support, as I recommended in my original ‘answer’ in this thread? Much of that data would be in the technical diagnostic that they would be reading. 

If you’re unable to tell what your neighbors are using, I’d definitely try other channels, just as a test. 

It is a nice quote from the document , but not the only source of potential interference. I’ve seen lots of issues with DECT phones, and I’ve had personal experience with both a failing microwave that when on was spamming interference across the WiFi spectrum, and a new neighbor choosing to use a channel I’d been using for SonosNet. Once I figured that out, a quick change to my own network channels resolved that. Oh, and I replaced the errant microwave. If it was causing issues for Sonos, there’s no way of knowing what potential effect it was having on me. 

Nor have we ruled out a potential hardware issue on your device itself, something that would likely be discovered in the data you provide to Sonos support. 

You made several assertions in your post that I’ve not found to be accurate, when talking about Sonos, and the way it interacts with the network. 

Hopefully, talking to Sonos directly might resolve the issue you’re evidently experiencing, or at least provide you with more hard data to consider. 

I don’t understand your statement that says ‘ My Play 1 is too new to add to S1 ‘. All PLAY:1s no matter what the age will run S1. You would need to factory reset it, and then ‘add a device’ to your existing S1 system.

I wouldn’t touch a BRIDGE with a ten foot pole. I’d instead, if needed, use a BOOST, again setting it us as an S1 device…but it really isn’t required if you can wire to a speaker, The BOOST (and BRIDGE before it) is essentially just a standard Sonos speaker, without the speaker parts, but instead all the electronics/networking/CPU/Memory in a small package. 
 

You should always be able to share music across the same version of the Sonos operating system, either S1 or S2. If you’re having an issue, you should submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it.

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 phone folks, they have tools at their disposal that will allow them to give you advice specific to your Sonos system and network.

Blair, 

I’d still encourage the diagnostic and calling in to Sonos aspect. If it’s just happening with one stream, that really points a lot more to issues on their side, rather than Sonos, but then each stream tends to have its own sensitivity to Wi-Fi interference, so checking in with Sonos would likely be a good thing. 8 second intervals could be anything, unfortunately, from IP conflicts, to interference, to issues with Spotify’s servers.  Without looking at that hard data in the diagnostics, that only Sonos folk have access to, it’s really hard to tell.

Your PLAY:1 definitely can run S1, sound like you may just need to fiddle a bit more. Might not hurt to bring that up on your call, Sonos could likely help you get that speaker reconnected to your S1 system. 

I think you can call, although you might get shunted to the UK call center.

Shouldn’t be any ‘memory’ issues on a standard S1 stream, however HD streams are much more sensitive to wifi interference due to their need for higher bandwidth. 

The PLAY:1 is probably in a better receptive area for a signal, and is then sharing it via SonosNet with the PLAY:5. 

Wifi is a tricky thing, and constantly changing. It’s also affected by all sorts of external influences, up to and including solar flares. It isn’t ever a ‘set and forget’ system that never changes. Even wired networks are constantly changing for a multitude of reasons. 

Which is exactly why I suggested calling in. Just because 99% of the time, it is issue X doesn’t mean that you’re not in the other 1%. And not having access to anything other than your comments here, I’m somewhat hampered, and will almost always go with the 99%. 

I had vexing issues with my setup. Much fussing about before I sent in a diagnostic and talked with support.

My problem I had two different issues, a pair of Play 1 Surrounds that were too close together, inches, and a Beam and Play 3 that were also inches apart even though in different rooms.

Giving them both a couple feet of separation ended the issues.

My Play 5 Gen 1 has this issue. I spoke to support for over an hour. All they said at the end of that call was, try plugging it in via ethernet. Never mentioned this memory issue.