Skip to main content
September 19, 2023
Answered

Connect Amp keeps dropping out audio

  • September 19, 2023
  • 105 replies
  • 15459 views

Hi I have 4 Connect Amps that have been working fine for some years but just recently they are dropping the Audio for a few seconds which is very annoying. I have spoken to Sonos Support on a few occasions and done everything they have suggested to fix this which they say is WiFi Interference such as switching channels etc but still have problems. This happens on any music source but I have noticed when the speakers go silent the sound levels are still going up and down on the app as if its playing the audio in other words not muted, not sure if this helps identify the problem. I am getting to the point now where soon these will be removed as they just aren't worth the hassle. I have seen a few threads where people have had the same problem but the only answers I have seen are contact Sonos Support.

Has anyone had this problem and got a viable solution??????

Some posts suggest an issue with S2 being introduced so does anyone know if this is a problem??

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Best answer by Ken_Griffiths

So far I have tried as suggested by Sonos to give the 5GHz Wifi a different name, turned off auto on 2.4GHz channels so I can force it to be 1, 6 or 11, I haven't tried setting to 20Mhz so will give this a try.

Btw Ken can you give me more advice re your comment “give Sonnet a shot”? I did originally have one C:A hard wired to my switch with ethernet cable and then daisy chained the other 3 C:A’s but this didnt help, do you think it would be better for each C:A to be hard wired to the switch?

SonosNet is where one device is wired to the router (but positioned at least one metre away) - that allows Sonos to use its own in-built wireless mesh signal… so all your other Amps connect back to the wired device either directly or indirectly. If doing that, it’s best to do two further things…

  1. Set the SonosNet channel in the App’s network settings so it is at least 5 channels away from your chosen 2.4Ghz router channel, which should in turn be on fixed channel 1, 6 or 11 and ideally set at 20Mhz channel-width (if the router allows).
  2. Remove the router WiFi SSID from the Sonos App network settings as the local WiFi signal is no longer used and that will stop the Amps trying to hop onto your WiFi signal.

All that said however, the fact you now have the option to wire all to a switch - it makes sense to go with that option instead and you could even choose to switch off the Amps WiFi adapters in the Sonos App to reduce the potential for network loops/storms, but if they do work fine with the WiFi adapters enabled, then I would just leave them - that’s a matter for yourself.

Here are some links that may assist too…

 

105 replies

Airgetlam
March 11, 2024

I think it is less of a ‘borked firmware’ issue, and more of a ‘MTBF’ issue with electronic memory.

Bruce
Stanley_4
Grand Maestro
March 11, 2024

The newer firmware is apparently causing the problem to manifest but it isn’t an error in the firmware causing the problem. The firmware is forcing the hardware to use previously unused amounts of memory, memory that should (MTBF issues aside) be available and error free. As the memory isn’t performing properly due to age/wear issues we see the problem manifest.

This apparently is only impacting some older Sonos, and only a few of them. Ones that have a history of heavy memory use, leading to the additional failed memory locations.

Sonos may be able to find a solution to the memory issue and add it to the S2 firmware or they may be forced to admit it is unfixable and reclassify the older Sonos as S1 systems. Maybe leave them as S2 until the errors appear, then offer to drop them back to S1 or possible offer a reduced price S2 replacement.

Sonos rarely acts quickly but in the end they have a history of dealing well with customers.

Lyricist II
March 16, 2024

Add me to the list with super frustrating issues with 6 connects and 1 connect amps.  I guess misery loves company!  No way would I invest the money to upgrade.  I have no newer items.  is there any risk in the S2 to S1 downgrade?  Can someone link me to a procedure to do that?

Lyricist III
March 16, 2024

I’ve come to terms with the fact this issue will never be sorted, I just power the unit down when the problems start and it works okay for the next week or so. 

Lyricist II
March 17, 2024

Its no coincidence SONOS wanted to phase out and actually disable these older products. As I recall they only backtracked when users became outraged and they started getting a ton of bad press. Well then it seems scheduled obsolescence is what they decided to do instead. As a Wireless Network Engineer what really upsets me is the attempt to blame it on network issues when they know exactly what the issue is. Well if they won't upgrade we will make them upgrade. I would never recommend another SONOS product to anyone. I just can't trust they will stand behind their products. 

There's an old saying in Tennessee — I know it's in Texas, probably in Tennessee — that says, fool me once, shame on — shame on you Fool me — you can't get fooled again.
Airgetlam
March 17, 2024

I don’t recall any time at which Sonos planned, discussed, or announced that they wanted to phase out older equipment. They always had S1 support for them. Can you point me to a discussion where this is not the case?

The only thing I’m aware of that they backtracked on was forcing the old device out of service when it was used to get a discount on a newer device. That lasted for about three weeks, then they decided to allow the user to keep the old device ‘traded in’ as functional. 

Bruce
Trending Lyricist I
March 17, 2024

Your reply actually proves the point that they did attempt to phase out…in my view what they’re currently doing is essentially a way to force you to upgrade. 
I’m not inclined to spend another 5K$ to upgrade just to have them pull the same in 1 or 2 years.

Airgetlam
March 17, 2024

I don’t follow your logic. If they maintained S1 for older devices, and only chose to disable devices that were used for upgrades, how does that indicate ‘phasing out’? I can see the ‘phasing out’ for trade ins, but wouldn’t it have been much easier for them to stop support completely, and drop S1? Force everyone to upgrade, rather than giving people an option? 

I will ask again for a discussion where Sonos talked about this. It’s certainly possible I’m wrong, so I would love to see a link. 

And if you’re concerned about the need for ‘upgrades’, I’d recommend staying away from technology completely. Everything that has electronic memory, and a CPU will eventually need to be updated/upgraded . It’s happened to phones, computers, handhelds, etc. 

Bruce
Bumper
March 17, 2024

Your reply actually proves the point that they did attempt to phase out…in my view what they’re currently doing is essentially a way to force you to upgrade. 
I’m not inclined to spend another 5K$ to upgrade just to have them pull the same in 1 or 2 years.

Sonos screwed up massively releasing this firmware. But IMO this more Hanlon’s razor, not a diabolical attempt to get people to upgrade. 

Lyricist II
March 17, 2024

ln my opinion there is a big difference between sunsetting support for a product and pushing a firmware that renders a product unusable. All I expect in a product of this nature is to be able to continue to use it as advertised. I have no delusions of an electronic product that is "supported"  indefinitely. However I do expect it to function as advertised until the hardware breaks down and fails  What I feel SONOS has done here is render a perfectly working device (less then five years old I might add) unusable and I don't believe for a second that they were unaware of this issue before pushing the firmware that borked the same products they planned on bricking

https://fortune.com/2020/01/23/sonos-apologizes-updates-speakers/

and this is where I have a problem it's a move out of the old Apple iphone playbook and I understand that works for some. I just didn't anticipate it coming from SONOS. Live and learn I guess?!?!