Alex we are very disappointed that you didn’t join the forum earlier to help Sonos figure this out cause they were incapable of doing this on their own (or maybe that was the point . Shame shame shame on you LOL /s

I've only had one install that had issues with the new equipment. Primarily from what I understand the issue was when the client would group play the arc audio from his TV throughout the home. SONOS support had informed me that streaming this audio source requires each Amp to decode the audio stream from the raw hdmi signal which requires more processing power. After installing a new dedicated switch in the home for the 5 Amps and disabling their Wi-Fi. The issue seemes to be resolved now.

I only note this since it seems to be related to SONOS devices maxing out their processor and memory in general.

$700 for the Connect:Amp?

Replacing the connect:amp with Amp will be ~$700 each no? 

On first read, it sounded like he was saying that the original purchase was $700.  I see it now.  

NEW S2 UPDATE! Any joy with it?  I might be imagining it but our system of various older & recently bought kit seems more responsive.

Need to leave it on a few days….

So had many customers reporting problems with Connect Amp from last summer and doesn’t think to mention a thing or join the community here until 7th February - no wonder Sonos were unaware of the issue. Certainly could not put the blame down to the network either, as that was being maintained by them too.

Presumably this is tongue in cheek, because this particular poster’s delay in joining the community does  not excuse Sonos from not knowing the issue, and further, from proactively communicating it to all Connect Amp users on S2. This is a BIG Sonos fail, right up there with their bricking fiasco four years ago.

@Alex.Dickson I suggest you send a diagnostic reference via email to Sonos Support for the issue with the new Amp because it is unlikely to be caused by the memory failures issue.

A professional installer that states they first noticed the C:A issue starting last summer, has a good many clients, they maintain their clients networks too and able to eliminate the local network as being the cause - but then lands here on the 7th February 2024, just seems a little late to the party IMV.

It’s these type of professionals, that I would personally expect to first bring a ‘real world’ matter to the attention of Sonos - I say that because individual customers that land here in the community, often don’t know if it’s a local network issue, or not and so the wood can get lost for the trees in trying to establish if that’s the case, whereas a professional installer, as I see it, can possibly be an entirely different ‘ball game’ - maybe more-so if they do speak direct to Sonos and can show details of their client-reported C:A cases since last summer.

The best person to respond to this “could have done/should have done” thing is the installer in question if he chooses to do so. 

Complaints that land up in this community cannot be the entire universe of  complaints that arise with the use of Sonos; indeed I suspect that they would be a small percentage of such, and I am sure that of the many installers of Sonos kit, some would have brought this issue to the attention of Sonos directly in the way that according to you, this installer should have done. It is also likely that this is the reason that Sonos has finally accepted this to be a Sonos created issue and not another user network one.

As you can see from the opening post of this thread, a preceding discussion on this issue in this community was locked by Sonos before the discussion was finished.

Late to the party or not. I didn't expect to receive such hostility from any community member here. I just want to help see the issue resolved. As I'm sure we all do.

I’ve discovered that it’s par for the course, I’m afraid. 

If you bring an issue early, you’re accused of overplaying it because you’re alone in suffering the problem.

If you bring an issue late, you’re accused of being late to the party because you should’ve shown up sooner. 

And if everyone with the same problem shows up en-masse at the same time, we’re all accused of acting in concert or worse, being a banned troll with fake accounts. 

I’ve been on the internet a while and this place requires the thickest skin and biggest sense of humour that I’ve ever come across. So don’t let the buggers get you down!

There are some obnoxious types here and others that do mean well inspite of being guilty of being naive fanboys. Don’t let any get you down is the right approach, but I have seen a lot worse on the internet!

I have already posted somewhere that I have the same problem with my C:A. But there was an update to S2 about a week ago and, I may regret being optimistic, but it seems to have cured the problem. Nothing else changed but in that last week I can’t recall one single drop out. 
I have to own up to not having read every comment even on this thread but I am of course curious to find out if anyone else with the problem has seen a recent improvement. Not sure where to look but is there anything in release notes for 16.0 that may justify my view?

Andy 

Absence of drop outs should be justification enough; on one of the threads on this subject, Sonos Staff endorsed this comment from me: Don’t look gift horses in the mouth.

As long as the gift keeps working!

Another user has reported a similar experience as yours, but two data points are just that.

downloaded the update, my Connect Amp has come back to life.  It had gotten to the point where it wouldn’t even detect zones or play at all, but after the update, we are looking good.  Will monitor performance over the next week or so.  If this was the fix, my sincere appreciation to the Sonos engineering team for rolling out the fix.

With these reports of the fix having worked, it remains to be seen if Sonos will make any recommendation to users of the affected kit to keep updating it with ever advancing versions of S2.

Hi all,

Sorry not been about for a couple of weeks, but some things I’ve noticed.

Rebooting the Connect Amp seems to fix the issue for a week or so (in my experience). Updates cause a reboot, so this can mess up the counting if an update happens in that time. So for those saying the update has fixed it, hopefully it has, but it might just be because it forced an reboot.

What I’ve done, which is the temp solution I’ll go with until it’s fixed, is to put the Connect Amp on a smart plug and I’ll just automatically reboot it every day. I’d much rather the issue was properly fixed though.

It’s weird though, if it’s true that Sonos has released a fix for this, and posted about it elsewhere, why haven’t they posted that to this thread? I don’t get them.

To be fair, I had the issue since Summer ‘23 and I didn’t create this thread till NYE! I kept checking the forum to see if anyone else had reported it, there was one thread that was locked for some reason which prompted me to start this one.

There is some talk by Sonos that the issue in the other threads is not the same as the one surfaced here and therefore the fix may not apply here, but there some lack of conviction in that talk. Basically, if the fix works for you, use it and be happy!

I am having the same issue as the original poster. Regular short dropouts (usually one per song) from a single hard-wired connect amp. Very frustrating issue.

Have you tried the latest S2 update? If so and it’s still not working properly then;

1. Please let us know and

2. You should try reverting to S1. I’m now over six weeks into my S1 rolllback and my connect amps and apps have been completely stable.

Yes I did the latest S2 update last week and was hopeful that would fix things but the issue persists. It might be happening a bit less since the update but it’s hard to be certain.

I had resisted upgrading to S2 for a long time as my S1 worked great but I had to get a new Sonos Amp last year and apparently needed to update to S2 at that time. I’m worried if I revert to S1 the dropout issue might fix but I won’t be able to connect to the newer amp.

According to Sonos the Amp is both S1 and S2 capable: https://support.sonos.com/article/sonos-s2-compatibility

Well spotted!