I have a person entity whose location is determined by a device tracker entity coming from the Life360 integration.
This device tracker entity occasionally has short-lived periods of incorrect location:
Here the person was at home during the 17 seconds that Life360 had a wrong location.
How can I make the person entity only change to a new state of a device tracker after, say, 20 seconds ? Any transient state change of less than 20 seconds should be ignored.
Many thanks!
The default consider_home for most HA device trackers is usually 3 minutes, though I could not find documentation for what Life360 uses.
To get more reliable person entity presence tracking, make sure to include at least one stationary device tracker like router or bluetooth-based trackers. Take a look at the Person integration docs to understand the order used to determine presence based on multiple sources.
I had a similar issue with my partner’s iPhone, and found the Arpscan tracker to be very helpful at eliminating those false “away” states.
There are four Members in my Life360 Circle, and I’ve not really seen issues like this with the corresponding HA device tracker entities. At least, I haven’t seen it often.
What is the radius of HA’s Home zone? Mine is 90 meters. If yours is much smaller, you might want to consider making it a little bigger.
The Life360 integration (like most GPS based tracker integrations) does not implement the consider_home feature. That is only required for integrations (like routers, ping, etc.) that don’t detect very well when a device has left the Home zone. I.e., these integrations are very good at knowing when a device has come home, but are fairly terrible at knowing when it has left home. Hence, they need an algorithm like this to make up for that deficiency.
