You cannot install UniFi controller on your router. Use something simple like RPi for that if you really need your controller running 24x7 or install it on your desktop if you need it only for occasional configuration changes and maintenance tasks.
Unifi Controller is a controller to all unifi devices which is connected by API so each devices doesn't have to run web server (which is lighter). Usually it's installed in desktop for fire and forget management, but there are some cases where unifi controller installed in mini server or stand alone device for cloud based management and other function like hotspot control.
Extra effort must be made to make adoption work when running in Docker. The default network type for Docker (bridge) means containers are not accessible on the network. For Layer 2 adoption, the documentation for Jacob Alberty's image mentions using host networking or the macvlan network. I've used host networking with this Docker image in Linux and it works well, however at the time of this writing (2022-04-10) host networking is not available in macOS Docker Desktop. I haven't tried using macvlan but it might work well (with either image, even though the LinuxServer.io documentation doesn't mention it). For Layer 3 adoption, it looks like you must enter the Docker host's IP in the UniFi Network Application's settings (the documentation for both Docker images has details of where to find the setting).
You can also run the Network Application "headlessly." I haven't tried it, but the instructions at -the-unifi-controller-headless-on-mac/ look promising. Note that you'll need to use a different exec string than the ones suggested on that page.
This is a parent/child set of drivers in order to read data from your Unifi controller (originally based around my Unifi Dream Machine Pro but now expanded to other Unifi controllers) and provide some information that may be useful to your Hubitat. Like most of my drivers this will be a perpetual project and I am always open to feedback.
Also it might be wise to separate out the system info from device count polling options. When i ran in debug, it brought back a lot of data for all my devices which was great, but i want System health every minute, but don't need the firehose of device data as often. Just a thought. Might be more impactful for bigger networks.
I'm going to be setting up my Unifi stuff this week, using a non-UDM/P controller, and I'm wondering how similar the APIs actually are. It looks pretty minimal in terms of path differences, but I haven't even begun to poke at it.
I have the same problem, when trying to start the UniFi interface
Java-based controller in web browser I get: Cannot access this website.
But I do the same procedure on another computer without Kaspersky protection and it starts normally.
I should have mentioned I did try that IP, which is the IP of my windows machine running the controller. So, I think it must either be the wrong login credentials (UN / PW) or the wrong Port. But I suspect the default 443 Port is probably not the problem. So, most likely bad credentials. Ubiquiti / UniFi has separate login credentials for the controller app and the online account - tried both of those. Also tried the Home Assistant login credentials. Any other thoughts?
Comprehensive network customization has always been a touchstone of the UniFi Network application, and a guiding principle for our developers who work tirelessly to refine it. However, providing such an immense degree of user control can sometimes complicate our larger pursuit to simplify IT for every type of user. We want our settings to provide a wealth of options while also being easy to navigate and understand. Otherwise, network optimization is only possible for the most technically adept.
UniFi is a community of wireless access points, switches, routers, controller devices, VoIP phones, and access control products. It can be used for the corporate network and also for the home network. An Unifi network controller manages all the equipment in the UNIFI network. The best part of the Unifi network is that its controller can be hosted online with a Ubiquiti account using an Unifi Cloud Key, giving online access to the network to manage the Unifi devices and the connected client so can handle most of the operations remotely.
Having an UniFi Controller on the cloud allows us easy deployment of hardware. On any UniFi network where we have UniFi Security Gateway (USG) Installed, any UniFi equipment plugged into the network is immediately recognized by the Unifi Controller and is also ready for adoption. Whenever the controller adopts the device, the device receives the correct configuration and comes up in the network within a short period.
In the UniFi network, the user can see everything going on in their network, from connected clients, total traffic to speed and throughput tests to information broken down into individual protocol using deep packet inspection available right in the UniFi Controller. UniFi Controller offers information about your network, how it is being used, and that insight can optimize the network for better efficiency.
df19127ead