Life360 Device Tracker Platform

Leonardo_Del_Vecchio · April 25, 2019, 5:42pm

pnbruckner:

his topic, specifically, if anything can be assumed by an overdue update. IMHO you can’t – the device is just as likely to be where it was last reported as somewhere else, and if it’s somewhere else there’s no reasonable assumption as to where it might be. The lack of information is simply the lack of information.

However, you can do what you want, but as I’ve hinted, I’m not sure why you would. It might be reasonable to take action based on a lack of an update, e.g. change a light, an alarm, etc., but changing the state of the device_tracker entity itself is not something that makes sense to me.

But if you really want to, you can use the device_tracker.see service to do so. But in doing so you’re basically saying the device has been seen, when it really hasn’t.

Thank you Phil!

pnbruckner · April 25, 2019, 7:59pm

PR for documentation submitted.

Note that for users of the custom component this will represent several breaking changes. I already commented on a few of those above. A more complete list can be seen here, or by reviewing the proposed documentation page.

pnbruckner · April 25, 2019, 8:58pm

PR for code submitted. And the fun begins!

javiermi · April 26, 2019, 9:02pm

Hi Phil
Upgraded to 0.92 and it broke life360, so reinstalled from the last code copying the life360 folder into custom_components folder - this after I went back to my previous version of HA ( 091.4)
Then tried to follow the instructions to install the custom_updater component, but found the instructions are not right: on the link ( https://github.com/custom-components/custom_updater/wiki/Installation) says to copy the custom_updater.py to a new folder called custom_updater. It turns out on the Zip file, there is no file with that name ( there is a folder, yes)
anyway, I run the custom_updater install service, then the custom_updater.check_all and restarted HA
I’m not sure if it has done anything, as I still getting a warning saying: “You are using a custom component for life360 which has not been tested by Home Assistant”
I’m scared of upgrading back to 0.92 as I suspect it will fail again
Any suggestions?

pnbruckner · April 26, 2019, 9:08pm

I can’t comment about custom_updater. I didn’t write it.

You don’t have to use custom_updater to install life360. You can, but you don’t have to. There are manual installation instructions for life360 if you’d rather do that.

So you say you upgraded to 0.92 and life360 broke. Can you be more specific? What broke & how? Are there error messages? If so, can you post them? Are you using the latest version (2.9.5, or at least 2.9.4)?

I’ve gotten some reports of life360 not working after upgrading to 0.92, but none of them have been proven to be a real issue. Either it was an old version of life360, or it wasn’t installed correctly, or something like that. I’m happy to try and help, but I’ve tested it extensively with many versions of HA, including 0.92.0. I even went through an experiment today where I installed it on 0.91.4, then upgraded to 0.92.0, and I’ve yet to find where it doesn’t work, as long as it’s at least version 2.9.4.

javiermi · April 26, 2019, 9:52pm

Phil
I’m impressed: this was a really quick reply!
I did reinstall life360 a couple of weeks back, as I was worried a new version would break it, so it couldn’t be too old, I replaced the old system that had two .py files to just one, and it was working until I upgrade to 0.92
After the upgrade HA could not report any tracking data
Unfortunately, I did revert to the previous snapshot, so all the logs are now gone
As I have reinstalled everything , now is running on the last release ( 2.9.5) - but I’m still getting the warning message about life360 -not sure if is relevant or not
Is there any way of testing it - before the upgrade to 0.92?
It’s really painful to revert to an older snapshot, but if that is the only way of testing it…

Sorry I cannot provide a lot of information
Let me know , and I can try again

Javier

pnbruckner · April 26, 2019, 10:02pm

All the work I did to make it work with 0.92 started with version 2.9.1 on 4/19, and I didn’t get it completely right until version 2.9.4 I released on 4/22. So anything older than 4/22 (i.e., older than 2.9.4) will probably fail on HA 0.92.0+.

That’s good!

HA will always warn about custom components/integrations. We just have to live with that. It’s actually a good sign because it’s at least finding it!

You can’t test if it will work with 0.92 unless you install 0.92. But I’ve done that and I know it will work. I understand the pain, but I can’t see anyway to avoid it if you want to upgrade. If you do upgrade to 0.92, and you still run into problems, let’s diagnose it and fix it. I would recommend at least setting logger to debug. That way you should be able to see if/what life360 is doing in home-assistant.log.

javiermi · April 26, 2019, 11:02pm

Thanks for your reply
I will probably try tomorrow
I already have the log in debug
And will let you know once I do it
Thanks again

Christiaan · April 27, 2019, 11:07am

After updating Life360 to the latest release (2.9.5) I upgraded Home Assistant to 0.92.1 and Life360 is working fine.

Thanks for the great work Phil.

javiermi · April 27, 2019, 6:49pm

Phil
Followed your advice and took the plunge to 0.92.1
Everything is working OK now
I had, obviously, upgraded life360 to last release ( 2.9.5 ?) before upgrading
Well done, an thanks!
Javier

JediBrown · April 29, 2019, 7:05am

I’m only getting the device tracker as a state it does not appear to register as an entity under Entity Registry. Is this expected or did I miss something?

Ideally I’d like to use the status in node-RED to trigger various flows, but node-RED required the Entity_ID.

I’m using hassio if that helps.

pnbruckner · April 29, 2019, 1:00pm

That is normal. That is how device_tracker’s currently work. What you see on the States page is an entity_id. I.e., device_tracker.xxx is an entity_id.

BigRob · April 29, 2019, 7:17pm

Hello all.

Im a bit stuck with the updating life360 device tracket for home assistant.

I installed it manually a couple of months back.

I have updated home assistant to 0.92 to look at some of the ESP camera functions that DrZzs is playing with.

The Life360 stopped working, so I commented out the config.yaml to park it for a while. I am now trying to fix it but I cant even get the error message up again as I cant upload “errors” in the config.yaml

Can you please tell me the best steps to follow. I think I go distracted by custom updater and that failed…

Just want to re install life360 from scratch.

Sorry for the bone questions, a point in the right direction would be appreciated.

Regards, Rob

pnbruckner · April 29, 2019, 8:03pm

You need to be using at least version 2.9.4 of life360. See its installation instructions.

brucys · April 30, 2019, 9:48am

Hi Phil
I cannot seem to get Life360 to show the Entity and badge on overview screen. I am sure I have setup as per you detailed description however it is not showing my User under states
I have a feeling reading these posts that it relates to where my config folder is located. I setup Home assistant on Pi 3 B+ and it is working fine for all my devices thus far.
I have tried Owntrack which was ok and now I would like to run with Life360.
Reading this post my Configuration.yaml file is located here
Path to configuration.yaml: /config
If I go to the home /home… this folder is empty and has been empty since my install
I do not have the following path as per this post
/home/homeassistant/.homeassistant/custom_components
I have created the custom_components folder under
/config/custom_components, which is the same location as the configuration.yaml file

I am assuming this is partly to do with my issues? I hope this all makes sense to you

Also, it appears I have loaded your version 2.9.5

Really hope you can help as I really keen on running your project
cheers

pnbruckner · April 30, 2019, 1:38pm

This seems correct for your install. You should, therefore, have at least these files:

/config/custom_components/life360/__init__.py
/config/custom_components/life360/device_tracker.py
/config/custom_components/life360/manifest.json

Also good.

What version of HA do you have?

Do you see any messages at all in the log about life360? Either on the Info page, or more importantly, in home-assistant.log? Do you have logger set to debug?

What do you see in /config/known_devices.yaml?

brucys · April 30, 2019, 8:39pm

Thanks for your reply.

Yes i do have the 3 files located in custome_components/life360 folder
I am running HA version 0.91.4 (See attached)
There is four messages in the Info Page
a - Suppressing further errors until OK: get_circles: HTTPError: 502 Server Error: Bad Gateway for url: https://api.life360.com/v3/circles.json
8:28 AM custom_components/life360/device_tracker.py (ERROR)

b. - get_circles: HTTPError: 502 Server Error: Bad Gateway for url: https://api.life360.com/v3/circles.json
8:28 AM custom_components/life360/device_tracker.py (ERROR)

c. - get_circles: ReadTimeout: HTTPSConnectionPool(host=‘api.life360.com’, port=443): Read timed out. (read timeout=9.0)
8:28 AM custom_components/life360/device_tracker.py (WARNING)

d. - You are using a custom component for life360.device_tracker which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
8:17 AM loader.py (WARNING)

e. You are using a custom component for life360 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
8:17 AM loader.py (WARNING)

I have just turned on Logging have attached the log

Not sure how to upload Log file to you, so here is google drive. Hope it works

Thanks in advance for your help

brucys · April 30, 2019, 8:42pm

Sorry fogot Known devices

My new one for Life360 is called “Bruce” and it is not showing in Know devices.yaml file

bruces_xs:
hide_if_away: false
icon:
mac:
name: Bruce’s Xs
picture: /local/brucys_small.png
track: true

bruce_ipad_pro:
hide_if_away: false
icon:
mac:
name: Bruce iPad Pro
picture:
track: true

jessica’s iPhone:
hide_if_away: false
icon:
mac:
name: Jess iPhone
picture: /local/jess.jpg
track: true

hilda’s iPhone (2):
hide_if_away: false
icon:
mac:
name: Charo iPhone
picture: /local/hilda.jpg
track: true

hildas_iphone_2:
hide_if_away: false
icon:
mac:
name: Hilda’s iPhone (2)
picture:
track: true

pnbruckner · April 30, 2019, 8:53pm

You don’t have logger set to debug, so I can’t see what life360 may or may not be doing. Please try something like this:

logger:
  default: info
  logs:
    custom_components.life360: debug
    life360: debug

Also, can you share your life360 configuration (redacting anything sensitive)?

brucys · April 30, 2019, 9:34pm

ok I have added Debug for Life360

Here is extract of log for that pertains to Life360.
Hope this what you are looking for
Cheers

2019-05-01 09:21:58 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 2.4 seconds.
2019-05-01 09:21:58 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 3.3 seconds.
2019-05-01 09:21:58 INFO (MainThread) [homeassistant.setup] Setting up history
2019-05-01 09:21:58 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.0 seconds.
2019-05-01 09:21:58 INFO (MainThread) [homeassistant.loader] Loaded life360 from custom_components.life360
2019-05-01 09:21:58 WARNING (MainThread) [homeassistant.loader] You are using a custom component for life360 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-05-01 09:21:58 INFO (MainThread) [homeassistant.loader] Loaded life360.device_tracker from custom_components.life360.device_tracker
2019-05-01 09:21:58 WARNING (MainThread) [homeassistant.loader] You are using a custom component for life360.device_tracker which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-05-01 09:21:58 INFO (MainThread) [homeassistant.loader] Loaded mqtt.switch from homeassistant.components.mqtt.switch

2019-05-01 09:22:02 INFO (MainThread) [homeassistant.setup] Setup of domain switch took 2.5 seconds.
2019-05-01 09:22:02 INFO (MainThread) [homeassistant.setup] Setup of domain hassio took 0.5 seconds.
2019-05-01 09:22:02 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 3.1 seconds.
2019-05-01 09:22:03 INFO (MainThread) [homeassistant.setup] Setup of domain weather took 3.3 seconds.
2019-05-01 09:22:03 DEBUG (SyncWorker_0) [custom_components.life360.device_tracker] Checking Places
2019-05-01 09:22:03 INFO (SyncWorker_10) [homeassistant.components.plex.media_player] Discovery configuration done (no token needed)
2019-05-01 09:22:03 INFO (SyncWorker_10) [homeassistant.components.plex.media_player] Connected to: http://192.168.1.200:32400
2019-05-01 09:22:03 INFO (MainThread) [homeassistant.setup] Setup of domain media_player took 1.5 seconds.
2019-05-01 09:22:04 DEBUG (SyncWorker_0) [custom_components.life360.device_tracker] Will check Places every: 0:15:00
2019-05-01 09:22:05 DEBUG (SyncWorker_0) [custom_components.life360.device_tracker] Setup successful!
2019-05-01 09:22:05 INFO (MainThread) [homeassistant.setup] Setup of domain device_tracker took 5.1 seconds.
2019-05-01 09:22:05 INFO (MainThread) [homeassistant.loader] Loaded owntracks.device_tracker from homeassistant.components.owntracks.device_tracker
2019-05-01 09:22:05 INFO (MainThread) [homeassistant.setup] Setting up ios
2019-05-01 09:22:05 INFO (MainThread) [homeassistant.setup] Setting up mobile_app
2019-05-01 09:22:05 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.owntracks