Logger: custom_components.life360.coordinator
Source: custom_components/life360/coordinator.py:567
Integration: Life360 (documentation, issues)
First occurred: 7:15:00 PM (1 occurrence)
Last logged: 7:15:00 PM
[email protected]: while getting data for My_Name from Family Circle: aiohttp.client_exceptions.ClientResponseError: 403, message='Forbidden', url='https://api-cloudfront.life360.com/v3/circles/REDACTED/members/REDACTED'; status: 403
This is the current error from the logs.
Unfortunately, that happens to some people sometimes and I have no idea why or what to do about it.
I've updated the access_token again, let's see how long this one lasts.
I had a problem a couple of days ago just randomly after a restart of HA. It wasn't related to any updates as far as I know.
I was getting a login credentials error.
I tried updating the credentials and it kept saying that the credentials were invalid.
I even deleted and re-added the integration and I got the exact same error when I tried to login with my username/password. But that has been the way I've always logged in and I know the credentials were the same and haven't changed.
I eventually figured out the token method and after that it all seemed to work again.
I'm also on 0.9.1
Unfortunately the access_token update only lasted a few hours. Same error.
Logger: custom_components.life360.coordinator
Source: custom_components/life360/coordinator.py:567
Integration: Life360 (documentation, issues)
First occurred: May 26, 2026 at 10:04:27 PM (1 occurrence)
Last logged: May 26, 2026 at 10:04:27 PM
[email protected]: while getting data for My_Name from Family Circle: aiohttp.client_exceptions.ClientResponseError: 403, message='Forbidden', url='https://api-cloudfront.life360.com/v3/circles/REDACTED/members/REDACTED'; status: 403
I've nothing to add bar a +1 (which I realise isn't overly helpful) but same error as mentioned here ongoing with regularity over past few days (or more).....HA 2026.5.4 and Life360 0.9.1
Have tested Life360 using different logins with same result.....
I decided to give this another go today only to find what looks like Life360 have changed something. I can't see a response any longer for the access token.
Yep, it would seem so. 
A few days ago, Life 360 was working perfectly until the latest update (0.10.0)! I don't understand why I always have to re-authenticate! I deleted and re-entered the integration and authenticated via username/password, but it's incorrect, even though I can access life360.com with those credentials. I tried using a token, but I don't understand it at all. I repeat, it's unacceptable that we have such problems with every update!
I have no idea why you would have to re-authenticate after every update. That does not happen to me, and I don't believe I've heard anyone else having this experience. Also, you should not have to delete & re-enter the integration. Doing so will definitely require you to re-authenticate.
I'm sorry if you are frustrated, but please remember, this integration is based on an undocumented & unsupported API. To put that another way, Life360 does NOT support the use of their system from Home Assistant. In fact, it often looks like they do everything they can to make it difficult to do so. Therefore, there are no guarantees with this integration. If it works for you, great! If not, there often isn't anything I can do about it.
How do you explain that the same credentials (username/password) successfully entered on life360.com fail in the Life360 Home Assistant integration?
I can't, because the API is undocumented & unsupported.
Most of us understand the situation and really appreciate your efforts Phil.....
As i posted above I'm seeing this disconnect too......can see it's flagged now on GitHub too Keep Disconnecting · Issue #93 · pnbruckner/ha-life360 · GitHub do you need a +1 there too.....
Thanks!
What you and @c0rnflake posted above was seeing error 403 (forbidden) while fetching a member's data. The new issue you refer to is not exactly the same. Although it happens in response to the same query (i.e., retrieving a member's data), the error is different, specifically error 429 (too many requests.)
In theory, error 429 can be retried (like it is while retrieving the list of Circles & Members), but the "retry_after" values that have been shared are on the order of 23 hours or so. Obviously, waiting 23 hours between member data updates would render the integration useless.
For anyone who is seeing these "too many requests" (429) errors, it might be helpful to add a comment to that effect on issue #93. I'm not sure what to do about it, but it would be nice to know how many people are being affected.
On a related note (i.e., Life360 making it more difficult for us), it seems the method of getting the access token (if you use that authorization method) doesn't work anymore. I.e., looking at the network traffic while logging into Life360's website doesn't show the access type & token anymore. However, someone discovered that looking at the Application tab instead, the token can be found in the cookies. I'm updating the instructions for the integration accordingly.
I was able to find the token 'LIFE360_AUTH_TOKEN' via applications/cookies, but I only get one entity: binary_sensor.life360_online_xxxxxx_gmail_com. No device trackers !!!!.
Did you not see a warning in the system log?
Some recent releases:
20260603: 0.10.0 - Bump life360 package to 7.2.0
20260604: 0.10.1 - Fix "deprecated alias TrackerEntity" warning in HA 2026.6
20260611: 0.10.2 - Fixes & updated instructions for retrieving access token
My experience with 0.10.2 is that:
Hope you are able to figure it out. Appreciate all your great work on this!
experiencing the same issues with the most recent life360 update, as a side note, HA didn't tell me there where any updates to 0.10.2 and had to manually update.