the best place for adding your +1 to issues is in the GitHub repo for the integration.
That way the core devs can see how many users are impacted, and, if relevant, which details you share regarding your setups
this space is more for free discussion (though yes, the devs are very active !) which is awesome indeed,
Solved my own problem. Reboot the unifi console as it appears it was an error with too many repetitive local logins.
Mines trucking along Marius. (it’s an SE, not a Pro, but the sensor is updating)
Yeah it’s really odd because was functioning properly before, and triggering my cooling fans.
I noticed now because the fans had been on for hours…
Really hard btw to find the temp in the UniFi app itself….
in the web interface we have /about-this-console
and there is the temp sensor:
which is a far cry from 48 C:
btw I did manually update the entity, but it doesn’t update at all
reloading the integration does update the temp sensor (the others were live so it seemed)
edit
opened an issue at : UniFi Protect Statistics Sensors are not Updating with Real Time Disabled · Issue #117324 · home-assistant/core · GitHub
edit2
seems the diagnostics sensors are not always update without having enabled the real time updating in the integration settings.
its been identified, hope it can be fixed, because enabling that causes some heavy lifting we didnt need before
I have been on a mission to clear up old abandoned entities attached to my Unifi Network. Mistakenly started here but finally found this thread and a thanks to a long read and the work of the addon authors I found out how to Enable a dead entity, restart, then delete that entity. That got rid of fifty… but still have three left. All are Windows laptops that have been on my house network and now gone.
I managed to get them Enabled fine, but the delete button will still not light up.
I assume that is because these are also in this list
So how do I take these three “network clients” off of this list?
Or do I need to “create entities from network clients” so I can then delete them?
And checked - these are not listed on Unifi Network Controller itself. So not sure where they are coming from.
-=-=-
My network changes a lot. Often have devices connect for a few days, then gone to never been seen again. I would love to have a way to setup an automation to say “delete entity if not seen in a week”.
Take them out of your UNIFI controller. They should show up as your offline clients. Once you do that, after a few synchs in HA, they will start getting listed to a point where you can delete them in HA.
AHA!! I’ll delete my other reply… only just found the ALL filter.
Thanks for poking me to look there again. I had looked before, but didn’t notice that drop down list that showed “1D”. The fact my laptop was not showing up as offline got me poking everything… and finally found these pesky items hiding. Didn’t realise “1D” meant a “1 Day” filter.
Once they were removed there, they disappeared from HA. Perfect.
I now have to find some way of automating the cleanup.
An ages-old thread, yes, but there’s some improvement:
Unfortunately it is only cloud API atm
Hey all!
Another month and Home Assistant 2024.8.0 release with changes in the UniFi integration.
Forgot to do a couple of these notes during the summer, but as can be seen below most have been revolving around improving test infrastructure stuff and bugs. As there are so many features that have evolved over time the tests where not as easy as they could be, and still aren’t, but they’re better than before at least.
We’ve got two new functional additions from the community; WAN latency sensors by @kimdv and Traffic rule switches which Bdowden who finished up a previous stale Pr by Vividboarder.
Thanks guys!
Try these features out during the beta, feedback is appreciated.
Cheers!
/Robban
Home Assistant 2024.6
aiounifi library v79 change log
For feature requests of the integration post an issue at aiounifi github
If you appreciate my work I’m on Github Sponsors.
Hi guys, first thanks a bunch for the awesome integration! Am really happy about it 
I have a quick question maybe one of you knows more about.
Since I updated to Home Assistant 2024.8.0 today, I see ca. every 10 sec in my HA logs:
2024-08-08 10:25:38.097 WARNING (MainThread) [homeassistant.components.unifi] Exception on update Call https://XX.XX.XX.1:443/proxy/network/v2/api/site/default/trafficrules received 401 Unauthorized
2024-08-08 10:25:48.100 WARNING (MainThread) [homeassistant.components.unifi] Exception on update Call https://XX.XX.XX.1:443/proxy/network/v2/api/site/default/trafficrules received 401 Unauthorized
The integration still seems to work fine and my Unifi entities still update. I did not make any changes to the my local ready only Unifi user and are not certain why authorization fails. Any input is appreciated and have a wonderful day
Edit: Looked at some other threads having similar issues and tried:
Not if this belongs into this thread, if not please excuse me and Ill remove it.
Thanks!
Hi Robban,
your work has been immense by the looks of that, simply amazing. thanks.
I noticed we get an event entity when someone rings our doorbell now (dont think that is even listed above 
) , which ofc is a nice feature.
These events are only created when actually pushing that button are they?
I started looking for events for the activated motion detections per camera, but then figured that might not be the usecase you’re all after?
Anyways, thanks for the continuous development, must be hard with such a huge integration and diverse product lineup
Which UniFi gateway are you running?
I think that doorbell is coming from the UniFi protect integration, else its pure magic
Riiiiight!
My bad.
Still, the integration works beautifully in 2024.8!
Thanks Marius! Its nice to hear a power user like you have no issues. Unfortunately its not the same experience for everyone right now 
@Robban, am using the cloud gateway max. Also update the other thread. Was not sure its the right place here. Anyhow, thanks
Edit: I tested some more and it seems that if I remove the integration and re-add it, it will fail if I use the same local user credentials as before. If I create a new user then and use that, I can connect just fine again but the same warning keeps coming in the logs. Let me know if there is anything I can do to help/ test.
Ok, then you have this issue Authentication error 429/421 with controls but status sensors are working · Issue #122438 · home-assistant/core · GitHub
We’re trying to figure out what the difference is when doing a toggle on the UniFi app and through the integration.
Thanks! Had quick look through the linked thread and will dig into it later but to note is that I use a local “read only” account and did not configure (at least knowingly) and toggles. My intention is only to read data such as number of clients, up and down speeds, loads on memory / cpu.
