Merge branch 'rc' into current

_config.yml

@@ -100,9 +100,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 107
+current_minor_version: 108
-current_patch_version: 7
+current_patch_version: 0
-date_released: 2020-03-25
+date_released: 2020-04-08
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

sass/custom/_paulus.scss

@@ -345,6 +345,10 @@ article.post, article.page, article.listing {
     // Future re-design
     // margin: 1.5em 0 1rem;
   }
+
+  details {
+    padding-bottom: 1em;
+  }
 }
 
 p.note, div.note {

source/_docs/configuration/customizing-devices.markdown

@@ -40,11 +40,6 @@ hidden:
   required: false
   type: boolean
   default: false
-emulated_hue_hidden:
-  description: Set to `true` to hide the entity from `emulated_hue` (this will be deprecated in the near future and should be configured in [`emulated_hue`](/integrations/emulated_hue)).
-  required: false
-  type: boolean
-  default: false
 entity_picture:
   description: URL to use as picture for entity.
   required: false

source/_docs/mqtt/discovery.markdown

@@ -61,14 +61,6 @@ The discovery topic need to follow a specific format:
 
 The payload must be a JSON dictionary and will be checked like an entry in your `configuration.yaml` file if a new device is added. This means that missing variables will be filled with the platform's default values. All configuration variables which are *required* must be present in the initial payload send to `/config`.
 
-If the integration is `alarm_control_panel`, `binary_sensor`, or `sensor` and the mandatory `state_topic` is not present in the payload, `state_topic` will be automatically set to:
-
-```text
-<discovery_prefix>/<component>/[<node_id>/]<object_id>/state
-```
-
-The automatic setting of `state_topic` is deprecated and may be removed in a future version of Home Assistant.
-
 An empty payload will cause a previously discovered device to be deleted.
 
 The `<node_id>` level can be used by clients to only subscribe to their own (command) topics by using one wildcard topic like `<discovery_prefix>/+/<node_id>/+/set`.

source/_integrations/airly.markdown

@@ -11,7 +11,7 @@ ha_codeowners:
 ha_domain: airly
 ---
 
-The `airly` integration uses the [Airly](https://airly.eu/) web service as a source for air quality data for your location. 
+The `airly` integration uses the [Airly](https://airly.eu/) web service as a source for air quality data for your location.
 
 ## Setup
 
@@ -19,26 +19,10 @@ To generate an Airly API key, go to [Airly for developers](https://developer.air
 
 ## Configuration
 
-To add Airly to your installation, go to **Configuration** >> **Integrations** in the UI and enable the Airly integration. By default, the values will be taken from the Home Assistant configuration.
+To add Airly to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Airly**. By default, the values will be taken from the Home Assistant configuration.
 
-{% configuration %}
+<div class="note warning">
-api_key:
+
-  description: The Airly API key.
+Airly allows 100 data updates per day. For this reason, the more Airly instances configured, the less frequent updates will be. For one configured Airly instance, data will be updated every 15 minutes, for two configured instances, data will be updated every 30 minutes, for three configured instances, data will be updated every 45 minutes, etc.
-  required: true
+
-  type: string
+</div>
-name:
-  description: Manually specify Name.
-  required: false
-  type: string
-  default: Airly
-latitude:
-  description: Manually specify latitude.
-  required: false
-  type: float
-  default: Provided by Home Assistant configuration
-longitude:
-  description: Manually specify longitude.
-  required: false
-  type: float
-  default: Provided by Home Assistant configuration
-{% endconfiguration %}

source/_integrations/alarm_control_panel.template.markdown

@@ -73,7 +73,7 @@ panels:
           type: string
           default: Template Alarm Control Panel
         value_template:
-          description: "Defines a template to set the state of the alarm panel. Only the states `armed_away`, `armed_home`, `armed_night`, `disarmed`, `triggered` and `unavailable` are used."
+          description: "Defines a template to set the state of the alarm panel. Only the states `armed_away`, `armed_home`, `armed_night`, `disarmed`, `pending`, `triggered` and `unavailable` are used."
           required: false
           type: template
         disarm:

source/_integrations/alarmdecoder.markdown

@@ -82,10 +82,15 @@ panel_display:
   default: false
   type: boolean
 autobypass:
-  description: "If this is set to `true`, then when arming (home or away), it will automatically bypass all open zones (sending '6#')."
+  description: "If this is set to `true`, then when arming (home or away), it will automatically bypass all open zones (sending '6#'). This will require your code to be entered even if `code_arm_required` is set to `false`."
   required: false
   default: false
   type: boolean
+code_arm_required:
+  description: "If this is set to `false`, you will not need to enter your code to arm the system."
+  required: false
+  default: true
+  type: boolean
 zones:
   description: "AlarmDecoder has no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/integrations/alarmdecoder) documentation. *Note: If no zones are specified, Home Assistant will not load any binary_sensor integrations.*"
   required: false
@@ -131,6 +136,7 @@ There are several attributes available on the alarm panel to give you more infor
 - `programming_mode`: Set to `true` if your system is in programming mode.
 - `ready`: Set to `true` if your system is ready to be armed. Any faults, including motions sensors, will make this value `false`.
 - `zone_bypassed`: Set to `true` if your system is currently bypassing a zone.
+- `code_arm_required`: Set to the value specified in your configuration.
 
 ## Services
 

source/_integrations/alarmdotcom.markdown

@@ -1,47 +0,0 @@
----
-title: Alarm.com
-description: Instructions on how to integrate Alarm.com into Home Assistant.
-logo: alarmdotcom.png
-ha_category:
-  - Alarm
-ha_release: 0.11
-ha_domain: alarmdotcom
----
-
-The `alarmdotcom` platform is consuming the information provided by [Alarm.com](https://www.alarm.com/).
-
-## Configuration
-
-To enable this, add the following lines to your `configuration.yaml`:
-
-```yaml
-# Example configuration.yaml entry
-alarm_control_panel:
-  platform: alarmdotcom
-  username: YOUR_USERNAME
-  password: YOUR_PASSWORD
-```
-
-{% configuration %}
-username:
-  description: Username for the Alarm.com account.
-  required: true
-  type: string
-password:
-  description: Password for the Alarm.com account.
-  required: true
-  type: string
-name:
-  description: The name of the alarm.
-  required: false
-  default: Alarm.com
-  type: string
-code:
-  description: Specifies a code to enable or disable the alarm in the frontend.
-  required: false
-  type: integer
-{% endconfiguration %}
-
-<div class='note warning'>
-  Please make sure that your alarm.com language is set to English before open any issue.
-</div>

source/_integrations/alexa.smart_home.markdown

@@ -413,6 +413,7 @@ The following integrations are currently supported:
 - [Binary Sensor](#binary-sensor)
   - [Doorbell Announcement](#doorbell-announcement)
   - [Presence Detection](#presence-detection-with-binary-sensor)
+- [Camera](#camera)
 - [Climate](#climate)
 - [Cover](#cover)
   - [Garage Doors](#garage-doors)
@@ -570,6 +571,18 @@ Each Echo device will need the communication and Announcements setting enabled,
 
 [Image Processing](#image-processing) entities also support this notification.
 
+### Camera
+
+View a camera stream on an Amazon echo device.
+
+- _"Alexa, show the front door camera."_
+
+The [`stream`](/integrations/stream/) integration is required to stream cameras to Amazon echo devices.
+
+The Amazon echo device will request the camera stream from Home Assistant. The Home Assistant URL must be accessible from the network the Amazon echo device is connected to and must support HTTPS on port 443 with a certificate signed by [an Amazon approved certificate authority](https://ccadb-public.secure.force.com/mozilla/IncludedCACertificateReport). These requirements can be satisfied with Home Assistant Cloud, or LetsEncrypt/DuckDNS.
+
+Enable preload stream option for cameras used with echo devices to reduce response time, and prevent timing out before the 6 second limit.   
+
 ### Climate
 
 Single, double, and triple set-point thermostats are supported. The temperature value from the thermostat will also be exposed at a separate [temperature sensor](#sensor).

source/_integrations/amcrest.markdown

@@ -1,6 +1,6 @@
 ---
 title: Amcrest
-description: Instructions on how to integrate Amcrest IP cameras within Home Assistant.
+description: Instructions on how to integrate Amcrest (or Dahua) IP cameras within Home Assistant.
 logo: amcrest.png
 ha_category:
   - Hub
@@ -14,7 +14,7 @@ ha_codeowners:
 ha_domain: amcrest
 ---
 
-The `amcrest` camera platform allows you to integrate your [Amcrest](https://amcrest.com/) IP camera in Home Assistant.
+The `amcrest` camera platform allows you to integrate your [Amcrest](https://amcrest.com/) or Dahua IP camera in Home Assistant.
 
 There is currently support for the following device types within Home Assistant:
 
@@ -153,7 +153,8 @@ Available services:
 `enable_motion_recording`, `disable_motion_recording`,
 `enable_recording`, `disable_recording`,
 `goto_preset`, `set_color_bw`,
-`start_tour` and `stop_tour`
+`start_tour`, `stop_tour`, and
+`ptz_control`
 
 #### Service `enable_audio`/`disable_audio`
 
@@ -161,7 +162,7 @@ These services enable or disable the camera's audio stream.
 
 Service data attribute | Optional | Description
 -|-|-
-`entity_id` | no | Name(s) of entities, e.g., `camera.living_room_camera`.
+`entity_id` | no | The entity ID of the camera to control. May be a list of multiple entity IDs. To target all cameras, set entity ID to `all`.
 
 #### Service `enable_motion_recording`/`disable_motion_recording`
 
@@ -169,7 +170,7 @@ These services enable or disable the camera to record a clip to its configured s
 
 Service data attribute | Optional | Description
 -|-|-
-`entity_id` | no | Name(s) of entities, e.g., `camera.living_room_camera`.
+`entity_id` | no | The entity ID of the camera to control. May be a list of multiple entity IDs. To target all cameras, set entity ID to `all`.
 
 #### Service `enable_recording`/`disable_recording`
 
@@ -177,7 +178,7 @@ These services enable or disable the camera to continuously record to its config
 
 Service data attribute | Optional | Description
 -|-|-
-`entity_id` | no | Name(s) of entities, e.g., `camera.living_room_camera`.
+`entity_id` | no | The entity ID of the camera to control. May be a list of multiple entity IDs. To target all cameras, set entity ID to `all`.
 
 #### Service `goto_preset`
 
@@ -185,7 +186,7 @@ This service will cause the camera to move to one of the PTZ locations configure
 
 Service data attribute | Optional | Description
 -|-|-
-`entity_id` | no | Name(s) of entities, e.g., `camera.living_room_camera`.
+`entity_id` | no | The entity ID of the camera to control. May be a list of multiple entity IDs. To target all cameras, set entity ID to `all`.
 `preset` | no | Preset number, starting from 1.
 
 #### Service `set_color_bw`
@@ -194,7 +195,7 @@ This service will set the color mode of the camera.
 
 Service data attribute | Optional | Description
 -|-|-
-`entity_id` | no | Name(s) of entities, e.g., `camera.living_room_camera`.
+`entity_id` | no | The entity ID of the camera to control. May be a list of multiple entity IDs. To target all cameras, set entity ID to `all`.
 `color_bw` | no | One of `auto`, `bw` or `color`.
 
 #### Service `start_tour`/`stop_tour`
@@ -203,7 +204,153 @@ These services start or stop the camera's PTZ tour function.
 
 Service data attribute | Optional | Description
 -|-|-
-`entity_id` | no | Name(s) of entities, e.g., `camera.living_room_camera`.
+`entity_id` | no | The entity ID of the camera to control. May be a list of multiple entity IDs. To target all cameras, set entity ID to `all`.
+
+#### Service `ptz_control`
+
+If your Amcrest or Dahua camera supports PTZ, you will be able to pan, tilt or zoom your camera.  
+
+Service data attribute | Optional | Description
+-|-|-
+ `entity_id` | no| The entity ID of the camera to control. May be a list of multiple entity IDs. To target all cameras, set entity ID to `all`.
+ `movement` | no | Direction of the movement. Allowed values: `zoom_in`, `zoom_out`, `up`, `down`, `left`, `right`, `right_up`, `right_down`, `left_up`,  `left_down`
+ `travel_time` | yes |Travel time in fractional seconds. Allowed values: `0` to `1`. Default: `0.2`.
+
+#### Notes
+
+- PTZ zoom capability does not control VariFocal lens adjustments.
+- There can be several seconds of lag before the video (snapshot or live) reflects the camera movement.
+
+### Example card with controls
+
+<p class='img'>
+  <img src='/images/integrations/amcrest/amcrest_ptz.jpg' alt='Screenshot using a picture-elements with PTZ controls.'>
+  Example showing an Amcrest IP2M-841 PT camera with controls for Pan and Tilt.
+</p>
+
+Using the following picture-elements card code, you can display a live video feed from an Amcrest camera with controls for moving or zooming the camera.
+
+```yaml
+type: picture-elements
+entity: camera.lakehouse
+camera_image: camera.lakehouse
+camera_view: live   # or auto for snapshot view
+elements:
+  - type: icon
+    icon: 'mdi:arrow-up'
+    style:
+      background: 'rgba(255, 255, 255, 0.25)'
+      right: 25px
+      bottom: 50px
+    tap_action:
+      action: call-service
+      service: amcrest.ptz_control
+      service_data:
+        entity_id: camera.lakehouse
+        movement: up
+  - type: icon
+    icon: 'mdi:arrow-down'
+    style:
+      background: 'rgba(255, 255, 255, 0.25)'
+      right: 25px
+      bottom: 0px
+    tap_action:
+      action: call-service
+      service: amcrest.ptz_control
+      service_data:
+        entity_id: camera.lakehouse
+        movement: down
+  - type: icon
+    icon: 'mdi:arrow-left'
+    style:
+      background: 'rgba(255, 255, 255, 0.25)'
+      right: 50px
+      bottom: 25px
+    tap_action:
+      action: call-service
+      service: amcrest.ptz_control
+      service_data:
+        entity_id: camera.lakehouse
+        movement: left
+  - type: icon
+    icon: 'mdi:arrow-right'
+    style:
+      background: 'rgba(255, 255, 255, 0.25)'
+      right: 0px
+      bottom: 25px
+    tap_action:
+      action: call-service
+      service: amcrest.ptz_control
+      service_data:
+        entity_id: camera.lakehouse
+        movement: right
+  - type: icon
+    icon: 'mdi:arrow-top-left'
+    style:
+      background: 'rgba(255, 255, 255, 0.25)'
+      right: 50px
+      bottom: 50px
+    tap_action:
+      action: call-service
+      service: amcrest.ptz_control
+      service_data:
+        entity_id: camera.lakehouse
+        movement: left_up
+  - type: icon
+    icon: 'mdi:arrow-top-right'
+    style:
+      background: 'rgba(255, 255, 255, 0.25)'
+      right: 0px
+      bottom: 50px
+    tap_action:
+      action: call-service
+      service: amcrest.ptz_control
+      service_data:
+        entity_id: camera.lakehouse
+        movement: right_up
+  - type: icon
+    icon: 'mdi:arrow-bottom-left'
+    style:
+      background: 'rgba(255, 255, 255, 0.25)'
+      right: 50px
+      bottom: 0px
+    tap_action:
+      action: call-service
+      service: amcrest.ptz_control
+      service_data:
+        entity_id: camera.lakehouse
+        movement: left_down
+  - type: icon
+    icon: 'mdi:arrow-bottom-right'
+    style:
+      background: 'rgba(255, 255, 255, 0.25)'
+      right: 0px
+      bottom: 0px
+    tap_action:
+      action: call-service
+      service: amcrest.ptz_control
+      service_data:
+        entity_id: camera.lakehouse
+        movement: right_down
+  - type: icon
+    icon: 'mdi:magnify'
+    style:
+      background: 'rgba(255, 255, 255, 0.25)'
+      bottom: 25px
+      right: 25px
+    tap_action:
+      action: call-service
+      service: amcrest.ptz_control
+      service_data:
+        entity_id: camera.lakehouse
+        movement: zoom_in
+    hold_action:
+      action: call-service
+      service: amcrest.ptz_control
+      service_data:
+        entity_id: camera.lakehouse
+        movement: zoom_out
+```
 
 ## Advanced Configuration
 

source/_integrations/bmp280.markdown

@@ -0,0 +1,48 @@
+---
+title: Bosch BMP280 Environmental Sensor
+description: Instructions on how to integrate a BMP280 sensor into Home Assistant.
+ha_release: 0.108
+logo: raspberry-pi.png
+ha_category:
+  - DIY
+ha_iot_class: Local Polling
+ha_quality_scale: silver
+ha_code_owners:
+  - '@belidzs'
+---
+
+The `bmp280` sensor platform allows you to read temperature and pressure values of a [Bosch BMP280 Environmental sensor](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/pressure-sensors-bmp280-1.html) connected via [I2C](https://en.wikipedia.org/wiki/I²C) bus (SDA, SCL pins).
+
+This integration has been tested on a Raspberry Pi 4B, but it should work on any device which is supported by [CircuitPython](https://circuitpython.org/).
+
+## Configuration
+
+To use a BMP280 sensor in your installation, you have to enable I2C on your host device then configure the integration using the following example:
+
+```yaml
+sensor:
+  - platform: bmp280
+  - i2c_address: 0x77
+```
+
+{% configuration %}
+name:
+  description: The name of the sensor.
+  required: false
+  default: BMP280
+  type: string
+i2c_address:
+  description: I2C address of the sensor. It is either 0x76 or 0x77, depending on your actual wiring configuration.
+  required: true
+  type: integer
+{% endconfiguration %}
+
+## Setting up the I2C interface on the host device
+
+To get more information on how to set up the I2C interface on your Raspberry Pi, please refer to the [BME680 sensor integration](/integrations/bme680/#directions-for-installing-smbus-support-on-raspberry-pi).
+
+## Choosing the appropriate I2C address
+
+Please note that the I2C address of this device depends on the state of the `SDO` pin. If it is pulled down (to the `GND` rail) it will be `0x76`, if it's pulled up (to the `VCC` rail) it will be `0x77`.
+
+If you leave it floating then the address will be unpredictable or even worse, it can change over time. So it is recommended to hook up this pin to either the positive or the negative rail of your host device.

source/_integrations/brother.markdown

@@ -9,6 +9,7 @@ ha_config_flow: true
 ha_codeowners:
   - '@bieniu'
 ha_domain: brother
+ha_quality_scale: platinum
 ---
 
 The `Brother Printer` integration allows you to read current data from your local Brother printer.

source/_integrations/camera.mqtt.markdown

@@ -24,6 +24,10 @@ camera:
 ```
 
 {% configuration %}
+availability_topic:
+  description: The MQTT topic subscribed to receive availability (online/offline) updates.
+  required: false
+  type: string
 device:
   description: "Information about the device this camera is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set."
   required: false
@@ -57,6 +61,14 @@ device:
       description: 'Identifier of a device that routes messages between this device and Home Assistant. Examples of such devices are hubs, or parent devices of a sub-device. This is used to show device topology in Home Assistant.'
       required: false
       type: string
+json_attributes_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the JSON dictionary from messages received on the `json_attributes_topic`."
+  required: false
+  type: template
+json_attributes_topic:
+  description: The MQTT topic subscribed to receive a JSON dictionary payload and then set as sensor attributes. Implies `force_update` of the current sensor state when a message is received on this topic.
+  required: false
+  type: string
 name:
   description: The name of the camera.
   required: false

source/_integrations/cover.markdown

@@ -23,6 +23,7 @@ The way these sensors are displayed in the frontend can be modified in the [cust
 - **damper**: Control of a mechanical damper that reduces airflow, sound, or light.
 - **door**: Control of a door or gate that provides access to an area.
 - **garage**: Control of a garage door that provides access to a garage.
+- **gate**: Control of a gate. Gates are found outside of a structure and are typically part of a fence.
 - **shade**: Control of shades, which are a continuous plane of material or connected cells that expanded or collapsed over an opening, such as window shades.
 - **shutter**: Control of shutters, which are linked slats that swing out/in to covering an opening or may be tilted to partially cover an opening, such as indoor or exterior window shutters.
 - **window**: Control of a physical window that opens and closes or may tilt.

source/_integrations/doorbird.markdown

@@ -7,8 +7,10 @@ ha_category:
   - Switch
 ha_release: 0.54
 ha_iot_class: Local Push
+ha_config_flow: true
 ha_codeowners:
   - '@oblogic7'
+  - '@bdraco'
 ha_domain: doorbird
 ---
 
@@ -30,7 +32,9 @@ It is recommended to set up a new account on your Doorbird App for use with Home
 
 ## Configuration
 
-To connect your device, add the following to your `configuration.yaml` file:
+To add `DoorBird` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **DoorBird**.
+
+Alternatively, add the following to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry

source/_integrations/elkm1.markdown

@@ -12,6 +12,9 @@ ha_category:
   - Switch
 ha_iot_class: Local Push
 ha_domain: elkm1
+ha_config_flow: true
+ha_codeowners:
+  - '@bdraco'
 ---
 
 The Elk-M1 is a home security and automation controller that is capable of alarm control panel functions and automation.
@@ -29,8 +32,9 @@ There is currently support for the following device types within Home Assistant:
 
 ## Configuration
 
-To integrate one or more Elk-M1 controllers with Home Assistant, add the following
+To add `ElkM1` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Elk-M1 Control**.
-section to your `configuration.yaml` file:
+
+Alternatively, add the following section to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
@@ -63,6 +67,11 @@ temperature_unit:
   required: false
   type: string
   default: F
+auto_configure:
+  description: Auto configure `area`, `counter`, `keypad`, `output`, `setting`, `task`, `thermostat`, `plc`, and `zone` by only adding elements that ElkM1 reports on the initial sync.
+  required: false
+  type: boolean
+  default: False
 area:
   description: Elk areas to include in Home Assistant.
   required: false
@@ -270,6 +279,16 @@ elkm1:
     exclude: [b12-d5]
 ```
 
+Example configuration using `auto_configure`:
+
+```yaml
+elkm1:
+  host: elks://IP_ADDRESS
+  username: USERNAME
+  password: PASSWORD
+  auto_configure: true
+```
+
 Example for a serial port instance on /dev/ttyUSB0 at 115200 baud:
 
 ```yaml

source/_integrations/freebox.markdown

@@ -10,6 +10,8 @@ ha_release: 0.85
 ha_iot_class: Local Polling
 ha_codeowners:
   - '@snoof85'
+  - '@Quentame'
+ha_config_flow: true
 ha_domain: freebox
 ---
 
@@ -17,15 +19,26 @@ The `freebox` integration allows you to observe and control [Freebox router](htt
 
 There is currently support for the following device types within Home Assistant:
 
-* [Sensor](#sensor) with traffic metrics
+* [Sensor](#sensor) with traffic and temperature metrics
 * [Device tracker](#presence-detection) for connected devices
 * [Switch](#switch) to control Wi-Fi
 
 ## Configuration
 
-If you have enabled the [discovery component](/integrations/discovery/),
+If you have enabled the [discovery integration](/integrations/discovery/), your Freebox should be detected automatically.
-your Freebox should be detected automatically. Otherwise, you can set it
+Otherwise, you can set it up manually via the frontend or via your `configuration.yaml` file.
-up manually in your `configuration.yaml` file:
+
+You can find out your Freebox host and port by opening this address <http://mafreebox.freebox.fr/api_version> in your browser.
+The returned JSON should contain an `api_domain` (`host`) and a `https_port` (`port`).
+Please consult the [API documentation](https://dev.freebox.fr/sdk/os/) for more information.
+
+### Via the frontend
+
+Menu: **Configuration** -> **Integrations**. Search for "Freebox", add your host and port, click submit.
+
+If you add the integration for the first time, follow the instructions in the [Initial setup](#initial-setup) section.
+
+### Via the configuration file
 
 ```yaml
 freebox:
@@ -44,28 +57,23 @@ port:
   type: string
 {% endconfiguration %}
 
-You can find out your Freebox host and port by opening the address <http://mafreebox.freebox.fr/api_version> in your browser. The
-returned JSON should contain an `api_domain` (`host`) and a `https_port` (`port`).
-Please consult the [API documentation](https://dev.freebox.fr/sdk/os/) for more information.
-
 <div class='note warning'>
   
-If you change your Freebox router for a new one, you need to delete the `freebox.conf` file located in your Home Assistant configuration directory to make the association again.
+  If you change your Freebox router for a new one, go into your Home Assistant configuration `.storage` folder and delete the "freebox" folder, then add the integration again.
 
 </div>
 
 ### Initial setup
 
 <div class='note warning'>
-You must have set a password for your Freebox router web administration page. Enable the option "Permettre les nouvelles demandes d'associations" and check that the option "Accès à distance sécurisé à Freebox OS" is active in "Gestion des ports" > "Connexions entrantes".
+
+  You must have set a password for your Freebox router web administration page. Enable the option "Permettre les nouvelles demandes d'associations" and check that the option "Accès à distance sécurisé à Freebox OS" is active in "Gestion des ports" > "Connexions entrantes".
+
 </div>
 
-The first time Home Assistant will connect to your Freebox, you will need to
+The first time Home Assistant will connect to your Freebox, you will need to authorize it by pressing the right arrow on the facade of the Freebox when prompted to do so.
-authorize it by pressing the right arrow on the facade of the Freebox when
-prompted to do so.
 
-To make the Wi-Fi switch and the reboot service working you will have to add "Modification des réglages de la Freebox
+To make the Wi-Fi switch and the reboot service working you will have to add "Modification des réglages de la Freebox" permission to Home Assistant application in "Paramètres de la Freebox" > "Gestion des accès" > "Applications".
-" permission to Home Assistant application in "Paramètres de la Freebox" > "Gestion des accès" > "Applications".
 
 ### Supported routers
 
@@ -77,8 +85,7 @@ Only the routers with Freebox OS are supported:
 
 ## Presence Detection
 
-This platform offers presence detection by keeping track of the
+This platform offers presence detection by keeping track of the devices connected to a [Freebox](https://www.free.fr/) router.
-devices connected to a [Freebox](https://www.free.fr/) router.
 
 ### Notes
 
@@ -93,8 +100,8 @@ refreshes the devices states.
 
 ## Sensor
 
-This platform offers you sensors to monitor a Freebox router. The monitored conditions are
+This platform offers you sensors to monitor a Freebox router.
-instant upload and download rates in KB/s.
+The monitored conditions are internal temperature and upload and download rates in KB/s.
 
 ## Service
 

source/_integrations/garmin_connect.markdown

@@ -104,4 +104,14 @@ Latest Respiration Update
 Highest Respiration
 Lowest Respiration
 Latest Respiration
+
+Weight
+BMI
+Body Fat
+Body Water
+Body Mass
+Muscle Mass
+Physique Rating
+Visceral Fat
+Metabolic Age
 ```

source/_integrations/harmony.markdown

@@ -5,8 +5,11 @@ ha_category:
   - Remote
 ha_iot_class: Local Push
 ha_release: 0.34
+ha_config_flow: true
 ha_codeowners:
   - '@ehendrix23'
+  - '@bramkragten'
+  - '@bdraco'
 ha_domain: harmony
 ---
 
@@ -18,10 +21,13 @@ Supported units:
 - Harmony Companion
 - Harmony Pro
 - Harmony Elite
+- Harmony Pro 2400
 
-The preferred way to setup the Harmony remote is by enabling the [discovery component](/integrations/discovery/).
+The preferred way to setup the Harmony remote for your installation is via **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Logitech Harmony Hub**.
 
-However, if you want to manually configure the device, you will need to add its settings to your `configuration.yaml` file:
+Once `Logitech Harmony Hub` has been configured, the default activity and duration in seconds between sending commands to a device can be adjusted in the settings via **Configuration** >> **Integrations** >> **Your Logitech Harmony Hub**
+
+Alternatively, if you want to manually configure the device, you will need to add its settings to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
@@ -29,14 +35,6 @@ remote:
   - platform: harmony
     name: Bedroom
     host: 10.168.1.13
-```
-
-You can override some default configuration values on a discovered hub (e.g., the `port` or `activity`) by adding a `configuration.yaml` setting. In this case leave the `host` setting empty so the platform will discover the host IP automatically, but set the `name` in the configuration to match exactly the name you have set for your Hub so the platform knows what Hub you are trying to configure.
-
-```yaml
-# Example configuration.yaml entry with discovery
-  - platform: harmony
-    name: Living Room
     activity: Watch TV
 ```
 
@@ -47,13 +45,8 @@ name:
   type: string
 host:
   description: The Harmony device's IP address. Leave empty for the IP to be discovered automatically.
-  required: false
+  required: true
   type: string
-port:
-  description: The Harmony device's port.
-  required: false
-  type: integer
-  default: 5222
 activity:
   description: Activity to use when `turn_on` service is called without any data. Overrides the `activity` setting for this discovered hub.
   required: false
@@ -63,16 +56,11 @@ delay_secs:
   required: false
   type: float
   default: 0.4
-hold_secs:
-  description: Default duration in seconds between sending the "press" command and sending the "release" command.
-  required: false
-  type: integer
-  default: 0
 {% endconfiguration %}
 
 ### Configuration file
 
-Upon startup one file will be written to your Home Assistant configuration directory per device in the following format: `harmony_REMOTENAME.conf`. The file will contain:
+Upon startup one file will be written to your Home Assistant configuration directory per device in the following format: `harmony_UNIQUE_ID.conf`. The file will contain:
 
 - List of all programmed activity names and ID numbers
 - List of all programmed device names and ID numbers

source/_integrations/here_travel_time.markdown

@@ -89,6 +89,15 @@ traffic_mode:
   required: false
   type: boolean
   default: false
+arrival:
+  description: "Time when travel is expected to end. A 24 hour time string like `08:00:00`. On a sensor update it will be combined with the current date to get travel time for that moment. Cannot be used in combination with `departure`. Can only be used in combination with `mode: publicTransportTimeTable`"
+  required: false
+  type: time
+departure:
+  description: "Time when travel is expected to end. A 24 hour time string like `08:00:00`. On a sensor update it will be combined with the current date to get travel time for that moment. Cannot be used in combination with `arrival`. The default is now (the current date and time)" 
+  required: false
+  type: time
+  default: "now"
 unit_system:
   description: "You can choose between `metric` or `imperial`."
   required: false
@@ -125,9 +134,8 @@ sensor:
     route_mode: fastest
     traffic_mode: false
     unit_system: imperial
+    departure: "17:00:00"
     scan_interval: 2678400 # 1 month
-    
-
 ```
 
 ## Entity Tracking

source/_integrations/homekit_controller.markdown

@@ -36,7 +36,7 @@ There is currently support for the following device types within Home Assistant:
 - Cover (HomeKit garage door openers, windows, or window coverings)
 - Light (HomeKit lights)
 - Lock (HomeKit lock)
-- Switch (HomeKit switches)
+- Switch (HomeKit switches, outlets and valves)
 - Binary Sensor (HomeKit motion, contact, occupancy and smoke sensors)
 - Sensor (HomeKit humidity, temperature, co2 and light level sensors)
 - Fan

source/_integrations/hue.markdown

@@ -20,6 +20,7 @@ There is currently support for the following device types within Home Assistant:
 
 - Lights
 - Motion sensors (including temperature and light level sensors)
+- Hue switches (as device triggers for automations and also exposed as battery sensors when they are battery-powered)
 
 To set up this integration, click Configuration in the sidebar and then click Integrations. You should see "Philips Hue" in the discovered section (if you do not, click the + icon in the lower right and find Philips Hue). Click configure and you will be presented with the initiation dialog. This will prompt you to press the button on your Hue bridge to register the hub with Home Assistant. After you click submit, you will have the opportunity to select the area that your bridge is located.
 

source/_integrations/ipp.md

@@ -0,0 +1,21 @@
+---
+title: Internet Printing Protocol (IPP)
+description: Instructions on how to integrate printers that support the Internet Printing Protocol (IPP) into Home Assistant.
+ha_category:
+  - System Monitor
+ha_release: 0.108
+ha_iot_class: Local Polling
+ha_config_flow: true
+ha_quality_scale: platinum
+ha_codeowners:
+  - '@ctalkington'
+ha_domain: ipp
+---
+
+The `Internet Printing Protocol (IPP)` integration allows you to read current data from your networked printer that supports the [Internet Printing Protocol](https://www.pwg.org/ipp/everywhere.html).
+
+It provides information about the printer's state and remaining ink levels.
+
+## Configuration
+
+To add `Internet Printing Protocol (IPP)` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Internet Printing Protocol (IPP)**.

source/_integrations/kef.markdown

@@ -74,7 +74,7 @@ supports_on:
   type: integer
 {% endconfiguration %}
 
-## Advanced configuration example
+## Advanced - configuration example
 
 ```yaml
 # Example configuration.yaml entry
@@ -87,7 +87,90 @@ media_player:
    volume_step: 0.05
 ```
 
-Notes:
+## Services
+
+Just like in the KEF Control app, we can change the digital signal processing (DSP) settings.
+
+The speaker's current DSP settings are updated automatically each hour and after each service call.
+To update the settings manually, use `kef.update_dsp`.
+
+### Service `kef.update_dsp`
+
+Update all DSP settings.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| entity_id              | No       | The entity_id of the KEF speaker. |
+
+### Service `kef.set_mode`
+
+Set the mode of the speaker. When optional attributes are left out, the setting will be unchanged.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| entity_id              | No       | The entity_id of the KEF speaker. |
+| desk_mode              | Yes      | "Desk mode" (`true` or `false`) |
+| wall_mode              | Yes      | "Wall mode" (`true` or `false`) |
+| phase_correction       | Yes      | "Phase correction" (`true` or `false`) |
+| high_pass              | Yes      | "High-pass mode" (`true` or `false`) |
+| sub_polarity           | Yes      | "Sub polarity" (`-` or `+`) |
+| bass_extension         | Yes      | "Bass extension" selector (`Less`, `Standard`, or `Extra`) |
+
+### Service `kef.set_desk_db`
+
+Set the "Desk mode" slider of the speaker in dB.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| entity_id              | No       | The entity_id of the KEF speaker. |
+| db_value               | No       | Value of the slider (-6 to 0 with steps of 0.5) |
+
+### Service `kef.set_wall_db`
+
+Set the "Wall mode" slider of the speaker in dB.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| entity_id              | No       | The entity_id of the KEF speaker. |
+| db_value               | No       | Value of the slider (-6 to 0 with steps of 0.5) |
+
+### Service `kef.set_treble_db`
+
+Set desk the "Treble trim" slider of the speaker in dB.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| entity_id              | No       | The entity_id of the KEF speaker. |
+| db_value               | No       | Value of the slider (-2 to 2 with steps of 0.5) |
+
+### Service `kef.set_high_hz`
+
+Set the "High-pass mode" slider of the speaker in Hz.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| entity_id              | No       | The entity_id of the KEF speaker. |
+| hz_value               | No       | Value of the slider (50 to 120 with steps of 5) |
+
+### Service `kef.set_low_hz`
+
+Set the "Sub out low-pass frequency" slider of the speaker in Hz.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| entity_id              | No       | The entity_id of the KEF speaker. |
+| hz_value               | No       | Value of the slider (40 to 250 with steps of 5) |
+
+### Service `kef.set_sub_db`
+
+Set the "Sub gain" slider of the speaker in dB.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| entity_id              | No       | The entity_id of the KEF speaker. |
+| db_value               | No       | Value of the slider (-10 to 10 with steps of 1) |
+
+## Notes
 
 - The LS50 Wireless was tested with the latest firmware of 19-11-2019: `p6.3001902221.105039422` and older firmware: `p6.2101809171.105039422`
 - The LSX Wireless was tested with the latest firmware of 10-10-2019 v4.1: `p20.4101909240.105243`

source/_integrations/konnected.markdown

@@ -65,23 +65,43 @@ The settings UI starts by having you configure the general behavior of each zone
 ##### Binary Sensor:
 
 **Binary Sensor Type:** The type of sensor connected to the zone.
+
 **Name (optional)** The friendly name for the entity associated with the zone.
+
 **Invert the open/close state:** Inverts the open/closed meaning of a binary sensor circuit. Commonly needed for normally open wired smoke alarm circuits.
 
 ##### Digital Sensor:
 
 **Sensor Type:** The type of sensor connected to the zone - either `dht` or `ds18b20`.
+
 **Name (optional)** The friendly name for the entities associated with the zone.
+
 **Poll Interval (optional):** How often in minutes to poll the sensor for updates.
 
 ##### Switchable Output:
 
 **Name: (optional)** The friendly name for the entity associated with the zone.
+
 **Output when on:** The state of the switch when activated.
+
 **Pulse Duration (optional):** The duration in ms to pulse the switch once activated.
+
 **Pause between pulses (optional):** The duration in ms to wait between pulses when activated.
+
 **Times to repeat (optional):** The number of times to repeat the pulse each time the switch is activated.
 
+**Configure additional states for this zone:** Selecting "No" will complete configuration for the zone and proceed to options for the next zone. Select "Yes" if you need to create additional output states for this zone.  
+
+#### Using Settings UI to Configure Additional Panel Behavior
+
+Once all zones are configured you'll be presented with the configuration for additional panel behaviors.
+
+**Blink panel LED on when sending state change:** The desired LED behavior for the panel.
+
+**Override default Home Assistant API host panel URL:** The Konnected Alarm Panel post sensor states back to the Home Assistant API.  If this value is unchecked the panel will default postbacks using `base_url` in the `http` component. If you've set `base_url` to an external hostname, then you'll want to check this field and set the **Override API host URL** to your _local_ IP address and port (e.g., `http://192.168.1.101:8123`).
+
+**Override API host URL (optional):** The host info to use if you checked **Override default Home Assistant API host panel URL** in the step above. This is ignored if **Override default Home Assistant API host panel URL** is unchecked.
+
 ### YAML Configuration
 
 If you prefer you can utilize a `konnected` section in the `configuration.yaml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them. If using `configuration.yaml` the configuration will be one-time imported when going through the Configuration Flow for the panel. **Note that you must still complete the UI based setup before the integration will be configured and entities created/accessible.**
@@ -313,6 +333,10 @@ Konnected runs on an ESP8266 board with the NodeMCU firmware. It is commonly use
 
 ## Revision History
 
+### 0.108
+
+- Multiple output states for a zone. Details on configuring additional panel behaviors via the UI.
+
 ### 0.106
 
 - Added information on configuration and options flow. Mention that alarm panel FW should be updated before connecting.

source/_integrations/lutron.markdown

@@ -74,7 +74,7 @@ After setup, scenes will appear in Home Assistant using the area, keypad and but
 
 ## Occupancy Sensors
 
-Any configured Powr Savr occuancy sensors will be added as occupancy binary sensors. Lutron reports occupancy for an area, rather than reporting individual sensors. Sensitivity and timeouts are controlled on the sensors themselves, not in software.
+Any configured Powr Savr occupancy sensors will be added as occupancy binary sensors. Lutron reports occupancy for an area, rather than reporting individual sensors. Sensitivity and timeouts are controlled on the sensors themselves, not in software.
 
 ## Example Automations
 

source/_integrations/lutron_caseta.markdown

@@ -9,22 +9,24 @@ ha_category:
   - Scene
   - Switch
   - Fan
+  - Binary Sensor
 ha_release: 0.41
 ha_iot_class: Local Polling
 ha_domain: lutron_caseta
 ---
 
-[Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches, dimmers, occupancy sensors, HVAC controls, etc. The `lutron_caseta` integration in Home Assistant is responsible for communicating with the Lutron Caseta Smart Bridge for the [Caseta](https://www.casetawireless.com/) product line of dimmers, switches and shades.
+[Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches, dimmers, occupancy sensors, HVAC controls, etc. The `lutron_caseta` integration in Home Assistant is responsible for communicating with the Lutron Caseta Smart Bridge for the [Caseta](https://www.casetawireless.com/) product line of dimmers, switches, shades, and sensors. It will also communicate with the Lutron Radio RA2 Main Repeater for the [RA2 Select](http://www.lutron.com/en-US/Products/Pages/WholeHomeSystems/RA2Select/Overview.aspx) product line of dimmers, switches, shades, and sensors.
 
-This integration only supports the [Caseta](https://www.casetawireless.com/) line of products. Both Smart Bridge (L-BDG2-WH) and Smart Bridge PRO (L-BDGPRO2-WH) models are supported. For the RadioRA 2 product line, see the [Lutron component](/integrations/lutron/).
+This integration only supports the [Caseta](https://www.casetawireless.com/) line of products. The Smart Bridge (L-BDG2-WH), Smart Bridge PRO (L-BDGPRO2-WH), and RA2 Select (RR-SEL-REP2-BL) models are supported. For the RadioRA 2 and HomeWorks QS product lines, see the [Lutron component](/integrations/lutron/).
 
-The currently supported Caseta devices are:
+The currently supported Caseta and RA2 Select devices are:
 
 - Wall and plug-in dimmers as [lights](#light)
 - Wall switches as [switches](#switch)
 - Scenes as [scenes](#scene)
 - Lutron shades as [covers](#cover)
 - Lutron smart [fan](#fan) speed control
+- Lutron Occupancy/Vacancy [sensors](#sensor)
 
 When configured, the `lutron_caseta` integration will automatically discover the currently supported devices as setup in the Lutron Smart Bridge. The name assigned in the Lutron mobile app will be used to form the `entity_id` used in Home Assistant. e.g., a dimmer called 'Lamp' in a room called 'Bedroom' becomes `light.bedroom_lamp` in Home Assistant.
 
@@ -115,3 +117,17 @@ After setup, fans will appear in Home Assistant using an `entity_id` based on th
 For more information on working with fans in Home Assistant, see the [Fans component](/components/fan/).
 
 Available services: `fan.turn_on`, `fan.turn_off`, and `fan.set_speed`.
+
+## Sensor
+
+Occupancy sensors can be added to a Lutron Caseta system to trigger events when an area becomes vacant and, optionally, occupied. However, Lutron systems report occupancy and vacancy statuses only in *occupancy groups* -- that is, groups of one or more sensors.
+
+Occupancy groups will appear in Home Assistant using an `entity_id` based on the area name in which the first sensor of the group is located. For example, one or more sensors in the Master Bathroom will appear in Home Assistant as `binary_sensor.master_bathroom_occupancy`.
+
+An occupancy group is considered occupied if any of the sensors in the group are currently in an "occupied" state. Specifically, this means that motion has been detected more recently than that sensor's particular timeout setting. Only after all sensors in an occupancy group report being vacant does the occupancy group itself report being vacant.
+
+Lutron Caseta occupancy sensors support 4 different timeouts and 3 different sensitivity levels, but those are only controllable from the devices themselves and cannot be set from either Home Assistant or even the Caseta mobile app.
+
+Because Lutron Caseta devices automatically report state to Home Assistant (rather than relying on polling), occupancy status updates occur almost instantaneously.
+
+For more information on working with binary sensors in Home Assistant, see the [Binary Sensors Component](/components/binary_sensor/)

source/_integrations/miflora.markdown

@@ -103,6 +103,11 @@ adapter:
   required: false
   default: hci0
   type: string
+go_unavailable_timeout:
+  description: "Timeout to report this device as unavailable. This option hides a bad link quality"
+  required: false
+  default: 7200
+  type: integer
 {% endconfiguration %}
 
 <div class='note warning'>
@@ -123,6 +128,7 @@ sensor:
     name: Flower 1
     force_update: true
     median: 3
+    go_unavailable_timeout: 43200
     monitored_conditions:
       - moisture
       - light
@@ -130,3 +136,18 @@ sensor:
       - conductivity
       - battery
 ```
+An automation example to report a battery failure:
+
+```yaml
+- id: flower1_moisture_unavailable_check
+  alias: Flower 1 sensors available
+  trigger:
+  - entity_id: sensor.flower1_moisture
+    for: 24:00:00
+    platform: state
+    to: unavailable
+  action:
+  - data_template:
+      message: "Flower 1 moisture is unavailable for more than 24 hours"
+    service: notify.notifier_telegram_someone
+```

source/_integrations/modbus.markdown

@@ -53,6 +53,11 @@ timeout:
   required: false
   default: 3
   type: integer
+delay:
+  description: Time to sleep in seconds after connecting and before sending messages. Some modbus-tcp servers need a short delay typically 1-2 seconds in order to prepare the communication. If a server accepts connecting, but there is no response to the requests send, this parameter might help.
+  required: false
+  default: 0
+  type: integer
 {% endconfiguration %}
 
 ### Serial connection

source/_integrations/monoprice.markdown

@@ -4,6 +4,7 @@ description: Instructions on how to integrate Monoprice 6-Zone Home Audio Contro
 ha_category:
   - Media Player
 ha_release: 0.56
+ha_config_flow: true
 ha_iot_class: Local Polling
 ha_codeowners:
   - '@etsinko'
@@ -12,53 +13,28 @@ ha_domain: monoprice
 
 The `monoprice` platform allows you to control [Monoprice 6-Zone Amplifier](https://www.monoprice.com/product?p_id=10761) using a serial connection.
 
-To add a Monoprice device to your installation, add the following to your `configuration.yaml` file:
+## Configuration
 
-```yaml
+Menu: **Configuration** -> **Integrations**.
-# Example configuration.yaml entry
-media_player:
-  - platform: monoprice
-    port: /dev/ttyUSB0
-    zones:
-      11:
-        name: Main Bedroom
-      12:
-        name: Living Room
-      13:
-        name: Kitchen
-      14:
-        name: Bathroom
-      15:
-        name: Dining Room
-      16:
-        name: Guest Bedroom
-    sources:
-      1:
-        name: Sonos
-      5:
-        name: Chromecast
-```
 
-{% configuration %}
+Click on the `+` sign to add an integration and click on **Monoprice**.
-port:
+Select the serial port to which Monoprice amplifier is connected, and name the six sources (leave sources you're not using empty).
-  description: The serial port to which Monoprice amplifier is connected.
+
-  required: true
+Sources can also be later edited from the integration options (gear icon in the top right when selecting the integration). In order to remove an existing source, you'll need to replace it with a space (simply removing its name will still keep it in place). Note that editing sources will remove the snapshot you may have saved.
-  type: string
+
-zones:
+## Zone Management
-  description: This is the list of zones available. Valid zones are 11, 12, 13, 14, 15 or 16. In case multiple Monoprice devices are stacked together the list of valid zones is extended by 21, 22, 23, 24, 25 or 26 for the second device and 31, 32, 33, 34, 35 or 36 for the third device. Each zone must have a name assigned to it.
+
-  required: true
+Devices and entities are created for each of the possible 18 zones, and can be enabled, disabled and renamed through regular Home Assisant methods.
-  type: integer
+By default, the first 6 zones (11..16) are enabled, while the 12 extension zones (21..26, and 31..36) are disabled.
-sources:
+
-  description: The list of sources available. Valid source numbers are 1, 2, 3, 4, 5 or 6. Each source number corresponds to the input number on the Monoprice amplifier. Similar to zones, each source must have a name assigned to it.
+## Services
-  required: true
-  type: integer
-{% endconfiguration %}
 
 ### Service `monoprice.snapshot`
 
-Take a snapshot of one or more zones' states. This service, and the following one are useful if you want to play a doorbell or notification sound and resume playback afterward. If no `entity_id` is provided, all zones are snapshotted.
+Take a snapshot of one or more zones' states. This service, and the following one are useful if you want to play a doorbell or notification sound and resume playback afterward. If `entity_id` is `all`, all zones are snapshotted.
 
 The following attributes are stored in a snapshot:
+
 - Power status (On/Off)
 - Mute status (On/Off)
 - Volume level
@@ -70,7 +46,7 @@ The following attributes are stored in a snapshot:
 
 ### Service `monoprice.restore`
 
-Restore a previously taken snapshot of one or more speakers. If no `entity_id` is provided, all zones are restored.
+Restore a previously taken snapshot of one or more speakers. If `entity_id` is `all`, all zones are restored.
 
 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |

source/_integrations/mopar.markdown

@@ -1,65 +0,0 @@
----
-title: Mopar
-description: Instructions on how to integrate Mopar vehicles into Home Assistant.
-ha_category:
-  - Car
-  - Sensor
-  - Switch
-  - Lock
-ha_release: 0.53
-ha_iot_class: Cloud Polling
-ha_domain: mopar
----
-
-The `mopar` integration provides the following for owners of FCA vehicles with a uConnect subscription:
-
-- Sensor per vehicle with vehicle health report and other meta-data
-- Lock per vehicle allowing to lock/unlock the vehicle
-- Switch per vehicle allowing to turn the engine on and off
-- A service for running the horn & lights
-
-## Setup
-
-Be sure you have a [mopar.com](http://mopar.com) account with your vehicle(s) registered by VIN. You must also have a current uConnect subscription.
-
-## Configuration
-
-To enable this component, add the following lines to your `configuration.yaml`. All platforms will be automatically loaded.
-
-```yaml
-# Example configuration.yaml entry
-mopar:
-  username: YOUR_USERNAME
-  password: YOUR_PASSWORD
-  pin: YOUR_UCONNECT_PIN
-```
-
-{% configuration %}
-username:
-  description: Your mopar.com username.
-  required: true
-  type: string
-password:
-  description: Your mopar.com password.
-  required: true
-  type: string
-pin:
-  description: The pin for your account.
-  required: true
-  type: string
-{% endconfiguration %}
-
-## Service
-
-Call the `mopar.sound_horn` service to sound the horn and flash the lights on your vehicle.
-
-| Service data attribute | Description |
-| `vehicle_index`        | The index of the vehicle to trigger. This is exposed in the sensor's device attributes. |
-
-Example data:
-
-```json
-{
-  "vehicle_index": 0
-}
-```

source/_integrations/myq.markdown

@@ -3,8 +3,12 @@ title: MyQ
 description: Instructions on how to integrate MyQ-Enabled garage door covers into Home Assistant.
 ha_category:
   - Cover
+  - Binary Sensor
 ha_release: 0.39
 ha_iot_class: Cloud Polling
+ha_config_flow: true
+ha_codeowners:
+  - '@bdraco'
 ha_domain: myq
 ---
 
@@ -12,7 +16,9 @@ The `myq` cover platform lets you control MyQ-Enabled garage doors through Home
 
 ## Configuration
 
-To use your MyQ cover in your installation, add the following to your `configuration.yaml` file:
+To add `MyQ` cover to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **MyQ**.
+
+Alternatively, add the following to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
@@ -32,3 +38,11 @@ password:
   required: true
   type: string
 {% endconfiguration %}
+
+### Binary Sensor
+
+Your `MyQ` gateway will appear as a binary sensor that shows if the device is connected.
+
+### Cover
+
+Garage doors and gates linked to your `MyQ` account will appear as covers.

source/_integrations/nexia.markdown

@@ -0,0 +1,101 @@
+---
+title: Nexia
+description: Instructions on how to integrate Nexia Thermostats (Trane/American Standard) into Home Assistant.
+ha_category:
+  - Binary Sensor
+  - Sensor
+  - Climate
+  - Scene
+ha_release: 0.108
+ha_iot_class: Cloud Polling
+ha_config_flow: true
+ha_codeowners:
+  - '@bdraco'
+  - '@ryannazaretian'
+ha_domain: nexia
+---
+
+The `nexia` integration allows you to integrate your [Nexia](https://mynexia.com/) thermostats into Home Assistant.
+
+There is currently support for the following device types within Home Assistant:
+
+- [Binary Sensor](#binary-sensor)
+- [Climate](#climate)
+- [Sensor](#sensor)
+- [Scene](#scene)
+
+## Configuration
+
+You will need your mynexia.com username and password to use this module.
+
+To add `Nexia` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Nexia**.
+
+Alternatively, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+nexia:
+  username: YOUR_NEXIA_USERNAME
+  password: YOUR_NEXIA_PASSWORD
+```
+
+{% configuration %}
+username:
+  description: The username for accessing your Nexia account.
+  required: true
+  type: string
+password:
+  description: The password for accessing your Nexia account.
+  required: true
+  type: string
+{% endconfiguration %}
+
+### Binary Sensor
+
+The following binary sensors are added for each thermostat:
+
+- Blower Active
+
+### Sensor
+
+The following binary sensors are added for each thermostat:
+
+- Air Cleaner Mode
+- Current Compressor Speed
+- Requested Compressor Speed
+- Outdoor Temperature
+- Relative Humidity
+- System Status
+
+The following binary sensors are added for each thermostat zone:
+
+- Zone Temperature
+- Zone Setpoint Status
+- Zone Status
+
+### Climate
+
+The `nexia` climate platform lets you control a thermostat.
+
+### Scene
+
+The `nexia` scene platform lets you activate a nexia automation.
+
+### Service `nexia.set_aircleaner_mode`
+
+Sets the air cleaner mode. Options include 'auto', 'quick', and 
+'allergy'. This setting will affect all zones on the same thermostat.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | no | String or list of strings that point at `entity_id`'s of climate devices to control.
+| `aircleaner_mode` | no | 'auto', 'quick', or 'allergy'
+
+### Service `nexia.set_humidify_setpoint`
+
+Sets the humidify setpoint. This setting will affect all zones on the same thermostat.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | no | String or list of strings that point at `entity_id`'s of climate devices to control.
+| `humidity` | no | Humidify setpoint level, from 35 to 65. 

source/_integrations/nextcloud.markdown

@@ -0,0 +1,45 @@
+---
+title: Nextcloud Sensor
+description: Instructions on how to integrate Nextcloud monitor api data into Home Assistant.
+ha_category:
+  - Sensor
+ha_iot_class: Cloud Polling
+ha_release: 0.108
+ha_domain: nextcloud
+---
+
+The `nextcloud` integration pulls summary [Nextcloud](https://nextcloud.com/) information into Home Assistant.
+
+![Nextcloud Example Sensor]('/images/screenshots/nextcloud-sample-sensor.png')
+
+## Configuration
+
+This integration requires access to the monitor API of a Nextcloud instance (This is generally an admin user).
+
+You should also generate an App password from the Nextcloud web UI: **Settings** > **Security** > **Devices & sessions** > **Create new app password**.
+
+Once you have generated the App password, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+nextcloud:
+  url: Https://YOUR_NEXTCLOUD_URL
+  username: YOUR_USERNAME
+  password: YOUR_APP_PASSWORD
+
+```
+
+{% configuration %}
+url:
+  description: The full URL to your Nextcloud instance.
+  required: true
+  type: string
+username:
+  description: The username of a Nextcloud user that has access to the Nextcloud monitor API.
+  required: true
+  type: string
+password:
+  description: The app password generated from the Nextcloud security settings page.
+  required: true
+  type: string
+{% endconfiguration %}

source/_integrations/nuheat.markdown

@@ -6,6 +6,9 @@ ha_category:
 ha_release: 0.61
 ha_iot_class: Cloud Polling
 ha_domain: nuheat
+ha_config_flow: true
+ha_codeowners:
+  - '@bdraco'
 ---
 
 The `nuheat` integration lets control your connected [NuHeat Signature](https://www.nuheat.com/products/thermostats/signature-thermostat) floor heating thermostats from [NuHeat](https://www.nuheat.com/).
@@ -16,7 +19,9 @@ There is currently support for the following device types within Home Assistant:
 
 First, you will need to obtain your thermostat's numeric serial number or ID by logging into [MyNuHeat.com](https://mynuheat.com/) and selecting your thermostat(s).
 
-Once you have the Thermostat ID(s), add the following information to your `configuration.yaml` file:
+Once you have the Thermostat ID(s), to add `NuHeat` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **NuHeat**.
+
+Alternatively, add the following information to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
@@ -134,35 +139,18 @@ Returns the maximum supported temperature by the thermostat
 
 ## Services
 
-The following services are provided by the NuHeat Thermostat: `set_temperature`, `set_hvac_mode`, `set_preset_mode`, `resume_program`.
+The following services are provided by the NuHeat Thermostat: `set_temperature`, `set_hvac_mode`, `set_preset_mode`.
 
-The services `fan_min_on_time`, `set_aux_heat`, `set_away_mode`, `set_humidity`, `set_fan_mode`, and `set_swing_mode` offered by the [Climate component](/integrations/climate/) are not implemented for this thermostat.
+### Service `climate.set_hvac_mode` ([Climate integration](/integrations/climate/))
 
-### Service `set_temperature`
+NuHeat Thermostats do not have an off concept. Setting the temperature to `min_temp` and changing the mode to `heat` will cause the device to enter a `Permanent Hold` preset and will stop the thermostat from turning on unless you happen to live in a freezing climate.
 
-Puts the thermostat into an indefinite hold at the given temperature.
+### Service `climate.set_temperature` ([Climate integration](/integrations/climate/))
 
-| Service data attribute | Optional | Description |
+If the thermostat is in auto mode, it puts the thermostat into a temporary hold at the given temperature.
-| ---------------------- | -------- | ----------- |
-| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Use `entity_id: all` to target all.
-| `temperature` | no | Desired target temperature (when not in auto mode)
 
-Only the target temperatures relevant for the current operation mode need to
+If the thermostat is in heat mode, it puts the thermostat into a permanent hold at the given temperature.
-be provided.
 
-### Service `set_preset_mode`
+### Service `climate.set_preset_mode` ([Climate integration](/integrations/climate/))
 
-Sets the thermostat's preset mode. Without a preset mode set it run the thermostat's programmed schedule, "temperature" (to indefinitely hold the thermostat's current target temperature), or "temporary_temperature" (to hold the thermostat's current target temperature until the thermostat's next scheduled event).
+The following presets are available: `Run Schedule`, `Temporary Hold`, `Permanent Hold`.
-
-| Service data attribute | Optional | Description |
-| ---------------------- | -------- | ----------- |
-| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Use `entity_id: all` to target all.
-| `hold_mode` | no | New value of hold mode.
-
-### Service `nuheat.resume_program`
-
-Resumes the currently active schedule.
-
-| Service data attribute | Optional | Description |
-| ---------------------- | -------- | ----------- |
-| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Use `entity_id: all` to target all.

source/_integrations/nut.markdown

@@ -6,13 +6,18 @@ ha_category:
 ha_iot_class: Local Polling
 ha_release: 0.34
 ha_domain: nut
+ha_config_flow: true
+ha_codeowners:
+  - '@bdraco'
 ---
 
 The `nut` sensor platform allows you to monitor a UPS (battery backup) by using data from a [NUT](https://networkupstools.org/) (Network UPS Tools) server.
 
 ## Configuration
 
-To use this sensor platform, you need to add the following to your `configuration.yaml` file:
+To add `nut` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Network UPS Tools (NUT)**.
+
+Alternatively, you need to add the following to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry

source/_integrations/powerwall.markdown

@@ -0,0 +1,62 @@
+---
+title: Telsa Powerwall
+description: Instructions on how to integrate Tesla Power Walls into Home Assistant.
+ha_category:
+  - Binary Sensor
+  - Sensor
+ha_release: 0.108
+ha_iot_class: Local Polling
+ha_config_flow: true
+ha_codeowners:
+  - '@bdraco'
+ha_domain: powerwall
+---
+
+The `powerwall` integration allows you to integrate your [Tesla Powerwall](https://www.tesla.com/powerwall) into Home Assistant.
+
+There is currently support for the following device types within Home Assistant:
+
+- [Binary Sensor](#binary-sensor)
+- [Sensor](#sensor)
+
+## Configuration
+
+You will need the IP Address of your Powerwall to use this module.
+
+To add `Tesla Powerwall` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Tesla Powerwall**.
+
+Alternatively, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+powerwall:
+  ip_address: YOUR_POWERWALL_IP
+```
+
+{% configuration %}
+ip_address:
+  description: The IP address of your Powerwall.
+  required: true
+  type: string
+{% endconfiguration %}
+
+### Binary Sensor
+
+The following binary sensors are added for each Powerwall:
+
+- Powerwall Status
+- Powerwall Connected to Tesla
+- Grid Status
+
+### Sensor
+
+The following binary sensors are added for each Powerwall:
+
+- Powerwall Charge
+- Powerwall Site Now
+- Powerwall Load Now
+- Powerwall Battery Now
+- Powerwall Frequency Now (if applicable)
+- Powerwall Busway Now (if applicable)
+- Powerwall Solar Now (if applicable)
+- Powerwall Generator Now (if applicable)

source/_integrations/pvpc_hourly_pricing.markdown

@@ -0,0 +1,82 @@
+---
+title: PVPC Hourly Pricing
+description: Instructions on how to set up the PVPC Hourly Pricing sensor in Home Assistant.
+ha_category:
+  - Energy
+ha_release: '0.108'
+ha_iot_class: Cloud Polling
+ha_quality_scale: platinum
+ha_config_flow: true
+ha_codeowners:
+  - '@azogue'
+ha_domain: pvpc_hourly_pricing
+---
+
+This sensor uses the official API to get the hourly price of electricity in Spain from https://www.esios.ree.es/en/pvpc.
+
+Specifically, it shows the current __active energy invoicing price (FEU)__ in €/kWh, 
+which is the energy term hourly price applied in the consumers' electrical bill 
+with a contracted power not exceeding 10 kW and which are under the PVPC 
+(Voluntary Price for Small Consumer).
+
+It includes the energy term of the access tolls, the charges and the production cost. It does not include taxes.
+The hourly prices are the same throughout the Spanish territory regardless of the time zone.
+
+It can be set up via the integrations panel in the configuration screen.
+
+<iframe src="https://www.esios.ree.es/en/embed/active-energy-invoicing-price-pvpc" width="100%" height="608"></iframe>
+
+More information available at http://www.cnmc.es/en/ and http://www.omie.es/en/
+
+## Configuration
+
+To configure PVPC Hourly Pricing, you can set it up via the integrations panel in the configuration screen.
+
+Set a name for the price sensor (default is `sensor.pvpc`) and select one of the three tariffs, 
+corresponding to your contracted rate, according to the number of billing periods per day 
+(one / peak + valley / shifted peak + valley).
+
+- 1 period: `normal`, for the "Default PVPC tariff, (2.0 A)".
+- 2 periods: `discrimination`, for the "Efficiency 2 periods (2.0 DHA)", with 10h peak interval from 11:00 UTC to 21:00 UTC.
+- 3 periods: `electric_car`, for the "Electric vehicle tariff (2.0 DHS)", optimized for electric car owners to charge at night.
+
+The default is `discrimination`, with 2 periods, as it is usually the cheapest one for home consumers. 
+
+You can add multiple sensors (up to 3, one per tariff) by adding them again through the integrations panel.
+
+### Advanced configuration
+
+PVPC Hourly Pricing allows manual configuration by adding a section to your `configuration.yaml`. 
+
+```yaml
+# Set up electricity price sensors as a component:
+pvpc_hourly_pricing:
+  - name: PVPC manual ve
+    tariff: electric_car
+  - name: PVPC manual nocturna
+    tariff: discrimination
+```
+
+{% configuration %}
+name:
+  description: Custom name for the sensor.
+  required: true
+  type: string
+tariff:
+  description: Contracted electric tariff.
+  required: true
+  default: discrimination
+  type: string
+{% endconfiguration %}
+
+
+<div class='note'>
+
+The sensor provides an hourly price for energy consumed, but the variable cost of energy is only one of the factors that add up to the electricity bill:
+* Fixed cost of contracted power
+* Fixed cost of energy consumed
+* Variable cost of energy consumed (the sensor's value)
+* Other fixed expenses, such as the rental of the electric meter
+* Multiple taxes applied
+
+</div>

source/_integrations/qvr_pro.markdown

@@ -42,6 +42,10 @@ password:
   description: The password for accessing your QVR account.
   required: true
   type: string
+port:
+  description: The port where QVR accepts connections.
+  required: false
+  type: integer
 exclude_channels:
   description: Comma separated list of channel numbers to be excluded.
   required: false

source/_integrations/rachio.markdown

@@ -28,7 +28,9 @@ They will be automatically added if the Rachio integration integration is loaded
 
 ## Configuration
 
-To add this platform to your installation, add the following to your `configuration.yaml` file:
+To add `Rachio` go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Rachio**.
+
+Alternatively, add the following to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry

source/_integrations/roku.markdown

@@ -8,18 +8,27 @@ ha_category:
 ha_iot_class: Local Polling
 ha_release: 0.86
 ha_domain: roku
+ha_config_flow: true
+ha_quality_scale: silver
 ha_codeowners:
   - '@ctalkington'
 ---
 
-The [Roku](https://www.roku.com/) integration allows integration of Roku, which will be automatically discovered if you enable the [discovery component](/integrations/discovery/).
+The Roku integration allows you to control a [Roku](https://www.roku.com/) device.
+
+### Configuration
+
+Go to the integrations page in your configuration and click on new integration -> Roku.
+If your Roku device is on, it has likely been discovered already and you just have to confirm the detected device.
 
 There is currently support for the following device types within Home Assistant:
 
 - Media Player
 - Remote
 
-The `roku` integration can also be forced to load by adding the following lines to your `configuration.yaml`:
+### YAML Configuration
+
+Manual configuration of your Roku device is also possible, add the following to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
@@ -34,12 +43,6 @@ host:
   type: string
 {% endconfiguration %}
 
-## Services
-
-### Service `roku_scan`
-
-Scans the local network for Rokus. All found devices are presented as a persistent notification.
-
 ## Remote
 
 The `roku` remote platform allows you to send remote control buttons to a Roku device. It is automatically set up when a Roku is configured.
@@ -90,7 +93,7 @@ data:
 
 ## Media Player
 
-When the Home Assistant Roku integration is enabled and has found a Roku device, in the Home Assistant GUI the Roku media player will show a listing of the installed channels, or apps, under “source”. Select one and it will attempt to launch the channel on your Roku device. This action can also be automated, but it requires you to acquire an extra piece of information; the ```appID``` for the channel specific to your Roku. Although this information is gathered by the Roku integration, at the moment it is not exposed to the end user. This item might be added in a future release. For now though, you can easily get the information yourself. All you need to do is a simple GET API call on the same network as your device.
+When the Home Assistant Roku integration is enabled and a Roku device has been configured, in the Home Assistant UI the Roku media player will show a listing of the installed channels, or apps, under “source”. Select one and it will attempt to launch the channel on your Roku device. This action can also be automated, but it requires you to acquire an extra piece of information; the ```appID``` for the channel specific to your Roku. Although this information is gathered by the Roku integration, at the moment it is not exposed to the end user. This item might be added in a future release. For now though, you can easily get the information yourself. All you need to do is a simple GET API call on the same network as your device.
 
 The API calls are like this:
 

source/_integrations/rtorrent.markdown

@@ -21,6 +21,12 @@ sensor:
       - 'current_status'
       - 'download_speed'
       - 'upload_speed'
+      - 'all_torrents'
+      - 'stopped_torrents'
+      - 'complete_torrents'
+      - 'uploading_torrents'
+      - 'downloading_torrents'
+      - 'active_torrents'
 ```
 
 This sensor requires the rTorrent XML-RPC API exposed on an HTTP interface.
@@ -49,4 +55,16 @@ monitored_variables:
       description: The current download speed.
     upload_speed:
       description: The current upload speed.
+    all_torrents:
+      description: The number of all torrents.
+    stopped_torrents:
+      description: The number of torrents that are stopped.
+    complete_torrents:
+      description: The number of torrents that are fully downloaded.
+    uploading_torrents:
+      description: The number of torrents that are seeding.
+    downloading_torrents:
+      description: The number of torrents that are leeching.
+    active_torrents:
+      description: The number of torrents that are actively ( measurable speed ) leeching, seeding or both.
 {% endconfiguration %}

source/_integrations/schluter.markdown

@@ -0,0 +1,50 @@
+---
+title: Schluter
+description: Instructions on how to integrate your Schluter DITRA-HEAT-E-WiFi thermostat into Home Assistant.
+ha_category:
+  - Climate
+ha_release: 0.108
+ha_iot_class: Cloud Polling
+ha_domain: schluter
+---
+
+The `schluter` integration allows you to integrate your [Schluter-DITRA-HEAT-E-WiFi](https://www.schluter.com/schluter-us/en_US/ditra-heat-wifi) electric floor heating thermostat in Home Assistant.
+
+<div class='note'>
+You will need to create a Schluter DITRA-HEAT account and register your thermostat with it. This can be done via the thermostat touchscreen, where an email will be sent to you to confirm your account.
+</div>
+
+## Configuration
+
+You will need your Schluter login information (email and password) to use this module.
+
+To set it up, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+schluter:
+  username: YOUR_SCHLUTER_EMAIL
+  password: YOUR_SCHLUTER_PASSWORD
+```
+
+{% configuration %}
+username:
+  description: The email for accessing your Schluter account.
+  required: true
+  type: string
+password:
+  description: The password for accessing your Schluter account.
+  required: true
+  type: string
+{% endconfiguration %}
+
+Once Home Assistant is started, you will have access to any thermostats registered with your account.
+
+### Supported Features
+
+Currently, this integration supports the following features:
+
+- Retrieving current temperature & target temperature
+- Setting target temperature
+
+When adjusting the temperature via Home Assistant, it will place the thermostat in "permanent mode", meaning schedules programmed within the thermostat will be ignored. You can return to scheduled mode by pressing the "Return to Schedule" button on the thermostat.

source/_integrations/sensor.mqtt.markdown

@@ -78,10 +78,6 @@ icon:
   description: The icon for the sensor.
   required: false
   type: icon
-json_attributes:
-  description: (Deprecated, replaced by json_attributes_topic) A list of keys to extract values from a JSON dictionary payload and then set as sensor attributes.
-  required: false
-  type: [string, list]
 json_attributes_template:
   description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the JSON dictionary from messages received on the `json_attributes_topic`."
   required: false

source/_integrations/slack.markdown

@@ -74,77 +74,65 @@ The following attributes can be placed inside `data` for extended functionality.
 
 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
-| `file`                 |      yes | Groups the attributes for file upload. If present, either `url` or `path` have to be provided.
+| `file`                   |      yes | Local path of file, photo, etc. to post to Slack.
-| `path `                |      yes | Local path of file, photo etc to post to Slack. Is placed inside `file`.
+| `attachments`            |      yes | Array of [Slack attachments](https://api.slack.com/messaging/composing/layouts#attachments) (legacy). *NOTE*: if using `attachments`, they are shown **in addition** to `message`.
-| `url`                  |      yes | URL of file, photo etc to post to Slack. Is placed inside `file`.
+| `blocks`                 |      yes | Array of [Slack blocks](https://api.slack.com/messaging/composing/layouts). *NOTE*: if using `blocks`, they are shown **in addition** to `message`.
-| `username`             |      yes | Username if the URL requires authentication. Is placed inside `file`.
-| `password`             |      yes | Password if the URL requires authentication. Is placed inside `file`.
-| `auth`                 |      yes | If set to `digest` HTTP-Digest-Authentication is used. If missing HTTP-BASIC-Authentication is used. Is placed inside `file`.
-| `attachments`          |      yes | Array of [Slack attachments](https://api.slack.com/docs/message-attachments). See [the attachment documentation](https://api.slack.com/docs/message-attachments) for how to format. *NOTE*: if using `attachments`, they are shown **in addition** to `message`
 
-Example for posting file from URL:
+Example for posting a file from local path:
 
-```json
+```yaml
-{
+message: Message that will be added as a comment to the file.
-  "message":"Message that will be added as a comment to the file.",
+title: Title of the file.
-  "title":"Title of the file.",
+data:
-  "target": ["#channelname"], 
+  file: "/path/to/file.ext"
-  "data":{
-    "file":{
-      "url":"http://[url to file, photo, security camera etc]",
-      "username":"optional user, if necessary",
-      "password":"optional password, if necessary",
-      "auth":"digest"
-    }
-  }
-}
 ```
 
-Example for posting file from local path:
+Please note that `file` is validated against the `whitelist_external_dirs` in the `configuration.yaml`.
 
-```json
+Example for using the block framework:
-{
+
-  "message":"Message that will be added as a comment to the file.",
+```yaml
-  "title":"Title of the file.",
+message: Message that will be added as a comment to the file.
-  "data":{
+title: Title of the file.
-    "file":{
+data:
-      "path":"/path/to/file.ext"
+  attachments:
-    }
+    - type: section
-  }
+      text:
-}
+        type: mrkdwn
+        text: 'Danny Torrence left the following review for your property:'
+    - type: section
+      block_id: section567
+      text:
+        type: mrkdwn
+        text: "<https://example.com|Overlook Hotel> \n :star: \n Doors had too many
+          axe holes, guest in room 237 was far too rowdy, whole place felt stuck in
+          the 1920s."
+      accessory:
+        type: image
+        image_url: https://is5-ssl.mzstatic.com/image/thumb/Purple3/v4/d3/72/5c/d3725c8f-c642-5d69-1904-aa36e4297885/source/256x256bb.jpg
+        alt_text: Haunted hotel image
+    - type: section
+      block_id: section789
+      fields:
+      - type: mrkdwn
+        text: |-
+          *Average Rating*
+          1.0
 ```
 
-Please note that `path` is validated against the `whitelist_external_dirs` in the `configuration.yaml`.
+Example for using the legacy attachments framework:
 
-Example for posting formatted attachment:
+```yaml
-
+message: Message that will be added as a comment to the file.
-```json
+title: Title of the file.
-{
+data:
-  "message": "",
+  attachments:
-  "data": {
+    - title: WHAT A HORRIBLE NIGHT TO HAVE A CURSE.
-    "attachments": [
+      image_url: https://i.imgur.com/JEExnsI.gif
-      {
-        "title": "WHAT A HORRIBLE NIGHT TO HAVE A CURSE.",
-        "image_url": "https://i.imgur.com/JEExnsI.gif"
-      }
-    ]
-  }
-}
 ```
 
 You can also use YAML to send messages from your automations
 
-```yaml
-
-    - service: notify.slack
-      data:
-        message: "Latest notification"
-        title: "Latest image"
-        target: ["#home-assistant"]
-        data:
-          file:
-            path: "/myfile.jpg"
-```
 Please note that both `message` is a required key, but is always shown, so use an empty (`""`) string for `message` if you don't want the extra text.
 
 To use notifications, please see the [getting started with automation page](/getting-started/automation/).

source/_integrations/switchbot.markdown

@@ -31,6 +31,10 @@ name:
   description: The name used to display the switch in the frontend.
   required: false
   type: string
+password:
+  description: The password of the switch if set
+  required: false
+  type: string
 {% endconfiguration %}
 
 ## SwitchBot Entity

source/_integrations/tado.markdown

@@ -63,7 +63,7 @@ fallback:
 
 The Tado thermostats are internet connected thermostats. There exists an unofficial API at [my.tado.com](https://my.tado.com/), which is used by their website and now by this component.
 
-It currently supports presenting the current temperature, the setting temperature and the current operation mode. Switching the mode is also supported. If no user is at home anymore, the devices are showing the away-state. Switching to away-mode is not supported.
+It currently supports presenting the current temperature, the setting temperature and the current operation mode. The operation mode can be set to manual, auto and off. If no user is at home anymore, all Tado zones show the away-state (Only with Tado assist mode). Manually switching between home-mode and away-mode is also supported. Any Tado climate card can be switched between these presence modes, this changes the setting for the entire home.
 
 ## Presence Detection
 

source/_integrations/tesla.markdown

@@ -27,7 +27,7 @@ This integration provides the following platforms:
 - Device tracker - to track location of your car
 - Lock - Door lock and charger door lock. Enables you to control Tesla's door and charger door lock
 - Climate - HVAC control. Allow you to control (turn on/off, set target temperature) your Tesla's HVAC system.
-- Switch - Charger and max range switch to allow you to start/stop charging and set max range charging. Update switch to allow you to disable polling of vehicles to conserve battery
+- Switch - Charger and max range switch to allow you to start/stop charging and set max range charging. Update switch to allow you to disable polling of vehicles to conserve battery. Sentry mode switch to enable or disable Sentry mode.
 
 ## Configuration
 
@@ -59,3 +59,9 @@ scan_interval:
   type: integer
   default: 660
 {% endconfiguration %}
+
+## Options
+
+Tesla options are set via **Configuration** -> **Integrations** -> **Tesla** -> **Options**.
+
+* Wake cars on start - Whether to wake sleeping cars on Home Assistant startup. This allows a user to choose whether cars should continue to sleep (and not update information) or to wake up the cars potentially interrupting long term hibernation and increasing vampire drain.

source/_integrations/ubee.markdown

@@ -44,12 +44,14 @@ password:
 {% endconfiguration %}
 
 Supported models:
-- EVW3200-Wifi
+
-- EVW320B
+- Ambit EVW320B
-- EVW321B
+- Ambit EVW321B
-- EVW32C-0N
+- Ubee DDW36C
-- EVW3226@UPC
+- Ubee DVW32CB
-- DVW32CB
+- Ubee EVW3200-Wifi
+- Ubee EVW3226 (UPC)
+- Ubee EVW32C-0N
 
 <div class='note info'>
 

source/_integrations/unifi.markdown

@@ -5,8 +5,9 @@ ha_category:
   - Hub
   - Presence Detection
   - Switch
+  - Sensor
 ha_release: 0.81
-ha_iot_class: Local Polling
+ha_iot_class: Local Push
 ha_config_flow: true
 ha_quality_scale: platinum
 ha_codeowners:
@@ -20,70 +21,17 @@ There is currently support for the following device types within Home Assistant:
 
 - [Presence Detection](#presence-detection)
 - [Switch](#switch)
+- [Sensor](#sensor)
 
 ## Configuration
 
-Home Assistant offers UniFi integration through **Configuration** -> **Integrations** -> **UniFi Controller**.
+Home Assistant offers UniFi integration through **Configuration** -> **Integrations** -> **UniFi Controller**. Follow the instructions to get it set up.
 
-Enter `host address`, `user name` and `password` and then continue to select which `site` you want to connect to Home Assistant. The user needs administrator privileges in order to control POE switches.
+The user needs administrator privileges in order to control switches.
 
-### Extra configuration for device tracker
+### Extra configuration of the integration
 
-You can augment the behavior of UniFi device tracker by adding
+All configuration options are offered from the front end. Enter what UniFi integration you want to change options on and press the cog wheel.
-
-```yaml
-# Example configuration.yaml entry
-unifi:
-  controllers:
-    - host: unifi
-      site: My site
-      ssid_filter:
-        - 'HomeSSID'
-        - 'IoTSSID'
-```
-
-{% configuration %}
-host:
-  description: Same address as relevant configuration entry, needed to identify configuration entry.
-  type: string
-  required: true
-  default: None
-site:
-  description: Same site as relevant configuration entry, needed to identify configuration entry.
-  type: string
-  required: true
-  default: None
-block_client:
-  description: A list of Clients MAC Addresses that can be blocked from the network.
-  type: list
-  required: false
-  default: None
-detection_time:
-  description: How long since the last seen time before the device is marked away, specified in seconds.
-  type: integer
-  required: false
-  default: 300
-dont_track_clients:
-  description: enable to not allow device tracker to track clients.
-  type: boolean
-  required: false
-  default: false
-dont_track_devices:
-  description: enable to not allow device tracker to track devices.
-  type: boolean
-  required: false
-  default: false
-dont_track_wired_clients:
-  description: enable to not allow device tracker to track wired clients.
-  type: boolean
-  required: false
-  default: false
-ssid_filter:
-  description: Filter the SSIDs that tracking will occur on.
-  type: list
-  required: false
-  default: None
-{% endconfiguration %}
 
 ### Configuring Users
 
@@ -111,7 +59,7 @@ If Home Assistant and the UniFi controller are running on separate machines or V
 
 ### Block network access for clients
 
-Allow control of network access to clients configured in the `configuration.yaml` file by adding a list of the MAC addresses. Items in this list will have a Home Assistant switch created, using the UniFi Device name, allowing for blocking and unblocking.
+Allow control of network access to clients configured in the integration options by adding MAC addresses. Items in this list will have a Home Assistant switch created, using the UniFi Device name, allowing for blocking and unblocking.
 
 ### Control clients powered by POE
 
@@ -119,6 +67,12 @@ Entities appear automatically for each connected POE client. If no POE client de
 
 Note that POE control actually configures the network port of the switch which the client is connected to.
 
+## Sensor
+
+### Bandwidth sensor
+
+Get entities reporting receiving and transmitting bandwidth per network client.
+
 ## Debugging integration
 
 If you have problems with UniFi or the integration you can add debug prints to the log.

source/_integrations/velbus.markdown

@@ -57,6 +57,37 @@ port:
   type: string
 {% endconfiguration %}
 
+## Services
+
+- `velbus.sync clock`: Synchronize Velbus time to local clock.
+- `velbus.set_memo_text`: Show memo text on Velbus display modules.
+
+### Service `velbus.sync_clock`
+
+You can use the service `velbus.sync clock` to synchronize the clock of the Velbus modules to the clock of the machine running Home Assistant. This is the same as the 'sync clock' button at the VelbusLink software.
+
+### Service `velbus.set_memo_text`
+
+You can use the service `velbus.set_memo_text` to provide the memo text to be displayed at Velbus modules like VMBGPO(D) and VMBELO.
+
+| Service data attribute | Optional | Description                              |
+| ---------------------- | -------- | ---------------------------------------- |
+| `address`              | no       | The module address in decimal format, which is displayed at the device list at the integration page. |
+| `memo_text`            | yes      | Text to be displayed on module. When no memo text is supplied the memo text will be cleared. |
+
+Example:
+
+```yaml
+script:
+  trash_memo:
+    alias: Trash memo text
+    sequence:
+    - data:
+        address: 65
+        memo_text: "It's trash day"
+      service: velbus.set_memo_text
+```
+
 ## Example automation
 
 The Velbus integration allows you to link a Velbus button (i.e., a button of a [VMBGPOD](https://www.velbus.eu/products/view/?id=416302&lang=en) module) to a controllable entity of Home Assistant.

source/_integrations/vicare.markdown

@@ -51,11 +51,25 @@ heating_type:
   required: false
   type: string
   default: generic
+scan_interval:
+  description: The update frequency of this component in seconds. See [Viessmann API limits](#viessmann-api-limits)
+  default: 60
+  required: false
+  type: integer
 {% endconfiguration %}
 
 Two components will be created: `climate.vicare_heating` and `water_heater.vicare_water` (for domestic hot water).
 Unless you specify a `circuit` parameter, it will pick up the first heating circuit of your installation.
 
+## Viessmann API limits
+
+Recently Viessmann has introduced a rate limit on their REST API. If you exceed one of the limits below you will be banned for 24 hours:
+
+- Limit 1: 120 calls for a time window of 10 minutes
+- Limit 2: 1450 calls for a time window of 24 hours
+
+The default `scan_interval` of 60 seconds will work within these limits. Note however that any additional requests to the API, e.g., by setting the temperature via the integration but also by interacting with the ViCare app also counts into those limits. It is therefore advised to adjust the scan_interval to your usage scenario.
+
 ## Climate
 
 A note about the current temperature attribute: Viessmann devices with room temperature sensing will show the current room temperature via `current_temperature`. All other devices will show the current supply temperature of the heating circuit.
@@ -94,12 +108,13 @@ The `climate.vicare_heating` component has the following mapping of HVAC modes t
 
 #### Service `set_preset_mode`
 
-Sets the preset mode. Supported preset modes are *eco* and *comfort*. These are identical to the respective Viessmann programs and are only temporary. Please consult your heating device manual for more information.
+Sets the preset mode. Supported preset modes are *eco* and *comfort*. These are identical to the respective Viessmann programs and are only active temporarily for 8 hours.
+Eco mode reduces the target temperature by 3°C, whereas Comfort mode sets the target temperature to a configurable value. Please consult your heating device manual for more information.
 
 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
 | `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. To target all entities, use `all` keyword instead of entity_id.
-| `preset_mode` | no | New value of hold mode.
+| `preset_mode` | no | New value of preset mode.
 
 ## Water Heater
 

source/_integrations/vizio.markdown

@@ -41,11 +41,11 @@ Write down its IP address and port number. If you have trouble finding a device
 
 ## Pairing
 
-This integration requires an access token in order to communicate with TVs (speakers do not need an access token). An access token can be obtained by going through a pairing process, either manually, or through the HA frontend.
+This integration requires an access token in order to communicate with TVs (speakers do not need an access token). An access token can be obtained by going through a pairing process, either manually, or through the Home Assistant frontend.
 
-### Pair using the HA frontend
+### Pair using the Home Assistant frontend
 
- - **Using `configuration.yaml`:** If you have a `vizio` entry in `configuration.yaml` but don't provide an access token value in your configuration, after you initialize HomeAssistant, you will see a Vizio SmartCast device ready to be configured. When you open the configuration window, you will be guided through the pairing process. While HA will store the access token for the life of your `vizio` entity, it is a good idea to note the access token value displayed in the window and add it to your `configuration.yaml`. This will ensure that you will not have to go through the pairing process again in the future if you decide to rebuild your HA instance.
+ - **Using `configuration.yaml`:** If you have a `vizio` entry in `configuration.yaml` but don't provide an access token value in your configuration, after you initialize Home Assistant, you will see a Vizio SmartCast device ready to be configured. When you open the configuration window, you will be guided through the pairing process. While Home Assistant will store the access token for the life of your `vizio` entity, it is a good idea to note the access token value displayed in the window and add it to your `configuration.yaml`. This will ensure that you will not have to go through the pairing process again in the future if you decide to rebuild your Home Assistant instance.
 - **Using discovery or manual setup through the Integrations menu:** To initiate the pairing process, submit your initial configuration with an empty Access Token value.
 
 ### Pair manually using the CLI
@@ -120,7 +120,7 @@ name:
   type: string
   default: Vizio SmartCast
 access_token:
-  description: Authentication token you received in the last step of the pairing process. This token is only needed if your device is a TV, and you can opt not to provide it in your configuration and instead go through the pairing process via the HA frontend.
+  description: Authentication token you received in the last step of the pairing process. This token is only needed if your device is a TV, and you can opt not to provide it in your configuration and instead go through the pairing process via the Home Assistant frontend.
   required: false
   type: string
 device_class:
@@ -177,16 +177,10 @@ apps:
 
 ### Obtaining an app configuration
 
-If there is an app you want to be able to launch from Home Assistant that isn't detected by default, you will need to specify the app configuration in `configuration.yaml`. In order to determine the values to specify for each configuration parameter, launch the app you want to configure on your device, and run the following command (requires `pyvizio` to be installed locally):
+If there is an app you want to be able to launch from Home Assistant that isn't detected by default, you will need to specify the app configuration in `configuration.yaml`. This configuration can be obtained from the `app_id` state attribute when an unknown app is running on your device.
-
-```bash
-pyvizio --ip={IP:PORT} get-current-app-config
-```
-
-`pyvizio` will return the value of the three parameters (`APP_ID`, `NAME_SPACE`, `MESSAGE`) for the currently running app which you can then include in your configuration.
 
 ### Obtaining a list of valid apps to include or exclude
-To get the list of apps that can be excluded or included, run the following command (requires `pyvizio` to be installed locally):
+The list of apps that are provided by default is statically defined [here](https://github.com/vkorn/pyvizio/blob/master/pyvizio/const.py#L23). If you'd prefer a more concise list, you can either view the source list of a Vizio Smart TV in the Home Assistant frontend, or run the following command (requires `pyvizio` to be installed locally):
 
 ```bash
 pyvizio --ip=0 get-apps-list

source/_integrations/wled.markdown

@@ -45,13 +45,17 @@ entity.
 Only native supported features of a light in Home Assistant are supported
 (which includes effects).
 
-## Sensors	
+## Sensors
 
-This integration provides sensors for the following information from WLED:	
+This integration provides sensors for the following information from WLED:
 
-- Estimated current.	
+- Estimated current (in mA).
-- Uptime.	
+- Uptime (disabled by default)
-- Free memory.
+- Free memory (in bytes, disabled by default).
+- Wi-Fi Signal Strength (in %m disabled by default).
+- Wi-Fi Signal Strength (RSSI in dBm).
+- Wi-Fi Channel (disabled by default).
+- Wi-Fi BSSID (disabled by default).
 
 ## Switches
 
@@ -63,4 +67,20 @@ The integration will create a number of switches:
 
 ## Services
 
-This integration currently does not offer any additional services.
+Currently, the WLED integration provides one service for controlling effect.
+More services for other WLED features are expected to be added in the future.
+
+### Service `wled.effect`
+
+This service allows for controlling the WLED effect.
+
+| Service Data Attribute | Required | Description                                                                                                     |
+| ---------------------- | -------- | --------------------------------------------------------------------------------------------------------------- |
+| `entity_id`            | no       | A WLED entity ID, or list entity IDs, to apply the effect to. Use `entity_id: all` to target all WLED entities. |
+| `effect`               | no       | Name or ID of the WLED light effect.                                                                            |
+| `intensity`            | no       | Intensity of the effect.                                                                                        |
+| `speed`                | no       | Speed of the effect. Number between `0` (slow) and `255` (fast).                                                |
+| `reverse`              | no       | Reverse the effect. Either `true` to reverse or `false` otherwise.                                              |
+
+A list of all available effects (and the behavior of the intensity for each
+effect) [is documented in the WLED Wiki](https://github.com/Aircoookie/WLED/wiki/List-of-effects-and-palettes#effects).

source/_integrations/yeelight.markdown

@@ -81,7 +81,7 @@ devices:
           required: false
           type: string
         model:
-          description: "Yeelight model. Possible values are `mono1`, `color1`, `color2`, `strip1`, `bslamp1`, `ceiling1`, `ceiling2`, `ceiling3`, `ceiling4`. The setting is used to enable model specific features f.e. a particular color temperature range. Its also used to setup device, if its not available and discovery if disabled, during Home Assistant startup. If model is not specified, it will be guessed, by integration by looking at supported properties, reported by device."
+          description: "Yeelight model. Possible values are `mono1`, `color1`, `color2`, `strip1`, `bslamp1`, `ceiling1`, `ceiling2`, `ceiling3`, `ceiling4`, `ceiling13`. The setting is used to enable model specific features f.e. a particular color temperature range. Its also used to setup device, if its not available and discovery if disabled, during Home Assistant startup. If model is not specified, it will be guessed, by integration by looking at supported properties, reported by device."
           required: false
           type: string
 custom_effects:
@@ -151,6 +151,7 @@ This integration is tested to work with the following models. If you have a diff
 | `ceiling3` | YLXD05YL     | Yeelight Ceiling Light (Jiaoyue 480)             |
 | `ceiling4` | YLXD02YL     | Yeelight Ceiling Light (Jiaoyue 650)             |
 | `mono`     | YLTD03YL     | Yeelight Serene Eye-Friendly Desk Lamp           |
+| `ceiling13`     | YLXD01YL     | Yeelight LED Ceiling Light           |
 
 ## Services
 

source/_lovelace/entities.markdown

@@ -264,6 +264,65 @@ icon:
   default: "`mdi:link`"
 {% endconfiguration %}
 
+### Buttons
+
+{% configuration %}
+type:
+  required: true
+  description: buttons
+  type: string
+entities:
+  required: true
+  description: A list of entities to show. Each entry is either an entity ID or a map.
+  type: list
+  keys:
+    entity:
+      required: true
+      description: The entity to render.
+      type: string
+    icon:
+      required: false
+      description: Override the entity icon.
+      type: string
+    image:
+      required: false
+      description: Override the entity image.
+      type: string
+    name:
+      required: false
+      description: Label for the button
+      type: string
+{% endconfiguration %}
+
+### Attribute
+
+{% configuration %}
+type:
+  required: true
+  description: attribute
+  type: string
+entity:
+  required: true
+  description: Home Assistant entity ID.
+  type: string
+attribute:
+  required: true
+  description: Attribute to display from the entity.
+  type: string
+prefix:
+  required: false
+  description: Text before entity state.
+  type: string
+suffix:
+  required: false
+  description: Text after entity state.
+  type: string
+name:
+  required: false
+  description: Overwrites friendly name.
+  type: string
+{% endconfiguration %}
+
 ## Example
 
 Entity rows:

source/_lovelace/entity.markdown

@@ -0,0 +1,66 @@
+---
+title: "Entity Card"
+sidebar_label: Entity
+description: "The Entity card gives you a quick overview of your entity's state"
+---
+
+The Entity card gives you a quick overview of your entity's state.
+
+<p class='img'>
+  <img src='/images/lovelace/lovelace_entity_card.png' alt='Screenshot of the entity card'>
+  Screenshot of the entity card.
+</p>
+
+{% configuration %}
+type:
+  required: true
+  description: entity
+  type: string
+entity:
+  required: true
+  description: Home Assistant entity ID.
+  type: string
+name:
+  required: false
+  description: Name of Entity
+  type: string
+  default: Entity Name
+icon:
+  required: false
+  description: Overwrites icon.
+  type: string
+attribute:
+  required: false
+  description: An attribute associated with the `entity`
+  type: string
+unit:
+  required: false
+  description: Unit of Measurement given to data
+  type: string
+  default: "Unit Of Measurement given by entity"
+theme:
+  required: false
+  description: Set to any theme within `themes.yaml`
+  type: string
+footer:
+  required: false
+  description: Footer widget to render. See [footer documentation](/lovelace/header-footer/).
+  type: map
+{% endconfiguration %}
+
+## Example
+
+```yaml
+- type: entity
+  entity: cover.kitchen_window
+- type: entity
+  entity: light.bedroom
+  attribute: brightness
+  unit: '%'
+- type: entity
+  entity: vacuum.downstairs
+  name: Vacuum
+  icon: 'mdi:battery'
+  attribute: battery_level
+  unit: '%'
+```

source/_lovelace/map.markdown

@@ -42,6 +42,11 @@ dark_mode:
   description: Enable a dark theme for the map.
   type: boolean
   default: false
+hours_to_show:
+  required: false
+  description: Shows a path of previous locations. Hours to show as path on the map.
+  type: integer
+  default: 0
 {% endconfiguration %}
 
 <div class='note'>
@@ -74,3 +79,10 @@ geo_location_sources:
 entities:
   - zone.home
 ```
+
+```yaml
+type: map
+entities:
+  - device_tracker.demo_paulus
+hours_to_show: 48
+```

source/_lovelace/markdown.markdown

@@ -81,3 +81,18 @@ card:
 ```
 
 {% endraw %}
+
+
+A special template variable - `user` is set up for the `content` of the card. It contains the currently logged in user.
+
+For example:
+
+{% raw %}
+
+```yaml
+type: markdown
+content: |
+  Hello, {{user}}
+```
+
+{% endraw %}

source/_lovelace/picture-glance.markdown

@@ -90,6 +90,18 @@ entity:
   required: true
   description: Home Assistant entity ID.
   type: string
+attribute:
+  required: false
+  description: Attribute of the entity to display instead of the state
+  type: string
+prefix:
+  required: false
+  description: Prefix to display before the attribute's value
+  type: string
+suffix:
+  required: false
+  description: Suffix to display after the attribute's value
+  type: string
 icon:
   required: false
   description: Overwrites default icon.

source/_posts/2016-01-17-extended-support-for-diy-solutions.markdown

@@ -13,7 +13,7 @@ First release of 2016 and we are on 🔥! The [main repository][github-ha] has p
 [github-ha]: https://github.com/home-assistant/home-assistant/
 [release-pr]: https://github.com/home-assistant/home-assistant/pull/883#partial-users-participants
 
-<img src='https://brands.home-assistant.io/mysensors/logo.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/raspberry-pi.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='50' /><img src='/images/supported_brands/yr.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/telldus_tellstick.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/free_mobile.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/netatmo.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/alarmdotcom.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/proliphix.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' />
+<img src='https://brands.home-assistant.io/mysensors/logo.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/raspberry-pi.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='50' /><img src='/images/supported_brands/yr.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/telldus_tellstick.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/free_mobile.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/netatmo.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/proliphix.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' />
 
  - [MySensors] revamped and switch support added ([@MartinHjelmare][@MartinHjelmare])
  - Full refactor of RPi GPIO. Now includes [binary sensor][rpi-bs] and [switch][rpi-s] ([@sfam])
@@ -53,7 +53,6 @@ First release of 2016 and we are on 🔥! The [main repository][github-ha] has p
 [Cast]: /integrations/cast
 [Universal media player]: /integrations/universal
 [Netatmo]: /integrations/netatmo#sensor
-[Alarm.com]: /integrations/alarmdotcom
 [Proliphix]: /integrations/proliphix/
 [rpi-bs]: /integrations/rpi_gpio#binary-sensor
 [rpi-s]: /integrations/rpi_gpio#switch

source/_posts/2017-04-22-ikea-tradfri--spotify.markdown

@@ -132,7 +132,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - Bump pywemo version. ([@pavoni] - [#7004])
 - Fix Synology camera content type ([@balloob] - [#7010]) ([camera.synology docs])
 - Fix two more instances of JSON parsing synology ([@balloob] - [#7014])
-- Bump pyalarmdotcom to support new version of aiohttp ([@Xorso] - [#7021]) ([alarm_control_panel.alarmdotcom docs])
+- Bump pyalarmdotcom to support new version of aiohttp ([@Xorso] - [#7021])
 - Fix US states check (fixes #7015) ([@fabaff] - [#7017])
 - Remove deprecated remote classes ([@balloob] - [#7011]) (breaking change)
 - Replace 'vendor_id' with 'arch' (fixes #7003) ([@fabaff] - [#7023])
@@ -417,7 +417,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
 [@turbokongen]: https://github.com/turbokongen
 [@viswa-swami]: https://github.com/viswa-swami
 
-[alarm_control_panel.alarmdotcom docs]: /integrations/alarmdotcom
 [arduino docs]: /integrations/arduino/
 [automation docs]: /integrations/automation/
 [binary_sensor.ping docs]: /integrations/ping#binary-sensor

source/_posts/2017-09-09-release-53.markdown

@@ -62,7 +62,7 @@ This release ships a new KNX implementation thanks to @Julius2342. It will insta
 - Bayesian Binary Sensor ([@jlmcgehee21] - [#8810]) ([binary_sensor.bayesian docs]) (new-platform)
 - Add Tank Utility sensor ([@krismolendyke] - [#9132]) ([sensor.tank_utility docs]) (new-platform)
 - Tesla platform ([@zabuldon] - [#9211]) ([tesla docs]) ([binary_sensor.tesla docs]) ([climate.tesla docs]) ([device_tracker.tesla docs]) ([lock.tesla docs]) ([sensor.tesla docs]) (new-platform)
-- mopar sensor ([@happyleavesaoc] - [#9136]) ([sensor.mopar docs]) (new-platform)
+- mopar sensor ([@happyleavesaoc] - [#9136]) (new-platform)
 - Add Geofency device tracker ([@gunnarhelgason] - [#9106]) ([device_tracker.geofency docs]) (new-platform)
 - Added DWD WarnApp Sensor ([@runningman84] - [#8657]) ([sensor.dwdwarnapp docs]) (new-platform)
 - Add input_text component ([@BioSehnsucht] - [#9112]) ([input_text docs]) (new-platform)
@@ -147,7 +147,7 @@ frontend:
 - Allow panels with external URL ([@andrey-git] - [#9214])
 - Use ZCL mandatory attribute to determine ZHA light capabilities ([@jkl1337] - [#9232]) ([light.zha docs])
 - A bugfix for pushbullet ([@danielhiversen] - [#9237]) ([notify.pushbullet docs])
-- mopar sensor ([@happyleavesaoc] - [#9136]) ([sensor.mopar docs]) (new-platform)
+- mopar sensor ([@happyleavesaoc] - [#9136]) (new-platform)
 - Upgrade discord.py to 0.16.11 ([@fabaff] - [#9239]) ([notify.discord docs])
 - Skip automatic events older than latest data ([@armills] - [#9230]) ([device_tracker.automatic docs])
 - title and message was swapped in pushbullet ([@danielhiversen] - [#9241]) ([notify.pushbullet docs])
@@ -419,7 +419,6 @@ frontend:
 [sensor.dwdwarnapp docs]: /integrations/dwd_weather_warnings/
 [sensor.fitbit docs]: /integrations/fitbit
 [sensor.homematic docs]: /integrations/homematic
-[sensor.mopar docs]: /integrations/mopar
 [sensor.radarr docs]: /integrations/radarr
 [sensor.season docs]: /integrations/season
 [sensor.shodan docs]: /integrations/shodan

source/_posts/2017-09-23-release-54.markdown

@@ -60,7 +60,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - Allow multiple observations of same entity ([@jlmcgehee21] - [#9391]) ([binary_sensor.bayesian docs])
 - Break up Alexa per functionality ([@balloob] - [#9400]) ([alexa docs])
 - Upgrade psutil to 5.3.1 ([@fabaff] - [#9403]) ([sensor.systemmonitor docs])
-- fix mopar sensor ([@happyleavesaoc] - [#9389]) ([sensor.mopar docs])
+- fix mopar sensor ([@happyleavesaoc] - [#9389])
 - Support specifying no Apple TVs ([@postlund] - [#9394]) ([apple_tv docs])
 - Update netdisco to 1.2.0 ([@balloob] - [#9408])
 - components/xiaomi: Add initial discovery using NetDisco. ([@pfalcon] - [#9283])
@@ -329,7 +329,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
 [sensor.fitbit docs]: /integrations/fitbit
 [sensor.homematic docs]: /integrations/homematic
 [sensor.knx docs]: /integrations/sensor.knx/
-[sensor.mopar docs]: /integrations/mopar
 [sensor.onewire docs]: /integrations/onewire
 [sensor.swiss_public_transport docs]: /integrations/swiss_public_transport
 [sensor.systemmonitor docs]: /integrations/systemmonitor

source/_posts/2018-01-14-release-61.markdown

@@ -56,7 +56,7 @@ broadlink.send_packet_192_168_0_107 -> switch.broadlink_send_packet_192_168_0_10
 ## Release 0.61.1 - January 16
 
 - Fix zha color probe ([@rcloran] - [#11670]) ([zha docs]) ([light.zha docs])
-- Move several local services to their right domain ([@amelchio] - [#11677]) ([calendar.todoist docs]) ([media_player.snapcast docs]) ([media_player.soundtouch docs]) ([sensor.mopar docs]) ([switch.broadlink docs]) ([switch.scsgate docs]) (breaking change)
+- Move several local services to their right domain ([@amelchio] - [#11677]) ([calendar.todoist docs]) ([media_player.snapcast docs]) ([media_player.soundtouch docs]) ([switch.broadlink docs]) ([switch.scsgate docs]) (breaking change)
 - Rfxtrx fix ([@danielhiversen] - [#11678]) ([rfxtrx docs]) ([binary_sensor.rfxtrx docs])
 - History order bugfix and opt-in option ([@rwa] - [#11686]) ([history docs])
 - Fix purge with MariaDB / MySQL ([@tinloaf] - [#11713])
@@ -155,7 +155,7 @@ Note however, that this feature was replaced by a new ignore_string config optio
    broadlink.learn_command_192_168_0_107 -> switch.broadlink_learn_command_192_168_0_107
    broadlink.send_packet_192_168_0_107 -> switch.broadlink_send_packet_192_168_0_107
    ```
-   ([@amelchio] - [#11677]) ([calendar.todoist docs]) ([media_player.snapcast docs]) ([media_player.soundtouch docs]) ([sensor.mopar docs]) ([switch.broadlink docs]) ([switch.scsgate docs]) (breaking change)
+   ([@amelchio] - [#11677]) ([calendar.todoist docs]) ([media_player.snapcast docs]) ([media_player.soundtouch docs]) ([switch.broadlink docs]) ([switch.scsgate docs]) (breaking change)
 
 
 ## All changes
@@ -789,7 +789,6 @@ Note however, that this feature was replaced by a new ignore_string config optio
 [media_player.snapcast docs]: /integrations/snapcast
 [media_player.soundtouch docs]: /integrations/soundtouch
 [rfxtrx docs]: /integrations/rfxtrx/
-[sensor.mopar docs]: /integrations/mopar
 [switch.broadlink docs]: /integrations/broadlink#switch
 [switch.scsgate docs]: /integrations/scsgate#switch
 [zha docs]: /integrations/zha/

source/_posts/2018-03-09-release-65.markdown

@@ -318,7 +318,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - IMAP sensor async/await conversion ([@amelchio] - [#12988]) ([sensor.imap docs])
 - Refactor Google Assistant ([@balloob] - [#12959]) ([google_assistant docs]) ([light docs]) (breaking change)
 - Bump pyEmby version to support aiohttp => 3 ([@mezz64] - [#12986]) ([media_player.emby docs])
-- Update pyalarmdotcom version ([@koolsb] - [#12987]) ([alarm_control_panel.alarmdotcom docs])
+- Update pyalarmdotcom version ([@koolsb] - [#12987])
 - Show the error message when Zabbix fails to log in ([@cyberjacob] - [#12985]) ([zabbix docs])
 - Script/gen_requirements: Ignore package families ([@cdce8p] - [#12963])
 - Fix Sonos group discovery ([@amelchio] - [#12970]) ([media_player.sonos docs])
@@ -540,7 +540,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
 [@teharris1]: https://github.com/teharris1
 [@thejta]: https://github.com/thejta
 [@turbokongen]: https://github.com/turbokongen
-[alarm_control_panel.alarmdotcom docs]: /integrations/alarmdotcom
 [alarm_control_panel.concord232 docs]: /integrations/concord232#alarm-control-panel
 [alarm_control_panel.egardia docs]: /integrations/egardia
 [api docs]: /integrations/api/

source/_posts/2018-05-11-release-69.markdown

@@ -172,7 +172,7 @@ rainmachine:
 - Sensor device classes ([@cdce8p] - [#14282]) ([sensor docs]) (breaking change)
 - Matrix Chatbot ([@tinloaf] - [#13355]) ([matrix docs]) ([notify docs]) (breaking change) (new-platform)
 - deCONZ add new device without restart ([@Kane610] - [#14221]) ([deconz docs]) ([binary_sensor.deconz docs]) ([light.deconz docs]) ([sensor.deconz docs])
-- Add alarmdotcom sensor status ([@jnewland] - [#14254]) ([alarm_control_panel.alarmdotcom docs])
+- Add alarmdotcom sensor status ([@jnewland] - [#14254])
 - Add domain to labels and count state changes to Prometheus ([@jnewland] - [#14253]) ([prometheus docs])
 - Add support for max_volume ([@relvacode] - [#13822]) ([media_player.onkyo docs])
 - Refactor ImageProcessingFaceEntity ([@robmarkcole] - [#14296]) ([image_processing docs]) ([image_processing.dlib_face_detect docs]) ([image_processing.dlib_face_identify docs]) ([image_processing.microsoft_face_detect docs]) ([image_processing.microsoft_face_identify docs])
@@ -372,7 +372,6 @@ rainmachine:
 [@thelittlefireman]: https://github.com/thelittlefireman
 [@tinloaf]: https://github.com/tinloaf
 [abode docs]: /integrations/abode/
-[alarm_control_panel.alarmdotcom docs]: /integrations/alarmdotcom
 [auth docs]: /integrations/auth/
 [binary_sensor docs]: /integrations/binary_sensor/
 [binary_sensor.deconz docs]: /integrations/deconz#binary-sensor

source/_posts/2018-07-16-release-73-2.markdown

@@ -14,7 +14,6 @@ A man in the middle attack is when an attacker is able to inject itself between
 
 After research, the following integrations have been impacted. Although the odds are extremely small, we still suggest that if you use any of these integrations, to create new API keys or change your password.
 
-- [alarm_control_panel.alarmdotcom](/integrations/alarmdotcom)
 - [climate.sensibo](/integrations/sensibo)
 - [cloud](/integrations/cloud/) (only short lived tokens impacted)
 - [device_tracker.automatic](/integrations/automatic)

source/_posts/2019-01-23-release-86.markdown

@@ -279,7 +279,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - Lowercase code format ([@balloob] - [#20077]) ([alarm_control_panel docs]) (breaking change)
 - fix logic error in dubln bus ([@ttroy50] - [#20075]) ([sensor.dublin_bus_transport docs])
 - Bump abode to 0.15.0 ([@shred86] - [#20064]) ([abode docs])
-- Change return text code for alarm control panels ([@arsaboo] - [#20055]) ([alarm_control_panel.alarmdotcom docs])
+- Change return text code for alarm control panels ([@arsaboo] - [#20055])
 - Adjust OpenUV integration for upcoming API limit changes ([@bachya] - [#19949]) ([openuv docs]) (breaking change)
 - Fix ihc issues caused by update to defusedxml ([@mopolus] - [#20091]) ([ihc docs])
 - Move ESPHome Source Files ([@OttoWinter] - [#20092]) ([esphome docs])
@@ -596,7 +596,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
 [abode docs]: /integrations/abode/
 [ads docs]: /integrations/ads/
 [alarm_control_panel docs]: /integrations/alarm_control_panel/
-[alarm_control_panel.alarmdotcom docs]: /integrations/alarmdotcom
 [alarm_control_panel.arlo docs]: /integrations/arlo
 [alarm_control_panel.elkm1 docs]: /integrations/elkm1
 [alarm_control_panel.homekit_controller docs]: /integrations/homekit_controller

source/_posts/2019-03-20-release-90.markdown

@@ -227,7 +227,7 @@ Users will need to change `- platform: firetv` to `- platform: androidtv` in the
 - ZHA fixes ([@dmulcahey] - [#21592]) ([zha docs])
 - Update pyhomematic ([@danielperna84] - [#21600]) ([homematic docs])
 - Add parameter hold_secs for Harmony remote send command ([@ehendrix23] - [#19650]) ([remote docs]) ([remote.harmony docs])
-- Upgrade motorparts to 1.1.0 ([@rohankapoorcom] - [#21602]) ([sensor.mopar docs])
+- Upgrade motorparts to 1.1.0 ([@rohankapoorcom] - [#21602])
 - Further Yale ZWave lock device mapping cleanup ([@mw-white] - [#21128]) ([zwave docs])
 - Added support for multiple Netatmo thermostats/valves ([@shanbs] - [#19407]) ([netatmo docs]) ([climate.netatmo docs]) (breaking change)
 - Add the velbus sync clock service ([@Cereal2nd] - [#21308]) ([velbus docs])
@@ -792,7 +792,6 @@ Users will need to change `- platform: firetv` to `- platform: androidtv` in the
 [sensor.dsmr docs]: /integrations/dsmr
 [sensor.flunearyou docs]: /integrations/flunearyou
 [sensor.loopenergy docs]: /integrations/loopenergy
-[sensor.mopar docs]: /integrations/mopar
 [sensor.mqtt_room docs]: /integrations/mqtt_room
 [sensor.netdata docs]: /integrations/netdata
 [sensor.nmbs docs]: /integrations/nmbs

source/_posts/2019-04-03-release-91.markdown

@@ -105,7 +105,7 @@ If you run hass.io on an Intel NUC and haven't seen it yet, check out the VS Cod
 
 ## Release 0.91.2 - April 8
 
-- Correctly load Mopar's config ([@rohankapoorcom] - [#22771]) ([mopar docs])
+- Correctly load Mopar's config ([@rohankapoorcom] - [#22771])
 - Fix konnected unique_id computation for switches ([@heythisisnate] - [#22777]) ([konnected docs]) (breaking change)
 - make the custom polling actually request state ([@dmulcahey] - [#22778]) ([zha docs])
 - ZHA Light debug logging. ([@Adminiuga] - [#22776]) ([zha docs])
@@ -153,7 +153,6 @@ If you run hass.io on an Intel NUC and haven't seen it yet, check out the VS Cod
 [hassio docs]: /integrations/hassio/
 [konnected docs]: /integrations/konnected/
 [mobile_app docs]: /integrations/mobile_app/
-[mopar docs]: /integrations/mopar/
 [tado docs]: /integrations/tado/
 [yeelight docs]: /integrations/yeelight/
 [zha docs]: /integrations/zha/
@@ -212,7 +211,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - __Dark Sky__ - Dark Sky provides hourly forecasts for various monitored conditions. This change creates new sensors for each hourly forecasted condition with suffix `_<hour>h` while adding the suffix `_<day>d` to the daily forecasted conditions. For example, now a `sensor.dark_sky_summary_<day>d` and `sensor.dark_sky_summary_<hour>h` will be created if the forecast and hourly_forecast parameters are populated. ([@rtclauss] - [#21820]) ([darksky docs])
 - __Konnected__ - This will change the internal unique_id for Konnected switches (i.e., siren, buzzer, generic switch). Users will need to manually remove the orphaned switch entities from the entity registry after updating and re-configure any changes stored in the entity registry (i.e., name and entity_id), as their unique IDs will change. ([@heythisisnate] - [#22389]) ([konnected docs])
 
-- __Mopar__ - The mopar sensor platform has been broken up into a base component with sensor, switch, and lock platforms. The sensor.mopar_remote_command service has been removed since the functionality has been folded into the new platforms and the new mopar.sound_horn service. Please view the documentation to see the new setup instructions. ([@rohankapoorcom] - [#21526]) ([mopar docs])
+- __Mopar__ - The mopar sensor platform has been broken up into a base component with sensor, switch, and lock platforms. The sensor.mopar_remote_command service has been removed since the functionality has been folded into the new platforms and the new mopar.sound_horn service. Please view the documentation to see the new setup instructions. ([@rohankapoorcom] - [#21526])
 
 ## Beta Fixes
 
@@ -415,7 +414,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - Move HKDevice into connection ([@Jc2k] - [#22430]) ([homekit_controller docs])
 - Incoming SMS handling for netgear_lte ([@amelchio] - [#22402]) ([netgear_lte docs])
 - Entur upgrade to v0.2.0: async polling, number of departures, omit non boarding departures ([@hfurubotten] - [#22001]) ([entur_public_transport docs])
-- Mopar split ([@rohankapoorcom] - [#21526]) ([mopar docs]) (breaking change)
+- Mopar split ([@rohankapoorcom] - [#21526]) (breaking change)
 - Fix too-abrubt SimpliSafe data refresh termination on error ([@bachya] - [#22466]) ([simplisafe docs])
 - Great migration notify ([@robbiet480] - [#22406])
 - Print error instead of warning for custom platforms in legacy format ([@balloob] - [#22486])
@@ -795,7 +794,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
 [microsoft docs]: /integrations/microsoft/
 [mold_indicator docs]: /integrations/mold_indicator/
 [moon docs]: /integrations/moon/
-[mopar docs]: /integrations/mopar/
 [mqtt docs]: /integrations/mqtt/
 [nanoleaf docs]: /integrations/nanoleaf/
 [ness_alarm docs]: /integrations/ness_alarm/

source/_posts/2019-10-30-release-101.markdown

@@ -574,7 +574,7 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
 - Move imports in nest component ([@Quentame] - [#27778]) ([nest docs])
 - moved imports to top level ([@Bouni] - [#27781]) ([airvisual docs])
 - Move imports in netgear component ([@Quentame] - [#27776]) ([netgear docs])
-- moved imports to top level ([@Bouni] - [#27784]) ([alarmdotcom docs])
+- moved imports to top level ([@Bouni] - [#27784])
 - Generate ADB key for Android TV integration ([@JeffLIrion] - [#27344]) ([androidtv docs])
 - moved imports to top level ([@Bouni] - [#27782]) ([aladdin_connect docs])
 - Move imports in android_ip_webcam component ([@Bouni] - [#27797]) ([android_ip_webcam docs])
@@ -709,7 +709,7 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
 - Move imports in eliqonline component ([@djpremier] - [#27980]) ([eliqonline docs])
 - Move imports in frontend component ([@djpremier] - [#27988]) ([frontend docs])
 - Move imports in message_bird component ([@djpremier] - [#28022]) ([message_bird docs])
-- Move imports in mopar component ([@djpremier] - [#28028]) ([mopar docs])
+- Move imports in mopar component ([@djpremier] - [#28028])
 - Move imports in mvglive component ([@djpremier] - [#28031]) ([mvglive docs])
 - Move imports in mpd component ([@djpremier] - [#28030]) ([mpd docs])
 - Move imports in namecheapdns component ([@djpremier] - [#28034]) ([namecheapdns docs])
@@ -1527,7 +1527,6 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
 [aladdin_connect docs]: /integrations/aladdin_connect/
 [alarm_control_panel docs]: /integrations/alarm_control_panel/
 [alarmdecoder docs]: /integrations/alarmdecoder/
-[alarmdotcom docs]: /integrations/alarmdotcom/
 [alexa docs]: /integrations/alexa/
 [alpha_vantage docs]: /integrations/alpha_vantage/
 [amazon_polly docs]: /integrations/amazon_polly/
@@ -1735,7 +1734,6 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
 [miflora docs]: /integrations/miflora/
 [mitemp_bt docs]: /integrations/mitemp_bt/
 [mobile_app docs]: /integrations/mobile_app/
-[mopar docs]: /integrations/mopar/
 [mpd docs]: /integrations/mpd/
 [mqtt docs]: /integrations/mqtt/
 [msteams docs]: /integrations/msteams/

source/_posts/2020-02-05-release-105.markdown

@@ -755,7 +755,7 @@ Hats over your heart for these shuttered integrations. Pour one out for:
 - Removes Cisco Spark integration ([@frenck] - [#30738]) (breaking change)
 - Fix translation from HA playlist to UPnP playlistItem ([@StevenLooman] - [#30743]) ([dlna_dmr docs])
 - Fix 'NewIPAddress' error in component fritz ([@basdelfos] - [#30210]) ([fritz docs]) ([fritzbox_netmonitor docs]) (breaking change)
-- Fix small typo in alarmdotcom component ([@akinomeroglu] - [#30758]) ([alarmdotcom docs])
+- Fix small typo in alarmdotcom component ([@akinomeroglu] - [#30758])
 - Fix supported_features in MQTT fan ([@springstan] - [#28680]) ([mqtt docs]) (breaking change)
 - Add support for the voltage sensor on the greeneye GEM ([@garbled1] - [#30484]) ([greeneye_monitor docs])
 - Add Safe Mode ([@balloob] - [#30723]) ([frontend docs]) ([http docs]) ([safe_mode docs]) (breaking change) (new-integration)
@@ -1413,7 +1413,6 @@ Hats over your heart for these shuttered integrations. Pour one out for:
 [adguard docs]: /integrations/adguard/
 [airly docs]: /integrations/airly/
 [alarmdecoder docs]: /integrations/alarmdecoder/
-[alarmdotcom docs]: /integrations/alarmdotcom/
 [alexa docs]: /integrations/alexa/
 [almond docs]: /integrations/almond/
 [amcrest docs]: /integrations/amcrest/

source/_redirects

@@ -83,7 +83,6 @@
 /components/air_quality.opensensemap /integrations/opensensemap
 /components/alarm_control_panel.abode /integrations/abode
 /components/alarm_control_panel.alarmdecoder /integrations/alarmdecoder#alarm-control-panel
-/components/alarm_control_panel.alarmdotcom /integrations/alarmdotcom
 /components/alarm_control_panel.arlo /integrations/arlo
 /components/alarm_control_panel.blink /integrations/blink
 /components/alarm_control_panel.canary /integrations/canary
@@ -783,7 +782,6 @@
 /components/sensor.modem_callerid /integrations/modem_callerid
 /components/sensor.mold_indicator /integrations/mold_indicator
 /components/sensor.moon /integrations/moon
-/components/sensor.mopar /integrations/mopar
 /components/sensor.mqtt_room /integrations/mqtt_room
 /components/sensor.mvglive /integrations/mvglive
 /components/sensor.mychevy /integrations/mychevy
@@ -1099,7 +1097,6 @@
 /components/alarm_control_panel.ifttt /integrations/alarm_control_panel.ifttt
 /components/alarm_control_panel.mqtt /integrations/alarm_control_panel.mqtt
 /components/alarmdecoder /integrations/alarmdecoder
-/components/alarmdotcom /integrations/alarmdotcom
 /components/alert /integrations/alert
 /components/alexa /integrations/alexa
 /components/alexa.flash_briefings /integrations/alexa.flash_briefings
@@ -1580,7 +1577,6 @@
 /components/mold_indicator /integrations/mold_indicator
 /components/monoprice /integrations/monoprice
 /components/moon /integrations/moon
-/components/mopar /integrations/mopar
 /components/mpchc /integrations/mpchc
 /components/mpd /integrations/mpd
 /components/mqtt /integrations/mqtt

source/lovelace/header-footer.markdown

@@ -75,4 +75,41 @@ entities:
       required: false
       description: Override the entity image.
       type: string
+    name:
+      required: false
+      description: Label for the button
+      type: string
+{% endconfiguration %}
+
+## Graph header & footer
+
+Widget to show an entity in the sensor domain as a graph in the header or footer.
+
+<p class='img'><img src='/images/lovelace/header-footer/graph.png' alt="Screenshot of an entities card with a graph footer.">
+Screenshot of an entities card with a graph footer.
+</p>
+
+```yaml
+footer:
+  type: graph
+  entity: sensor.outside_temperature
+  hours_to_show: 24
+  detail: 1
+```
+
+{% configuration header-footer %}
+entity:
+  required: true
+  description: Entity id of `sensor` domain
+  type: string
+detail:
+  required: false
+  description: Detail of the graph `1` or `2`, `1` equals one point/hour, `2` equals six points/hour
+  type: integer
+  default: 1
+hours_to_show:
+  required: false
+  description: Hours to show in graph
+  type: integer
+  default: 24
 {% endconfiguration %}