Life360 Device Tracker Platform

Third party integrations
1077

Transition from custom to standard integration

For those that have been using this custom component/integration, when upgrading to HA 0.95.0b0 or later, you need to make some changes to avoid errors and keep your trackers working. This is a summary of the steps you should take.

Basic steps

  1. Delete <config>/custom_components/life360.
  2. Modify the life360 related configuration. (See below.)
  3. Update HA as usual.

NOTE: life360 is still a “legacy” device tracker, so it still uses known_devices.yaml. Do not modify, and do not delete known_devices.yaml.

NOTE: After you complete these steps you should see Life360 configured on the Integrations page. If you click on it it will say, “This integration has no devices.” That is normal.

Modifying your configuration

A) Life360 Account(s)

This part of your configuration:

device_tracker:
  - platform: life360
    username: LIFE360_USERNAME
    password: LIFE360_PASSWORD
    # Other life360 configuration variables...

should be changed to this:

life360:
  accounts:
    username: LIFE360_USERNAME
    password: LIFE360_PASSWORD
  # Other life360 configuration variables...

NOTE: If you have any other configuration variables besides your account credentials, make sure they are at the same indentation level as accounts:.

If you have more than one Life360 account, they should all go under the one accounts: key. E.g.:

life360:
  accounts:
    - username: LIFE360_USERNAME_1
      password: LIFE360_PASSWORD_1
    - username: LIFE360_USERNAME_2
      password: LIFE360_PASSWORD_2
  # Other life360 configuration variables...

The remainder of the configuration variables can only be specified once, which applies to all Life360 accounts. It’s no longer possible to have different settings for each account as was possible before.

B) Unsupported configuration variables

The following options are no longer supported and must be removed:

add_zones
filename
home_place
time_as
zone_interval

C) Changed configuration variables

prefix

NOTE: This is important to prevent your device_tracker entity IDs from changing.

The default “device ID” prefix is now life360, whereas it used to be none.

If you did not include prefix: in your configuration, then you need to add this to keep your device_tracker entity_id’s the same:

  prefix: ''

Any other prefix: value can be left as-is.

show_as_state

This variable now only accepts driving and moving. If you had places listed under this option, you need to remove it.

Also, if you had it entered like this:

    show_as_state: driving, moving, places

You need to change it to a true YAML list, e.g., like this:

  show_as_state: [driving, moving]

error_threshold and warning_threshold

If you were using either or both of these before, just increase them each by 1 to get the same behavior.

members

Originally this was an “include” list, with Life360 Member names specified in any of these formats: first,last name name, ,name. It can now be either an include or exclude list, with Member names specified as first last or name. So, if you specified this option, change it from:

members:
  - first, last
  - name1
  - , name2
  - name3,

to:

members:
  include:
    - first last
    - name1
    - name2
    - name3

Note that you can instead specify an exclude list for Members, and there is a new option for specifying which Life360 Circles to include/exclude. See standard integration doc for more details.

D) Zones

As noted above, the options for automatically adding/updating HA zones from Life360 Places are no longer supported. If you were using this feature, then you’ll need to add the corresponding HA zones a different way. See documentation for standard integration which talks more about this.

A final note. Life360 credentials used to be cached in a file in your <config> folder which, by default, was named life360.conf. This file is no longer used or created and you can delete it if you like. (Credentials are now stored in the HA standard .storage folder.)

10 Likes