byUBNT-MikeD06-01-201607:11 AM - edited 12-18-201609:04 AM
UniFi 5.0.6 is our newest official General Availability Releasefor UniFi wireless AP (UAP), routing (USG), switching (USW).
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.
For hotspot management console, make sure you have bookmark the url with site name. For example: https://unifi.yourdomain.com:8443/hotspot/s/SITENAME
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'
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 can no longer toggle the VoIP port on the USG (UGW3). It needs to be enabled prior to upgrading/using v5, otherwise you will not be able to control it. If you rely on using the VoIP port then you may want to stay on v4.8.19. Currently it can only be configured as a secondary WAN in v5, but we will be expanding the functionality so it can be used as either a secondary WAN or LAN (LAN will be fully configurable).
Windows users must have x64 Java installed as we only support 64 bit webRTC library. Please see HERE and download the missing version (64bit offline Windows install package).
Speed limits for wireless clients only work on guest VAPs. Non-guest VAPs will not enforce speed limits. This is to help with overall throughput. Please see our original post HERE. If you need to have enforced speed limits on non-guest VAPs then you should use firmware 3.4.19 (do note that you will lose some features when changing to 3.4.19). We've been working on a fix for this and will include it as soon as possible.
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 VLAN set to 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: