Thank you very much.
First of all for the reference to the old directory entry and secondly, thank you very much for your correction. It works perfect.
1 Like
I specifically used my email address to provision the app, not phone number (you have a choice). It then insists on doing the 2fa thing, even though I never specifically set this.
I have a terrible feeling this isnât going to end well for the HA community⊠Its a worrying trend now (Chamberlain MyQ garage door api as an example)⊠I sincerely hope this is just a minor glitch in the matrix 
As i new user running HAOS all i can say is Home Assistant makes zero sense. I had Life360 working, but itâs like there is no trace of it. Iâve installed Samba share, terminals, studio code server and nothing what so ever returns anything about Life360. Entering this in terminal
find / -name life360
Does nothing, doesnt even return an error.
Everyone talking about manifest files, Life360 folders, api.py files and none of that exists despite Life360 being installed. Struggling to comprehend why i canât simply navigate to a file somewhere and just edit or replace it.
This is just my opinion, but most of the install methods are more âlocked downâ, mostly to make them easier to âjust useâ, but also, I guess, to help prevent users from âshooting themselves in the foot.â These workarounds are really intended for advanced users, who have, over time, learned the ins and outs and tricks of how the system works internally. And even many of them have shot themselves in the foot when attempting this sort of thing, mostly by forgetting to undo the temporary workaround when the formal fix comes out.
If youâre new to HA, I would not recommend attempting to apply a workaround. Just wait for the next release, which hopefully will come out soon. The fix has already been accepted and staged to be part of the next release.
Reinstall with GitHub - pnbruckner/ha-life360: Project for testing significant changes to the Home Assistant Life360 integration worked for me.
1 Like
Thank you Phil, confirmed that I removed the life360 folder from the previous âfixâ and restarted HA and the integration is working for me now.
1 Like
Phil, thank you for your continued support in getting this situation resolved at least for most of us. Iâm using ProxMox running HAOS. I too was not able to find any of those life360 folders. Ultimately, I used ha-life360: Project for testing and finally got things working again.
Just to be clear, in the future when the new life360 is updated with the patch, do I need to delete the /homeassistant/custom_components/life360 folder that was created, or just leave it be?
Appreciate your time and effort in this. Thanks again!
1 Like
very true. 
I originally switched back to your custom integration since the last round of bug fix iterations were coming pretty quick.
hopefully this fix lasts until the next HA release (which I likely wonât upgrade to until the end of january since thatâs the way I roll )
Iâve already started to reverse engieer the 2FA authentication methods and have exposed the APIs to do this, just need to figure out how to generate some unique IDs which will probably involve decompiling the mobile app.
There would have to be a number of changes both in the python module and the HA integration though to implement that as itâs not a straightforward task.
1 Like
See my comment above.
Having said that, youâre free to continue using the customer version of the integration (i.e., ha-life360) if you want. It does have more features, especially for dealing with multiple Life360 accounts, Members in multiple Circles, etc. It was intended to test features & implementation I was going to submit for the built-in integration, but decided it was too much to try to get accepted. I will try to maintain it to keep it working, but probably nothing more.
And to be clear, if you have a custom integration installed, with the same name as a built-in integration, it will be used instead of the built-in one.
1 Like
I tried that in the first place and did a reboot. Didnât work, unfortunately.
Thanks a lot Patrick.
This worked for me. So basically, I removed the previous integration, deleted the life360 folder from the config folder, and then restarted the HA.
After that, I downloaded the zip file and put the life360 folder into \config\custom_components, then restarted HA.
at the end readded the life360 integration, bang worked 
I did exactly as you described @aliaghil and it work 
@pnbruckner when the official fix comes out, should we remove the life360 folder from custom_component?
I guess you might have already said it somewhere⊠and sorry because I guess Iâm forcing you to repeat yourself againâŠ
See my comment three comments back. 
1 Like
The reason you do not see the files is because you are likely inside the supervisor and not the home assistant container, so you need to go into the docker container of home assistant. That is why you need to follow the instructions of @mobile.andrew.jones
At the prompt type login and hit enter to get a linux shell.
Type docker exec -it homeassistant /bin/bash to get into the bash shell of the home assistant container.
cd /usr/src/homeassistant/homeassistant/components/life360/
run the sed command.
exit twice
restart home assistant.
2 Likes
Good morning, this morning I still have authentication problems, I have installed the latest version of your custom. Until a few days ago everything was ok
same for me âŠ
when can we obtain a new release 2023.12.4 to definitively resolve the Life360 problem??
Am not sure what exactly is going on here. Many people have success. I donât seem to
Despite uninstalling, and re-installing the patch several times, I still canât get this to work. I think, during this process, I reset (tried to) my password, and life360 have now disassociated my account
Then, I got this response from them this morning. Very disappointing.
We understand the importance of using the Home Assistant program with Life360. However, we want to inform you that we no longer support home automation programs such as Home Assistant, Google Home, Alexa, IFTTT, and others, and these programs are no longer compatible with Life360.
Currently, we have no plans to reintroduce compatibility with these programs. Nonetheless, we appreciate your feedback on this matter, and I will share it with the appropriate team.
If you are running Virt Env config, itâs located (most likely) at the below location.
/srv/homeassistant/lib/python3.11/site-packages/homeassistant/components/life360
Also, if you check
ls /srv/homeassistant/lib/python3.11/site-packages/life360 <Tab twice>
You should see two folders, one is something like life360-6.0.1.dist-info. It did not update to 6.0.1 for me until I went to add the life360 component again. If you already have it added and donât want to remove/readd, you can probably go through like youâre updating HomeAssistant, but instead of HomeAssistant, put the package name as life360==6.0.1. Like below.
sudo -u homeassistant -H -s
cd /srv/homeassistant
source bin/activate
python3.11 -m pip install --upgrade life360==6.0.1
Unfortunately, Iâm still not operational, still scanning to see if I missed anything else, and Iâve read you can get locked out after so many bad auth attempts, so that may be my problem at this point.