Readers will learn how to change the firmware on their UniFi device. A simple device upgrade to the most recent release can be done within the controller, in the Devices section. An upgrade option will appear under the Actions column of each device when there is an available upgrade.

For APs there is now the option of a rolling upgrade: once inside the Devices tab, click on APS. A button will appear on the upper, right-hand of the screen, offering the option to Start Rolling Upgrade if there are UAPs with pending upgrades on the list.

However, this article describes how to change the firmware when a simple device upgrade is not what the user is looking for. They might be in need of an older or a non-released version. This can be handy to help with adoption issues, for troubleshooting, or simply upgrading to the latest available firmware if a new controller isn’t yet available. It is possible to run a different version of firmware on any UniFi device. Usually you would run the same version on APs, or your switches, but in some cases you may only want to test a new firmware in a certain location before rolling it out site wide (or to multiple sites). As of Controller version 5.4.2 we allow batch firmware upgrading via the controller UI.

There are three methods described in this article: via the controller Web UI, or via SSH either with the “standard” method or by a local upgrade. For more information on how to connect to a device using SSH refer to the Related Articles at the bottom of this article.

A Hue bridge and Unifi controller client. Enables/disables specified Hue schedules in the presence/absence of specified wifi devices on the Unifi controller. 0.4.2 Feb 10, 2019 0.4.1. Download the file for your platform. If you're not sure which to choose, learn more about installing packages. Files for huunifie, version. Error: Network error: Failed to fetch. Solution: Our UniFi - How to Remove (Prune) Older Data and Adjust Mongo Database Size article includes instructions and a script for database cleanup and reduction. Database Corruption. Issue: Database corruption can lead to a state in which the Controller cannot read the database documents.Typically this would throw errors in mongo.log or in server.log. When you click on Locate in the UniFi Controller software, the AP will blink. It will also display the location of the AP on the map. The 3.2.6 & 3.2.10 controllers have trouble with discovery on Win & Mac. Move up to the 4.2.6 controller - it will find the APs properly. For some reason chrome says that it’s being managed by an.

Table of Contents

How to Change the Firmware via the Controller Web UI

Applicable for: UniFi AP/UniFi Switch/UniFi Security Gateway/UniFi Security Gateway Pro

We’ve made it much easier to change device firmware via the controller web UI. For any unadopted device, you will have the upgrade option which can be performed before you adopt the device. This may help if you experience issues adopting a device.

For any adopted UniFi device you can easily upgrade or change the device firmware from the device properties window. This is found under either under Configuration>Custom Upgrade or Configuration>Manage Device>Custom Upgrade.

We’ve made it much easier to change device firmware via the controller web UI. For any unadopted AP and Switch, you will have the upgrade button in the Devices tab of the controller. You will be able to use this option even before adopting the device, this will be specially useful if you are experiencing issues adopting a device. Note: the upgrade button does not work for USG and USG-PRO-4.

For any adopted UniFi device you can easily upgrade or change the device firmware from the device Properties window. In the Devices tab click on Name/MAC address of the AP to expand the Properties panel. Select the Configurationtab > Manage Device > Custom Upgrade.

In this section you can enter a link that points to the new firmware version. Firmware links can be found on our official download page, HERE, and also within the release notes or firmware blog posts HERE.

How to Change the Firmware using the Standard SSH Method

Applicable for: UniFi AP/ UniFi Switch

Unifi Controller Download For Mac

SSH into the AP/Switch. For more information on how to connect to a device using SSH please refer to this article: How to Establish a Connection Using SSH. Issue the following command, making the necessary substitutions described below:

IP of Controller: is the IP address of the Cloud Key or computer where the controller software is installed.
8080: is the inform port for the devices to communicate with the controller. You should use 8080 unless you changed it manually when setting up the controller.
Binary folder: represents the model name of the AP or Switch. Check the table below.
Firmware version for AP or Switch: is the firmware version number. To find this navigate to /dl/firmware/FolderDevice ModelBZ2UAP, UAP-LR, UAP-OD, UAP-OD5 U2HSRUAP-Outdoor+U2IWUAP-InWallU2Sv2UAP-v2, UAP-LR-v2U7EUAP-AC, UAP-AC v2, UAP-AC-ODU7PUAP-ProU7PG2UAP-AC-Lite/UAP-AC-LR/UAP-AC-PRO/UAP-AC-EDU/UAP-AC-M/UAP-AC-M-PRO/UAP-AC-IWU7HDUAP-AC-HD US24P250US (all current models, with the exception of the US-16-XG)USXGUS-16-XG

