UniFi Network 10.1: What's New and How the WiFi Doctor Works

With UniFi Network 10.1 (released February 2026), Ubiquiti has delivered an update that is less about new hardware than about a clear promise: networks should be more stable, more transparent and easier to manage. The most striking new feature is the WiFi Doctor, an automatic diagnosis and repair tool that is meant to fix common WiFi problems with a single click.

This article first explains the basics of the UniFi Network controller: what it is, how it works and how to use it. Then it goes deep into what is new in version 10.1, and especially into the WiFi Doctor: what it can do, what it cannot do, and what the community criticizes about it.

Part 1: UniFi Network, the Basics

1. What is UniFi Network, anyway?

UniFi Network is the central management software for all Ubiquiti UniFi devices: switches, access points, gateways (routers), cameras and more.

The principle behind it is the concept of SDN (Software Defined Networking): all network configuration and monitoring is not done on each device individually (via Telnet, SSH or the device’s own web interface), but centrally through a single interface. That is the controller.

Analogy: imagine you manage a building with 20 rooms. Without a controller, you have to walk into each room individually to change a setting. With the controller, all rooms are on a single screen: you change something once and it applies to all of them.

What the controller is not: it is not an active network device. The network keeps running even when the controller is offline. The controller is pure management: it writes the configuration to the devices, and the devices carry it out. This is an important distinction that confuses many beginners at first.

2. Where does the UniFi Network controller run?

The controller is software, and it can be run in different ways:

Option 1: Cloud Gateway / UDM (recommended) The simplest and most professional solution: the Cloud Gateway (e.g. UCG-Ultra, UDM-SE, UDR) already has the controller built in. Switch it on, set it up, done. No separate PC, no server, no cloud dependency for operation.

Option 2: UniFi Cloud Key A small USB-stick-like computer that hosts nothing but the controller. It is powered via PoE from the switch. Makes sense if you already have your own router and do not want to buy a UDM.

Option 3: Self-hosted controller (UniFi Network Application) The controller software can be installed on your own PC, a Raspberry Pi, a NAS or a Linux server. For pros who want full control. Downside: you have to take care of updates, backups and availability yourself.

Option 4: UniFi Cloud Console (hosted) Ubiquiti offers a cloud-hosted controller. The network is then managed by Ubiquiti servers. Rarely needed for home users, increasingly interesting for MSPs (Managed Service Providers) with many sites.

Important for your choice: some features, including the new WiFi Doctor, strictly require a Cloud Gateway or the remote access feature. If you run a self-hosted controller without a Cloud Gateway, you do not have access to all features. More on this in section 9.

3. The UniFi Network interface: what is where?

The interface is divided into a few clear areas:

Dashboard The start page. Shows network status, connected devices, data traffic and alerts at a glance. Here you can see immediately if something is wrong.

Devices All adopted UniFi devices: switches, access points, gateways. Per device: firmware version, uptime, PoE consumption, ports, connected clients. From here you can trigger firmware updates, configure ports and restart devices.

Clients All connected end devices: laptops, smartphones, cameras, IoT devices. You can see the IP address, MAC address, signal, connection type and VLAN. From here you can assign fixed IP addresses (DHCP reservation), rename devices and view the connection history.

Settings The heart of the system. Everything is configured here:

• Networks: create VLANs, define IP ranges, configure DHCP
• WiFi: create SSIDs, passwords, bands, roaming settings, VLAN assignment
• Routing & Firewall: firewall rules, traffic rules, port forwarding, inter-VLAN routing
• VPN: WireGuard, OpenVPN, site-to-site VPN
• System: controller backups, updates, remote access, users

WiFi → AirView Channel analysis, RF environment, and since 10.1: the Roaming Journey (more on this in section 11).

Topology Visual representation of the network: which device is connected to which port, which switch is upstream, which clients are connected. Extremely helpful in more complex networks.

4. Adopt: how do devices get into the controller?

A new UniFi device does not know the controller at first. It has to be adopted (registered) first. The procedure:

1. Connect the device to power and the network
2. In the controller it appears as “Pending Adoption” (waiting to be admitted)
3. Click “Adopt”
4. The controller transfers its configuration to the device
5. The device restarts and then shows as “Online” in the controller

On a Cloud Gateway this often happens automatically if the device is on the same network. With a self-hosted controller you have to tell the device where to find the controller, via SSH or a DHCP option.

