Person.entity_id + life360

Configuration
1

It’s my understanding that the person entity reports either “home” or “not_home”, as stated in the documentation.

I’m hoping to use Life360 as the tracker, as we already use it as a family and it was always accurate when I used it with SmartThings.

The problem appears to be that the person entity, when updated by Life360, shows the Life360 status directly, which is home, away, moving and driving. According to the Life360 documentation, it looks like I can fix this with the “show_as_state” variable, but is there another way to default the person entity to home and not_home?

2

No, it can also show the state of the GPS-based tracker when you’re not home, which might be the name of a zone, or for life360, it can be moving or driving as well (if you have it configured to show those states.)

That’s not a problem with the person component. That’s how it’s designed to work.

I wouldn’t call it “fixing.” Basically, the life360 integration is fairly flexible and you can configure it the way you would like it to work. If you don’t want it to show moving or driving as its state, then don’t configure it to do so.

In general, I have to ask - if you’re only planning on using life360, then why even use the person component? It may have more features in the future, but right now it’s really designed for combining multiple device trackers.

If you really want an entity per person that only shows home or away, then use a Template Binary Sensor with a device_class of presence.

binary_sensor:
  - platform: template
    sensors:
      me:
        device_class: presence
        value_template: "{{ is_state('device_tracker.life360_me', 'home') }}"
3

This…is a good question, lol. It didn’t even dawn on me, I’ll just forgo the person entity and adjust my triggers to fire on the Life360 status’s.

Thanks for the template as well, I’ll be sure to implement that!

1 Like