Okey-dokey. I’ll try in a bit. Thank you:)
Life360 changed its API. HA 2023.8.0b3 should get things working again.
I can confirm this fix (workaround?) works. Not sure what I do with the folder now, assume I just keep it there until the 2023.8 release is released.
I have the same issue, started around same time. Does Life360 still have issues? or did they change anything?
The Life360 app on my mobile works normal though, no report about anything not working properly…
edit: got it now reading through all the comments… will simply wait for the update to come
Without any changes applied to my instance of HA, integration started to work again - after restart of HA all error messages are gone and device trackers are working again. Probably they fixed the problem on their side.
Same here. A reboot of HA seems to have fixed mine as well.
Guys, the problem is back. Even with the correction the problem reappeared, the same error 500.
Life360 is working even it appears to reconfigure and when clicked to reconfigure it shows the same error 500.
Log:
Logger: aiohttp.server
Source: components/life360/config_flow.py:140
First occurred: 18:45:47 (2 occurrences)
Last logged: 18:48:09
Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py”, line 433, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py”, line 504, in _handle
resp = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py”, line 117, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/http/security_filter.py”, line 85, in security_filter_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/http/forwarded.py”, line 100, in forwarded_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/http/request_context.py”, line 28, in request_context_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/http/ban.py”, line 80, in ban_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/http/auth.py”, line 236, in auth_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/http/view.py”, line 148, in handle
result = await handler(request, **request.match_info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/config/config_entries.py”, line 172, in get
return await super().get(request, flow_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py”, line 96, in get
result = await self._flow_mgr.async_configure(flow_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 296, in async_configure
result = await self._async_handle_step(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 392, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/life360/config_flow.py”, line 140, in async_step_reauth_confirm
self._password = user_input[CONF_PASSWORD]
~~~~~~~~~~^^^^^^^^^^^^^^^
TypeError: ‘NoneType’ object is not subscriptable
Same. Problem returned.
1 Like
Same here, both with the previous manual fix applied, and with that removed. I came back here just to double check it wasnt just a me thing.
1 Like
Same here!
Same thing here…
I update to version 2023.8.3 but same error here
has everyone currently having the problem recently updated to the latest HA release?
I’m still on 2023.7.3 and mine is running fine.
Yes to latest release for me.
I just mentioned this in another topic, but what I’ve found is, if you have a valid life360 integration in HA, then it will mostly likely still work with older versions of HA. But if your Life360 credentials change, or you delete/re-add or try to add a new life360 account in HA, then it requires at least HA 2023.8.
1 Like
I have updated to version 2023.8.4 with no changes in my life360 credentials and I still get the Internal 500 error from HA. The HA Life360 integration has been non-functional for about a week for me.
I have a life360 folder in my Config directory of HA that I have renamed to life360_OLD and rebooted and that did not fix it. Do I or do I not need that life360 directory?
No, you should not need it any longer. That was a temporary fix and is superseded by 2023.8.x (which includes a new version of the life360 package that is the “official” release of the change that was in the temporary fix.)
I’m getting very mixed messages from users. It seems to work for some, but not for others. It works for me personally.
I don’t know what the problem might be. Again, this is using an unofficial and undocumented API from Life360. And although I have tried to monitor the network traffic from the official Android Life360 app, I’ve been unable to do so. So, there is no way for me to “reverse engineer” the API.
Continues to fail for me. I’ve tried everything I can think of. Unfortunately between this and the lousy GPS perf from the companion app, my house is totally confused as to who is home and who isn’t. 
Please see:
Maybe that will help.
sorry, how do you remove the life360 integration?