Life360 Device Tracker Platform

Didn’t worked for me (Docker version)
Still the same error message :frowning:
Tried several times

I should note, that I had actually deleted the integration from Home Assistant yesterday, so after I made the change and restarted I then added the life360 integration. And it all worked happily.

I’ve done the same on HAOS and doesn’t work for me, password won’t authorise. Are you using a paid life360? I’m not so wonder if this is also part of the issue

My account is not a paid account, but I am in a bubble created by a family member who is paying. So I don’t know if that makes any difference.

1 Like

This worked for me as well - ty!

1 Like

I’m on HAOS on an x86 NUC, i have a paid account and i cant get it to work after hours of trying. But i dont even know if i’m doing it right or not. I’ve tried Studio Code Server to execute the commands. I get issues, but probably not even in the right spot.

1 Like

Not working for me either. :worried:

Docker installation. Downloaded latest HA image. Ran.

Docker exec -it home-assistant /bin/bash

Ran sed command. manifest.json now shows:

"requirements": ["life360==6.0.1"]

Restarted HA from web UI.

HA configuration directory contains life360 folder with previous fix and api.py version July 30, 2023 and 8,271 bytes.

I did login to Life360 web and fixed my password (apparently needs to be more complex now). I used new password and still getting the auth failed message. BUT… when I tried to login to Life360 web it is telling me my password is incorrect again… :frowning:

Reset my password AGAIN. Am able to login AGAIN on Life360 web. Still auth failed on HA Life360 reconfig. I am logging in with my email on both web and HA - I assume that is correct since that is what I have been doing all along…

-Tim

1 Like

I’m using your custom Life 360 integration on home Assistant 07.2023 and it works perfectly, thanks for your work

1 Like

You’ve applied two different workarounds. If you want to use the workaround that updates the built-in life360’s manifest.json, then don’t also add a life360 folder to your config folder with the updated api.py file.

I’ve tried it both ways - no luck.

Same here. Changing the manifest to 6.0.1 and doing a password reset didn’t work. I still get authentication failed.

If I want to install Life360 on HAOS from scratch (with the fix) - can somebody to point me to documentation - I believe I need to download some files to life360 directory

It looks like when I tried to fix Life360 on my own, I deleted the whole directory “life360” i Home Assistant

Thanks

I have a HA Container install and just tried the commands above from phil in the docker shell for HA and restarted HA. Unfortunately it didn’t work.

Any suggestions from someone who has tried it in another way and got it work reliably?

I didn’t remove and re-install the integration. Is that a required step?

I didn’t have to reinstall no, just docker exec to get a command prompt inside the HA container and ran the 2 commands, followed by a restart. Am am on the latest bersion of HA so not sure if that makes a difference

I’m still getting authentication issues.

Can confirm updated the manifest.json to 6.0.1. And rebooted multiple times
Have changed my password in Life360, logged out and logged back in on my phone.

Still getting Invalid authentication.

Do you have an entry in the logs?

Found my issue, and this may be part of what others are running into as well.

I updated the manifest.json file, but I still had a life360 folder in /config/life360 with an old api.py file from August. Thinking back, I believe last time this happened with Life360, the fix was to add that folder with contents to the config folder. So even though I was updating manifest.json, the config/life360 folder was overwriting it.

Deleted /config/life360, rebooted, and confirmed working.

5 Likes

I had this as well. After updating manifest.json, delete this entire folder in /config/life360 with the previous fix from July 30, then reboot. Was able to log in right away.

That wasn’t exactly it but that pointed me in the direction.

I had installed the previous fixe as a custom_component and I completely forgot about it being there. I deleted that folder from the custom_component folder and after a restart it’s back to working again.

Thanks, Phil! :+1: :+1:

1 Like

If you’re taking about my ha-life360 custom integration, you could have just updated it, since it also has the fix. Lol! Glad you got it working.

1 Like