Life360 no longer reporting movement

1

Hi All,

I noticed my automations (node-red) that leverage Life360 stopped working. It took me a while to figure out why this is and discovered the Moving/Driving attribute is not being updated. I had created a binary_sensor to track moving and ultimately how I discovered it wasn’t being updated.

I’m using 117.2 core currently and the last time it was working was Oct 26th. I’m using the HACS addon for Life360 and was previously using the custom component (this was months ago) and up until recently was working perfectly. I run it via Docker and it’s updated via ouroboros nightly if an update exists. I do not know which version I was running on the 26th when it was still working but I do know it was working in 116.x

The app itself works fine on my phone and my automations do recognize all the data from life360 (read in via device_tracker into node-red) but the moving/driving attribute is not updating and tracked over the last 48 hours it remains false (I know I was moving/at work/etc :slight_smile: )

My only config for Life360 in configuration.yaml is:

life360:
  driving_speed: 10

And the default in HACs addon of “enable newly added entities” is set to true/on.

Is there anything further I can do to help troubleshoot the issue?

Thanks!

EDIT: Linking to @pnbruckner in hopes to catch his attention on this :slight_smile:

2

I’m github challenged – is there a place I can post this as an issue specifically for life360 there?

3

Did you ever figure this out? I think I may be seeing the same but never had it working so less sure. I created a template sensor and it seems to only show false and unknown.

4

Was just trying to figure this out as I thought it’d be interesting to mess with. Looks like he got a github issue opened here [https://github.com/home-assistant/core/issues/42936] and it was closed stating driving appeared to be working, but moving did not appear to work. Probably a limitation of the reverse engineered API they are using, unfortunately. Mine doesn’t appear to show true for driving attribute either, but I just set it up so maybe I’m missing something in my config.

5

Was thinking of trying to figure this out based on changes to address and last update but haven’t had time to figure it out yet.

6

It used to work. I was using it in a node-red automation where it factored in whether the device was moving or not (it reduced false positives hugely) and one day it stopped updating. Driving still works for me but my kid only drives on the bus to school so not really useful to me as a whole :slight_smile:

As stated in the github issue, it is what it is. I would love to have it back again but I ended up changing the way I determine movement (good old haversine) and seems to be working pretty well but I’m guessing I’m a very small minority that used this to begin with.

1 Like