-
-
Notifications
You must be signed in to change notification settings - Fork 29k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unifi Network integration fails to setup #117158
Comments
Hey there @Kane610, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) unifi documentation |
With what change did you experience this. What version of Unifi app and os are you running |
Unfortunately I am not sure when it happened as I do not rely on too many automations for Unifi |
What version of Unifi app and os are you running |
Unifi OS v3.12.12 and Network 8.1.127 |
Same here (HA Docker): Logger: homeassistant.components.unifi Seems like the port is missing after IP when connecting. Connecting should be: 192.168.1.1:443 |
I was / am having the same issue. Created new Local User on UDMSE after Early Access (I know, likely to break things!) install broke integration with needing new auth. New local account didn't solve after reboot of both devices. Deleted integration, but on re-add using the new local account I receive "Unknown Error Occurred" or "Invalid Auth" Network integration works perfect with same u/p. Unifi OS: 4.0.3 |
Lets keep this issue to be about Network, protect has its own implementation |
Based on this comment, does Network work for OP?
|
Sorry about that! Jumped in wrong repo! |
I have not upgraded to early access. Should I try deleting and then reinstalling the integration again? |
Just a random thought I had as I continue to research...starting to think that the issue may have started when I enabled MFA... |
The integrations expect local accounts which are not required to have 2FA enabled. |
Thanks. I just checked and I do have a local user setup for the integration |
Hey @Kane610, did you check on this: #117158 (comment)? |
I faced the same issue when creating a user for Home Assistant and found the following workaround:
I would assume provisioning users via SSH/CLI could be an alternate approach when the legacy interface is removed at some point. |
Good observation, the log could be clearer, the format of the log is |
As most people have reported it is working on both 3 and 4 right now I would make sure to properly restart all equipment to make sure its back in a known state |
Done already: Pulled new HA Docker image, deactivated HACS and all its integrations. Restarted UDM Pro, deactivated any firewall rules. Same result: ERROR (MainThread) [homeassistant.components.unifi] Error connecting to the UniFi Network at 192.168.1.1: By the way: the same problem exists with @homeassistant/components/fritzbox |
Having the same issue trying to set up the integration for the first time. Getting the following error message: 2024-05-16 09:36:38.035 ERROR (MainThread) [homeassistant.components.unifi] Error connecting to the UniFi Network at 192.168.36.1: Running HA on a Raspberry Pi 4 Unifi Network is on 8.1.127 running on a UDM-Pro running OS version 3.2.12. I have restarted the UDM-Pro, HA, and my Switch Pro 24 PoE and nothing changes. I can ping 192.168.36.1 from HA as well. Also tested the login credentials of the local admin I created and that works just fine. |
Probably unrelated, but the issue is on your side as it can't connect to the address. |
Are you sure its the correct address, not too common using a high number as 36 |
Yes, I use some odd numbers so I can tell what site is what and I don't end up accidentally making changes to the wrong site if I forget to switch between UDM consoles. |
The error seemed to be related to QNAP Container Station (Docker), when running HA in Host mode docker (lxcbr0). After the most recent firmware update, the connection can be re-established. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
I've been having this issue for about the same amount of time as others here. Getting 403 Forbidden upon login attempt. Agree it also appeared around the same time I setup MFA for my cloud users. I have a Here is the log for integration reload:
and the log for integration (re)setup:
|
Accounts with MFA is not supported by the integration. |
Thanks for the quick response! I've disabled MFA for my account and still getting the same error in my logs. I'll try to give it some time and reboot the UDMSE to see if it works. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
The problem
The integration has been working fine for over 2 years. Now I am not able to load the configuration even after creating a new local user in Unifi OS and using those login credentials
What version of Home Assistant Core has the issue?
2024.5.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Unifi Network
Link to integration documentation on our website
https://www.home-assistant.io/integrations/unifi
Diagnostics information
home-assistant_unifi_2024-05-09T20-15-57.791Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: