Merge branch 'rc' into current

2025-07-09 18:36:51 +00:00 · 2019-12-11 18:48:35 +01:00 · 2019-12-11 18:48:35 +01:00 · 23f9af6fa3
commit 23f9af6fa3
parent e3124ebcc0 92c761b770
87 changed files with 3053 additions and 329 deletions
--- a/.github/workflows/markdown.yml
+++ b/.github/workflows/markdown.yml
@ -4,7 +4,8 @@ on: [push, pull_request]

 jobs:
  remark:
-    runs-on: ubuntu-latest
+    #runs-on: ubuntu-latest
+    runs-on: self-hosted
    steps:
      - name: Checking out files from GitHub
        uses: actions/checkout@v1
--- a/_config.yml
+++ b/_config.yml
@ -100,9 +100,9 @@ social:

 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 102
-current_patch_version: 3
-date_released: 2019-11-29
+current_minor_version: 103
+current_patch_version: 0
+date_released: 2019-12-11

 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
--- a/sass/base/_typography.scss
+++ b/sass/base/_typography.scss
@ -10,9 +10,15 @@ $header-subtitle-font-family: $heading-font-family !default;
 .heading {
  font-family: $heading-font-family;
 }
-.sans { font-family: $sans; }
-.serif { font-family: $serif; }
-.mono { font-family: $mono; }
+.sans {
+  font-family: $sans;
+}
+.serif {
+  font-family: $serif;
+}
+.mono {
+  font-family: $mono;
+}

 body > header h1 {
  font-size: 2.2em;
@ -37,75 +43,172 @@ h1 {
 }

@media only screen and (min-width: 992px) {
-  body { font-size: 1.15em; }
-  h1 { font-size: 2.6em; line-height: 1.2em; }
+  body {
+    font-size: 1.15em;
+  }
+  h1 {
+    font-size: 2.6em;
+    line-height: 1.2em;
+  }
 }

-#{headings()}{
+#{headings()} {
  @extend .heading;
  text-rendering: optimizelegibility;
  margin-bottom: 1em;
  font-weight: bold;
 }
-h2, section h1 {
+h2,
+section h1 {
  font-size: 1.5em;
 }
-h3, section h2, section section h1 {
+h3,
+section h2,
+section section h1 {
  font-size: 1.3em;
 }
-h4, section h3, section section h2, section section section h1 {
+h4,
+section h3,
+section section h2,
+section section section h1 {
  font-size: 1em;
 }
-h5, section h4, section section h3 {
-  font-size: .9em;
+h5,
+section h4,
+section section h3 {
+  font-size: 0.9em;
 }
-h6, section h5, section section h4, section section section h3 {
-  font-size: .8em;
+h6,
+section h5,
+section section h4,
+section section section h3 {
+  font-size: 0.8em;
 }

-p, article blockquote, ul, ol { margin-bottom: 1.5em; }
-
-ul { list-style-type: disc;
-  ul { list-style-type: circle; margin-bottom: 0px;
-    ul { list-style-type: square; margin-bottom: 0px; }}}
-
-ol { list-style-type: decimal;
-  ol { list-style-type: lower-alpha; margin-bottom: 0px;
-    ol { list-style-type: lower-roman; margin-bottom: 0px; }}}
-
-ul, ol { &, ul, ol { margin-left: 1.3em; }}
-ul, ol { ul, ol { margin-bottom: 0em; }}
-
-strong { font-weight: bold; }
-
-em { font-style: italic; }
-
-sup, sub { font-size: 0.75em; position: relative;  display: inline-block; padding: 0 .2em; line-height: .8em;}
-sup { top: -.5em; }
-sub { bottom: -.5em; }
-
-a[rev='footnote']{ font-size: .75em; padding: 0 .3em; line-height: 1; }
-
-q { font-style: italic;
-  &:before { content: "\201C"; }
-  &:after { content: "\201D"; }
+p,
+article blockquote,
+ul,
+ol {
+  margin-bottom: 1.5em;
 }

-em, dfn { font-style: italic; }
+ul {
+  list-style-type: disc;
+  ul {
+    list-style-type: circle;
+    margin-bottom: 0px;
+    ul {
+      list-style-type: square;
+      margin-bottom: 0px;
+    }
+  }
+}

-strong, dfn { font-weight: bold; }
+ol {
+  list-style-type: decimal;
+  ol {
+    list-style-type: lower-alpha;
+    margin-bottom: 0px;
+    ol {
+      list-style-type: lower-roman;
+      margin-bottom: 0px;
+    }
+  }
+}

-del, s { text-decoration: line-through; }
+ul,
+ol {
+  &,
+  ul,
+  ol {
+    margin-left: 1.3em;
+  }
+}
+ul,
+ol {
+  ul,
+  ol {
+    margin-bottom: 0em;
+  }
+}

-abbr, acronym { border-bottom: 1px dotted; cursor: help; }
+strong {
+  font-weight: bold;
+}

-pre, code, tt { @extend .mono; }
+em {
+  font-style: italic;
+}

-hr { margin-bottom: 0.2em; }
+sup,
+sub {
+  font-size: 0.75em;
+  position: relative;
+  display: inline-block;
+  padding: 0 0.2em;
+  line-height: 0.8em;
+}
+sup {
+  top: -0.5em;
+}
+sub {
+  bottom: -0.5em;
+}

-small { font-size: .8em; }
+a[rev="footnote"] {
+  font-size: 0.75em;
+  padding: 0 0.3em;
+  line-height: 1;
+}

-big { font-size: 1.2em; }
+q {
+  font-style: italic;
+  &:before {
+    content: '"';
+  }
+  &:after {
+    content: '"';
+  }
+}
+
+em,
+dfn {
+  font-style: italic;
+}
+
+strong,
+dfn {
+  font-weight: bold;
+}
+
+del,
+s {
+  text-decoration: line-through;
+}
+
+abbr,
+acronym {
+  border-bottom: 1px dotted;
+  cursor: help;
+}
+
+pre,
+code,
+tt {
+  @extend .mono;
+}
+
+hr {
+  margin-bottom: 0.2em;
+}
+
+small {
+  font-size: 0.8em;
+}
+
+big {
+  font-size: 1.2em;
+}

 article blockquote {
  $bq-margin: 1.2em;
@ -114,11 +217,21 @@ article blockquote {
  font-size: 1.2em;
  line-height: 1.5em;
  padding-left: 1em;
-  border-left: 4px solid rgba($text-color-light, .5);
+  border-left: 4px solid rgba($text-color-light, 0.5);
  cite {
    font-style: italic;
-    a { color: $text-color-light !important; word-wrap: break-word; }
-    &:before { content: '\2014'; padding:{right: .3em; left: .3em;} color: $text-color-light; }
+    a {
+      color: $text-color-light !important;
+      word-wrap: break-word;
+    }
+    &:before {
+      content: "\2014";
+      padding: {
+        right: 0.3em;
+        left: 0.3em;
+      }
+      color: $text-color-light;
+    }
  }
  @media only screen and (min-width: 992px) {
    padding-left: 1.5em;
@ -138,7 +251,7 @@ article blockquote {
  /* Pull out to the right, modular scale based margins. */
  float: right;
  width: 45%;
-  margin: .5em 0 1em 1.5em;
+  margin: 0.5em 0 1em 1.5em;

  /* Baseline correction */
  position: relative;
@ -150,7 +263,7 @@ article blockquote {
 .pullquote-left:before {
  /* Make left pullquotes align properly. */
  float: left;
-  margin: .5em 1.5em 1em 0;
+  margin: 0.5em 1.5em 1em 0;
 }

 /* @extend this to force long lines of continuous text to wrap */
@ -161,4 +274,3 @@ article blockquote {
  white-space: pre-wrap;
  word-wrap: break-word;
 }
-
--- a/sass/inuitcss/base/_quotes.scss
+++ b/sass/inuitcss/base/_quotes.scss
@ -5,12 +5,11 @@
 /**
 * If English quotes are set in `_vars.scss`, define them here.
 */
-@if $english-quotes == true{
-    $open-quote:    \201C;
-    $close-quote:   \201D;
+@if $english-quotes == true {
+  $open-quote: '"';
+  $close-quote: '"';
 }

-
 /**
 * Big up @boblet: html5doctor.com/blockquote-q-cite
 */
@ -18,55 +17,52 @@
 /**
 * Inline quotes.
 */
-q{
-    quotes:"\2018" "\2019" "#{$open-quote}" "#{$close-quote}";
+q {
+  quotes: "\2018""\2019""#{$open-quote}""#{$close-quote}";

-    &:before{
-        content:"\2018";
-        content:open-quote;
-    }
-    &:after{
-        content:"\2019";
-        content:close-quote;
-    }
+  &:before {
+    content: "\2018";
+    content: open-quote;
+  }
+  &:after {
+    content: "\2019";
+    content: close-quote;
+  }

-    q:before{
-        content:"\201C";
-        content:open-quote;
-    }
-    q:after{
-        content:"\201D";
-        content:close-quote;
-    }
+  q:before {
+    content: '"';
+  }
+  q:after {
+    content: '"';
+  }
 }

-blockquote{
-    quotes:"#{$open-quote}" "#{$close-quote}";
+blockquote {
+  quotes: "#{$open-quote}""#{$close-quote}";

-    p:before{
-        content:"#{$open-quote}";
-        content:open-quote;
-    }
-    p:after{
-        content:"";
-        content:no-close-quote;
-    }
-    p:last-of-type:after{
-        content:"#{$close-quote}";
-        content:close-quote;
-    }
+  p:before {
+    content: "#{$open-quote}";
+    content: open-quote;
+  }
+  p:after {
+    content: "";
+    content: no-close-quote;
+  }
+  p:last-of-type:after {
+    content: "#{$close-quote}";
+    content: close-quote;
+  }

-    q:before{
-        content:"\2018";
-        content:open-quote;
-    }
-    q:after{
-        content:"\2019";
-        content:close-quote;
-    }
+  q:before {
+    content: "\2018";
+    content: open-quote;
+  }
+  q:after {
+    content: "\2019";
+    content: close-quote;
+  }
 }

-
 /**
 *
   <blockquote>
@ -76,22 +72,22 @@ blockquote{
   </blockquote>
 *
 */
-blockquote{
-    /**
+blockquote {
+  /**
     * .4em is roughly equal to the width of the opening “ that we wish to hang.
     */
-    text-indent:-0.41em;
+  text-indent: -0.41em;

-    p:last-of-type{
-        margin-bottom:0;
-    }
+  p:last-of-type {
+    margin-bottom: 0;
+  }
 }

-.source{
-    display:block;
-    text-indent:0;
+.source {
+  display: block;
+  text-indent: 0;

-    &:before{
-        content:"\2014";
-    }
+  &:before {
+    content: "\2014";
+  }
 }
--- a/sass/oscailte/base/_post.scss
+++ b/sass/oscailte/base/_post.scss
@ -1,7 +1,6 @@
 $meta-color: lighten($text-color, 20%);

 article {
-
  blockquote {
    @extend .clearfix;
    border-left: 2px solid $primary-color;
@ -24,16 +23,17 @@ article {
    }
  }

-  .pullquote-left::before, .pullquote-right::before {
-    @media only screen and (max-width: $palm-end){
-      border-top:    1px dotted $primary-color;
+  .pullquote-left::before,
+  .pullquote-right::before {
+    @media only screen and (max-width: $palm-end) {
+      border-top: 1px dotted $primary-color;
      border-bottom: 1px dotted $primary-color;
      padding: 0 10px;
      width: 100%;
    }
    border: medium none;
    color: $primary-color;
-    content: "\201C" attr(data-pullquote) "\201D";
+    content: "\201C"attr(data-pullquote) "\201D";
    float: right;
    font-family: $serif;
    font-size: 1.4em;
@ -42,7 +42,7 @@ article {
    margin: 0.3em 0 1em 1.5em;
    padding: 0;
    position: relative;
-      top: 7px;
+    top: 7px;
    width: 45%;
  }

@ -60,7 +60,9 @@ article {
      a {
        color: $meta-color;
        text-decoration: none;
-        &:hover {text-decoration: underline;}
+        &:hover {
+          text-decoration: underline;
+        }
      }
    }
  }
@ -105,7 +107,7 @@ article {
  }

  &.post {
-    @media only screen and (max-width: $palm-end){
+    @media only screen and (max-width: $palm-end) {
      .tags {
        clear: both;
        margin-top: 7px;
--- a/source/_docs/configuration/templating.markdown
+++ b/source/_docs/configuration/templating.markdown
@ -325,7 +325,10 @@ Some of these functions can also be used in a [filter](https://jinja.palletsproj
 - `e` mathematical constant, approximately 2.71828.
 - `pi` mathematical constant, approximately 3.14159.
 - `tau` mathematical constant, approximately 6.28318.
- Filter `round(x)` will convert the input to a number and round it to `x` decimals.
+- Filter `round(x)` will convert the input to a number and round it to `x` decimals. Round has four modes and the default mode (with no mode specified) will [round-to-even](https://en.wikipedia.org/wiki/Rounding#Roundhalfto_even).
+  - `round(x, "floor")` will always round down to `x` decimals
+  - `round(x, "ceil")` will always round up to `x` decimals
+  - `round(1, "half")` will always round to the nearest .5 value. `x` should be 1 for this mode
 - Filter `max` will obtain the largest item in a sequence.
 - Filter `min` will obtain the smallest item in a sequence.
 - Filter `value_one|bitwise_and(value_two)` perform a bitwise and(&) operation with two values.
--- a/source/_integrations/alarm_control_panel.ifttt.markdown
+++ b/source/_integrations/alarm_control_panel.ifttt.markdown
@ -64,7 +64,7 @@ event_disarm:
  type: string
  default: alarm_disarm
 optimistic:
-  description: Specify if the state will be updated by an ifttt_push_alarm_state call (false) or can be set immediately (true).
+  description: Specify if the state will be updated by an ifttt.push_alarm_state call (false) or can be set immediately (true).
  required: false
  type: boolean
  default: false
@ -87,7 +87,7 @@ For this system to operate correctly, the following IFTTT applets have to be set
 * **IF** Webhook event `YOUR_ARM_HOME_EVENT` is called, **THEN** set the alarm system to armed home.
 * **IF** Webhook event `YOUR_ARM_NIGHT_EVENT` is called, **THEN** set the alarm system to armed away.
 * **IF** Webhook event `YOUR_DISARM_EVENT` is called, **THEN** set the alarm system to armed night.
-* **IF** the alarm system was disarmed, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/alarm_control_panel/ifttt_push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "disarmed"}`.
-* **IF** the alarm system state changed to armed home, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/alarm_control_panel/ifttt_push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_home"}`.
-* **IF** the alarm system state changed to armed away, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/alarm_control_panel/ifttt_push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_away"}`.
-* **IF** the alarm system state changed to armed night, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/alarm_control_panel/ifttt_push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_night"}`.
+* **IF** the alarm system was disarmed, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/ifttt/push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "disarmed"}`.
+* **IF** the alarm system state changed to armed home, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/ifttt/push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_home"}`.
+* **IF** the alarm system state changed to armed away, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/ifttt/push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_away"}`.
+* **IF** the alarm system state changed to armed night, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/ifttt/push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_night"}`.
--- a/source/_integrations/alarmdecoder.markdown
+++ b/source/_integrations/alarmdecoder.markdown
@ -135,7 +135,7 @@ The Alarm Decoder integration gives you access to several services for you to co
 - `alarm_arm_night`: Arms the alarm in instant mode; all faults will trigger the alarm. Additionally, the entry delay is turned off on the doors.
 - `alarm_disarm`: Disarms the alarm from any state. Also clears a `check_zone` flag after an alarm was triggered.
 - `alarmdecoder.alarm_keypress`: Sends a string of characters to the alarm, as if you had touched those keys on a keypad.
- `alarmdecoder_alarm_toggle_chime`: Toggles the alarm's chime state.
+- `alarmdecoder.alarm_toggle_chime`: Toggles the alarm's chime state.

 <div class='note'>

@ -157,11 +157,11 @@ Using a combination of the available services and attributes, you can create swi
      friendly_name: Chime
      value_template: "{{ is_state_attr('alarm_control_panel.alarm_panel', 'chime', true) }}"
      turn_on:
-        service: alarm_control_panel.alarmdecoder_alarm_toggle_chime
+        service: alarmdecoder.alarm_toggle_chime
        data:
          code: !secret alarm_code
      turn_off:
-        service: alarm_control_panel.alarmdecoder_alarm_toggle_chime
+        service: alarmdecoder.alarm_toggle_chime
        data:
          code: !secret alarm_code
      icon_template: >-
--- a/source/_integrations/apns.markdown
+++ b/source/_integrations/apns.markdown
@ -46,7 +46,7 @@ sandbox:
  type: boolean
 {% endconfiguration %}

-The APNS platform will register two services, `notify.NOTIFIER_NAME` and `notify.apns_NOTIFIER_NAME`.
+The APNS platform will register two services, `notify.NOTIFIER_NAME` and `apns.apns_NOTIFIER_NAME`.

 ### notify.apns_NOTIFIER_NAME

--- a/source/_integrations/aten_pe.markdown
+++ b/source/_integrations/aten_pe.markdown
@ -0,0 +1,53 @@
+---
+title: "ATEN Rack PDU"
+description: "Instructions on how to integrate ATEN Rack PDUs into Home Assistant."
+logo: aten.png
+ha_category:
+  - Switch
+ha_release: 0.103
+---
+
+The `aten_pe` integration lets you control [ATEN Rack PDUs](https://www.aten.com/eu/en/products/energy-intelligence-pduupsracks/rack-pdu/) from Home Assistant.
+
+In order to use it, SNMP must be enabled on your PDU. It is recommended to use SNMPv3 to protect your credentials from eavesdropping.
+
+Tested devices:
+  * [PE8324G](https://www.aten.com/eu/en/products/energy-intelligence-pduupsracks/rack-pdu/pe8324/)
+
+To set it up, add the following information to your `configuration.yaml` file:
+
+```yaml
+switch:
+  - platform: aten_pe
+    host: 192.168.0.60
+```
+
+{% configuration %}
+host:
+  description: The IP/host which to control.
+  required: true
+  type: string
+port:
+  description: The port on which to communicate.
+  required: false
+  type: string
+  default: 161
+community:
+  description: community string to use for authentication (SNMP v1 and v2c).
+  required: false
+  type: string
+  default: private
+username:
+  description: Username to use for authentication.
+  required: false
+  type: string
+  default: administrator
+auth_key:
+  description: Authentication key to use for SNMP v3.
+  required: false
+  type: string
+priv_key:
+  description: Privacy key to use for SNMP v3.
+  required: false
+  type: string
+{% endconfiguration %}
--- a/source/_integrations/bbox.markdown
+++ b/source/_integrations/bbox.markdown
@ -66,6 +66,8 @@ sensor:
      - up_max_bandwidth
      - current_down_bandwidth
      - current_up_bandwidth
+      - uptime
+      - number_of_reboots
 ```

 {% configuration %}
@ -87,4 +89,8 @@ monitored_variables:
      description: Instant measure of the current used bandwidth for download.
    current_up_bandwidth:
      description: Instant measure of the current used bandwidth for upload.
+    uptime:
+      description: Uptime since the last boot.
+    number_of_reboots:
+      description: Number of reboot since the initial configuration of the router.
 {% endconfiguration %}
--- a/source/_integrations/blackbird.markdown
+++ b/source/_integrations/blackbird.markdown
@ -52,7 +52,7 @@ sources:
      type: string
 {% endconfiguration %}

-### Service `media_player.blackbird_set_all_zones`
+### Service `blackbird.set_all_zones`

 Set all zones to the same input source. This service allows you to immediately synchronize all the TVs in your home. Regardless of `entity_id` provided, all zones will be updated.

--- a/source/_integrations/bluesound.markdown
+++ b/source/_integrations/bluesound.markdown
@ -55,7 +55,7 @@ media_player:
      - host: 192.168.1.131
 ```

-### Service `bluesound_join`
+### Service `bluesound.join`

 Group players together under a single master speaker. That will make a new group or join an existing group.

@ -64,7 +64,7 @@ Group players together under a single master speaker. That will make a new group
 | `master` | no | A single `entity_id` that will become/hold the master speaker.
 | `entity_id` | no | String or list of a single `entity_id` that will group to master speaker.

-### Service `bluesound_unjoin`
+### Service `bluesound.unjoin`

 Remove one or more speakers from a group of speakers. If no `entity_id` is provided, all speakers are unjoined.

@ -72,7 +72,7 @@ Remove one or more speakers from a group of speakers. If no `entity_id` is provi
 | ---------------------- | -------- | ----------- |
 | `entity_id` | yes | String or list of `entity_id`s that will be separated from their master speaker.

-### Service `bluesound_set_sleep_timer`
+### Service `bluesound.set_sleep_timer`

 Sets a timer that will turn off the speaker. For each time you call this it will increase the time by one step. The steps are (in minutes): 15, 30, 45, 60, 90, 0.
 If you increase an ongoing timer of for example 13 minutes, it will increase it to 15. If the timer is set to 90, it will remove the time (hence the 0).
@ -81,7 +81,7 @@ If you increase an ongoing timer of for example 13 minutes, it will increase it
 | ---------------------- | -------- | ----------- |
 | `entity_id` | no | String or list of `entity_id`s that will have their timers set.

-### Service `bluesound_clear_sleep_timer`
+### Service `bluesound.clear_sleep_timer`

 Clear the sleep timer on a speaker, if one is set.

--- a/source/_integrations/broadlink.markdown
+++ b/source/_integrations/broadlink.markdown
@ -3,6 +3,7 @@ title: "Broadlink"
 description: "Instructions on how to integrate Broadlink within Home Assistant."
 logo: broadlink.png
 ha_category:
+  - Remote
  - Switch
  - Sensor
 ha_release: 0.35
@ -11,9 +12,161 @@ ha_iot_class: Local Polling

 There is currently support for the following device types within Home Assistant:

+- [Remote](#remote)
 - [Sensor](#sensor)
 - [Switch](#switch)

+## Remote
+
+The `broadlink` remote platform allows you to interact with Broadlink remote control devices.
+
+### Configuration
+
+To enable it, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+remote:
+  - platform: broadlink
+    host: IP_ADDRESS
+    mac: MAC_ADDRESS
+```
+
+{% configuration %}
+host:
+  description: The hostname/IP address to connect to.
+  required: true
+  type: string
+mac:
+  description: Device MAC address.
+  required: true
+  type: string
+timeout:
+  description: Timeout in seconds for the connection to the device.
+  required: false
+  default: 5
+  type: integer
+name:
+  description: Name of the device.
+  required: false
+  default: Broadlink
+  type: string
+{% endconfiguration %}
+  
+### Learn command
+
+Use the `remote.learn_command` service to learn new commands.
+
+| Service data attribute | Optional | Description                               |
+| ---------------------- | -------- | ----------------------------------------- |
+| `entity_id`            | no       | ID of the remote.                         |
+| `device`               | no       | Name of the device to control.            |
+| `command`              | no       | Names of the commands to learn.           |
+| `alternative`          | yes      | Toggle commands?                          |
+| `timeout`              | yes      | Timeout in seconds to learn each command. |
+
+Example 1: Learn a single command
+
+```yaml
+script:
+  learn_mute_tv:
+    sequence:
+      - service: remote.learn_command
+        data:
+          entity_id: remote.bedroom
+          device: television
+          command: mute
+```
+
+Example 2: Learn a sequence of commands
+
+```yaml
+script:
+  learn_tv_commands:
+    sequence:
+      - service: remote.learn_command
+        data:
+          entity_id: remote.bedroom
+          device: television
+          command:
+            - turn on
+            - turn off
+            - volume up
+            - volume down
+```
+
+Example 3: Learn a toggle command
+
+The `alternative` flag is useful for capturing commands where the same button is used for more than one purpose, such as the power button, which can turn the television on and off.
+
+```yaml
+script:
+  learn_tv_power_button:
+    sequence:
+      - service: remote.learn_command
+        data:
+          entity_id: remote.bedroom
+          device: television
+          command: power
+          alternative: True
+```
+
+In the above example, two codes will be captured for the power command, and will be sent alternately each time the command is called.
+
+### Send command
+
+Use the `remote.send_command` service to send commands.
+
+| Service data attribute | Optional | Description                                          |
+| ---------------------- | -------- | ---------------------------------------------------- |
+| `entity_id`            | no       | ID of the remote.                                    |
+| `device`               | no       | Name of the device to control.                       |
+| `command`              | no       | Names of the commands to send.                       |
+| `num_repeats`          | yes      | Number of times to repeat the commands.              |
+| `delay_secs`           | yes      | Interval in seconds between one command and another. |
+
+Example 1: Send a single command
+
+```yaml
+script:
+  mute_tv:
+    sequence:
+      - service: remote.send_command
+        data:
+          entity_id: remote.bedroom
+          device: television
+          command: mute
+```
+
+Example 2: Send a command repeatedly
+
+```yaml
+script:
+  turn_up_tv_volume_20:
+    sequence:
+      - service: remote.send_command
+        data:
+          entity_id: remote.bedroom
+          device: television
+          command: volume up
+          num_repeats: 20
+```
+
+Example 3: Send a sequence of commands
+
+```yaml
+script:
+  turn_on_ac:
+    sequence:
+      - service: remote.send_command
+        data:
+          entity_id: remote.bedroom
+          device: air conditioner
+          command:
+            - turn on
+            - turn off display
+```
+
 ## Sensor

 The `broadlink` sensor platform let you monitor data from an RM2 and A1 E-air. There is currently no support for the cloud API.
@ -292,10 +445,10 @@ switch:

 You can use the service `broadlink.send` to directly send IR packets without the need to assign a switch entity for each command.

-| Service data attribute | Optional | Description |
-| ---------------------- | -------- | ----------- |
-| `host`   | no | IP address to send command to.
-| `packet` | no | String or list of strings that contain the packet data.
+| Service data attribute | Optional | Description                                             |
+| ---------------------- | -------- | ------------------------------------------------------- |
+| `host`                 | no       | IP address to send command to.                          |
+| `packet`               | no       | String or list of strings that contain the packet data. |

 Example:

--- a/source/_integrations/channels.markdown
+++ b/source/_integrations/channels.markdown
@ -40,7 +40,7 @@ name:
  type: string
 {% endconfiguration %}

-### Service `channels_seek_forward`
+### Service `seek_forward`

 Seek forward by the number of seconds currently set in settings on the instance of Channels.

@ -49,7 +49,7 @@ Seek forward by the number of seconds currently set in settings on the instance
 | `entity_id` | no | String that points at `entity_id` of Channels app.


-### Service `channels_seek_backward`
+### Service `seek_backward`

 Seek backward by the number of seconds currently set in settings on the instance of Channels.

@ -57,7 +57,7 @@ Seek backward by the number of seconds currently set in settings on the instance
 | ---------------------- | -------- | ----------- |
 | `entity_id` | no | String that points at `entity_id` of Channels app.

-### Service `channels_seek_by`
+### Service `seek_by`

 Seek forward or backward by a provided number of seconds.

--- a/source/_integrations/climate.modbus.markdown
+++ b/source/_integrations/climate.modbus.markdown
@ -22,6 +22,14 @@ climate:
    name: Watlow F4T
    hub: hub1
    slave: 1
+    data_type: uint
+    count: 1
+    scale: 0.1
+    offset: 0
+    precision: 1
+    max_temp: 30
+    min_temp: 15
+    temp_step: 1
    target_temp_register: 2782
    current_temp_register: 27586
 ```
@ -62,6 +70,36 @@ precision:
  required: false
  type: integer
  default: 0
+scale:
+  description: Scale factor (output = scale * value + offset).
+  required: false
+  type: float
+  default: 1
+offset:
+  description: Final offset (output = scale * value + offset).
+  required: false
+  type: float
+  default: 0
+max_temp:
+  description: Maximum setpoint temperature.
+  required: false
+  type: integer
+  default: 35
+min_temp:
+  description: Maximum setpoint temperature.
+  required: false
+  type: integer
+  default: 5 
+temp_step:
+  description: The supported step size a target temperature can be increased/decreased.
+  required: false
+  type: float
+  default: 0.5 
+temperature_unit:
+  description: Temperature unit reported by the current_temp_register. C or F
+  required: false
+  type: string
+  default: C
 {% endconfiguration %}


--- a/source/_integrations/comfoconnect.markdown
+++ b/source/_integrations/comfoconnect.markdown
@ -58,14 +58,27 @@ To register the sensors, add the following to your `configuration.yaml` file:
 sensor:
  - platform: comfoconnect
    resources:
-      - current_temperature
-      - current_humidity
-      - outside_temperature
-      - outside_humidity
-      - air_flow_supply
      - air_flow_exhaust
+      - air_flow_supply
+      - bypass_state
+      - current_humidity
+      - current_temperature
+      - days_to_replace_filter
+      - exhaust_fan_duty
+      - exhaust_fan_speed
+      - exhaust_humidity
+      - exhaust_temperature
+      - outside_humidity
+      - outside_temperature
+      - power_usage
+      - supply_fan_duty
+      - supply_fan_speed
+      - supply_humidity
+      - supply_temperature
 ```

+The list above indicates all supported sensors. It is recommended to only include the ones you need.
+
 <div class='note'>
 Note that it's not possible to have multiple connection to the bridge at the same time. This integration will keep the connection open, and if you open the app, it will ask you to disconnect Home Assistant. If you close the app again, Home Assistant will reconnect automatically.
 </div>
--- a/source/_integrations/dsmr_reader.markdown
+++ b/source/_integrations/dsmr_reader.markdown
@ -0,0 +1,24 @@
+---
+title: "DSMR Reader"
+description: "Instructions on how to integrate DSMR Reader."
+ha_category:
+  - Energy
+ha_iot_class: Cloud Polling
+ha_release: 0.103
+---
+
+The `dsmr_reader` sensor platform allows you to easily add all sensors that [DSMR Reader](https://dsmr-reader.readthedocs.io/en/latest/) exposes to MQTT. It adds a separate sensor for every field in the MQTT topics.
+
+## Setup
+
+To use this component, you will need DSMR Reader to be set up to publish to the MQTT server, that Home Assistant also uses. It is important that you setup DSMR Reader to publish to MQTT using "Split Topic" and that you use the default mappings.
+
+## Configuration
+
+To use this sensor in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: dsmr_reader
+```
--- a/source/_integrations/envisalink.markdown
+++ b/source/_integrations/envisalink.markdown
@ -137,5 +137,5 @@ The following services are supported by Envisalink and can be used to script or
 - **alarm_arm_away**: Arms the alarm in standard away mode.
 - **alarm_arm_night**: Arms the alarm in night mode.
 - **alarm_trigger**: Trigger an alarm on the Envisalink connected alarm system. For example, a newer zwave/zigbee sensor can now be integrated into a legacy alarm system using a Home Assistant automation.
- **envisalink_alarm_keypress**: Sends a string of up to 6 characters to the alarm. *Works with DSC panels, and confirmed to work with Honeywell Vista-20P (aka First Alert FA-168)*
+- **alarm_keypress**: Sends a string of up to 6 characters to the alarm. *Works with DSC panels, and confirmed to work with Honeywell Vista-20P (aka First Alert FA-168)*
 - **invoke_custom_function**: Invokes a custom PGM function. *DSC alarms only*
--- a/source/_integrations/facebox.markdown
+++ b/source/_integrations/facebox.markdown
@ -111,9 +111,9 @@ Use the `image_processing.detect_face` events to trigger automations, and breako
 ```
 {% endraw %}

-## Service `facebox_teach_face`
+## Service `facebox.teach_face`

-The service `facebox_teach_face` can be used to teach Facebox faces.
+The service `facebox.teach_face` can be used to teach Facebox faces.

 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
@ -141,7 +141,7 @@ You can use an automation to receive a notification when you train a face:
  alias: Face taught
  trigger:
  - event_data:
-      service: facebox_teach_face
+      service: facebox.teach_face
    event_type: call_service
    platform: event
  condition: []
--- a/source/_integrations/fan.xiaomi_miio.markdown
+++ b/source/_integrations/fan.xiaomi_miio.markdown
@ -342,7 +342,7 @@ Set the fan speed/operation mode.
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.                      |
 | `speed`                   |       no | Fan speed. Valid values are 'Auto', 'Silent', 'Favorite' and 'Idle' |

-### Service `fan.xiaomi_miio_set_buzzer_on` (Air Purifier Pro excluded)
+### Service `xiaomi_miio.fan_set_buzzer_on` (Air Purifier Pro excluded)

 Turn the buzzer on.

@ -350,7 +350,7 @@ Turn the buzzer on.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |

-### Service `fan.xiaomi_miio_set_buzzer_off` (Air Purifier Pro excluded)
+### Service `xiaomi_miio.fan_set_buzzer_off` (Air Purifier Pro excluded)

 Turn the buzzer off.

@ -358,7 +358,7 @@ Turn the buzzer off.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |

-### Service `fan.xiaomi_miio_set_led_on` (Air Purifiers only)
+### Service `xiaomi_miio.fan_set_led_on` (Air Purifiers only)

 Turn the led on.

@ -366,7 +366,7 @@ Turn the led on.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |

-### Service `fan.xiaomi_miio_set_led_off` (Air Purifiers only)
+### Service `xiaomi_miio.fan_set_led_off` (Air Purifiers only)

 Turn the led off.

@ -374,7 +374,7 @@ Turn the led off.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |

-### Service `fan.xiaomi_miio_set_child_lock_on`
+### Service `xiaomi_miio.fan_set_child_lock_on`

 Turn the child lock on.

@ -382,7 +382,7 @@ Turn the child lock on.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |

-### Service `fan.xiaomi_miio_set_child_lock_off`
+### Service `xiaomi_miio.fan_set_child_lock_off`

 Turn the child lock off.

@ -390,7 +390,7 @@ Turn the child lock off.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |

-### Service `fan.xiaomi_miio_set_led_brightness` (Air Purifier 2S and Air Purifier Pro excluded)
+### Service `xiaomi_miio.fan_set_led_brightness` (Air Purifier 2S and Air Purifier Pro excluded)

 Set the led brightness. Supported values are 0 (Bright), 1 (Dim), 2 (Off).

@ -399,7 +399,7 @@ Set the led brightness. Supported values are 0 (Bright), 1 (Dim), 2 (Off).
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |
 | `brightness`              |       no | Brightness, between 0 and 2.                            |

-### Service `fan.xiaomi_miio_set_favorite_level` (Air Purifiers only)
+### Service `xiaomi_miio.fan_set_favorite_level` (Air Purifiers only)

 Set the favorite level of the operation mode "favorite".

@ -408,7 +408,7 @@ Set the favorite level of the operation mode "favorite".
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |
 | `level`                   |       no | Level, between 0 and 16.                                |

-### Service `fan.xiaomi_miio_set_auto_detect_on` (Air Purifier 2S and Air Purifier Pro only)
+### Service `xiaomi_miio.fan_set_auto_detect_on` (Air Purifier 2S and Air Purifier Pro only)

 Turn the auto detect on.

@ -416,7 +416,7 @@ Turn the auto detect on.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |

-### Service `fan.xiaomi_miio_set_auto_detect_off` (Air Purifier 2S and Air Purifier Pro only)
+### Service `xiaomi_miio.fan_set_auto_detect_off` (Air Purifier 2S and Air Purifier Pro only)

 Turn the auto detect off.

@ -424,7 +424,7 @@ Turn the auto detect off.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |

-### Service `fan.xiaomi_miio_set_learn_mode_on` (Air Purifier 2 only)
+### Service `xiaomi_miio.fan_set_learn_mode_on` (Air Purifier 2 only)

 Turn the learn mode on.

@ -432,7 +432,7 @@ Turn the learn mode on.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |

-### Service `fan.xiaomi_miio_set_learn_mode_off` (Air Purifier 2 only)
+### Service `xiaomi_miio.fan_set_learn_mode_off` (Air Purifier 2 only)

 Turn the learn mode off.

@ -440,7 +440,7 @@ Turn the learn mode off.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |

-### Service `fan.xiaomi_miio_set_volume` (Air Purifier Pro only)
+### Service `xiaomi_miio.fan_set_volume` (Air Purifier Pro only)

 Set the sound volume.

@ -449,7 +449,7 @@ Set the sound volume.
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |
 | `volume`                  |       no | Volume, between 0 and 100.                              |

-### Service `fan.xiaomi_miio_reset_filter` (Air Purifier 2 only)
+### Service `xiaomi_miio.fan_reset_filter` (Air Purifier 2 only)

 Reset the filter lifetime and usage.

@ -457,7 +457,7 @@ Reset the filter lifetime and usage.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |

-### Service `fan.xiaomi_miio_set_extra_features` (Air Purifier only)
+### Service `xiaomi_miio.fan_set_extra_features` (Air Purifier only)

 Set the extra features.

@ -466,7 +466,7 @@ Set the extra features.
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO fan entity.          |
 | `features`                |       no | Integer, known values are 0 and 1.                      |

-### Service `fan.xiaomi_miio_set_target_humidity` (Air Humidifier only)
+### Service `xiaomi_miio.fan_set_target_humidity` (Air Humidifier only)

 Set the target humidity.

--- a/source/_integrations/flume.markdown
+++ b/source/_integrations/flume.markdown
@ -0,0 +1,73 @@
+---
+title: "flume"
+description: "Documentation about the flume sensor."
+logo: flume.jpg
+ha_category:
+  - Sensor
+ha_iot_class: Cloud Polling
+ha_release: 0.103
+---
+
+The `flume` sensor will show you the current [flume](https://portal.flumetech.com/) status for the given Device ID.
+
+Flume monitors the real-time status of your home water meter. Allowing the end-user to detect small leaks, gain real-time information on household water consumption, set water goals and budgets, and receive push notifications when suspicious water activities occur. 
+
+## Configuration
+
+You can find your Client ID and Client Secret under "API Access" on the [settings page](https://https://portal.flumetech.com/#settings). 
+
+To enable the flume sensor, add the following lines to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  # Flume
+  - platform: flume
+    username: YOUR_FLUME_USERNAME
+    password: YOUR_FLUME_PASSWORD
+    client_id: YOUR_FLUME_CLIENT_ID
+    client_secret: YOUR_FLUME_CLIENT_SECRET
+```
+
+{% configuration %}
+username:
+  description: Your flume user id.
+  required: true
+  type: string
+password:
+  description: Your flume password.
+  required: true
+  type: string
+client_id:
+  description: Your flume Client ID.
+  required: true
+  type: string
+client_secret:
+  description: Your flume Client Secret.
+  required: true
+  type: string
+name:
+  description: A name to display on the sensor.
+  required: false
+  default: Flume Sensor
+  type: string
+{% endconfiguration %}
+
+# Configuration for Binary Sensor
+
+The following YAML creates a binary sensor. This requires the default sensor to be configured successfully.
+
+{% raw %}
+
+```yaml
+# Example configuration.yaml entry
+binary_sensor:
+  - platform: template
+    sensors:
+      flume_status:
+        friendly_name: "Flume Flow Status"
+        value_template: >-
+          {{ states.sensor.flume_sensor.state != "0" }}
+```
+
+{% endraw %}
--- a/source/_integrations/fritzbox_callmonitor.markdown
+++ b/source/_integrations/fritzbox_callmonitor.markdown
@ -23,6 +23,7 @@ $ sudo apt-get install libxml2-dev libxslt-dev \

 If you installed Home Assistant in a virtualenv, also run the following command inside it.
 Be patient this will take a while.
+
 ```bash
 pip3 install lxml
 ```
@ -48,7 +49,7 @@ name:
  default: Phone
  type: string
 host:
-  description: The IP address of your router, e.g., 192.168.1.1. It is optional since every fritzbox is also reachable by using the IP address 169.254.1.1.
+  description: The IP address of your router, e.g., 192.168.1.1. It is optional since every FRITZ!Box is also reachable by using the IP address 169.254.1.1. If you have a local DNS server and have assigned a hostname to your FRITZ!Box, you can also use that here instead of the IP address.
  required: false
  default: 169.254.1.1
  type: string
--- a/source/_integrations/geonetnz_volcano.markdown
+++ b/source/_integrations/geonetnz_volcano.markdown
@ -0,0 +1,96 @@
+---
+title: "GeoNet NZ Volcanic Alert Level"
+description: "Instructions on how to integrate the GeoNet New Zealand Volcanic Alert Level feed into Home Assistant."
+logo: geonet-nz.png
+ha_category:
+  - Sensor
+ha_iot_class: Cloud Polling
+ha_release: 0.103
+ha_config_flow: true
+---
+
+The `geonetnz_volcano` integration lets you use a GeoJSON feed provided by 
+New Zealand's [GeoNet](https://www.geonet.org.nz/) with information 
+about volcanoes in the New Zealand region. 
+It shows information of those volcanoes filtered by distance to Home Assistant's 
+location.
+
+Entities are generated and updated automatically with each update 
+from the feed. Each entity defines the [volcanic alert level](https://www.geonet.org.nz/about/volcano/val) 
+as its state.  Latitude and longitude of the volcano are included as attributes 
+to show on the default map automatically.
+
+The data is updated every 5 minutes.
+
+<p class='img'>
+  <img src='{{site_root}}/images/integrations/geonetnz_volcano/map.png' />
+</p>
+
+<p class='img'>
+  <img src='{{site_root}}/images/integrations/geonetnz_volcano/sensor.png' />
+</p>
+
+<div class='note'>
+
+The material used by this integration is provided under the [Creative Commons Attribution 3.0 New Zealand (CC BY 3.0 NZ) license](http://creativecommons.org/licenses/by/3.0/nz/).
+It has only been modified for the purpose of presenting the material in Home Assistant.
+Please refer to the [creator's disclaimer notice](https://www.geonet.org.nz/disclaimer) and [data policy](https://www.geonet.org.nz/policy) for more information.
+
+We acknowledge the New Zealand GeoNet project and its sponsors EQC, GNS Science and LINZ, for providing data/images used in this integration.
+
+</div>
+
+## Configuration
+
+To integrate the GeoNet New Zealand Volcanic Alert Level feed use the **Integrations** feature 
+in the GUI, you find it under **Configurations** -> **Integrations**, or add the 
+following line to your `configuration.yaml`.
+
+```yaml
+# Example configuration.yaml entry
+geonetnz_volcano:
+```
+
+{% configuration %}
+radius:
+  description: The radius around your location to monitor; defaults to 50 km or mi (depending on the unit system defined in your configuration).
+  required: false
+  type: float
+  default: 50.0
+latitude:
+  description: Latitude of the coordinates around which volcanoes are considered.
+  required: false
+  type: float
+  default: Latitude defined in your configuration.
+longitude:
+  description: Longitude of the coordinates around which volcanoes are considered.
+  required: false
+  type: float
+  default: Longitude defined in your configuration.
+{% endconfiguration %}
+
+## State Attributes
+
+The following state attributes are available for each entity in addition to 
+the standard ones:
+
+| Attribute              | Description |
+|------------------------|-------------|
+| latitude               | Latitude of the volcano.  |
+| longitude              | Longitude of the volcano. |
+| external_id            | The external ID used in the feed to identify the volcano. |
+| activity               | Volcanic activity. |
+| hazards                | Most likely hazards. |
+| distance               | The distance in km or mi to Home Assistant's location. |
+| last update            | Timestamp of the last update from the feed.  |
+| last update successful | Timestamp of the last successful update from the feed.  |
+
+## Full Configuration
+
+```yaml
+# Example configuration.yaml entry
+geonetnz_quakes:
+  radius: 100
+  latitude: -41.2
+  longitude: 174.7
+```
--- a/source/_integrations/google_assistant.markdown
+++ b/source/_integrations/google_assistant.markdown
@ -193,7 +193,7 @@ Currently, the following domains are available to be used with Google Assistant,
 - media_player (on/off/set volume (via set volume)/source (via set input source))
 - climate (temperature setting, hvac_mode)
 - vacuum (dock/start/stop/pause)
- sensor (temperature setting, only for temperature sensor)
+- sensor (temperature setting for temperature sensors and humidity setting for humidity sensors)
 - Alarm Control Panel (Arm/Disarm)

 <div class='note warning'>
--- a/source/_integrations/harmony.markdown
+++ b/source/_integrations/harmony.markdown
@ -182,7 +182,7 @@ data:
  delay_secs: 0.6
 ```

-### Service `remote.harmony_change_channel`
+### Service `harmony.change_channel`

 Sends the change channel command to the Harmony HUB

@ -194,13 +194,13 @@ Sends the change channel command to the Harmony HUB
 A typical service call for changing the channel would be::

 ```yaml
-service: remote.change_channel
+service: harmony.change_channel
 data:
  entity_id: remote.tv_room
  channel: 200
 ```

-### Service `remote.harmony_sync`
+### Service `harmony.sync`

 Force synchronization between the Harmony device and the Harmony cloud.

--- a/source/_integrations/heatmiser.markdown
+++ b/source/_integrations/heatmiser.markdown
@ -17,25 +17,24 @@ To set it up, add the following information to your `configuration.yaml` file:
 ```yaml
 climate:
  - platform: heatmiser
-    ipaddress: YOUR_IP_ADDRESS
+    host: YOUR_IP_ADDRESS
    port: YOUR_PORT
    tstats:
-      - 1:
-        id: THERMOSTAT_ID
+      - id: THERMOSTAT_ID
        name: THERMOSTAT_NAME
 ```

 A single interface can handle up to 32 connected devices.

 {% configuration %}
-ipaddress:
+host:
  description: The IP address of your interface.
  required: true
  type: string
 port:
  description: The port that the interface is listening on.
  required: true
-  type: integer
+  type: string
 tstats:
  description: A list of thermostats activated on the gateway.
  required: true
--- a/source/_integrations/hisense_aehw4a1.markdown
+++ b/source/_integrations/hisense_aehw4a1.markdown
@ -0,0 +1,44 @@
+---
+title: "Hisense AEH-W4A1"
+description: "Instructions to setup the Hisense AEH W4A1 WiFi module for ACs."
+logo: hisense.png
+ha_release: 0.103
+ha_category:
+  - Climate
+ha_iot_class: Local Poll
+---
+
+The Hisense AEH-W4A1 is a WiFi module used to give WiFi connectivity to some Hisense ACs and rebranded models (Smart Cool, Beko and others).
+
+Later AC models use other WiFi modules (like AEH-W4B1 and AEH-W4E1) that are not compatible or otherwise tested with this integration.
+
+It is highly recommended not to use one of the official smartphone applications and this integration at the same time, to avoid problems related to command collision.
+
+## Configuration
+
+To integrate one or more Hisense AEH-W4A1 controlled ACs with Home Assistant, use the Configuration/Integrations or add the following section to your `configuration.yaml` file:
+
+```yaml
+# Automatic discovery
+hisense_aehw4a1:
+```
+
+Alternately, devices that are not discoverable can be statically configured.
+The use of static configuration disables automatic discovery.
+
+{% configuration %}
+ip_address:
+  description: One or more static IP addresses
+  required: false
+  type: list
+{% endconfiguration %}
+
+## Full configuration example
+
+```yaml
+# Static configured devices
+hisense_aehw4a1:
+  ip_address:
+  - 192.168.5.10
+  - 192.168.5.20
+```
--- a/source/_integrations/html5.markdown
+++ b/source/_integrations/html5.markdown
@ -232,7 +232,7 @@ data:

 ### Dismiss

-You can dismiss notifications by using service notify.html5_dismiss like so:
+You can dismiss notifications by using service html5.dismiss like so:

 ```json
 {
--- a/source/_integrations/huawei_lte.markdown
+++ b/source/_integrations/huawei_lte.markdown
@ -8,6 +8,7 @@ ha_category:
  - Notifications
  - Sensor
  - Switch
+  - Binary Sensor
 ha_release: 0.79
 ha_iot_class: Local Polling
 ---
@ -20,6 +21,7 @@ There is currently support for the following platforms within Home Assistant:
 - Notifications - via SMS
 - Sensors - device, signal, and traffic information
 - Switch - mobile data on/off
+- Binary sensor - mobile connection status

 ## Configuration

@ -44,6 +46,7 @@ default:
 - WAN IP address sensor
 - LTE signal sensors RSRQ, RSRP, RSSI, and SINR
 - mobile data switch
+- mobile connection binary sensor
 - device tracker entries

 The rest are added to the entity registry, but disabled by default.
--- a/source/_integrations/icloud.markdown
+++ b/source/_integrations/icloud.markdown
@ -64,7 +64,7 @@ If 2 Step Authentication is enabled for your iCloud account. The integration wil
 2 Factor Authentication is the improved version of 2 Step Authentication, this is still not supported by the pyicloud library. Therefore it's not possible to use it with the device_tracker yet.

 4 services are available for this component:
- **icloud_update**: This service can be used to ask for an update of a certain iDevice. The `account_name` and `device_name` are optional. Request will result in new Home Assistant [state_changed](/docs/configuration/events/#event-state_changed) event describing current iphone location. Can be used in automations when manual location update is needed, e.g., to check if anyone is home when door's been opened.
- **icloud_lost_iphone**: This service will play the Lost iPhone sound on a certain iDevice. The `account_name` and `device_name` are optional.
- **icloud_set_interval**: This service will change the dynamic interval of an iDevice. The `account_name` and `device_name` are optional. If `interval` is used in the service_data, the iDevice will be updated with that new interval. That interval will be fixed until the iDevice changes zone or if this service is called again. If `interval` isn't used in the service_data, the interval for that iDevice will revert back to its default dynamic interval based on its current zone, its distance towards home and its battery level.
- **icloud_reset_account**: This service can be used to reset an iCloud account. This is helpful when not all devices are found by the integration or if you have added a new iDevice to your account. The `account_name` is optional.
+- **update**: This service can be used to ask for an update of a certain iDevice. The `account_name` and `device_name` are optional. Request will result in new Home Assistant [state_changed](/docs/configuration/events/#event-state_changed) event describing current iphone location. Can be used in automations when manual location update is needed, e.g., to check if anyone is home when door's been opened.
+- **lost_iphone**: This service will play the Lost iPhone sound on a certain iDevice. The `account_name` and `device_name` are optional.
+- **set_interval**: This service will change the dynamic interval of an iDevice. The `account_name` and `device_name` are optional. If `interval` is used in the service_data, the iDevice will be updated with that new interval. That interval will be fixed until the iDevice changes zone or if this service is called again. If `interval` isn't used in the service_data, the interval for that iDevice will revert back to its default dynamic interval based on its current zone, its distance towards home and its battery level.
+- **reset_account**: This service can be used to reset an iCloud account. This is helpful when not all devices are found by the integration or if you have added a new iDevice to your account. The `account_name` is optional.
--- a/source/_integrations/jewish_calendar.markdown
+++ b/source/_integrations/jewish_calendar.markdown
@ -82,53 +82,54 @@ For easier use in automations, all time sensors have a `timestamp` attribute, wh

 ### Holiday sensor

-The holiday sensor includes two attibutes: *type* and *id*.
+The holiday sensor includes 3 attributes: *type*, *type_id* and *id*.
+The *type_id* is useful for cases to condition automations based on a range of types.

 The following is the list of holidays the sensor knows about with their selected type:


-| ID                   | English                    | Hebrew                | Type                      |
-|----------------------|----------------------------|-----------------------|---------------------------|
-| erev_rosh_hashana    | Erev Rosh Hashana          | ערב ראש השנה          | EREV_YOM_TOV              |
-| rosh_hashana_i       | Rosh Hashana I             | א' ראש השנה           | YOM_TOV                   |
-| rosh_hashana_ii      | Rosh Hashana II            | ב' ראש השנה           | YOM_TOV                   |
-| tzom_gedaliah        | Tzom Gedaliah              | צום גדליה             | FAST_DAY                  |
-| erev_yom_kippur      | Erev Yom Kippur            | עיוה"כ               | EREV_YOM_TOV              |
-| yom_kippur           | Yom Kippur                 | יום הכפורים           | YOM_TOV                   |
-| erev_sukkot          | Erev Sukkot                | ערב סוכות             | EREV_YOM_TOV              |
-| sukkot               | Sukkot                     | סוכות                 | YOM_TOV                   |
-| hol_hamoed_sukkot    | Hol hamoed Sukkot          | חול המועד סוכות       | HOL_HAMOED                |
-| hoshana_raba         | Hoshana Raba               | הושענא רבה            | EREV_YOM_TOV              |
-| simchat_torah        | Simchat Torah              | שמחת תורה             | YOM_TOV                   |
-| chanukah             | Chanukah                   | חנוכה                 | MELACHA_PERMITTED_HOLIDAY |
-| asara_btevet         | Asara B'Tevet              | צום עשרה בטבת         | FAST_DAY                  |
-| tu_bshvat            | Tu B'Shvat                 | ט"ו בשבט             | MINOR_HOLIDAY             |
-| taanit_esther        | Ta'anit Esther             | תענית אסתר            | FAST_DAY                  |
-| purim                | Purim                      | פורים                 | MELACHA_PERMITTED_HOLIDAY |
-| shushan_purim        | Shushan Purim              | שושן פורים            | MELACHA_PERMITTED_HOLIDAY |
-| erev_pesach          | Erev Pesach                | ערב פסח               | EREV_YOM_TOV              |
-| pesach               | Pesach                     | פסח                   | YOM_TOV                   |
-| hol_hamoed_pesach    | Hol hamoed Pesach          | חול המועד פסח         | HOL_HAMOED                |
-| pesach_vii           | Pesach VII                 | שביעי פסח             | YOM_TOV                   |
-| yom_haatzmaut        | Yom HaAtzma'ut             | יום העצמאות           | MODERN_HOLIDAY            |
-| lag_bomer            | Lag B'Omer                 | ל"ג בעומר            | MINOR_HOLIDAY             |
-| erev_shavuot         | Erev Shavuot               | ערב שבועות            | EREV_YOM_TOV              |
-| shavuot              | Shavuot                    | שבועות                | YOM_TOV                   |
-| tzom_tammuz          | Tzom Tammuz                | צום שבעה עשר בתמוז    | FAST_DAY                  |
-| tisha_bav            | Tish'a B'Av                | תשעה באב              | FAST_DAY                  |
-| tu_bav               | Tu B'Av                    | ט"ו באב              | MINOR_HOLIDAY             |
-| yom_hashoah          | Yom HaShoah                | יום השואה             | MEMORIAL_DAY              |
-| yom_hazikaron        | Yom HaZikaron              | יום הזכרון            | MEMORIAL_DAY              |
-| yom_yerushalayim     | Yom Yerushalayim           | יום ירושלים           | MODERN_HOLIDAY            |
-| shmini_atzeret       | Shmini Atzeret             | שמיני עצרת            | YOM_TOV                   |
-| pesach_viii          | Pesach VIII                | אחרון של פסח          | YOM_TOV                   |
-| shavuot_ii           | Shavuot II                 | שני של שבועות         | YOM_TOV                   |
-| sukkot_ii            | Sukkot II                  | שני של סוכות          | YOM_TOV                   |
-| pesach_ii            | Pesach II                  | שני של פסח            | YOM_TOV                   |
-| family_day           | Family Day                 | יום המשפחה            | ISRAEL_NATIONAL_HOLIDAY   |
-| memorial_day_unknown | Memorial day for fallen whose place of burial is unknown | יום זכרון... | MEMORIAL_DAY |
-| rabin_memorial_day   | Yitzhak Rabin memorial day | יום הזכרון ליצחק רבין | MEMORIAL_DAY              |
-| zeev_zhabotinsky_day | Zeev Zhabotinsky day       | יום ז'בוטינסקי       | MEMORIAL_DAY              |
+| ID                   | English                    | Hebrew                | Type                          |
+|----------------------|----------------------------|-----------------------|--------------------------------|
+| erev_rosh_hashana    | Erev Rosh Hashana          | ערב ראש השנה          | EREV_YOM_TOV (2)              |
+| rosh_hashana_i       | Rosh Hashana I             | א' ראש השנה           | YOM_TOV (1)                   |
+| rosh_hashana_ii      | Rosh Hashana II            | ב' ראש השנה           | YOM_TOV (1)                   |
+| tzom_gedaliah        | Tzom Gedaliah              | צום גדליה             | FAST_DAY (5)                  |
+| erev_yom_kippur      | Erev Yom Kippur            | עיוה"כ                | EREV_YOM_TOV (2)              |
+| yom_kippur           | Yom Kippur                 | יום הכפורים           | YOM_TOV (1)                   |
+| erev_sukkot          | Erev Sukkot                | ערב סוכות             | EREV_YOM_TOV (2)              |
+| sukkot               | Sukkot                     | סוכות                 | YOM_TOV (1)                   |
+| hol_hamoed_sukkot    | Hol hamoed Sukkot          | חול המועד סוכות       | HOL_HAMOED (3)                |
+| hoshana_raba         | Hoshana Raba               | הושענא רבה            | EREV_YOM_TOV (2)              |
+| simchat_torah        | Simchat Torah              | שמחת תורה             | YOM_TOV (1)                   |
+| chanukah             | Chanukah                   | חנוכה                 | MELACHA_PERMITTED_HOLIDAY (4) |
+| asara_btevet         | Asara B'Tevet              | צום עשרה בטבת         | FAST_DAY (5)                  |
+| tu_bshvat            | Tu B'Shvat                 | ט"ו בשבט              | MINOR_HOLIDAY (7)             |
+| taanit_esther        | Ta'anit Esther             | תענית אסתר            | FAST_DAY (5)                  |
+| purim                | Purim                      | פורים                 | MELACHA_PERMITTED_HOLIDAY (4) |
+| shushan_purim        | Shushan Purim              | שושן פורים            | MELACHA_PERMITTED_HOLIDAY (4) |
+| erev_pesach          | Erev Pesach                | ערב פסח               | EREV_YOM_TOV (2)              |
+| pesach               | Pesach                     | פסח                   | YOM_TOV (1)                   |
+| hol_hamoed_pesach    | Hol hamoed Pesach          | חול המועד פסח         | HOL_HAMOED (3)                |
+| pesach_vii           | Pesach VII                 | שביעי פסח             | YOM_TOV (1)                   |
+| yom_haatzmaut        | Yom HaAtzma'ut             | יום העצמאות           | MODERN_HOLIDAY (6)            |
+| lag_bomer            | Lag B'Omer                 | ל"ג בעומר             | MINOR_HOLIDAY (7)             |
+| erev_shavuot         | Erev Shavuot               | ערב שבועות            | EREV_YOM_TOV (2)              |
+| shavuot              | Shavuot                    | שבועות                | YOM_TOV (1)                   |
+| tzom_tammuz          | Tzom Tammuz                | צום שבעה עשר בתמוז    | FAST_DAY (5)                  |
+| tisha_bav            | Tish'a B'Av                | תשעה באב              | FAST_DAY (5)                  |
+| tu_bav               | Tu B'Av                    | ט"ו באב               | MINOR_HOLIDAY (7)             |
+| yom_hashoah          | Yom HaShoah                | יום השואה             | MEMORIAL_DAY (8)              |
+| yom_hazikaron        | Yom HaZikaron              | יום הזכרון            | MEMORIAL_DAY (8)              |
+| yom_yerushalayim     | Yom Yerushalayim           | יום ירושלים           | MODERN_HOLIDAY (6)            |
+| shmini_atzeret       | Shmini Atzeret             | שמיני עצרת            | YOM_TOV (1)                   |
+| pesach_viii          | Pesach VIII                | אחרון של פסח          | YOM_TOV (1)                   |
+| shavuot_ii           | Shavuot II                 | שני של שבועות         | YOM_TOV (1)                   |
+| sukkot_ii            | Sukkot II                  | שני של סוכות          | YOM_TOV (1)                   |
+| pesach_ii            | Pesach II                  | שני של פסח            | YOM_TOV (1)                   |
+| family_day           | Family Day                 | יום המשפחה            | ISRAEL_NATIONAL_HOLIDAY (9)   |
+| memorial_day_unknown | Memorial day for fallen whose place of burial is unknown | יום זכרון... | MEMORIAL_DAY (8) |
+| rabin_memorial_day   | Yitzhak Rabin memorial day | יום הזכרון ליצחק רבין | MEMORIAL_DAY (8)              |
+| zeev_zhabotinsky_day | Zeev Zhabotinsky day       | יום ז'בוטינסקי        | MEMORIAL_DAY (8)              |


 ## Full configuration sample
--- a/source/_integrations/lifx.markdown
+++ b/source/_integrations/lifx.markdown
@ -65,7 +65,7 @@ script:

 The available light effects and their options are listed below.

-### Service `light.lifx_effect_pulse`
+### Service `lifx.effect_pulse`

 Run a flash effect by changing to a color and then back.

@ -80,7 +80,7 @@ Run a flash effect by changing to a color and then back.
 | `mode` | The way to change between colors. Valid modes: `blink` (default - direct transition to new color for 'period' time with original color between cycles), `breathe` (color fade transition to new color and back to original), `ping` (short pulse of new color), `strobe` (light turns off between color changes), `solid`(light does not return to original color between cycles).
 | `power_on` | Set this to False to skip the effect on lights that are turned off (defaults to True).

-### Service `light.lifx_effect_colorloop`
+### Service `lifx.effect_colorloop`

 Run an effect with colors looping around the color wheel. All participating lights will coordinate to keep similar (but not identical) colors.

@ -94,7 +94,7 @@ Run an effect with colors looping around the color wheel. All participating ligh
 | `spread` | Maximum color difference between participating lights, in degrees on a color wheel (ranges from 0 to 359).
 | `power_on` | Set this to False to skip the effect on lights that are turned off (defaults to True).

-### Service `light.lifx_effect_stop`
+### Service `lifx.effect_stop`

 Run an effect that does nothing, thereby stopping any other effect that might be running.

--- a/source/_integrations/light.xiaomi_miio.markdown
+++ b/source/_integrations/light.xiaomi_miio.markdown
@ -132,7 +132,7 @@ model:

 ## Platform Services

-### Service `light.xiaomi_miio_set_scene`
+### Service `xiaomi_miio.light_set_scene`

 Set one of the 4 available fixed scenes.

@ -141,7 +141,7 @@ Set one of the 4 available fixed scenes.
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO light entity.      |
 | `scene`                   |       no | Scene, between 1 and 4.                               |

-### Service `light.xiaomi_miio_set_delayed_turn_off`
+### Service `xiaomi_miio.light_set_delayed_turn_off`

 Delayed turn off.

@ -150,7 +150,7 @@ Delayed turn off.
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO light entity.      |
 | `time_period`             |       no | Time period for the delayed turn off.                 |

-### Service `light.xiaomi_miio_reminder_on` (Eyecare Smart Lamp 2 only)
+### Service `xiaomi_miio.light_reminder_on` (Eyecare Smart Lamp 2 only)

 Enable the eye fatigue reminder/notification.

@ -158,7 +158,7 @@ Enable the eye fatigue reminder/notification.
 |---------------------------|----------|-------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO light entity.      |

-### Service `light.xiaomi_miio_reminder_off` (Eyecare Smart Lamp 2 only)
+### Service `xiaomi_miio.light_reminder_off` (Eyecare Smart Lamp 2 only)

 Disable the eye fatigue reminder/notification.

@ -166,7 +166,7 @@ Disable the eye fatigue reminder/notification.
 |---------------------------|----------|-------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO light entity.      |

-### Service `light.xiaomi_miio_night_light_mode_on`  (Eyecare Smart Lamp 2 only)
+### Service `xiaomi_miio.light_night_light_mode_on`  (Eyecare Smart Lamp 2 only)

 Turn the smart night light mode on.

@ -174,7 +174,7 @@ Turn the smart night light mode on.
 |---------------------------|----------|-------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO light entity.      |

-### Service `light.xiaomi_miio_night_light_mode_off`  (Eyecare Smart Lamp 2 only)
+### Service `xiaomi_miio.light_night_light_mode_off`  (Eyecare Smart Lamp 2 only)

 Turn the smart night light mode off.

@ -182,7 +182,7 @@ Turn the smart night light mode off.
 |---------------------------|----------|-------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO light entity.      |

-### Service `light.xiaomi_miio_eyecare_mode_on`  (Eyecare Smart Lamp 2 only)
+### Service `xiaomi_miio.light_eyecare_mode_on`  (Eyecare Smart Lamp 2 only)

 Turn the eyecare mode on.

@ -190,7 +190,7 @@ Turn the eyecare mode on.
 |---------------------------|----------|-------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO light entity.      |

-### Service `light.xiaomi_miio_eyecare_mode_off`  (Eyecare Smart Lamp 2 only)
+### Service `xiaomi_miio.light_eyecare_mode_off`  (Eyecare Smart Lamp 2 only)

 Turn the eyecare mode off.

--- a/source/_integrations/local_file.markdown
+++ b/source/_integrations/local_file.markdown
@ -34,7 +34,7 @@ name:
  type: string
 {% endconfiguration %}

-### Service `camera.local_file_update_file_path`
+### Service `local_file.update_file_path`

 Use this service to change the file displayed by the camera.

--- a/source/_integrations/lutron_caseta.markdown
+++ b/source/_integrations/lutron_caseta.markdown
@ -8,6 +8,7 @@ ha_category:
  - Light
  - Scene
  - Switch
+  - Fan
 ha_release: 0.41
 ha_iot_class: Local Polling
 ---
@ -22,6 +23,7 @@ The currently supported Caseta devices are:
 - Wall switches as [switches](#switch)
 - Scenes as [scenes](#scene)
 - Lutron shades as [covers](#cover)
+- Lutron smart [fan](#fan) speed control

 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.

@ -104,3 +106,11 @@ For dimmable lights including wall and plug-in dimmers, see the light section on
 For more information on working with switches in Home Assistant, see the [Switches component](/integrations/switch/).

 Available services: `switch.turn_on` and `switch.turn_off`.
+
+## Fan
+
+After setup, fans will appear in Home Assistant using an `entity_id` based on the name used in the Lutron mobile app. For example, a light switch called 'Master Bathroom Vanity' will appear in Home Assistant as `fan.master_bedroom_ceiling_fan`.
+
+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`.
--- a/source/_integrations/mill.markdown
+++ b/source/_integrations/mill.markdown
@ -36,7 +36,7 @@ password:

 This platform supports a service to set the temperature for the room connected to heater in the Mill app:

-`climate.mill_set_room_temperature`
+`mill.set_room_temperature`


 | Service data attribute | Optional | Description |
--- a/source/_integrations/monoprice.markdown
+++ b/source/_integrations/monoprice.markdown
@ -52,7 +52,7 @@ sources:
  type: integer
 {% endconfiguration %}

-### Service `snapshot`
+### 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.

@ -66,7 +66,7 @@ The following attributes are stored in a snapshot:
 | ---------------------- | -------- | ----------- |
 | `entity_id` | yes | String or list of strings that point at `entity_id`s of zones.

-### Service `restore`
+### Service `monoprice.restore`

 Restore a previously taken snapshot of one or more speakers. If no `entity_id` is provided, all zones are restored.

--- a/source/_integrations/neato.markdown
+++ b/source/_integrations/neato.markdown
@ -78,11 +78,11 @@ Currently supported services are:

 And a specific Platform Service:

- `vacuum.neato_custom_cleaning`
+- `neato.custom_cleaning`

 ### Platform Services

-#### Service `vacuum.neato_custom_cleaning`
+#### Service `neato.custom_cleaning`

 Starts a custom cleaning of your house. You can set the various options like in the mobile application (mode, map usage, navigation mode, zone).

--- a/source/_integrations/nuheat.markdown
+++ b/source/_integrations/nuheat.markdown
@ -159,7 +159,7 @@ Sets the thermostat's preset mode. Without a preset mode set it run the thermost
 | `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all.
 | `hold_mode` | no | New value of hold mode.

-### Service `resume_program`
+### Service `nuheat.resume_program`

 Resumes the currently active schedule.

--- a/source/_integrations/nzbget.markdown
+++ b/source/_integrations/nzbget.markdown
@ -62,6 +62,7 @@ This component will create these sensors:
 - `nzbget_speed`: Current download rate in MB/s.
 - `nzbget_queue_size`: Remaining size to download in MB.
 - `nzbget_disk_free`: Free disk space at the storage location of NZBGet.
+- `nzbget_post_processing_jobs`: Number of Par-Jobs or Post-processing script jobs in the post-processing queue.
 - `nzbget_post_processing_paused`: Whether post processing is paused.
 - `nzbget_uptime`: NZBGet server uptime.
 - `nzbget_size`: Amount of data downloaded since server start in MB.
--- a/source/_integrations/ombi.markdown
+++ b/source/_integrations/ombi.markdown
@ -12,8 +12,12 @@ The `Ombi` integration monitors data from your [Ombi](https://ombi.io) instance.

 ## Setup

+This component needs to authenticate to your Ombi instance with either a user `password` or an `api_key`.
+
 To find your `api_key` open the Ombi web interface. Navigate to **Settings** and then to **Ombi**, you should then be able to see your `api_key`.

+If you want to use `password` authentication simply use the same `password` you normally use to login to Ombi. Alternatively, you can set up a separate local account in Ombi designated for Home Assistant. In order to do this, open the Ombi web interface. Navigate to **User Management** and then press **Add User To Ombi**. Input your desired user details and use the same details when configuring this integration.
+
 ## Configuration

 If you want to enable this sensor, add the following lines to your `configuration.yaml`:
@ -21,16 +25,12 @@ If you want to enable this sensor, add the following lines to your `configuratio
 ```yaml
 # Example configuration.yaml entry
 ombi:
-  api_key: OMBI_API_KEY
  host: OMBI_HOST
  username: OMBI_USERNAME
+  password: OMBI_PASSWORD
 ```

 {% configuration %}
-api_key:
-  description: Your Ombi API key.
-  required: true
-  type: string
 host:
  description: The hostname or IP Address Ombi is running on.
  required: true
@ -39,6 +39,14 @@ username:
  description: Your Ombi username.
  required: true
  type: string
+password:
+  description: Your Ombi password. [`password`](#password) and [`api_key`](#api_key) cannot be specified concurrently.
+  required: exclusive
+  type: string
+api_key:
+  description: Your Ombi API key. [`password`](#password) and [`api_key`](#api_key) cannot be specified concurrently.
+  required: exclusive
+  type: string
 port:
  description: The port Ombi is running on.
  required: false
@ -60,9 +68,9 @@ ssl:
 ```yaml
 # Example configuration.yaml entry
 ombi:
-  api_key: OMBI_API_KEY
  host: OMBI_HOST
  username: OMBI_USERNAME
+  api_key: OMBI_API_KEY
  port: OMBI_PORT
  urlbase: ombi/
  ssl: true
--- a/source/_integrations/opengarage.markdown
+++ b/source/_integrations/opengarage.markdown
@ -23,7 +23,10 @@ cover:
      device_key: opendoor
      name: Left Garage Door
    garage2:
-      host: 192.168.1.13
+      protocol: https
+      verify_ssl: false
+      host: garage.example.com
+      port: 443
      device_key: opendoor
      name: Right Garage Door
 ```
@ -39,6 +42,16 @@ covers:
      required: true
      type: map
      keys:
+        ssl:
+          description: Use HTTPS instead of HTTP to connect.
+          required: false
+          type: boolean
+          default: false
+        verify_ssl:
+          description: Enable or disable SSL certificate verification. Set to false if you have a self-signed SSL certificate and haven't installed the CA certificate to enable verification.
+          required: false
+          default: true
+          type: boolean
        host:
          description: IP address of device.
          required: true
@ -123,4 +136,5 @@ customize:
  sensor.garage_car_present:
    icon: mdi:car
 ```
+
 {% endraw %}
--- a/source/_integrations/opentherm_gw.markdown
+++ b/source/_integrations/opentherm_gw.markdown
@ -19,7 +19,7 @@ The following device types are currently supported within Home Assistant:
 - Climate
 - Sensor

-This integration will add a single `climate` entity and multiple `sensor` and `binary_sensor` entities to Home Assistant for each configured gateway.
+This integration will add a single `climate` entity to Home Assistant for each configured gateway. Each gateway also has a collection of `sensor` and `binary_sensor` entities, which are disabled by default. These can be enabled from the `Devices` panel in the `Configuration` page of the web interface.

 <div class='note'>
 The OpenTherm protocol is based on polling. The thermostat sends requests to the boiler at specific intervals. As a result, it may take some time for changes to propagate between Home Assistant and the thermostat.
@ -183,7 +183,7 @@ The value you provide here will be used with the GPIO `home` (5) and `away` (6)

 ## Sensors

-The following `sensor` entities will be created for each configured gateway. The `entity_id` of every sensor will have a suffix containing the `gateway_id` of the gateway to which it belongs.
+The following `sensor` entities will be created for each configured gateway. The `entity_id` of every sensor will have a suffix containing the `gateway_id` of the gateway to which it belongs. All `sensor` entities are disabled by default.
 <p class='note'>
 Not all boilers and thermostats properly support all OpenTherm features, so not all of the sensors will have useful values.
 </p>
@ -383,7 +383,7 @@ Not all boilers and thermostats properly support all OpenTherm features, so not

 ## Binary Sensors

-The following `binary_sensor` entities will be created for each configured gateway. The `entity_id` of every sensor will have a suffix containing the `gateway_id` of the gateway to which it belongs.
+The following `binary_sensor` entities will be created for each configured gateway. The `entity_id` of every sensor will have a suffix containing the `gateway_id` of the gateway to which it belongs. All `binary_sensor` entities are disabled by default.
 <p class='note'>
 Not all boilers and thermostats properly support all OpenTherm features, so not all of the sensors will have useful values.
 </p>
--- a/source/_integrations/panasonic_viera.markdown
+++ b/source/_integrations/panasonic_viera.markdown
@ -33,7 +33,7 @@ If your model is not on the list then give it a test, if everything works correc

 Some Panasonic Viera TVs allow Home Assistant to turn them on, if you specify the MAC address with `mac:`.

-Note that your TV has to reside in the same network as your home assistant instance for this platform to work.
+Note that your TV has to reside in the same network as your Home Assistant instance for this platform to work. If you have multiple network interfaces on your Home Assistant instance, you may need to specify the `broadcast_address`.

 To add a TV to your installation, add the following to your `configuration.yaml` file:

@ -58,6 +58,11 @@ mac:
  description: The MAC address of your Panasonic Viera TV, e.g., `AA:BB:CC:DD:99:1A`.
  required: false
  type: string
+broadcast_address:
+  description: The broadcast address on which to send the Wake-On-Lan packet.
+  required: false
+  default: 255.255.255.255
+  type: string
 app_power:
  description: Set to `true` if your Panasonic Viera TV supports "Turn on via App".
  required: false
--- a/source/_integrations/proxmoxve.markdown
+++ b/source/_integrations/proxmoxve.markdown
@ -0,0 +1,100 @@
+---
+title: "Proxmox VE"
+description: "Access your ProxmoxVE instance in Home Assistant."
+logo: proxmoxve.png
+ha_category:
+  - Binary Sensor
+ha_release: 0.103
+ha_iot_class: Local Polling
+---
+
+[Proxmox VE](https://www.proxmox.com/en/) is an open-source server virtualization environment. This integration allows you to poll various data from your instance.
+
+After configuring this component, the binary sensors automatically appear.
+
+## Configuration
+
+<div class='note'>
+You should have at least one VM or container entry configured, else this integration won't do anything.
+</div>
+
+To use the `proxmoxve` component, add the following config to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+proxmox:
+  - host: IP_ADDRESS
+    username: USERNAME
+    password: PASSWORD
+    nodes:
+      - node: NODE_NAME
+        vms:
+          - VM_ID
+        containers:
+          - CONTAINER_ID
+```
+
+{% configuration %}
+host:
+  description: IP address of the Proxmox VE instance.
+  required: true
+  type: string
+port:
+  description: The port number on which Proxmox VE is running.
+  required: false
+  default: 8006
+  type: integer
+verify_ssl:
+  description: Whether to do strict validation on SSL certificates.
+  required: false
+  default: true
+  type: boolean
+username:
+  description: The username used to authenticate.
+  required: true
+  type: string
+password:
+  description: The password used to authenticate.
+  required: true
+  type: string
+realm:
+  description: The authentication realm of the user.
+  required: false
+  default: pam
+  type: string
+nodes:
+  description: List of the Proxmox VE nodes to monitor.
+  required: true
+  type: map
+  keys:
+    node:
+      description: Name of the node
+      required: true
+      type: string
+    vms:
+      description: List of the QEMU VMs to monitor.
+      required: false
+      type: list
+    containers:
+      description: List of the LXC containers to monitor.
+      required: false
+      type: list
+{% endconfiguration %}
+
+Example with multiple VMs and no containers:
+
+```yaml
+proxmox:
+  - host: IP_ADDRESS
+    username: USERNAME
+    password: PASSWORD
+    nodes:
+      - node: NODE_NAME
+        vms:
+          - VM_ID_1
+          - VM_ID_2
+```
+
+## Binary Sensor
+
+The integration will automatically create a binary sensor for each tracked VM or container, the binary sensor will either be on if the VM's state is running or off if the VM's state is different.
--- a/source/_integrations/pulseaudio_loopback.markdown
+++ b/source/_integrations/pulseaudio_loopback.markdown
@ -46,7 +46,7 @@ host:
 port:
  description: The port that Pulseaudio is listening on.
  required: false
-  default: 4712
+  default: 4713
  type: integer
 buffer_size:
  description: How much data to load from Pulseaudio at once.
--- a/source/_integrations/remote.xiaomi_miio.markdown
+++ b/source/_integrations/remote.xiaomi_miio.markdown
@ -111,7 +111,7 @@ The Xiaomi IR Remote Platform currently supports two different formats for IR co

 ### Raw

-A raw command is a command learned from [`remote.xiaomi_miio_learn_command`](/integrations/remote.xiaomi_miio/#remotexiaomi_miio_learn_command).
+A raw command is a command learned from [`xiaomi_miio.remote_learn_command`](/integrations/remote.xiaomi_miio/#xiaomi_miioremote_learn_command).

 A raw command is defined as in the following example:

@ -158,7 +158,7 @@ The Xiaomi IR Remote Platform registers two services.

 Allows sending either named commands using an identifier or sending commands as one of the two types defined in [Command Types](/integrations/remote.xiaomi_miio/#command-types).

-### `remote.xiaomi_miio_learn_command`
+### `xiaomi_miio.remote_learn_command`

 Used to learn new commands.

--- a/source/_integrations/rest.markdown
+++ b/source/_integrations/rest.markdown
@ -132,6 +132,8 @@ $ curl -X GET http://192.168.1.31/temperature/
 {"temperature": 77, "id": "sensor02", "name": "livingroom", "connected": true}
 ```

+The response is expected to be a dictionary or a list with a dictionary as its 0th element.
+
 ## Examples

 In this section you find some real-life examples of how to use this sensor.
--- a/source/_integrations/rest_command.markdown
+++ b/source/_integrations/rest_command.markdown
@ -31,7 +31,7 @@ service_name:
    url:
      description: The URL (supports template) for sending request.
      required: true
-      type: [string, template]
+      type: template
    method:
      description: HTTP method to use (get, patch, post, put, or delete).
      required: false
@ -44,7 +44,7 @@ service_name:
    payload:
      description: A string/template to send with request.
      required: false
-      type: [string, template]
+      type: template
    username:
      description: The username for HTTP authentication.
      required: false
@ -83,6 +83,7 @@ rest_command:
    headers:
      authorization: !secret rest_headers_secret
      accept: 'application/json, text/html'
+      user-agent: 'Mozilla/5.0 {{ useragent }}'
    payload: '{"profile":{"status_text": "{{ status }}","status_emoji": "{{ emoji }}"}}'
    content_type:  'application/json; charset=utf-8'
    verify_ssl: true
--- a/source/_integrations/rfxtrx.markdown
+++ b/source/_integrations/rfxtrx.markdown
@ -7,33 +7,58 @@ ha_category:
 ha_release: pre 0.7
 ---

-The `rfxtrx` integration supports RFXtrx devices by [RFXCOM](http://www.rfxcom.com) which communicate in the frequency range of 433.92 MHz.
+The `rfxtrx` integration supports RFXtrx devices by [RFXCOM](http://www.rfxcom.com), which communicate in the frequency range of 433.92 MHz.

 To enable RFXtrx in your installation, add the following to your `configuration.yaml` file:

 ```yaml
-# Example configuration.yaml entry
+# Example configuration.yaml entry for local serial device
 rfxtrx:
-  device: PATH_TO_DEVICE
+  device: /dev/ttyUSB0
+```
+
+OR
+
+```yaml
+# Example configuration.yaml entry for TCP connected device using ser2net
+rfxtrx:
+  host: 192.168.0.2
+  port: 50000
 ```

 {% configuration %}
 device:
-  description: "The path to your device, e.g., `/dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Y0NJGR-if00-port0` or `/dev/ttyUSB0`."
-  required: true
+  description: "The path to your device, e.g., `/dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Y0NJGR-if00-port0` or `/dev/ttyUSB0`. Required if you are using a locally connected USB device."
+  required: false
  type: string
+host:
+  description: "The hostname the remote RFXtrx is available on if connecting via TCP. If this is set, a port is required."
+  required: false
+  type: string
+port:
+  description: "The TCP port the remote RFXtrx is available on. If this is set, a host is required."
+  required: false
+  type: integer
 debug:
-  description: If you want to receive debug output.
+  description: "If you want to receive debug output."
  required: false
  default: false
  type: boolean
 dummy:
-  description: Then you have need a connected drive to test your settings. Can be useful for debugging and testing.
+  description: "Then you need a connected drive to test your settings. Can be useful for debugging and testing."
  required: false
  default: false
  type: boolean
 {% endconfiguration %}

-Supported protocols
+## Supported protocols

-Not all protocols as advertised are enabled on initial setup of your transceiver. Enabling all protocols is not recommended either. Your 433.92 product not showing in the logs? Visit the RFXtrx website to [download RFXmgmr](http://www.rfxcom.com/epages/78165469.sf/nl_NL/?ObjectPath=/Shops/78165469/Categories/Downloads) and enable the required protocol.
+Not all protocols as advertised are enabled on the initial setup of your transceiver. Enabling all protocols is not recommended either. Your 433.92 product not showing in the logs? Visit the RFXtrx website to [download RFXmgmr](http://www.rfxcom.com/epages/78165469.sf/nl_NL/?ObjectPath=/Shops/78165469/Categories/Downloads) and enable the required protocol.
+
+### ser2net
+
+You can host your device on another computer by setting up ser2net and example configuration for ser2net looks like this and then using host/port in your home assistant config.
+
+```text
+50000:raw:0:/dev/ttyUSB0:38400 8DATABITS NONE 1STOPBIT
+```
--- a/source/_integrations/roomba.markdown
+++ b/source/_integrations/roomba.markdown
@ -58,6 +58,11 @@ continuous:
  required: false
  type: boolean
  default: true
+delay:
+  description: Custom connection delay (in seconds) for periodic mode
+  required: false
+  type: integer
+  default: 1
 {% endconfiguration %}

 <div class='note'>
--- a/source/_integrations/samsungtv.markdown
+++ b/source/_integrations/samsungtv.markdown
@ -48,6 +48,11 @@ mac:
  description: "The MAC address of the Samsung Smart TV, e.g., `00:11:22:33:44:55:66`. Required for power on support via wake on lan."
  required: false
  type: string
+broadcast_address:
+  description: The broadcast address on which to send the Wake-On-Lan packet.
+  required: false
+  default: 255.255.255.255
+  type: string
 {% endconfiguration %}

 Currently known supported models:
--- a/source/_integrations/scene.markdown
+++ b/source/_integrations/scene.markdown
@ -96,12 +96,12 @@ Whenever you make a change to your scene configuration, you can call the `scene.

 Create a new scene without having to configure it by calling the `scene.create` service. This scene will be discarded after reloading the configuration.

-You need to pass a `scene_id` in lowercase and with underscores instead of spaces. You also need to specify the entities in the same format as when configuring the scene.
+You need to pass a `scene_id` in lowercase and with underscores instead of spaces. You also may want to specify the entities in the same format as when configuring the scene. You can also take a snapshot of the current state by using the `snapshot_entities` parameter. In this case, you have to specify the `entity_id` of all entities you want to take a snapshot of. `entities` and `snapshot_entities` can be combined but you have to use at least one of them.

 If the scene was previously created by `scene.create`, it will be overwritten. If the scene was created by YAML, nothing happens but a warning in your log files.

 ```yaml
-# Example automation
+# Example automation using entities
 automation:
  trigger:
    platform: homeassistant
@ -119,3 +119,41 @@ automation:
          state: on
          source: HDMI 1
 ```
+
+The following example turns off some entities as soon as a window opens. The states of the entities are restored after the window is closed again.
+
+```yaml
+# Example automation using snapshot
+- alias: Window opened
+  trigger:
+  - platform: state
+    entity_id: binary_sensor.window
+    from: 'off'
+    to: 'on'
+  condition: []
+  action:
+  - service: scene.create
+    data:
+      scene_id: before
+      snapshot_entities:
+      - climate.ecobee
+      - light.ceiling_lights
+  - service: light.turn_off
+    data:
+      entity_id: light.ceiling_lights
+  - service: climate.set_hvac_mode
+    data:
+      entity_id: climate.ecobee
+      hvac_mode: 'off'
+- alias: Window closed
+  trigger:
+  - platform: state
+    entity_id: binary_sensor.window
+    from: 'on'
+    to: 'off'
+  condition: []
+  action:
+  - service: scene.turn_on
+    data:
+      entity_id: scene.before
+```
--- a/source/_integrations/season.markdown
+++ b/source/_integrations/season.markdown
@ -37,4 +37,9 @@ type:
  required: false
  type: string
  default: astronomical
+name:
+  description: "An identifier for the sensor in the frontend."
+  required: false
+  type: string
+  default: Season
 {% endconfiguration %}
--- a/source/_integrations/simplisafe.markdown
+++ b/source/_integrations/simplisafe.markdown
@ -5,13 +5,15 @@ logo: simplisafe.png
 ha_release: 0.81
 ha_category:
  - Alarm
+  - Lock
 ---

 The `simplisafe` integration integrates SimpliSafe home security (V2 and V3) systems into Home Assistant. Multiple SimpliSafe accounts can be accommodated.

 There is currently support for the following device types within Home Assistant:

- Alarm
+- **Alarm Control Panel**: reports on the current alarm status and can be used to arm and disarm the system.
+- **Lock**: Reports on `Door Locks` and can be used to lock and unlock a lock.

 ## Configuration

@ -52,15 +54,54 @@ Remove a SimpliSafe PIN (by label or PIN value).

 | Service Data Attribute    | Optional | Description                                 |
 |---------------------------|----------|---------------------------------------------|
-| `system_id`                |      no  | The ID of the system to remove the PIN from |
+| `system_id`                 |      no  | The ID of a SimpliSafe system               | 
 | `label_or_pin`              |      no  | The PIN label or value to remove            |

+### `simplisafe.set_alarm_duration`
+
+Set the duration (in seconds) of an active alarm.
+
+| Service Data Attribute    | Optional | Description                                 |
+|---------------------------|----------|---------------------------------------------|
+| `system_id`                 |      no  | The ID of a SimpliSafe system               | 
+| `duaration`                 |      no  | The number of seconds to sound the alarm    |
+
+### `simplisafe.set_delay`
+
+Set a duration for how long the base station should delay when transitioning between states.
+
+| Service Data Attribute    | Optional | Description                                 |
+|---------------------------|----------|---------------------------------------------|
+| `system_id`                 |      no  | The ID of a SimpliSafe system               | 
+| `arrival_state`             |      no  | The target "arrival" state (away, home)     | 
+| `transition`                |      no  | The system state transition to affect (entry, exit)               | 
+| `seconds`                   |      no  | The number of seconds to delay              |
+
+### `simplisafe.set_light`
+
+Turn the base station light on/off.
+
+| Service Data Attribute    | Optional | Description                                 |
+|---------------------------|----------|---------------------------------------------|
+| `system_id`                 |      no  | The ID of a SimpliSafe system               | 
+| `light_state`               |      no  | True for on, False for off                  |
+
 ### `simplisafe.set_pin`

 Set a SimpliSafe PIN.

 | Service Data Attribute    | Optional | Description                                 |
 |---------------------------|----------|---------------------------------------------|
-| `system_id`                |      no  | The ID of the system to remove the PIN from |
+| `system_id`                 |      no  | The ID of the system to remove the PIN from |
 | `label`                     |      no  | The label to show in the SimpliSafe UI      |
 | `pin`                       |      no  | The PIN value to use                        |
+
+### `simplisafe.set_volume_property`
+
+Set a level for one of the base station's various volumes.
+
+| Service Data Attribute    | Optional | Description                                 |
+|---------------------------|----------|---------------------------------------------|
+| `system_id`                 |      no  | The ID of a SimpliSafe system               | 
+| `volume_property`           |      no  | The volume property to set (alarm, chime, voice_prompt)               | 
+| `volume`                    |      no  | A volume (off, low, medium, high)           |
--- a/source/_integrations/songpal.markdown
+++ b/source/_integrations/songpal.markdown
@ -49,7 +49,7 @@ See [python-songpal's documentation](https://github.com/rytilahti/python-songpal

 In addition to the general [media player services](/integrations/media_player/#services), the following services are provided:

-### Service `media_player/songpal_set_sound_setting`
+### Service `songpal/set_sound_setting`

 For a list of available settings and their values use [`songpal sound`](https://github.com/rytilahti/python-songpal#sound-settings) command.

--- a/source/_integrations/soundtouch.markdown
+++ b/source/_integrations/soundtouch.markdown
@ -83,7 +83,7 @@ You can use TTS services like [Google Text-to-Speech](/integrations/google_trans

 A workaround if you want to publish your Home Assistant installation on Internet in SSL is to configure an HTTPS Web Server as a reverse proxy ([nginx](/docs/ecosystem/nginx/) for example) and let your Home Assistant configuration in HTTP on your local network. The Soundtouch devices will be available to access the TTS files in HTTP in local and your configuration will be in HTTPS on the Internet.

-### Service `soundtouch_play_everywhere`
+### Service `play_everywhere`

 Create a multi-room (zone) from a master and play same content on all other
 devices (slaves)
@ -92,7 +92,7 @@ Create a multi-room (zone) from a master and play same content on all other
 | ---------------------- | -------- | ----------- |
 | `master` | no | `entity_id` of the master device

-### Service `soundtouch_create_zone`
+### Service `create_zone`

 Create a multi-room (zone) from a master and play on selected slaves

@ -101,7 +101,7 @@ Create a multi-room (zone) from a master and play on selected slaves
 | `master` | no | `entity_id` of the master device|
 | `slaves` | no | List of slaves `entity_id`      |

-### Service `soundtouch_add_zone_slave`
+### Service `add_zone_slave`

 Add slave(s) to an existing zone

@ -110,7 +110,7 @@ Add slave(s) to an existing zone
 | `master` | no | `entity_id` of the master device |
 | `slaves` | no | List of slaves `entity_id` to add|

-### Service `soundtouch_remove_zone_slave`
+### Service `remove_zone_slave`

 Remove slave(s) from an existing zone.

--- a/source/_integrations/squeezebox.markdown
+++ b/source/_integrations/squeezebox.markdown
@ -59,7 +59,7 @@ transporter_toslink:
        media_content_type: "music"
 ```

-### Service `squeezebox_call_method`
+### Service `call_method`

 Call a custom Squeezebox JSONRPC API.

--- a/source/_integrations/starline.markdown
+++ b/source/_integrations/starline.markdown
@ -0,0 +1,62 @@
+---
+title: "StarLine"
+description: "Instructions on how to setup your StarLine account with Home Assistant."
+logo: starline.png
+ha_category:
+  - Car
+  - Binary Sensor
+  - Presence Detection
+  - Lock
+  - Sensor
+  - Switch
+ha_release: 0.103
+ha_iot_class: Cloud Polling
+ha_config_flow: true
+---
+
+The `starline` integration lets you retrieve data of your StarLine security system from the StarLine portal. You will need a working StarLine account.
+
+This integration provides the following platforms:
+
+- Binary Sensors: Hand brake, hood, trunk, alarm status and doors lock state.
+- Device tracker: The location of your car.
+- Lock: Control the lock of your car.
+- Sensors: Battery level, SIM card balance, GSM signal level, interior temperature and engine temperature.
+- Switches: Start/stop engine, heater (webasto), additional channel and sound the horn.
+- Services: Update the state, set update frequency. More details can be found [here](#services).
+
+## Configuration
+
+1. Create a new application in the [StarLine developer profile](https://my.starline.ru/developer).
+2. Open the integrations page and add the StarLine integration.
+3. Fill in your application ID, secret, login and password.
+
+After adding the integration, you can configure the API update interval on the integration page.
+
+<div class='note'>
+
+You can make up to 1000 API calls per day, which means you could make one approximately every 86 seconds.
+By default, the state of integration will be updated every 3 minutes, making 480 calls per day.
+It is not recommended to set an update interval of less than 90 seconds.
+
+</div>
+
+## Services
+
+### Update the state
+
+The service `starline.update_state` fetches the last state of the device from the StarLine server.
+
+This service does not require any attributes.
+
+### Set scan interval
+
+The service `starline.set_scan_interval` sets update frequency for entities.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `scan_interval` | no | Update frequency in seconds.
+
+## Disclaimer
+
+This software is not affiliated with or endorsed by StarLine Company.
--- a/source/_integrations/switch.mysensors.markdown
+++ b/source/_integrations/switch.mysensors.markdown
@ -54,7 +54,7 @@ The MySensors switch platform exposes a service to change an IR code attribute f

 | Service | Description |
 | ------- | ----------- |
-| mysensors_send_ir_code | Set an IR code as a state attribute for a MySensors IR device switch and turn the switch on.|
+| mysensors.send_ir_code | Set an IR code as a state attribute for a MySensors IR device switch and turn the switch on.|

 The service can be used as part of an automation script. For example:

@ -66,7 +66,7 @@ automation:
      platform: time
      at: '5:30:00'
    action:
-      service: switch.mysensors_send_ir_code
+      service: mysensors.send_ir_code
      entity_id: switch.hvac_1_1
      data:
        V_IR_SEND: '0xC284'  # the IR code to send
@ -76,7 +76,7 @@ automation:
      platform: time
      at: '0:30:00'
    action:
-      service: switch.mysensors_send_ir_code
+      service: mysensors.send_ir_code
      entity_id: switch.hvac_1_1
      data:
        V_IR_SEND: '0xC288'  # the IR code to send
--- a/source/_integrations/switch.xiaomi_miio.markdown
+++ b/source/_integrations/switch.xiaomi_miio.markdown
@ -88,7 +88,7 @@ model:

 ## Platform Services

-### Service `switch.xiaomi_miio_set_wifi_led_on` (Power Strip only)
+### Service `xiaomi_miio.switch_set_wifi_led_on` (Power Strip only)

 Turn the wifi led on.

@ -96,7 +96,7 @@ Turn the wifi led on.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO switch entity.       |

-### Service `switch.xiaomi_miio_set_wifi_led_off` (Power Strip only)
+### Service `xiaomi_miio.switch_set_wifi_led_off` (Power Strip only)

 Turn the wifi led off.

@ -104,7 +104,7 @@ Turn the wifi led off.
 |---------------------------|----------|---------------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO switch entity.       |

-### Service `switch.xiaomi_miio_set_power_price` (Power Strip)
+### Service `xiaomi_miio.switch_set_power_price` (Power Strip)

 Set the power price.

@ -113,7 +113,7 @@ Set the power price.
 | `entity_id`               |       no | Only act on a specific Xiaomi miIO switch entity.       |
 | `price`                   |       no | Power price, between 0 and 999.                         |

-### Service `switch.xiaomi_miio_set_power_mode` (Power Strip V1 only)
+### Service `xiaomi_miio.switch_set_power_mode` (Power Strip V1 only)

 Set the power mode.

--- a/source/_integrations/todoist.markdown
+++ b/source/_integrations/todoist.markdown
@ -121,7 +121,7 @@ Home Assistant does its best to [determine what task in each project is "most" i

 ### Services

-Todoist also comes with access to a service, `calendar.todoist_new_task`. This service can be used to create a new Todoist task. You can specify labels and a project, or you can leave them blank, and the task will go to your "Inbox" project.
+Todoist also comes with access to a service, `todoist.new_task`. This service can be used to create a new Todoist task. You can specify labels and a project, or you can leave them blank, and the task will go to your "Inbox" project.

 Here are two example JSON payloads resulting in the same task:

--- a/source/_integrations/transmission.markdown
+++ b/source/_integrations/transmission.markdown
@ -119,8 +119,10 @@ Adds a new torrent to download. It can either be a URL (http, https or ftp), mag

 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
+| `name`    | no | Name of the configured instance
 | `torrent` | no | Torrent to download

+
 ## Templating

 ### Sensor `started_torrents`
--- a/source/_integrations/vacuum.xiaomi_miio.markdown
+++ b/source/_integrations/vacuum.xiaomi_miio.markdown
@ -54,15 +54,15 @@ name:

 ## Platform Services

-In addition to all of the services provided by the `vacuum` integration (`start`, `pause`, `stop`, `return_to_base`, `locate`, `set_fan_speed` and `send_command`), the `xiaomi` platform introduces specific services to access the remote control mode of the robot. These are:
+In addition to all of the services provided by the `vacuum` integration (`start`, `pause`, `stop`, `return_to_base`, `locate`, `set_fan_speed` and `send_command`), the `xiaomi_miio` platform introduces specific services to access the remote control mode of the robot. These are:

- `xiaomi_remote_control_start`
- `xiaomi_remote_control_stop`
- `xiaomi_remote_control_move`
- `xiaomi_remote_control_move_step`
- `xiaomi_clean_zone`
+- `xiaomi_miio.vacuum_remote_control_start`
+- `xiaomi_miio.vacuum_remote_control_stop`
+- `xiaomi_miio.vacuum_remote_control_move`
+- `xiaomi_miio.vacuum_remote_control_move_step`
+- `xiaomi_miio.vacuum_clean_zone`

-### Service `vacuum.xiaomi_remote_control_start`
+### Service `xiaomi_miio.vacuum_remote_control_start`

 Start the remote control mode of the robot. You can then move it with `remote_control_move`; when done, call `remote_control_stop`.

@ -70,7 +70,7 @@ Start the remote control mode of the robot. You can then move it with `remote_co
 |---------------------------|----------|---------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific robot                      |

-### Service `vacuum.xiaomi_remote_control_stop`
+### Service `xiaomi_miio.vacuum_remote_control_stop`

 Exit the remote control mode of the robot.

@ -78,7 +78,7 @@ Exit the remote control mode of the robot.
 |---------------------------|----------|---------------------------------------------------|
 | `entity_id`               |       no | Only act on a specific robot                      |

-### Service `vacuum.xiaomi_remote_control_move`
+### Service `xiaomi_miio.vacuum_remote_control_move`

 Remote control the robot. Please ensure you first set it in remote control mode with `remote_control_start`.

@ -89,7 +89,7 @@ Remote control the robot. Please ensure you first set it in remote control mode
 | `rotation`                |       no | Rotation: between -179 degrees and 179 degrees            |
 | `duration`                |       no | The number of milliseconds that the robot should move for |

-### Service `vacuum.xiaomi_remote_control_move_step`
+### Service `xiaomi_miio.vacuum_remote_control_move_step`

 Enter remote control mode, make one move, stop, and exit remote control mode.

@ -100,7 +100,7 @@ Enter remote control mode, make one move, stop, and exit remote control mode.
 | `rotation`                |       no | Rotation: between -179 degrees and 179 degrees            |
 | `duration`                |       no | The number of milliseconds that the robot should move for |

-### Service `vacuum.xiaomi_clean_zone`
+### Service `xiaomi_miio.vacuum_clean_zone`

 Start the cleaning operation in the areas selected for the number of repeats indicated.

@ -110,7 +110,7 @@ Start the cleaning operation in the areas selected for the number of repeats ind
 | `zone`                    |       no | List of zones. Each zone is an array of 4 integer value. Example: [[23510,25311,25110,26361]] |
 | `repeats`                 |       no | Number of cleaning repeats for each zone between 1 and 3. |

-Example of `vacuum.xiaomi_clean_zone` use:
+Example of `xiaomi_miio.vacuum_clean_zone` use:

 Inline array:
 {% raw %}
@ -122,7 +122,7 @@ automation:
      platform: homeassistant
    condition: []
    action:
-    - service: vacuum.xiaomi_clean_zone
+    - service: xiaomi_miio.vacuum_clean_zone
      data_template:
        entity_id: vacuum.xiaomi_vacuum
        repeats: '{{states('input_number.vacuum_passes')|int}}'
@ -140,7 +140,7 @@ automation:
      platform: homeassistant
    condition: []
    action:
-    - service: vacuum.xiaomi_clean_zone
+    - service: xiaomi_miio.vacuum_clean_zone
      data_template:
        entity_id: vacuum.xiaomi_vacuum
        repeats: '{{states('input_number.vacuum_passes')|int}}'
@ -159,7 +159,7 @@ automation:
      platform: homeassistant
    condition: []
    action:
-    - service: vacuum.xiaomi_clean_zone
+    - service: xiaomi_miio.vacuum_clean_zone
      data:
        entity_id: vacuum.xiaomi_vacuum
        repeats: 1
--- a/source/_integrations/versasense.markdown
+++ b/source/_integrations/versasense.markdown
@ -0,0 +1,43 @@
+---
+title: "VersaSense"
+description: "Integrate your VersaSense MicroPnP devices."
+date: 2019-11-19 14:00
+logo: versasense.png
+ha_release: 0.103
+ha_category:
+  - Hub
+  - Sensor
+  - Switch
+ha_iot_class: Local Polling
+---
+
+The `VersaSense` integration supports the VersaSense Edge Gateway. The gateway is able to control hubs and their peripherals (sensors and actuators) in the mesh network.
+
+## Configuration
+
+```yaml
+# Example configuration.yaml entry
+versasense:
+  host: GATEWAY_URI
+```
+
+{% configuration %}
+host:
+  description: "The IP address or hostname of the VersaSense gateway. Including *protocol* and *port*, e.g., https://gateway.versasense.com:8889"
+  required: true
+  type: string
+{% endconfiguration %}
+
+## Supported hardware
+
+All Versasense gateways with software version >= 1.0.2.10
+
+The integration is tested with following peripherals and devices:
+
+- S03 S04: Temperature and Humidity sensor
+- S06: Barometric Pressure sensor
+- S10: Light sensor
+- S17: Object detection sensor
+- S19: Buzzer actuator
+- Pxx: SmartMesh IP Hub
+- M01: SmartMesh Edge Gateway
--- a/source/_integrations/version.markdown
+++ b/source/_integrations/version.markdown
@ -46,7 +46,7 @@ source:

 ### Supported images for Hass.io and Docker

-`default`, `qemux86`, `qemux86-64`, `qemuarm`, `qemuarm-64`, `intel-nuc`, `raspberrypi`, `raspberrypi2`, `raspberrypi3`, `raspberrypi3-64`, `tinker`, `odroid-c2`, `odroid-xu`
+`default`, `qemux86`, `qemux86-64`, `qemuarm`, `qemuarm-64`, `intel-nuc`, `raspberrypi`, `raspberrypi2`, `raspberrypi3`, `raspberrypi3-64`, `raspberrypi4`, `raspberrypi4-64`, `tinker`, `odroid-c2`, `odroid-xu`

 ## Alternatives for showing local version

--- a/source/_integrations/vivotek.markdown
+++ b/source/_integrations/vivotek.markdown
@ -43,6 +43,11 @@ password:
  description: The password for accessing your camera.
  required: true
  type: string
+security_level:
+  description: The security level of the user accessing your camera. This could be `admin` or `viewer`.
+  required: false
+  default: admin
+  type: string
 ssl:
  description: Enable or disable SSL. Set to false to use an HTTP-only camera.
  required: false
@ -76,6 +81,7 @@ camera:
    ssl: true
    username: !secret fd_camera_username
    password: !secret fd_camera_pwd
+    security_level: admin
    verify_ssl: false
    framerate: 5
    stream_path: live2.sdp
--- a/source/_integrations/wake_on_lan.markdown
+++ b/source/_integrations/wake_on_lan.markdown
@ -61,12 +61,12 @@ To enable this switch in your installation, add the following to your `configura
 # Example configuration.yaml entry
 switch:
  - platform: wake_on_lan
-    mac_address: "00-01-02-03-04-05"
+    mac: "00-01-02-03-04-05"
 ```

 {% configuration %}
-mac_address:
-  description: MAC address to send the wake up command to.
+mac:
+  description: The MAC address to send the wake up command to.
  required: true
  type: string
 name:
--- a/source/_integrations/waze_travel_time.markdown
+++ b/source/_integrations/waze_travel_time.markdown
@ -64,8 +64,25 @@ vehicle_type:
  description: "Set the vehicle type for the sensor: car, taxi, or motorcycle, otherwise the default is car."
  required: false
  type: string
+avoid_ferries:
+  description: "If this is set to true, Waze will avoid ferries on your route."
+  required: false
+  type: boolean
+  default: false
+avoid_toll_roads:
+  description: "If this is set to true, Waze will avoid toll roads on your route."
+  required: false
+  type: boolean
+  default: false
+avoid_subscription_roads:
+  description: "If this is set to true, Waze will avoid roads needing a vignette / subscription on your route."
+  required: false
+  type: boolean
+  default: false
 {% endconfiguration %}

+When using the `avoid_toll_roads`, `avoid_subscription_roads` and `avoid_ferries` options be aware that Waze will sometimes still route you over toll roads or ferries if a valid vignette/subscription is assumed. Default behaviour is that Waze will route you over roads having subscription options, so best is to set both `avoid_toll_roads` and `avoid_subscription_roads` or `avoid_ferries` if needed and experiment to ensure the desired outcome. 
+
 ## Example using dynamic destination

 Using the flexible option to set a sensor value to the `destination`, you can setup a single Waze integration that will calculate travel time to multiple optional locations on demand.
@ -118,6 +135,15 @@ sensor:
    region: 'US'
    units: imperial    # 'metric' for Metric, 'imperial' for Imperial
    vehicle_type: motorcycle  # vehicle type used for routing
+  
+  # Avoiding toll, subscription
+  - platform: waze_travel_time
+    name: Westerscheldetunnel
+    origin: 51.330436, 3.802043
+    destination: 51.445677, 3.749929
+    region: 'EU'
+    avoid_toll_roads: true
+    avoid_subscription_roads: true  
 ```
 {% endraw %}

--- a/source/_integrations/wemo.markdown
+++ b/source/_integrations/wemo.markdown
@ -101,5 +101,5 @@ There are several services which can be used for automations and control of the
 | `toggle` | Calling this service will toggle the humidifier between on and off states.
 | `turn_off` | Calling this service will turn the humidifier off (entity_id is required).
 | `turn_on` | Calling this service will turn the humidifier on and set the speed to the last used speed (defaults to medium, entity_id is required).
-| `wemo_set_humidity` | Calling this service will set the desired relative humidity setting on the device (entity_id is a required list of 1 or more entities to set humidity on, and target_humidity is a required float value between 0 and 100 (this value will be rounded down and mapped to one of the valid desired humidity settings of 45, 50, 55, 60, or 100 that are supported by the WeMo humidifier)).
-| `wemo_reset_filter_life` | Calling this service will reset the humdifier's filter life back to 100% (entity_id is a required list of 1 or more entities to reset the filter life on). Call this service when you change the filter on your humidifier.
+| `wemo.set_humidity` | Calling this service will set the desired relative humidity setting on the device (entity_id is a required list of 1 or more entities to set humidity on, and target_humidity is a required float value between 0 and 100 (this value will be rounded down and mapped to one of the valid desired humidity settings of 45, 50, 55, 60, or 100 that are supported by the WeMo humidifier)).
+| `wemo.reset_filter_life` | Calling this service will reset the humdifier's filter life back to 100% (entity_id is a required list of 1 or more entities to reset the filter life on). Call this service when you change the filter on your humidifier.
--- a/source/_integrations/wink.markdown
+++ b/source/_integrations/wink.markdown
@ -501,9 +501,9 @@ The requirement is that you have setup [Wink](/integrations/wink/) from above.
 The following services have only been confirmed on Schlage locks.
 </div>

-### Service `wink_set_lock_alarm_mode`
+### Service `set_lock_alarm_mode`

-You can use the service wink/wink_set_lock_alarm_mode to set the alarm mode of your lock.
+You can use the service wink/set_lock_alarm_mode to set the alarm mode of your lock.

 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
@ -516,14 +516,14 @@ Example:
 script:
  set_locks_to_tamper:
    sequence:
-      - service: wink.wink_set_lock_alarm_mode
+      - service: wink.set_lock_alarm_mode
        data:
          mode: "tamper"
 ```

-### Service `wink_set_lock_alarm_sensitivity`
+### Service `set_lock_alarm_sensitivity`

-You can use the service wink/wink_set_lock_alarm_sensitivity to set the alarm sensitivity of your lock.
+You can use the service wink/set_lock_alarm_sensitivity to set the alarm sensitivity of your lock.

 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
@ -536,14 +536,14 @@ Example:
 script:
  set_locks_to_high_sensitivity:
    sequence:
-      - service: wink.wink_set_lock_alarm_sensitivity
+      - service: wink.set_lock_alarm_sensitivity
        data:
          sensitivity: "high"
 ```

-### Service `wink_set_lock_alarm_state`
+### Service `set_lock_alarm_state`

-You can use the service wink/wink_set_lock_alarm_state to set the alarm state of your lock.
+You can use the service wink/set_lock_alarm_state to set the alarm state of your lock.

 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
@ -556,14 +556,14 @@ Example:
 script:
  disable_all_locks_alarm:
    sequence:
-      - service: wink.wink_set_lock_alarm_state
+      - service: wink.set_lock_alarm_state
        data:
          enabled: false
 ```

-### Service `wink_set_lock_beeper_state`
+### Service `set_lock_beeper_state`

-You can use the service wink/wink_set_lock_beeper_state to set the beeper state of your lock.
+You can use the service wink/set_lock_beeper_state to set the beeper state of your lock.

 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
@ -576,14 +576,14 @@ Example:
 script:
  disable_all_locks_beepers:
    sequence:
-      - service: wink.wink_set_lock_beeper_state
+      - service: wink.set_lock_beeper_state
        data:
          enabled: false
 ```

-### Service `wink_set_lock_vacation_mode`
+### Service `set_lock_vacation_mode`

-You can use the service wink/wink_set_lock_vacation_mode to set the vacation mode of your lock.
+You can use the service wink/set_lock_vacation_mode to set the vacation mode of your lock.

 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
@ -596,14 +596,14 @@ Example:
 script:
  enabled_vacation_mode_on_all_locks:
    sequence:
-      - service: wink.wink_set_lock_vacation_mode
+      - service: wink.set_lock_vacation_mode
        data:
          enabled: false
 ```

-### Service `wink_add_new_lock_key_code`
+### Service `add_new_lock_key_code`

-You can use the service wink/wink_add_new_lock_key_code to add a new user code to your Wink lock.
+You can use the service wink/add_new_lock_key_code to add a new user code to your Wink lock.

 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
--- a/source/_integrations/yamaha.markdown
+++ b/source/_integrations/yamaha.markdown
@ -127,7 +127,7 @@ script:

 ```

-### Service `yamaha_enable_output`
+### Service `enable_output`

 Enable or disable an output port (HDMI) on the receiver.

--- a/source/_lovelace/entities.markdown
+++ b/source/_lovelace/entities.markdown
@ -61,7 +61,7 @@ image:
  type: string
 secondary_info:
  required: false
-  description: "Show additional info. Values: `entity-id`, `last-changed`."
+  description: "Show additional info. Values: `entity-id`, `last-changed`, `last-triggered' (only for automations and scripts)."
  type: string
 format:
  required: false
--- a/source/_posts/2019-12-11-release-103.markdown
+++ b/source/_posts/2019-12-11-release-103.markdown
--- a/source/images/blog/2019-12-0.103/automation-actions.png
+++ b/source/images/blog/2019-12-0.103/automation-actions.png
--- a/source/images/blog/2019-12-0.103/automation-yaml.png
+++ b/source/images/blog/2019-12-0.103/automation-yaml.png
--- a/source/images/blog/2019-12-0.103/components.png
+++ b/source/images/blog/2019-12-0.103/components.png
--- a/source/images/blog/2019-12-0.103/natural-language-area.png
+++ b/source/images/blog/2019-12-0.103/natural-language-area.png
--- a/source/images/integrations/geonetnz_volcano/map.png
+++ b/source/images/integrations/geonetnz_volcano/map.png
--- a/source/images/integrations/geonetnz_volcano/sensor.png
+++ b/source/images/integrations/geonetnz_volcano/sensor.png
--- a/source/images/supported_brands/aten.png
+++ b/source/images/supported_brands/aten.png
--- a/source/images/supported_brands/flume.jpg
+++ b/source/images/supported_brands/flume.jpg
--- a/source/images/supported_brands/hisense.png
+++ b/source/images/supported_brands/hisense.png
--- a/source/images/supported_brands/proxmoxve.png
+++ b/source/images/supported_brands/proxmoxve.png
--- a/source/images/supported_brands/starline.png
+++ b/source/images/supported_brands/starline.png
--- a/source/images/supported_brands/versasense.png
+++ b/source/images/supported_brands/versasense.png