Merge branch 'current' into next

fabaff · fabaff · commit b8864917964a · 2017-10-23T10:10:39.000+02:00
diff --git a/_config.yml b/_config.yml
@@ -140,11 +140,11 @@ social:
 # Home Assistant release details
 current_major_version: 0
 current_minor_version: 56
-current_patch_version: 0
-date_released: 2017-10-21
+current_patch_version: 1
+date_released: 2017-10-22
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
 # Major release:
-#patch_version_notes: "#release-0551---october-15"
+patch_version_notes: "#release-0561---october-22"
 # Minor release (Example #release-0431---april-25):
diff --git a/source/_components/camera.skybell.markdown b/source/_components/camera.skybell.markdown
@@ -13,7 +13,7 @@ ha_release: 0.56
 ha_iot_class: "Cloud Polling"
 ---
 
-To get your [Skybell.com](https://skybell.com/) cameras working within Home Assistant, please follow the instructions for the general [Skybell component](/components/skybell).
+To get your [Skybell.com](https://www.skybell.com/) cameras working within Home Assistant, please follow the instructions for the general [Skybell component](/components/skybell).
 
 Once you have enabled the [Skybell component](/components/skybell), add the following to your `configuration.yaml` file:
 
diff --git a/source/_components/google_assistant.markdown b/source/_components/google_assistant.markdown
@@ -30,7 +30,9 @@ google_assistant:
     - group
 ```
 
-*Note:* It's very important that you use very long strings for `client_id` and `access_token`. Those are essentially the credentials to your Home Assistant instance.
+*Note:* It's very important that you use very long strings for `client_id` and `access_token`. Those are essentially the credentials to your Home Assistant instance. You can generate them with the following command:
+
+`cat /dev/urandom|fold -w 120|head -n 1|base64 -w 0|tr -dc '0-9A-Za-z'|cut -c -80`
 
 *Configuration Variables:*
 * *expose_by_default* (Optional): Expose devices in all supported domains by default.
diff --git a/source/_components/namecheapdns.markdown b/source/_components/namecheapdns.markdown
@@ -24,7 +24,7 @@ To use the component in your installation, add the following to your `configurat
 ```yaml
 # Example configuration.yaml entry
 namecheapdns:
-  host: @
+  host: '@'
   domain: example.com
   access_token: 0123_Dynamic_DNS_Password
 ```
diff --git a/source/_components/nest.markdown b/source/_components/nest.markdown
@@ -34,6 +34,8 @@ The Nest component is the main component to integrate all [Nest](https://nest.co
 9. Once the new product page opens the "Product ID" and "Product Secret" are located on the right side. These will be used as `client_id` and `client_secret` below.
 10. Once Home Assistant is started, a configurator will pop up asking you to log into your Nest account and copy a PIN code into Home Assistant.
 
+Connecting to the Nest Developer API requires outbound port 8553 on your firewall. The configuration will fail if this is not accessible.
+
 ### {% linkable_title Configuration %}
 
 ```yaml
diff --git a/source/_components/notify.clicksend_tts.markdown b/source/_components/notify.clicksend_tts.markdown
@@ -34,9 +34,9 @@ Configuration variables:
 * **name** (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is `ClickSend`. The notifier will bind to the service notify.NOTIFIER_NAME.
 * **username** (Required): Your username.
 * **api_key** (Required): Your API Key.
-* **recipient** (Required): Your phone no. This is where you want to send your notification SMS messages. eg: `09171234567`
-* **language** (Optional): The language you want to use to convert the message to audio. Accepted values are found in the [ClickSend Documentation](http://docs.clicksend.apiary.io/#reference/voice/voice-languages). Default value is 'en-us'.
-* **voice** (Optional): The voice that needs to be used to play the message to the recipient. Allowed values are 'female' or 'male'. Default value is 'female'.
+* **recipient** (Required): Your phone number. This is where you want to send your notification SMS messages (e.g., `09171234567`)
+* **language** (Optional): The language you want to use to convert the message to audio. Accepted values are found in the [ClickSend Documentation](http://docs.clicksend.apiary.io/#reference/voice/voice-languages). Default value is `en-us`.
+* **voice** (Optional): The voice that needs to be used to play the message to the recipient. Allowed values are `female` or `male`. Default value is `female`.
 
 To use notifications, please see the [getting started with automation page](https://home-assistant.io/getting-started/automation/).
 
diff --git a/source/_components/sensor.travisci.markdown b/source/_components/sensor.travisci.markdown
@@ -21,7 +21,7 @@ To enable this platform, please add the following to your `configuration.yaml` f
 # Example configuration.yaml entry
 sensor:
   - platform: travisci
-    github_token: 123456789
+    api_key: 123456789
 ```
 
 Configuration variables:
diff --git a/source/_components/toon.markdown b/source/_components/toon.markdown
@@ -15,7 +15,7 @@ ha_iot_class: "Cloud Polling"
 
 The `toon` component platform can be used to control your Toon thermostat. This component adds a climate device for your Toon thermostat and sensors for power and gas consumption. The component also auto-detects any smart plugs, solar panels and smoke detectors connected to Toon and adds sensors and switches for them.
 
-For the `toon` component to work, you'll need an active Toon subscription with Eneco. The component uses your Mijn Eneco credentials to control your thermostat through the [toonopafstand](https://toonopafstand.eneco.nl) website.
+For the `toon` component to work, you'll need an active Toon subscription with Eneco. The component uses your Mijn Eneco credentials to control your thermostat through the [toonopafstand](https://toonopafstand.eneco.nl) domain.
 
 To use your Toon thermostat in your installation, add the following to your `configuration.yaml` file:
 
diff --git a/source/_components/xiaomi_aqara.markdown b/source/_components/xiaomi_aqara.markdown
@@ -58,6 +58,7 @@ To enable {{ page.title }} in your installation, add the following to your `conf
 ```yaml
 # You can leave mac empty if you only have one gateway.
 xiaomi_aqara:
+  discovery_retry: 5
   gateways:
     - mac:
       key: xxxxxxxxxxxxxxxx
diff --git a/source/_cookbook/dim_and_brighten_lights.markdown b/source/_cookbook/dim_and_brighten_lights.markdown
@@ -40,7 +40,7 @@ automation:
           entity_id: zwave.YOUR_REMOTE
     action:
       - service: script.turn_off
-        data_template:
+        data:
           entity_id: script.light_bright
       - service: script.turn_off
         data:
@@ -69,7 +69,7 @@ automation:
           entity_id: zwave.YOUR_REMOTE
     action:
       - service: script.turn_off
-        data_template:
+        data:
           entity_id: script.light_dim
       - service: script.turn_off
         data:
diff --git a/source/_docs/autostart/synology.markdown b/source/_docs/autostart/synology.markdown
@@ -38,13 +38,13 @@ exec /bin/sh /volume1/homeassistant/hass-daemon start
 Register the autostart
 
 ```bash
-$ ln -s homeassistant-conf /etc/init/homeassistant-conf
+$ ln -s homeassistant.conf /etc/init/homeassistant.conf
 ```
 
 Make the relevant files executable:
 
 ```bash
-$ chmod -r 777 /etc/init/homeassistant-conf
+$ chmod -r 777 /etc/init/homeassistant.conf
 ```
 
 That's it - reboot your NAS and Home Assistant should automatically start
diff --git a/source/_docs/backend/database.markdown b/source/_docs/backend/database.markdown
@@ -10,8 +10,8 @@ footer: true
 redirect_from: /details/database/
 ---
 
-The default database that is used for Home Assistant is [SQLite](https://www.sqlite.org/) and is stored in your [configuration directory](/getting-started/configuration/), eg. `<path to config dir>/.homeassistant/home-assistant_v2.db`. You will need an installation of `sqlite3`, the command-line for SQLite database, or [DB Browser for SQLite](http://sqlitebrowser.org/) which provide an editor for executing SQL commands.
-First load your database with `sqlite3`.
+The default database that is used for Home Assistant is [SQLite](https://www.sqlite.org/) and is stored in your [configuration directory](/getting-started/configuration/) (e.g., `<path to config dir>/.homeassistant/home-assistant_v2.db`). You will need an installation of `sqlite3`, the command-line for SQLite database, or [DB Browser for SQLite](http://sqlitebrowser.org/), which provides an editor for executing SQL commands.
+First load your database with `sqlite3`:
 
 ```bash
 $ sqlite3 home-assistant_v2.db 
@@ -20,7 +20,7 @@ Enter ".help" for usage hints.
 sqlite> 
 ```
 
-It helps to set some options to make the output better readable.
+It helps to set some options to make the output more readable:
 
 ```bash
 sqlite> .header on
@@ -38,7 +38,7 @@ seq  name             file
 
 ### {% linkable_title Schema %}
 
-Get all available tables from your current Home Assistant database.
+Get all available tables from your current Home Assistant database:
 
 ```bash
 sqlite> SELECT sql FROM sqlite_master;
@@ -81,15 +81,15 @@ CREATE INDEX states__state_changes ON states (last_changed, last_updated, entity
 CREATE TABLE sqlite_stat1(tbl,idx,stat) 
 ```
 
-To only show the details about the `states` table as we are using that one in the next examples.
+To only show the details about the `states` table (since we are using that one in the next examples):
 
 ```bash
 sqlite> SELECT sql FROM sqlite_master WHERE type = 'table' AND tbl_name = 'states';
 ```
 
 ### {% linkable_title Query %}
 
-The identification of the available columns in the table is done and we are now able to create a query. Let's list of your Top 10 entities.
+The identification of the available columns in the table is done and we are now able to create a query. Let's list your Top 10 entities:
 
 ```bash
 sqlite> .width 30, 10,
@@ -110,7 +110,7 @@ group.all_switches              8018
 
 ### {% linkable_title Delete %}
 
-If you don't want to keep certain entities, you can delete them permanently.
+If you don't want to keep certain entities, you can delete them permanently:
 
 ```bash
 sqlite> DELETE FROM states WHERE entity_id="sensor.cpu";
@@ -123,4 +123,3 @@ sqlite> VACUUM;
 ```
 
 For a more interactive way to work with the database or the create statistics, checkout our [Jupyter notebooks](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/tree/master/).
-
diff --git a/source/_docs/ecosystem/ios/notifications/content_extensions.markdown b/source/_docs/ecosystem/ios/notifications/content_extensions.markdown
@@ -57,7 +57,7 @@ You can also pass the following properties under `action_data` to modify the map
 The notification thumbnail will be a still image from the camera.
 The notification content is a real time MJPEG stream of a camera (assuming the camera supports it).
 
-You can use the attachment parameters `content-type` and `hide-thumbnail` with camera.
+You can use the attachment parameters `content-type` and `hide-thumbnail` with camera to control the thumbnail.
 
 You can view an example [here](https://www.youtube.com/watch?v=LmYwpxPKW0g).
 
@@ -66,6 +66,8 @@ service: notify.ios_<your_device_id_here>
 data:
   message: Motion detected in the Living Room
   data:
+    attachment:
+      content-type: jpeg
     push:
       category: camera
     entity_id: camera.demo_camera
diff --git a/source/_docs/installation/archlinux.markdown b/source/_docs/installation/archlinux.markdown
@@ -1,15 +1,15 @@
 ---
 layout: page
-title: "Installation on ArchLinux"
-description: "Installation of Home Assistant on your ArchLinux computer."
+title: "Installation on Arch Linux"
+description: "Installation of Home Assistant on your Arch Linux computer."
 date: 2017-03-01 07:00
 sidebar: true
 comments: false
 sharing: true
 footer: true
 ---
 
-[ArchLinux](https://www.archlinux.org/) is a lightweight and flexible Linux distribution. There are official packages optimized for the i686 and x86-64 architectures available.
+[Arch Linux](https://www.archlinux.org/) is a lightweight and flexible Linux distribution. There are official packages optimized for the i686 and x86-64 architectures available.
 
 Install the needed Python packages.
 
diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown
@@ -90,6 +90,28 @@ wait_template: {% raw %}"{{ states.climate.kitchen.attributes.valve < 10 }}"{% e
 timeout: 00:01:00
 ```
 
+When using `wait_template` within an automation `trigger.entity_id` is supported for `state`, `numeric_state` and `template` triggers, see also [Available-Trigger-Data](/docs/automation/templating/#available-trigger-data).
+
+{% raw %}
+```yaml
+wait_template: "{{ is_state(trigger.entity_id, 'on') }}"
+```
+{% endraw %}
+
+It is also possible to use dummy variables, e.g., in scripts, when using `wait_template`.
+
+{% raw %}
+```yaml
+# Service call, e.g. from an automation.
+service: script.do_something
+data_template:
+  dummy: "{{ input_boolean.switch }}"
+
+# Inside the script
+wait_template: "{{ is_state(dummy, 'off') }}"
+```
+{% endraw %}
+
 ### {% linkable_title Fire an Event %}
 
 This action allows you to fire an event. Events can be used for many things. It could trigger an automation or indicate to another component that something is happening. For instance, in the below example it is used to create an entry in the logbook.
diff --git a/source/_docs/z-wave.markdown b/source/_docs/z-wave.markdown
@@ -32,3 +32,8 @@ There are 2 basic things you'll need to use Z-Wave, a Z-Wave [controller](/docs/
 
 There are 12 different regions for Z-Wave devices, which relates to the frequency the devices use. There is overlap between the regions, but you should ensure that you buy devices for your region. Wikipedia has a list of the [frequencies used](https://en.wikipedia.org/wiki/Z-Wave#Radio_frequencies).
 
+## {% linkable_title Getting started %}
+
+You'll now need to connect your [controller](/docs/z-wave/controllers/), [configure](/docs/z-wave/installation) the Z-Wave component, then [add some devices](/docs/z-wave/adding) using the [control panel](/docs/z-wave/control-panel). [This explains](/docs/z-wave/devices/) about devices, and how [entities are named](/docs/z-wave/entities).
+
+You can get more information on the [available services](/docs/z-wave/services/) and [events](/docs/z-wave/events/), what the [query stages](/docs/z-wave/query-stage) of battery powered devices are, as well as details on configuring [specific devices](/docs/z-wave/device-specific/).
diff --git a/source/_docs/z-wave/control-panel.markdown b/source/_docs/z-wave/control-panel.markdown
@@ -10,13 +10,17 @@ footer: true
 redirect_from: /getting-started/z-wave-panel/
 ---
 
+<p class='note'>
+  If you don't see the **Configuration** menu on the menubar, where you'll find the Z-Wave menu, [see here](/components/config/).
+</p>
+
 ## {% linkable_title Z-Wave Network Management %}
 
 Here is where you [include and exclude](/docs/z-wave/adding/) Z-Wave devices from your network.
 
 * **Add Node** puts the controller into inclusion mode, so you can include (add) a device to your Z-Wave network
 * **Add Node Secure** puts the controller into secure inclusion mode (this requires that you've created a [security key](/docs/z-wave/adding#sdding-security-devices))
-* **Remove Node** puts the controller into exclusion mdoe, so you can exclude (remove) a device. Note that you can exclude a non-secure device that's been added to another network
+* **Remove Node** puts the controller into exclusion mode, so you can exclude (remove) a device. Note that you can exclude a non-secure device that's been added to another network
 * **Cancel Command** cancels any of the above
 
 * **Heal Network** tells the controller to "heal" the Z-Wave network. Basically asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing.
diff --git a/source/_posts/2017-10-21-release-56.markdown b/source/_posts/2017-10-21-release-56.markdown
diff --git a/source/developers/documentation/index.markdown b/source/developers/documentation/index.markdown
diff --git a/source/developers/releasing.markdown b/source/developers/releasing.markdown
diff --git a/source/hassio/zwave.markdown b/source/hassio/zwave.markdown