Applicable for: UniFi Security Gateway/ UniFi Security Gateway Pro

Users upgrading a USG or a USG-Pro-4 must begin by going to an elevated console. So in the Command Line Interface you must type:

The USG will need internet access if the link used is not from a locally hosted FTP or HTTP server. Firmware files for USG and USG-PRO-4 do not come bundled with the UniFi Controller software due to file size constraints. You can download the required firmware files HERE.

How to Change the Firmware using Local Upgrade via SSH

Applicable for: UniFi AP / UniFi Switch

To perform a local firmware update, the firmware.bin file’s name needs to be changed to fwupdate.bin. So, what you need to do is copy the file from the appropriate directory of the controller—or from your computer if downloaded from our downloads page HERE. For the appropriate directory you can reference the binary folder table above.

For Linux you would:

Open Terminal and issue the following command, making the appropriate substitutions:

Where/usr/lib/unifi/dl/firmware/binary folder/firmware version for AP or Switch/firmware.bin is the path to the firmware file in your computer. If you have downloaded the firmware file from our Downloads page, the path must change to the saved location of the file.

For Mac you would:

Open Terminal and issue the following command, making the appropriate substitutions:

Where /Applications/UniFi.app/Contents/Resources/dl/firmware/binary folder/firmware version for AP or Switch/firmware.bin is the path to the firmware file in your computer. If you have downloaded the firmware file from our Downloads page, the path must change to the saved location of the file. The commands above will copy the firmware file to the required directory and rename it. You will now be prompted to enter the password that you use for SSH access. As you type, no characters will appear on screen for security purposes. Carefully enter the correct password, and press Enter. Then connect via SSH and issue the following command to initiate a local upgrade.

Applicable for: UniFi Security Gateway / UniFi Security Gateway Pro

The USG and USG-Pro do allow local upgrade, but you may want to use upgrade.tar for the file name instead of fwupdate.bin. You will have to place the firmware file in a writable directory, so use the following, substituting the admin-username with the appropriate name: /home/admin-username/

So the last part of the commands mentioned above would change. For example, for Linux the command would change from:

to

You need to run the command elevated. Assuming you’re in the home directory, and the file is named upgrade.tar then you would issue the following command:

This binding integrates with Ubiquiti UniFi Networks allowing for presence detection of network clients.

# Supported Things

• controller - An instance of the UniFi controller software
• wirelessClient - Any wireless client connected to a UniFi wireless network

# Discovery

Discovery is currently not supported.

# Binding Configuration

The binding has no configuration options, all configuration is done at the Bridge and Thing levels.

# Bridge Configuration

You need at least one UniFi Controller (Bridge) for this binding to work. It requires a network accessible instance of the Ubiquiti Networks Controller Software.

The following table describes the Bridge configuration parameters:

# Thing Configuration

You must define a UniFi Controller (Bridge) before defining UniFi Clients (Things) for this binding to work.

The following table describes the Thing configuration parameters:

Here's some additional notes regarding the thing configuration parameters:

#cid

The cid parameter is a universal 'client identifier'. It accepts the following values:

1. MAC address [highest priority]
2. IP address
3. Hostname (as show by the controller)
4. Alias (as defined by you in the controller UI) [lowest priority]

The priority essentially means the binding attempts to lookup by MAC address, then by IP address, then by hostname and finally by alias. Once it finds a matching client, it short circuits and stops searching. Most of the time, you will simply use the MAC address.

#site

The site parameter is optional. If you leave it blank, the client will appear ONLINE if found in any site defined on the controller.

You may use the site parameter as a filter if you only want the client to appear home if it is found in the site defined in the site parameter.

Additionally, you may use friendly site names as they appear in the controller UI.

#considerHome

The considerHome parameter allows you to control how quickly the binding marks a client as away. For example, using the default of 180 (seconds), the binding will report a client away as soon as lastSeen + 180 (seconds) < now

# Channels

The Wireless Client information that is retrieved is available as these channels:

Note: All channels with the Write permission require administrator credentials as defined in the controller.

#blocked

The blocked channel allows you to block / unblock a client via the controller.

#reconnect

The reconnect channel allows you to force a client to reconnect. Sending ON to this channel will trigger a reconnect via the controller.

# Full Example

things/unifi.things

Replace $user, $password and $cid accordingly.

Download Unifi Controller For Windows

items/unifi.items

transform/unifi.map

sitemaps/unifi.sitemap

Unifi Controller Mac Os