Answered

Please help me understand how sonos fails so i can mitigate

H

Hi All,

I’ve been fighting with my sonos speakers for about 5years now. I never seem to lose hope and each year I think I figure it out, then a few weeks go by and im back to square one.

 

This year I really thought I had it figured out by creating a dedicated network just for my speakers and then advertising a 2.4Ghz only wireless network for that network which again only my speakers connect to. That way there is no more sonosnet. There is no other interference on the network. 

 

Everything worked great for 16days and then i wake up to:

 

Here is what the speakers look like on my network when this happens(notice the “wifi” column - theyre all dropped off from a router standpoint...but in the app theyre in a state where they are connected to the wifi, but they arent responding? how?..):


So I reboot my entire network. All devices go offline. This is very disruptive, but its gotta work right?:
 

​
Nope theyre jacked up still...everything else on my other networks are connected right back up. Sonos app just shows the same screen with the gear icon and “Lets Fix it” at the top (which never works).

 

The final fix (its been over an hour now), is i have to walk around the house and unplug each speaker, wait 5mins, plug them back in...its insane. Theyre hard to get to so this isnt a sustainable solution.

 

 

TLDR:
What is happening with my speakers? How do they all just drop off a very stable unifi network, where they(speakers) have their own dedicated network and 2.4Ghz SSID? And how can i fix this next time it happens WITHOUT resetting each speaker’s power?

 

icon

Best answer by controlav 26 April 2024, 01:03

View original

10 replies

H

Thanks! I just enabled the following from How to configure your UniFi network for Sonos lets see how it goes...

  • Multicast Enhancement (IGMPv3): on
    • Settings -> Wireless Networks -> $YOUR_NETWORK
controlav
Userlevel 7
Badge +23

Its now been 15days of success, I had the system running ALL WIFI. No speakers wired. Only sonos speakers and the two iphones that control the speakers are up on this network. 

 

Today i went to the app and blammy….empty screen, “Lets fix it” popup...reboot phone...nothing...go to 2nd iphone, it shows now playing, i can add/remove now playing to all speakers for the currently playing group...but they dont play anything.

 

Ran a tcpdump on the Unifi UDM Pro to troubleshoot:

  • 0 traffic from my speaker(i chose one to tshoot with)…
  • reboot the speaker…
  • 0 TCP traffic from my speaker(yes i am sure my tcp dump is proper, i’ve confirmed it prior to my test)
  • ping speaker...pings just fine, no issues
  • go to app, take the speaker off “now playing” and put it back
  • bam, starts playing???
  • still 0 TCP traffic occurred...now im convinced i dont understand sonos, this shit is 100% for sure talking over some medium that is not on the wifi network
    • its gotta be airplay right? Does the iphone just switch the railroad tracks to airplay after i setup whats playing? 
      • just toggled “Group non-airplay products” to ON under settings in a desperate attempt to make any positive impact...idk what that does
    • or is it that my Beam (which is NOT wired) still using sonosnet to create a mesh behind my back?
      • cant be, sonosnet is greyed out in settings
  • 5mins later, speaker drops music...no tcp traffic indicating any network issue nor is there any packets related to speaker 192.168.4.153 regardless 

TLDR

These speakers dont run on your network like everyone thinks they do. Yeah there are tcp sessions where SSL is setup between some hosts in AWS from your speakers out and yeah there is SSDP traffic for discover initially, but ultimately its not constant back and forth 3-way handshakes from your speaker to the media source...i’ll need to understand whats under the hood by researching. I think peoples wifi or “network” get blamed far too much with these stupid speakers. Theyre honestly garbage. Like we’re literally talking a dedicated network and wireless network. Its essentially a sonos lab im working with. Theres no “interference” or faulty unifi settings. Its just a bad product.

 

I have only been a Uni user for a few days, but your description indicates broadcasts and/or multicasts are being blocked somewhere, which is why SSDP fails to find any speakers (which uses UDP, not TCP by the way). There are plenty of options that can do this.

 

Author of the leading independent Sonos app for Windows, the only Sonos app for Xbox, and a Sonos app for iOS
H

Its now been 15days of success, I had the system running ALL WIFI. No speakers wired. Only sonos speakers and the two iphones that control the speakers are up on this network. 

 

Today i went to the app and blammy….empty screen, “Lets fix it” popup...reboot phone...nothing...go to 2nd iphone, it shows now playing, i can add/remove now playing to all speakers for the currently playing group...but they dont play anything.

 

