Skip to main content
Tutorial

Sonos + UniFi: Best Practices & Recommended Settings

  • April 8, 2026
  • 39 replies
  • 1274 views

Show first post

39 replies

Stanley_4
  • Grand Maestro
  • April 16, 2026

Dug out my looong Ethernet cable and hooked up my Arc Ultra, looked like it did a quick restart once the cable was inserted.

Before Ethernet:

running /sbin/ifconfig

ath0 Link encap:Ethernet HWaddr C4:38:xxx  

          inet6 addr: fe80::c638:75ff:fe16:2e47/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:636036 errors:0 dropped:0 overruns:0 frame:0

          TX packets:266366 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:3000 

          RX bytes:134895628 (128.6 MiB) TX bytes:57859403 (55.1 MiB)

 

ath1 Link encap:Ethernet HWaddr C4:38:xxx  

          inet6 addr: fe80::c638:75ff:fe16:2e49/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:1641178 errors:0 dropped:2 overruns:0 frame:0

          TX packets:4104789 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:209143564 (199.4 MiB) TX bytes:909762340 (867.6 MiB)

 

br0 Link encap:Ethernet HWaddr C4:38:xxx 

          inet addr:172.16.1.130 Bcast:172.16.3.255 Mask:255.255.252.0

          inet6 addr: fe80::c638:75ff:fe16:2e47/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:1209504 errors:0 dropped:87106 overruns:0 frame:0

          TX packets:725844 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:189360453 (180.5 MiB) TX bytes:92183575 (87.9 MiB)

 

eth0 Link encap:Ethernet HWaddr C4:38:xxx  

          UP BROADCAST MULTICAST MTU:1500 Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

          Interrupt:15 

 

lo Link encap:Local Loopback  

          inet addr:127.0.0.1 Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING MTU:65536 Metric:1

          RX packets:527 errors:0 dropped:0 overruns:0 frame:0

          TX packets:527 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:52008 (50.7 KiB) TX bytes:52008 (50.7 KiB)

 

 

/usr/sbin/brctl showstp br0

running /usr/sbin/brctl showstp br0

br0

 STP is disabled for this interface

 

After Ethernet:

running /sbin/ifconfig

ath0 Link encap:Ethernet HWaddr C4:38:xxx  

          inet6 addr: fe80::c638:75ff:fe16:2e47/64 Scope:Link

          UP BROADCAST MULTICAST MTU:1500 Metric:1

          RX packets:637501 errors:0 dropped:0 overruns:0 frame:0

          TX packets:267442 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:3000 

          RX bytes:135129955 (128.8 MiB) TX bytes:58196377 (55.5 MiB)

 

ath1 Link encap:Ethernet HWaddr C4:38:xxx  

          inet6 addr: fe80::c638:75ff:fe16:2e49/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:1649028 errors:0 dropped:3 overruns:0 frame:0

          TX packets:4116697 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:210669808 (200.9 MiB) TX bytes:912280243 (870.0 MiB)

 

br0 Link encap:Ethernet HWaddr C4:38:xxx  

          inet addr:172.16.1.130 Bcast:172.16.3.255 Mask:255.255.252.0

          inet6 addr: fe80::c638:75ff:fe16:2e47/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:3000 errors:0 dropped:35 overruns:0 frame:0

          TX packets:2956 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:780394 (762.1 KiB) TX bytes:1018695 (994.8 KiB)

 

eth0 Link encap:Ethernet HWaddr C4:38:xxx  

          inet6 addr: fe80::c638:75ff:fe16:2e47/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:2396 errors:0 dropped:0 overruns:0 frame:0

          TX packets:2389 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:756120 (738.3 KiB) TX bytes:1011972 (988.2 KiB)

          Interrupt:15 

 

lo Link encap:Local Loopback  

          inet addr:127.0.0.1 Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING MTU:65536 Metric:1

          RX packets:598 errors:0 dropped:0 overruns:0 frame:0

          TX packets:598 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:70298 (68.6 KiB) TX bytes:70298 (68.6 KiB)

 

 

/usr/sbin/brctl showstp br0

running /usr/sbin/brctl showstp br0

br0

 STP is disabled for this interface

Either way it does look like STP is disabled, Sonos must be doing something other than STP to prevent network looping. Might well have been easier than trying to move the core Linux kernel code forward to RSTP.

 

Edit: Pulled the Ethernet and 30 seconds later got a reboot LED pattern, the reboot seemed to go faster than a power/update reboot. Interesting stuff, sure wish we could see the internals, even if only the open-source stuff.


Forum|alt.badge.img+18
  • Local Superstar
  • April 17, 2026

Either way it does look like STP is disabled, Sonos must be doing something other than STP to prevent network looping.

If there are no additional network paths, there is no requirement for loop detection.


controlav
Forum|alt.badge.img+24
  • Lead Maestro
  • April 17, 2026

All five of my Sonos systems are mixed wireless & wired on Ubiquiti, and I have never needed to mess with STP.

Curious, what UniFi switch(es) are you using? Maybe STP is disabled.

I have a UDR 7 + USW Lite 8 in one location, and a UCG Ultra + USW Flex Mini in the other.


Stanley_4
  • Grand Maestro
  • April 17, 2026

Either way it does look like STP is disabled, Sonos must be doing something other than STP to prevent network looping.

If there are no additional network paths, there is no requirement for loop detection.

True but the Arc Ultra in the second example had two paths available, Wi-Fi and Ethernet. 


Forum|alt.badge.img+18
  • Local Superstar
  • April 17, 2026

Either way it does look like STP is disabled, Sonos must be doing something other than STP to prevent network looping.

If there are no additional network paths, there is no requirement for loop detection.

True but the Arc Ultra in the second example had two paths available, Wi-Fi and Ethernet. 

The Arc Ultra has 3 physical network interfaces, 2x WiFi, and 1x Ethernet. The ‘ifconfig’ command is not showing any network paths, just displaying the interfaces on the Arc Ultra. I recall the network matrix/brctl command will show paths, if SonosNet is enabled on older devices.


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.


Forum|alt.badge.img+18
  • 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.


Forum|alt.badge.img+18
  • 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
Forum|alt.badge.img+3
  • 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.


Forum|alt.badge.img+18
  • 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.


Forum|alt.badge.img+18
  • 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
Forum|alt.badge.img+3
  • 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.

 


Forum|alt.badge.img+18
  • 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?