If you’re looking for a swift solution, manually implement it by accessing the commit on the Official Github repository here
I just changed this file in my Home Assistant docker container:
/usr/local/lib/python3.11/site-packages/life360/api.py
It works for me now.
Thank you to @pnbruckner et al. for quickly resolving this!
Fix to life360 (package, not the HA integration) has been released. See temporary workaround here: Life360 Device Tracker Platform - Third party integrations - Home Assistant Community (home-assistant.io)
I am facing the same problem here.
Is there a simple fix to solve this, or do I have to wait for an official update?
no simple fixes - either the workaround above which involves updating the manifest of the integration manually, or like you say, waiting for next update.
Excellent
Thank you !
That previous post is a workaround. It is no longer required and I would strongly recommend not applying it. Simply update to 2023.12.4 (or later), and you should be able to get the Life360 integration working again.
If you run into any issues, please see this post for more detail and suggestions.
Trying to catch all the Life360 related threads…
Something changed this morning that broke the integration again. I’m throwing in the towel. It’s become much too difficult to try to keep up with a moving target that may be purposely trying to “hide” itself.
I understand what you’re saying, but PLEASE don’t give up… Honestly, thank you very much for the work you’ve put into this. I guess it’s time to find a new solution. Any ideas?
Phil, it started working fine after 2023.12.4 but since yesterday its giving the same error to reconfigure. I’ve now upgraded my HA core to 2024.1.0 but still same issue
Please see my comment three posts up 
Yes, as @Jsdray said, PLEASE don’t give up! As a family of mixed Android and iPhone users, Life360 is pretty much the only option that works well, and works well within HA (when it works) thanks to you!
Does anyone know if this can be solved within HA?
It seems to me that the Life360 site has changed something regarding logging in.
I can imagine that this is not solvable within HA.
It’s not entirely “just giving up” trying to keep up with the API changes. It seems now that Life360 (via Cloudflare) has started to actively lock out unauthorized uses of their API.
It’s not 100% clear, but it seems they have enabled “bot protection” (don’t ask me to explain, I’m not the expert on that).
In the past, the HA Life360 integration (via the life360 PyPI package), tried to emulate the network requests their app does, and this has worked well for a long time. Recently their API changed, and through the help of some others we were able to adjust accordingly and effectively continue what we’ve been doing for years.
But very recently, those emulated queries are getting rejected. We can verify that the HA integration is making the exact same requests (URLs, headers, auth tokens, etc.) as their app, yet they are getting rejected from HA, where they work when issued from their official app. It would seem this cannot be worked around, which, of course, is by design.
So, until Life360 provides a supported API, which, given recent responses from them, seems very unlikely to ever happen, there’s no point in trying to make the HA integration work.
I was already afraid of this. But in any case, thank you for your effort and time you’ve put into trying to resolve it.
My Life360 integration has not been working for over 2 months now and I am at a point to replace that integration with “Mobile App” integration. But I would really like to see Life360 integration working again!
So does everyone, except for Life360. 
Kinda sad that many companies have taken the MyQ approach 
Hopefully there will be a more stable and larger Matter or Zigbee2MQTT ecosystem in 2024.
When accessing a site using CloudFlare with bot detection using a Windows tool we developed it was odd. We had to use the Delphi integrated socket code, indy socket class kept on failing, AND we had to use an Edge useragent. If we used Chrome, it failed always despite the official API/Browser communication we were emulating was using a Chrome useragent.
So despite using byte for byte the exact same request (header, referrer, useragent, keep alive, cookies, http version etc) as the official app it would not work. Started POSTing requests changing things one by one and when the useragent was changed bingo Edge got through.
Thank you for all of the work that you put in on the Life360 addin. I enjoyed using it and appreciate your dedication.
I wish the mobile app ‘just worked’ out of the box as well as Life360 seems to.