Ran a tcpdump on the Unifi UDM Pro to troubleshoot:

  • 0 traffic from my speaker(i chose one to tshoot with)…
  • reboot the speaker…
  • 0 TCP traffic from my speaker(yes i am sure my tcp dump is proper, i’ve confirmed it prior to my test)
  • ping speaker...pings just fine, no issues
  • go to app, take the speaker off “now playing” and put it back
  • bam, starts playing???
  • still 0 TCP traffic occurred...now im convinced i dont understand sonos, this shit is 100% for sure talking over some medium that is not on the wifi network
    • its gotta be airplay right? Does the iphone just switch the railroad tracks to airplay after i setup whats playing? 
      • just toggled “Group non-airplay products” to ON under settings in a desperate attempt to make any positive impact...idk what that does
    • or is it that my Beam (which is NOT wired) still using sonosnet to create a mesh behind my back?
      • cant be, sonosnet is greyed out in settings
  • 5mins later, speaker drops music...no tcp traffic indicating any network issue nor is there any packets related to speaker 192.168.4.153 regardless 

TLDR

These speakers dont run on your network like everyone thinks they do. Yeah there are tcp sessions where SSL is setup between some hosts in AWS from your speakers out and yeah there is SSDP traffic for discover initially, but ultimately its not constant back and forth 3-way handshakes from your speaker to the media source...i’ll need to understand whats under the hood by researching. I think peoples wifi or “network” get blamed far too much with these stupid speakers. Theyre honestly garbage. Like we’re literally talking a dedicated network and wireless network. Its essentially a sonos lab im working with. Theres no “interference” or faulty unifi settings. Its just a bad product.

controlav
Userlevel 7
Badge +23

I can’t see your pictures very well on my phone but it looks like you have a UniFi gateway and switch?

There are some STP related settings you must set in UniFi.  If you’ve already done this ignore, but if not check this out:

https://github.com/IngmarStein/unifi-sonos-doc?tab=readme-ov-file

Or follow Uni’s advice for Sonos

https://help.ui.com/hc/en-us/articles/18930473041047-Best-Practices-for-Sonos-Devices

but for the love of all things, don’t expect it to work out of the box on a Uni system.

Author of the leading independent Sonos app for Windows, the only Sonos app for Xbox, and a Sonos app for iOS
controlav
Userlevel 7
Badge +23

Tell me you’re a Uni user without telling me you’re a Uni user.

Author of the leading independent Sonos app for Windows, the only Sonos app for Xbox, and a Sonos app for iOS
buzz

UDM PRO does not support STP (unless they’ve recently made a change). The UDM PRO’s setup menu is nasty because there is an STP option to click, but this is simply setting the default for downstream UBIQUITI switches, not the UDM PRO.

H

Yep its all unifi router/switches/ap’s

Thanks @Bumper I havent seen that before. It looks like the author is calling out folks using wireless & wired at the same time? I do have one single speaker wired to the UDM Pro…i’ll look into that

@craigski  appreciate the idea not to create SSID’s and separate networks. I did that for years and it was a fine until it wasnt. It ended up being a headache as my network grew. I’ve seen the best success creating a separate broadcast domain for sonos.

@buzz thats an interesting one too. Is there perhaps some issue with my one-and-only wired “Laundry” speaker patched to my UDM pro port 4, i’ll just make it wireless?

after considering all this for a minute...

I find it really hard to believe that my one single Play:1 being wired is the main culprit to the full outage. I will put that thing back on wireless and see how long it lasts. I doubt i had that STP issue on the single Play:1 because there weren't any other wired devices on the whole network that couldve created the STP issue...i wouldve only saw the single “Laundry” speaker go down in that case.

buzz

I don’t recommend wiring SONOS units to the UDM PRO, wire them to switches.

C
Userlevel 6
Badge +11

TLDR: KISS

No need for dedicated networks for Sonos, with separate SSIDs, wireless channels, VLANS, etc. It does look like UniFi from the screenshots. I would just connect all the Sonos devices to your home 2.4/5GHz WiFi, dont plug any in to ethernet (SonosNet), and all will be good.

As soon as you try to make things more complicated, it will break, even though you may (or may not) enjoy the network problem solving/learning exercise of trying to fix a more complex setup.

Bumper
Userlevel 7
Badge +14

I can’t see your pictures very well on my phone but it looks like you have a UniFi gateway and switch?

There are some STP related settings you must set in UniFi.  If you’ve already done this ignore, but if not check this out:

https://github.com/IngmarStein/unifi-sonos-doc?tab=readme-ov-file

Reply


Terms & ConditionsCookie settings