UniFi 5.4.15 稳定版正式发行及发行日志



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:

  • For Debian/Ubuntu users, please update your APT source (see HERE).

  • unifi-beta/unifi-rapid are obsoleted. The old repo has been removed.

  • use stable or unifi-5.4 in your source file.

On Linux you can now use Oracle Java instead of OpenJDK (if desired). When using Oracle Java you may need to define the JAVA_HOME location on your Debian/Ubuntu installation. To do this you need to create a default file to define the path. This method is persistent across controller upgrades. Something like the following will work for Oracle Java (change JAVA_HOME path as needed):
echo “JAVA_HOME=/usr/lib/jvm/java-8-oracle” | sudo tee /etc/default/unifi

  • You can no longer manage/control UniFi VoIP devices from the UniFi controller. Please use the UniFi VoIP controller for UVP products. The latest release as the time of this post is found HERE.
  • 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:

sudo rm /usr/lib/unifi/lib/native/Linux/armhf/libubnt_webrtc_jni.so

  • 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.
  • Do note that DFS channels can not be used for wireless uplink as of this release. 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).


  • We no longer support Java version 6, it needs to be 7 or later. We recommend Java version 8.
  • 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 should not 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.

从 5.4.14 版本开始控制器的bug修复与变更:

  • Support SSO Cloud Access with 2FA. *******
  • Update WLAN group load balancing limit.
  • Allow switch downlinks table to scroll.
  • Allow migrate only adopted and connected devices.
  • Add cancel migration of device.
  • Fix memory leak in WebRTC.
  • Fix WAN IP change detection.
  • Update WebRTC JNI.
  • Update bundled Tomcat.
  • Improve validation of configured VLANs on USG (prevents setting invalid VLANs).
  • Fix Not Authorized/Bad Request on first launch after accepting SDN Invitation.
  • Another security improvement

***Not yet exposed at the account side. This option will be available on your UBNT SSO account in the future, and configured via your account page**.

自 3.7.49/4.3.34固件版本开始的修复与变更:

  • [UAP] Wireless uplink improvements.
  • [UAP] Guest mode broadcast filter improvements.
  • [UAP] Fix a memory leak.
  • [UAP] Various tweaks to improve wireless uplink function.
  • [UAP] Add jq for CLI json processing.
  • [USW] Config changes preparing for LLDP-MED and Voice VLAN.
  • [HW] Add ca-certificates package.
  • [SEC] Various security improvements.
  • [USG] Fixed config_network_wan2 reporting (cause of “WAN1 gateway overwriting WAN2” problem).
  • [USG] Back end changes for DPI statistics retention coming in a future controller version.
  • [USG] Send info on L2TP Remote Access VPN clients to controller.
  • [USG] Fix memory leak in guest redirector.
  • [USG] Enable authentication logging for RADIUS server.
  • [USG] Fix “iptables: Index of deletion too big” after successful delete and unsuccessful addition problem described here (unlikely to be encountered on USG, but possible with some config.gateway.json uses).

Firmware 3.7.55 has been pushed for UAP/USW, and 4.3.41 for USG (see HERE and HERE, respectively).






从 5.4.14 版本开始控制器的bug修复与变更:

  1. 支持使用2FA的SSO云访问
  2. 更新WLAN组负载均衡限制。
  3. 允许交换机下行表中滚动。
  4. 允许仅迁移采用和连接的设备(没太明白)
  5. 添加取消设备迁移
  6. 修复WebRTC中的内存泄漏
  7. 修复WAN IP变更检测
  8. 更新WebRTC JNI
  9. 更新捆绑的Tomcat
  10. 改善USG上配置的VLAN的验证(防止设置无效的VLAN)。
  11. 在接受SDN邀请后首次启动时修复未授权/不正确请求。
  12. 另一个安全改进
    自 3.7.49/4.3.34固件版本开始的修复与变更:
    [UAP]添加jq进行CLI json处理
    [USW]配置更改准备LLDP-MED和Voice VLAN