There should be away to provide controller redundancy - currently if the controller goes off line (hardware crash, or service shuts down), the access points go into autonomous mode. This means guest networks end up either being locked out, or if access is granted there are no limitations (other than restricted networks, etc).
Please consider implementing the ability to have redundant controllers - a primary and secondary source. So that if the primary is offline, the AP contacts the secondary. Synchronization of the primary and secondary controller should be easy enough to arrange.
It would be nice if making UniFi a Windows service was simply part of the installation process, instead of having to use the steps outlined in the knowledge base.
It would be nice if Ubiquiti standardized the way that they allowed custom SSL's to be installed.
It would be really great if the UniFi backend portal could be integrated with a LDAP (or ActiveDirectory) infrastructure. Being able to assign sites and privileges based on LDAP/AD username or group membership would be amazing.
Almost every other software package we use has this ability and has greatly reduced the burdon on securing everything (Remembering to go through every package we use and deactive accounts when someone leaves), and it means the end user only needs to remember one username/password combination. Adding/removing a user from a system is in a centeralized place.
Forgive me if this request already exists -- I didn't see it while searching. You can delete this if I'm doubling up.
As it stands now, I can enable a guest network, but my settings for that (hotspot, portal, etc.) are SITE-WIDE. I've often encountered where I may want to have an encrypted guest network with no portal, along with an open guest network -with- a portal, agreement, etc.
I'd -much- prefer SSID-specific settings vs. site-wide settings!
It would be awesome if the firmware handling of the controller could be beefed up significantly.
First, firmware and controller software needs to be decoupled. Noting which version of firmware is optimized for which controller would also be nice so if you are running and older firmware and a feature doesn't work it could be tracked down more easily. Now done - UBNT can now release new firmware without updating the controller - but these newer firmware releases are not downloaded and distributed from the controller which causes problems for Unifi gear that does not have Internet access. So we are part way there. This makes my next request even more important:
The controller needs to be able to download and cache multiple versions of firmware, especially if you are working with the devs on hotfix firmware.
Building on the ability for the controller to manage multiple versions of firmware, the ability to group APs and assign particular groups of AP's a particular firmware version would also be very welcome.
This would allow people more flexibility in upgrading some or all of their APs, or quickly downgrading if they run into issues with newer firmware.
Also having in the controller notations about best known stabel versions, most recent with most features but a few outstanding problems, vs. custom uploaded hotfix/alpha firmware would be amazing.
There are now enough devices with enough different firmware versions out there that each have pro/cons to using over others or even the most current that some help from the controller in managing and tracking all of this would be very, very welcome! Especially for the really large sites out there.
Add an option for each AP in UniFi Controller to view nearby Wifi networks (SSIDs, Channel, Signal Strength, etc.) like in AirOS.
May be very usefull to help avoid overlaps and interferences AP per AP without having to move physically on place.
We have so many APs on a map, that the details layer is overloaded.
I'd like to be able to show a user heat map, a bit like the coverage map layer to show where a quantity of users are logged on. Perhaps a ring system around each AP with definable steps (e.g. 1 green ring for 5 users, 2 green rings for 10 users, a 3rd amber ring for 20, a 4th red ring for 30 etc).
This would help see if I have enough APs in a densely used area of too many in another.
Just a thought!
Support for more than 4 SSID's per radio.
UniFi Enterprise WIFI products should support more than 4 SSID's per Radio.
Enterprise products of other companies like HP or Cisco also support more than 4 SSID's.
Would like to see LDAP as a supported authentication method for cleaner integrations with Active Directory and other environments.
We need to know the temperature of our unify switches. If something is failing because of heat or is running to hot, we need to be able to act on it before it becomes a problem.
1. Temperature alarms should be configurable as well
2. Historical temperature data
Actually this should work on ap, routers, switches, etc.
As crazy as this request may sound, please consider creating UniFi firmware for the Nanostation M2.
I love the UniFi system, but I also love how well the NSM2 works as a low cost outdoor sector AP. I have many customers happily using NSM2 as an AP, but I really wish it could be managed by UniFi.
UAP-Outdoor with an external sector antenna is overkill and not economically feasible in most settings I encounter. NSM2 w/ UniFi firmware would be an ideal solution.
Recently Wifi schedule was introduced, which allows you to turn on an SSID for a time period during the day. Unfortunally, it does not exactly match my needs. Typically I turn on my AP early in the morning (7:00 AM) and turn it off after midnight (1:00 AM). The current WiFi Schedule feature allows you to only configure one "on" time period; for my case I want to turn "on" between 0:00 and 1:00 AM and 7:00AM and 23:59PM. OR in other words, I would like to be able to configure an "off" time period (between 1:00 and 7:00 AM). Basically I need an "inversion" of the currrent feature. The way I envisage this is a checkbox on the right side of the sliders which allows you to indicate if the time period "slice" should be considered as "On" or "Off" time.
Can you please considere as feature enhancement for the next update!!!???
I want UBNT to take the next step and release a VMware Linux OVF UniFi Controller package that we can simply import into our existing VMware environments. I want a prepackaged Controller that requires very little setup.
If you want to own the enterprise space, this is a necessity. If you don't know it's a necessity, you need to hire someone like me. I've got a hundred ideas like this floating around in my head, but I'm usually too busy to take the time to express them.
Currently, as per the discussions in this thread, the controller binds to all IP addresses available on the host system. The port the server runs on is already configurable through the system.properties file, however the IP address is not (system_ip= is not used for this purpose). Currently therefore, the controller binds to the same port on every IP address.
I propose that the IP address be made configurable to bind to only a single IP if required. This would allow the the controller to run on say port 443 whilst another service, such as a web server, was also listening on port 443 on another IP address.
We need a way to clear stats per client and to be able to "forget" a client entirely.
Clearing stats zeros out upload, download and connection history except First Seen and Last Seen dates.
Forget also erases any aliases or notes, essentially all data about that client is erased- the next time they connect it would be as if it were the first time.
I'm currently coding a custom portal to match our internal way of authorising users.
The basic functions around allowing a guest are documented in some code, but I had to resort to reverse engineering of the web interface for stuff like POST /api/upd/user/517f75fXXXXXXX HTTP/1.1 (to update the name, note of a user)
A good documentation would really help in dev and maintenance of such custom portals.
Sometimes it is necessary to migrate sites or an entire controller to a new controller. Maybe you are going from a local machine to an AWS instance, or you want to split a large controller into multiple pieces.
You can manually load a backup into the new controller, that is easy enough. What may not be easy however is updating all the UAP if you do not have a VPN into the network or you have manually adopted them instead of using DNS or DHCP options.
What I would like to see is a migration tool built into the controller which you can basically move Site X to Controller Y, and this tool updates all UAP on Site X automatically like any other config change. UAP provisions with new controller and links right up. It would also copy all other settings like WLAN Groups, Guest Portal, config.properties, etc.
- Hsd1965 on: How to build catfish function for wifi marketting
- Tommy885 on: Show Load Average On USG In Controller
- CRnapa on: Going Green Request: Guest/Hotspot Voucher issue via Email
- garretth on: Request - Web content filtering
- swilkey on: Unifi controller and firmware updates for devices
- ZSN on: Wireless broadcast exclusion
- flopp on: Delete/Hide Sample map
- reedy on: UniFi Cloud Key Bundle UniFi SDN Controller 5.9.x
- NaNUnifi on: Assign Multiple Sites to a Single Dashboard
- Marcn5 on: Clients bulk remove
- How to build catfish function for wifi marketting
- Enable Kernel Extensions to run Docker on Cloud Key
- Manufacture Date
- Request notification email when WAN2 on USG-PRO is turned on as failover
- Feature Request - Further Statistics
- Allow to connect vlan network in the portal or guest
- Show Load Average On USG In Controller
- Wifi time schedule issue
- Going Green Request: Guest/Hotspot Voucher issue via Email
- Request - VPN (L2TP) Customization