Skip to main content
Atom P
Sonos Staff
April 8, 2026
Tutorial

Sonos + UniFi: Best Practices & Recommended Settings

  • April 8, 2026
  • 106 replies
  • 9461 views

Hello, everyone! I want to share some insights regarding Sonos setups in Ubiquiti UniFi environments. We see common questions and suggestions around how best to use Sonos with UniFi networks, and I wanted to give you the inside scoop on how we approach this troubleshooting. Unifi already has a solid guide on Sonos that we recommend checking out here, but we wanted to expand upon this.

We know that UniFi gear is incredibly popular among our power users (and many of us internally!). While Sonos is designed to work on standard home networks out of the box, managed networks like UniFi offer a level of control that can sometimes inadvertently block the communication Sonos needs to keep your system in sync.

To be clear, home networking is complex and every environment is unique. However, based on our internal documentation and successful troubleshooting sessions, here are the configurations we recommend to keep your music playing without interruption.

 

Disclaimer. This article is up to date through April 2026. Some settings might have changed since we first made this article.

June 2026 Update: The Sonos app now gives users the ability to disable SonosNet across their entire Sonos system. Take a look at ​@Liz P.’s update post for more info!

 

 

 

The "Golden Rule": Wired vs. Wireless

 

One of the most common causes of network storms/loops is a mixed environment where some Sonos players are wired and others are wireless, combined with conflicting Spanning Tree Protocol (STP) settings.

For the most stability, we generally recommend one of two approaches:

  • Fully Wireless: All Sonos products connect directly to your UniFi WiFi. 
    • This is often the easiest setup for modern Sonos products like Era 100/300, Move, and Roam.
  • Fully Wired: All capable Sonos products are Ethernet-wired.
    • WiFi is manually disabled on each player via the Sonos app.

If you are using a "Mixed" setup (some wired, some wireless using SonosNet), you must configure your STP settings correctly on your switches to avoid packet storms. (See the "Spanning Tree" section below).

 

Troubleshooting: "Missing Rooms" or Grouping Issues

 

If you are seeing speakers disappear from the Sonos app, or if you group rooms but audio only plays from one speaker, check that Multicast traffic is not being blocked or filtered and IGMP snooping is enabled.

Here are the settings we recommend checking in your UniFi Network Controller. Note: Menus may vary slightly depending on your Controller version.

  1. Check the basics: Ensure the controller (your phone) and the system are on the same subnet/VLAN.
  2. Verify the "Disable" list: Go back to the WiFi settings above and triple-check that Multicast and Broadcast Control and Multicast Enhancement are turned off. 
  3. Re-Provision: After changing these settings, allow a minute for the Access Points to re-provision. It is often helpful to reboot the Sonos players after the network settings have been applied to clear any stale connection states.

Unifi WiFi & Network Settings for Sonos

 

TL;DR: Disable Multicast Enhancement, Broadcast Control, and Client Isolation

Go to Settings > WiFi and select your WiFi name. Change Advanced Configuration to Manual to verify the following:

  • Hotspot 2.0: Set to Off. 
  • Multicast to Unicast (previously called “Multicast Enhancement”): Disabled (unchecked). Note: While this sounds like something you’d want on, it converts multicast to unicast, which can cause issues with Sonos grouping.
  • Multicast and Broadcast Control: Disabled (unchecked). This blocks multicast traffic for non-listed devices and is a common culprit for missing players.
  • Client Device Isolation: Disabled (unchecked). This prevents devices on the same AP from talking to each other.
  • Proxy ARP: Disabled (unchecked).

Global Network Settings

 

TL;DR: mDNS: Enabled, IGMP Snooping: Enabled

Go to Settings > Networks and select the network Sonos uses:

  • IGMP Snooping: Enabled. This helps reduce unnecessary multicast traffic while ensuring the right packets get to your speakers.
  • mDNS: Enabled. Technically speaking, this helps with device discovery. However, if you are running a complex setup with separate Sonos systems on different VLANs, mDNS might actually need to be disabled—but for 99% of home users, keep this ON.

Spanning Tree Protocol (STP) Settings

 

If you have any Sonos devices wired to your network (without disabling WiFi), you must configure STP on your UniFi switches to prevent network loops. Sonos uses STP (802.1d) to figure out the best path for data.

 

Global Switch Settings

 

TL;DR: STP switch priority 4096/8192/12288.

  • Spanning Tree: Select STP (not RSTP).
  • Priority: Set your core/main switch to 4096.
    • If you have secondary switches daisy-chained, set them to 8192.
    • Tertiary switches should be set to 12288.

Port Specific Settings: For the specific ports where a Sonos device is plugged in:

  • STP: Enabled
  • Edge Port: Auto or Enabled
  • BPDU Guard: Disabled
  • Root Guard: Disabled
  • Path Cost: 10
  • Port Priority: 128

Final Thoughts

 

I hope this helps clarify the best way to harmonize Sonos with UniFi gear. We know some of you have sophisticated home networks, and we want to ensure our products play nicely with them.

I'm happy to answer questions about these specific settings to the best of my ability. If you have a specific topology that defies these rules, let us know in the comments—we love seeing how you all set things up!

106 replies

Stanley_4
Grand Maestro
April 17, 2026

The brctl command output is the last entry on both my listings.

We do not have enough access to see what is actually happening versus earlier releases.

Local Superstar
April 18, 2026

The brctl command output is the last entry on both my listings.

We do not have enough access to see what is actually happening versus earlier releases.

We can what’s happening from the support pages/network matrix that we have always had access to, ie we can see network paths (or lack of, with modern players)

