Improve HACS support (#35)

Author: pnbruckner

README.md

@@ -1,11 +1,11 @@
 # Composite Device Tracker
 
-This platform creates a composite device tracker from one or more other device trackers and/or binary sensors. It will update whenever one of the watched entities updates, taking the last_seen/last_updated (and possibly GPS and battery) data from the changing entity. The result can be a more accurate and up-to-date device tracker if the "input" device tracker's update irregularly.
+This integration creates a composite `device_tracker` entity from one or more other device trackers and/or binary sensors. It will update whenever one of the watched entities updates, taking the `last_seen`/`last_updated` (and possibly GPS and battery) data from the changing entity. The result can be a more accurate and up-to-date device tracker if the "input" entities update irregularly.
 
-Currently device_tracker's with a source_type of bluetooth, bluetooth_le, gps or router are supported, as well as binary_sensor's.
+Currently `device_tracker` entities with a `source_type` of `bluetooth`, `bluetooth_le`, `gps` or `router` are supported, as well as `binary_sensor` entities.
 
-Follow the installation instructions below.
-Then add the desired configuration. Here is an example of a typical configuration:
+Follow the [installation](#installation) instructions below.
+Then, after restarting Home Assistant, add the desired configuration and restart Home Assistant once more. Here is an example of a typical configuration:
 
 ```yaml
 composite:
@@ -42,9 +42,18 @@ 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
-### Versions
+### With HACS
+[![hacs_badge](https://img.shields.io/badge/HACS-Custom-41BDF5.svg)](https://hacs.xyz/)
 
-This custom integration supports HomeAssistant versions 2021.12 or newer, using Python 3.9 or newer.
+You can use HACS to manage the installation and provide update notifications.
+
+1. Add this repo as a [custom repository](https://hacs.xyz/docs/faq/custom_repositories/):
+
+```text
+https://github.com/pnbruckner/ha-composite-tracker
+```
+
+2. Install the integration using the appropriate button on the HACS Integrations page. Search for "composite".
 
 ### Manual
 
@@ -60,8 +69,9 @@ 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/).
+### Versions
+
+This custom integration supports HomeAssistant versions 2021.12 or newer, using Python 3.9 or newer.
 
 ### numpy on Raspberry Pi
 

custom_components/composite/manifest.json

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

hacs.json

@@ -0,0 +1,4 @@
+{
+  "name": "Composite Device Tracker",
+  "homeassistant": "2021.12.0b0"
+}

info.md

@@ -0,0 +1,7 @@
+# Composite Device Tracker
+
+This integration creates a composite `device_tracker` entity from one or more other device trackers and/or binary sensors. It will update whenever one of the watched entities updates, taking the `last_seen`/`last_updated` (and possibly GPS and battery) data from the changing entity. The result can be a more accurate and up-to-date device tracker if the "input" entities update irregularly.
+
+Currently `device_tracker` entities with a `source_type` of `bluetooth`, `bluetooth_le`, `gps` or `router` are supported, as well as `binary_sensor` entities.
+
+For now configuration is done strictly in YAML and will be imported into the Integrations and Entities pages in the UI.