diff --git a/components/alarm_control_panel.mqtt/index.html b/components/alarm_control_panel.mqtt/index.html
index ca8e8879c4..73f879ef56 100644
--- a/components/alarm_control_panel.mqtt/index.html
+++ b/components/alarm_control_panel.mqtt/index.html
@@ -79,9 +79,9 @@
To enable this platform, add the following lines to your configuration.yaml:
# Example configuration.yaml entry
alarm_control_panel:
- platform: mqtt
- state_topic: "home/alarm"
- command_topic: "home/alarm/set"
+ - platform: mqtt
+ state_topic: "home/alarm"
+ command_topic: "home/alarm/set"
Configuration variables:
diff --git a/components/apiai/index.html b/components/apiai/index.html
index 204e5331db..9c622c040c 100644
--- a/components/apiai/index.html
+++ b/components/apiai/index.html
@@ -88,16 +88,16 @@
Select name, language (if you are planning to use it with Google Actions check here supported languages) and time zone
Click “Save”
Go to “Fullfiment” (in the left menu)
- Enable Webhook and set your HA url with the apiai endpoint. Eg.: https://myhome.duckdns.org/api/apiai?api_password=HA_PASSWORD
+ Enable Webhook and set your Home Assistant URL with the Api.ai endpoint. Eg.: https://myhome.duckdns.org/api/apiai?api_password=HA_PASSWORD
Click “Save”
Create a new intent
Below “User says” write one phrase that you, the user, will tell Api.ai. Eg.: Which is the temperature at home?
- In “Action” set some key (this will be the bind with HA config), eg.: GetTemperature
- In “Response” set “Cannot connect to HA or it is taking to long” (fall back response)
+ In “Action” set some key (this will be the bind with Home Assistant configuration), eg.: GetTemperature
+ In “Response” set “Cannot connect to Home Assistant or it is taking to long” (fall back response)
At the end of the page, click on “Fulfillment” and check “Use webhook”
Click “Save”
On the top right, where is written “Try it now…”, write, or say, the phrase you have previously defined and hit enter
- Api.ai has send a request to your HA server
+ Api.ai has send a request to your Home Assistant server
Take a look to “Integrations”, in the left menu, to configure third parties.
Configuring Home Assistant
@@ -122,7 +122,7 @@
- speech (Optional): Text or template to return to Api.ai
- action (Optional): Script definition
- - async_action (Optional): If HA should execute the action asynchronously (returning response to Api.ai without waiting the action to finish). Should be set to
True if Api.ai is returning the “Cannot connect to HA or it is taking to long” message, but then you will not be able to use values based on the result of the action. Defaults to False.
+ - async_action (Optional): If Home Assistant should execute the action asynchronously (returning response to Api.ai without waiting the action to finish). Should be set to
True if Api.ai is returning the “Cannot connect to Home Assistant or it is taking to long” message, but then you will not be able to use values based on the result of the action. Defaults to False.
Examples
Download this zip and load it in your Api.ai agent (Settings -> Export and Import) for examples intents to use with this configuration:
diff --git a/components/binary_sensor.command_line/index.html b/components/binary_sensor.command_line/index.html
index 490e5c2728..d84214ba01 100644
--- a/components/binary_sensor.command_line/index.html
+++ b/components/binary_sensor.command_line/index.html
@@ -81,7 +81,7 @@
device_class (Optional): The type/class of the sensor to set the icon in the frontend.
payload_on (Optional): The payload that represents enabled state. Default is “ON”.
payload_off (Optional): The payload that represents disabled state. Default is “OFF”.
- value_template (Optional): Defines a template to extract a value from the payload.
+ value_template (Optional): Defines a template to extract a value from the payload.
Examples
In this section you find some real life examples of how to use this sensor.
@@ -110,14 +110,15 @@
An alternative solution could look like this:
binary_sensor:
- platform: command_line
- name: Printer
- command: ping -W 1 -c 1 192.168.1.10 > /dev/null 2>&1 && echo success || echo fail
- device_class: connectivity
- payload_on: "success"
- payload_off: "fail"
+ - platform: command_line
+ name: Printer
+ command: ping -W 1 -c 1 192.168.1.10 > /dev/null 2>&1 && echo success || echo fail
+ device_class: connectivity
+ payload_on: "success"
+ payload_off: "fail"
Consider to use the ping sensor as an alternative to the samples above.