-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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 OS 4.0.3 EA release breaks UniFi integrations #116411
Comments
@Kane610 hi! could you please take a look on this one? integrations are not working but command line sensor (gettin additional infor from unifi api) working ok |
Early access is unsupported territory so this is always the risk. Do you run a local account or cloud account? |
Agree about early access, but this is preparaion to udm pro max migration coming tomorrow... i'm running local account. this what it shows in debug
|
same time unifi api replying back normally on
exactly as it was on unifi os 3.2.12 plus Unifi Protect version kept the same but it's not working as well as network |
Seems to be a problem setting up the websocket |
any quick fix solution? |
No. Need to figure out if websocket has been moved or changed or something. If you know how to use the browser developer tools you can play around in the unifi interface and look at the traffic to see if you can identify it |
so i got protect working - delete integration, restart ha and it got found automatically and integration started just fine. same trick not working for network. but i got new simpthom - integration entities got aliveevery 9-10 seconds. and went back to unavailable Recording.2024-04-29.214351.mp4 |
What does the log say? |
|
while trying to add network integration back it hangs for a long time and as a result |
This comment was marked as duplicate.
This comment was marked as duplicate.
having the same issue with this version of unifi ea in home assistant. interestingly enough a home bridge connecting to the same unifi version does not have the issue with its plugin. |
I would wager that Homebridge doesn't use websocket. Looking at the little data shared so far it's the webso ket connection which h fails causing a reauthentication which in turn causes the too many Auth requests failure |
I did try the whole delete, restart and re-initialize protect. It does not work for me. It won't login. So that does not seem to be a universal solve for protect. |
I was able to restore Unifi Protect by creating a new local user and reauthenticating with that. No joy on the network component but at least my doorbell works again. |
@johnmacfadyen blessed are you, I have tried everything and am without more access =( @to4ko If it helps, I can give access to a test UDM Pro |
Thanks for the hint, the new local user worked for me, too. FYI: Deleting the user and recreating it with the same name didn't work, not sure why. Maybe something cached on the HA side? |
@Kane610 Thanks for integration update! All working just fine!
not sure if this one should worry me or not but just in case :) |
The problem
Unifi Network and Unifi Protect are not working with Unifi OS 4.0.3
It gives next message
homeassistant.bootstrap] Waiting on integrations to complete setup: {('unifi', '1a32234bcdf065653f810dcdca0c68d3'): 33491.298705887}
and after some time hang totally
What version of Home Assistant Core has the issue?
core-2024.4.4
What was the last working version of Home Assistant Core?
core-2024.4.4
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
unifi network, unifi protect
Link to integration documentation on our website
No response
Diagnostics information
No response
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: