I feel like this should be straight forward, but its not working.
Im trying to set up the unifi integration.
I have a Cloud Key Gen 2 set up as the controller.
I enter the IP address of the controller in the host line.
Then for the username/password, Im copy pasting the credentials that sucessfuly log me in to the controller at the above IP.
So I tried it via configuration.yaml. In the previous hass.io version, it would just give me an error upon restart and not work.
This time, I got a “new devices found” message so I was thinking it worked. But then it just took me to the integration page, where it showed up under unconfigured. And then Im back to the same issue, where it gives me “bad user credentials”
And I cant install it via add-ons because the webui wont show up, since Im using hass.io cloud. So yeah.
…where you choose whether to Configure the Cloud Key (hardware) or Manage the Controller (software). The Controller is what HA needs access to so look at the port number in the URL after you select ‘Manage’ (it’s probably 8443).
Have port numbers (they are there by default) for both setups. Still get the same issue with our without. How do I verify Im using the correct port? (although it should be 8443…)
I’m not familiar with the gen. 2 CK, maybe they changed the default port number?
You need to look at the port number in the URL after you select ‘Manage’. It should be something like; https://192.168.1.7:8443/manage/site/default/dashboard, where 8443 is the port number.
If you have more than one Site configured in Unifi you might also need to add the site_id, which is default in the example URL given above.
If no port # is showing then the default for SSL connections (https://) is being used, which is 443.
It seems unlikely, but 443 might be forwarded to another port in the CK by default. You’d need to check your port-forwarding settings in the Controller to confirm. <-- Scratch that, it wouldn’t matter anyway. HA should still be able to connect.
I have a completely seperate login for unifi local access (which is my ubiquity login) then I do for cloud access (admin/password). It makes no sense. But finally got it to work
Ok so I spoke to soon apparently. I got the integration to work. But when I add the device tracker (with the now working login), I get the following error:
Failed to connect to Unifi. Error:
You will need to restart hass after fixing.
Weird. Ubiquity may have changed methods used to remotely access the Controller with Gen 2. Maybe someone who has experience integrating that specific model will chime in.
You might want to update the post title to include Cloud Key Gen. 2…?