I am experiencing delays today.
Can anyone propose a good alternative for Life360 with HA integration?
The Home Assistant app!
HA companion app is not able to update a battery level periodically )))
iPhone 5S (iOS 12.5.5), iPad Air 2 (iOS 15.x) - same outdated data.
Also, I do not want to install HA app on 9 mobile phones for my family.
Could you please open a new topic to request suggestions for other HA device trackers? This topic is intended for discussions about the Life360 integration. Thanks!
I’m working on converting the standard integration to the newer entity-based format (which many other device tracker integrations did a while ago.) I’m looking for testers. Please see:
@pnbruckner Just installed with HACS and no problems so far.
Am i forced to have the app installed and running?
I’m sorry, I don’t understand what you’re asking.
I mean: to use your custom component i must have the android app installed on my mobile and running or not? Is the custom component independent from the app or not?
I was using the old integration, so i already have username and passwords.
So, the life360 integration has been a built-in integration in Home Assistant for a long time now. When you say you were “using the old integration”, do you mean the built-in one, or my custom version from way back before it was added as a built-in one?
In any case, the Home Assistant life360 integration (whether the old one, the current built-in one, or this new version, which will hopefully replace the built-in one) gets location information from the Life360 server. It cannot operate independent of Life360. In order to use the integration, you must have a Life360 account, and for it to be useful, yes, you’d need to have the Life360 app installed on your phone(s.)
Ok, what happens if i have the app installed but deactivated (i noticed in past a BIG waste of battery)?
Is it enough to have a Life360 account?
I’ve never had any issues with battery usage from the Life360 app, and I’ve been using it for almost 9 years. AFAIK, they go to great lengths to minimize battery usage while maximizing useful location updates. If you have battery issues you should check their FAQs.
Um, how do you expect the Life360 server to get location information from your phone if the app (that supplies that information) is deactivated? I think you’re misunderstanding how this works. The app sends location information to the Life360 server, and the HA integration periodically queries the Life360 server for that data. This is basically the same model that most, if not all, tracker systems use. E.g., I also use Google Maps, and it works exactly the same way. (Moreover, I use both apps on the same phone, which I’ve been doing for years, and do not have any battery issues.)
Of course, using any app that periodically runs, uses GPS, and sends information to a server, is going to use some battery. Nothing is free. But, in my experience, I wouldn’t classify either Life360 or Google Location Sharing as “BIG” wastes of battery.
I am pretty sure that L360 will respond with the latest location data that it has. My wife’s phone ran out of battery a few days ago and L360 was still reporting her location as “at work”.
Just a stupid question:
How, having HA OS, to run the life360_backup.py script?
EDIT: found it…
I get ‘unavailable’ state very often since i switched from legacy integration to yours and i am foced to reload the integration to have again the device available.
Are there any messages in the log? Have you enabled debug for this?
Still not… can you tell me how?
logger: default: info logs: life360: debug homeassistant.components.life360: debug
Add that to configuration.yaml, then restart HA. Then look in
home-assistant.log for messages related to life360.
What i see is only this:
2022-05-31 04:22:21 ERROR (MainThread) [custom_components.life360] Error fetching life360 ([email protected]) data: 2022-05-31 05:20:45 ERROR (MainThread) [custom_components.life360] Error fetching life360 ([email protected]) data: 2022-05-31 06:31:58 ERROR (MainThread) [custom_components.life360] Error fetching life360 ([email protected]) data: 2022-05-31 06:38:46 ERROR (MainThread) [custom_components.life360] Error fetching life360 ([email protected]) data:
2022-06-02 00:08:00 ERROR (MainThread) [custom_components.life360] Unexpected error fetching life360 ([email protected]) data: Executor shutdown has been called Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 191, in _async_refresh self.data = await self._async_update_data() File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 150, in _async_update_data return await self.update_method() File "/config/custom_components/life360/__init__.py", line 154, in async_update_data return await get_life360_data(hass, api) File "/config/custom_components/life360/helpers.py", line 134, in get_life360_data for circle in await retrieve_data(api.get_circles): File "/config/custom_components/life360/helpers.py", line 124, in retrieve_data return await hass.async_add_executor_job(func, *args) File "/usr/src/homeassistant/homeassistant/core.py", line 479, in async_add_executor_job task = self.loop.run_in_executor(None, target, *args) File "/usr/local/lib/python3.9/asyncio/base_events.py", line 807, in run_in_executor self._check_default_executor() File "/usr/local/lib/python3.9/asyncio/base_events.py", line 514, in _check_default_executor raise RuntimeError('Executor shutdown has been called') RuntimeError: Executor shutdown has been called