Unifi Network integration Failed to Connect

Third party integrations
21

From the beginning I have been using a local account created through the console’s local portal.

Just tried creating a new account from the local portal again and nothing has changed, still a Failed to Connect error.

22

Same boat here. Anyone found a different solution? “Enabling the local remote access” on 443 did NOT work for me either, still showing Unknown Error Occurred

23

After many months I finally found the solution.
Just create a local user in you Concole (e.g. UCK).
I did it through the UniFi mobile app, under Settings > Admin Management, making sure the Local Access Only option is checked. Then use this to login in HA.

1000030059
10000300591080×2125 117 KB

1 Like
24

Related question: Is it possible to add a remote console as a second Hub to the Protect Iintegration?

I have my home (local network) Protect integration set up.

I also have Unifi set up at a second site, and I have access to the console directly via IP and DDNS. But when I try to create a second Protect Hub in the HA integration, I’m running into the “Failed to connect” error.

  • I’ve logged into the console locally and created a local admin user with local access only.

  • I’m able to see the Unifi console login when I type in the URL or IP of the second site manually, and can connect using the local user.

  • However, when I input these into the Protect Integration, I always get a few seconds of spinning and then “Failed to connect.”

I’m able to connect to the Protect cameras remotely with the Generic Camera integration, but I’d like to get Protect set up so I can see the AI/motion detection alerts.

Edit: My god. 2 seconds after posting this, and it seems to work now.

What fixed it:

  1. Type in the url of the site without “https://”, e.g., “site.duckdns.org”
  2. Uncheck “Verify SSL certificate”
1 Like
25

I am getting the same Failed to Connect. I created a local user with Full Rights for the Network App, then tried to login with the same user in the console which worked. Then i went into the console of my HAOS and pinged my Cloudgateway to check if the IP is reachable, which came back with a IP is alive message. Then I went to the Integrations selected Ubiquiti>Unifi Network and then inserted the gateway IP of my Cloudgateway which i was able to ping. Then inserted the local user credentials which worked in the Unifi Console but i still got this error.

This is what is showing in the logs:

Logger: homeassistant.components.unifi
Quelle: components/unifi/hub/api.py:76
Integration: UniFi Network (Dokumentation, Probleme)
Erstmals aufgetreten: 17:00:23 (1 Vorkommnisse)
Zuletzt protokolliert: 17:00:23

Error connecting to the UniFi Network at 192.168.10.1:
26

Hey, to everyone who are still having this issue.
I finally got that resolved on my end.

OFC you need a local user that we all know :slight_smile:
This user needs to be an Admin type user with those permissions:

image
image394×196 1.39 KB

image
image372×368 2.86 KB

After that you should be able to add any Ubiquity integrations using creds for above user.
BUT! If you are still getting Failed to Connect error, this is what helped me:

  1. Reboot HA machine wait for everything to come back online.
  2. Restart Ubiquity Gateway

After that the integration worked like a charm!
Hope that helped someone!

1 Like
27

I’ve tried most of the steps above but I am still stuck on the same error message, but I don’t possess the possibility to “Restrict to Local Access Only” because I do not have the Unifi Console. I am running my network via a dedicated Unifi Network Server (Unifi Server version is: 9.0.108). Is it still possibly to make this integration work even though I am not using a Cloud Key/Unifi Console?

28

Is there any hope to a resolution on this?? I still can’t get this to work and am receiving the same error

29

Another one with same issue here…

30

Finally figured out what was going on. My HA box was in the DMZ zone, which by default blocks access to the Gateway zone.

A simple rule to allow HA access to the Gateway on port 443 did the trick.

Hope this helps others. It took some back & forth to figure this one out :slight_smile:

1 Like
31

It should work on self hosted controller as well. Are you running the hardware without a controller? Or is it a remote located server?

32

After far to many hours, this comment finally pointed out something that should have been obvious but I just couldn’t see…

The integration is asking for the hostname/IP not the url to the WebUI. :man_facepalming:

The integration adds the HTTPS when it tries to connect, which after adding it, the HA log’s showed… there were lines of connection attempts to ‘https://https://AHostnameHere:7777’

Cheers for fixing my silly problem :slight_smile:

33

For me it was the UniFi firewall I had set up blocking access to the Gateway port 443. I paused the rule and it connects now :slight_smile: