Merge branch 'current' into next

.textlintrc.json

@@ -303,6 +303,7 @@
         ["colour", "color"],
         ["config\\b", "configuration"],
         ["DarkSky", "Dark Sky"],
+        ["docs\\b", "documentation"],
         ["e\\.g\\.", "e.g.,"],
         ["end ?to ?end", "end-to-end"],
         ["FRITZ!? ?Box", "FRITZ!Box"],

source/_docs/asterisk_mbox.markdown

@@ -92,7 +92,7 @@ Before beginning make sure that you have the following:
    Type=simple
    User=asterisk
    Group=asterisk
-   ExecStart=/usr/local/bin/asterisk_mbox_server -cfg /etc/asterisk/asterisk_mbox.ini
+   ExecStart=/usr/local/bin/asterisk_mbox_server --cfg /etc/asterisk/asterisk_mbox.ini
    Restart=on-failure
 
    [Install]

source/_docs/autostart/systemd.markdown

@@ -77,24 +77,24 @@ WantedBy=multi-user.target
 You need to reload `systemd` to make the daemon aware of the new configuration.
 
 ```bash
-$ sudo systemctl --system daemon-reload
+sudo systemctl --system daemon-reload
 ```
 
 To have Home Assistant start automatically at boot, enable the service.
 
 ```bash
-$ sudo systemctl enable home-assistant@YOUR_USER
+sudo systemctl enable home-assistant@YOUR_USER
 ```
 
 To disable the automatic start, use this command.
 
 ```bash
-$ sudo systemctl disable home-assistant@YOUR_USER
+sudo systemctl disable home-assistant@YOUR_USER
 ```
 
 To start Home Assistant now, use this command.
 ```bash
-$ sudo systemctl start home-assistant@YOUR_USER
+sudo systemctl start home-assistant@YOUR_USER
 ```
 
 You can also substitute the `start` above with `stop` to stop Home Assistant, `restart` to restart Home Assistant, and 'status' to see a brief status report as seen below.
@@ -114,18 +114,18 @@ $ sudo systemctl status home-assistant@YOUR_USER
 To get Home Assistant's logging output, simple use `journalctl`.
 
 ```bash
-$ sudo journalctl -f -u home-assistant@YOUR_USER
+sudo journalctl -f -u home-assistant@YOUR_USER
 ```
 
 Because the log can scroll quite quickly, you can select to view only the error lines:
 ```bash
-$ sudo journalctl -f -u home-assistant@YOUR_USER | grep -i 'error'
+sudo journalctl -f -u home-assistant@YOUR_USER | grep -i 'error'
 ```
 
 When working on Home Assistant, you can easily restart the system and then watch the log output by combining the above commands using `&&`
 
 ```bash
-$ sudo systemctl restart home-assistant@YOUR_USER && sudo journalctl -f -u home-assistant@YOUR_USER
+sudo systemctl restart home-assistant@YOUR_USER && sudo journalctl -f -u home-assistant@YOUR_USER
 ```
 
 ### Automatically restarting Home Assistant on failure

source/_docs/installation.markdown

@@ -47,7 +47,7 @@ These install options are fully supported by Home Assistant's documentation. For
 
 <div class='note'>
 
-The only installation methods that allow you to use Home Assistant Add-ons is using the Home Assistant image and [manual Supervised installer](/hassio/installation/#alternative-install-on-a-generic-linux-host). All other methods only install the base Home Assistant packages, however the software from the add-ons may still usually be installed manually like any other program.
+The only installation methods that allow you to use Home Assistant Add-ons is using the Home Assistant image and [manual Supervised installer](/hassio/installation/#alternative-install-home-assistant-supervised-on-a-generic-linux-host). All other methods only install the base Home Assistant packages, however the software from the add-ons may still usually be installed manually like any other program.
 
 </div>
 
@@ -112,7 +112,7 @@ These guides are provided as-is. Some of these install methods are more limited
     </div>
     <div class='title'>FreeNAS</div>
   </a>
-  <a class='option-card' href='/hassio/installation/#alternative-install-on-a-generic-linux-host'>
+  <a class='option-card' href='/hassio/installation/#alternative-install-home-assistant-supervised-on-a-generic-linux-host'>
     <div class='img-container'>
       <img src='https://brands.home-assistant.io/homeassistant/icon.png' />
     </div>

source/_docs/installation/docker.markdown

@@ -44,7 +44,7 @@ If you wish to browse directly to `http://localhost:8123` from your macOS host,
 docker run --init -d --name="home-assistant" -e "TZ=America/Los_Angeles" -v /PATH_TO_YOUR_CONFIG:/config -p 8123:8123 homeassistant/home-assistant:stable
 ```
 
-Alternatively, `docker-compose` works with any recent release of `docker-ce` on macOS. Note that (further down this page) we provide an example `docker-compose.yml` however it differs from the `docker run` example above. To make the .yml directives match, you would need to make _two_ changes: first add the equivalent `ports:` directive, then _remove_ the `network_mode: host` section. This is because `Port mapping is incompatible with network_mode: host:`. More details can be found at [Docker networking docs](https://docs.docker.com/network/). Note also the `/dev/tty*` device name used by your Arduino etc. devices will differ from the Linux example, so the compose `mount:` may require updates.
+Alternatively, `docker-compose` works with any recent release of `docker-ce` on macOS. Note that (further down this page) we provide an example `docker-compose.yml` however it differs from the `docker run` example above. To make the .yml directives match, you would need to make _two_ changes: first add the equivalent `ports:` directive, then _remove_ the `network_mode: host` section. This is because `Port mapping is incompatible with network_mode: host:`. More details can be found at [Docker networking documentation](https://docs.docker.com/network/). Note also the `/dev/tty*` device name used by your Arduino etc. devices will differ from the Linux example, so the compose `mount:` may require updates.
 
 ### Windows
 

source/_docs/installation/virtualenv.markdown

@@ -98,7 +98,7 @@ pip3 install --upgrade git+git://github.com/home-assistant/home-assistant.git@de
 
 - In the future, if you want to start Home Assistant manually again, follow step 2, 3 and 5.
 - It's recommended to run Home Assistant as a dedicated user.
-- If you want Home Assistant to automatically start at boot, check the [autostart docs](/docs/autostart/)
+- If you want Home Assistant to automatically start at boot, check the [autostart documentation](/docs/autostart/)
 
 <div class='info'>
  

source/_docs/tools/credstash.markdown

@@ -5,7 +5,7 @@ description: "Script to store credentials securely in AWS"
 
 Using [Credstash](https://github.com/fugue/credstash) is an alternative way to `secrets.yaml`. They can be managed from the command line via the credstash script.
 
-Before using credstash, you need to set up AWS credentials either via the `aws` command line tool or using environment variables as explained in the [AWS CLI docs](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) as well as creating a KMS key named `credstash` as explained in the [credstash Readme](https://github.com/fugue/credstash#setting-up-kms). After that is complete, you can use the provided script to add secrets to your Home Assistant secret store in credstash.
+Before using credstash, you need to set up AWS credentials either via the `aws` command line tool or using environment variables as explained in the [AWS CLI documentation](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) as well as creating a KMS key named `credstash` as explained in the [credstash Readme](https://github.com/fugue/credstash#setting-up-kms). After that is complete, you can use the provided script to add secrets to your Home Assistant secret store in credstash.
 
 ```bash
 $ hass --script credstash --help

source/_docs/z-wave/devices.markdown

@@ -59,7 +59,7 @@ Where a device doesn't send updates on status changes to the controller, you can
 
 For example, with `polling_interval=60000` (which is the default) if you have 10 devices that are being polled at every interval, and each polling takes one secound (request/response round trip), then it will take 10 seconds to complete the polling list. This only leaves 50 seconds left for normal traffic. The more devices you poll, and the shorter the interval, the less bandwidth that's available for normal traffic.
 
-Polling needs to be enabled per device, you can control this through the *polling intensity* (interval) of the device. See the [Node Management](/docs/z-wave/control-panel#z-wave-node-management) docs for details.
+Polling needs to be enabled per device, you can control this through the *polling intensity* (interval) of the device. See the [Node Management](/docs/z-wave/control-panel#z-wave-node-management) documentation for details.
 
 ## Central Scene support
 

source/_faq/missing-documentation.markdown

@@ -1,6 +1,6 @@
 ---
 title: "Missing Documentation"
-description: "The docs are missing or outdated"
+description: "The documentation is missing or outdated"
 ha_category: Documentation
 ---
 

source/_includes/custom/grid_item_left.html

@@ -12,7 +12,7 @@
     <img src='/images/supported_brands/philips_hue.png' alt="Philips Hue" />
   </a>
   <a href='/integrations/cast/'>
-    <img src='/images/supported_brands/google_cast.png' alt="Google Cast" />
+    <img src='https://brands.home-assistant.io/cast/logo.png' srcset="https://brands.home-assistant.io/cast/logo@2x.png 2x" alt="Google Cast"/>
   </a>
   <a href='/integrations/mqtt/'>
     <img src='/images/supported_brands/mqtt.png' alt="MQTT" />

source/_includes/site/header.html

@@ -24,7 +24,7 @@
             {% endcomment %}
             <li><a href="/getting-started/">Getting started</a></li>
             <li><a href="/integrations/">Integrations</a></li>
-            <li><a href="/docs/">Docs</a></li>
+            <li><a href="/docs/">Documentation</a></li>
             <li><a href="/cookbook/">Examples</a></li>
             <li><a href="/blog/">Blog</a></li>
             <li><a href="/help/">Need help?</a></li>
@@ -35,7 +35,7 @@
       <div class='search-container' style='display: none'>
         <div class='search'>
           <i class="icon-search"></i>
-          <input id='search' placeholder='Search the docs…'>
+          <input id='search' placeholder='Search the documentation…'>
           <a href='#' class='close'><i class="icon-remove-sign"></i></a>
         </div>
       </div>

source/_integrations/alarmdecoder.markdown

@@ -87,7 +87,7 @@ autobypass:
   default: false
   type: boolean
 zones:
-  description: "AlarmDecoder has no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/integrations/alarmdecoder) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor integrations.*"
+  description: "AlarmDecoder has no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/integrations/alarmdecoder) documentation. *Note: If no zones are specified, Home Assistant will not load any binary_sensor integrations.*"
   required: false
   type: list
   keys:

source/_integrations/androidtv.markdown

@@ -1,7 +1,6 @@
 ---
 title: Android TV
 description: Instructions on how to integrate Android TV and Fire TV devices into Home Assistant.
-logo: androidtv.png
 ha_category:
   - Media Player
 ha_release: 0.7.6

source/_integrations/automation.markdown

@@ -10,7 +10,7 @@ ha_codeowners:
 ha_domain: automation
 ---
 
-Please see the [docs section](/docs/automation/) for in-depth
+Please see the [automation section](/docs/automation/) for in-depth
 documentation on how to use the automation integration.
 
 <p class='img'>

source/_integrations/aws.markdown

@@ -103,7 +103,7 @@ context:
 
 ## Lambda Notify Usage
 
-AWS Lambda is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will invoke a Lambda for all targets given in the notification payload. A target can be formatted as a function name, an entire ARN ([Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)) or a partial ARN. For more information, please see the [botocore docs](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/lambda.html#Lambda.Client.invoke).
+AWS Lambda is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will invoke a Lambda for all targets given in the notification payload. A target can be formatted as a function name, an entire ARN ([Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)) or a partial ARN. For more information, please see the [botocore documentation](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/lambda.html#Lambda.Client.invoke).
 
 The Lambda event payload will contain everything passed in the service call payload. Here is an example payload that would be sent to Lambda:
 
@@ -131,7 +131,7 @@ The context will look like this:
 
 ## SNS Notify Usage
 
-AWS SNS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to all targets given in the notification payload. A target must be a SNS topic or endpoint ARN ([Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)). For more information, please see the [botocore docs](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sns.html#SNS.Client.publish).
+AWS SNS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to all targets given in the notification payload. A target must be a SNS topic or endpoint ARN ([Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)). For more information, please see the [botocore documentation](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sns.html#SNS.Client.publish).
 
 If one exists, the SNS Subject will be set to the title. All attributes from the payload, except the message, will be sent as stringified message attributes.
 
@@ -157,7 +157,7 @@ If you do not download them, you will lose them and will have to recreate a new
 
 ## SQS Notify Usage
 
-AWS SQS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to the queue for all targets given in the notification payload. A target must be a SQS topic URL. For more information, please see the [SQS docs](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/ImportantIdentifiers.html) and [bototcore docs](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sqs.html#SQS.Client.send_message)
+AWS SQS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to the queue for all targets given in the notification payload. A target must be a SQS topic URL. For more information, please see the [SQS documentation](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/ImportantIdentifiers.html) and [bototcore documentation](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sqs.html#SQS.Client.send_message)
 
 The SQS event payload will contain everything passed in the service call payload. SQS payloads will be published as stringified JSON. All attributes from the payload, except message, will also be sent as stringified message attributes. Here is an example message that would be published to the SQS queue:
 

source/_integrations/bom.markdown

@@ -34,7 +34,7 @@ name:
   required: false
   type: string
 station:
-  description: "The station ID string. See the [`sensor.bom` docs](#sensor) for details on how to find the ID of a station."
+  description: "The station ID string. See the [`sensor.bom` documentation](#sensor) for details on how to find the ID of a station."
   required: false
   type: string
   default: The closest station

source/_integrations/caldav.markdown

@@ -8,22 +8,13 @@ ha_release: '0.60'
 ha_domain: caldav
 ---
 
-The `caldav` platform allows you to connect to your WebDAV calendar and generate
+The `caldav` platform allows you to connect to your WebDAV calendar and generate binary sensors. A different sensor will be created for each individual calendar, or you can specify custom calendars which match a criteria you define (more on that below). These sensors will be `on` if you have an on going event in that calendar or `off` if the event is later in time, or if there is no event at all. The WebDAV calendar get updated roughly every 15 minutes.
-binary sensors. A different sensor will be created for each individual calendar,
-or you can specify custom calendars which match a criteria you define (more on
-that below). These sensors will be `on` if you have an on going event in that
-calendar or `off` if the event is later in time, or if there is no event at all.
-The WebDAV calendar get updated roughly every 15 minutes.
 
 ### Prerequisites
 
-You need to have a CalDAV server and credentials for it. This integration was
+You need to have a CalDAV server and credentials for it. This integration was tested against [Baikal](http://sabre.io/baikal/) but any integration complying with the RFC4791 should work. [Nextcloud](https://nextcloud.com/) and [Owncloud](https://owncloud.org/) work fine.
-tested against [Baikal](http://sabre.io/baikal/) but any integration complying
-with the RFC4791 should work. [Nextcloud](https://nextcloud.com/)
-and [Owncloud](https://owncloud.org/) work fine.
 
-You might need some additional system packages to compile the
+You might need some additional system packages to compile the Python CalDAV library. On a Debian based system, install them by:
-Python CalDAV library. On a Debian based system, install them by:
 
 ```bash
 $ sudo apt-get install libxml2-dev libxslt1-dev zlib1g-dev
@@ -31,8 +22,7 @@ $ sudo apt-get install libxml2-dev libxslt1-dev zlib1g-dev
 
 ### Basic Setup
 
-To integrate a WebDAV calendar in Home Assistant,
+To integrate a WebDAV calendar in Home Assistant, add the following section to your `configuration.yaml` file:
-add the following section to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry for baikal
@@ -52,16 +42,11 @@ calendar:
     url: https://nextcloud.example.com/remote.php/dav
 ```
 
-This example will generate default binary sensors for each calendar you have in
+This example will generate default binary sensors for each calendar you have in your account. Those calendars will be `on` when there is an ongoing event and `off` if not. Events that last a whole day are ignored in those calendars. You have to setup custom calendars in order to take them into account or for advanced event filtering.
-your account. Those calendars will be `on` when there is an ongoing event and
-`off` if not. Events that last a whole day are ignored in those calendars.
-You have to setup custom calendars in order to take them into account or for
-advanced event filtering.
 
 ### Custom calendars
 
-You have the possibility to create multiple binary
+You have the possibility to create multiple binary sensors for events that match certain conditions.
-sensors for events that match certain conditions.
 
 ```yaml
 # Example configuration.yaml entry
@@ -79,13 +64,9 @@ calendar:
         search: 'Warmup'
 ```
 
-This will create two binary sensors for the calendar name Agenda: "HomeOffice"
+This will create two binary sensors for the calendar name Agenda: "HomeOffice" and "WarmupFlat". Those sensors will be `on` if there is an ongoing event matching the regular expression specified in `search`. In custom calendars, events that last a whole day are taken into account.
-and "WarmupFlat". Those sensors will be `on` if there is an ongoing event
-matching the regular expression specified in `search`.
-In custom calendars, events that last a whole day are taken into account.
 
-Please note that when you configure custom calendars,
+Please note that if you use the `custom_calendars` option, only those calendars will be loaded. You cannot use `calendars` and `custom_calendars` in the same configuration.
-the default ones are not created anymore.
 
 {% configuration %}
 url:
@@ -102,13 +83,11 @@ password:
   type: string
 calendars:
   required: false
-  description: >
+  description: List of the calendars to filter. Empty or absent means no filtering, i.e., all calendars will be added. It cannot be used if `custom_calender` option is used.
-    List of the calendars to filter.
-    Empty or absent means no filtering, i.e., all calendars will be added.
   type: list
 custom_calendars:
   required: false
-  description: Details on any custom binary sensor calendars you want to create.
+  description: Details on any custom binary sensor calendars you want to create. Using this will only load the custom calendars supplied. No other calendars will load.
   type: list
   keys:
     name:
@@ -121,9 +100,7 @@ custom_calendars:
       type: string
     search:
       required: true
-      description: >
+      description: Regular expression for filtering the events based on the content of their summary, description or location.
-        Regular expression for filtering the events based on
-        the content of their summary, description or location.
       type: string
 {% endconfiguration %}
 
@@ -140,6 +117,7 @@ custom_calendars:
 ### Examples
 
 All events of the calendars "private" and "holidays". Note that all day events are not included.
+
 ```yaml
 # Example configuration.yaml entry for nextcloud
 calendar:
@@ -152,12 +130,9 @@ calendar:
       - holidays
 ```
 
-Full example with automation to wake up to music if not holiday.
+Full example with automation to wake up to music if not holiday. Prerequisite: you have a calendar named "work" where you create calendar entries containing "Holiday".
-Prerequisite: you have a calendar named "work" where
-you create calendar entries containing "Holiday".
 
-Custom calendar names are built from the
+Custom calendar names are built from the main calendar + name of the custom calendar. Using the option of `'.*'` will load all calendar events.
-main calendar + name of the custom calendar.
 
 ```yaml
 # configuration.yaml
@@ -170,6 +145,9 @@ calendar:
       - name: holiday
         calendar: work
         search: 'Holiday'
+      - name: vacation
+        calendar: vacation
+        search: '.*'
 
 # automations.yaml
 - id: wakeup

source/_integrations/cast.markdown

@@ -1,7 +1,6 @@
 ---
 title: Google Cast
 description: Instructions on how to integrate Google Cast into Home Assistant.
-logo: google_cast.png
 ha_category:
   - Media Player
 featured: true

source/_integrations/dialogflow.markdown

@@ -11,7 +11,7 @@ ha_domain: dialogflow
 
 The `dialogflow` integration is designed to be used with the [webhook](https://dialogflow.com/docs/fulfillment#webhook) integration of [Dialogflow](https://dialogflow.com/). When a conversation ends with a user, Dialogflow sends an action and parameters to the webhook.
 
-To be able to receive messages from Dialogflow, your Home Assistant instance needs to be accessible from the web and you need to have the `base_url` configured for the HTTP integration ([docs](/integrations/http/#base_url)). Dialogflow will return fallback answers if your server does not answer or takes too long (more than 5 seconds).
+To be able to receive messages from Dialogflow, your Home Assistant instance needs to be accessible from the web and you need to have the `base_url` configured for the HTTP integration ([documentation](/integrations/http/#base_url)). Dialogflow will return fallback answers if your server does not answer or takes too long (more than 5 seconds).
 
 Dialogflow could be [integrated](https://dialogflow.com/docs/integrations/) with many popular messaging, virtual assistant and IoT platforms.
 

source/_integrations/envisalink.markdown

@@ -105,7 +105,7 @@ panic_type:
   default: Police
   type: string
 zones:
-  description: "Envisalink boards have no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/integrations/envisalink) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.*"
+  description: "Envisalink boards have no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/integrations/envisalink) documentation. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.*"
   required: false
   type: integer
   keys:

source/_integrations/google_domains.markdown

@@ -1,7 +1,6 @@
 ---
 title: Google Domains
 description: Keep your computer registered with the Google Domains dynamic DNS.
-logo: google_domains.png
 ha_category:
   - Network
 ha_release: 0.57

source/_integrations/google_translate.markdown

@@ -1,7 +1,6 @@
 ---
 title: Google Translate Text-to-Speech
 description: Instructions on how to setup Google Translate Text-to-Speech with Home Assistant.
-logo: google.png
 ha_category:
   - Text-to-speech
 ha_release: 0.35

source/_integrations/habitica.markdown

@@ -73,7 +73,7 @@ A successful call to this service will fire an event `habitica_api_call_success`
 |----------------------|--------|----------------|
 |  `name`                |   string   |  Copied from service data attribute. |
 | `path` | [string] | Copied from service data attribute. |
-| `data` | map | Deserialized `data` field of JSON object Habitica's server returned in response to API call. For more info see [docs](https://habitica.com/apidoc/). |
+| `data` | map | Deserialized `data` field of JSON object Habitica's server returned in response to API call. For more info see the [API documentation](https://habitica.com/apidoc/). |
 
 #### Let's consider some examples on how to call the service.
 
@@ -87,7 +87,7 @@ So let's call the API on `habitica.api_call`.
   * Remove `https://habitica.com/api/v3/` at the beginning of the endpoint URL.
   * Split the remaining on slashes (/) and **append the lowercase method** at the end.
   * You should get `["tasks", "user", "post"]`. To get a better idea of the API you are recommended to try all of the API calls in IPython console [using this package](https://github.com/ASMfreaK/habitipy/blob/master/README.md).
-* The `args` key is more or less described in the [docs](https://habitica.com/apidoc/).
+* The `args` key is more or less described in the [API documentation](https://habitica.com/apidoc/).
 
 Combining all together:
 call `habitica.api_call` with data

source/_integrations/html5.markdown

@@ -90,7 +90,7 @@ The `html5` platform can only function if all of the following requirements are
 
 ### Configuring the platform
 
-1. Make sure you can access your Home Assistant installation from outside your network over HTTPS ([see docs](/docs/configuration/remote/)) or can perform an alternative [Domain Name Verification Method](https://support.google.com/webmasters/answer/9008080#domain_name_verification) on the domain used by Home Assistant.
+1. Make sure you can access your Home Assistant installation from outside your network over HTTPS ([see documentation](/docs/configuration/remote/)) or can perform an alternative [Domain Name Verification Method](https://support.google.com/webmasters/answer/9008080#domain_name_verification) on the domain used by Home Assistant.
 2. Create a new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard), this project will be imported into Firebase later (alternatively, the project can also be created during step 4).
 3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [see below](#verify-your-domain).
 4. With the domain verified, go to [https://console.firebase.google.com](https://console.firebase.google.com), select import Google project and select the project you created.

source/_integrations/hue.markdown

@@ -1,4 +1,4 @@
----
+--
 title: Philips Hue
 description: Instructions on setting up Philips Hue within Home Assistant.
 ha_category:
@@ -148,4 +148,4 @@ The Hue API doesn't activate scenes directly; rather, they must be associated wi
 
 Neither group names nor scene names are guaranteed unique in Hue. If you are observing unexpected behavior from calling Hue scenes in Home Assistant, make the names of your Hue scenes more specific in the Hue app.
 
-The Hue hub has limited space for scenes and will delete scenes if new ones get created that would overflow that space. The API docs say this is based on the scenes that are "least recently used."
+The Hue hub has limited space for scenes and will delete scenes if new ones get created that would overflow that space. The API documentation says this is based on the scenes that are "least recently used."

source/_integrations/ifttt.markdown

@@ -14,7 +14,7 @@ ha_domain: ifttt
 
 ## Sending events from IFTTT to Home Assistant
 
-To be able to receive events from IFTTT, your Home Assistant instance needs to be accessible from the web and you need to have the `base_url` configured for the HTTP integration ([docs](/integrations/http/#base_url)).
+To be able to receive events from IFTTT, your Home Assistant instance needs to be accessible from the web and you need to have the `base_url` configured for the HTTP integration ([documentation](/integrations/http/#base_url)).
 
 ### Setting up the integration
 

source/_integrations/light.mqtt.markdown

@@ -8,7 +8,7 @@ ha_release: 0.8
 ha_domain: mqtt
 ---
 
-The `mqtt` light platform lets you control your MQTT enabled lights through one of the supported message schemas.
+The `mqtt` light platform lets you control your MQTT enabled lights through one of the supported message schemas, `default`, `json` or `template`.
 
 ## Comparison of light MQTT schemas
 
@@ -214,6 +214,11 @@ rgb_value_template:
   description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the RGB value."
   required: false
   type: string
+schema:
+  description: The schema to use. Must be `default` or omitted to select the default schema".
+  required: false
+  type: string
+  default: default
 state_topic:
   description: The MQTT topic subscribed to receive state updates.
   required: false
@@ -501,6 +506,11 @@ rgb:
   required: false
   type: boolean
   default: false
+schema:
+  description: The schema to use. Must be `json` to select the JSON schema".
+  required: false
+  type: string
+  default: default
 state_topic:
   description: The MQTT topic subscribed to receive state updates.
   required: false
@@ -784,6 +794,11 @@ red_template:
   description: "[Template](/docs/configuration/templating/#processing-incoming-data) to extract red color from the state payload value."
   required: false
   type: string
+schema:
+  description: The schema to use. Must be `template` to select the template schema".
+  required: false
+  type: string
+  default: default
 state_template:
   description: "[Template](/docs/configuration/templating/#processing-incoming-data) to extract state from the state payload value."
   required: false

source/_integrations/mailgun.markdown

@@ -9,7 +9,7 @@ ha_config_flow: true
 ha_domain: mailgun
 ---
 
-To be able to receive webhooks from Mailgun, your Home Assistant instance needs to be accessible from the web and you need to have the `base_url` configured for the HTTP integration ([docs](/integrations/http/#base_url)).
+To be able to receive webhooks from Mailgun, your Home Assistant instance needs to be accessible from the web and you need to have the `base_url` configured for the HTTP integration ([documentation](/integrations/http/#base_url)).
 
 To set it up, go to the integrations page in the configuration screen and find Mailgun. Click on configure. Follow the instructions on the screen to configure Mailgun.
 

source/_integrations/map.markdown

@@ -18,3 +18,7 @@ map:
 <div class='note'>
 Devices that are currently at home won't show on the map.
 </div>
+
+<div class='note'>
+This map always shows the location of all tracked devices. If you want to hide certain entities, you should look into the [Map Card](/lovelace/map).
+</div>

source/_integrations/microsoft.markdown

@@ -1,7 +1,6 @@
 ---
 title: Microsoft Text-to-Speech (TTS)
 description: Instructions on how to set up Microsoft Text-to-Speech with Home Assistant.
-logo: microsoft.png
 ha_category:
   - Text-to-speech
 ha_release: 0.57

source/_integrations/microsoft_face.markdown

@@ -1,7 +1,6 @@
 ---
 title: Microsoft Face
 description: Instructions on how to integrate Microsoft Face integration into Home Assistant.
-logo: microsoft.png
 ha_category:
   - Image Processing
 ha_release: 0.37

source/_integrations/microsoft_face_detect.markdown

@@ -1,7 +1,6 @@
 ---
 title: Microsoft Face Detect
 description: Instructions on how to integrate Microsoft Face Detect into Home Assistant.
-logo: microsoft.png
 ha_category:
   - Image Processing
 ha_release: 0.38

source/_integrations/microsoft_face_identify.markdown

@@ -1,7 +1,6 @@
 ---
 title: Microsoft Face Identify
 description: Instructions on how to integrate Microsoft Face Identify into Home Assistant.
-logo: microsoft.png
 ha_category:
   - Image Processing
 ha_release: 0.37

source/_integrations/minio.markdown

@@ -10,7 +10,7 @@ ha_domain: minio
 ---
 
 This integration adds interaction with [Minio](https://min.io).
-Also enables to listen for bucket notifications: [watch docs](https://docs.min.io/docs/minio-client-complete-guide.html#watch)
+It also enables listening for bucket notifications: [see documentation](https://docs.min.io/docs/minio-client-complete-guide.html#watch)
 
 To download or upload files, folders must be added to [whitelist_external_dirs](/docs/configuration/basic/).
 

source/_integrations/rocketchat.markdown

@@ -45,6 +45,6 @@ rocketchat_notification:
 #### Message variables
 
 - **message** (*Required*): Message to be displayed.
-- **data** (*Optional*): Dictionary containing any of the variables defined in the [Rocket.Chat docs](https://rocket.chat/docs/developer-guides/rest-api/chat/postmessage#message-object-example)
+- **data** (*Optional*): Dictionary containing any of the variables defined in the [Rocket.Chat documentation](https://rocket.chat/docs/developer-guides/rest-api/chat/postmessage#message-object-example)
 
 To use notifications, please see the [getting started with automation page](/getting-started/automation/).

source/_integrations/slack.markdown

@@ -14,11 +14,11 @@ The `slack` platform allows you to deliver notifications from Home Assistant to
 
 ### Bot posting as you
 
-1. Create a [new app](https://api.slack.com/apps) under your Slack.com account
+1. Create a [new app](https://api.slack.com/apps) under your Slack.com account.
-2. Click the `OAuth & Permissions` link in the sidebar, under the Features heading
+2. Click the `OAuth & Permissions` link in the sidebar, under the Features heading.
-3. In the Scopes section, add the `chat:write:user` scope, `Send messages as user`. If you wish to also be able to include files, you will need to include `files:write:user`. If you get a `missing_scope` error when trying to send a message, check these permissions.
+3. In the Scopes section, add the `chat:write` scope, `Send messages as user`. If you get a `missing_scope` error when trying to send a message, check these permissions.
-4. Scroll up to `OAuth Tokens & Redirect URLs` and click `Install App`
+4. Scroll up to `OAuth Tokens & Redirect URLs` and click `Install App`.
-5. Copy your `OAuth Access Token` and put that key into your `configuration.yaml` file -- see below
+5. Copy your `OAuth Access Token` and put that key into your `configuration.yaml` file -- see below.
 
 <div class='note'>
 

source/_integrations/sonos.markdown

@@ -31,7 +31,7 @@ The queue is not snapshotted and must be left untouched until the restore. Using
 
 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
-| `entity_id` | yes | The speakers to snapshot.
+| `entity_id` | no | The speakers to snapshot. To target all Sonos devices, use `all`.
 | `with_group` | yes | Should we also snapshot the group layout and the state of other speakers in the group, defaults to true.
 
 ### Service `sonos.restore`
@@ -50,7 +50,7 @@ A cloud queue cannot be restarted. This includes queues started from within Spot
 
 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
-| `entity_id` | yes | String or list of `entity_id`s that should have their snapshot restored.
+| `entity_id` | no | String or list of `entity_id`s that should have their snapshot restored. To target all Sonos devices, use `all`.
 | `with_group` | yes | Should we also restore the group layout and the state of other speakers in the group, defaults to true.
 
 ### Service `sonos.join`

source/_integrations/ssdp.markdown

@@ -7,7 +7,7 @@ ha_release: 0.94
 ha_domain: ssdp
 ---
 
-The `ssdp` "Simple Service Discovery Protocol" integration will scan the network for supported devices and services. Discovered integrations will show up in the discovered section on the integrations page in the configuration panel.
+The `ssdp` "Simple Service Discovery Protocol" (part of UPnP) integration will scan the network for supported devices and services. Discovered integrations will show up in the discovered section on the integrations page in the configuration panel.
 
 Integrations can opt-in to be found by adding [an SSDP section](https://developers.home-assistant.io/docs/en/next/creating_integration_manifest.html#ssdp) to their `manifest.json`.
 

source/_integrations/twilio.markdown

@@ -39,7 +39,7 @@ auth_token:
 
 After configuring the base Twilio component, add and configure either or both of the [Twilio SMS](/integrations/twilio_sms) and [Twilio Phone](/integrations/twilio_call) integrations to utilize the notification functionality.
 
-To be able to receive events from Twilio, your Home Assistant instance needs to be accessible from the web and you need to have the `base_url` configured for the HTTP integration ([docs](/integrations/http/#base_url)).
+To be able to receive events from Twilio, your Home Assistant instance needs to be accessible from the web and you need to have the `base_url` configured for the HTTP integration ([documentation](/integrations/http/#base_url)).
 
 To set it up, go to the integrations page in the configuration screen and find Twilio. Click on configure. Follow the instructions on the screen to configure Twilio.
 

source/_integrations/utility_meter.markdown

@@ -18,7 +18,7 @@ From a user perspective, utility meters operate in cycles (usually monthly) for
 Some utility providers have different tariffs according to time/resource availability/etc. The utility meter enables you to define the various tariffs supported by your utility provider and accounts your consumptions in accordance. When tariffs are defined a new entity will show up indicating the current tariff. In order to change the tariff, the user must call a service, usually through an automation that can be based in time or other external source (eg. a REST sensor).
 
 <div class='note'>
-Sensors created with this integration are persistent, so values are retained across restarts of Home Assistant. The first cycle for each sensor, will be incomplete; a sensor tracking daily usage, will start to be accurate the next day after the integration was activated. A sensor tracking monthly usage, will present accurate data starting the first of the next month after being added to Home Assistant.
+Sensors created with this integration are persistent, so values are retained across restarts of Home Assistant. The first cycle for each sensor will be incomplete; a sensor tracking daily usage will start to be accurate the next day after the integration was activated. A sensor tracking monthly usage will present accurate data starting the first of the next month after being added to Home Assistant.
 </div>
 
 ## Configuration

source/_integrations/vacuum.mqtt.markdown

@@ -8,7 +8,7 @@ ha_domain: mqtt
 ---
 
 The `mqtt` vacuum integration allows you to control your MQTT-enabled vacuum.
-There are two possible message schemas - `legacy` and `state`.
+There are two possible message schemas - `legacy` and `state`, chosen by setting the `schema` configuration parameter.
 New installations should use the `state` schema as `legacy` is deprecated and might be removed someday in the future.
 The `state` schema is preferred because the vacuum will then be represented as a `StateVacuumDevice` which is the preferred parent vacuum entity.
 
@@ -158,7 +158,7 @@ retain:
   type: boolean
   default: false
 schema:
-  description: The schema to use.
+  description: The schema to use. Must be `legacy` or omitted to select the legacy schema".
   required: false
   type: string
   default: legacy
@@ -336,7 +336,7 @@ retain:
   type: boolean
   default: false
 schema:
-  description: The schema to use.
+  description: The schema to use. Must be `state` to select the state schema".
   required: false
   type: string
   default: legacy

source/_integrations/vizio.markdown

@@ -88,13 +88,13 @@ Initiation will show you two different values:
 
 | Value           | Description                                                                                             |
 | :-------------- | :------------------------------------------------------------------------------------------------------ |
-| Challenge type  | Usually, it should be `"1"`. If not, use the additional parameter `--ch_type=your_type` in the next step |
+| Challenge type  | Usually, it should be `"1"`.                                                                            |
 | Challenge token | Token required to finalize pairing in the next step                                                     |
 
 At this point, a PIN code should be displayed at the top of your TV. With all these values, you can now finish pairing:
 
 ```bash
-pyvizio --ip={ip:port} --device_type={device_type} pair-finish --token={challenge_token} --pin={pin}
+pyvizio --ip={ip:port} --device_type={device_type} pair-finish --token={challenge_token} --pin={pin} --ch_type={challenge_type}
 ```
 
 You will need the authentication token returned by this command to configure Home Assistant.

source/_integrations/xs1.markdown

@@ -11,7 +11,7 @@ ha_iot_class: Local Polling
 ha_domain: xs1
 ---
 
-The [EZcontrol XS1](http://www.ezcontrol.de/content/view/36/28/) integration for Home Assistant allows you to observe and control devices configured on the XS1 Gateway. Please have a look at the official docs for using this gateway [Bedienungsanleitung v3.0.0.0](http://www.ezcontrol.de/support/downloads/XS1/xs1manual/Bedienungsanleitung_EZcontrol_XS1_3.0.0.0-2.pdf).
+The [EZcontrol XS1](http://www.ezcontrol.de/content/view/36/28/) integration for Home Assistant allows you to observe and control devices configured on the XS1 Gateway. Please have a look at the official documentation for using this gateway [Bedienungsanleitung v3.0.0.0](http://www.ezcontrol.de/support/downloads/XS1/xs1manual/Bedienungsanleitung_EZcontrol_XS1_3.0.0.0-2.pdf).
 
 ## Configuration
 

source/_lovelace/picture-elements.markdown

@@ -380,7 +380,7 @@ style:
 {% endconfiguration %}
 
 The process for creating and referencing custom elements is the same as for custom cards.
-Please see the [developer docs on creating custom cards](https://developers.home-assistant.io/docs/en/lovelace_custom_card.html)
+Please see the [developer documentation](https://developers.home-assistant.io/docs/en/lovelace_custom_card.html)
 for more information.
 
 ## How to use the style object

source/_posts/2016-05-21-release-020.markdown

@@ -8,7 +8,7 @@ author_twitter: balloob
 categories: Release-Notes
 ---
 
-<img src='/images/supported_brands/roku.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/lastfm.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/gpmdp.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/twilio.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/aws_lambda.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/aws_sns.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/aws_sqs.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' />
+<img src='/images/supported_brands/roku.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/lastfm.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='https://brands.home-assistant.io/gpmdp/icon.png' srcset='https://brands.home-assistant.io/gpmdp/icon@2x.png 2x' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/twilio.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/aws_lambda.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/aws_sns.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/aws_sqs.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' />
 
 Tons of new supported things in 0.20.
 

source/_posts/2016-08-13-foursquare-fast-com-ffmpeg-gpsd.markdown

@@ -12,7 +12,7 @@ It's time for 0.26 and it's again full of new features and fixes. First I want t
 
 This release includes code contributed by 31 different people. The biggest change in this release is a new unit system. Instead of picking Celsius or Fahrenheit you'll have to pick imperial or metric now. This influences the units for your temperature, distance, and weight. This will simplify any platform or component that needs to know this information. Big thanks to [@Teagan42] for her hard work on this!
 
-<img src='/images/supported_brands/foursquare.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/ohmconnect.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/fastdotcom.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/gpsd.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/ffmpeg.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' />
+<img src='/images/supported_brands/foursquare.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/ohmconnect.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/fastdotcom.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/gpsd.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='https://brands.home-assistant.io/ffmpeg/logo.png' srcset='https://brands.home-assistant.io/ffmpeg/logo@2x.png 2x' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' />
 
 - Core: Introduce notion of unit system (deprecates temperature unit option) ([@Teagan42])
 - Front end: Speed improvements ([@balloob])

source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown

@@ -28,7 +28,7 @@ For a long time we have had a bunch of [weather sensors][weather-sensors] but it
 
 ### All changes
 
-<img src='/images/supported_brands/icloud.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/influxdb.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/emby.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/synology.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/garadget.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/yeelight.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/philips.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/nfandroidtv.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/currencylayer.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/influxdb.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' />
+<img src='/images/supported_brands/icloud.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/influxdb.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/emby.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/synology.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/garadget.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/yeelight.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/philips.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='https://brands.home-assistant.io/androidtv/logo.png' srcset='https://brands.home-assistant.io/androidtv/logo@2x.png 2x' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/currencylayer.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/influxdb.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' />
 
 - Cover: New [garadget] platform ([@JasonCarter80])
 - Media player: New support for [Emby][emby-media] ([@mezz64])

source/hassio/installation.markdown

@@ -215,21 +215,21 @@ A detailed guide about running Home Assistant as a virtual machine is available
 [balenaEtcher]: https://www.balena.io/etcher
 [Virtual Appliance]: https://github.com/home-assistant/operating-system/blob/dev/Documentation/boards/ova.md
 [hassos-network]: https://github.com/home-assistant/operating-system/blob/dev/Documentation/network.md
-[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi0-w-3.11.img.gz
+[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi0-w-3.12.img.gz
-[pi1]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi-3.11.img.gz
+[pi1]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi-3.12.img.gz
-[pi2]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi2-3.11.img.gz
+[pi2]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi2-3.12.img.gz
-[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi3-3.11.img.gz
+[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi3-3.12.img.gz
-[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi3-64-3.11.img.gz
+[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi3-64-3.12.img.gz
-[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi4-3.11.img.gz
+[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi4-3.12.img.gz
-[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi4-64-3.11.img.gz
+[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi4-64-3.12.img.gz
-[tinker]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_tinker-3.11.img.gz
+[tinker]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_tinker-3.12.img.gz
-[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_odroid-c2-3.11.img.gz
+[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_odroid-c2-3.12.img.gz
-[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.3/hassos_odroid-n2-4.3.img.gz
+[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.4/hassos_odroid-n2-4.4.img.gz
-[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_odroid-xu4-3.11.img.gz
+[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_odroid-xu4-3.12.img.gz
-[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_intel-nuc-3.11.img.gz
+[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_intel-nuc-3.12.img.gz
-[vmdk]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_ova-3.11.vmdk.gz
+[vmdk]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_ova-3.12.vmdk.gz
-[vhdx]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_ova-3.11.vhdx.gz
+[vhdx]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_ova-3.12.vhdx.gz
-[vdi]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_ova-3.11.vdi.gz
+[vdi]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_ova-3.12.vdi.gz
 [linux]: https://github.com/home-assistant/hassio-installer
 [local]: http://homeassistant.local:8123
 [samba]: /addons/samba/

source/lovelace/changelog.markdown

@@ -183,12 +183,12 @@ description: "Changelog of the Lovelace UI."
 - ⚠️ [sensor card]: Removed configs `height`, `line_color` and `line_width`
 - ⚠️ [gauge card]: Renamed configuration `title` to `name`
 - ⚠️ [alarm panel card]: Renamed configuration `title` to `name`
-- ⚠️ [glance card]: `tap_action` and `hold_action` configurations changed. See docs.
+- ⚠️ [glance card]: `tap_action` and `hold_action` configurations changed. See documentation.
-- ⚠️ [entity button card]: `tap_action` and `hold_action` configurations changed. See docs.
+- ⚠️ [entity button card]: `tap_action` and `hold_action` configurations changed. See documentation.
-- ⚠️ [picture card]: `tap_action` and `hold_action` configurations changed. See docs.
+- ⚠️ [picture card]: `tap_action` and `hold_action` configurations changed. See documentation.
-- ⚠️ [picture elements card]: `tap_action` and `hold_action` configurations for elements changed. See docs.
+- ⚠️ [picture elements card]: `tap_action` and `hold_action` configurations for elements changed. See documentation.
-- ⚠️ [picture entity card]: `tap_action` and `hold_action` configurations changed. See docs.
+- ⚠️ [picture entity card]: `tap_action` and `hold_action` configurations changed. See documentation.
-- ⚠️ [picture glance card]: `tap_action` and `hold_action` configurations changed. See docs.
+- ⚠️ [picture glance card]: `tap_action` and `hold_action` configurations changed. See documentation.
 
 ### All Changes
 - ❤️ [weather forecast card]: New configuration `name`