Sonos is forcing people to buy new hardware as they've broken the Connect:Amp and they refuse to fix it



Show first post

261 replies

Userlevel 4
Badge +5

Still getting the issue. An occasional reboot will stop the issue for a week or two. It's gone very quiet here, waiting for an update from Sonos…

Userlevel 4
Badge +2

I’m nearly 11 weeks into the rollback and even the latest S1 app is stable. 

How did you decide to risk that update? Fingers crossed basis?!

I didn’t spot it until it was too late 🙈

I generally ‘update all’ on my iPhone and didn’t notice the S1 update until it was too late so I had to cross my fingers and hope. 
 

No other devices were updated and there doesn’t seem to be a MacOS update so worst case my phone would’ve been out of the loop but everything else would have been okay. 
 

But for the faint of heart, 11.14 has been working fine so far… 🤞

Unless Sonos speaks on the subject, I am not budging beyond 11.12. All to lose and little to gain.

Userlevel 7
Badge +14

I’m nearly 11 weeks into the rollback and even the latest S1 app is stable. 

How did you decide to risk that update? Fingers crossed basis?!

Asked the magic 8 ball, but it didn’t predict the Alexa bug 🤣

I’m nearly 11 weeks into the rollback and even the latest S1 app is stable. 

How did you decide to risk that update? Fingers crossed basis?!

Is there a procedure to roll back the entire system of connects & connect amps to S1?  If that fixes it, that would work for me.  

Yes. You’ll find the procedure on the Sonos website. 
Be patient - sometimes the devices will hang on the roll-back and you have to wait and if that doesn’t work, restart the process for that particular device. 
 

I’m nearly 11 weeks into the rollback and even the latest S1 app is stable. 

I just completed the rollback.  Appears to be working great.  

Userlevel 4
Badge +2

Is there a procedure to roll back the entire system of connects & connect amps to S1?  If that fixes it, that would work for me.  

Yes. You’ll find the procedure on the Sonos website. 
Be patient - sometimes the devices will hang on the roll-back and you have to wait and if that doesn’t work, restart the process for that particular device. 
 

I’m nearly 11 weeks into the rollback and even the latest S1 app is stable. 

Is there a procedure to roll back the entire system of connects & connect amps to S1?  If that fixes it, that would work for me.  

Userlevel 1
Badge +2

I just updated to 16.1 and the issue is still there.

Sorry to hear that 16.1 isn’t working. 
The S1 rollback remains utterly stable (devices and app) after more than 10 weeks of continuous up-time. 

Yup still an issue.   Like others rolling back is not an issue due to mix with other newer kit.  (Relying on nightly power downs on a smart power strip.)

Userlevel 4
Badge +2

I just updated to 16.1 and the issue is still there.

Sorry to hear that 16.1 isn’t working. 
The S1 rollback remains utterly stable (devices and app) after more than 10 weeks of continuous up-time. 

Badge

I just updated to 16.1 and the issue is still there.

Userlevel 7
Badge +22

Interesting, hopefully that information will be forwarded to the development team to aid them in finding a solution.

Badge

Adding myself to this list of users with issues on the new firmware.  I use Roon to send music to Sonos players throughout my house and am having issues similar to everyone here.  Roon loses connection with each of the Sonos players after 29 seconds.

Using Wireshark I was able to confirm the issue with my Play 3. From the Sonos Play 3 to Windows, I am getting [TCP ZeroWindow] and [TCP Window Update] and from the Sever to the Device I am getting [TCP Window Full], to which the device then drops off the connection.  It seems when Roon sends the song data it is too much for the allocated buffer of the device.

This firmware bug is impacting Play1, 3, 5, Connect and Connect Amps that were originally on S1 and upgraded to S2.

Using Plex, Sonos library I can get more playtime out of it, but it will eventually cutout.  Similar to some of the old Play 1’s will work if I reduce quality to 16 bit on Roon, I can get them to play a bit longer.  But the Play 3, even a 96kbps AAC file through Roon it will cut out at 29 seconds saying that the allocated data through TCP is full and the device closes the connection and stops playback.

Add my name to the list of Connect:Amps that drop out. Started a couple of months ago. Worked fine until then. 

Joining the thread heard -- spent all this time F’ with the network but seems it is just the S2 and C:A issue...Tracking as well

Is not this present issue with Connect Amp memory cards there even where the Connect Amps are hardwired back to the core network? Why are channels relevant if that is the case?

If I am not mistaken even while hardwired SONOS devices still broadcast the SONOSnet backbone Wi-Fi.

They do if their radio is not turned off as it can be via the app. But comms between wired units are always by wire regardless of state of the radio.

Userlevel 1

Is not this present issue with Connect Amp memory cards there even where the Connect Amps are hardwired back to the core network? Why are channels relevant if that is the case?

If I am not mistaken even while hardwired SONOS devices still broadcast the SONOSnet backbone Wi-Fi.

Userlevel 7
Badge +17

I’m running 16.0.

Userlevel 4
Badge +2

Using my Connect (Gen 2) yesterday to play the new Walter Trout CD to my system I noticed too that the sound stops every few minutes. Since my other speakers are not affected I suspect my Connect also suffers from this. I hope that Sonos is able to restore the Connect to it’s former stable performance.

Are you running the latest S2 update?

Userlevel 7
Badge +17

Using my Connect (Gen 2) yesterday to play the new Walter Trout CD to my system I noticed too that the sound stops every few minutes. Since my other speakers are not affected I suspect my Connect also suffers from this. I hope that Sonos is able to restore the Connect to it’s former stable performance.

Userlevel 4
Badge +2

A quick update eight weeks into the S1 rollback. 
 

Everything remains tickety-boo. 
 

Has the last S2 update resolved the issue for those of you on S2? 

Is not this present issue with Connect Amp memory cards there even where the Connect Amps are hardwired back to the core network? Why are channels relevant if that is the case?

Userlevel 7
Badge +22

Also just because a channel is good today doesn’t mean it will be good tomorrow.

We have had issues with neighbor’s routers that auto select channels picking our Sonos channel. Right now we are seeing most neighbors dropping Cox Cable and their router for Quantum Fiber and their three pod mesh, so much fun for us trying to find the best channel.

Unless you have a channel monitor (not a simple WiFi scanner) you can’t get a great answer on which channel is best, still worth trying the scanner though as it points you correctly in most situations.

WiFi interference will be location dependent. Channel 6 might be the magic bullet in one location and not so good in another. And conditions can change. For example, a neighbor cold reconfigure their system and start interfering with your WiFi.

Start keeping a log. You may notice that certain times of day or week are better than others. This might allow you to start a discussion with a neighbor. 

Userlevel 1

Some of my coworkers are reporting that SONOS is now advising people to adjust the channel that SONOS net operates on. They seemed to have shown success in the short term with the audio drop outs. Has anyone still had this issue after adjusting away from the default channel 6? Please if you have a system still experiencing this issue give this a shot and report back.

Thanks.

Reply