Life360 Device Tracker Platform

Third party integrations
2274

The last time I tried the integration again on my production system, it still did not work – constant error 403’s.

I was still running HA 2024.5.5. Based on recent comments, and the fact that it worked on my test system, which was running newer versions of HA, I upgraded my production system to 2024.7.4 today and re-enabled the Life360 integration. To my pleasant surprise, it worked!

The only thing I can think of is that somehow the TLS fingerprint changed due to changes in the latest HA versions. If so, maybe this will work again for most or all of us for at least a while until Life360 and/or Cloudflare gets upset with us again. Who knows!

FWIW, I doubt the difference between 0.5.2 & 0.5.3bx matters. I happen to be running 0.5.3b2. I’ll try to release it as 0.5.3 before too long.

EDIT:

Oh, and I might change the update period from 10s back to 5s.

1 Like
2275

Released 0.5.3

  • Delay & more retries for error 403 while fetching Member data
  • Fix bug when disabling account
  • Move “client” request to background task
  • Display retry attempt number in debug message
1 Like
2276

This would make sense why mine isn’t working still. I’m on 2024.6.4. 2024.7.0 breaks something for me so I haven’t upgraded yet. Maybe I’ll go ahead and try it this weekend. Do you know if the token i have saved will work or would I need a new one?

dj

2277

Phil I think you are on to something. I upgraded to the latest HA and my Life360 is working again.

dj

1 Like
2278

Is there a way to get the Life360 Zones into HA Zones? Or does it or will it happen automatically?

I just discovered I had a hard-coded zones.yaml file that was old and not being updated. I removed it from the configuration.yaml and restarted. Now HA only sees one zone: “Home”.

Thanks!

-Tim

2279

No. There used to be a way to get the Place details in the debug log, which was printed in a format that made it easy to copy & paste into a zones.yaml file, but that feature wasn’t added when I rewrote the integration from scratch recently.

2280

@pnbruckner, so are you saying the intgration is back? are the details in thew OP or do you have a link you can share to the repo?

I am on my last month of life360 and If the integration works again I will keep the dang service…

2281

It’s still not sure if it will keep working. We are testing it, but it has changed a couple of times now in the last few months. It has been working for some people again for 2 weeks now I think. But no guarantees.

2282

You can find the integration here:

pnbruckner/ha-life360: A Home Assistant integration for Life360. (github.com)

As @frits1980 says, no guarantees. Seems to require HA 2024.7 or later.

2283

Released 0.5.4b0
Released 0.5.4

  • Use UTC datetimes internally to avoid DST → Standard Time issues
  • Fix error due to breaking change in 2024.11
2284

Damn, seems like it broke for me… and now the 3b is not working either… :man_facepalming:

2285

What HA version are you using? I assume you mean it was working, but when upgrading to 0.5.4b0 it stopped working, yes? Exactly how did it break?

2286

Using 2024.11.1 and 0.5.4b0

Got the:
image

Noticed one thing…
Did a logout and login and it seems like its only works with verification keys.
It didnt even ask for password, instead it send me a verification key to my email…

2287

Fixed… Did the token variant… and now it works!

1 Like
2288

Anyone’s devices suddenly become unavailable?

Tried deleting the integration and connecting via the token method instead but still no dice

2289

Working here.

2290

User error I think! When trying with the token method, I wasn’t selecting ‘Done with accounts’ so it wasn’t saving it!

:person_facepalming:

1 Like
2291

Hello,life 360 not working with HA 2025.01
this error
Setup failed for custom integration ‘life360’: Unable to import component: cannot import name ‘LENGTH_FEET’ from ‘homeassistant.const’ (/usr/src/homeassistant/homeassistant/const.py)

2292

Thanks. I’ll work on a fix soon.

UPDATE:

Actually, that was fixed a long time ago. You need to update the integration.

2 Likes
2293

Could be setup specific, working fine for me after upgrade to 2025.1.