- last edited
Introducing our latest release for UniFi wireless, routing & switching hardware. This is our latest stable release for our current LTS branch.
How to play safe?
Make sure you always do a backup before any updates, especially if you plan to upgrade your existing installation.
For people who are migrating from v3, there're many changes to APIs and it's not backward compatible. You may need to update the shell library (unifi_sh_api) and/or your customized portal/external portal code.
Windows users must have x64 Java installed to use the unifi.ubnt.com cloud tie in, as we only support 64 bit webRTC library. Please see HERE and download the missing version (64bit offline Windows install package). The controller will run in an x86 only environment, or with x86 Java, but the unifi.ubnt.com tie in will not work.
For hotspot management console, make sure you have bookmark the URL with site ID (i.e. x66cipn3, or whatever random string is generated for that site). For example: https://unifi.yourdomain.com:8443/manage/hotspot/site/SITE_ID
For Debian/Ubuntu users, please update your APT source (seeHERE).
unifi-beta/unifi-rapid are obsoleted. The old repo has been removed.
You cannot re-use a VLAN ID for dynamic VLAN if it is set as a static value for another SSID on the same AP. So, if I have a SSID set to use VLAN 10, I cannot use VLAN ID 10 for RADIUS controlled VLAN users as those users will not get an IP.
Cloud Access feature in this release is not supported on Linux/ARMv6 architecture (for exmaple, Raspberry Pi 1). If you have problem starting controller on this platform, please remove the native library:
Smart Queue QoS is similar to the implementation as in EdgeOS (see HERE). Please note that DPI will not work when using Smart Queue QoS, as traffic will not be offloaded. It's also worth noting that maximum throughput will be affected when using Smart Queue QoS, as traffic is not offloaded. There are some rough guidelines in the article linked above.
DFS channels can not be used for wireless uplink in the US. Please use non-DFS channels if you need to use wireless uplink on dual band UAPs.
Official UniFi MIBs can be downloaded from HERE and HERE (those are 2 different files).
A full changelog has been attached, showing changes back to the first public release (1.2.1).
As of 5.6.x we dropped support for Java 6. The minimum supported version of Java is 7, but we highly recommend version 8. At this time Java 9 is not supported.
All APs will be reprovisioned on controller upgrade, which will cause a temporary outage for all connected users. Please make sure to do this after hours, or a time when it's okay to disconnect users for several minutes. This shouldnot affect users upgrading from 5.3.8 or later.
Features like airtime fairness, bandsteering, load balancing and minimum RSSI are default disabled. If you need them you need to go to Settings>Site and check Enable advanced features.
If you previously used Google Maps for a site map, then you have to enable this feature again by adding an API key. This is done under Settings>Controller. There is a linked guide with instructions.
Do not choose the skip option when running the Migrate Site wizard. If you do your devices may end up in a weird state.
The initial database migrationwill take longer than normal.It is expected to see mongo using most, if not all, of the available CPU cycles during this process. Please be patient, this process could easily take 15+ minutes, depending on the amount of historical stats, as well as the system specs. As always, err on the side of caution, and make a backup before upgrading.
The controller will not start if it is set to bind to a privileged port (<1024), as it now runs as a non-root user.
If your controller is running on a UniFi Cloud Key (UCK), make sure it ison firmware 0.6.4 or later, otherwise the controller will not start. This firmware is available via the normal upgrade mechanism found in the controller or it's local management page.Make sure to make a backup before upgrading the UCK firmware, as you'll need it to restore after, and it's good to have a backup on hand before any controller upgrade.
airTime will not work if a radio is disabled and/or there isn't any SSID present. This will be fixed in a future release. If you enable it, and it still isn't working, then you may need to force a refresh without cache.
If you start both a 2.4GHz and 5GHz scan in quick succession, then it will fail.
It is expected that airView will stop occasionally. A stop/start sequence should restore functionality.
If you start an airTime scan while airView is running, then airView will stop and you'll need to perform a stop/start sequence to get it working again. This will be fixed in the future.
Controller bugfixes/changes from 5.6.30:
Improve Neighboring Access Points loading.
Display warning information before choosing DFS channel as wireless uplink.
Display downgrade button if lower version is detected.
Moved device warnings to new tab in property panel.
Added warnings count in device status badge.
Merged Users and Guests tabs in property panel.
Hide Switch temperature if not present.
Disable RF scan for UAP-nanoHD.
Show RF Scan only for devices with proper wifi capabilities.
Add in UI password change suggestion when controller admin password matches device SSH password.
Clear VLAN ID when VLAN is disabled in override.
Fix default 5G channel width.
Fixing load page error in IE11.
Fix display interface stats for USG-XG.
Fix factory reset issue on UCK.
Fix pre-adoption upgrade of USG devices.
Fix VPN status reporting.
Fix WebSocket error for site admin without show pending devices permission.
Fix password field validation in edit account form.
Fixing not opening DPI clients.
Fix invisible debug terminal when device is RF scanning.
Lower strict RSSI requirements for wireless adoption.
Remove reboot before upgrade logic from UAP upgrades.
*This release follows our usual release structure which means it will initially be available via this blog post only. It will be posted to the download site and official repos in the near future. If you aren't familiar with our release structure, please take a moment to read our postHERE. Thanks!