Important: if a device is reset (long press of the reset button), it leaves the controller and has to be adopted again. The device configuration is erased in the process; the controller notices and shows the device as “Pending” again.

5. Updates, backups and remote access

Firmware updates UniFi devices receive firmware updates regularly. These can be triggered manually or scheduled automatically (e.g. at 3 a.m.). Important: always run updates during quiet hours, because an AP restarts briefly (~30 seconds of downtime).

The controller shows per device whether an update is available and offers a comparison of the changes. Upgrade paths are checked automatically.

Backups The controller creates automatic backups of the configuration. These can be downloaded to a PC at the push of a button or stored in a cloud. If something goes wrong, the entire configuration can be restored in a few minutes, on the same or on a new controller.

Remote access Once remote access is enabled (Settings → System → Remote Access), you can reach the controller from anywhere via unifi.ui.com, with no VPN and no port forwarding. It works by using Ubiquiti’s cloud infrastructure as a relay.

For the WiFi Doctor and some other features, remote access is mandatory. It is one of the most common questions in the community: “Why can’t I see the WiFi Doctor?” Answer: remote access is not active.

Part 2: UniFi Network 10.1, What’s New?

6. What is UniFi Network 10.1?

UniFi Network 10.1 was officially announced by Ubiquiti on February 2, 2026. The final release candidate carries the number 10.1.83.

The update is not a feature fireworks display, but a targeted push toward stability and professionalization. Ubiquiti itself describes it as “a deliberate step toward rock-solid, predictable and professionally managed networks.”

The four big new features at a glance:

Feature	What it brings
WiFi Doctor	Automatic diagnosis and repair of common WiFi problems
High Availability 2.0	Easier setup and testing of redundant gateways
Roaming Journey	Visualization of how devices move between access points
UniFi Site Manager	Central management of multiple sites (Early Access)

On top of that: Starlink integration with signal strength display, device tags, optional AP name broadcasting, improved log filtering and about a dozen bug fixes.

7. High Availability 2.0: redundancy for critical networks

High Availability (HA) means: if the primary gateway fails, a second one automatically takes over. No network outage, no manual intervention.

Until version 10.1, setting up HA in UniFi was technically complex and error-prone. Many administrators avoided it because the configuration required too much experience.

10.1 solves this with a guided setup:

1. Step-by-step wizard that walks you through the entire setup
2. Automatic firmware check: both gateways must have the same firmware. The controller checks this and blocks activation if the versions do not match
3. Real-time configuration sync: all settings are transferred live from the primary to the shadow gateway
4. Failover verification: a simulated outage tests whether the backup gateway really takes over, before it happens in a real emergency

The result: HA is now accessible to non-experts too. Especially relevant for commercial customers, hotels, offices and fincas, where a network outage means real damage.

Requirement: two compatible UniFi Cloud Gateways (e.g. two UCG-Ultra or two UDM-SE). The shadow gateway takes over the primary gateway’s IP via VRRP (Virtual Router Redundancy Protocol), invisibly to all client devices.

8. Roaming Journey: follow a device’s path through the WiFi

In every multi-AP network the question comes up: why is my guest’s iPhone still connected to the access point on the ground floor when they have been sitting on the first floor for ages? Why did the laptop briefly lose its connection when moving between rooms?

Until now these questions could only be answered with effort. UniFi 10.1 answers them with the Roaming Journey.

In the AirView section of the controller you can now visualize for each client:

• Which access point was responsible at what time
• When the device switched (roaming event)
• Whether the switch was successful or caused dropped connections
• Which band (2.4 GHz / 5 GHz / 6 GHz) was used

There are also filter options by source and destination AP, band, time range and device.

Practical use: with this data you can answer concrete questions:

• Is another access point needed at a particular spot?
• Does a device roam too late (sticky client: stays on the weak AP too long)?
• Does a device roam too early (ping-pong between two APs)?
• Is the assisted roaming configuration (802.11r/v/k) correct?

This is real progress. Until now you had to resort to external tools like WiFiman or manual log analysis.

Part 3: The WiFi Doctor in Detail

9. What is the WiFi Doctor?

The WiFi Doctor (also called “WiFi Agent” in the Ubiquiti documentation) is an automatic diagnosis and repair tool that detects and fixes common WiFi configuration errors with a single click.

The goal: what used to take hours of manual analysis (channel overlaps, misconfigured roaming parameters, IoT problems, outdated firmware) should be identified by the WiFi Doctor in seconds and, where possible, corrected automatically.

