*** Official Ubiquiti Discussion Thread ***

I can see why, per site you configure the USG and in a multi sited business yes you'd want each site to be on a different range but not having a way of grouping the sites so that some settings are universal, wireless for example. Is a real pain.

There's a customer we have who would really benefit from this and currently whilst the platform is great and working for their APs, being able to shove USGs in just as easily would be the cherry on the icing.
 
Thanks, my preferred ceiling location is actually blocked off from the loft due to the way the built the extension so access there is tricky.
 
Upgraded my controller software and AP firmware this morning and was frustrated to see that the custom names I had set up for a lot of the devices on my network have reverted back to default. Grrr.
 
Upgraded my controller software and AP firmware this morning and was frustrated to see that the custom names I had set up for a lot of the devices on my network have reverted back to default. Grrr.
I've learned that ubnt updates are best left unless there is a feature you really want or the firmware fixes something broken.

Had so many problems with AirOS over the years.
 
Upgraded my controller software and AP firmware this morning and was frustrated to see that the custom names I had set up for a lot of the devices on my network have reverted back to default. Grrr.

I've seen a few people complain of that happening on teh Ubnt foruns, nto specific to whatever new version youre on, it seems to happen to some people irrespective of the version. As far as I know Ubnt haven't found the reason for it.

I must be one of the lucky ones, I'm usually on the bleeding edge versions of controller and firmware and am yet to have the issue.

Does it make any difference if you import a controller backup from previous version?
 
Upgraded my controller software and AP firmware this morning and was frustrated to see that the custom names I had set up for a lot of the devices on my network have reverted back to default. Grrr.
Do you have some super complicated names for your devices that might make something wig out? I've never had the issue but i only use simple short names, just a guess.

Just installed 5.6.15 they are really rounding out the software, no idea why the controller ain't on the testing repo and you have to manually install though.
 
Last edited:
https://community.ubnt.com/t5/UniFi...able-Candidate-has-been-released/ba-p/2056618

Just updated mine without any issues, it was a lot quicker than the 5.4 to 5.5 update. The extra features in the GUI are really helpful, as it means I can trim my custom JSON code back quiet a bit.

Notes:

  • As always, make a backup prior to upgrading.
  • 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).
  • 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 SSID set to use VLAN 10, I cannot use VLAN ID 10 for RADIUS controlled VLAN users as those users will not get an IP.
  • Smart Queue QoS is similar to the implementation as in EdgeOS (see HERE). Please note that DPI will not work when using QoS, as traffic will not be offloaded. It's also worth noting that maximum throughput will be affected when using QoS, as traffic is not offloaded. There are some rough guidelines in the article linked above.
  • DFS channels can not be used for wireless uplink in the US. Please use non-DFS channels if you need to use wireless uplink on dual band UAPs.
  • Official UniFi MIBs can be downloaded from HERE and HERE (those are 2 different files).
  • We no longer support Java version 6, it needs to be 7 or later. We recommend Java version 8.
  • Features like airtime fairness, bandsteering, load balancing and minimum RSSI are default disabled. If you need them you need to go to Settings>Site and check Enable advanced features.
  • If you previously used Google Maps for a site map, then you have to enable this feature again by adding an API key. This is done under Settings>Controller. There is a linked guide with instructions.


Important Notes:

  • The initial database migration will take longer than normal. It is expected to see mongo using most, if not all, of the available CPU cycles during this process. Please be patient, this process could easily take 15+ minutes, depending on the amount of historical stats, as well as the system specs. As always, err on the side of caution, and make a backup before upgrading.
  • The controller will not start if it is set to bind to a privileged port (<1024), as it now runs as a non-root user. There are various ways you can fix this immediately, like authbind, although there may be better ways. We're considering options here.
  • If your controller is running on a UniFi Cloud Key (UCK), make sure it is on firmware 0.6.4 or later, otherwise the controller will not start. This firmware is available via the normal upgrade mechanism found in the controller or it's local management page. Make sure to make a backup before upgrading the UCK firmware, as you'll need it to restore after, and it's good to have a backup on hand before any controller upgrade.


