Wireless mesh has always paid a tax. A satellite that talks to the router over the air usually spends one radio on that uplink, and whatever is left serves your devices. Wi-Fi 7 promised a way around it through Multi-Link Operation, yet the useful half of MLO stayed missing from consumer mesh gear for two years. That changed on 10 September 2026, when Ubiquiti added STR MLO for mesh to UniFi Network. Here is what the feature does, what it needs, how much headroom it really adds, and when turning it on is worth the trouble.
What Ubiquiti shipped, and on what date
UniFi Network Application 10.6.106 appeared on Ubiquiti's release page on 10 September 2026. The first line of its improvements list reads: added MLO STR Mesh support for WiFi 7 Access Points, requires UAP 8.8 or newer. Two bug fixes in the same build point at the same subsystem. One corrects Wi-Fi Broadcast failing on the UDR7 and the UDR 5G Max when MLO STR is in use. Another fixes MLO clients showing the wrong IP address.
One caveat belongs up front. Ubiquiti first posted 10.6.106 as a Release Candidate on 10 September and moved it to its general download page on 15 September, so check that your console has actually taken the update before looking for the option.
STR MLO is not the MLO you already had
Multi-Link Operation is a single idea with several very different implementations, and the difference decides whether you gain speed or only stability. Ubiquiti's own documentation splits client behaviour into four types.
| Mode | What the radio does | Effect on throughput |
|---|---|---|
| MLSR | One radio, switches between bands | None |
| eMLSR | One radio, listens on several bands, transmits on one | Lower latency, no extra bandwidth |
| Async MLMR | Several radios, bands run independently | Higher, bands add up |
| Sync MLMR | Several radios, transmissions coordinated | Higher, bands add up |
STR stands for simultaneous transmit and receive, and it covers the two multi-radio modes at the bottom of that table. Until now UniFi offered only eMLSR, and eMLSR does exactly what its row says. It helps a phone hold a steadier link in a crowded flat, yet it never widens the pipe. That is why MLO felt underwhelming to a lot of people who enabled it and measured no change.
Why the backhaul is where this matters
Think about what a mesh satellite actually does. It has a fronthaul, the link to your laptops and phones, and a backhaul, the uplink to the router. The backhaul sets the ceiling for everything downstream of that node.
If one band carries both jobs, roughly half its capacity goes to each, so a node on a shared 5 GHz link gives your devices about half of a 5 GHz radio. Tri-band hardware often solves this by reserving a band purely for the uplink, which is called a dedicated backhaul. That works, but it costs you the whole band for client use.
STR MLO takes the third route. The node bonds two bands into one uplink and runs both at once, so the uplink gets the sum rather than a share of one. Ubiquiti confirmed earlier this year that the feature is used for the backhaul link only. Fronthaul, meaning your actual clients, stays on eMLSR.
The arithmetic of a two-band uplink
Take the UniFi Express 7, which Ubiquiti now sells in mesh packs. Its published radio rates are 5.7 Gbps on 6 GHz and 4.3 Gbps on 5 GHz, both 2×2. Bond those two and the arithmetic is simple.
5.7 + 4.3 = 10.0 Gbps of combined PHY rate
Read that number correctly. A PHY rate is a modulation ceiling measured at close range with a clean channel, not throughput you will see on a speed test. Real figures land well below it, and the gap widens with distance, walls and neighbours. The honest claim is comparative rather than absolute. A bonded 5 GHz and 6 GHz uplink has more headroom than either band alone, and far more than half of one band.
The second correction matters as much. If those same two bands also carry client traffic on that node, the sharing rule has not gone away. Half of the combined capacity is available to each side. Half of a bonded pair still beats half of a single band, which is the entire point.
What you need before the option appears
Four conditions have to line up. First, UniFi Network 10.6.106 or newer on the console. Second, access point firmware UAP 8.8 or newer, which the release notes state explicitly. Third, Wi-Fi 7 hardware with at least two usable bands on both ends of the link, since one radio cannot transmit on two bands at once. Fourth, WPA3.
That last one surprises people. The 802.11be standard requires WPA3 on every link in a multi-link association, so you cannot keep WPA2 on 5 GHz and run WPA3 only on 6 GHz. If an old printer or a cheap smart plug still needs WPA2, put it on a separate SSID rather than weakening the one carrying MLO.
MLO itself is a per-SSID setting in UniFi, found under Settings and then WiFi, as a checkbox on the network you want it on.
The hardware Ubiquiti built around it
The feature arrived alongside a product push. Ubiquiti introduced Whole Home WiFi, a consumer mesh line built from UniFi Express 7 units sold in packs. On the United States store on 13 September 2026 a single UX7 listed from 199 dollars, shown as 214 dollars with the memory surcharge included, and the three-pack listed at 559 dollars, shown as 603 dollars with the surcharge. Those two figures explain the conflicting prices in early coverage, because some outlets quoted the surcharge-inclusive number.
The unit itself is unusual for a mesh node. Ubiquiti's specifications list a 10 GbE WAN port, a 2.5 GbE port, tri-band Wi-Fi 7, 3 GB of memory, coverage of 160 square metres, and a maximum draw of 22 watts over USB-C.
Power explains the two-year wait
That 22 watt figure is not incidental. Running two radios at once costs far more energy than switching between them, which is why eMLSR spread quickly through phones and laptops while STR did not. Ubiquiti's first STR MLO device, the AirWire adapter announced on 19 March 2026, needs up to 20 watts and carries a second USB-C port purely so it can draw extra power when the host cannot supply enough.
So STR MLO belongs on mains-powered gear: access points, mesh nodes and bridges. Do not expect it to appear on a laptop card any time soon, and do not read a client-side MLO badge as a promise of this behaviour.
Dedicated radio or bonded uplink?
Both approaches fix the same problem, and they trade differently. A dedicated backhaul radio is predictable and needs no client cooperation, but it removes a band from client duty and the ceiling is whatever that one radio can do. A bonded STR uplink keeps both bands in play and raises the ceiling, yet it depends on firmware maturity and on 6 GHz behaving well over the distance between your nodes.
Range is the practical catch. 6 GHz carries less far through walls than 5 GHz, so a node placed two floors away may spend most of its time on the weaker half of the pair. Placement still decides mesh performance more than any feature flag.
Should you turn it on?
If you run UniFi Wi-Fi 7 nodes on a wireless uplink, yes. The gain is real and it lands exactly where mesh hurts. If your satellites are already wired over Ethernet, skip it, because a cable beats every wireless uplink ever shipped and nothing here changes that.
Two groups should wait. Anyone running a network they cannot afford to have wobble should wait for a few weeks of reports on the build before enabling it. Anyone still carrying WPA2-only devices on the main SSID needs to move those off before MLO is worth enabling at all.