Where do you find the WiFi Doctor?

• In the UniFi Network controller: WiFi → WiFi Doctor (or WiFi Agent)
• In the UniFi mobile app: visible directly on the dashboard as a shortcut (since 10.1)

What exactly does the WiFi Doctor check?

Check	What it analyzes
ISP / internet connection	Interruptions at the internet provider that cause connection problems
AP firmware	Outdated firmware on access points that can lead to instability
APs offline	Unreachable access points that cause dead spots
Channel optimization	Overlapping channels that cause interference
Roaming configuration	Misconfigured assisted roaming (802.11r/v/k)
IoT compatibility	Settings that disrupt or exclude IoT devices
Sticky clients	Devices that stay too long on a bad AP
Transmit power	Transmit power that is too high and prevents roaming

After the analysis, the WiFi Doctor shows a list of the problems found with an explanation and, where possible, an “Automatically fix” button.

10. Requirements for the WiFi Doctor: the most common source of error

This is the point where many users were disappointed after updating to 10.1: the WiFi Doctor does not appear or is grayed out. The reason: it has strict requirements.

Minimum requirements according to Ubiquiti:

1. UniFi Network 10.1 or higher (at least version 10.1.83)
2. Either: a direct connection to the UniFi network (Direct Access, meaning you are connected to the WiFi or LAN that the controller manages)
3. Or: remote access enabled (Settings → System → enable Remote Access and link your Ubiquiti account)

What this means in practice:

If you host your controller yourself (on a PC or Raspberry Pi) and have disabled remote access, you cannot use the WiFi Doctor. This was a frequent topic in the Ubiquiti community after the release: many privacy-conscious users, or pros who disable remote access for security reasons, have no access to the feature.

Ubiquiti has since documented the requirements in its help documentation, but at the time of release many users were surprised.

Other limitations:

• The WiFi Doctor needs at least one active UniFi Cloud Gateway or a UCK Gen2+ as controller hardware. Pure software controllers on a Raspberry Pi may have a limited feature set
• The feature was refined further with 10.1.83; if you have an earlier 10.1 version, you should update to 10.1.83

11. What the WiFi Doctor fixes automatically, and what it does not

This is the most important section for anyone who wants to work with the WiFi Doctor.

The WiFi Doctor fixes automatically:

• Channel overlaps by reselecting channels (like a manual “Auto-Channel” run)
• Misconfigured Fast Roaming (802.11r): it enables or disables it depending on device compatibility
• IoT-specific settings such as DTIM interval, minimum data rate and multicast filtering
• Transmit power recommendation (it suggests reducing the power if it is too high)

Diagnoses, but does not fix automatically:

• Physical AP placement problems (it shows that an AP is too far away, but it cannot move it)
• ISP problems (it detects instabilities at the provider, but cannot fix them)
• Offline APs due to hardware defects or cable problems
• Too few access points for the area (it recommends more, but cannot add them)

What it expressly does not do:

• It does not change manually set configurations without explicit confirmation
• It does not touch firewall rules, VLANs or routing
• It is not a replacement for professional network planning in complex environments

12. Known problems and criticism from the community

Since the release, users and networking pros in the Ubiquiti community, on Reddit and in specialist forums have described several weak points:

Problem 1: “No access to the WiFi Doctor” The most common problem. Cause: remote access not enabled. Solution: turn on Settings → System → Remote Access and link a Ubiquiti account. If you do not want to do that for privacy reasons, you have to do without the feature; there is no alternative.

Problem 2: WiFi Doctor too superficial for complex setups Networking pros criticize that the WiFi Doctor is designed mainly for simple to medium-sized home networks. In complex setups with many VLANs, multiple SSIDs and customized roaming parameters, the recommendations are sometimes too generic or even counterproductive. For example, it recommends enabling Fast Roaming (802.11r) even when the network has IoT devices that do not support 802.11r compatibly.

Problem 3: 802.11r and legacy devices Fast Roaming (802.11r) dramatically improves roaming for modern devices. But older printers, smart home hubs and certain IoT devices have known bugs with 802.11r implementations: they lose the connection or reconnect in an endless loop. The WiFi Doctor enables 802.11r automatically in some configurations without pointing out legacy devices. Recommendation: after running the WiFi Doctor, check that all IoT devices are still connected.

