Download Firmware Unifi Controller
Sharyl Kimbro
If you have a local UniFi Network application and the UniFi devices don't have internet access, the application will store a copy to be used at a later stage. This will avoid multiple internet downloads for the same firmware each time.
If you have a HostiFi hosted UniFi Controller, there might not be much benefit in enabling firmware caching as the server is cloud based and will have to reach out to the internet. However, with the high speed network our provider Vultr runs, it might have some speed benefits.
To cache firmware, go to Settings > System Settings > Maintenance > Device Firmware Cache. Under the Available Firmware tab, hover over the Cache column of the device and select Cache. Under the Available Firmware tab, hover over the Cache column of the device and select Cache.
I am hosting an offline unifi controller using docker and it will never be connected to the internet. The unifi controller can easily be upgraded using the latest docker images however I haven't figured out how I can manage device firmware. My previous setup was building the unifi controller on an internet connected network and caching all the available firmware in the unifi UI. This worked great initially because some devices needed to be incrementally upgraded in order to get to the latest version.
Hi @snell,
I've just installed the unifi driver on my UDM Pro, and finally got the presence detection for my iPhone working after years of nightmares. So, thank you.
I also have the Protect ecosystem on my UDMPro, with a bunch of G3 cameras.
Are you interested in getting info on the cameras? I have 12 x G3Flex and 1 x G3 Pro (so it has the Zoom feature)?
I cannot get my Unifi Protect Controller device to access info from my Protect cameras. The problem is that I have vlans set up, #20 for my IOT device which includes Hubitat and #30 is for all the Unifi cameras. I have firewall rule that does not allow IOT devices access to gateways.
I need some info on how to make a firewall rule that will allow Hubitat only to access the correct vlan gateway so I can connect to Protect. I am not sure if I need to access the camera gateway or the main gateway that the Unifi equipment is on. I believe I need the main gateway because the Cameras are on a vlan but the Protect controller is on the UDM Pro on the main gateway #1.
I know enough about vlans and firewall rules to be dangerous and really screw up everything. I followed Youtube videos to set up everything up and pretty much understood what I was doing but this is a horse of a different color. When it comes to IP address and ports I get confused. Any help will be appreciated.
Normally the firmware of your UniFi devices is updated through the console. But sometimes we will need to update the UniFi Firmware manually. For example, when you are unable to adopt an access point.
After you have started the firmware upgrade you will lose your SSH connection. The device will update the firmware and reboot once completed. It can take a couple of minutes until the upgrade is completed.
also how do i update my waps after i update the controller as as you can see all the waps are on v3.9 (under firmware) so i want to update them to a new firmware as i have one new wap i purchased yesterday and thats got v4.0.6 or something
Your cloud key is whatever's running this controller. It appears to be the UCK, which was the first generation. It may be capped at an older Unifi Controller version, I'm not sure they're supported anymore.
On the Maintenance tab at the bottom it has a Firmware section. If the latest firmware show up there then you can cache it by clicking cache on the right of that firmware. It will then pull from the cache rather than redownloading it each time. As i have a fast connection here i just download for each AP rather than caching them. Usually the firmware is less than 10mb depending on AP.
The controller allows you to access and manage your devices. You could remove it from your network and everything will still work fine. You will not be able to make changes though unless you go through a process to reassign the waps (which is a huge pain in the ) to a new controller or you plug the controller back in.
You can upgrade to a custom firmware by going into the device(wap) and clicking the gear (center button) for config. Scroll to the bottom and in manage device there is a custom upgrade. You can pull the URL from Ubiquiti Downloads Opens a new window page. Choose your exact model of wap and when you click the download button it will give you a download link. Just copy and paste that to your custom field and it will update.
BIG WARNING - If you do the above and use the custom firmware update option it may break your connection to the controller. You may pass the controllers ability to talk to the waps. This is why i mention upgrade through the controller then keep updating through the controller. It keeps the firmware's lined up so you keep access to your devices. I have had to factory default and ssh downgrade a wap to get it to register to a controller again (not a fun process).
My scenario now is, my controller is on a certain version and so are my old waps connected to it but they can't update to a later firmware (new waps have new firmware) as the controller hasn't got the updated firmware for the waps
ok so on the webgui on my cloud key, i cant update the cloud key firmware or the controller at all on the web, so i think the only way to update is via ssh into the cloud key and do both the firmware and the controller
It should download the new firmware from Ubiquity downloads and then install them. You can go to the downloads site and click download then accept. It will pop up a window with the URL to direct download it. Run the command and paste the URL at the end to update to whichever (recommend the latest) firmware you want.
I have a setup at a customer's site, where I have a cisco rv320 Router with 4 VLANS. Behind the router, I have Unifi switches, which as controlled by unifi controller. The VLANS created on the switches as in "VLAN only" mode, which means, the gateway (CiSCO Router) is the gateway along with DHCP server for those VLANS. I have disables inter vLAN routing on the router. So the VLANS are isolated. It works great. However, when I replaced the Cisco router with TP-Link ER7206 router along with Omada software controller, everything works as far as creation of VLANS. However, in switch ACL (Which is the LAN port of the TP-LINK router) the deny rules from source VLAN to Destination VLANS don't work. Every VLAN is able to reach every other VLANs. There is no isolation. Therefore the ACL don't work. How do I resolve this problem?
Can you tell us a little more about your UnFi setup? Are these new APs? Or are they currently/previously adopted on another controller? What about your controller? Is this a fresh install or did you restore from backup?
Scenario
Make: Ubiquiti
Model: Ubiquiti Unifi Controller, Unifi UAP-nanoHD
Mode: CLI (Command Line Interface)
Version: 6.0.43
Description: This article contains a detailed stepwise method to upgrade the firmware of a Ubiquiti Unifi Controller. It is really important to keep the firmware of devices up-to-date and we would definitely need to upgrade the firmware of the Unifi Controller someday. Hopefully, this article will be helpful to many.
Step1: Firmware version
It is recommended to check the release notes of the unifi firmware before the upgrade. Check the current firmware version of the controller and to which next or latest unifi firmware version you would like to upgrade. The unifi firmware version can be checked at unifi software download centre.
Step3: Unifi Software Download Center
Access the Ubiquiti unifi software download centre and copy the URL of the firmware which needs to be installed on the controller. Follow the steps shown in the image below
Step8: Confirmation
Once the software is 100% downloaded successfully [as shown above] onto the controller, then we would need to install the downloaded software and make it as primary software to load. Follow the command shown below.