FR
live

UniFi Network 11 makes the network Matter-aware and merges IP and Thread topology into one map

On October 12, 2026, Ubiquiti shipped UniFi Network Application 11.0.83, which brings Matter and Thread devices into the network console with a single pairing code and, for the first time, renders IP and Thread topology on the same map. For UniFi site administrators, the network map and the smart-home map now tell the same story.

Two kinds of cable — a thick copper Ethernet strand and a thin luminous thread — braided together in one dark cable tray, a single amber connector lit at the convergence point.

October 12, 2026. Ubiquiti shipped UniFi Network Application 11.0.83, version 11 of its network management console. One pairing code. That is now all it takes to bring a Matter device into UniFi and read its battery level, firmware, and signal strength. A first. IP topology and Thread topology render on a single, unified map. Why it matters: the network map and the smart-home map — two views people used to keep separate — now tell the same story, and an administrator sees at a glance how a Thread device attaches to the rest of the infrastructure.

Matter and Thread enter the network map

The real change is conceptual before it is technical. Historically, Matter-over-Thread devices lived in a blind spot: the Matter controller (often a home-automation hub) managed them, while the UniFi console only saw the IP network. Between the two, nobody had the full picture. A bulb that lost its Thread network appeared as a simple “offline” in the home app, with the network unable to say why.

UniFi Network 11 closes that gap. Entering a Matter pairing code into the console brings the device into UniFi, which then shows detailed insights: battery level, firmware version, and signal strength. The Matter device becomes a full citizen of the map, just like a Wi-Fi client or a switch.

The centerpiece is the unified topology. For the first time, IP and Thread devices are visualized together, with custom alerts for critical equipment in both worlds and troubleshooting tools that span both connectivity types. It is the end of double-reading: you no longer guess whether a device is disconnected — you see it, and you see exactly which link it traverses.

Telemetry rewritten for scale

Behind the Matter headline, Ubiquiti rewrote its telemetry engine, and the number it puts forward is 30% better scalability. In practice the console holds up better as sites grow, which translates into two new features.

Live Traffic Flows shows real-time traffic for every device connected to a UniFi Gateway — who is talking to whom, at what rate, without waiting for a refresh. Time Machine Topology adds the temporal dimension: you rewind the map to visualize how the network changed and understand the moment a link moved. For an MSP running several sites, that is the difference between “it is broken now” and “here is what moved yesterday at 2 p.m.”

These features are not gimmicks: they shift network debugging from the log toward temporal visualization. Instead of correlating scattered logs, you look at the map and rewind the timeline. That is a change of method as much as a change of interface.

Version 11 is not only a visibility overhaul. UniFi Gateways receive three changes that touch resilience and network organization.

The most striking is WiFi WAN: on supported models, any available Wi-Fi network — including the mobile hotspot on your phone — can become a primary or backup WAN connection. A site whose fiber line drops fails over to a phone hotspot until service is restored. That is continuity insurance without extra hardware.

Network Lists gain external URL support: firewall rules and VPN resources can reference dynamically updated lists instead of frozen addresses maintained by hand. Combined with expanded VLAN capacity, they simplify routing policies on complex sites. For a network segmenting its IoT, its guests, and its back office, that means less manual maintenance and fewer rules rotting in a corner.

Security and SD-WAN: the enterprise layer

Two further additions target multi-site deployments. The first is Cybersecure Enhanced, whose daily threat signatures from Proofpoint now carry AI-assisted explanations. An alert no longer just names a threat: it summarizes its scope, risk, and impact, and offers an actionable recommendation. For an administrator who is not a full-time security analyst, that is the translation of a raw signal into an operational decision.

The second is the evolution of SD-WAN policies, with custom failover rules and application-based routing across multiple sites. You can now fail a specific traffic class over to a specific link, or route a critical application down a dedicated path, all governed from a single console. That is the level of control that teams administering several UniFi sites remotely were missing.

What this really changes

Step back. The October 12 announcement confirms a direction Ubiquiti has followed for several releases: bringing the network and the smart home together in one management surface. Matter-awareness is not a marketing gimmick — it is the recognition that Thread is an edge network like any other, and deserves the same observability as Ethernet or Wi-Fi.

The trade-off is a compatibility perimeter you must check. Version 11.0.83 requires UniFi OS 6.0.10 and rolls out in stages: not every controller receives it at once, and some features — WiFi WAN in particular — depend on the gateway model. Before promising unified Thread topology to your leadership, verify that your hardware actually supports it.

One more point to keep in mind: Matter monitoring is a read-only observability feature, not a controller. UniFi sees the state and connectivity of Matter devices, but the home-automation logic — scenes, automations — still lives in the existing Matter controller. The two systems coexist; they do not replace each other.

What to check before you upgrade

Because the rollout is staged, not every controller receives 11.0.83 on day one. The release requires UniFi OS 6.0.10, and features are uneven across hardware: WiFi WAN depends on the gateway model, and the Matter view needs a compatible UniFi Network Application plus an existing Matter controller to pair against. Before promising the new topology to stakeholders, confirm your cloud gateway or self-hosted controller actually meets the minimum, then enable Cybersecure Enhanced separately — the AI-assisted explanations are a feature flag, not a default.

For the homelab crowd the upgrade is a no-brainer, but treat it as a two-part migration: the network application first, then a deliberate pass to pair your Matter devices into UniFi. Nothing is auto-discovered on the Thread side; you still enter each pairing code by hand. The unified map is the reward for that one-time chore, not a switch you flip.

Verdict

If you run a UniFi site as a homelab or small business, the unified IP + Thread topology is the reason to upgrade: it removes the most annoying blind spot in home automation, the “offline” device with no explanation. If you manage multiple sites for clients, the Time Machine Topology, Live Traffic Flows, and application-based SD-WAN justify version 11 on their own — that is where the 30% scalability gain turns into shorter time-to-resolution. If your hardware is old, check compatibility with UniFi OS 6.0.10 before scheduling the migration. Ubiquiti did not invent a new protocol: it did what was missing for years — giving Matter and Thread the same place on the network map as any Ethernet cable.

References

The cyber brief, every Tuesday

The flaws that matter and the patches to apply, in a ten-minute read.

No spam. One-click unsubscribe.
read next

On the same topic

The FCC and four US states target TP-Link while five Aginet flaws remain unpatched

On October 6, 2026, Florida, Iowa, Montana and Nebraska sued TP-Link for misleading consumers about router security, while the FCC still denies it an exemption to the ban on routers made outside the US. In parallel, SEC Consult detailed five flaws in the Aginet line — CVE-2025-30237 through CVE-2025-30241 — some of which will never be patched on affected models: inventory your TP-Link hardware before trusting its update channel.

Cloudflare makes its secure web gateway and DLP programmable with inline Workers

On October 15, 2026, Cloudflare added a Forward action and Custom Functions to Cloudflare Gateway, running your own code at the exact moment a security policy makes its decision. If you maintain NGINX proxy pools for header injection or Logpush pipelines for alerting, replace them with a single Worker.

← Back to the feed

Type at least two characters.

↑ ↓ navigate ↵ open esc dismiss