Problem 4: Sticky clients are detected but not really fixed The sticky client problem (a device stays too long on the wrong AP) is one of the most discussed WiFi challenges. The WiFi Doctor diagnoses it correctly, but the automatic corrections (reducing transmit power, setting a minimum RSSI) are not a complete solution. The real cause of sticky clients often lies with the client device itself, and no controller in the world can force that.

Problem 5: “Auto-Optimize Network” was a warning sign Experienced UniFi users remember: the old “Auto-Optimize Network” function was notorious for creating more problems than it solved. It enabled several beta features at once and overwrote manual settings. The WiFi Doctor is conceptually similar but better implemented: it asks before every change. Even so, it is wise to understand every proposed change before you confirm it.

13. Using the WiFi Doctor properly: recommendations from practice

Before the first use:

1. Create a backup: Settings → System → Backup → “Create backup now”. If the WiFi Doctor changes a setting that causes problems, you can roll back immediately.
2. Choose a maintenance window: the WiFi Doctor can change channels and enable Fast Roaming; both cause brief re-authentications on connected devices. Do not run it during a video conference.
3. Know your IoT devices: do you have devices that are known not to be compatible with 802.11r? Write them down and check after the run whether they are still connected.

After running it:

1. Read all recommendations, do not confirm blindly. Every change has an explanation; understand it.
2. Check the IoT devices: smart home devices, printers, heating controllers: are they all still online?
3. Test roaming: walk through all rooms with a smartphone and check that switching between APs goes smoothly.
4. Check the controller log: Settings → System → Logs: any unusual events after the WiFi Doctor run?

When NOT to use the WiFi Doctor:

• On networks with many old IoT devices (built before 2018) and unknown 802.11r compatibility
• Shortly before or during important events (a wedding party, a business presentation)
• As a replacement for a professional initial installation: the WiFi Doctor optimizes, but it does not replace well-thought-out AP placement and VLAN structure

14. Other new features in 10.1 at a glance

Starlink integration UniFi 10.1 now shows Starlink connections with signal strength details directly in the controller dashboard. The firmware status of the Starlink hardware is also visible, without having to open the separate Starlink app.

For fincas and rural installations in Mallorca that use Starlink as a primary or backup connection, this is a direct win: everything on one screen.

Note on Starlink + UniFi: the LAN subnet must not be 192.168.100.0/24. Starlink uses that range internally for its management and you will otherwise get conflicts.

Device tags Access points, switches and clients can now be given freely definable tags, e.g. “Ground floor”, “Pool house”, “IoT”, “Priority”. This makes filtering and navigation in larger networks with many devices much easier.

Optional AP name broadcasting Access points can now broadcast their own name in the beacon frame (the network announcement packet). This simplifies WiFi site surveys considerably: tools like WiFiman see not only the SSID signal but also which AP is broadcasting it.

Extended log filtering The system log has new filter options: filter by device, event type, severity and time range. Especially when troubleshooting in complex environments, this saves a lot of time.

UniFi Site Manager (Early Access) A new central portal that lets you manage multiple UniFi sites in a single interface. Still in the early access phase, but the direction is clear: UniFi is evolving from a single-site tool into a true multi-site platform.

15. Updating to 10.1: what you should know

How do you update? In the controller: Settings → System → Application → “Check for updates”. Or: Settings → Devices → update all APs and switches individually.

Absolutely beforehand:

1. Create a full backup (Settings → Backup)
2. Check firmware compatibility: all devices should have current firmware before the controller is updated. Controller version and device firmware are not necessarily always compatible right away.
3. Plan for downtime: the controller restarts briefly during the update. Devices keep running, but configuration changes are not possible during that time.

Known limitations after the update:

• Older devices (e.g. first-generation UAP-AC-Lite, UAP-AC-Pro with very old firmware) may not be able to use all new features after the controller update
• The device firmware update to new versions should happen after the controller update, not before
• In mixed networks (older Gen1 switches + new U7 APs), a test in a staging network is recommended before you update production systems

Summary: UniFi Network 10.1 at a glance

Feature	Benefit	Requirement
WiFi Doctor	Automatic WiFi diagnosis and repair	Remote access enabled or Direct Access
HA 2.0	Easy setup of redundant gateways	2x compatible Cloud Gateways
Roaming Journey	Roaming visualization per client	Multi-AP network, UniFi Cloud Gateway
Site Manager	Multi-site management	Early Access, Ubiquiti account
Starlink integration	Signal strength and firmware in the controller	Starlink connected as WAN
Device tags	Better organization of large networks	No extra requirement