Merge branch 'current' into next

This commit is contained in:
Fabian Affolter 2018-01-08 20:55:49 +01:00
commit e518238065
No known key found for this signature in database
GPG key ID: DDF3D6F44AAB1336
10 changed files with 44 additions and 24 deletions

View file

@ -7,7 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
logo: heat-control.png
logo: mqtt.png
ha_category: Climate
ha_release: 0.55
ha_iot_class: "Local Polling"

View file

@ -7,7 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
logo: huawei.png
logo: huawei.svg
ha_category: Presence Detection
ha_release: 0.51
---

View file

@ -32,11 +32,11 @@ host:
required: true
type: string
username:
description: The username used to connect to your Unifi AP.
description: The SSH device username used to connect to your Unifi AP.
required: true
type: string
password:
description: The password used to connect to your Unifi AP.
description: The SSH device password used to connect to your Unifi AP.
required: true
type: string
{% endconfiguration %}

View file

@ -154,7 +154,7 @@ hdmi_cec:
### {% linkable_title Select Device %}
Call the `hdmi_cec/select_device` service with the name of the device from config or entity_id or physical address"to select it, for example:
Call the `hdmi_cec.select_device` service with the name of the device from config or entity_id or physical address"to select it, for example:
```json
{"device": "Chromecast"}
@ -179,15 +179,29 @@ action:
### {% linkable_title Power On %}
Call the `hdmi_cec/power_on` service (no arguments) to power on any devices that support this function.
Call the `hdmi_cec.power_on` service (no arguments) to power on any devices that support this function.
An Automation action using the example above would look something like this.
```yaml
action:
service: hdmi_cec.power_on
```
### {% linkable_title Standby %}
Call the `hdmi_cec/standby` service (no arguments) to place in standby any devices that support this function.
Call the `hdmi_cec.standby` service (no arguments) to place in standby any devices that support this function.
An Automation action using the example above would look something like this.
```yaml
action:
service: hdmi_cec.standby
```
### {% linkable_title Change volume level %}
Call the `hdmi_cec/volume` service with one of following commands:
Call the `hdmi_cec.volume` service with one of following commands:
#### {% linkable_title Volume up %}
Increase volume three times:
@ -208,7 +222,6 @@ Stop increasing volume:
{"up": "release"}
```
#### {% linkable_title Volume down %}
Decrease volume three times:

View file

@ -66,7 +66,7 @@ The `html5` platform can only function if all of the following requirements are
Assuming you have already added the platform to your configuration:
1. Open Home Assistant in Chrome or Firefox.
2. Assuming you have met all the [requirements](#requirements) above, you should see a new slider in the sidebar labeled Push Notifications.
2. Assuming you have met all the [requirements](#requirements) above, you should see a new slider for Push Notifications through the sidebar Configuration > General.
3. Slide it to the on position.
4. Within a few seconds you should be prompted to allow notifications from Home Assistant.
5. Assuming you accept, that's all there is to it!

View file

@ -7,7 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
logo: dublin_bus.jpg
logo: dublin_bus.png
ha_category: Transport
ha_iot_class: "Cloud Polling"
ha_release: 0.36

View file

@ -21,11 +21,11 @@ To enable it, add the following lines to your `configuration.yaml`:
```yaml
# Example configuration.yaml entry
switch:
platform: command_line
switches:
kitchen_light:
command_on: switch_command on kitchen
command_off: switch_command off kitchen
- platform: command_line
switches:
kitchen_light:
command_on: switch_command on kitchen
command_off: switch_command off kitchen
```
Configuration variables: