Device_tracker: ignoring old position updates (from Life360)

@mikeage wrote:

Hi,

I currently use the Life360 integration to track a bunch of phones, but I’d like to ignore old reports. By that, I mean when the user has not connected to life360 for a while (perhaps their phone is off, out of service, etc). The docs mention a parameter that can be used to trigger when no update has been received:

max_update_wait

(time)(Optional)

If specified and Life360 does not provide an update for a member within that maximum time window, an event named life360_update_overdue will be fired with the entity_id of the corresponding member’s device_tracker entity. Once an update does come, an event named life360_update_restored will be fired with the entity_id of the corresponding member’s device_tracker entity and another data item named wait that will indicate the amount of time spent waiting for the update. You can use these events in automations to be notified when they occur.

There’s a sample there with sending a notification, but I’d really rather mark the device_tracker.life360_foo as unavailable or unknown or even a generic not_home (since, while they may be in the place reported, they might not as well, and we should fall back to a different device tracker if present for the person).

Is there any way to do this? It’s probably more of a generic device tracker question than specific for Life360, but this was the only one I found that even exposed “old” reports, so maybe not…

Thanks

Posts: 1

Participants: 1

Read full topic