A UniFi update is rarely a problem – until it is. If you follow the right order, take a backup beforehand and pick the correct release channel, you avoid almost every typical failure. This guide shows how to bring your controller, gateway, switches and access points up to date calmly and in control.
Before the update: backup, release notes, channel
Before you click anything, secure your current state. A UniFi update can change the Network application (formerly the „controller“) and your device configuration – and in the rare failure case you want a way back. So take a fresh configuration export or backup of your Network application and store it somewhere that is not on the device you are about to update.
Reading the release notes pays off
Ubiquiti publishes notes for every version covering bug fixes, new features and known issues. A quick look tells you whether an update is security-relevant and therefore urgent, or whether you are better off waiting a week or two until a fresh version has proven itself in the field.
Stable or Early Access?
UniFi software and firmware run on several parallel channels. Simplified, a build first goes through Early Access, then an intermediate stage (Release Candidate) and finally reaches Stable. For a production network – anything you or others rely on – Stable is the right choice. Early Access is deliberately experimental and must first be enabled at the account level. Only turn it on for test devices, or when you specifically need a not-yet-released feature and can live with bugs.
The recommended order
The Network application and device firmware are linked: new firmware often expects a sufficiently recent application. That is why the following order has become common in the community. It is a recommendation, not a hard rule – but in practice it reduces adoption and provisioning problems.
- Network application first. Update the controller software (or UniFi OS on the console) and then check that all devices are back online and stable before you continue.
- Gateway or console. Next comes the central device – the UniFi console or the gateway/router. Deliberately plan for a brief internet outage here.
- Switches. Then the switches, ideally from the core outward. Since access points and other devices are often powered over switches via PoE, this brings the infrastructure up to date first.
- Access points and remaining devices. Finally the APs, cameras and other accessories – again one after another, not all at once.
The key principle is „one device at a time“: wait until a device has installed the firmware, rebooted and reached the Connected state before you trigger the next one. That way you can clearly attribute a problem to a single device.
Common mistakes & how to avoid them
- Updating during peak hours. Every device reboots during an update – meaning brief outages of Wi-Fi, internet or PoE. Schedule updates for off-hours, not in the middle of a video call or evening streaming.
- Updating everything at once. Bulk updates look convenient but make troubleshooting harder and strain the network. Stagger it device by device instead.
- Letting application and firmware drift apart. Very new device firmware on an outdated application (or vice versa) can trigger adoption and provisioning problems. Keep both matched and current.
- No backup. Without a current export, a failure leaves only tedious manual work. The export takes seconds – make it routine.
- Unstable power. A device that loses power mid-update can get stuck in a loop. Ensure clean PoE delivery and a stable power source.
When an update goes wrong
If a device stays stuck in Provisioning, Adopting or Disconnected after an update, that is usually not a total loss. Common causes are flaky uplinks, marginal PoE delivery, or firmware that sits too far from the application version.
Work through it step by step: first give the device a few minutes – provisioning can take a while. If that does not help, reboot the affected device deliberately (via the application or by briefly cutting power). Check the cable, port and PoE budget. Make sure exactly one Network application is responsible for the device – a second, old controller on the network can „fight over“ a device.
If the device stays stubborn, a clean re-adoption often helps: forget the device in the application, factory-reset it and adopt it again. Once it then reaches the current firmware and the Connected state, the case is usually closed. If you get stuck, restore the backup you created earlier when in doubt.
Frequently asked questions
Should I enable auto-update? For a simple home network, automatic updating can be convenient and safe enough. For important or third-party-managed networks, manual, staggered updates are better – you control the timing, the order and have a backup ready. A compromise: notifications on, automatic installation off.
Do I really have to update the application before the devices? It is the common recommendation, because new firmware often expects a sufficiently recent application. It is not strictly mandatory in every case, but in practice it saves you many adoption and provisioning problems.
Stable or Early Access day to day? Stable for production. Early Access is meant for testers and may contain bugs – use it only deliberately and not on devices you depend on.
How long does such an update take? Usually a few minutes per device including the reboot. With several switches and access points, budget some extra time because you deliberately proceed one after another.
Sources: Ubiquiti Help Center – UniFi Updates, Ubiquiti Help Center – Upgrading to Early Access in UniFi. As of August 2026.
