Skip to main content
Avid Contributor I
December 21, 2023
Answered

Constant connection issues with two speakers

My system has started exhibiting near constant connection issues on two speakers in particular. A (I think) first gen Play:3 and first gen Playbar are the problems for the most part. Started about 6 months ago maybe. At night I play rain sounds from my music library on 3 different rooms in my home. A Play:1, a Play:3 (the problem one) and the Playbar that’s part of a surround setup with the Sub and two Play:1’s. The Play:3 will only function for a few nights before it starts cutting out again. If unplug it and restart the speaker it seems to fix it for a few more days.  Same with the Playbar, though it can also exhibit similar issues with TV programming. When I play this audio from my library, each room is playing it independently, mainly because playing grouping across multiple rooms usually gives me problems as well. So like I said, rebooting the guilty speaker seems to fix things for a few days. It’s almost as if they are encountering so many errors they freeze up or something. 
 

My network is a Google Nest mesh wifi. I’ve had if for a couple years, and nothing about my network has changed recently. Can someone take a look at my diagnostics and see if anything stands out?  The doagnostic is 281607275. 

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.
Corry P
Corry PAnswer
Sonos Staff
December 27, 2023

Hi @BrentD 

Thanks for the new diagnostics - they indicate that the Boost’s signal to the Play:3 is more than sufficient, and that there isn’t a troubling amount of interference near the Play:3, or at least there hadn’t been in the 15 minutes prior to the submission of the diagnostic. It’s also not reporting any playback errors, so I can’t correlate what goes wrong to anything specific. This does lead me to believe that if you can cure the multicast flooding issue at the Boost, you will probably fix the Play:3’s issues. Note that although Boost reports a 10% transmission error rate (that I reported before), it reports similar levels with other speakers, so this probably isn’t the answer we’re looking for.

Alternatively, you could try putting your Sonos system on to WiFi instead of SonosNet - go to Settings » System » Network » Manage Networks » Update Networks and follow the on-screen instructions to connect your system to WiFi. When the app tells you to disconnect the ethernet cable, just unplug Boost from power and wait a couple of minutes. If, after testing, things don’t work as well as they currently do now, just power the Boost back on to revert. Please ensure all speakers are online when you setup for WiFi.

I hope this helps.

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein

16 replies

Airgetlam
December 28, 2023

Just didn’t want you to fret. The forum moderators seem to be excellent folks, but they’re neither 24 nor 7, and with the holiday, even more so ;)

Bruce
Corry P
Sonos Staff
December 28, 2023

Hi @BrentD 

OFDM ANI in Network Matrix indicates the 5GHz interference levels - as you were on 2.4GHz SonosNet, this interference probably wasn’t the interference causing the problems, but the baby monitor might have been (the change wouldn’t have shown in the OFDM ANI readings). On your latest diagnostics, all speakers other than Playbar are using 5GHz, so those readings in Network Matrix are now relevant. Playbar will only ever connect to 2.4GHz.

I recommend you relocate the WiFi access point to another location in the same room, away from other devices - not only will this improve things for those devices, but anything trying to connect to that AP too. The only playback error I see in the diagnostics now was on the Playbar, and moving the AP should fix that.

The Guest Bathroom is a bit of a puzzle. Is the speaker very close to a glass/metal/tile surface? If so, it may be interfering with itself, if you’ll excuse the expression - radio reflecting off the surface back at the speaker would be interpreted (and act) as interference.

I also noticed that every speaker can “see” 4 access points with sufficient signal strength to connect to any one of them - it may just be that you have one or two more access points than you really need, and this may be costing you reliable connections. Conceivably, not definitely.

The one thing missing from your last post is a report of things are now behaving, which is the important thing. Has it been an improvement?

I hope this helps.

 

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
BrentDAuthor
Avid Contributor I
December 28, 2023

@Corry P 

Not long after posting the edit to my last comments I watched the guest bathroom speaker interference drop to 0 as I refreshed the matrix several times. The interference at the sub also dropped to 0. The Playbar has remained orange at 6, which seems odd given its proximity to the sub that now has zero issues, but I suppose that’s due to the 2.4 vs 5 GHz you mentioned. I didn’t notice any issues yet, but I made these changes at 10pm last night and it is only now morning. Not sure where you are located, but I’m in the eastern time zone of the US. Had no issues with the rain storm sounds we play every night throughout the  night that I noticed. 
 

