Bump version to 2.4.0b0

Update README.md.

Author: pnbruckner

README.md

@@ -8,22 +8,46 @@ Follow the installation instructions below.
 Then add the desired configuration. Here is an example of a typical configuration:
 
 ```yaml
-device_tracker:
-  - platform: composite
-    name: me
-    time_as: device_or_local
-    entity_id:
-      - device_tracker.platform1_me
-      - device_tracker.platform2_me
-      - binary_sensor.i_am_home
+composite:
+  trackers:
+    - name: Me
+      time_as: device_or_local
+      entity_id:
+        - device_tracker.platform1_me
+        - device_tracker.platform2_me
+        - binary_sensor.i_am_home
 ```
 
+## Legacy vs entity-based implementation
+
+When this integration was originally created the
+[Device Tracker](https://www.home-assistant.io/integrations/device_tracker/)
+component worked differently than it does today.
+That older implementation is now referred to as the "legacy" implementation,
+and is the one that creates and uses the `known_devices.yaml` file in HA's configuration folder.
+
+Starting with the 2.4.0 release this integration now uses the newer entity-based implementation.
+That implementation stores configuration and entity settings in HA's `.storage` folder,
+and supports reconfiguring those items via the Integrations and Entities pages in the UI.
+The initial configuration, though, is still done via YAML, and is "imported" and will show up
+on the Integrations UI page as such.
+In the future the integration will likely allow adding & fully reconfiguring composite trackers
+via the UI.
+
+To allow for a smoother transition, the integration currently still supports the older,
+legacy implementation as well. If it sees entries under `device_tracker`, it will still create the
+entities as before, but it will issue a warning and a persistent notification that the configuration
+has changed and suggest how to edit your configuration accordingly.
+
+At some point (i.e., in an upcoming 3.0.0 release) legacy support will be removed.
+
 ## Installation
 ### Manual
 
 Place a copy of:
 
 [`__init__.py`](custom_components/composite/__init__.py) at `<config>/custom_components/composite/__init__.py`  
+[`config_flow.py`](custom_components/composite/config_flow.py) at `<config>/custom_components/composite/config_flow.py`  
 [`const.py`](custom_components/composite/const.py) at `<config>/custom_components/composite/const.py`  
 [`device_tracker.py`](custom_components/composite/device_tracker.py) at `<config>/custom_components/composite/device_tracker.py`  
 [`manifest.json`](custom_components/composite/manifest.json) at `<config>/custom_components/composite/manifest.json`
@@ -33,7 +57,7 @@ where `<config>` is your Home Assistant configuration directory.
 >__NOTE__: Do not download the file by using the link above directly. Rather, click on it, then on the page that comes up use the `Raw` button.
 
 ### With HACS
-You can use [HACS](https://hacs.xyz/) to manage installation and updates by adding this repo as a [custom repository](https://hacs.xyz/docs/faq/custom_repositories/) and then searching for and installing the "Composite" integration.
+You can use [HACS](https://hacs.xyz/) to manage installation and updates by adding this repo as a [custom repository](https://hacs.xyz/docs/faq/custom_repositories/).
 
 ### numpy on Raspberry Pi
 
@@ -44,7 +68,9 @@ sudo apt install libatlas3-base
 >Note: This is the same step that would be required if using a standard HA component that uses numpy (such as the [Trend Binary Sensor](https://www.home-assistant.io/components/binary_sensor.trend/)), and is only required if you use `device_or_utc` or `device_or_local` for `time_as`.
 
 ## Configuration variables
-### `composite` integration
+
+- **trackers** (*Optional*): The list of composite trackers to create. For each entry see [Tracker entries](#tracker-entries).
+NOTE: Once legacy support is removed, this variable, with at least one entry, will become required.
 
 - **tz_finder** (*Optional*): Specifies which `timezonefinder` package, and possibly version, to install. Must be formatted as required by `pip`. Default is `timezonefinderL==4.0.2`. Other common values:  
 
@@ -57,10 +83,11 @@ sudo apt install libatlas3-base
 
 >Note: Starting with release 4.4.0 the `timezonefinder` package provides two classes to choose from: the original `TimezoneFinder` class, and a new class named `TimezoneFinderL`, which effectively replaces the functionality of the `timezonefinderL` package.
 
-### `device_tracker` platform
+### Tracker entries
 
 - **entity_id**: Entity IDs of watched device tracker devices. Can be a single entity ID, a list of entity IDs, or a string containing multiple entity IDs separated by commas. Another option is to specify a dictionary with `entity` specifying the entity ID, and `all_states` specifying a boolean value that controls whether or not to use all states of the entity (rather than just the "Home" state, which is the default.)
-- **name**: Object ID (i.e., part of entity ID after the dot) of composite device. For example, `NAME` would result in an entity ID of `device_tracker.NAME`.
+- **name**: Friendly name of composite device.
+- **id** (*Optional*): Object ID (i.e., part of entity ID after the dot) of composite device. If not supplied, then object ID will be generated from the `name` variable. For example, `My Name` would result in an entity ID of `device_tracker.my_name`.
 - **require_movement** (*Optional*): `true` or `false`. Default is `false`. If `true`, will skip update from a GPS-based tracker if it has not moved. Specifically, if circle defined by new GPS coordinates and accuracy overlaps circle defined by previous GPS coordinates and accuracy then update will be ignored.
 - **time_as** (*Optional*): One of `utc`, `local`, `device_or_utc` or `device_or_local`. Default is `utc` which shows time attributes in UTC. `local` shows time attributes per HA's `time_zone` configuration. `device_or_utc` and `device_or_local` attempt to determine the time zone in which the device is located based on its GPS coordinates. The name of the time zone (or `unknown`) will be shown in a new attribute named `time_zone`. If the time zone can be determined, then time attributes will be shown in that time zone. If the time zone cannot be determined, then time attributes will be shown in UTC if `device_or_utc` is selected, or in HA's local time zone if `device_or_local` is selected.
 
@@ -76,9 +103,9 @@ If a watched device has a `battery` or `battery_level` attribute, that will be u
 
 ## known_devices.yaml
 
-The watched devices, and the composite device, should all have `track` set to `true`.
+NOTE: This only applies to "legacy" tracker devices.
 
-It is recommended to _not_ use the native merge feature of the device tracker component (i.e., do not add the MAC address from network-based trackers to a GPS-based tracker. See more details in the [Device Tracker doc page](https://www.home-assistant.io/components/device_tracker/#using-gps-device-trackers-with-local-network-device-trackers).)
+The watched devices, and the composite device, should all have `track` set to `true`.
 
 ## Attributes
 
@@ -101,17 +128,16 @@ time_zone | The name of the time zone in which the device is located, or `unknow
 composite:
   tz_finder: timezonefinder<6
   tz_finder_class: TimezoneFinderL
-device_tracker:
-  - platform: composite
-    name: me
-    time_as: device_or_local
-    require_movement: true
-    entity_id:
-      - device_tracker.platform1_me
-      - device_tracker.platform2_me
-      - device_tracker.router_my_device
-      - entity: binary_sensor.i_am_home
-        all_states: true
+  trackers:
+    - name: Me
+      time_as: device_or_local
+      require_movement: true
+      entity_id:
+        - device_tracker.platform1_me
+        - device_tracker.platform2_me
+        - device_tracker.router_my_device
+        - entity: binary_sensor.i_am_home
+          all_states: true
 ```
 
 ### Time zone examples

custom_components/composite/manifest.json

@@ -1,7 +1,7 @@
 {
   "domain": "composite",
   "name": "Composite",
-  "version": "2.3.0",
+  "version": "2.4.0b0",
   "documentation": "https://github.com/pnbruckner/ha-composite-tracker/blob/master/README.md",
   "issue_tracker": "https://github.com/pnbruckner/ha-composite-tracker/issues",
   "requirements": [],