It seems like I’m having some issues with the Unifi presence tracking component. My known_devices.yaml file is being created properly at startup and updates as soon as I put a new device on the network.
Home/away status does not seem to be functioning correctly. My android shows as away even though its being reported as connected in the unifi controller web interface. If i toggle the android’s wifi connection off then back on I will see the status in HASS change to home for approximately five seconds and then change back to away. Whenever my android’s status in HASS changes to home I see all the other tracked device’s status change at the same time, I see the same behavior five seconds later when my android’s status change’s to away.
Not quite sure how to go about debugging this issue. I’ve mimicked the code in components/device_tracker/unifi.py and can see the devices being reported correctly when scan_devices() is ran. Any ideas would be greatly appreciated!
I did try to add owntracks tracking but that didnt have any affect on the weird behavior from the unifi tracking, now its just the unifi module doing presence tracking.
Thanks for the reply Landrash, it looks like it may be an issue with the unifi controller itself.
I was correlating times between my phone connecting to WIFI, changing state in HASS, and changing state in the unifi controller when I noticed my phone stays in the Unifi’s connected client list for a varying amount of time. The first iteration it dropped off the client list approx two minutes after disconnecting from the network, the second iteration took closer to five minutes. Interestingly enough the uptime value in the unifi controller was very accurate, the uptime for my phone didnt continue to advance while the other devices in the client list that were still connected to the wireless network did.
I’m currently running the Ubuntu version 4.8.02 of the controller, just checked their website and I see that version 5.0.7 is out, I will try to upgrade and see if responsiveness improves.