vad
diff --git a/‎source/_addons/tellstick.markdown
Lines changed: 4 additions & 4 deletions b/‎source/_addons/tellstick.markdown
Lines changed: 4 additions & 4 deletions
diff --git a/‎source/_components/alarm_control_panel.egardia.markdown
Lines changed: 1 addition & 1 deletion b/‎source/_components/alarm_control_panel.egardia.markdown
Lines changed: 1 addition & 1 deletion
diff --git a/‎source/_components/alarm_control_panel.ialarm.markdown
Lines changed: 2 additions & 2 deletions b/‎source/_components/alarm_control_panel.ialarm.markdown
Lines changed: 2 additions & 2 deletions
diff --git a/‎source/_components/calendar.caldav.markdown
Lines changed: 0 additions & 5 deletions b/‎source/_components/calendar.caldav.markdown
Lines changed: 0 additions & 5 deletions
diff --git a/‎source/_components/cloud.markdown
Lines changed: 4 additions & 0 deletions b/‎source/_components/cloud.markdown
Lines changed: 4 additions & 0 deletions
diff --git a/‎source/_components/cover.zwave.markdown
Lines changed: 10 additions & 1 deletion b/‎source/_components/cover.zwave.markdown
Lines changed: 10 additions & 1 deletion
diff --git a/‎source/_components/device_tracker.meraki.markdown
Lines changed: 1 addition & 1 deletion b/‎source/_components/device_tracker.meraki.markdown
Lines changed: 1 addition & 1 deletion
diff --git a/‎source/_components/device_tracker.unifi.markdown
Lines changed: 1 addition & 1 deletion b/‎source/_components/device_tracker.unifi.markdown
Lines changed: 1 addition & 1 deletion
diff --git a/‎source/_components/google_assistant.markdown
Lines changed: 26 additions & 20 deletions b/‎source/_components/google_assistant.markdown
Lines changed: 26 additions & 20 deletions
diff --git a/‎source/_components/hue.markdown
Lines changed: 2 additions & 2 deletions b/‎source/_components/hue.markdown
Lines changed: 2 additions & 2 deletions
@@ -94,10 +94,10 @@ You can also use this to list devices or sensors and read the output in the add-
 - `"function":"list-sensors"`
 - `"function":"list-devices"`: Alternative devices/sensors listing: Shows devices and/or sensors using key=value format (with tabs as separators, one device/sensor per line, no header lines.)
 
-- `"function":"on":"device":"x"`: Turns on device. ’x’ could either be an integer of the device-id, or the name of the device. 
+- `"function":"on","device":"x"`: Turns on device. ’x’ could either be an integer of the device-id, or the name of the device. 
 
-- `"function":"off":"device":"x"`: Turns off device. ’x’ could either be an integer of the device-id, or the name of the device. 
+- `"function":"off","device":"x"`: Turns off device. ’x’ could either be an integer of the device-id, or the name of the device. 
 
-- `"function":"bell":"device":"x"`: Sends bell command to devices supporting this. ’x’ could either be an integer of the device-id, or the name of the device.
+- `"function":"bell","device":"x"`: Sends bell command to devices supporting this. ’x’ could either be an integer of the device-id, or the name of the device.
 
-- `"function":"learn":"device":"x"`: Sends a special learn command to devices supporting this. This is normaly devices of ’selflearning’ type. ’x’ could either be an integer of the device-id, or the name of the device. 
+- `"function":"learn","device":"x"`: Sends a special learn command to devices supporting this. This is normaly devices of ’selflearning’ type. ’x’ could either be an integer of the device-id, or the name of the device. 
@@ -16,7 +16,7 @@ The `egardia` platform enables the ability to control an [Egardia](http://egardi
 
 You will need to know the IP of your alarm panel on your local network. Test if you can login to the panel by browsing to the IP address and log in using your Egardia/Woonveilig account.
 
-To enable this, add the following lines to your `configuration.yaml`:
+To enable this, add the following lines to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
 
@@ -16,7 +16,7 @@ The `ialarm` platform provides connectivity with the [Antifurto365](https://www.
 
 This platform supports the following services: `alarm_arm_away`, `alarm_arm_home` and `alarm_disarm`.
 
-To enable this, add the following lines to your `configuration.yaml`:
+To enable this, add the following lines to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
@@ -37,7 +37,7 @@ alarm_control_panel:
     required: true
     type: string
   password:
-    description: Password used to sign into the iAlarm web client.
+    description: Password used to sign into the iAlarm web client. If it has a leading zero you need to put the password within quotes.
     required: true
     type: string
   name:
 
@@ -70,11 +70,6 @@ custom_calendars:
       required: true
       pending_charges: Regular expression for filtering the events
       type: string
-    all_day:
-      required: false
-      description: Include events that last the whole day.
-      type: boolean
-      default: true
 {% endconfiguration %}
 
 
 
@@ -93,3 +93,7 @@ Currently, the following domains are available to be used with Alexa:
 - switch
 
 [alexa skill]: https://alexa.amazon.com/spa/index.html#skills/dp/B0772J1QKB/?ref=skill_dsk_skb_sr_2
+
+### {% linkable_title Frequently Asked Questions %}
+
+You can find a list of frequently asked questions (and their answers) in [this blog post](https://home-assistant.io/blog/2017/12/17/introducing-home-assistant-cloud/#faq).
@@ -2,7 +2,7 @@
 layout: page
 title: "Z-Wave Cover"
 description: "Instructions how to setup the Z-Wave covers within Home Assistant."
-date: 2016-08-24 14:15
+date: 2016-12-18 19:41
 sidebar: true
 comments: false
 sharing: true
@@ -16,3 +16,12 @@ ha_iot_class: "Local Push"
 Z-Wave garage doors, blinds, and roller shutters are supported as cover in Home Assistant.
 
 To get your Z-Wave covers working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
+
+If you discover that you need to [invert the operation]](/docs/z-wave/installation/#invert_openclose_buttons) of open/close for a particular device, you may change this behavior in your Z-Wave section of your `configuration.yaml` file as follows:
+
+```yaml
+zwave:
+  device_config:
+    cover.my_cover:
+      invert_openclose_buttons: true
+```
@@ -20,7 +20,7 @@ After you configure access to the Meraki CMX API, add the following to your `con
 # Example configuration.yaml entry
 device_tracker:
   - platform: meraki
-    secret: your_secert
+    secret: your_secret
     validator: meraki_validator
 ```
 
 
@@ -33,7 +33,7 @@ Configuration variables:
 - **password** (*Required*): The password for your given admin account.
 - **site_id** (*Optional*): Allows you to specify a `site_id` for device tracking. Defaults to `default`. Found in the URL of the controller (i.e. https://CONTROLLER:PORT/manage/site/SITE_ID/dashboard).
 - **verify_ssl** (*Optional*): Controls if the SSL certificate running on your Unifi webserver must be trusted by a known Certificate Authority on the server running Home Assistant. Defaults to 'True' but can also be a value that points to your custom cert "path/to/custom_cert.pem".
-- **detection_time** (*Optional*): The Unifi component will not return a device that has not been seen by the controller in the last 180 seconds. You can adjust this threshold with this variable and accepts seconds or `00:00:00` time formats.
+- **detection_time** (*Optional*): The Unifi component will only return devices that have been seen by the controller in the last 180 seconds. You can adjust this threshold with this variable and accepts seconds or `00:00:00` time formats.
 
 See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
 
 
@@ -13,14 +13,15 @@ featured: true
 ha_release: 0.56
 ---
 
-# Google Assistant Docs
+The `google_assistant` component allows you to control things via Google Assistant (on your mobile or tablet) or a Google Home device.
+
 The Google Assistant component requires a bit more setup than most due to the way Google requires Assistant Apps to be set up.
 
 <p class='note'>
 To use Google Assistant your Home Assistant configuration has to be externally accessible, with a hostname and SSL certificate. If you haven't already configured that you should do so before continuing.
 </p>
 
-### {% linkable_title Configuration %}
+To enable this, add the following lines to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
@@ -36,20 +37,15 @@ 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. 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`
-
-If you're not using Linux, you can use sites such as [this one](https://www.browserling.com/tools/random-string) to generate a random string (containing mixed case letters and numbers) of up to 80 characters.
+Configuration variables:
 
-*Configuration Variables:*
-* *expose_by_default* (Optional): Expose devices in all supported domains by default.
-* *project_id* (Required): Project ID from the Google Developer console (looks like `words-2ab12`)
-* *client_id* (Required): A long random URL safe string (no spaces or special characters) that will be used for Implicit OAuth.
-* *access_token* (Required): Another different long random URL safe string.
-* *agent_user_id* (Optional): A string to identify the user, e.g., email address. If not provided, the component will generate one.
-* *api_key* (Optional): An API Key generated for the project from [Google Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) which allows you to update devices without unlinking and relinking an account (see setup below). If not provided then the request_sync service is not exposed.
-* *exposed_domains* (Optional): An array of Home Assistant domains to expose to Google Assistant. Options include:
+- **expose_by_default** (*Optional*): Expose devices in all supported domains by default.
+- **project_id** (*Required*): Project ID from the Google Developer console (looks like `words-2ab12`)
+- **client_id** (*Required*): A long random URL safe string (no spaces or special characters) that will be used for Implicit OAuth.
+- **access_token** (*Required*): Another different long random URL safe string.
+- **agent_user_id** (*Optional*): A string to identify the user, e.g., email address. If not provided, the component will generate one.
+- **api_key** (*Optional*): An API Key generated for the project from [Google Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) which allows you to update devices without unlinking and relinking an account (see setup below). If not provided then the request_sync service is not exposed.
+- **exposed_domains** (*Optional*): An array of Home Assistant domains to expose to Google Assistant. Options include:
     - `switch`
     - `light`
     - `cover`
@@ -60,6 +56,15 @@ If you're not using Linux, you can use sites such as [this one](https://www.brow
     - `script`
     - `climate`
 
+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:
+
+```bash
+$ cat /dev/urandom | fold -w 120 | head -n 1 | base64 -w 0 | tr -dc '0-9A-Za-z' | cut -c -80
+```
+
+If you're not using Linux, you can use sites such as [this one](https://www.browserling.com/tools/random-string) to generate a random string (containing mixed case letters and numbers) of up to 80 characters.
+
+
 You can also customize your devices similar to other components by adding keys to entities:
 
 ```yaml
@@ -77,11 +82,12 @@ homeassistant:
       google_assistant_type: light
 ```
 
-*Entity Customization Keys:*
-* *google_assistant*: True exposes entity, false will hide it
-* *google_assistant_name*: Can be used to override the primary name of an entity. By default the `friendly_name` of an entity is used.
-* *google_assistant_type*: Can be used to override the domain/type of an entity. For example a switch can be treated as a light
-* *aliases*: Provides "nicknames" to Google Assistant. These function as alternate names for an entity that Assistant will understand when spoken.
+Entity Customization Keys:
+
+- **google_assistant**: True exposes entity, false will hide it.
+- **google_assistant_name**: Can be used to override the primary name of an entity. By default the `friendly_name` of an entity is used.
+- **google_assistant_type**: Can be used to override the domain/type of an entity. For example a switch can be treated as a light
+- **aliases**: Provides "nicknames" to Google Assistant. These function as alternate names for an entity that Assistant will understand when spoken.
 
 ### {% linkable_title Setup %}
 
 
@@ -127,15 +127,15 @@ script:
 
 *Note*: `group_name` is not linked to Home Assistant group name.
 
-*** Finding Group and Scene Names ***
+### {% linkable_title Finding Group and Scene Names %}
 
 How do you find these names?
 
 The easiest way to do this is only use the scenes from the 2nd generation Hue app. That is organized by room (group) and scene Name. Use the values of room name and scene name that you see in the app. You can test these work on the `dev-service` console of your Home Assistant instance.
 
 Alternatively, you can dump all rooms and scene names using this [gist](https://gist.github.com/sdague/5479b632e0fce931951c0636c39a9578). This does **not** tell you which groups and scenes work together but it's sufficient to get values that you can test in the `dev-service` console.
 
-*** Caveats ***
+### {% linkable_title Caveats %}
 
 The Hue API doesn't activate scenes directly, only on a Hue Group (typically rooms, especially if using the 2nd gen app). But Hue Scenes don't actually reference their group. So heuristic matching is used.