From SonosNet to home theater: one user's Wi-Fi tinkering journey
- An Unexpected Encounter
My introduction to Sonos was, in fact, a complete accident.
Last year, while browsing IKEA, I happened to notice the SYMFONISK wall-mounted speakers. Compared with traditional speakers, they look more like home decor—they blend naturally into a room without requiring dedicated space for audio equipment. I was drawn to the design almost immediately, and after much deliberation, I finally bought one and brought it home.
What surprised me most, though, was the sound. I had bought it purely for its looks, but the audio quality far exceeded my expectations—and that's what got me interested in Sonos as a brand.
As it happened, the IKEA–Sonos partnership was coming to an end around that time, and the SYMFONISK line was being cleared out. Not wanting to miss out on these uniquely designed products, I took advantage of a domestic IKEA sale and bought quite a few SYMFONISK speakers from China. Before long, the number of Sonos devices at home kept growing, gradually forming a speaker system covering multiple rooms.
One of them, a SYMFONISK bookshelf speaker, happened to sit right next to my router. Since Sonos provides an Ethernet port, I casually plugged in a network cable.
That seemingly ordinary move unexpectedly changed the entire network architecture of my Sonos system.
After connecting the cable, Sonos automatically enabled its proprietary wireless network—SonosNet. By design, it should make connections between speakers more stable and reduce reliance on the home Wi-Fi. What I actually experienced, however, was the exact opposite: devices that had been running fine began to slow down. After pressing play, I often had to wait a long time for a response; if I selected speakers in multiple rooms to play simultaneously, a few would invariably fail to join the playback group. The overall experience was even less smooth than when everything ran on ordinary Wi-Fi.
This left me puzzled. Why would connecting one speaker to Ethernet make the wireless connection worse?
And it was from this question that I gradually discovered that Sonos's wireless networking is far more complex than I had originally imagined.
- SonosNet: A Once-Advanced Design
To understand this problem, you first need to know what SonosNet is.
SonosNet is a proprietary wireless mesh network that Sonos designed for its own speakers. As long as one SonosNet-capable speaker is connected to the router, it can automatically establish a 2.4GHz wireless network independent of the home Wi-Fi. Other compatible Sonos speakers can then connect to each other through this network, and even relay signals through one another, without needing to connect directly to the home wireless router.
From a design standpoint, this is actually a very clever solution.
When SonosNet was born, home Wi-Fi was nowhere near as reliable as it is today. Wireless routers had limited coverage, performance problems arose when multiple devices connected at once, and few households had a well-built multi-AP network. For Sonos, which needs to play music in sync across different rooms, building a dedicated wireless network for its speakers made more sense than relying on home Wi-Fi of varying quality.
This improved coverage and gave Sonos more control over communication between devices. At the time, it was genuinely an appealing design.
But the thing is, the home network environment has changed a great deal.
Today, multi-AP setups, mesh Wi-Fi, and even whole-home wired backhaul are no longer rare. Modern routers also have more mature wireless management capabilities. Meanwhile, the 2.4GHz band is becoming increasingly crowded: besides traditional Wi-Fi, there are large numbers of smart home devices using Zigbee, Thread, and various other wireless devices.
Although SonosNet is independent of home Wi-Fi, it does not have its own wireless spectrum. It still occupies the same 2.4GHz space. Especially under the 20MHz channel planning commonly used in the US, 2.4GHz has only three main non-overlapping channels: 1, 6, and 11. An extra proprietary network does not mean extra wireless capacity—it may instead increase competition with existing networks.
What's more troublesome is that SonosNet also complicates the home network topology.
Because it supports both Ethernet connections and wireless mesh communication between speakers, when multiple Sonos devices are connected to the wired network at the same time, multiple interconnected paths can form. SonosNet itself uses Spanning Tree Protocol (STP) to avoid network loops, but under some switch configurations, the STP behavior of two sets of network devices can conflict—causing port blocking in mild cases, or affecting the stability of the entire LAN in severe cases.
Moreover, SonosNet cannot guarantee that all devices have equally good network paths. Although mesh can forward data through multiple speakers, actual performance still depends on speaker placement, wireless signal quality, and the distribution of wired exits. When multiple devices need to communicate with the home network through a few nodes, those nodes and links can become bottlenecks.
Looking back at my own experience, this also made me suspect why Sonos, which performed normally on ordinary Wi-Fi, would develop problems with control and multi-room playback once SonosNet was enabled. Especially when selecting multiple speakers to play at the same time, the independent network meant to improve reliability did not seem to deliver the expected benefits.
Of course, this does not mean SonosNet performs poorly in every home. If the home Wi-Fi coverage is poor, or some speakers are too far from the router, a proprietary network that can relay through speakers may still be more stable than ordinary Wi-Fi.
But for households that already have good wireless coverage, SonosNet's advantages are no longer so obvious, while the extra spectrum usage and network complexity it brings remain.
In fact, Sonos itself is gradually reducing its reliance on SonosNet. Newer products such as the Era 100, Era 300, and Arc Ultra no longer support connecting via SonosNet, instead using home Wi-Fi directly or supported wired connections. Sonos has also added a setting in its app to turn SonosNet off independently, allowing users to keep some speakers wired while letting other devices continue using home Wi-Fi.
This ultimately led me to decide not to let SonosNet participate in my home network.
However, I later discovered that even with SonosNet turned off, Sonos does not necessarily stop building its own wireless network.
Because for home theater systems, Sonos has another wireless connection mechanism that is not so easy to notice.
- Home Theater: Another Overlooked Wireless Network
Originally I thought that as long as SonosNet was turned off and all devices returned to home Wi-Fi, the problem should be solved. But as the number of Sonos speakers at home grew, I gradually discovered that Sonos actually has another relatively independent wireless network—and it may be even less noticeable to users than SonosNet.
This network comes from Sonos's home theater system.
When a Sonos soundbar is combined with two surround speakers and one or more Subs to form a home theater, these devices typically do not each connect to the home wireless router like ordinary Sonos speakers. Instead, the soundbar acts as a wireless access point, establishing a private wireless connection dedicated to the home theater, so that the surround speakers and subwoofer communicate directly with it.
This design also has its rationale.
Home theater is different from ordinary multi-room music playback. Multi-room music can rely on buffering to ensure synchronization, but TV audio needs the lowest possible latency, otherwise noticeable audio-video desync occurs. Having surround speakers communicate directly with the soundbar reduces reliance on the home network and makes it easier for Sonos to control synchronization between channels.
To this end, Sonos uses a wireless mechanism different from SonosNet. In some traditional home theater products, surround speakers and Subs return to a 2.4GHz connection after being idle for a while, and switch to a dedicated 5GHz wireless connection when playback begins, to meet audio transmission requirements.
At first glance, this also seems like a reasonable design. But when a home has multiple home theater setups and more and more smart devices using 2.4GHz, problems begin to appear.
First, this means Sonos may maintain its own wireless connection on the 2.4GHz band even when nothing is playing. Although standby communication itself may not generate much traffic, it still needs to share the limited wireless spectrum with home Wi-Fi, Zigbee, Thread, and other devices. For an already very crowded 2.4GHz environment, this is clearly not another wireless system I want to add.
Second, the band switching between standby and playback also means devices need to go through changes in wireless connection state. In my own use, sometimes the surround speakers did not produce sound immediately in the first few seconds after playback started. I suspect this is related to the wireless link recovering from a power-saving state. Although I cannot determine the cause from this phenomenon alone, a design that requires repeatedly switching connection states at least introduces an additional potential point of failure.
What troubled me even more was that this network is almost entirely outside the control of the home router.
The soundbar chooses the channel used by the private wireless link on its own, and Sonos does not provide a convenient user setting to directly specify the 5GHz channel used by the home theater.
This means that even if I have carefully planned the channels, bandwidth, and transmit power of the whole-home APs, Sonos may still use another wireless link in the same space that I cannot control. It may compete for spectrum with nearby Wi-Fi networks, and it cannot directly take advantage of the home network's existing channel planning and wireless management mechanisms.
And this automatic channel selection design has an even more hidden problem: compatibility of devices from different sales regions.
Different countries and regions have different regulations for 5GHz Wi-Fi. Some channels can be used in the US but may be restricted in other countries, and vice versa. Ordinary Wi-Fi devices usually determine which channels they can use based on their own regional configuration, but when Sonos devices from different markets form a home theater, the problem becomes complicated.
Some of my surround speakers were purchased in China, while the soundbar is a US version. Since there are quite a few 5GHz channels commonly available in both China and the US, most of the time they work fine. But occasionally the surround speakers suddenly produce no sound.
I later learned that mixing devices from different regions such as China and Japan, or the US and Europe, can cause more obvious compatibility problems. In particular, when the soundbar selects a channel not supported in the region of the surround speakers, the devices may pair successfully but still fail to establish an audio connection properly.
What's more troublesome is that it is very difficult for users to intervene in this process. If the problem indeed comes from channel selection, sometimes the only option is to try restarting the soundbar so it re-establishes the wireless connection and tries to reselect a channel—but this does not necessarily completely solve the regional compatibility problem.
In the official Sonos community, you can also find staff confirming cross-region surround compatibility issues. This is not just speculation by individual users, but a real limitation brought about by wireless spectrum regulations in different regions.
Of course, a private wireless link is not necessarily worse than home Wi-Fi. For households using ordinary routers with imperfect wireless coverage, having the soundbar communicate directly with surround speakers may still be a simpler and more reliable solution.
But for me, the situation is different.
My home has multiple APs, and the entire wireless network has already undergone channel planning and coverage optimization. I not only want Sonos to play stably, but also want to know where each device is connected, what band it uses, and where to start troubleshooting when network problems occur.
SonosNet at least provides an independent switch that can be turned off directly. But the private wireless network used by home theater is hidden deeper. Even if I have turned off SonosNet, it still continues to exist.
This made me start thinking about another question:
Since modern home Wi-Fi can already provide stable 5GHz coverage, why must surround speakers communicate through a proprietary network established by the soundbar? Can the entire home theater also use the existing home network directly?
Later I found that, at least with my combination of devices, this is indeed possible.
- Returning Network Control to Home Wi-Fi
Since SonosNet can be turned off, can the home theater's proprietary wireless network also be turned off?
At first, I thought the answer was no.
Although the Sonos app provides an option to turn off Wi-Fi, for a soundbar already configured with surround speakers, this option is effectively unusable. Even if the soundbar is connected via Ethernet, Sonos still requires Wi-Fi to remain on so it can communicate with the surround speakers and Sub. According to the official setup logic, the home theater's wireless connection seems indispensable.
However, from a networking principle standpoint, I did not think this must be an insurmountable limitation.
Since Sonos speakers themselves can communicate over ordinary home Wi-Fi, and the various devices in a home theater ultimately need to connect to the same LAN, then in theory, as long as the network quality is good enough, surround audio should also be able to travel over the home network, rather than necessarily going through a wireless hotspot built by the soundbar itself.
So I ran an experiment.
First, in the Sonos app, I unbound the soundbar from all surround speakers and Subs, making them independent devices again. Then I connected the soundbar to the home network via Ethernet and turned off its Wi-Fi in the settings.
Next, I tried adding the previous surround speakers and Sub back to the home theater.
Something interesting happened.
During the re-pairing process, the Sonos app prompts that the soundbar's Wi-Fi must be enabled. According to the normal setup flow, users seem to have no choice but to accept this requirement. But I found that even if you dismiss this prompt, the pairing process can still continue, and it can ultimately complete successfully.
More importantly, after pairing, the surround speakers and Sub did not reconnect to the soundbar's private wireless network, but instead connected to the LAN through the home APs. The soundbar communicated with them via Ethernet, and the entire home theater still played normally.
In other words, with my combination of devices, a Sonos home theater can indeed run without relying on the soundbar's self-built wireless hotspot.
This is not Sonos's officially recommended standard configuration, nor does it mean all models and firmware versions can necessarily reproduce it. But for me, it proved something important: at least under certain conditions, a proprietary wireless link between the soundbar and surround speakers is not necessarily required.
Of course, this approach is not without cost.
Originally Sonos could directly manage the connection between the soundbar and surround speakers; now all audio must go through the home network. The performance of the wireless APs, channel congestion, device roaming, and the stability of the LAN itself will all begin to affect home theater performance.
Especially for multi-channel home theater, a stable low-latency connection is far more important than raw speed test results. Even if Wi-Fi's theoretical bandwidth is high, that does not mean it can reliably transmit real-time audio under various loads.
However, in my own network environment, this is not an impossible requirement.
My home already has multiple UniFi APs deployed, providing fairly stable 5GHz coverage for different rooms. I can also adjust channel width and transmit power according to actual conditions, and assign Sonos devices to suitable APs. Rather than letting the soundbar choose a completely uncontrollable dedicated channel on its own, I would rather hand these connections over to the existing wireless network management.
But a new problem appeared.
To turn off the soundbar's Wi-Fi, Sonos requires it to have an Ethernet connection. For a soundbar that happens to sit next to a network jack, this is of course easy. But most homes do not have network cables pre-installed next to every TV, and mine is no exception.
Since direct wiring is not possible, can a wireless bridge be used to make the soundbar think it is connected via Ethernet while actually accessing the network through home Wi-Fi?
I tried several different approaches.
One was to use a Mac mini, connecting to the home AP over wireless and then passing the network connection through to the soundbar. This worked stably in my tests, and it proved that the idea of using wireless-to-wired conversion to replace physical cabling is feasible.
But obviously, keeping a Mac mini running long-term just for one soundbar is not a particularly economical solution.
Later, I thought of an Apple product that had been discontinued for years: the AirPort Express.
The AirPort Express was originally a small wireless router Apple introduced, but it also has a very practical feature: it can connect to an existing Wi-Fi network and then provide network connectivity to wired devices through its Ethernet port.
More interestingly, it supports a mechanism called ProxySTA.
Ordinary wireless clients cannot directly forward the MAC addresses of multiple downstream devices like a true transparent Ethernet bridge. ProxySTA, however, can proxy the wireless access of wired devices, allowing the upstream network to still identify and manage these downstream devices without putting them into an additional NAT subnet.
This is exactly suitable for Sonos, which wants to preserve LAN device discovery and management capabilities.
I bought several used AirPort Express units for testing. They were already quite cheap, and once configured, they did not require maintaining a complex set of network services. For the scenario of simply providing a wireless-to-wired connection for one soundbar, it is almost an ideal solution.
However, the AirPort Express is, after all, a very old product. The second-generation model only supports 802.11n, and its Ethernet port is only 100Mbps. Although these specs do not necessarily pose a problem for ordinary audio transmission, its wireless processing capability and concurrency performance are clearly no match for modern network equipment.
In my tests, for a standard home theater configuration of two surround speakers plus one Sub, the AirPort Express's performance was completely sufficient, and playback was quite stable.
But I also tried using a third-party tool called SonoSequencr to add front speakers to the home theater. This configuration goes beyond the conventional layout of Sonos's native home theater and places higher demands on the network. In this case, the limitations of the AirPort Express began to show.
Especially in the living room configuration, I once encountered brief stuttering in TV audio. By comparison, the Mac mini bridge performed more stably for the same purpose.
Therefore, I am still very willing to recommend the AirPort Express. For an ordinary two-surround-plus-one-Sub home theater, it is a very low-cost, easy-to-configure wireless bridging solution, and its actual performance is not bad.
What really makes me hesitant is its long-term prospects.
After all, the AirPort Express has been discontinued for years, and its wireless specs and processing capability are stuck in the past. Although it is currently sufficient for standard home theater needs, as future devices, audio features, and home network environments evolve, it may not always be up to the task. Rather than saying its current performance is insufficient, it is more accurate to say it can hardly provide the expansion room and long-term assurance that modern network equipment should offer.
Unfortunately, so far I have not found a modern product that is equally cheap, convenient, and able to well replace the AirPort Express's bridging mechanism. If a small wireless bridge device supporting a new generation of Wi-Fi and featuring something like ProxySTA becomes available in the future, I would be very willing to try it.
Looking back at the whole process, I do not actually think Sonos's private wireless connections are necessarily bad. For users with average home Wi-Fi coverage, they can indeed save a lot of trouble in configuration and network troubleshooting.
But when the home network is already sufficiently mature, I would rather have all devices use the same network infrastructure, instead of each brand building its own independent wireless system.
This may not bring every device's performance to its theoretical maximum, but it allows me to plan spectrum uniformly, observe device connection status, and truly know where to start troubleshooting when problems occur.
For me, this is more valuable than a fully automatic proprietary network that is almost impossible to intervene in.
- Conclusion
After all this tinkering, I still really like Sonos.
From initially being drawn in by the SYMFONISK design to gradually building a speaker system covering multiple rooms, Sonos still satisfies me in many ways when it comes to product design, sound quality, and the multi-room audio experience.
I also do not think SonosNet or the home theater's private wireless network were wrong designs from the start. On the contrary, they once solved the problem of unreliable home Wi-Fi very well, allowing ordinary users to enjoy stable multi-room audio without needing to understand complex networking.
It's just that as home networks continue to evolve, the assumptions these designs rely on are also changing. Today, a well-planned home Wi-Fi can already handle many tasks that once required a proprietary network. For such an environment, continuing to maintain multiple independent, hard-to-manage wireless systems may not still be the best choice.
Of course, my approach may not suit everyone. It requires sufficiently good wireless coverage and relatively mature network management capabilities, and some of the operations are not officially supported Sonos configurations. But at least for me, after handing connectivity back to the home network, the whole system has become more transparent and easier to maintain.
Looking back, the starting point of all this was actually just a network cable I casually plugged in.
At the time, I just wanted the speaker next to the router to connect more stably. I never expected that I would end up spending so much time figuring out how to stop Sonos from building an extra wireless network that I cannot manage.
Is your final approach of using a Mac mini as a wireless bridge stable for long-term operation? Could Sonos drop offline after sleep or a restart?