Merge branch 'rc' into current

Author: balloob

_config.yml

@@ -139,14 +139,14 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 70
-current_patch_version: 1
-date_released: 2018-05-31
+current_minor_version: 71
+current_patch_version: 0
+date_released: 2018-06-08
 
 # 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-0701---may-31"
+patch_version_notes: "#"
 # Minor release (Example #release-0431---april-25):
 
 # Date we moved to Discourse for comments

source/_components/binary_sensor.hydrawise.markdown

@@ -0,0 +1,41 @@
+---
+layout: page
+title: "Hunter Hydrawise Binary Sensor"
+description: "Instructions on how to integrate your Hunter Hydrawise Wi-Fi irrigation control system within Home Assistant."
+date: 2018-04-11 08:02
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: hydrawise_logo.png
+ha_category: Binary Sensor
+ha_release: 0.71
+ha_iot_class: Cloud Polling
+---
+
+Before setting up the [Hunter Hydrawise](https://hydrawise.com) binary sensors please follow the instructions for setting up the [Hydrawise hub](/components/hydrawise) component.
+
+Once you have enabled the `hydrawise` component, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+binary_sensor:
+  - platform: hydrawise
+```
+
+{% configuration %}
+monitored_conditions:
+  description: The binary sensors that should be displayed on the frontend.
+  required: false
+  type: list
+  default: All binary sensors are enabled.
+  keys:
+    is_watering:
+      description: The binary sensor is `on` when the zone is actively watering.
+    rain_sensor:
+      description: Is `on` when the rain_sensor (if installed on the controller) is active (wet).
+    status:
+      description: This will indicate `on` when there is a connection to the Hydrawise cloud. It is not an indication of whether the irrigation controller hardware is online.
+{% endconfiguration %}
+
+Finish the configuration by visiting the [Hydrawise sensor](/components/sensor.hydrawise/) and [Hydrawise switch](/components/switch.hydrawise/) documentation.

source/_components/binary_sensor.nest.markdown

@@ -39,6 +39,8 @@ Configuration variables:
 
 The following conditions are available by device:
 
+- Nest Home:
+  - away
 - Nest Thermostat:
   - online
   - fan

source/_components/binary_sensor.rainmachine.markdown

@@ -0,0 +1,23 @@
+---
+layout: page
+title: "RainMachine Binary Sensor"
+description: "Instructions on how to use RainMachine binary sensors with Home Assistant."
+date: 2018-05-06 21:26
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: rainmachine.png
+ha_category: Binary Sensor
+ha_iot_class: "Cloud Polling"
+ha_release: 0.71
+---
+
+The `rainmachine` binary sensor platform allows you to view crucial sensor data
+within a [RainMachine smart Wi-Fi sprinkler controller](http://www.rainmachine.com/). 
+
+<p class='note'>
+You must have the [RainMachine component](https://www.home-assistant.io/components/rainmachine/)
+configured to use this platform. After configuring that component, binary
+sensors automatically appear.
+</p>

source/_components/climate.homematicip_cloud.markdown

@@ -0,0 +1,21 @@
+---
+layout: page
+title: "HomematicIP Cloud Climate"
+description: "Instructions on how to integrate HomematicIP climate within Home Assistant."
+date: 2018-05-18 22:40
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: homematicip_cloud.png
+ha_category: Sensor
+ha_release: 0.71
+ha_iot_class: "Cloud Push"
+---
+
+The `homematicip_cloud` climate platform allows you to control
+[HomematicIP](https://www.homematic-ip.com) climate through Home Assistant.
+
+Devices will be configured automatically. Please refer to the
+[component](/components/homematicip_cloud/) configuration on how to setup
+HomematicIP Cloud.

source/_components/cover.ryobi_gdo.markdown

@@ -0,0 +1,59 @@
+---
+layout: page
+title: "Ryobi GDO Cover"
+description: "Instructions on how to integrate Ryobi Garage Door Opener (RyobiGDO) within Home Assistant."
+date: 2018-04-22 09:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: ryobi.png
+ha_category: Cover
+ha_release: 0.71
+ha_iot_class: "Cloud Polling"
+---
+
+
+The `ryobi_gdo` cover platform lets you control [Ryobi](https://www.ryobitools.com/gdo/) garage door opener through Home Assistant.
+
+## {% linkable_title Setup %}
+
+In order to be able to use your Ryobi garage door opener, you will have to get the DEVICE_ID_OF_YOUR_COVER (one for each garage door).
+
+The DEVICE_ID_OF_YOUR_COVER can be retrieved using `curl`, simply use your username and password using the following example. Your `DEVICE_ID_OF_YOUR_COVER` will be `varName`:
+
+```bash
+$ curl -H "Content-Type: application/json" -X GET \
+    -d '{"username":"RYOBIGDO_USERNAME","password":"RYOBIGDO_PASSWORD"}' \
+    https://tti.tiwiconnect.com/api/devices
+```
+
+## {% linkable_title Configuration %}
+
+To enable Ryobi covers in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+cover:
+  - platform: ryobi_gdo
+    username: RYOBIGDO_USERNAME
+    password: RYOBIGDO_PASSWORD
+    device_id:
+      - DEVICE_ID_OF_YOUR_COVER#1
+      - DEVICE_ID_OF_YOUR_COVER#2
+```
+
+{% configuration %}
+username:
+  description: Your RyobiGDO account username.
+  required: true
+  type: string
+password:
+  description: Your RyobiGDO account password.
+  required: true
+  type: string
+device_id:
+  description: List of your doors.
+  required: true
+  type: list
+{% endconfiguration %}

source/_components/device_tracker.luci.markdown

@@ -42,6 +42,7 @@ Configuration variables:
 - **host** (*Required*): The IP address of your router, e.g., `192.168.1.1`.
 - **username** (*Required*): The username of an user with administrative privileges, usually `admin`.
 - **password** (*Required*): The password for your given admin account.
+- **ssl** (*Optional*): If your router enforces SSL connections, set to `true`. Defaults to `false`.
 
 See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
 

source/_components/homekit.markdown

@@ -30,9 +30,18 @@ homekit:
     include_domains:
       - alarm_control_panel
       - light
+      - media_player
   entity_config:
     alarm_control_panel.home:
       code: 1234
+    media_player.living_room:
+      feature_list:
+        - feature: on_off
+        - feature: play_pause
+        - feature: play_stop
+        - feature: toggle_mute
+    switch.bedroom_outlet:
+      type: outlet
 ```
 
 {% configuration %}
@@ -95,6 +104,20 @@ homekit:
                 required: false
                 type: string
                 default: '`<No code>`'
+              feature_list:
+                description: Only for `media_player` entities. List of feature dictionaries to add for a given entity. Comparable to the platform schema.
+                required: false
+                type: list
+                keys:
+                  feature:
+                    description: Name of the feature to add to the entity representation. Valid features are `on_off`, `play_pause`, `play_stop` and `toogle_mute`. The media_player entity must support the feature to be valid.
+                    required: true
+                    type: string
+              type:
+                description: Only for `switch` entities. Type of accessory to be created within HomeKit. Valid types are `switch` and `outlet`.
+                required: false
+                type: string
+                default: switch
 {% endconfiguration %}
 
 <p class='note'>
@@ -221,22 +244,24 @@ The following components are currently supported:
 | Component | Type Name | Description |
 | --------- | --------- | ----------- |
 | alarm_control_panel | SecuritySystem | All security systems. |
+| automation / input_boolean / remote / script | Switch | All represented as switches. |
 | binary_sensor | Sensor | Support for `co2`, `door`, `garage_door`, `gas`, `moisture`, `motion`, `occupancy`, `opening`, `smoke` and `window` device classes. Defaults to the `occupancy` device class for everything else. |
 | climate | Thermostat | All climate devices. |
 | cover | GarageDoorOpener | All covers that support `open` and `close` and have `garage` as their `device_class`. |
 | cover | WindowCovering | All covers that support `set_cover_position`. |
 | cover | WindowCovering | All covers that support `open_cover` and `close_cover` through value mapping. (`open` -> `>=50`; `close` -> `<50`) |
 | cover | WindowCovering | All covers that support `open_cover`, `stop_cover` and `close_cover` through value mapping. (`open` -> `>70`; `close` -> `<30`; `stop` -> every value in between) |
 | device_tracker | Sensor | Support for `occupancy` device class. |
-| fan | Fan | Support for `on / off`, `direction` and `oscillating`. | 
+| fan | Fan | Support for `on / off`, `direction` and `oscillating`. |
 | light | Light | Support for `on / off`, `brightness` and `rgb_color`. |
 | lock | DoorLock | Support for `lock / unlock`. |
+| media_player | MediaPlayer | Represented as a series of switches which control `on / off`, `play / pause`, `play / stop`, or `mute` depending on `supported_features` of entity and the `mode` list specified in `entity_config`. |
 | sensor | TemperatureSensor | All sensors that have `Celsius` or `Fahrenheit` as their `unit_of_measurement` or `temperature` as their `device_class`. |
 | sensor | HumiditySensor | All sensors that have `%` as their `unit_of_measurement` and `humidity` as their `device_class`. |
 | sensor | AirQualitySensor | All sensors that have `pm25` as part of their `entity_id` or `pm25` as their `device_class` |
 | sensor | CarbonDioxideSensor | All sensors that have `co2` as part of their `entity_id` or `co2` as their `device_class` |
 | sensor | LightSensor | All sensors that have `lm` or `lx` as their `unit_of_measurement` or `illuminance` as their `device_class` |
-| switch / remote / input_boolean / script | Switch | All represented as switches. |
+| switch | Switch | Represented as a switch by default but can be changed by using `type` within `entity_config`. |
 
 
 ## {% linkable_title Error reporting %}

source/_components/hydrawise.markdown

@@ -0,0 +1,40 @@
+---
+layout: page
+title: "Hunter Hydrawise"
+description: "Instructions on how to integrate your Hunter Hydrawise Wi-Fi irrigation control system within Home Assistant."
+date: 2018-04-11 08:02
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: hydrawise_logo.png
+ha_category: Hub
+ha_release: 0.71
+ha_iot_class: Cloud Polling
+---
+
+The `hydrawise` component allows you to integrate your [Hunter Hydrawise](https://hydrawise.com) Wi-Fi irrigation controller system in Home Assistant.
+
+To enable it, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+hydrawise:
+  access_token: YOUR_API_KEY
+```
+
+{% configuration %}
+access_token:
+  description: The API KEY assigned to your Hydrawise account.
+  required: true
+  type: string
+scan_interval:
+  description: The time interval, in seconds, to poll the Hydrawise cloud.
+  required: false
+  type: int
+  default: 30
+{% endconfiguration %}
+
+To get your API access token log into your [Hydrawise account](https://app.hydrawise.com/config/account) and in the 'My Account Details' section under Account Settings click 'Generate API Key'. Enter that key in your configuration file as the `API_KEY`.
+
+Finish the configuration by visiting the [Hydrawise binary sensor](/components/binary_sensor.hydrawise/), [Hydrawise sensor](/components/sensor.hydrawise/) and [Hydrawise switch](/components/switch.hydrawise/) documentation.

source/_components/keyboard_remote.markdown

@@ -15,7 +15,7 @@ ha_iot_class: "Local Push"
 
 Receive signals from a keyboard and use it as a remote control.
 
-This component allows you to use a keyboard as remote control. It will fire `keyboard_remote_command_received` events which can then be used in automation rules. 
+This component allows you to use one or more keyboards as remote controls. It will fire `keyboard_remote_command_received` events which can then be used in automation rules.
 
 The `evdev` package is used to interface with the keyboard and thus this is Linux only. It also means you can't use your normal keyboard for this because `evdev` will block it.
 
@@ -37,15 +37,17 @@ In case of presence of multiple devices of the same model, `device_descriptor` m
 
 A list of possible device descriptors and names is reported in the debug log at startup when the device indicated in the configuration entry could not be found.
 
-A full configuration for Keyboard Remote could look like the one below:
+A full configuration for two Keyboard Remotes could look like the one below:
 
 ```yaml
 keyboard_remote:
-  device_descriptor: '/dev/input/by-id/bluetooth-keyboard'
+- device_descriptor: '/dev/input/by-id/bluetooth-keyboard'
+  type: 'key_up'
+- device_descriptor: '/dev/input/event0'
   type: 'key_up'
 ```
 
-or like the following:
+or like the following for one keyboard:
 
 ```yaml
 keyboard_remote:
@@ -62,11 +64,13 @@ automation:
     platform: event
     event_type: keyboard_remote_command_received
     event_data:
+      device_descriptor: "/dev/input/event0"
       key_code: 107 # inspect log to obtain desired keycode
   action:
     service: light.turn_on
     entity_id: light.all
 ```
+`device_descriptor` or `device_name` may be specificed in the trigger so the automation will be fired only for that keyboard. This is especially useful if you wish to use several bluetooth remotes to control different devices. Omit them to ensure the same key triggers the automation for all keyboards/remotes.
 
 ## {% linkable_title Disconnections %}
 This component manages disconnections and re-connections of the keyboard, for example in the case of a Bluetooth device that turns off automatically to preserve battery.

source/_components/light.lw12wifi.markdown

@@ -0,0 +1,45 @@
+---
+layout: page
+title: "Lagute LW-12"
+description: "Instructions on how to setup Lagute LW-12 Wifi LED controller within Home Assistant."
+date: 2018-04-28 08:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+ha_category: Light
+ha_iot_class: "Local Polling"
+logo: lagute.png
+ha_release: 0.71
+---
+
+The `lw12wifi` light platform supports Lagute LW-12 Wifi LED controller.
+
+## {% linkable_title Configuration %}
+
+To enable these lights, add the following lines to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+light:
+  - platform: lw12wifi
+    host: IP_ADDRESS_CONTROLLER
+```
+
+{% configuration %}
+host:
+  description: Host name or IP of LW-12 LED stripe to control.
+  required: true
+  type: string
+port:
+  description: Some firmware versions of the LW-12 controller listen on different ports.
+  required: false
+  type: int
+  default: 5000
+name:
+  description: Name to use in the frontend.
+  required: false
+  type: string
+  default: LW-12 FC
+{% endconfiguration %}
+

source/_components/light.nanoleaf_aurora.markdown

@@ -16,7 +16,11 @@ ha_release: 0.67
 
 ### {% linkable_title Configuration Sample %}
 
-To enable the Aurora lights, add the following lines to your `configuration.yaml` file:
+The `nanoleaf_aurora` platform allows you to control [Nanoleaf Aurora Light Panels](https://nanoleaf.me) from Home Assistant.
+
+The preferred way to set up this platform is by enabling the [discovery component](https://www.home-assistant.io/components/discovery/). Make sure to press and hold the *ON* button for 5 seconds (the LED will start flashing) on your Nanoleaf Aurora Panel while Home Assistant is starting.
+
+To configure the Aurora lights manually, add the following lines to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry