account regularly deactivated

[mendo862]

Hello,

I use the application on 4 phones and on ha I regularly find my account deactivated, do I have to delete and re-register the account?

what could this be due to?

Thank you for your feedback.

[pnbruckner]

Versions? Errors?

[aaronburt]

Hi @pnbruckner

Version: 0.5.4 & 0.5.3 same behaviour

Occasionally, requests result in a 403 error, causing the Life360 integration to enter the "Life360 Account Login Error" setup stage. Despite this, the Bearer token still works after setup. This behaviour seems similar to hitting a rate limit. A possible workaround could involve ignoring these errors a certain number of times or reducing the polling frequency.

Logger: custom_components.life360.coordinator
Source: custom_components/life360/coordinator.py:551
integration: Life360 ([documentation](https://github.com/pnbruckner/ha-life360/blob/0.5.4/README.md), [issues](https://github.com/pnbruckner/ha-life360/issues))
First occurred: 26 November 2024 at 05:59:54 (2 occurrences)
Last logged: 03:29:34

    life360@.co.uk: while getting data for PERSON_NAME_REDACTED from Family Circle: aiohttp.client_exceptions.ClientResponseError: 403, message='Forbidden', url='https://api-cloudfront.life360.com/v3/circles/REDACTED/members/REDACTED'; status: 403
    life360@.co.uk: while getting data for PERSON_NAME_REDACTED from Burt Family Circle: aiohttp.client_exceptions.ClientResponseError: 403, message='Forbidden', url='https://api-cloudfront.life360.com/v3/circles/REDACTED/members/REDACTED'; status: 403

Additional Warning Logs (Possibly Unrelated)

This error originated from a custom integration.

Logger: custom_components.life360.device_tracker
Source: custom_components/life360/device_tracker.py:385
integration: Life360 (documentation, issues)
First occurred: 25 November 2024 at 20:34:44 (4 occurrences)
Last logged: 27 November 2024 at 15:06:59

Life360 Hse (device_tracker.life360_hse): Ignoring location update because expected GPS accuracy (100.0) is not met: 826
Life360 Rac (device_tracker.life360_rac): Ignoring location update because expected GPS accuracy (25.0) is not met: 31

[pnbruckner]

@aaronburt, the integration already has an extensive set of fairly complex retry mechanisms (due to the touchy nature of the Life360 server), including in response to error 403. Under normal conditions, when it gets an error 403 (Forbidden), it will retry up to 30 times, with a one-minute delay between retries.

If you want to see what the integration is doing in response to these errors, enable debug and view the DEBUG messages in the log.