In addition, if you have UniFi Network App, you have greater visibility, eg network topology, showing STP, roaming between APs and 2.4GHz/5GHz, data flow/rate, packet capture, etc.

What is it that you think is happening that you can’t see?

Stanley_4
Grand Maestro
April 18, 2026

What happens internally when a Wi-Fi connected device has an Ethernet cable attached.

Local Superstar
April 19, 2026

What happens internally when a Wi-Fi connected device has an Ethernet cable attached.

The internal network stack will use the physical Ethernet connection that is connected to your network, via the bridge adapter to keep the network address consistent?

Think of the non SonosNet devices listed above in my link to Sonos, as ‘client’ devices on your network, where as the older devices capable of SonosNet as ‘node’ devices, capable of creating/joining a private mesh network, and forwarding packets to other nodes. Hence potential issues with incorrectly configured STP.

I assume by not running SonosNet on a devices (listen to all packets 24/7, and potentially forward them to other nodes) will reduce resource on the devices (cpu, memory, etc) and also power consumption.

The Ninth
Collaborator I
April 25, 2026

I am also facing issues with Sonos and UniFi.

My Sonos Amp disappears from the network a few hours after every reboot. It is not only gone from the Sonos controller, but becomes completely unreachable:

  • no response to ping
  • no response to ARP requests

At the same time, the physical link indicator on the switch still shows an active connection.

Setup:

  • Ubiquiti UniFi network system
  • All Sonos devices are wired to an USW 24 PoE, which is connected to an UDM Pro.
  • Devices: 2× Sonos One, 1× Era, 1× Amp
  • WiFi disabled on the Ones and the Amp
  • For the Era (where WiFi cannot be disabled), I blocked WiFi access and UniFi shows it connected via Ethernet

I have already tried the commonly recommended settings mentioned here, but without success.

Question:
Is this behavior, where the Amp becomes completely unreachable on the network, something that can still be caused by UniFi configuration? Or does this point more towards a device issue?

To me, it looks like the device stops responding at a very low level, possibly a crash of its network stack.

Local Superstar
April 25, 2026

Question:
Is this behavior, where the Amp becomes completely unreachable on the network, something that can still be caused by UniFi configuration? Or does this point more towards a device issue?

To me, it looks like the device stops responding at a very low level, possibly a crash of its network stack.

What switch and version?

https://community.ui.com/releases/UniFi-Switch-7-4-1/6d6aed12-f95d-4ca9-affa-4f1bf3954208

Bugfixes

 

 

STP & Stability

All Models

  • Fixed false STP blocked anomalies when a port links up or when STP is disabled on a port.

Sounds to me as if the switch is blocking the port. When it happens again, don’t restart Amp. Disable/Enable port on Switch, see if it clears. If you can try restarting switch, rather than Amp.

If you have invested in a Wi-Fi solution for your house, and only 4 Sonos devices, use Wi-Fi. There are many users using just Wi-Fi with many more Sonos devices.

Local Superstar
April 25, 2026

Interestingly, I already followed the same steps based on the same documentation when I had trouble adding the AMP to my system. Back then it did not help, for adding the AMP only switching it to wireless worked.

 

Déjà vu?

The Ninth
Collaborator I
April 25, 2026

What switch and version?.

The USW 24 PoE, and it already runs on 7.4.1.

 

Sounds to me as if the switch is blocking the port. When it happens again, don’t restart Amp. Disable/Enable port on Switch, see if it clears. If you can try restarting switch, rather than Amp.

Just tried this, but it did not help, the Amp is not coming back when I disable the port and then enable it again.

 

If you have invested in a Wi-Fi solution for your house, and only 4 Sonos devices, use Wi-Fi. There are many users using just Wi-Fi with many more Sonos devices.

I tried to switch the Amp to WiFi and the problem stayed the same. Do you think if I switch all the other devices to WiFi it would go away?

 

Déjà vu?

Yes, already when I setup the system initially I run into some troubles. In the end it worked, even with the wired Amp. However now it doesn’t, maybe some Unifi update broke it. It is our holiday home, we have not been there that much over the past year, and I am not entirely sure at which point it broke.

 

Local Superstar
April 25, 2026

 

If you have invested in a Wi-Fi solution for your house, and only 4 Sonos devices, use Wi-Fi. There are many users using just Wi-Fi with many more Sonos devices.

I tried to switch the Amp to WiFi and the problem stayed the same. Do you think if I switch all the other devices to WiFi it would go away?

Yes, no need to wire Sonos in 2026, unless a high density rack solution. Spend you time listening to Music, rather than managing Ethernet ports, STP loops, etc 😀 That's what you did two years ago to fix the problem?

The Ninth
Collaborator I
April 26, 2026

I have now reset all UniFi settings to their defaults and started from scratch, following the recommendations from the original post in this thread.

Unfortunately, this did not help. My Sonos Amp still disappears after about one to two hours after every reboot.

I was also not able to find all of the options mentioned there in my setup. This may be due to differences in hardware or changes in the UniFi software. For example, I cannot find a direct mDNS setting for the network. Instead, there is only a “Gateway mDNS Proxy” option with Auto, Off, or Custom.

In any case, I am no t sure this is primarily a discovery issue.

In my tests, I am not even using a controller. I simply reboot the Amp and leave it idle. After about one to two hours, it becomes unreachable without any interaction with it or any other Sonos device. I am monitoring this via periodic pings, and once the issue occurs, the device no longer responds to ping at all.

Question:
If no controller is active and all Sonos devices are idle, is there still background communication between them that could potentially trigger this behavior?