UniFi 5.4.11 Stable has been released

by Ubiquiti Employee ‎02-08-2017 10:38 AM - edited ‎04-06-2017 02:21 PM (79,859 Views)

UniFi_V5_IG_FIN.jpgIntroducing our latest release for UniFi wireless, routing & switching hardware.This is our latest Stable release for the 5.4.x branch.


How to play safe?

Make sure you always do a backup before any updates, especially if you plan to upgrade your existing installation. 


Release Notes:

  • 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 'unifi5' in your source file, instead of 'stable' or 'unifi4'
  • 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).

Other Notes:

  • 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.


Controller bugfixes/changes from 5.4.9:

  • Add Migrate Site (Export Site) Wizard.
  • Support concurrent L3 device adoption.
  • Improve dates in statistics page.
  • Fix slow database backup.
  • Fix RADIUS profile migration issue.
  • Fix database migration issue, causing the controller not to start after upgrading.
  • Update port speed availability for 10GBASE-T ports.


Controller bugfixes/changes backported from 5.5.3:

  • Add validation for USG/USW SNMP community string. 
  • Enable traffic-control for USG on supported firmware versions.
  • Various VPN and routing policy fixes.


Controller Bugfixes/Changes specific to UniFi Elite:

  • Add chat_elite tag to chat in Elite Controllers.
  • Fix discovering devices on Windows machines.
  • Handle license registration error on device adopt.
  • Fix saving Controller Settings for Elite.


Firmware changes from 3.7.34:

  • [UAPG3] Enable tinysnmp.
  • [UAPG3] Enable 802.1x identity support.
  • [UAPG3] Fix RX rate error.
  • [UAPG3] Update NSS offload firmware.
  • [UAPG3] Enable bonding in the firmware, controller support pending on some releases. 
  • [UAPG2] Fix spectral scanning causing some DFS frequencies to be skipped during the scan. 
  • [UAP] Fix an issue with wireless uplink connectivity.
  • [UAP] Fix an issue with wireless adoption.
  • [UAP] Fixed issue with random disconnects.
  • [UAP] Fixed issue where stations were improperly getting kicked while roaming subnets.
  • [UAP] Fix open SSIDs on 1st gen AC models. 
  • [UAP] Add broadcast filter support.*
  • [UAP] Add rate control framework.*
  • [UAP] Numerous backend fixes and changes.
  • [USW] Fix invalid BPDU hello time.
  • [USW] Fix broken PoE restart on US-8.
  • [USW] Fix LED handling when port running at 10/100M on US-8/US-8-60W.

UAP/USW firmware 3.7.51 has been pushed to this release. See HERE for details. We also pushed USG firmware 4.3.37 to this release (details HERE).


Bundled Firmware: