In short
- 5.1.28 is a pure stability and bugfix release at the OS level. The bundled Network app 10.4.57 is not new — it already shipped with 5.1.27.
- The only substantive fix repairs a blocking function for multicast/broadcast traffic. What it actually does is not spelled out in the note.
- Same version number does not mean same device: Dream Routers 5.1.28 is a different thing from Cloud Gateways 5.1.28 or Dream Machines 5.1.27.
What 5.1.28 actually changes
The note lists two items. One improvement, "Improved device stability", and one bugfix: a function meant to block multicast and broadcast traffic had stopped doing so reliably. On top of that, the roll-out is staged. The update does not land on every device on the same day. If it is not offered to you yet, nothing is broken.
That is the whole list. No new Wi-Fi feature, no new interface, no new function in the Network app. Anyone expecting more is confusing the OS release with the app inside it.
Why the Network app is not new
5.1.28 ships with UniFi Network 10.4.57. But that app version is not what is new about the release. It was already part of UniFi OS 5.1.27 and ran on other device classes in the same window. The app's feature set had been in circulation for a while.
In practice: if you were already on 5.1.27, 5.1.28 adds nothing at the app level. The step is only what happens at the operating-system level — stability and the one fix. That is not a drawback. It just needs to be stated honestly, so nobody forces an update that gives them nothing.
The one fix, and how to read it
Multicast and broadcast traffic sits behind many services that announce themselves on the network — from AirPlay to Sonos to the network printer. On large networks with many clients, that traffic can get noisy. So there is a setting that deliberately blocks it. That blocking function was broken, and it is now repaired.
Here is the part not to twist: the fix restores a function that suppresses traffic — not one that makes services reachable across network boundaries. If you had turned the block on deliberately and wondered why it had no effect, 5.1.28 gives you back the behaviour you configured.
What the fix does beyond that, the note does not say. On the Cloud Gateways, the same bug was explicitly limited to a single model on the same day. For the Dream Routers, no model is named. Whether the fix here covers every device on the track or just one cannot be read from the note. If you run a larger network that depends on this block, check after the update that it does what it should.
Same number, different device
The most common mistake with these releases is mixing up the tracks. "5.1.28" on its own does not tell you which device is meant. Ubiquiti keeps several separate OS lines in parallel, and they sometimes carry the same number without being the same release.
| Track | Devices (examples) | Version |
|---|---|---|
| Dream Routers | UDR, UDR7 | 5.1.28 |
| Cloud Gateways | UCG-Ultra/-Max/-Fiber/-Industrial, UXG | 5.1.28 (separate release) |
| Dream Machines | UDM, UDM-Pro/-SE/-Pro-Max | 5.1.27 |
The thing to remember: Dream Routers 5.1.28 and Cloud Gateways 5.1.28 are two different releases with the same number. On the Dream Machines the number even sits at 5.1.27. Placing the UDR7 on this track is plausible from the name family but not explicitly documented — check it on the device if in doubt. If you run devices from different classes at one site, match the version per device, not per site.
Why an all-in-one calls for more caution
The Dream Router is one device doing several jobs at once: router, Wi-Fi, switch, often the console for cameras as well. For a single finca unit, a guest house or a small office, that is sized just right. Depending on the figures given, a UDR7 handles around 30 UniFi devices and a few hundred clients across roughly 160 square metres.
That bundling is exactly the weak spot at update time. When router, Wi-Fi and switch are separate devices, a failed update takes one part down. On an all-in-one, everything hangs off one console. If the update goes wrong, the whole site network is down. So what can be handled more loosely with separate components applies strictly here: back up first, pick a window with no operation, and not on a Friday evening.
For the large projects we plan — estates with several buildings, villas with separate networks for owners, guests and technical gear — the UDR is usually too small anyway. That calls for the class above it. The Dream Router is the device for the smaller, self-contained unit. For that, it fits well. Where more substance is needed, we lay out the infrastructure differently.
Is the update worth it?
Honestly: no island-specific reason to rush. 5.1.28 changes nothing about the law, the climate, the power grid or availability here — it is a global firmware release. Anyone who tells you otherwise is just blowing smoke. If you do not specifically depend on the repaired blocking function, you can wait for the staged roll-out and apply the update when it is offered normally.
For anyone running a UDR or UDR7 as the single console of a site, the advice is: apply it, but plan it. Stability updates are good. Touching a production all-in-one without a backup and a window is not. If you are unsure whether your device is on the right track and whether the fix affects you at all, we sort that out beforehand — get in touch and you reach a dedicated point of contact before you press the button.
Before updating to 5.1.28
- Check which track: Dream Router (5.1.28), Dream Machine (5.1.27) or Cloud Gateway (its own 5.1.28)?
- Take a backup of the console before anything is applied.
- Pick a window with no operation — not while guests are in the house.
- After the update: does the multicast/broadcast block work again as configured?
- Do not force the update — the staged roll-out is normal, "not there yet" is not a fault.
Related reading
German-speaking IT service for fincas, villas and businesses on Mallorca. Networks, Wi-Fi, security technology and smart home — planned, installed and maintained.