Hide upgrade available notifications when the installed version is newer than the published version. This applies to device updates as well as controller updates.
"Update available" is listed when the current controller version is newer than the 'available' version:
The desired behavior would be for the upgrade notifications to be present only if the available version is greater than the currently installed version for the controller or device.
I have a company with 15 sites.
I label things like "android-dd0e4a5827ff4139" to more useful things like "Big boss phone"
Can you PLEASE make it so that custom device names are tied to the MAC address of those devices AND also make it controller-wide? If "Big boss phone" moves to a different site, it doesn't show "Big boss phone" it shows that "android-dd0e4a5827ff4139". I have to re-label it for every single site.
Trying Controller versions (even stable ones) beyond what is the default inside of the Cloud Key firmware always results in a controller downgrade on the next Cloud Key firmware update. Since Controller downgrades aren't supported this means you then need to immediately go back to the Controller you were on and then restore from backup. This takes a silly amount of time.
Can we have Cloud Key firmware updates just not mess with the Controller version if it is newer than what is bundled? This would not only save time for those bothering to jump through these hoops currently but would likely encourage more people to try newer stable Controller versions.
An option in the unifi voucher manager page to delete multiple vouchers without pressing each time one by one to delete, for example an option to delete all used, and an option to delete all the vouchers the new ones and the used ones all together,and the expired too ofcourse, without deleting one by one, its a top requested feature by many business , hope very soon to see this. example in the picture above.....
Transfer clients trying to connet to a device for example ( UniFi AP-AC-Lite ) that at certain time its maximum concurrent clients capacity has been surpassed. as i describe below....
Organizing and changing like this the site names and in subcategories will give a big advantage even with thousands of devices and installations will be mush more fast and ofcourse no errors or meshing up diferent site confiqurations or no finding the correct site name .... example in the photo below
UniFi Controller > Statistics > Switch Stats
Current Switch Stats graphs show volume of traffic passed over time which provides a view of data flowing in network.
What it lacks is true port utilization. Example, is the interface shown below reaching 100% utilization here or not?
You would need to use some math to determine this answer today because the graph just says it's passing about 29 GB of traffic every 5 minutes for several hours.
Feature Request 1: graph switch stats as utilization by percentage of interface's speed (0%-100%). This allows you to identify ports that are saturated and may be causing preformance issues. If a port can send 1Gbps and it is, the graph would show 100% utilization. This new view would be selected using a persistent per-user setting. So when I login, my default view for switch stats would be ports by utilization, but other users can continue using ports by volume graphs (if they wanted) as both view can provide value in their own way.
Feature Request 2: Graphs can be shown using fixed y-axis scaling. This lets you quickly visualize which port is causing the largest load on a given device (one with tallest graph). This is hard to visualize today because each graph is independently scaling so they all look equally utilized when in actuality, some ports are flowing GB and others MB. This would enhance request 1 above also.
The Controller must have a simple way to define time slots as well as firewall rules and associate a rule to a slot.
This is simple to implement.
A little more complex is to have a report/gui that shows at a certain point in time which rules are actives. This because in complex scenarios it could be difficult to understand what's going on. Also to avoid conflicting rules.
it is possible but is NOT a way to go as is too complex:
Custom range of ip per wlan ssid
wlan ssid : floor 1 ( ip range xxx.xxx.xxx.xx2 - xxx.xxx.xxx.x50 )
wlan ssid : floor 2 ( ip range xxx.xxx.xxx.xx51 - xxx.xxx.xxx.x80 )
wlan ssid : floor 3 ( ip range xxx.xxx.xxx.xx80 - xxx.xxx.xxx.x254 )
For models that support wireless uplink and/or mesh uplink, I need the ability to set the ethernet port to a VLAN.
This would be great to handle via
- in the unifi device config
- or even a text box in the device config to enter cli configurations that survive reboots.
Currently you need to enable guest policy restrictions to enable this feature. It would be nice to be able to set this independent of the guest policies. (I understand you could just remove the ACLs and enable guest policy for this but that is unintuitive.)
Many other guest pass systems allow you to specify the expiry time by either creation date or the first use date.
This is similar to other requests to speficy an exact expiry but this would be simpler in the UI for many users creating the guest passes.
Scheduled Firmware Update.
I'm sure I'm not the only person in the whole forum who experienced the following:
We left our Automatic Update on and once we updated our controllers, within seconds all the SSH connections with the server is disconnected because APs went into upgrading mode and Wi-Fi is down. A few minutes later, branches across the country or even the world call and complained that their Internet went down for a few mins.
To counter this problem, I'll suggest the following improvements:
1. Add an option to select the scheduled update time under the Automatically Update Firmware column.
2. The update time selected follows the time zone which was configured for the sites. This ease the job for IT if they have overseas sites to manage.
Non Destructive AP Update.
As we all know, if we leave the Automatically Update Firmware checked, all the APs will all go down at the same time and we will lose all Wi-Fi access for a few minutes before they came back up when a new firmware arrives. This is a large problem because someone might be doing something when the update is rolling.
My suggestion is:
1. Create a database so that the Controller knew which AP is nearby to which AP. Other than that, the controller needs to know which AP can takeover another AP's load if one went down (eg during Upgrading).
2. Update only selected APs at any one time so that this allows other APs to come in and take over their load while they are being upgraded. This reduces impact on the clients. They will simply roam onto another AP when the original AP is undergoing upgrades.
Support this idea by giving it a kudos if you think this is useful for you!
When using very expensive backhaul bandwidth, it would be great to have my UniFis tell my users' Android and iOS devices that they are on "metered bandwidth", which causes them to stop trying to do software updates, photo uploads, etc over this connection.
Android requires that DHCP option 43 be unconditionally set to the string "ANDROID_METERED". More details can be found at: http://www.lorier.net/docs/android-metered
iOS apparently sets an Apple-specific flag in the 802.11 beacon. There's a little more detail in: https://apple.stackexchange.com/questions/199163/how-does-ios-and-os-x-detect-when-a-wi-fi-network-is-a-personal-hotspot/200854
Hi guys, is there any chance Ubnt can make a function similar to Aruba's Adaptive Radio Management or Ruckus's Channelfly? This could help people with dedicated UniFi Controller to have better performance and allows the UAPs to optimize themselves (controlling Transmit Power and choosing the best Channel) automatically preventing interference from each other without needing a IT. This could really help when it comes to large deployment in companies, saving their IT hours of walking around with WiFi Analyzer tweaking the WiFi. As we all know, as of now setting Transmit Power to Auto is essentially setting it to High and this problem has been known for years. I guess this is a change that benefits most people.
5.3.8 seems to have introduced a feature not present in 5.2.9, and not mentioned in the release notes where it generates an alert on detecting a rogue AP.
These notifications are not helpful in an environment where your buildings are surrounded by other buildings that broadcast the same SSID. In my case, part of a University where different departments have their own wifi system but we all broadcast the same University-wide networks in addition to our local ones.
Equally this could be an issue for small businesses in built up areas who use popular 3rd party providers for guest access (such as The Cloud)
Within a minute of upgrading to 5.3.8, I'd had 45 notification emails (before disabling email notifications - which now means I can't tell when an AP has crashed or been unplugged), and the notifications continue to roll in on the console every time it refreshes.
So a config option please to revert back to the earlier behaviour of not being notified of rogue APs (at least until the more complicated idea of being able to mark rogue APs as good) would be perfect.
I recently added a UniFi Switch 8 POE-150W to my network and in the process I moved my Cloud Key from being USB powered on an unmanged switch to POE+ on the UniFi Switch. After this process the Cloud Key continually flashed white and would never go blue.
I was able to access port 443 but not port 8443. Additionally the Cloud Key continued to report offline in the https://unifi.ubnt.com site. I was able to SSH into the device and it appeared that the Mongo DB had become corrupted (although I'm not 100% sure on that).
I searched around for a bit and found other users reporting a similar issue. The only solution I saw was to reset to factory defaults or restore from backup. Not having a backup (my bad) I had to reprovision the network
Long story short the Cloud Key should be able to better handle a hard power loss...
- Andystebbins on: Hide "upgrade available" notifications when installed version is newer than the published version.
- Chubs on: Secondary (Lan) Port on AC LITES
- slooffmaster on: UniFi mac addresses across sites (custom device names)
- Dave-D on: UniFi - All SSIDs stop broadcasting when the UniFi controller is shutdown
- Dave-D on: Firewall Zones
- EDPR on: Password requirements
- wayneco on: Unifi POE Router
- michaeldimoudis on: REQUEST: iOS app support 2FA
- rdahlin on: Add channel utilization history to either Performance or Debugging area
- yonhmaikel on: Time control / parental controll
- Speed Throttle when it reached a certain volume of data (Hotspot)
- USG Support for Freedns.io Dynamic DNS service
- FIXED RADIUS time outs
- configurate wifi by authentication via radius
- GUI App to generate .jason file for Unifi controller
- SNMP v3 support
- Port Forwarding - Enable\Disable in USG Config GUI
- Backup to external location
- support edge max devices
- Restrict/Allow Subnets