Skip to main content

This issue has re-appeared after being resolved for quite some time.  That is, it was bad, then it got better for many months, and now it is back.  Perhaps something in the new updates?

 

 

 

Hi ​@Gerald Harmon, welcome back to the Sonos Community!

I’m sorry to hear that you’re having issues with your Connect:Amp again. After looking through the previous thread, the posts by Corry P are still relevant. The update that initially ‘fixed’ this for you, was just security fixes for S1 systems. I’ve had a look into our internal information and this is still ongoing.

I don’t see all of these mentioned in the previous thread, but there are ways to mitigate the issue. Please note however these may not fully resolve this, they are:

 1. Reboot your Connect:Amp.
 2. If the Connect:Amp is wired, make sure it only has one Ethernet cable and isn’t being used as a bridge.
 3. Reduce the load on the player by turning off Crossfade and Shuffle.
 4. If the Connect:Amp is the only wired product, wire a different Sonos product to network and ensure it's the first wired device.
 5. If the affected product is the Group Coordinator, choose a different Room as the Group Coordinator to see if performance improves.

I did see you tried a few of these already, but if these don’t mitigate the issue then a replacement is likely in order. If you’re not looking to replace the Connect:Amp, then please reach out to our support team to discuss what you’ve done and what your next options are.


thannks ​@Jamie A .  likely best and only option is the reboot.  already good on the other numbers other than replacement of course.  does seem inconsistent, however, and a bit weird that the issue lies dormant for great lengths then reappears with no change in hardware, etc.  but I’ve been around the environment long enough to appreciate a gremlin or two.

 

thanks again.


Reply