This is, as always, is maybe more of an aide-m\u00e9moire for me, but may be helpful if someone else is searching for a solution…<\/p>\n\n\n\n
Here is the scenario: My UniFi devices are on a separate subnet from my UniFi Controller. The problem, if you will, with this configuration is that when a UniFi device looks for the UniFi Controller is that is cannot find the Controller on a different subnet.<\/p>\n\n\n\n
There are a number of ways that this can be resolved (other than putting the Controller on the same subnet) as documented in UniFi – Device Adoption Methods for Remote UniFi Controllers<\/a>. The option that I took, or maybe it is two options, is:<\/p>\n\n\n\n One important thing to remember: If you statically <\/strong>set the IP addresses of your UniFi devices you will not get the DHCP Option 43 provided to the devices.<\/p>\n","protected":false},"excerpt":{"rendered":" This is, as always, is maybe more of an aide-m\u00e9moire for me, but may be helpful if someone else is searching for a solution… Here is the scenario: My UniFi devices are on a separate subnet from my UniFi Controller. … Continue reading unifi<\/code> to resolve to the UniFi Controller. That way when a device restarts (such as after a reboot, power loss) it can find the controller when it boots and executes the set-inform http:\/\/unifi:8080\/inform<\/code>. The hostname unifi<\/code> will resolve to my UniFi Controller.<\/li>01:04<\/code> to the hex<\/em> version of the IP address of your UniFi Controller. Browserling has a page to convert the IP address to hex: Convert IP Address to Hex Format<\/a>.<\/li><\/ol>\n\n\n\n