Any idea if this could work? I’d hate to have to go back to seeing multiple ssids at home… lol! 
Can you open an issue on aiounifi on GitHub and give a bit more detail, how do you set it up, how it looks on the interface and also provide the logs. This is possibly a bit of work.
Can this integration read Unifi errors? My dhcp-server breaks down once in while and the error is in Unifi logs . I’d like to set an automation to reboot the router when the error occurs in Unifi logs.
Probably. It is not supported today.
Hey all!
Another month and more UniFi functionality for Home Assistant 2023.12.0.
One major new thing is the new way to configure what clients should produce entities, it’s now just an opt in by selecting specific clients. The old options to configure clients will be removed down the line.
Starting this summer @herriejr worked hard to implement traffic rules support and got completed a few weeks back. He is now working on the integration side, keep a look out with future Home Assistant releases to use @herriejr work.
Try these features out during the beta, feedback is appreciated.
Cheers!
/Robban
Home Assistant 2023.12.3
Home Assistant 2023.12.0
- PoE power cycle button
- Refactor internal naming function @akx
- Handle forbidden errors “403”
- Normalize unique ID generation
- Make WLAN clients numerical
- Make RX-/TX-sensors diagnostic entities
- Fix clients stuck in options
aiounifi library v67 change log
For feature requests of the integration post an issue at aiounifi github
If you appreciate my work I’m on Github Sponsors.
3 Likes
Hey all!
Another month and some new changes to UniFi for Home Assistant 2024.2.0.
@wittypluck provided a couple of nice improvements to some poorly behaving sensors, making the uptime sensors more stable not overpopulating the database as well as improving the behaviour of the bandwidth sensors to report 0 if no data has been sent for some time.
There have been a few issues reported from multiple users about something looking like the web socket stops sending data after an undecided amount of time. I have not been able to reproduce it myself or figure out the core issue. Thought to have been affected by one recent upgrade of UniFi OS or App there have also been users reporting it being resolved by upgrading to latest or downgrading to 3.1.16, YMMV. If someone is a bit proficient in these technologies and experience the issue your help would be appreciated.
Try these features out during the beta, feedback is appreciated.
Cheers!
/Robban
Home Assistant 2024.2.2
Home Assistant 2024.2.0
- Reset UniFi bandwidth sensor when client misses heartbeat @wittypluck
- Mark Unifi bandwidth sensors as unavailable when client disconnects @wittypluck
- Reject UniFi uptime sensor updates if time delta is small @wittypluck
- Change behaviour of a 403 forbidden message to retry connection
- Add debug log to show last received UniFi web socket message
aiounifi library v70 change log
For feature requests of the integration post an issue at aiounifi github
If you appreciate my work I’m on Github Sponsors.
3 Likes
Was the ability to control traffic rules ever implemented? I can’t seem to find it (2024.1.6). Thanks!
1 Like
It’s in draft but nothing has happened for some time Add Traffic Rule switches to UniFi Network by ViViDboarder · Pull Request #104671 · home-assistant/core · GitHub
edit The author just had a child so a bit preoccupied for the moment.
3 Likes
The way the integration adds devices is quite problematic and it still does not remove devices.
The way the integration adds devices is quite problematic because it add devices that have at some point connected to your network, but were never properly identified and probably will never be connected again. I found a bunch of these devices in Unifi Network which just had a mac address but no other information.
I discovered that I could actually delete these old devices in Unifi Network which is why they don’t appear in the above screenshot. I was hoping that they would be removed from the Unifi Network integration, but alas they remain as noise in the system:
It seems that reconfiguring the integration will add more devices (and entities) but not remove them. I have now tried several ways to configure the integration with less and less boxes checked, but no devices ever seem to be removed.
Seems like the only alternative I have now is to remove the integration and reinstall it 
1 Like
Why is the installation configuration of the integration different to the configuration available after it’s installed?
The installation configuration does a better job of adding devices than configuring after installation, however it automatically detects devices and does not allow you to remove it from the list it wants to add to HA. It only allows you to add/change the room where the devices reside.
At least the re-installation has removed 50-60 rubbish devices that I didn’t want but I still have 20 more or so that I would like to get rid of. However there doesn’t seem to be any way to remove these devices?
This has come at a cost of breaking a bunch of automations because of changed entity names.
Installation and configuration are two separate flows. Configuration was added at a different point in time with the purpose of giving more fine granular controls.
I want to simplify the configuration options and also try to combine installation and configuration in some way.
I agree the flows should be the same.
I just found this issue now which answers my other question:
It’s unfortunate the automatic removing of devices is broken and there is no way for users to selectively remove devices. It means that some of the new functionality is less useful because it creates spam devices.
Anyways I resolved my biggest issue by making the configuration in Unifi Network import the way I want it to appear in HA without modification.
Your kid is more important than my integration issues. Enjoy parenthood @Robban!
Thank you! He is finally back to normal.
Not sure if bug or config issue my end:
I cannot get device tracker away status to track fast/reliably enough for what I’m trying to automate.
When a device gets marked as offline in the network application, it remains “home” in the device tracker for x amount of seconds as defined in the configuration options(300 by default). If I lower the threshold to 30 seconds or lower, I see devices repeatedly flip home/away despite remaining connected to the network.
I think I know why this happens, i.e. phone sleeping wifi etc.
But how is it the integration doesn’t match the status of the device in the Network Application?
Perhaps long term users of the integration might shed some light.
Is there a config setting I am missing?
EDIT:
In an attempted workaround I set up remote syslog and looked at “associated” and “disassociated” events. This works quite well for stationary devices - but not for devices roaming between APs. It seems with self-hosted Network Application installs, remote logging comes directly from the APs, and not from the controller application itself. I wonder is there any way to access the controller logs directly in Home Assistant?
I could possibly be better off just setting up ping sensors but if there was a way to do this with the info that’s already there with the network application addon I’d love to utilise that.
If my experience is anything to go by, the author of the traffic rule PR will certainly need this in ~13 years time to bring control to their teenagers rampant gaming addiction 
1 Like
Small fix to improve websocket stability with 2024.2.2
1 Like
Was wondering if you’re planning on integrating the ability to automate WIFI password changes? Specifically interested in this for the guest network.
There is an intent, but not a plan
Hey all!
Another month and some new changes to UniFi for Home Assistant 2024.3.0.
@layertwo has laid the foundation for controlling LED of UniFi devices, it will show up in a future release.
There have been multiple threads as well as issue reported on upcoming requirement of MFA to the cloud accounts, make sure that you are using a local account as that is the only supported path.
Still haven’t figured out the cause of the intermittent disconnects happening to the websocket, users have reported. Change to the websocket configuration to take compressed data to see if that has a positive effect.
Try these features out during the beta, feedback is appreciated.
Cheers!
/Robban
Home Assistant 2024.3.0
aiounifi library v72 change log
For feature requests of the integration post an issue at aiounifi github
If you appreciate my work I’m on Github Sponsors.
1 Like
Hey @Robban, did you ever get to look into toggling traffic management rules? It would really help me solve a couple of things
Cheers,
Linton