Known Issues:

  • Manual site-to-site VPN status is not reflected on the UniFi dashboard widget. Currently it will look like it's offline, even when the tunnel is up.
  • AirTime will not work if a radio is disabled and/or there isn't any SSID present. This will be fixed in a future release. If you enable it, and it still isn't working, then you may need to force a refresh without cache.
  • If you start both a 2.4GHz and 5GHz scan in quick succession, then it will fail.
  • It is expected that AirView will stop occasionally. A stop/start sequence should restore functionality.
  • If you start an AirTime scan while AirView is running, then AirView will stop and you'll need to perform a stop/start sequence to get it working again. This will be fixed in the future.


New Features:
  • Add AirView for UAP-SHD.
  • Add AirTime for UAP-SHD.
  • Add Switch Port Profiles.
  • Add RADIUS-based authorization in Hotspot.
  • Add new type of map with predictive coverage.
  • Add Ubiquiti store (buy devices directly from the controller).
  • Add EDU SIP settings.
  • Add Facebook Wi-Fi Authentication (Beta).
  • Add DPI blocking per categories.
  • Add LLDP-MED configuration.
  • Allow configure 8 SSIDs per radio (on supported devices).
  • Add Insights / Controller Logs page.
  • Add USG Performance Graphs.
  • Add temperatures to USG-Pro properties window.
  • Add LAN traffic statistics for client in Property Panel.
  • Add Debug Dashboard to Statistics section.
  • Batch add and remove device tags.
  • Add permissions options when inviting a site admin (device adoption, etc.).
  • Add Outdoor / Indoor Switch.
  • Add NTP server fields.
  • Add batch device provision.
  • Add DB migration page and show upgrade progress.
  • Add date header to email notifications.
  • Install and run service as `unifi` user instead of as root on Debian/Ubuntu.
  • Add Logging settings.
  • Add batch edit switches.
  • Add UPnP service (moved from config.properties).
  • Add Multicast DNS Service (moved from config.properties).
 
Hey everyone, my current setup is Netgear D7000 for the modem, and an R8000 for all the wireless, but they both transmit there own wireless channels. Having terrible trouble with them this weekend, which seems to me a good excuse to upgrade the system. Currently looking into a "mesh" system. I have read into this Ubiquiti and would appreciate some advice before going ahead with an order. Does this transmit the netgear wireless network and extends it, or does it create its own network and handles its own handovers across each unit?

I live in a large 4 bed house, so advice on the kit required would be great.

Thanks All
 
Hey everyone, my current setup is Netgear D7000 for the modem, and an R8000 for all the wireless, but they both transmit there own wireless channels. Having terrible trouble with them this weekend, which seems to me a good excuse to upgrade the system. Currently looking into a "mesh" system. I have read into this Ubiquiti and would appreciate some advice before going ahead with an order. Does this transmit the netgear wireless network and extends it, or does it create its own network and handles its own handovers across each unit?

I live in a large 4 bed house, so advice on the kit required would be great.

Thanks All

You disable the wireless on your router and let this deal with it.

So you configure your wireless networks (SSIDs) within the controller software, adopt your access points and then they'll transmit. You will need a switch to uplink them.

I believe the seamless handoff requires a local controller to be online, but most devices handle this better themselves anyway ruling out the requirement for it.
 
Are you referring to Ubiquiti Amplifi?

If you're looking at any mesh system expect to replace all of the existing wireless, and possibly the router as well.

Why don't you start a new thread and see if you(we) can address the problems you're seeing with the existing kit. It's not exactly junk.
 
I got back from holiday to find I've been sent a beta sample of the US-24-250W from Ubnt. I'd regsitered my interest on the forum a few weesk ago but didn't realise I'd be getting one. I like free stuff!
 
You disable the wireless on your router and let this deal with it.

So you configure your wireless networks (SSIDs) within the controller software, adopt your access points and then they'll transmit. You will need a switch to uplink them.

I believe the seamless handoff requires a local controller to be online, but most devices handle this better themselves anyway ruling out the requirement for it.

Zero-handoff is a thing of the past now. UBNT themselves actually recommended you no longer use it as it degrades performance. They have now built it into the wifi protocols for fast roaming.
 
Zero-handoff is a thing of the past now. UBNT themselves actually recommended you no longer use it as it degrades performance. They have now built it into the wifi protocols for fast roaming.

Hence:

"I believe the seamless handoff requires a local controller to be online, but most devices handle this better themselves anyway ruling out the requirement for it." :)
 
Back
Top Bottom