I’m sorry it’s taking so long to get the official fix out in 2023.12.4, but I have no control over that.
There are multiple workarounds that have been suggested. If you are having trouble with those, either 1) you haven’t applied the workaround correctly, or 2) you’ve applied more than one workaround that could be conflicting with each other, or 3) there’s some other reason Life360 is rejecting the credentials you entered in HA that we don’t understand.
Please remember, again, that the API the HA integration is using is undocumented and unsupported by Life360. We’re doing our best, but it appears to be a moving target.
First the workarounds: I would strongly suggest undoing all of those and picking one. IMHO, the easiest to use is my custom “ha-life360” integration.
Second, Life360 allows either an e-mail address or phone number (or both?) for your username. From what I can decipher, the e-mail address usually always works, but I’ve also heard that some users have been successful using a phone number for the username when adding Life360 to HA.
Third, I’ve heard that Life360 may ask you to verify your phone number, and if you do, then it is unlikely you’ll be able to use the Life360 integration in HA. It has been suggested that when it asks for verification, don’t do it, and escape out of that screen. I haven’t gone through this myself, so I can’t give precise directions, but you can probably find details above.
I use OwnTracks as a supplemental tracker. In my experience it’s not as quick and not quite as reliable as Life360. Not bad though. Better than the iCloud tracker integration. That’s really slow. I’ve really tried them all. Life 360 and the native mobile HA tracker are best.
I used @pnbruckner’s GitHub manual HACS integration; downloaded zip and put Life360 folder inside config–>custom components folder. After a reboot it works normally. Of note, I wasn’t able to “uninstall” my prior version of Life360 because there wasn’t an option to uninstall it.
You have to ignore the box on the top that says it needs reconfiguration. Instead click on the life360 box on the bottom. Then click the three dot menu and click delete.
I updated to 2023.12.4. It didn’t fix the authentication problem, so I deleted everything, including the previous fix (Life360 folder in config folder), and installed @pnbruckner 's Custom Integration. I am still getting the authentication error. Tried with email, phone number. Changed password using the tool. Nothing seems to work.
When I log in to the app, it never asks for a password. It always authenticates using a text. I don’t know if that’s causing the issue.
Any ideas appreciated before I decide to switch to another platform. My life360 is an unpaid account!
Thanks all for the fantastic work!
I reset the password again and was able to login through custom integration, but it’s showing only one entity. No members of my circle is shown as before. Any idea why?
Try opening the Life360 app. That should cause an update to all Members, which HA should (hopefully) then see.
What is the state of the binary sensor?
If the custom integration is “working” (at least, no authentication errors), then you can go back to the built-in integration in 2023.12.4 by removing the custom integration and restarting HA. Note the binary sensor is not supported by the built-in integration.
For anyone that applied one or more of the temporary workarounds, you MUST remove them, then restart HA (assuming you’ve upgraded to 2023.12.4.)
If you still get errors, try changing your life360 password, do NOT verify your phone number if it asks you to, then try again.
It appears that verifying your phone number enables added security (2FA), which the HA integration doesn’t support. Do not enable that, or if you already did, figure out how to disable it. (I don’t know how to. The Life360 app just asked me yesterday to verify my phone number, but I have not done so.)
UPDATE:
Some people who had verified their phone number, causing the HA integration to fail, were able to resolve the issue by changing their Life360 password, and then NOT verifying their phone number. The HA integration started working again with the new password.
I can confirm if you verify you phone number thru app , after that no chance to login in in life360 HA , even with last update 2023.12.4.
In my case to be able to use life360 again in HA, i use one of my circle member’s e-mail and pass(he was not verify his number thru app) and boom everything go back to normal.
Thanks
So, after some time, all the members of my circle appeared. This is the status of my things:
HA updated to 2023.12.4
Removed all previous workarounds and the built-in integration
Installed Life360 custom integration
Changed Life360 password.
Logged in to the integration using the new password.
My phone number was previously verified, but after changing the password, it became unverified. I think that is why I could log in to the integration.
You should now be able to remove the custom integration and go back to using the built-in integration if you want. The main difference you will see is that the “online” binary sensor will no longer be created, so you’ll have to manually delete it from the Entities page.
And, to be clear, I mean removing <config>/custom_components/life360 and restarting HA. You do NOT need to make any changes on the Integrations page.
This is my current understanding of the situation, and suggestions for getting the integration working.
NOTE: In the following, “/config” refers to your Home Assistant’s configuration directory. However, it might be a different path, depending on how you installed HA. Adjust accordingly.
Remove any life360 PyPI package workaround. I.e., remove “/config/life360” if it exists.
If you want to use the standard, built-in Life360 integration, remove any custom form of it (e.g., my “ha-life360” custom integration) by removing “/config/custom_components/life360”. (If you want to use my ha-life360 custom integration, make sure you are using at least version 0.3.10.)
Upgrade Home Assistant to at least 2023.12.4.
Restart Home Assistant.
If you have an existing Life360 integration config entry, or you try to add one, and it fails to start, that probably means you have verified your phone number via the Life360 app. When you do this, the Life360 server uses a different auth process that the HA integration does not support (yet.) In this case, change your Life360 password via the Life360 app or via their password reset website (see Reset My Password – Life360. See more details about this step below.) After doing this, do NOT verify your phone number if it asks again. Now you should be able to enter the new password in the HA Life360 integration entry.
If for some reason that doesn’t work, and you want to try to remove the HA Life360 integration entry, go to the Integrations page. Ignore any Life360 box that says it needs to be reconfigured. Below that there should be the “normal” Life360 integration box. Click on it. Then click on the three-dot menu, and select Delete.
If all of that fails, a suggestion has been made to make and use a new Life360 account to be used only for Home Assistant, since there is a new “feature” of Life360 that prevents two “login’s” to the same account from two different devices. See procedure below.
Separate Life360 Account for Home Assistant
Courtesy of @FriedCheese (FriedCheese2006 on github)
I’ve slightly worked around this. I created what is essentially a service account that I added to my family circle and used it to log in from HA. You can get a phone number for the text messages using Google Voice.
Get a number using GV (or any other text service of your choosing).
Sign up for a new account using that new number.
Add an email address to the account.
Add the new account to your existing circle (this will generate a code).
Sign into the Life360 app with the new account and join the circle using the code from step 4.
Sign back into the app using your normal account.
Use the new account in HA.
More details about “unverifying” your phone number
