From 39d5704d9bfab598226ab95a6f07fe1efe883324 Mon Sep 17 00:00:00 2001 From: Phil Bruckner Date: Thu, 7 Jul 2022 09:57:54 -0500 Subject: [PATCH] Update Life360 breaking change notes (#23305) Co-authored-by: Franck Nijhof --- .../_posts/2022-07-06-release-20227.markdown | 29 +++++++++++++++---- 1 file changed, 24 insertions(+), 5 deletions(-) diff --git a/source/_posts/2022-07-06-release-20227.markdown b/source/_posts/2022-07-06-release-20227.markdown index 1dd61a9f6b6..9cf13b92de3 100644 --- a/source/_posts/2022-07-06-release-20227.markdown +++ b/source/_posts/2022-07-06-release-20227.markdown @@ -601,6 +601,29 @@ integration, you will have to re-add it manually via the user interface. {% details "Life360" %} +### Overview + +The Life360 integration has been converted from the old "legacy" +implementation (which uses `known_devices.yaml`) to the newer entity based +design, similar to what was done back in the 0.94.0 release to many other +device tracker integrations. + +Due to this change, all your existing Life360 entities will become +non-functional, and there will be new entities, with different entity IDs, +that _are_ functional. + +### Steps to replace old entities with new ones + +1. 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. +2. Restart Home Assistant. All the old, non-functional Life360 entities +should now be gone. +3. Go to the Entities page (under Settings -> Devices & Services -> Entities) +and change the entity IDs for the new Life360 entities as desired. + +### Removed/changed functionality + The previously deprecated YAML configuration of the Life360 integration has been removed. @@ -608,17 +631,13 @@ Life360 is now configured via the UI. Any "advanced" options in YAML configuration will be imported. Once the migration is complete, any `life360` entries in YAML configuration should be removed. -As per other device tracker platforms that have migrated to entity-based, -entries in `known_devices.yaml` will no longer be created, and any existing -entries for `life360` should be removed. - The following options are no longer supported: - `circles` - `members` - `error_threshold` - `warning_threshold` -- `max_update_wait` +- `max_update_wait` (including the `life360_update_overdue` & `life360_update_restored` events) - `show_as_state: moving` Additionally, the following entity attributes have been changed: