Skip to main content
Answered

Strong wifi speakers cut in/out

  • January 5, 2025
  • 8 replies
  • 182 views
K

Hi - I know this has been asked and answered in many different ways and forums, I have tried many of those solutions but still have instances where speakers drop in/out. I have not been able to pinpoint any specific event that may drive this.

My wifi is strong, I have a mesh network, a few of the speakers connect to the 5Hz but most to the 2.4Hz network. When things get really, really bad I unplug all speakers (16) and reboot my router and mesh, then plug them all back in. This seems to work with some lags.

The issue has been persistent since the new app, I have changed my router (from stock xfinity to a Synology Mesh) and seen no difference. My Arc was hard wired, so SonosNet which I have since taken on wifi and away from SonosNet, there is some perceived stability after this (maybe?).

I have been thinking of creating a separate Sonos only 2.4Hz network for all the speakers to test, does this make sense? It will be a bit annoying since my mobile will have to use the 2.4Hz or I will have to switch networks to use the system.

I have a lot of traffic in a connected home, ~50 devices but there is plenty of bandwidth and all other devices work flawlessly.

This is part rant and part desperate plea to solicit other ideas I can try. Still boggles the mind how much damage was created to a system that worked so well by the new app though I understand it is a more secure system now.

Thanks much!

Best answer by Airgetlam

In general, it sounds like you’ve done a lot of things to assist, but I’m not a fan of setting up a ‘separate’ 2.4 GHz network for your Sonos, as the controller(s) would need to be on the same subnet, and effectively, you’ve already tried that when you set up SonosNet, which doesn’t have that same restriction, since the Sonos actually thinks it is wired and on the same subnet. 

The ‘other devices work flawlessly’ always seems like a cop-out to me, as almost all other devices don’t tax the network in the same way as Sonos does. Sonos has to maintain more than three different connections (your controller, the internet stream for the music, and all other Sonos devices), something most other devices don’t. They tend to either maintain a connection to your computer, or, in more rare cases, a connection to the outside world. 

The two things that struck me when reading your post were this: I didn’t see anything about assigning reserved IP addresses for your Sonos in your router’s DHCP table, something that has helped me significantly in the past, along with many other folks. Nor did I see anything mention of potential wifi interference , especially from the outside of your network. I’ve had two separate experiences there, one from a microwave that was going bad, and spewing RF interference, and once from a neighbor, who’s new router ended up stomping all over the channel I was using for my Sonos’ connection. In both cases, it took me several days to figure it all out, in retrospect it seems much easier, and I shouldn’t have been so slow. But I’d certainly tend to stick with a 2.4 GHz signal, if possible. It carries a bit further, and also permeates better than a 5Ghz signal. That being said, I do have a Roam that is on my 5Ghz signal, but it’s in range of my router. The rest of my Sonos speakers are connected via SonosNet, on a Sonos BOOST. 

Another note, having just reread your post, is that it’s not clear that you unplugged your speakers when you changed routers, in which case they would have held on to the same (potentially bad) IP addresses. You should always reboot your entire network, when changing a router. 

But, if none of my suggestions above help you, I would recommend that you submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it. But don’t post the resulting diagnostic number here, they get sensitive about GDPR.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

When you speak directly to the Support staff, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

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.

8 replies

Airgetlam
  • Airgetlam
  • Answer
  • January 6, 2025

In general, it sounds like you’ve done a lot of things to assist, but I’m not a fan of setting up a ‘separate’ 2.4 GHz network for your Sonos, as the controller(s) would need to be on the same subnet, and effectively, you’ve already tried that when you set up SonosNet, which doesn’t have that same restriction, since the Sonos actually thinks it is wired and on the same subnet. 

The ‘other devices work flawlessly’ always seems like a cop-out to me, as almost all other devices don’t tax the network in the same way as Sonos does. Sonos has to maintain more than three different connections (your controller, the internet stream for the music, and all other Sonos devices), something most other devices don’t. They tend to either maintain a connection to your computer, or, in more rare cases, a connection to the outside world. 

The two things that struck me when reading your post were this: I didn’t see anything about assigning reserved IP addresses for your Sonos in your router’s DHCP table, something that has helped me significantly in the past, along with many other folks. Nor did I see anything mention of potential wifi interference , especially from the outside of your network. I’ve had two separate experiences there, one from a microwave that was going bad, and spewing RF interference, and once from a neighbor, who’s new router ended up stomping all over the channel I was using for my Sonos’ connection. In both cases, it took me several days to figure it all out, in retrospect it seems much easier, and I shouldn’t have been so slow. But I’d certainly tend to stick with a 2.4 GHz signal, if possible. It carries a bit further, and also permeates better than a 5Ghz signal. That being said, I do have a Roam that is on my 5Ghz signal, but it’s in range of my router. The rest of my Sonos speakers are connected via SonosNet, on a Sonos BOOST. 

Another note, having just reread your post, is that it’s not clear that you unplugged your speakers when you changed routers, in which case they would have held on to the same (potentially bad) IP addresses. You should always reboot your entire network, when changing a router. 

But, if none of my suggestions above help you, I would recommend that you submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it. But don’t post the resulting diagnostic number here, they get sensitive about GDPR.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

When you speak directly to the Support staff, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

Bruce
Stanley_4
  • Stanley_4
  • Lead Maestro
  • January 6, 2025

First thing I’d do is unwire the Arc so you weren’t split between Sonosnet and WiFi.

Once on WiFi look at the signal strength at each speaker in the App to confirm the WiFi is strong for them.

If you have auto channel switching enabled on the router lock each band to a single channel.

Are any Sonos hunting between bands? Your router may be able to tell them to stay on one, likely 2.4 would be best.

If the reboot solves the issue it might be an IP related glitch. You can eliminate that as a possibility by assigning all Sonos a static/reserved IP from the router’s DHCP page. Do another reboot cycle to lock in the new addresses.

K
  • keyspd.vgqnd
  • Author
  • Contributor I
  • January 6, 2025

​@Airgetlam and ​@Stanley_4 Thanks for the thoughtful response. I did do a proper reboot across the system when I got eh new router in; I vaguely recall having static IPs under my old xfinity router which didn’t seem to fix things. I will give it another go with the new router. I will also trying locking in the bands and will report back as an FYI. I’ll also need to google how to determine if there is wifi interference, something I have been trying to avoid, lol! Thanks!

Airgetlam
  • Airgetlam
  • January 6, 2025

Good luck, I’ve never found a great way (that’s not an expensive tool) other than trial and error…and discovery. It’s only in the absence of it that I feel better about it.

Bruce
Stanley_4
  • Stanley_4
  • Lead Maestro
  • January 6, 2025

Cheapest “tool” I’ve found is to get a Ubiquity Access Point that includes an RF analyzer function. Not cheap and not all that casual/occasional user friendly.

 

    Airgetlam
    • Airgetlam
    • January 6, 2025

    I don’t happen to use Ubiquity, I’ve found their tools to have too many options for the average user, and plain confusing to most. Excellent for the advanced user, too opaque for the average user.
     

    Unfortunately, it seems that a lot of folks think their skills/understanding are greater than they are. Probably why we get so many Ubiquity based questions here on these forums. On the other hand, my perception could be based on sour grapes. 

    Bruce
    Stanley_4
    • Stanley_4
    • Lead Maestro
    • January 6, 2025

    I think you are right about Ubiquity in general, excellent for the professional that is in them every day dealing with issues, not so good for the home user.

    The Access Points are complex, but nowhere near as complex as the routers and switches. Not basic by any means, but someone willing to learn the system will find them usable.

    My decision was driven by wanting a true RF based WiFi spectrum analyzer and not wanting to spend over a thousand dollars on one.

    https://www.amazon.com/NetAlly-AIRCHECK-Display-Operating-Temperature/dp/B003JZ076U

      K
      • keyspd.vgqnd
      • Author
      • Contributor I
      • January 13, 2025

      ​@Airgetlam ​@Stanley_4 Just a quick update; had some stability for a few days after the static IPs but I think it was more due to a full reboot of all speakers and router + mesh. Today speakers started playing up again, 4 showed like they were playing on the app but weren’t really. Another one had the volume not staying as changed. Have not looked too much into wifi interference yet. The only “busy” area is where I have my Arc, which has an Apple TV, and a Shade Store hub. My NAS and Samsung SmartThings Hub are hard wired but close to the Arc. I think my next step is to move some of those devices away from the Arc. Let me know if you think of anything else to experiment with. Thanks!

      Terms & ConditionsCookie settingsAccessibility statement