HA Release 2022.7.0 introduces a BREAKING CHANGE to the Life360 integration
The Life360 integration has been converted from the old “legacy” implementation (i.e., that uses the
known_devices.yaml file in the config directory) to the newer entity-based design, similar to what was done for many other device tracker integrations when the new design was first introduced in release 0.94.0 over three years ago! (Interesting fact: the Life360 integration was first introduced in release 0.95.0, so was implemented while the device tracker component was in the process of being reorganized. So, this change is long overdue!)
When you upgrade to 2022.7 or newer for the first time, all your existing Life360
device_tracker entities will become non-functional. Unfortunately, given the implementation of the device tracker component level code there was no way to avoid this.
But there will also be new entities that are functional.
Take a look on the STATES tab of the Developer Tools page, or the Entities page under Settings, and you should see both the old and new entities. The old entities will have the same entity IDs as before, and so anything that used those entities (
person entities, automations, etc.) will no longer be getting updates.
Steps to replace old entities with the new ones
- Edit the
known_devices.yaml file in your configuration directory to remove any Life360 related entries. Or, if there are only Life360 entries in this file, simply delete the file entirely.
- Restart Home Assistant. All the old, non-functional Life360 entities should now be gone.
- Go to the Entities page (under Settings → Devices & Services → Entities) and change the entity IDs for the new Life360 entities as desired.
Configuring Life360 via YAML files is no longer supported. Any settings that were in YAML will be automatically migrated to the config entries. Once you upgrade you should remove the Life360 related entries from your YAML files. You can see or change the migrated settings by going to Settings → Devices & Services → Integrations and clicking CONFIGURE on a Life360 entry.
Which brings us to the next point – some settings are no longer supported, specifically:
max_update_wait (and the corresponding events
The following attributes have changed: