Merge branch 'current' into next

_config.yml

@@ -100,9 +100,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 113
+current_minor_version: 114
-current_patch_version: 3
+current_patch_version: 2
-date_released: 2020-08-01
+date_released: 2020-08-17
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

source/_docs/installation/updating.markdown

@@ -6,7 +6,7 @@ redirect_from: /getting-started/updating/
 
 <div class='note warning'>
 
-The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install: [Home Assistant](/hassio/) or [Home Assistant Core](/docs/installation/virtualenv/#upgrading-home-assistant).
+The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install: [Home Assistant](/hassio/) or [Home Assistant Core](/docs/installation/virtualenv/#upgrade).
 
 </div>
 

source/_docs/scripts.markdown

@@ -139,7 +139,7 @@ You can also get the script to abort after the timeout by using optional `contin
 # Wait until a valve is < 10 or abort after 1 minute.
 - wait_template: "{{ state_attr('climate.kitchen', 'valve')|int < 10 }}"
   timeout: '00:01:00'
-  continue_on_timeout: 'false'
+  continue_on_timeout: false
 ```
 {% endraw %}
 

source/_docs/scripts/conditions.markdown

@@ -242,7 +242,7 @@ condition:
   after_offset: "-01:00:00"
 ```
 
-This is 'when light' - equivalent to a state condition on `sun.sun` of `above_horizon`.
+This is 'when dark' - equivalent to a state condition on `sun.sun` of `below_horizon`.
 
 ```yaml
 condition:
@@ -251,7 +251,7 @@ condition:
       before: sunset
 ```
 
-This is 'when dark' - equivalent to a state condition on `sun.sun` of `below_horizon`.
+This is 'when light' - equivalent to a state condition on `sun.sun` of `above_horizon`.
 
 We cannot use both keys in this case as it will always be `false`.
 

source/_integrations/cast.markdown

@@ -93,19 +93,19 @@ Optional:
 
 ### Manual configuration
 
-By default, any discovered Cast device is added to Home Assistant. This can be restricted by supplying a list of wanted chrome casts.
+By default, any discovered Cast device is added to Home Assistant. This can be restricted by supplying a list of allowed chrome casts.
 
 ```yaml
 # Example configuration.yaml entry
 cast:
   media_player:
-    - host: 192.168.1.10
+    - uuid: "ae3be716-b011-4b88-a75d-21478f4f0822"
 ```
 
 {% configuration %}
 media_player:
-  description: A list that contains all Cast devices.
+  description: A list that contains advanced configuration options.
-  required: true
+  required: false
   type: list
   keys:
     uuid:

source/_integrations/doods.markdown

@@ -46,6 +46,10 @@ url:
     description: The URL of the DOODS server.
     required: true
     type: string
+auth_key:
+    description: The authentication key as set in the DOODS configuration file or as a Docker environment variable (DOODS_AUTH_KEY)
+    required: false
+    type: string
 timeout:
     description: Timeout for requests (in seconds).
     required: false
@@ -151,6 +155,7 @@ image_processing:
     url: "http://<my doods server>:8080"
     timeout: 60
     detector: default
+    auth_key: 2up3rL0ng4uthK3y
     source:
       - entity_id: camera.front_yard
     file_out:

source/_integrations/kankun.markdown

@@ -51,7 +51,7 @@ switches:
           required: false
           default: 80
           type: integer
-        patch:
+        path:
           description: Path of CGI script.
           required: false
           default: "/cgi-bin/json.cgi"

source/_integrations/push.markdown

@@ -22,7 +22,7 @@ The `push` camera can as an example be used with [motionEye](https://github.com/
 
 In motionEye, under **File Storage -> Run A Command** type in:
 ```bash
-curl -X POST -F "image=@%f" http://my.hass.server.com:8123/api/webhoo\k/my_custom_webhook_id
+curl -X POST -F "image=@%f" http://my.hass.server.com:8123/api/webhook/my_custom_webhook_id
 # inserting a backslash in the middle of "webhook" stops Motion to move the command to a webhook
 ```
 

source/_integrations/rest_command.markdown

@@ -71,8 +71,30 @@ service_name:
 
 ## Examples
 
+### Basic example which uses PUT method and payload encoded as form data
+
+This example implements 2 REST commands to add service calls for the missing shuffle functionality of the iTunes integration.
+
+```yaml
+rest_command:
+  shuffle_on: 
+    url: "http://YOUR_ITUNES-API_SERVER_IP:8181/shuffle"
+    method: put
+    content_type: "application/x-www-form-urlencoded"
+    payload: "mode=songs"
+  shuffle_off: 
+    url: "http://YOUR_ITUNES-API_SERVER_IP:8181/shuffle"
+    method: put
+    content_type: "application/x-www-form-urlencoded"
+    payload: "mode=off"
+```
+
+### Using templates to change the payload based on entities
+
 The commands can be dynamic, using templates to insert values of other entities. Service call support variables for doing things with templates.
 
+In this example, uses [templates](/docs/configuration/templating/) for dynamic parameters.
+
 {% raw %}
 ```yaml
 # Example configuration.yaml entry
@@ -90,7 +112,7 @@ rest_command:
 ```
 {% endraw %}
 
-In this example entry, you can see some simple [templates](/docs/configuration/templating/) in use for dynamic parameters.
+### How to test your new REST command
 
 Call the new service from [developer tools](/docs/tools/dev-tools/) in the sidebar with some `data` like:
 
@@ -100,7 +122,7 @@ Call the new service from [developer tools](/docs/tools/dev-tools/) in the sideb
   "emoji":":plex:"
 }
 ```
-Or in an example `automation`
+### Using a REST command as an action in an automation
 
 ```yaml
 automation:

source/_integrations/smtp.markdown

@@ -37,7 +37,7 @@ recipient:
   required: true
   type: [list, string]
 server:
-  description: SMTP server which is used to end the notifications.
+  description: SMTP server which is used to send the notifications.
   required: false
   type: string
   default: localhost  

source/_integrations/supla.markdown

@@ -26,7 +26,7 @@ To use Supla devices in your installation, add the following to your `configurat
 supla:
   servers:
     - server: svr1.supla.org
-      access_token: your_really_long_access_token
+      access_token: YOUR_ACCESS_TOKEN
 ```
 
 {% configuration %}
@@ -34,14 +34,13 @@ servers:
   description: List of server configurations.
   requires: true
   type: list
-server:
+  keys:
-  description: Address of your Supla Cloud server (either IP or DNS name)
+    server:
-  required: true
+      description: Address of your Supla Cloud server (either IP or DNS name)
-  type: string
+      required: true
-access_token:
+      type: string
-  description:
+    access_token:
-    An access token for REST API configuration. Can be acquired from
+      description: An access token for REST API configuration. Can be acquired from `http[s]://your.server.org/integrations/tokens` (please add at least Channel's Read and Action Execution permissions).
-    `http[s]://your.server.org/integrations/tokens` (please add at least Channel's Read and Action Execution permissions).
+      required: true
-  required: true
+      type: string
-  type: string
 {% endconfiguration %}

source/_integrations/yeelight.markdown

@@ -152,6 +152,7 @@ This integration is tested to work with the following models. If you have a diff
 | `mono`     | YLTD03YL     | Yeelight Serene Eye-Friendly Desk Lamp           |
 | `ceiling10`     | YLDL01YL     | Yeelight Meteorite Pendant Light            |
 | `ceiling13`     | YLXD01YL     | Yeelight LED Ceiling Light           |
+| `lamp` | MJTD02YL | Xiaomi Mijia Desk Lamp Pro |
 
 ## Services
 

source/_posts/2020-08-18-the-month-of-what-the-heck.markdown

@@ -0,0 +1,106 @@
+---
+title: The month of 'What the Heck?!'
+description: "Ever felt that 'What the heck Home Assistant?!' moment? This month, we would like to learn about your 'what the heck?!' moments..."
+date: 2020-08-18 00:00:00
+date_formatted: "August 18, 2020"
+author: Franck Nijhof
+author_twitter: frenck
+categories: Announcements
+og_image: /images/blog/2020-08-18-the-month-of-what-the-heck/social.png
+---
+
+<a href='https://community.home-assistant.io/c/what-the-heck/52'><img src='/images/blog/2020-08-18-the-month-of-what-the-heck/social.png' style='border: 0;box-shadow: none;'></a>
+
+Welcome to the month of “What the heck?!”
+
+Home Assistant is now almost around for 7 years! During that time, it has grown
+into a big project, beloved by many of you. However, as the project grew, some
+things might not have turned out the way it should be, are missing or maybe even
+started annoying you. That is what this month is about.
+
+We realize reporting bugs on our [GitHub][github-issues] might be a steep hill.
+You’ll need a GitHub account, report an issue following the issue templates
+using Markdown and the report itself needs to be written in a way a developer
+can work with it. Furthermore, we use our issue tracker for tracking actual
+issues and bugs; not small feature requests or annoyances.
+
+While this is a common and reasonable process to collect, track and process
+bugs, our issue tracking process might not be the ideal way to learn about
+annoyances or small tweaks and improvements that can make us all enjoy
+Home Assistant even more.
+
+In May, of this year, the Ruby on Rails project had a [similar month][rorwtf],
+which we have enjoyed watching. Now, we are going to do something similar.
+
+Today, we have opened up a [Community Forum category][forum] as a safe, lower
+barrier place to tell about your Home Assistant “What the heck?!” moments,
+and more importantly, discuss and vote  on topics your fellow users have
+brought up.
+
+Frenck recently tried something similar for Home Assistant on Twitter,
+by asking:
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Enlighten me 💡<br><br>The whole community would celebrate and be shedding happy tears of joy, if this tiny little thing was added to <a href="https://twitter.com/home_assistant?ref_src=twsrc%5Etfw">@home_assistant</a>...</p>&mdash; Franck Nijhof (@Frenck) <a href="https://twitter.com/Frenck/status/1285592609772244993?ref_src=twsrc%5Etfw">July 21, 2020</a>
+</blockquote>
+
+The responses to that question were amazing! Full of inspiration, recognition of
+stuff that annoyed us as well, but also some really really good suggestions.
+And this is not just about new tiny little things, examples may include:
+
+- I’d love to see some Home Assistant sensors with things like: The total
+  automations, triggers processed this hour, the total number of integrations,
+  entities, number of events fired.
+- I want to be able to upload a backup on the frontend on the first install.
+- Maybe you are annoyed by some logs that you need to refresh and scroll to see
+  updates?
+- You have a lot of template entities that all do the same thing and maybe could
+  be handled by Home Assistant automatically.
+- Always need a workaround to automate something the way you like and really
+  wished Home Assistant provided a better trigger/condition for it?
+
+These are the things we are looking for, the things we should share this month.
+
+We are really looking forward to all the stuff that will be brought up!
+This will be interesting!
+
+**[Join us on the forums!][forum]**
+
+<p class='img'>
+<img src='/images/blog/2020-08-18-the-month-of-what-the-heck/jackie-chan-what-the-heck.jpg' alt='Image of a person expressing a what the heck moment'></a>
+So, when does Home Assistant trigger this moment for you?
+</p>
+
+## FAQ
+
+- **_“I have multiple things! Should I put all my stuff in a single topic?!”_**
+
+  No, please create multiple, smaller topics. Each topic can be voted on,
+  picked up and resolved. Having multiple things stacked in a single forum
+  topic, makes resolving, discussing and voting on them hard. There is no
+  limitation on how many things one can suggest this month.
+
+- **_"Is everything reported going to be fixed/addressed?"_**
+
+  There is no guarantee that will happen. The goal is to lower the barrier to
+  reporting things for one month. Home Assistant still relies on contributors
+  to address or improve the project. However, we do think collecting feedback
+  this way can tremendously help with the upcoming
+  [Hacktoberfest][hacktoberfest].
+
+- **_"I really want this new integration to be implemented, so I can use my
+  devices. Is this the right place for it?"_**
+
+  No, this event is not for requesting new device or services integrations.
+  Please use the [“Feature Requests”][feature-requests] forum category instead.
+
+- **_"I’ve found a bug and am comfortable with GitHub. Where should I report my
+  issue now?"_**
+
+  If you are comfortable with using GitHub, please, by all means, [file an issue
+  report on GitHub][github-issues].
+
+[rorwtf]: https://weblog.rubyonrails.org/2020/5/7/A-May-of-WTFs/
+[forum]: https://community.home-assistant.io/c/what-the-heck/52
+[github-issues]: https://github.com/home-assistant/core/issues
+[feature-requests]: https://community.home-assistant.io/c/feature-requests/13
+[hacktoberfest]: https://hacktoberfest.digitalocean.com

source/_redirects

@@ -2118,6 +2118,10 @@
 # Redirect old /demo to new demo page
 /demo https://demo.home-assistant.io
 
+# Functionality-required redirects
+# This is a 200 so /tag/anything is a valid URL
+/tag/* /tag 200
+
 # Lovelace documentation
 /lovelace/entity-button /lovelace/button
 /lovelace/views /lovelace/dashboards-and-views

source/tag/index.markdown

@@ -0,0 +1,28 @@
+---
+title: "URL-Based Tag"
+description: "The landing page for URL-based tags"
+sidebar: false
+---
+
+You've reached this page because you navigated to an NFC, QR Code, or other URL-based tag in the format `https://www.home-assistant.io/tag/{tag}`. When the Home Assistant app is installed, it will [handle the tag](https://companion.home-assistant.io/docs/integrations/universal-links/).
+
+## iOS
+
+If you arrived here after scanning a tag on iOS, and you have the [Home Assistant Companion App](https://companion.home-assistant.io) installed, you may need to activate Universal Links:
+
+1. Long-press on [this link](https://www.home-assistant.io/tag/example_from_documentation)
+1. Choose "Open in 'Home Assistant'"
+1. Attempt to scan the tag again
+
+If you do not have it, you must [install the iOS app](https://apps.apple.com/us/app/home-assistant/id1099568401?mt=8) for these tags to function.
+
+## Android
+
+If you arrived here after scanning a tag on Android, and you have the [Home Assistant Companion App](https://companion.home-assistant.io) installed, you may need to change the link settings.
+
+1. Launch Settings and navigate to "Apps & Notifications", revealing the "Advanced" section if necessary
+1. Navigate to "Default apps" and then "Opening links"
+1. Open the "Home Assistant" settings and choose "Clear defaults"
+1. Attempt to scan the tag again, choosing to open in Home Assistant
+
+If you do not have it, you must [install the Android app](https://play.google.com/store/apps/details?id=io.homeassistant.companion.android) for these tags to function.