Here is a new diagnostic that is current. 1510097733
 

I do have 4 WiFi point in our single story home. One of them covers out doors that was added later, but the rest have been around since 2020, and the issues I had were new. If the Playbar gives me any more issues I may remove the one next to it and see how it affects our WiFi signal strength and speed. But for now with everything green other than the Playbar (which is largely used just by optical connection), I don’t foresee much issue with how it is. 
 

My only concern now is that after switching to WiFi rather than SonosNet, the controller app takes significantly more time to populate all of my speakers when opening it. We largely use our phones to control content on our TVs, so when changing to another provider or piece of content where the volume is drastically different, it makes scrambling to turn it down take a good bit longer. 

Corry P
Sonos Staff
December 28, 2023

Hi @BrentD 

I see a bit of interference on the solo speakers (except Play:3), but if there are no audible interruptions, this doesn’t concern me too much.

Playbar is still reporting transmission issues to Sub which I don’t see for the rear surrounds. This may be due to interference near the Sub, or it may be because you’ve not been playing a surround sound feed and therefore the Playbar wasn’t attempting to transmit to them. If the Sub is in close proximity to the Playbar, I recommend relocating it - the speakers can interfere with each other, after all.

My only concern now is that after switching to WiFi rather than SonosNet, the controller app takes significantly more time to populate all of my speakers when opening it. We largely use our phones to control content on our TVs, so when changing to another provider or piece of content where the volume is drastically different, it makes scrambling to turn it down take a good bit longer. 

This comes as a surprise to me. Not only does 5GHz have more bandwidth, but that bandwidth increase comes with a decrease in latency. The Sonos app, if anything, should be more responsive with your system now on 5GHz. That you see the opposite may be due to failed packet transmissions being swapped between the various APs and the main Google hub, which I would not see in the diagnostics. Please ensure that each AP is well within the range of the hub, and that each AP and the hub are separate from possible sources of interference. Routers can typically have printers, smart-home hubs or cordless telephone base units near them, so if you have any of these near (within 1m of) your main router hub, I recommend you move them away.

I don’t know how (what method) you are controlling your TV with your phones, but if you use the TV’s app and remote, does it improve the Sonos app’s responsiveness any? If so, it may be a bandwidth issue - AirPlay, for example, requires your phone to fetch the feed over the network - unless it’s a local file on the phone - and retransmit it over the network to your TV, which means the local AP is handling 3 video feed “transmits”.

I hope this helps.

 

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
BrentDAuthor
Avid Contributor I
December 28, 2023

@Corry P 

I still had the rain sounds playing through the surround setup when I took the diagnostic this morning. I have the surround setup configured to play music equally through all the speakers in that setup. I’m not terribly concerned about that setup at this point since the majority of my connection issues seem to be solved now. 
 

The slow loading of the speakers in the app occurred in the far end of my home. Once in the living room in the center of the house the speed was much improved. So it may very well be an issue with the mesh WiFi system handoff from one AP hop to the next. 
 

When I referred to controlling content from our phones, I’m really only referring to using the phone as a remote for the AppleTV box or to control the TV’s native Roku functions. We rarely use physical remotes for anything (the AppleTV’s physical remote is set up to control volume on the Playbar via IR, but is rarely used). 
 

Anyway, I appreciate all the help working through this. Seems the root issue was using the Boost instead of WiFi, and the other issues I can work through with some wireless network optimization. Thanks again. 

Corry P
Sonos Staff
December 28, 2023

Hi @BrentD 

I’m glad to hear there’s been significant improvement! And, you are most welcome!

Incidentally, now that the speakers have been scanning for WiFi (they don’t when on SonosNet), I can see that your APs are split between channels 1, 6 and 11. These are the channels you want to be using, but SonosNet was on channel 1, so it’s possible that the cause of the initial problems you reported were down to this sharing of channels. Should you ever decide to go back to using the Boost for whatever reason, I recommend that you move your Google mesh off of channel 1 beforehand. I think sticking with the current setup will be best though.

For now though, just enjoy some tunes! You’ve earned it!

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein