And the integration is working for me as well after updating to the 0.7.1b0 and getting a new token.
Thank you!
Yesterday I was able to login with token and connected, but without entities.
I removed the integration and downloaded your version 0.7.1b0 and my entities are showing again. Great work Phil!!
Looks like you have sorted it but incase it helps others the screen shot you shared was from the HA integration page. If you go to the HACS page, in the UI you can find it and re download it from there
You are correct but I looked in HACS and did not see Life360 listed there. Not sure how I got it installed.
I added the repository (GitHub - pnbruckner/ha-life360: A Home Assistant integration for Life360. ¡ GitHub) and now it shows up and I can select what version to install.
Thank you!
Bottom line- Is the issue fixed? What are the steps needed to fix the integration? Are the instructions on Github up-to-date?
Seems to be but as usual that is always subject to change
download the last dev version of the integration.
restart HA
in the integration configuration ui under âmodify accountâ enable the integration if it is disabled.
if that doesnât work delete and re-add the integration.
They seem to be except for possibly the troubleshooting part.
For anyone who is still having issues, please see:
Also, it would be helpful if you could provide your details there. If youâre not able to comment in github, then please provide the details requested there in a reply here.
Released 0.7.1b1
Fixed an initial setup race condition in 0.7.1b0.
2 Likes
After last update itâs start working again
@pnbruckner big THANK YOU for your great job and dedication to our community
Released 0.7.1
Should fix the issues that started with the HA Core 2026.2 release.
Released 0.8.0
-
Drop support for HA versions before 2025.11.3 by @pnbruckner in #86
- GPS accuracy attribute is now a float with one decimal place of precision.
- Fix spelling errors & incorrect instructions; fixes #85.
- For token method, allow any string for account ID; fixes #88.
- Make binary online sensor name translatable.
- Cache mem_circles property.
- Test cleanup & update test versions.
1 Like
Just an FYI, I'm working on two updates:
The first has to do with HTTP 500 Internal Server Errors that sometimes happen and cause a couple of warning messages (one when it happens, and usually almost immediately, another that says it has recovered.) The life360 pypi.org package automatically retries several different types of errors but wasn't retrying this one. So, it has been added to the list of errors to retry. Hopefully, this will prevent those nuisance warnings.
The second has to do with the GPS accuracy attribute & the corresponding configuration item that defines the maximum acceptable value. The type of the attribute changed recently from int to float, but the rest of the code wasn't updated accordingly, leading to possible problems. (See Location doesn't update since latest version of Integration ¡ Issue #89 ¡ pnbruckner/ha-life360.)
I'm testing these changes and should hopefully have a release soon.
4 Likes
Released 0.9.0
- Bump life360 package to 7.1.0, which retries HTTP 500 Internal Server Error. This avoids nuisance warnings.
Released 0.9.1
- Fix bugs related to max GPS accuracy option.
The Life360 integration works for me, but I was wondering if the authentication process needs to be repeated with each update.
I have never had ro repeat the authorisation after an update.
Its been solid.
No, you should not need to go through the authentication/authorization process once it has been completed. Although, some people do have problems and I have no idea why. Please remember this integration is using an undocumented & unsupported API. To say that another way, Life360 does not support our use of their server. The integration has been created via reverse engineering and there's no guarantee it will work. That said, it does work for most people who try it.
I guess I'm wondering why you ask, especially after saying it works for you.
Since updating (which may be unrelated) to 0.9.1 i've had to reconfigure the login token 3 times in the last 24 hours. Each update is only lasting a couple of hours now. Have Life360 changed something again at their end?
Do you know which version you were using before? What HA Core version are you on? Did you do anything besides updating the Life360 integration and just restarting HA?
To my knowledge, and in my experience, it should have just continued to work as before after updating. I am running 0.9.1 on two instances (running HA Core versions 2025.12.5 & 2026.5.3), and both are working fine.
