No, I havent. Only thing I added later on was a POE Switch. Well, and several cams obviously
as for the LL-HLS, I am using default_config, and that contains stream, which in itself sets true by default to that option? Stream - Home Assistant
tbh, the lag is ok, I can see my permanently streaming cams alright, and yes, there is a few seconds of real time delay when in fact streaming. nothing we can do I guess
so, if I would add a secondary UNVR, that would take a lot of the heavy lifting from the UDM-pro, and also run the Protect software from that machine?
It would then also lower the memory utilization?
Iâve updated to 2024.5.1 and I still have the same error with Unifi v4. The error states âInvalid Authorizationâ. I have a local user created and everything worked prior to Unifi v4.
Same issue for me
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,
3 Likes
Solved my own problem. Reboot the unifi console as it appears it was an error with too many repetitive local logins.
1 Like
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
1 Like
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.
1 Like
An ages-old thread, yes, but thereâs some improvement:
1 Like
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
- Use MockConfigEntry in tests
- Use runtime data
- Use fixtures to setup config entries
- Improve config flow tests
- Use fixtures in update tests
- Use fixtures in switch tests
- Use fixtures in service tests
- Use fixtures in diagnostics tests
- Use fixtures in image tests
- Use fixtures in sensor tests
- Use fixtures in device tracker tests
- Remove old test infrastructure
- Rewrite the button entity tests
- Rework tests to not use runtime data
- Fixture cleanup in tests
- Add sensor for number of clients connected to a device
- Clean up config option tests in device tracker tests
- Break out switch availability test to separate test
- Enable statistics for remaining power sensors
- Improve device tracker client tests
- Add one sensor test to validate entity attributes
- Make services handle unloaded config entry
- Add newer models to integrations discovery bdraco
- Reject small uptime updates for clients @wittypluck
- Simplify uptime sensor test
- Improve device tracker tests Pt1
- Improve device tracker tests Pt2
- Fix bad access to runtime_data when not assigned
- Mark power cycle button as unavailable if PoE is not enabled on port
- Use snapshots in update tests
- Use snapshot in device tracker tests
- Remove unused fixtures in tests
- Remove last references to hass.data[UNIFI_DOMAIN]
- Use snapshot in image tests
- Small speedups bdraco
- Use snapshot in button tests
- Cache device_tracker properties that never change bdraco
- Add Traffic Rule switches bdowden & vividboarder
- Add latency sensors kimdv
- Improve fixture typing
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.
8 Likes
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:
- restarted the Unifi console/ controller and HA
- removed the integration and re-added it with a new Unifi local user
- made sure SSL is not checked in the integration
- am only using Unifi Network application
- My UniFi OS version is 4.0.6
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
1 Like
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!