configuration.yaml
When a GPS tracker from the Home Assistant (official) app "freezes" and remain stuck at the Home state, and haven't reported for 24+ hours, and at the same time a Unifi device_tracker have reported not_home within the last 2 hours, the Person entity is stuck at Home.
As I read the documentation the Unifi sensor should have precedence in this scenario.
If I misunderstand the documentation, then I'm sorry - but the Person entity should represent the latest device_tracker state if the GPS report is too old.
I'm experiencing the same issue. I have my person set up with a unifi device tracker, and the official home assistant android app gps device tracker. Note the unifi device tracker shows away as expected, but the gps tracker does not.
Despite the GPS tracker reporting before the unifi device tracker it's still used for my person, and showing me as "home" (when I am in fact not home)



If there is anything I can provide that will be useful please let me know.
In the mean time I think I may remove the gps tracker from my person, as it is currently unreliable
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Still same issue on 109 branch.
Same issue. Document said stationary source must be priority over gps but it's not.
Same issue here:
Pixel 2 XL with Home Assistant App & Unifi tracker (using UDM-PRO)
Unifi correctly reports "not_home" but it doesn't seem to override the GPS previous "home" report.
Most helpful comment
Still same issue on 109 branch.