Now, any UniFi device (which isn't adopted yet) will automatically show up in the controller as 'awaiting adoption', just by powering it on and connecting to the network. In meraki, for example, the method is to use a CUSTOM code, use #43, and HEX, and then add the following: '01:04:xx:xx:xx:xx' (without quotes) where the last 4 'xx's are the IP address of your UniFi controller in hexadecimal format. In such a case, you can use DHCP option 43 to inject the IP address of your UniFi controller. Instead, most deployments of UniFi involve other manufacturer's firewall/routers and UniFi switching/WiFi equipment. The USGs (USG, USG-Pro, USG-Pro-4, USG-XG, and UDM/UDM-Pro) are mostly unsuitable for enterprise networks, as they lack a number of features and are difficult to configure for failover and other complex network configurations.

In addition, there is another method that is more suitable to most deployments, since most IT professionals do not use the UniFi Security gateways. Excellent rehash of what Ubiquiti reports on ui.com (formerly ).

Unifi discovery chrome