Merge pull request #4398 from home-assistant/release-0-61

0.61

_config.yml

@@ -139,12 +139,12 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 60
+current_minor_version: 61
-current_patch_version: 1
+current_patch_version: 0
-date_released: 2018-01-06
+date_released: 2018-01-14
 
 # 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-0601---january-6"
+patch_version_notes: "#"
 # Minor release (Example #release-0431---april-25):

source/_components/alarm_control_panel.alarmdecoder.markdown

@@ -18,3 +18,58 @@ The `alarmdecoder` alarm control panel platform allows you to control your [Alar
 
 The requirement is that you have setup your [AlarmDecoder hub](/components/alarmdecoder/).
 
+### {% linkable_title Services %}
+
+The Alarm Decoder component gives you access to several services for you to control your alarm with.
+
+- `alarm_arm_away`: Arms the alarm in away mode; all faults will trigger the alarm.
+- `alarm_arm_home`: Arms the alarm in stay mode; faults to the doors or windows will trigger the alarm.
+- `alarm_arm_night`: Arms the alarm in instant mode; all faults will trigger the alarm. Additionally, the entry delay is turned off on the doors.
+- `alarm_disarm`: Disarms the alarm from any state. Also clears a `check_zone` flag after an alarm was triggered.
+- `alarmdecoder_alarm_toggle_chime`: Toggles the alarm's chime state.
+
+**Note**: `alarm_arm_custom_bypass` and `alarm_trigger`, while available in the services list in Home Assistant, are not currently implemented in the Alarm Decoder component.
+
+### {% linkable_title Attributes %}
+
+There are several attributes available on the alarm panel to give you more information about your alarm.
+
+- `ac_power`: Set to `true` if your system has AC power supplying it.
+- `backlight_on`: Set to `true` if your keypad's backlight is on.
+- `battery_low`: Set to `true` if your system's back-up battery is low.
+- `check_zone`: Set to `true` if your system was recently triggered. When `check_zone` is `true`, it must be cleared by entering your code + 1 before attempting to rearm your alarm.
+- `chime`: Set to `true` if your system's chime is activated. When activated, your system will beep anytime a door or window is faulted while the alarm is disarmed.
+- `entry_delay_off`: Set to `true` if your system is in "Instant" mode, meaning the alarm will sound on any faults.
+- `programming_mode`: Set to `true` if your system is in programming mode.
+- `ready`: Set to `true` if your system is ready to be armed. Any faults, including motions sensors, will make this value `false`.
+- `zone_bypassed`: Set to `true` if your system is currently bypassing a zone.
+
+### {% linkable_title Examples %}
+
+Using a combination of the available services and attributes, you can create switch templates.
+
+#### {% linkable_title Chime Status and Control %}
+
+{% raw %}
+```yaml
+- platform: template
+  switches:
+    alarm_chime:
+      friendly_name: Chime
+      value_template: "{{ is_state_attr('alarm_control_panel.alarm_panel', 'chime', true) }}"
+      turn_on:
+        service: alarm_control_panel.alarmdecoder_alarm_toggle_chime
+        data:
+          code: !secret alarm_code
+      turn_off:
+        service: alarm_control_panel.alarmdecoder_alarm_toggle_chime
+        data:
+          code: !secret alarm_code
+      icon_template: >-
+          {% if is_state_attr('alarm_control_panel.alarm_panel', 'chime', true) %}
+            mdi:bell-ring
+          {% else %}
+            mdi:bell-off
+          {% endif %}
+```
+{% endraw %}

source/_components/alarm_control_panel.egardia.markdown

@@ -12,11 +12,11 @@ ha_release: 0.51
 ha_category: Alarm
 ---
 
-The `egardia` platform enables the ability to control an [Egardia](http://egardia.com/)/Woonveilig control panel. These alarm panels are known under different brand names across the world, including Woonveilig in the Netherlands. This was tested on a Gate01 version of the Egardia/Woonveilig platform.
+The `egardia` platform enables the ability to control an [Egardia](http://egardia.com/)/[Woonveilig](http://woonveilig.nl) control panel. These alarm panels are known under different brand names across the world, including Woonveilig in the Netherlands. This was tested on the GATE-01, GATE-02 and GATE-03 versions of the Egardia/Woonveilig platform.
 
 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` file:
+To enable the integration with your alarm panel, add the following lines to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
@@ -32,17 +32,18 @@ Configuration variables:
 - **host** (*Required*): The local IP address of the Egardia/Woonveilig alarm panel.
 - **username** (*Required*): Username for the Egardia/Woonveilig account.
 - **password** (*Required*): Password for Egardia/Woonveilig account.
+- **version** (*Optional*): The version of the Egardia system. `GATE-01`, `GATE-02` and `GATE-03` are currently supported. Defaults to `GATE-01`.
 - **port** (*Optional*): The port of the alarm panel. Defaults to 80.
 - **name** (*Optional*): Name to use for the alarm panel. Defaults to `Egardia`.
 - **report_server_enabled** (*Optional*): Enable reporting by server. Defaults to `False`.
-- **report_server_port** (*Optional*): Port of the Egardia server. Defaults to 85.
+- **report_server_port** (*Optional*): Port of the Egardia server. Defaults to 52010.
 - **report_server_codes** list (*Optional*): List of codes for the different states.
 
 Note that this basic configuration will only enable you to read the armed/armed away/disarmed status of your alarm and will **not** update the status if the alarm is triggered. This is because of how Egardia built their system. The alarm triggers normally go through their servers.
 You can change this, however, using the following procedure. This is a more advanced configuration.
 
 1. Log in into your alarm system's control panel. You will need to access http://[IP of your control panel]. You know this already since you need it in the basic configuration from above. Log in to the control panel with your Egardia/Woonveilig username and password.
-2. Once logged in, go to *System Settings*, *Report* and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. Also, update the port number 85 or to anything you like. The provided software that you will set up in the next steps runs on port 85 by default. **Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia's / Woonveilig services.** Maybe, that is just what you want. Make sure to save your settings by selecting 'OK'.
+2. Once logged in, go to *System Settings*, *Report* and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. You can leave the port number set to 52010 or change it to anything you like. **Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia's / Woonveilig services.** Maybe, that is just what you want. Make sure to save your settings by selecting 'OK'.
 3. On your Home Assistant machine run `$ sudo python3 egardiaserver.py`. Refer to the [python-egardia repository](https://github.com/jeroenterheerdt/python-egardia) for detailed documentation on parameters. This will receive status codes from your alarm control panel and display them. You will need the codes to include in your configuration.yaml. Make sure to change the status of your alarm to all states (disarm, arm, home) by all means possible (all users, remotes, web login, app) as well as trigger the alarm in all ways possible to get 100% coverage. **Before triggering the alarm it might be good to disable the siren temporarily (can be done in Panel Settings).**
 4. Once you have the codes, update your `configuration.yaml`:
 ```yaml
@@ -53,7 +54,7 @@ alarm_control_panel:
     username: YOUR_USERNAME
     password: YOUR_PASSWORD
     report_server_enabled: True
-    report_server_port: PORT_OF_EGARDIASERVER (85 as per the instructions above)
+    report_server_port: PORT_OF_EGARDIASERVER (optional, defaults to 52010)
     report_server_codes:
       arm: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
       disarm: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
@@ -62,29 +63,6 @@ alarm_control_panel:
       ignore: XXXXXXXXXXXXXXXX
 ```
 
-Note that for triggered, arm and disarm multiple codes can be entered since each sensor triggers with a different code and each user of the system has its own arm and disarm codes. Also note that your system will do regular system checks which will be reported as well. Since Home Assistant provides no way of handling them properly, you can enter those codes as ignore (again, multiple codes can be used here). The egardia component will ignore these codes and continue returning the old status if it receives any of the codes that are listed as ignore. This is useful for example when you have armed your alarm at night: normally a system check will occur at least once during the night and if that code is not specified anywhere Home Assistant will set the status of the alarm to its default, which is unarmed. This is in fact wrong. Listing the code as ignore changes this behavior and Home Assistant will continue to show the status the alarm is in (disarm, arm, home, triggered) even when system checks occur.
+Note that for *triggered*, *arm* and *disarm* multiple codes can be entered since each sensor triggers with a different code and each user of the system has its own arm and disarm codes. Also note that your system will do regular system checks which will be reported as well. Since Home Assistant provides no way of handling them properly, you can enter those codes as *ignore* (again, multiple codes can be used here). The egardia component will ignore these codes and continue returning the old status if it receives any of the codes that are listed as ignore. This is useful for example when you have armed your alarm at night: normally a system check will occur at least once during the night and if that code is not specified anywhere Home Assistant will set the status of the alarm to its default, which is unarmed. This is in fact wrong. Listing the code as ignore changes this behavior and Home Assistant will continue to show the status the alarm is in (disarm, arm, home, triggered) even when system checks occur.
 
-5. Start the `egardiaserver.py` script on boot of your Home Assistant machine, for example by using `systemctl` by `systemd`. To use this method, create a shell script named `egardiaserver.sh` that contains something like the following:
+5. Test your setup and enjoy. The component will update if the alarm status changes, including triggers. You can use this to build your own automations and send notifications as you wish. *Note*: previous versions required a separate egardiaserver to be set up. This is no longer necessary and corresponding system services can be removed (using systemctl).
-
-```bash
-$ source /srv/homeassistant/bin/activate
-$ python3 /srv/homeassistant/lib/python3.5/site-packages/pythonegardia/egardiaserver.py -host [YOURHOST] -password '[YOURPASSWORD]' -ssl True > /tmp/egardiaserver.log 2>&1
-```
-
-Mark it as executable (`$ chmod +x`) and run `sudo nano /lib/systemd/system/egardiaserver.service`. Enter the following into the `egardiaserver.service` file:
-
-```bash
-[Unit]
-Description=Egardia Server Service
-
-[Service]
-ExecStart=/bin/bash /srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/pythonegardia/egardiaserver.sh
-StandardOutput=journal+console
-
-[Install]
-WantedBy=multi-user.target
-Alias=egardiaserver.service
-```
-
-Save and then run `sudo systemctl enable egardiaserver.service` and `sudo systemctl start egardiaserver.service`.
-6. Test your setup and enjoy. The component will update if the alarm status changes, including triggers. You can use this to build your own automations and send notifications as you wish.

source/_components/alarm_control_panel.mqtt.markdown

@@ -35,14 +35,56 @@ alarm_control_panel:
     command_topic: "home/alarm/set"
 ```
 
-Configuration variables:
+{% configuration %}
-
+name:
-- **state_topic** (*Required*): The MQTT topic subscribed to receive state updates.
+  description: The name of the alarm.
-- **command_topic** (*Required*): The MQTT topic to publish commands to change the alarm state.
+  required: false
-- **name** (*Optional*): The name of the alarm. Default is 'MQTT Alarm'.
+  type: string
-- **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0. This QoS will also be used to publishing messages.
+  default: MQTT Alarm
-- **payload_disarm** (*Optional*): The payload to disarm your Alarm Panel. Default is "DISARM".
+state_topic:
-- **payload_arm_home** (*Optional*): The payload to set armed-home mode on your Alarm Panel. Default is "ARM_HOME".
+  description: The MQTT topic subscribed to receive state updates.
-- **payload_arm_away** (*Optional*): The payload to set armed-away mode on your Alarm Panel. Default is "ARM_AWAY".
+  required: true
-- **code** (*Optional*): If defined, specifies a code to enable or disable the alarm in the frontend.
+  type: string
-
+command_topic:
+  description: The MQTT topic to publish commands to change the alarm state.
+  required: true
+  type: string
+qos:
+  description: The maximum QoS level of the state topic.
+  required: false
+  type: integer
+  default: 0
+payload_disarm:
+  description: The payload to disarm your Alarm Panel.
+  required: false
+  type: string
+  default: DISARM
+payload_arm_home:
+  description: The payload to set armed-home mode on your Alarm Panel.
+  required: false
+  type: string
+  default: ARM_HOME
+payload_arm_away:
+  description: The payload to set armed-away mode on your Alarm Panel.
+  required: false
+  type: string
+  default: ARM_AWAY
+code:
+  description: If defined, specifies a code to enable or disable the alarm in the frontend.
+  required: false
+  type: string
+availability_topic:
+  description: The MQTT topic subscribed to receive availability (online/offline) updates.
+  required: false
+  type: string
+payload_available:
+  description: The payload that represents the available state.
+  required: false
+  type: string
+  default: online
+payload_not_available:
+  description: The payload that represents the unavailable state.
+  required: false
+  type: string
+  default: offline
+{% endconfiguration %}

source/_components/alarmdecoder.markdown

@@ -39,6 +39,7 @@ alarmdecoder:
     01:
       name: 'Smoke Detector'
       type: 'smoke'
+      rfid: '0123456'
     02:
       name: 'Front Door'
       type: 'opening'
@@ -53,3 +54,4 @@ Configuration variables:
 - **baudrate** (*Optional*): The baud rate of the AlarmDecoder device, if using serial type. Default: `115200`
 - **panel_display** (*Optional*): Create a sensor called sensor.alarm_display to match the Alarm Keypad display. Default: `off`
 - **zones** (*Optional*): AlarmDecoder has no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/components/binary_sensor.alarmdecoder/) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.*
+- **rfid** (*Optional*): The RF serial-number associated with RF zones.  Providing this field allows Home Assistant to associate raw sensor data to a given zone, allowing direct monitoring of the state, battery, and supervision status.

source/_components/binary_sensor.deconz.markdown

@@ -0,0 +1,33 @@
+---
+layout: page
+title: "deCONZ Binary Sensor"
+description: "Instructions on how to integrate Zigbee binary sensors from deCONZ into Home Assistant."
+date: 2017-11-12 16:30
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: deconz.jpeg
+ha_category: Binary Sensor
+ha_release: "0.61"
+ha_iot_class: "Local Push"
+---
+
+See the [deCONZ main component](/components/deconz/) for configuration instructions.
+
+The following sensor types are supported:
+
+ * Open/Close detection
+ * Presence detection
+
+Entity ids will be binary_sensor.device_name, where device_name is defined in deCONZ.
+
+#### {% linkable_title Verified to be supported binary sensors %}
+
+- Open/Close Detection
+  - Xiaomi Smart Home Security Door & Window Contact Sensor
+- Presence Detection
+  - IKEA Trådfri Motion Sensor
+  - Philips Hue Motion Sensor
+  - Xiaomi Motion Sensor
+  - Xiaomi Smart Home Aqara Human Body Sensor

source/_components/binary_sensor.doorbird.markdown

@@ -1,28 +0,0 @@
----
-layout: page
-title: "DoorBird Binary Sensor"
-description: "Instructions how to integrate DoorBird video doorbell state into Home Assistant."
-date: 2017-08-06 11:30
-sidebar: true
-comments: false
-sharing: true
-footer: true
-logo: doorbird.png
-ha_category: Binary Sensor
-ha_release: "0.54"
-ha_iot_class: "Local Polling"
----
-
-The `doorbird` binary sensor platform allows Home Assistant to monitor when your [DoorBird](http://www.doorbird.com/) doorbell rings.
-
-<p class='note'>
-  You must have the [DoorBird component](/components/doorbird/) configured to use this binary sensor.
-</p>
-
-To enable the binary sensor, add the following to your `configuration.yaml` file:
-
-```yaml
-# Example configuration.yaml entry
-binary_sensor:
-  - platform: doorbird
-```

source/_components/binary_sensor.hive.markdown

@@ -1,6 +1,6 @@
 ---
 layout: page
-title: "Hive Sensor"
+title: "Hive Binary Sensor"
 description: "Instructions on how to integrate Hive Sensors with Home Assistant."
 date: 2017-09-24 21:00
 sidebar: true

source/_components/binary_sensor.markdown

@@ -15,23 +15,26 @@ The way these sensors are displayed in the frontend can be modified in the [cust
 
 - **None**: Generic on/off. This is the default and doesn't need to be set.
 - **battery**: `On` means low, `Off` means normal
-- **cold**: `On` means cold
+- **cold**: `On` means cold, `Off` means normal
-- **connectivity**: `On` means connection present, `Off` means no connection
+- **connectivity**: `On` means connected, `Off` means disconnected
-- **gas**: `On` means gas detected
+- **door**: `On` means open, `Off` means closed
-- **heat**: `On` means hot
+- **garage_door**: `On` means open, `Off` means closed
-- **light**: Lightness threshold
+- **gas**: `On` means gas detected, `Off` means no gas (clear)
-- **moisture**: `On` means wet
+- **heat**: `On` means hot, `Off` means normal
-- **motion**: `On` means motion detected
+- **light**: `On` means light detected, `Off` means no light
-- **moving**: `On` means moving, `Off` means stopped
+- **moisture**: `On` means moisture detected (wet), `Off` means no moisture (dry)
-- **occupancy**: `On` means occupied, `Off` means not occupied
+- **motion**: `On` means motion detected, `Off` means no motion (clear)
+- **moving**: `On` means moving, `Off` means not moving (stopped)
+- **occupancy**: `On` means occupied, `Off` means not occupied (clear)
 - **opening**: `On` means open, `Off` means closed
 - **plug**: `On` means device is plugged in, `Off` means device is unplugged
-- **power**: Power, over-current, etc.
+- **power**: `On` means power detected, `Off` means no power
-- **presence**: `On` means Home, `Off` means Away
+- **presence**: `On` means home, `Off` means away
-- **problem**: `On` means a problem was detected, `Off` means the status is OK
+- **problem**: `On` means problem detected, `Off` means no problem (OK)
 - **safety**: `On` means unsafe, `Off` means safe
-- **smoke**: `On` means smoke detected
+- **smoke**: `On` means smoke detected, `Off` means no smoke (clear)
-- **sound**: `On` means sound detected, `Off` means no sound
+- **sound**: `On` means sound detected, `Off` means no sound (clear)
-- **vibration**: `On` means vibration detected, `Off` means no vibration
+- **vibration**: `On` means vibration detected, `Off` means no vibration (clear)
+- **window**: `On` means open, `Off` means closed
 
 For analog sensors please check the [component overview](https://home-assistant.io/components/#sensor).

source/_components/binary_sensor.mqtt.markdown

@@ -29,18 +29,54 @@ binary_sensor:
     state_topic: "home-assistant/window/contact"
 ```
 
-Configuration variables:
+{% configuration %}
-
+name:
-- **name** (*Optional*): The name of the binary sensor. Default is `MQTT Binary Sensor`.
+  description: The name of the binary sensor.
-- **state_topic** (*Required*): The MQTT topic subscribed to receive sensor values.
+  required: false
-- **payload_on** (*Optional*): The payload that represents the on state. Default is `ON`.
+  type: string
-- **payload_off** (*Optional*): The payload that represents the off state. Default is `OFF`.
+  default: MQTT Binary Sensor
-- **availability_topic** (*Optional*): The MQTT topic subscribed to receive birth and LWT messages from the MQTT device. If `availability_topic` is not defined, the binary sensor availability state will always be `available`. If `availability_topic` is defined, the binary sensor availability state will be `unavailable` by default.
+state_topic:
-- **payload_available** (*Optional*): The payload that represents the online state. Default is `online`.
+  description: The MQTT topic subscribed to receive sensor values.
-- **payload_not_available** (*Optional*): The payload that represents the offline state. Default is `offline`.
+  required: true
-- **qos** (*Optional*): The maximum QoS level to be used when receiving messages. Default is `0`.
+  type: string
-- **device_class** (*Optional*): The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend.
+payload_on:
-- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
+  description: The payload that represents the on state.
+  required: false
+  type: string
+  default: ON
+payload_off:
+  description: The payload that represents the off state.
+  required: false
+  type: string
+  default: OFF
+availability_topic:
+  description: "The MQTT topic subscribed to receive birth and LWT messages from the MQTT device. If `availability_topic` is not defined, the binary sensor availability state will always be `available`. If `availability_topic` is defined, the binary sensor availability state will be `unavailable` by default."
+  required: false
+  type: string
+payload_available:
+  description: The payload that represents the online state.
+  required: false
+  type: string
+  default: online
+payload_not_available:
+  description: The payload that represents the offline state.
+  required: false
+  type: string
+  default: offline
+qos:
+  description: The maximum QoS level to be used when receiving messages.
+  required: false
+  type: integer
+  default: 0
+device_class:
+  description: "The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend."
+  required: false
+  type: string
+value_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload."
+  required: false
+  type: string
+{% endconfiguration %}
 
 To test, you can use the command line tool `mosquitto_pub` shipped with `mosquitto` or the `mosquitto-clients` package to send MQTT messages. To set the state of the binary sensor manually:
 

source/_components/binary_sensor.threshold.markdown

@@ -14,15 +14,17 @@ ha_release: 0.34
 ---
 
 
-The `threshold` binary sensor platform observes the state of another sensor. If the value is below (`lower`) or higher (`upper`) than the given threshold then state of the threshold sensor is changed.
+The `threshold` binary sensor platform observes the state of another sensor. If the value is below (`lower`) or higher (`upper`) than the given threshold then state of the threshold sensor is changed. It support also a range if `lower` and `upper` are given.
 
 If the sensor is configured with no hysteresis and the sensor value is equal to the threshold, the sensor is turned off since it is not `lower` or `upper` with respect to the threshold.
 
 It's an alternative to the template binary sensor's `value_template:` to get the abnormal/too high/too low states.
 
+{% raw %}
 ```yaml
-{% raw %}{{ states.sensor.furnace.state > 2.5 }}{% endraw %}
+{{ states.sensor.furnace.state > 2.5 }}
 ```
+{% endraw %}
 
 To enable the threshold sensor, add the following lines to your `configuration.yaml`:
 
@@ -30,15 +32,32 @@ To enable the threshold sensor, add the following lines to your `configuration.y
 # Example configuration.yaml entry
 binary_sensor:
   - platform: threshold
-    threshold: 15
-    type: lower
     entity_id: sensor.random
+    lower: 20
 ```
 
-Configuration variables:
+{% configuration %}
+entity_id:
+  description: "The entity to monitor. Only [sensors](/components/sensor/) are supported."
+  required: true
+  type: entity_id
+lower:
+  description: The lower threshold which the observed value is compared against.
+  required: false
+  type: float
+upper:
+  description: The upper threshold which the observed value is compared against.
+  required: false
+  type: float
+hysteresis:
+  description: The distance the observed value must be from the threshold before the state is changed.
+  required: false
+  type: float
+  default: 0.0
+name:
+  description:  Name of the sensor to use in the frontend.
+  required: false
+  type: string
+  default: 
+{% endconfiguration %}
 
-- **entity_id** (*Required*): The entity to monitor. Only [sensors](/components/sensor/) are supported.
-- **threshold** (*Required*): The threshold which the observed value is compared against.
-- **type** (*Required*): `lower` if the value needs to be below the threshold or `upper` if higher.
-- **hysteresis** (*Optional*): The distance the observed value must be from the threshold before the state is changed. Defaults to `0.0`
-- **name** (*Optional*): Name of the sensor to use in the frontend. Defaults to `Stats`.

source/_components/binary_sensor.workday.markdown

@@ -37,6 +37,7 @@ Configuration variables:
 Days are specified as follows: `mon`, `tue`, `wed`, `thu`, `fri`, `sat`, `sun`. The keyword `holiday` is used for public holidays identified by the holidays module.
 
 <p class='note warning'>
+If you use the sensor for Norway (`NO`) you need to wrap `NO`in quotes or write the name in full. Otherwise the value is evaluated as `False`.
 If you use the sensor for Canada (`CA`) with Ontario (`ON`) as `province:` then you need to wrap `ON` in quotes. Otherwise the value is evaluated as `True` (check the YAML documentation for further details) and the sensor will not work.
 </p>
 

source/_components/camera.doorbird.markdown

@@ -13,7 +13,7 @@ ha_release: "0.54"
 ha_iot_class: "Local Polling"
 ---
 
-The `doorbird` implementation allows you to view the live video and saved images from your [DoorBird](http://www.doorbird.com/) device in Home Assistant.
+The `doorbird` implementation allows you to view the live video and previous images from your [DoorBird](http://www.doorbird.com/) device in Home Assistant.
 
 <p class='note'>
   You must have the [DoorBird component](/components/doorbird/) configured to use this camera.
@@ -26,7 +26,3 @@ To enable the camera, add the following to your `configuration.yaml` file:
 camera:
   - platform: doorbird
 ```
-
-Configuration variables:
-
-- **last_visitor** (*Optional*): Adds a second camera that shows the last picture taken when someone rang the doorbell. Default is `false`.

source/_components/climate.daikin.markdown

@@ -0,0 +1,46 @@
+---
+layout: page
+title: "Daikin AC"
+description: "Instructions on how to integrate Daikin AC(s) with Home Assistant."
+date: 2017-12-03 05:00
+sidebar: false
+comments: false
+sharing: true
+footer: true
+logo: N/A
+ha_category: Climate
+ha_release: 0.59
+ha_iot_class: "Local Polling"
+---
+
+### Description ###
+
+The climate component integrates Daikin air conditioning systems into Home Assistant, enabling control of setting the following parameters:
+- **mode** (cool, heat, dry, fan only or auto)
+- **fan speed**
+- **target temperature**
+- **swing mode** (on supported models)
+
+Current temperature is displayed.
+
+<p class='note warning'>
+    Please note, the `daikin` platform integrates **ONLY the european versions of Daikin ACs (models BRP069A41, 42, 43, 45)** into Home Assistant
+</p>
+
+### Configuration ###
+
+Manual configuration and customization is possible by using the sample configuration from below:
+
+```yaml
+# Example configuration.yaml entry
+climate:
+  - platform: daikin
+      host: 10.0.0.1
+      name: optional name
+```
+
+Configuration variables:
+
+- **host** (*Required*): IP or hostname of the device
+- **name** (*Optional*): If the device has a name previously set by the user than that name will be used
+

source/_components/climate.econet.markdown

@@ -0,0 +1,64 @@
+---
+layout: page
+title: "EcoNet water heater"
+description: "Instructions how to integrate Rheem EcoNet water heaters into Home Assistant."
+date: 2017-12-28 14:51
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: econet.png
+ha_category: Climate
+ha_release: 0.61.0
+ha_iot_class: "Cloud Polling"
+---
+
+
+The `econet` water heater platform is consuming the information provided by a [EcoNet enabled Rheem water heater](http://www.rheem.com/EcoNet/Home). This component allows you to set the temperature, the operation mode, and enable vaction mode.
+
+To enable the `econet` water heater platform add the following to your config.
+
+
+```yaml
+# Example configuration.yaml entry
+climate:
+  - platform: econet
+    username: YOUR_ECONET_EMAIL
+    password: YOUR_ECONET_PASSWORD
+```
+
+{% configuration %}
+username:
+  description: The username used to connect to your EcoNet account.
+  required: true
+  type: string
+password:
+  description: The password used to connect to your EcoNet account.
+  required: true
+  type: string
+{% endconfiguration %}
+
+
+### {% linkable_title Service `econet_add_vacation` %}
+
+You can use the service econet/add_vacation to create a new vacation for your EcoNet water heaters.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | yes | The entity id of the water heater to add the vaction to.
+| `start_date` | yes | This is a Unix timestamp for when the vaction should start.
+| `end_date` | yes | this is a Unix timestamp for when the vaction should end.
+
+<p class='note'>
+The Unix timestamps can be obtained from the input_datetime component. This will allow you to graphically set the start and end date.
+</p>
+
+### {% linkable_title Service `econet_delete_vacation` %}
+
+You can use the service econet/delete_vacation to remove all vactions from an EcoNet water heater.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | yes | The entity id of the water heater to remove the vaction from.
+
+

source/_components/climate.generic_thermostat.markdown

@@ -14,7 +14,7 @@ ha_iot_class: "Local Polling"
 ---
 
 
-The `generic_thermostat` climate platform is a thermostat implemented in Home Assistant. It uses a sensor and a switch connected to a heater under the hood. If the measured temperature is cooler then the target temperature, the heater will be turned on and turned off when required temperature is reached.
+The `generic_thermostat` climate platform is a thermostat implemented in Home Assistant. It uses a sensor and a switch connected to a heater or air conditioning under the hood. When in heater mode, if the measured temperature is cooler then the target temperature, the heater will be turned on and turned off when the required temperature is reached. When in air conditioning mode, if the measured temperature is hotter then the target temperature, the air conditioning will be turned on and turned off when required temperature is reached.
 
 ```yaml
 # Example configuration.yaml entry
@@ -28,20 +28,25 @@ climate:
 Configuration variables:
 
 - **name** (*Required*): Name of thermostat
-- **heater** (*Required*): `entity_id` for heater switch, must be a toggle device.
+- **heater** (*Required*): `entity_id` for heater switch, must be a toggle device. Becomes air conditioning switch when `ac_mode` is set to `True`
 - **target_sensor** (*Required*): `entity_id` for a temperature sensor, target_sensor.state must be temperature.
 - **min_temp** (*Optional*): Set minimum set point available (default: 7)
 - **max_temp** (*Optional*): Set maximum set point available (default: 35)
-- **target_temp** (*Optional*): Set initial target temperature. Failure to set this variable will result in target temperature being set to null on startup. As of version 0.59 it will retain the target temperature set before restart if this variable is not configured.
+- **target_temp** (*Optional*): Set initial target temperature. Failure to set this variable will result in target temperature being set to null on startup. As of version 0.59, it will retain the target temperature set before restart if available.
 - **ac_mode** (*Optional*): Set the switch specified in the *heater* option to be treated as a cooling device instead of a heating device.
 - **min_cycle_duration** (*Optional*): Set a minimum amount of time that the switch specified in the *heater* option must be in it's current state prior to being switched either off or on.
 - **cold_tolerance** (*Optional*): Set a minimum amount of difference between the temperature read by the sensor specified in the *target_sensor* option and the target temperature that must change prior to being switched on. For example, if the target temperature is 25 and the tolerance is 0.5 the heater will start when the sensor equals or goes below 24.5.
 - **hot_tolerance** (*Optional*): Set a minimum amount of difference between the temperature read by the sensor specified in the *target_sensor* option and the target temperature that must change prior to being switched off. For example, if the target temperature is 25 and the tolerance is 0.5 the heater will stop when the sensor equals or goes above 25.5.
-- **keep_alive** (*Optional*): Set a keep-alive interval. If set, the switch specified in the *heater* option will be triggered every time the interval elapses. Use with heaters and A/C units that shut off if they don't receive a signal from their remote for a while.
+- **keep_alive** (*Optional*): Set a keep-alive interval. If set, the switch specified in the *heater* option will be triggered every time the interval elapses. Use with heaters and A/C units that shut off if they don't receive a signal from their remote for a while. Use also with switches that might lose state. The keep-alive call is done with the current valid climate component state (either on or off).
 - **initial_operation_mode** (*Optional*): Set the initial operation mode. Valid values are `off` or `auto`. Value has to be double quoted. If this parameter is not set, it is preferable to set a *keep_alive* value. This is helpful to align any discrepancies between *generic_thermostat* and *heater* state.
+- **away_temp** (*Optional*): Set the temperature used by "away_mode" (default: 16). Please specify when using `ac_mode: True` to a higher value.
 
 A full configuration example looks like the one below. `min_cycle_duration` and `keep_alive` must contain at least one of the following entries: `days:`, `hours:`, `minutes:`, `seconds:` or `milliseconds:`.
 
+Currently the `generic_thermostat` climate platform supports 'heat', 'cool' and 'off' operation modes. You can force your `generic_thermstat` to avoid starting by setting Operation to 'off'. 
+
+Please note that changing Away Mode you will force a target temperature change as well that will get restored once the Away Mode is turned off. 
+
 ```yaml
 # Full example configuration.yaml entry
 climate:
@@ -51,6 +56,7 @@ climate:
     target_sensor: sensor.study_temperature
     min_temp: 15
     max_temp: 21
+    ac_mode: False
     target_temp: 17
     cold_tolerance: 0.3
     hot_tolerance: 0
@@ -59,4 +65,5 @@ climate:
     keep_alive:
       minutes: 3
     initial_operation_mode: "off"
+    away_temp: 16
 ```

source/_components/climate.hive.markdown

@@ -15,6 +15,7 @@ ha_iot_class: "Cloud Polling"
 
 
 The 'hive' climate component integrates your Hive thermostat and hot water into Home Assistant, enabling control of setting the **mode** and setting the **target temperature**.
+A short boost for Hive Heating or Hive Hot water can be set by using the **Aux Heat** function, this will turn on the boost feature for Hive Heating or Hive Hot water for 30 minutes at 0.5 degrees higher than the current temperature.
 
 The Hive climate component supports the following Hive products:
 - **Hive Active Heating**

source/_components/climate.markdown

@@ -23,7 +23,7 @@ climate:
 ## {% linkable_title Services %}
 
 ### {% linkable_title Climate control services %}
-Available services: `climate.set_aux_heat`, `climate.set_away_mode`, `climate.set_temperature`, `climate.set_humidity`, `climate.set_fan_mode`, `climate.set_operation_mode`, `climate.set_swing_mode`, `climate.set_hold_mode`
+Available services: `climate.set_aux_heat`, `climate.set_away_mode`, `climate.set_temperature`, `climate.set_humidity`, `climate.set_fan_mode`, `climate.set_operation_mode`, `climate.set_swing_mode`, `climate.set_hold_mode`, `climate.turn_on`, `climate.turn_off`
 
 <p class='note'>
 Not all climate services may be available for your platform. Be sure to check the available services Home Assistant has enabled by checking <img src='/images/screenshots/developer-tool-services-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> **Services**.
@@ -222,6 +222,22 @@ automation:
         entity_id: climate.kitchen
         swing_mode: 1
 ```
+### {% linkable_title Service `climate.turn_on` %}
+
+Turn climate device on
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Targets all when omitted.
+
+### {% linkable_title Service `climate.turn_off` %}
+
+Turn climate device off
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Targets all when omitted.
+
 #### {% linkable_title Customization  %}
 
 The step for the setpoint can be adjusted (default to 0,5 increments) by adding the following line into configuration

source/_components/climate.mqtt.markdown

@@ -28,34 +28,121 @@ climate:
     temperature_command_topic: /sensors/hvac_study/target_temp
 ```
 
-Configuration variables *except* for MQTT topics:
+{% configuration %}
-
+name:
-- **name** (*Required*): Name of MQTT HVAC.
+  description: The name of the HVAC.
-- **qos** (*Optional*): The maximum QoS level of the state topic. Default is `0` and will also be used to publishing messages.
+  required: false
-- **retain** (*Optional*): If the published message should have the retain flag on or not.
+  type: string
-- **send_if_off** (*Optional*): Set to `false` to suppress sending of all MQTT messages when the current mode is `Off`. Defaults to `true`.
+  default: MQTT HVAC
-- **initial** (*Optional*): Set the initial target temperature. Defaults to 21 degrees.
+qos:
-- **payload_on** (*Optional*): For MQTT topics that control an `on` / `off` value (e.g., `aux_command_topic`), set the value that should be sent for `on`. Defaults to 'ON'.
+  description: The maximum QoS level to be used when receiving and publishing messages.
-- **payload_off** (*Optional*): For MQTT topics that control an `on` / `off` value (e.g., `aux_command_topic`), set the value that should be sent for `off`. Defaults to 'OFF'.
+  required: false
-
+  type: integer
-Configuration of the MQTT topics:
+  default: 0
-
+retain:
-- **current_temperature_topic** (*Optional*): The MQTT topic on which to listen for the current temperature
+  description: Defines if published messages should have the retain flag set.
-- **power_command_topic** (*Optional*): The MQTT topic to publish commands to change the power state. This is useful if your device has a separate power toggle in addition to mode.
+  required: false
-- **mode_command_topic** (*Optional*): The MQTT topic to publish commands to change the HVAC operation mode.
+  type: boolean
-- **mode_state_topic** (*Optional*): The MQTT topic to subscribe for changes of the HVAC operation mode. If this is not set, the operation mode works in optimistic mode (see below).
+  default: false
-- **temperature_command_topic** (*Optional*): The MQTT topic to publish commands to change the target temperature.
+send_if_off:
-- **temperature_state_topic** (*Optional*): The MQTT topic to subscribe for changes in the target temperature. If this is not set, the target temperature works in optimistic mode (see below).
+  description: "Set to `false` to suppress sending of all MQTT messages when the current mode is `Off`."
-- **fan_mode_command_topic** (*Optional*): The MQTT topic to publish commands to change the fan mode.
+  required: false
-- **fan_mode_state_topic** (*Optional*): The MQTT topic to subscribe for changes of the HVAC fan mode. If this is not set, the fan mode works in optimistic mode (see below).
+  type: boolean
-- **swing_mode_command_topic** (*Optional*): The MQTT topic to publish commands to change the swing mode.
+  default: true
-- **swing_mode_state_topic** (*Optional*): The MQTT topic to subscribe for changes of the HVAC swing mode. If this is not set, the swing mode works in optimistic mode (see below).
+initial:
-- **away_mode_command_topic** (*Optional*): The MQTT topic to publish commands to change the away mode.
+  description: Set the initial target temperature.
-- **away_mode_state_topic** (*Optional*): The MQTT topic to subscribe for changes of the HVAC away mode. If this is not set, the away mode works in optimistic mode (see below).
+  required: false
-- **hold_command_topic** (*Optional*): The MQTT topic to publish commands to change the hold mode.
+  type: number
-- **hold_state_topic** (*Optional*): The MQTT topic to subscribe for changes of the HVAC hold mode. If this is not set, the hold mode works in optimistic mode (see below).
+  default: 21
-- **aux_command_topic** (*Optional*): The MQTT topic to publish commands to switch auxiliary heat.
+payload_on:
-- **aux_state_topic** (*Optional*): The MQTT topic to subscribe for changes of the auxiliary heat mode. If this is not set, the auxiliary heat mode works in optimistic mode (see below).
+  description: The payload that represents enabled state.
+  required: false
+  type: string
+  default: ON
+payload_off:
+  description: The payload that represents disabled state.
+  required: false
+  type: string
+  default: OFF
+availability_topic:
+  description: The MQTT topic subscribed to receive availability (online/offline) updates.
+  required: false
+  type: string
+payload_available:
+  description: The payload that represents the available state.
+  required: false
+  type: string
+  default: online
+payload_not_available:
+  description: The payload that represents the unavailable state.
+  required: false
+  type: string
+  default: offline
+current_temperature_topic:
+  description: The MQTT topic on which to listen for the current temperature.
+  required: false
+  type: string
+power_command_topic:
+  description: The MQTT topic to publish commands to change the power state. This is useful if your device has a separate power toggle in addition to mode.
+  required: false
+  type: string
+mode_command_topic:
+  description: The MQTT topic to publish commands to change the HVAC operation mode.
+  required: false
+  type: string
+mode_state_topic:
+  description: The MQTT topic to subscribe for changes of the HVAC operation mode. If this is not set, the operation mode works in optimistic mode (see below).
+  required: false
+  type: string
+temperature_command_topic:
+  description: The MQTT topic to publish commands to change the target temperature.
+  required: false
+  type: string
+temperature_state_topic:
+  description: The MQTT topic to subscribe for changes in the target temperature. If this is not set, the target temperature works in optimistic mode (see below).
+  required: false
+  type: string
+fan_mode_command_topic:
+  description: The MQTT topic to publish commands to change the fan mode.
+  required: false
+  type: string
+fan_mode_state_topic:
+  description: The MQTT topic to subscribe for changes of the HVAC fan mode. If this is not set, the fan mode works in optimistic mode (see below).
+  required: false
+  type: string
+swing_mode_command_topic:
+  description: The MQTT topic to publish commands to change the swing mode.
+  required: false
+  type: string
+swing_mode_state_topic:
+  description: The MQTT topic to subscribe for changes of the HVAC swing mode. If this is not set, the swing mode works in optimistic mode (see below).
+  required: false
+  type: string
+away_mode_command_topic:
+  description: The MQTT topic to publish commands to change the away mode.
+  required: false
+  type: string
+away_mode_state_topic:
+  description: The MQTT topic to subscribe for changes of the HVAC away mode. If this is not set, the away mode works in optimistic mode (see below).
+  required: false
+  type: string
+hold_command_topic:
+  description: The MQTT topic to publish commands to change the hold mode.
+  required: false
+  type: string
+hold_state_topic:
+  description: The MQTT topic to subscribe for changes of the HVAC hold mode. If this is not set, the hold mode works in optimistic mode (see below).
+  required: false
+  type: string
+aux_command_topic:
+  description: The MQTT topic to publish commands to switch auxiliary heat.
+  required: false
+  type: string
+aux_state_topic:
+  description: The MQTT topic to subscribe for changes of the auxiliary heat mode. If this is not set, the auxiliary heat mode works in optimistic mode (see below).
+  required: false
+  type: string
+{% endconfiguration %}
 
 #### Optimistic mode
 

source/_components/climate.nuheat.markdown

@@ -0,0 +1,139 @@
+---
+layout: page
+title: "NuHeat Thermostat"
+description: "Instructions how to integrate your NuHeat Signature thermostats within Home Assistant."
+date: 2017-11-11 18:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: nuheat.png
+ha_category: Climate
+ha_release: 0.61
+ha_iot_class: "Cloud Polling"
+---
+
+<p class='note'>
+To get your [NuHeat Signature](http://www.nuheat.com/products/thermostats/signature-thermostat) thermostats working within Home Assistant, please follow the instructions for the general [NuHeat component](/components/nuheat)
+</p>
+
+## {% linkable_title Concepts %}
+
+The NuHeat Thermostat supports the following key concepts.
+
+The `target temperature` is the temperature that the device attempts to achieve. The target temperature is either determined by the schedule programmed into the thermostat (`auto mode`) or may be overridden. When the target temperature is set by Home Assistant, the thermostat will hold this temperature until the schedule is resumed.
+
+
+## {% linkable_title Attributes %}
+
+The following attributes are provided by the NuHeat thermostat: `name`, `temperature_unit`, `current_temperature`, `target_temperature`, `current_hold_mode`, `current_operation`, `operation_list`, `min_temp` and `max_temp`.
+
+
+### {% linkable_title Attribute `name` %}
+
+Returns the name of the NuHeat Thermostat.
+
+| Attribute type | Description |
+| ---------------| ----------- |
+| String | Name of the thermostat
+
+### {% linkable_title Attribute `temperature_unit` %}
+
+Returns the unit of measurement used for temperature by the thermostat.
+
+| Attribute type | Description |
+| ---------------| ----------- |
+| String | Name of the temperature unit
+
+### {% linkable_title Attribute `current_temperature` %}
+
+Returns the current temperature measured by the thermostat.
+
+| Attribute type | Description |
+| ---------------| ----------- |
+| Integer | Currently measured temperature
+
+### {% linkable_title Attribute `target_temperature` %}
+
+Returns the target temperature of the thermostat, when the thermostat is
+not in auto operation mode.
+
+| Attribute type | Description |
+| ---------------| ----------- |
+| Integer | Target temperature
+
+### {% linkable_title Attribute `current_hold_mode` %}
+
+Returns the current temperature hold, if any.
+
+| Attribute type | Description |
+| ---------------| ----------- |
+| String | 'temperature', 'temporary_temperature', 'auto', etc.
+
+### {% linkable_title Attribute `current_operation` %}
+
+Returns the current operation of the thermostat.
+
+| Attribute type | Description |
+| ---------------| ----------- |
+| String | 'heat', 'idle'
+
+### {% linkable_title Attribute `operation_list` %}
+
+Returns the list of available operation modes.
+
+| Attribute type | Description |
+| ---------------| ----------- |
+| List of String | Available operation modes
+
+### {% linkable_title Attribute `min_temp` %}
+
+Returns the minimum supported temperature by the thermostat
+
+| Attribute type | Description |
+| ---------------| ----------- |
+| Integer | Minimum supported temperature
+
+### {% linkable_title Attribute `max_temp` %}
+
+Returns the maximum supported temperature by the thermostat
+
+| Attribute type | Description |
+| ---------------| ----------- |
+| Integer | Maximum supported temperature
+
+
+## {% linkable_title Services %}
+
+The following services are provided by the NuHeat Thermostat: `set_temperature`, `set_hold_mode`, `nuheat_resume_program`.
+
+The services `fan_min_on_time`, `set_aux_heat`, `set_away_mode`, `set_humidity`, `set_fan_mode`, `set_operation_mode` and `set_swing_mode` offered by the [Climate component](/components/climate/) are not implemented for this thermostat.
+
+### {% linkable_title Service `set_temperature` %}
+
+Puts the thermostat into an indefinite hold at the given temperature.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all.
+| `temperature` | no | Desired target temperature (when not in auto mode)
+
+Only the target temperatures relevant for the current operation mode need to
+be provided.
+
+### {% linkable_title Service `set_hold_mode` %}
+
+Sets the thermostat's hold mode. The NuHeat thermostat supports "auto" (to run the thermostat's programmed schedule), "temperature" (to indefinitely hold the thermostat's current target temperature), or "temporary_temperature" (to hold the thermostat's current target temperature until the thermostat's next scheduled event).
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all.
+| `hold_mode` | no | New value of hold mode.
+
+### {% linkable_title Service `nuheat_resume_program` %}
+
+Resumes the currently active schedule.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all.

source/_components/climate.touchline.markdown

@@ -0,0 +1,32 @@
+---
+layout: page
+title: "Roth Touchline"
+description: "Instructions how to integrate Roth Touchline within Home Assistant."
+date: 2018-01-03 12:35
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: roth.png
+ha_category: Climate
+ha_release: 0.61
+ha_iot_class: "Local Polling"
+---
+
+The `touchline` climate platform let you control [ROTH Touchline](http://www.roth-nordic.dk/dk/roth-touchline-tradloes-gulvvarmeregulering-1475.htm) floor heating thermostats from Roth. 
+
+
+To set it up, add the following information to your `configuration.yaml` file:
+
+```yaml
+climate:
+  - platform: touchline
+    host: YOUR_IPADDRESS
+```
+
+{% configuration %}
+host:
+  description: The IP address of your controller, e.g., http://192.168.1.1.
+  required: false
+  type: string
+{% endconfiguration %}

source/_components/cloud.alexa.markdown

@@ -0,0 +1,119 @@
+---
+layout: page
+title: "Alexa via Home Assistant Cloud"
+description: "Enable the Alexa integration via Home Assistant Cloud integration."
+date: 2017-11-17 20:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: home-assistant.png
+ha_release: 0.60
+ha_category: Cloud
+ha_iot_class: "Cloud Push"
+---
+
+The Alexa integration allows users to control the entities via the [Home Assistant Smart Home skill for Alexa][alexa skill]. This means that you can say things like "Alexa, turn on the kitchen light" to control your local Home Assistant.
+
+To use this integration, you need to have:
+
+ - The cloud component set up. [Learn more](/components/cloud/)
+ - An Alexa enabled device like the Amazon Echo
+ - Activated the [Home Assistant Smart Home skill for Alexa][alexa skill]
+
+<p class='note warning'>Only Amazon US is currently supported. Other regions are being certified.</p>
+
+You can use `configuration.yaml` to configure the entities that are being shown to Alexa and how they are exposed.
+
+```yaml
+# Example configuration.yaml entry configuring Alexa
+cloud:
+  alexa:
+    filter:
+      include_entities:
+        - light.kitchen
+        - light.kitchen_left
+      include_domains:
+        - switch
+      exclude_entities:
+        - switch.outside
+    entity_config:
+      light.kitchen:
+        name: Custom Name for Alexa
+        description: The light in the kitchen
+      switch.stairs:
+        display_categories: LIGHT
+```
+
+{% configuration %}
+alexa:
+  description: Configuration options for the Amazon Alexa integration.
+  required: false
+  type: map
+  keys:
+    filter:
+      description: Filters for entities to include/exclude from Alexa.
+      required: false
+      type: map
+      keys:
+        include_entities:
+          description: Entity IDs to include.
+          required: false
+          type: list
+        include_domains:
+          description: Domains to include.
+          required: false
+          type: list
+        exclude_entities:
+          description: Entity IDs to exclude.
+          required: false
+          type: list
+        exclude_domains:
+          description: Domains to exclude.
+          required: false
+          type: list
+    entity_config:
+      description: Entity specific configuration for Alexa
+      required: false
+      type: map
+      keys:
+        '`<ENTITY_ID>`':
+          description: Entity to configure
+          required: false
+          type: map
+          keys:
+            name:
+              description: Name of entity to show in Alexa
+              required: false
+              type: string
+            description:
+              description: Description of entity to show in Alexa
+              required: false
+              type: string
+            display_categories:
+              description: The display category to use in Alexa. [Available categories](https://developer.amazon.com/docs/device-apis/alexa-discovery.html#display-categories)
+              required: false
+              type: string
+{% endconfiguration %}
+
+### {% linkable_title Possible values for customizing %}
+
+_Configuration via `customize:` is no longer available. Use the entity config as described above._
+
+### {% linkable_title Available domains %}
+Currently, the following domains are available to be used with Alexa:
+
+- alert
+- automation (enables/disables)
+- cover
+- fan (supports on/off and set speed)
+- group
+- input_boolean
+- light
+- lock (lock and unlock, but unlock is untested as Amazon has disabled unlock for now)
+- media_player (play, pause, stop, set volume, adjust volume, next track, and previous track)
+- scene
+- script (enables/disables)
+- switch
+
+[alexa skill]: https://alexa.amazon.com/spa/index.html#skills/dp/B0772J1QKB/?ref=skill_dsk_skb_sr_2

source/_components/cloud.google_assistant.markdown

@@ -0,0 +1,98 @@
+---
+layout: page
+title: "Google Assistant via Home Assistant Cloud"
+description: "Enable the Google Assistant via Home Assistant Cloud integration."
+date: 2017-11-17 20:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: home-assistant.png
+ha_release: 0.61
+ha_category: Cloud
+ha_iot_class: "Cloud Push"
+published: false
+---
+
+The Google Assistant integration allows users to control the entities via the Home Assistant Smart Home skill for Google Assistant. This means that you can say things like "Ok Google, turn on the kitchen light" to control your local Home Assistant.
+
+To use this integration, you need to have:
+
+ - The cloud component set up. [Learn more](/components/cloud/)
+ - A Google Assistant enabled device like the Google Home
+ - Activated the Home Assistant Smart Home skill for Google Assistant
+
+You can use `configuration.yaml` to configure the entities that are being shown to Google Assistant and how they are exposed.
+
+```yaml
+# Example configuration.yaml entry configuring Google Assistant
+cloud:
+  google_actions:
+    filter:
+      include_entities:
+        - light.kitchen
+        - light.kitchen_left
+      include_domains:
+        - switch
+      exclude_entities:
+        - switch.outside
+    entity_config:
+      switch.kitchen:
+        name: Custom Name for Alexa
+        aliases:
+         - bright lights
+         - entry lights
+        type: 'action.devices.types.LIGHT'
+```
+
+{% configuration %}
+google_actions:
+  description: Configuration options for the Google Assistant integration.
+  required: false
+  type: map
+  keys:
+    filter:
+      description: Filters for entities to include/exclude from Alexa.
+      required: false
+      type: map
+      keys:
+        include_entities:
+          description: Entity IDs to include.
+          required: false
+          type: list
+        include_domains:
+          description: Domains to include.
+          required: false
+          type: list
+        exclude_entities:
+          description: Entity IDs to exclude.
+          required: false
+          type: list
+        exclude_domains:
+          description: Domains to exclude.
+          required: false
+          type: list
+    entity_config:
+      description: Entity specific configuration for Google Assistant
+      required: false
+      type: map
+      keys:
+        '`<ENTITY_ID>`':
+          description: Entity to configure
+          required: false
+          type: map
+          keys:
+            name:
+              description: Name of entity to show in Google Assistant
+              required: false
+              type: string
+            aliases:
+              description: Aliases that can also be used to refer to this entity
+              required: false
+              type: list
+            type:
+              description: Override the type of the entity in Google Assistant. [List of available types](https://developers.google.com/actions/smarthome/guides/)
+              required: false
+              type: string
+{% endconfiguration %}
+

source/_components/cloud.markdown

@@ -1,6 +1,6 @@
 ---
 layout: page
-title: "Cloud"
+title: "Home Assistant Cloud"
 description: "Enable the Home Assistant Cloud integration."
 date: 2017-11-17 20:00
 sidebar: true
@@ -13,95 +13,35 @@ ha_category: Voice
 ha_iot_class: "Cloud Push"
 ---
 
-The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services. Any processing of services from other cloud services is handled by your local Home Assistant.
+<p class='note'>The Home Assistant Cloud is currently in open beta and will become part of the upcoming Community Support Package. [Learn more](/blog/2017/12/17/introducing-home-assistant-cloud/)</p>
+
+The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services like Amazon Alexa.
+
+The following integrations are currently available:
+
+ - [Amazon Alexa (Amazon Echo)](/components/cloud.alexa/)
+
+<!-- - [Google Assistant (Google Home)](/components/cloud.google_assistant/) -->
+
+### {% linkable_title How does it work? %}
+
+The Home Assistant Cloud has been designed with security in mind. When you activate the Cloud component, your instance will create a secure connection to the Home Assistant Cloud. There is no need for any further configuration or to expose your instance to the internet.
+
+Integrations like Alexa will deliver messages to our cloud which we will forward to your local instance for processing. We just forward the response back to Alexa. This means that we do not have to store the state of your house in our cloud, we’re just the messenger!
+
+You can find a list of frequently asked questions (and their answers) in [this blog post](/blog/2017/12/17/introducing-home-assistant-cloud/#faq).
+
+### {% linkable_title Enabling the cloud %}
+
+The Home Assistant Cloud is enabled by default. If not, add this to your configuration:
 
 ```yaml
 # Example configuration.yaml entry to enable the cloud component
 cloud:
 ```
 
-Once activated, go to the configuration panel in Home Assistant and create an account and log in. There is no need to configure your router or expose your instance to the internet in any other way.
+Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Configuration** panel, make sure you have the following option enabled in your configuration.yaml` file.
-
-If you are not seeing the **Configuration** panel, make sure you have the following option enabled in your configuration.yaml` file.
 
 ```yaml
 config:
 ```
-
-### {% linkable_title Amazon Alexa %}
-
-The Alexa integration allows users to control the entities via the [Home Assistant Smart Home skill for Alexa][alexa skill]. This means that you can say things like "Alexa, turn on the kitchen light" to control your local instance.
-
-```yaml
-# Example configuration.yaml entry configuring Alexa
-cloud:
-  alexa:
-    filter:
-      include_entities:
-        - light.kitchen
-      include_domains:
-        - switch
-      exclude_entities:
-        - light.living_room
-      exclude_domains:
-        - script
-```
-
-{% configuration %}
-alexa:
-  description: Configuration options for the Amazon Alexa integration.
-  required: false
-  type: map
-  keys:
-    filter:
-      description: Filters for entities to include/exclude from Alexa.
-      required: false
-      type: map
-      keys:
-        include_entities:
-          description: Entity IDs to include.
-          required: false
-          type: list
-        include_domains:
-          description: Domains to include.
-          required: false
-          type: list
-        exclude_entities:
-          description: Entity IDs to exclude.
-          required: false
-          type: list
-        exclude_domains:
-          description: Domains to exclude.
-          required: false
-          type: list
-{% endconfiguration %}
-
-### {% linkable_title Possible values for customize %}
-
-| Attribute | Description |
-| --------- | ----------- |
-| `alexa_hidden` | Hide the entity from the Alexa smart home devices.
-| `alexa_name` | Defines name of the entity for a Alexa smart home device. Useful if you have an entity with a friendly name in a local language that you want to access using an English sounding name.
-| `alexa_description` | The description of the device in the Alexa smart home device list.
-| `alexa_display_categories` | Set displayCategories, useful for things like media_player (TV/SPEAKERS) or scene (ACTIVITY_TRIGGER/SCENE_TRIGGER). More info can be found [here](https://developer.amazon.com/docs/device-apis/alexa-discovery.html#display-categories).
-
-### {% linkable_title Available domains %}
-Currently, the following domains are available to be used with Alexa:
-- alert
-- automation (enables/disables)
-- cover
-- fan (supports on/off and set speed)
-- group
-- input_boolean
-- light
-- lock (lock and unlock, but unlock is untested as Amazon has disabled unlock for now)
-- media_player (play, pause, stop, set volume, adjust volume, next track and previous track)
-- scene
-- script (enables/disables)
-- 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).

source/_components/coinbase.markdown

@@ -0,0 +1,47 @@
+---
+layout: page
+title: "coinbase"
+description: "Instructions for how to add Coinbase sensors to Home Assistant."
+date: 2017-12-08 17:54
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: coinbase.png
+ha_release: 0.61
+ha_iot_class: "Cloud Polling"
+---
+
+
+The `coinbase` component lets you access account balances and exchange rates from [coinbase](https://coinbase.com).
+
+You will need to obtain an API key from coinbase's [developer site](https://www.coinbase.com/settings/api) to use this component. You need to give read access to `wallet:accounts` in order for the component to access relevant data. 
+
+To set it up, add the following information to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+coinbase:
+  api_key: asdfghjklqwertyuiopzxcvbnm 
+  api_secret: nkjnewncfghjklqwertyuiopzxcvbnm 
+  exchange_rate_currencies:
+    - BTC
+    - ETH
+    - LTC
+=======
+```
+
+{% configuration %}
+api_key:
+  description: Your API key to access coinbase.
+  required: true
+  type: string
+api_secret:
+  description: Your API secret to access coinbase.
+  required: true
+  type: string
+exchange_rate_currencies:
+  description: List of currencies to create exchange rate sensors for.
+  required: false
+  type: list
+{% endconfiguration %}

source/_components/cover.mqtt.markdown

@@ -35,33 +35,125 @@ cover:
     command_topic: "home-assistant/cover/set"
 ```
 
-Configuration variables:
+{% configuration %}
-
+name:
-- **name** (*Optional*): The name of the sensor. Default is `MQTT Cover`.
+  description: The name of the cover.
-- **command_topic** (*Optional*): The MQTT topic to publish commands to control the cover.
+  required: false
-- **payload_open** (*Optional*): The payload that opens the cover. Default is `OPEN`.
+  type: string
-- **payload_close** (*Optional*): The payload that closes the cover. Default is `CLOSE`.
+  default: MQTT Cover
-- **payload_stop** (*Optional*):  The payload that stops the cover. default is `STOP`.
+command_topic:
-- **state_topic** (*Optional*): The MQTT topic subscribed to receive cover state messages.
+  description: The MQTT topic to publish commands to control the cover.
-- **state_open** (*Optional*): The payload that represents the open state. Default is `open`.
+  required: false
-- **state_closed** (*Optional*): The payload that represents the closed state. Default is `closed`.
+  type: string
-- **availability_topic** (*Optional*): The MQTT topic subscribed to to receive birth and LWT messages from the MQTT cover device. If `availability_topic` is not defined, the cover availability state will always be "available". If `availability_topic` is defined, the cover availability state will be "unavailable" by default.
+payload_open:
-- **payload_available** (*Optional*): The payload that represents the online state. Default is `online`.
+  description: The command payload that opens the cover.
-- **payload_not_available** (*Optional*): The payload that represents the offline state. Default is `offline`.
+  required: false
-- **optimistic** (*Optional*): Flag that defines if switch works in optimistic mode. Default is `true` if no state topic defined, else `false`.
+  type: string
-- **qos** (*Optional*): The maximum QoS level to be used when receiving and publishing messages. Default is `0`.
+  default: OPEN
-- **retain** (*Optional*): Defines if published messages should have the retain flag set. Default is `false`.
+payload_close:
-- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
+  description: The command payload that closes the cover.
-- **set_position_topic** (*Optional*): The MQTT topic to publish position commands to.
+  required: false
-- **set_position_template** (*Optional*): Defines a [template](/topics/templating/) to define the position to be sent to the `set_position_topic` topic. Incoming position value is available for use in the template `{{position}}`. If no template is defined, the numeric position (0-100) will be written directly to the topic.
+  type: string
-- **tilt_command_topic** (*Optional*): The MQTT topic to publish commands to control the cover tilt.
+  default: CLOSE
-- **tilt_status_topic** (*Optional*): The MQTT topic subscribed to receive tilt status update values.
+payload_stop:
-- **tilt_min** (*Optional*): The minimum tilt value. Default is `0`
+  description: The command payload that stops the cover.
-- **tilt_max** (*Optional*): The maximum tilt value. Default is `100`
+  required: false
-- **tilt_closed_value** (*Optional*): The value that will be sent on a `close_cover_tilt` command. Default is `0`
+  type: string
-- **tilt_opened_value** (*Optional*): The value that will be sent on an `open_cover_tilt` command. Default is `100`
+  default: STOP
-- **tilt_status_optimistic** (*Optional*): Flag that determines if tilt works in optimistic mode. Default is `true` if `tilt_status_topic` is not defined, else `false`
+state_topic:
-- **tilt_invert_state** (*Optional*): Flag that determines if open/close are flipped; higher values toward closed and lower values toward open. Default is `False`
+  description: The MQTT topic subscribed to receive cover state messages.
+  required: false
+  type: string
+state_open:
+  description: The payload that represents the open state.
+  required: false
+  type: string
+  default: open
+state_closed:
+  description: The payload that represents the closed state.
+  required: false
+  type: string
+  default: closed
+availability_topic:
+  description: "The MQTT topic subscribed to to receive birth and LWT messages from the MQTT cover device. If `availability_topic` is not defined, the cover availability state will always be `available`. If `availability_topic` is defined, the cover availability state will be `unavailable` by default."
+  required: false
+  type: string
+payload_available:
+  description: The payload that represents the online state.
+  required: false
+  type: string
+  default: online
+payload_not_available:
+  description: The payload that represents the offline state.
+  required: false
+  type: string
+  default: offline
+optimistic:
+  description: Flag that defines if switch works in optimistic mode.
+  required: false
+  type: string
+  default: "`true` if no state topic defined, else `false`."
+qos:
+  description: The maximum QoS level to be used when receiving and publishing messages.
+  required: false
+  type: integer
+  default: 0
+retain:
+  description: Defines if published messages should have the retain flag set.
+  required: false
+  type: boolean
+  default: false
+value_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload."
+  required: false
+  type: string
+set_position_topic:
+  description: The MQTT topic to publish position commands to.
+  required: false
+  type: string
+set_position_template:
+  description: " Defines a [template](/topics/templating/) to define the position to be sent to the `set_position_topic` topic. Incoming position value is available for use in the template `{{position}}`. If no template is defined, the numeric position (0-100) will be written directly to the topic."
+  required: false
+  type: string
+tilt_command_topic:
+  description: The MQTT topic to publish commands to control the cover tilt.
+  required: false
+  type: string
+tilt_status_topic:
+  description: The MQTT topic subscribed to receive tilt status update values.
+  required: false
+  type: string
+tilt_min:
+  description: The minimum tilt value.
+  required: false
+  type: integer
+  default: 0
+tilt_max:
+  description: The maximum tilt value
+  required: false
+  type: integer
+  default: 100
+tilt_closed_value:
+  description: The value that will be sent on an `close_cover_tilt` command.
+  required: false
+  type: integer
+  default: 0
+tilt_opened_value:
+  description: The value that will be sent on an `open_cover_tilt` command.
+  required: false
+  type: integer
+  default: 0
+tilt_status_optimistic:
+  description: Flag that determines if tilt works in optimistic mode.
+  required: false
+  type: boolean
+  default: "`true` if `tilt_status_topic` is not defined, else `false`"
+tilt_invert_state:
+  description: Flag that determines if open/close are flipped; higher values toward closed and lower values toward open.
+  required: false
+  type: boolean
+  default: false
+{% endconfiguration %}
 
 ## {% linkable_title Examples %}
 
@@ -78,7 +170,7 @@ cover:
     name: "MQTT Cover"
     command_topic: "home-assistant/cover/set"
     state_topic: "home-assistant/cover/state"
-    availability_topic: "home-assistant/cover/availability"    
+    availability_topic: "home-assistant/cover/availability"
     qos: 0
     retain: true
     payload_open: "OPEN"

source/_components/daikin.markdown

@@ -0,0 +1,63 @@
+---
+layout: page
+title: "Daikin AC"
+description: "Instructions on how to integrate Hive devices with Home Assistant."
+date: 2017-12-10 21:00
+sidebar: false
+comments: false
+sharing: true
+footer: true
+logo: N/A
+ha_category: Climate
+ha_release: 0.59
+ha_iot_class: "Local Polling"
+---
+
+### Description ###
+
+The component integrates Daikin air conditioning systems into Home Assistant.
+
+To automatically add all your Daikin devices (ACs and associated sensors) into your Home Assistant installation, add the following to your 'configuration.yaml' file:
+
+<p class='note warning'>
+    Please note, the Daikin platform integrates **ONLY the european versions of Daikin ACs (models BRP069A41, 42, 43, 45)** into Home Assistant
+</p>
+
+```yaml
+# Example configuration.yaml entry
+daikin:
+  hosts:
+    - 192.168.4.161
+
+  monitored_conditions:
+    - inside_temperature  
+    - outside_temperature  
+    
+```
+
+{% configuration %}
+hosts:
+  description: List of IP addresses or hostnames.
+  required: true
+  type: array
+monitored_conditions:
+  description: List of items you want to monitor for each device.
+  required: false
+  detault: All conditions
+  type: list
+  keys:
+    inside_temperature:
+      description: The current temperature measured inside the house.
+    outside_temperature:
+      description: The current temperature measured outside the house.      
+{% endconfiguration %}
+
+<p class='note warning'>
+    Please note that some AC devices may report outside temperature only when they are turned on.
+</p>
+
+
+The Daikin Home Assistant platform currently supports the following Hive devices:
+
+- [Climate](/components/climate.daikin)
+- [Sensor](/components/sensor.daikin)

source/_components/deconz.markdown

@@ -0,0 +1,148 @@
+---
+layout: page
+title: "deCONZ"
+description: "Instructions on how to setup Conbee/Raspbee devices with deCONZ from Dresden Elektronik within Home Assistant."
+date: 2017-11-12 16:30
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: deconz.jpeg
+ha_category: Hub
+ha_release: "0.61"
+ha_iot_class: "Local Push"
+---
+
+[deCONZ](https://www.dresden-elektronik.de/funktechnik/products/software/pc/deconz/) by [Dresden Elektronik](https://www.dresden-elektronik.de) is a software that communicates with Conbee/Raspbee Zigbee gateways and exposes Zigbee devices that are connected to the gateway.
+
+[deCONZ REST API](http://dresden-elektronik.github.io/deconz-rest-doc/).
+
+Home Assistant will automatically discover deCONZ presence on your network, if `discovery:` is present in your `configuration.yaml` file.
+
+If you don't have the API key, you can generate an API key for deCONZ by using the one-click functionality similar to Philips Hue. Go to Menu->Settings->Unlock Gateway in deCONZ and then use the deCONZ configurator in Home Assistant GUI to create an API key. When you've generated the API key from Home Assistant, the API key will be stored in deconz.conf inside the home-assistant folder.
+
+You can add the following to your configuration.yaml file if you are not using the `discovery:` component:
+
+```yaml
+# Example configuration.yaml entry
+deconz:
+  host: IP ADDRESS
+```
+
+#### {% linkable_title Supported Device types %}
+
+- [Zigbee Lights](/components/light/deconz/)
+- [Humidity Sensors](/components/sensor/deconz/)
+- [Light Level Sensors](/components/sensor/deconz/)
+- [OpenClose Detectors](/components/binary_sensor/deconz/)
+- [Presence Detectors](/components/binary_sensor/deconz/)
+- [Pressure Sensors](/components/sensor/deconz/)
+- [Switches (Remote Controls)](/components/sensor/deconz/)
+- [Temperature Sensors](/components/sensor/deconz/)
+
+{% configuration %}
+host:
+  description: The IP address of your deCONZ web server.
+  required: false
+  type: string
+api_key:
+  description: The API key to access your deCONZ web server.
+  required: false
+  type: string
+port:
+  description: Configure port deCONZ web server is accessible from.
+  required: false
+  default: 80
+  type: int
+{% endconfiguration %}
+
+A full configuration could look like this:
+
+```yaml
+# Example configuration.yaml entry
+deconz:
+  host: 127.0.0.1
+  api_key: 0123456789
+  port: 80
+```
+
+## {% linkable_title Device services %}
+Available services: `configure`.
+
+#### {% linkable_title Service `deconz/configure` %}
+Set attribute of device in Deconz using [Rest API](http://dresden-elektronik.github.io/deconz-rest-doc/rest/).
+
+| Service data attribute | Optional | Description |
+|-----------|----------|-------------|
+| `field` | No | String representing a specific device in deCONZ. |
+| `data` | No | Data is a JSON object with what data you want to alter. |
+
+{ "field": "/lights/1", "data": {"name": "light2"} }
+
+{ "field": "/config", "data": {"permitjoin": 60} }
+
+## {% linkable_title Remote control devices%}
+
+Remote controls (ZHASwitch category) will be not be exposed as a regular entity, but as events named 'deconz_event' with a payload of 'id' and 'event'. Id will be the device name from deCONZ and Event will be the momentary state of the switch. However, a sensor entity will be created that shows the battery level of the switch as reported by deCONZ, named sensor.device_name_battery_level.
+
+Typical values for switches, the event codes are 4 numbers where the first and last number are of interest here.
+
+| Switch code | Description |
+|-------------|-------------|
+| 1XXX | Button #1 up to #8 |
+| XXX1 | Button hold |
+| XXX2 | Button short release |
+| XXX3 | Button long release |
+
+Where for example on a Philips Hue Dimmer, 2001 would be holding the dim up button.
+
+## {% linkable_title Examples %}
+
+### {% linkable_title Step up and step down input number with wireless dimmer %}
+
+```yaml
+automation:
+  - alias: 'Toggle lamp from dimmer'
+    initial_state: 'on'
+    trigger:
+      platform: event
+      event_type: deconz_event
+      event_data:
+        id: remote_control_1
+        event: 1002
+    action:
+      service: light.toggle
+      entity_id: light.lamp
+
+  - alias: 'Increase brightness of lamp from dimmer'
+    initial_state: 'on'
+    trigger:
+      platform: event
+      event_type: deconz_event
+      event_data:
+        id: remote_control_1
+        event: 2002
+    action:
+      - service: light.turn_on
+        data_template:
+          entity_id: light.lamp
+          brightness: {% raw %}>
+            {% set bri = states.light.lamp.attributes.brightness | int %}
+            {{ [bri+30, 249] | min }}{% endraw %}
+
+  - alias: 'Decrease brightness of lamp from dimmer'
+    initial_state: 'on'
+    trigger:
+      platform: event
+      event_type: deconz_event
+      event_data:
+        id: remote_control_1
+        event: 3002
+    action:
+      - service: light.turn_on
+        data_template:
+          entity_id: light.lamp
+          brightness: {% raw %}>
+            {% set bri = states.light.lamp.attributes.brightness | int %}
+            {{ [bri-30, 0] | max }}{% endraw %}
+```

source/_components/device_tracker.gpslogger.markdown

@@ -19,7 +19,14 @@ To integrate GPSLogger in Home Assistant, add the following section to your `con
 # Example configuration.yaml entry
 device_tracker:
   - platform: gpslogger
+    password: !secret gpslogger_password
 ```
+{% configuration %}
+password:
+  description: Separate password for GPS Logger endpoint. If provided using regular API password to contact endpoint will result in 401 response.
+  required: false
+  type: string
+{% endconfiguration %}
 
 ## {% linkable_title Setup on your smartphone %}
 

source/_components/device_tracker.owntracks.markdown

@@ -32,6 +32,9 @@ Configuration variables:
 - **waypoints** (*Optional*): Owntracks users can define [waypoints](http://owntracks.org/booklet/features/waypoints/) (a.k.a regions) which are similar in spirit to Home Assistant zones. If this configuration variable is `True`, the Owntracks users who are in `waypoint_whitelist` can export waypoints from the device and Home Assistant will import them as zone definitions. Defaults to `True`.
 - **waypoint_whitelist** (*Optional*): A list of user names (as defined for [Owntracks](/components/device_tracker.owntracks/)) who can export their waypoints from Owntracks to Home Assistant.  This would be the `username` portion of the Base Topic Name, (e.g. owntracks/**username**/iPhone). Defaults to all users who are connected to Home Assistant via Owntracks.
 - **secret** (*Optional*): [Payload encryption key](http://owntracks.org/booklet/features/encrypt/). This is usable when communicating with a third-party untrusted server or a public server (where anybody can subscribe to any topic). By default the payload is assumed to be unencrypted (although the communication between Home Assistant and the server might still be encrypted). This feature requires the `libsodium` library to be present.
+- **mqtt_topic** (*Optional*): The topic to subscribe for Owntracks updates on your MQTT instance (defaults to `owntracks/#`).
+- **events_only** (*Optional*): Home Assistant will ignore all location updates and rely solely on geofence enter/leave events.
+- **region_mapping** (*Optional*): Dictionary to remap names of regions as configured in the Owntracks app to Home Assistant zones. Use this if you have multiple homes or Home Assistant instances and want to map a different label to 'home'. `key: value` maps Owntracks region `key` to Home Assistant zone `value`.
 
 A full sample configuration for the `owntracks` platform is shown below:
 
@@ -41,9 +44,14 @@ device_tracker:
   - platform: owntracks
     max_gps_accuracy: 200
     waypoints: True
+    mqtt_topic: "owntracks/#"
+    events_only: True
     waypoint_whitelist:
       - jon
       - ram
+    region_mapping:
+      cabin: home
+      office: work
 ```
 
 ### {% linkable_title Using Owntracks with other device trackers %}

source/_components/device_tracker.tile.markdown

@@ -25,9 +25,6 @@ device_tracker:
   - platform: tile
     username: email@address.com
     password: MY_PASSWORD_123
-    monitored_variables:
-      - TILE
-      - PHONE
 ```
 
 {% configuration %}
@@ -43,4 +40,8 @@ device_tracker:
     description: the Tile types to monitor; valid values are `TILE` and `PHONE` (default is for all types to be included)
     required: false
     type: list
+  show_inactive:
+    description: whether to show expired/disabled Tiles
+    required: false
+    type: boolean
 {% endconfiguration %}

source/_components/doorbird.markdown

@@ -30,3 +30,8 @@ Configuration variables:
 - **host** (*Required*): The LAN IP address or hostname of your device. You can find this by going to the [DoorBird Online check](http://www.doorbird.com/checkonline) and entering the information from the paper that was included in the box.
 - **username** (*Required*): The username of a non-administrator user account on the device.
 - **password** (*Required*): The password for the user specified.
+- **doorbell_events** (*Optional*): Setting this to `true` this will register a callback URL with the device so that events can be published to the event bus when the doorbell rings.
+
+<p class="note warning">
+Enabling `doorbell_events` will delete all other registered push notification services with the device every time Home Assistant starts. This will not affect notifications delivered by the DoorBird mobile app.
+</p>

source/_components/fan.insteon_local.markdown

@@ -14,21 +14,4 @@ ha_version: 0.48
 
 The `insteon_local` fan component lets you control your fan connected to an [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant.
 
-To integrate add a fan, configure your hub Insteon(local) with Home Assistant, add the following section to your `configuration.yaml` file:
+To get your insteon fans working with Home Assistant, follow the instructions for the general [Insteon local component](/components/insteon_local/). The fans will be automatically disovered and added to Home Assistant. The device names will be the Insteon address of the fans.
-
-```yaml
-# Example configuration.yaml platform entry
-insteon_local:
-  host: YOUR HUB IP
-  username: YOUR HUB USERNAME
-  password: YOUR HUB PASSWORD
-  timeout: 10
-  port: 25105
-```
-
-To add fans to your set-up, add the platform to your light configuration:
-```yaml
-fan:
-  - platform: insteon_local
-```
-

source/_components/fan.mqtt.markdown

@@ -30,30 +30,117 @@ fan:
     command_topic: "bedroom_fan/on/set"
 ```
 
-Configuration variables:
+{% configuration %}
-
+name:
-- **command_topic** (*Required*): The MQTT topic to publish commands to change the fan state.
+  description: The name of the fan.
-- **state_topic** (*Optional*): The MQTT topic subscribed to receive state updates.
+  required: false
-- **name** (*Optional*): The name of the fan. Default is 'MQTT Fan'.
+  type: string
-- **state_topic** (*Optional*): The MQTT topic subscribed to receive state updates.
+  default: MQTT Fan
-- **payload_on** (*Optional*): The payload that represents the running state. Default is "ON".
+command_topic:
-- **payload_off** (*Optional*): The payload that represents the stop state. Default is "OFF".
+  description: The MQTT topic to publish commands to change the fan state.
-- **state_value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the state.
+  required: true
-- **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
+  type: string
-- **optimistic** (*Optional*): Flag that defines if lock works in optimistic mode. Default is `true` if no state topic defined, else `false`.
+state_topic:
-- **retain** (*Optional*): If the published message should have the retain flag on or not.
+  description: The MQTT topic subscribed to receive state updates.
-- **oscillation_state_topic** (*Optional*): The MQTT topic subscribed to receive oscillation state updates.
+  required: false
-- **oscillation_command_topic** (*Optional*): The MQTT topic to publish commands to change the oscillation state.
+  type: string
-- **payload_oscillation_on** (*Optional*): The payload that represents the oscillation on state. Default is "oscillate_on".
+payload_on:
-- **payload_oscillation_off** (*Optional*): The payload that presents the oscillation off state. Default is "oscillate_off".
+  description: The payload that represents the running state.
-- **oscillation_value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the oscillation.
+  required: false
-- **speed_state_topic** (*Optional*): The MQTT topic subscribed to receive speed state updates.
+  type: string
-- **speed_command_topic** (*Optional*): The MQTT topic to publish commands to change speed state.
+  default: ON
-- **payload_low_speed** (*Optional*): The payload that represents the fan's low speed.
+payload_off:
-- **payload_medium_speed** (*Optional*): The payload that represents the fan's medium speed.
+  description: The payload that represents the stop state.
-- **payload_high_speed** (*Optional*): The payload that represents the fan's high speed.
+  required: false
-- **speed_value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the speed payload.
+  type: string
-- **speeds** array (*Optional*): Valid entries for the list are `off`, `low`, `medium`, and `high`.
+  default: OFF
+state_value_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the state."
+  required: false
+  type: string
+qos:
+  description: The maximum QoS level of the state topic.
+  required: false
+  type: integer
+  default: 0
+optimistic:
+  description: Flag that defines if lock works in optimistic mode
+  required: false
+  type: boolean
+  default: "`true` if no state topic defined, else `false`."
+retain:
+  description: If the published message should have the retain flag on or not.
+  required: false
+  type: boolean
+  default: true
+oscillation_state_topic:
+  description: The MQTT topic subscribed to receive oscillation state updates.
+  required: false
+  type: string
+oscillation_command_topic:
+  description: The MQTT topic to publish commands to change the oscillation state.
+  required: false
+  type: string
+payload_oscillation_on:
+  description: The payload that represents the oscillation on state.
+  required: false
+  type: string
+  default: oscillate_on
+payload_oscillation_off:
+  description: The payload that represents the oscillation off state.
+  required: false
+  type: string
+  default: oscillate_off
+oscillation_value_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the oscillation."
+  required: false
+  type: string
+speed_state_topic:
+  description: The MQTT topic subscribed to receive speed state updates.
+  required: false
+  type: string
+speed_command_topic:
+  description: The MQTT topic to publish commands to change speed state.
+  required: false
+  type: string
+payload_low_speed:
+  description: The payload that represents the fan's low speed.
+  required: false
+  type: string
+  default: low
+payload_medium_speed:
+  description: The payload that represents the fan's medium speed.
+  required: false
+  type: string
+  default: medium
+payload_high_speed:
+  description: The payload that represents the fan's high speed.
+  required: false
+  type: string
+  default: high
+speed_value_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the speed payload."
+  required: false
+  type: string
+speeds:
+  description: "List of speeds this fan is capable of running at. Valid entries are `off`, `low`, `medium`, and `high`."
+  required: false
+  type: string list
+availability_topic:
+  description: The MQTT topic subscribed to receive availability (online/offline) updates.
+  required: false
+  type: string
+payload_available:
+  description: The payload that represents the available state.
+  required: false
+  type: string
+  default: online
+payload_not_available:
+  description: The payload that represents the unavailable state.
+  required: false
+  type: string
+  default: offline
+{% endconfiguration %}
 
 <p class='note warning'>
 Make sure that your topics match exactly. `some-topic/` and `some-topic` are different topics.

source/_components/google_assistant.markdown

@@ -18,7 +18,7 @@ The `google_assistant` component allows you to control things via Google Assista
 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.
+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>
 
 To enable this, add the following lines to your `configuration.yaml` file:
@@ -35,26 +35,77 @@ google_assistant:
     - switch
     - light
     - group
+  entity_config:
+    switch.kitchen:
+      name: Custom Name for Alexa
+      aliases:
+        - bright lights
+        - entry lights
+      type: 'action.devices.types.LIGHT'
+    light.living_room:
+      expose: false
 ```
 
 Configuration variables:
 
-- **expose_by_default** (*Optional*): Expose devices in all supported domains by default.
+{% configuration %}
-- **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.
+project_id:
-- **access_token** (*Required*): Another different long random URL safe string.
+  description: Project ID from the Google Developer console (looks like `words-2ab12`)
-- **agent_user_id** (*Optional*): A string to identify the user, e.g., email address. If not provided, the component will generate one.
+  required: true
-- **api_key** (*Optional*): A Homegraph 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.
+  type: string
-- **exposed_domains** (*Optional*): An array of Home Assistant domains to expose to Google Assistant. Options include:
+client_id:
-    - `switch`
+  description: A long random URL safe string (no spaces or special characters) that will be used for Implicit OAuth (example `aBcDeFgHiJkLmNoP`)
-    - `light`
+  required: true
-    - `cover`
+  type: string
-    - `media_player`
+access_token:
-    - `group`
+  description: Another different long random URL safe string  (example `aBcDeFgHiJkLmNoP`)
-    - `fan`
+  required: true
-    - `scene`
+  type: string
-    - `script`
+agent_user_id:
-    - `climate`
+  description: A string to identify the user, e.g., email address. If not provided, the component will generate one.
+  required: false
+  type: string
+api_key:
+  description: 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.
+  required: false
+  type: string
+expose_by_default:
+  description: Expose devices in all supported domains by default.
+  required: false
+  default: True
+  type: boolean
+exposed_domains:
+  description: List of entity domains to expose to Google Assistant.
+  required: false
+  type: list
+entity_config:
+  description: Entity specific configuration for Google Assistant
+  required: false
+  type: map
+  keys:
+    '`<ENTITY_ID>`':
+      description: Entity to configure
+      required: false
+      type: map
+      keys:
+        name:
+          description: Name of the entity to show in Google Assistant
+          required: false
+          type: string
+        expose:
+          description: Force an entity to be exposed/excluded.
+          required: false
+          type: boolean
+        aliases:
+          description: Aliases that can also be used to refer to this entity
+          required: false
+          type: list
+        type:
+          description: Override the type of the entity in Google Assistant. [List of available types](https://developers.google.com/actions/smarthome/guides/)
+          required: false
+          type: string
+{% endconfiguration %}
 
 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:
 
@@ -64,31 +115,6 @@ $ cat /dev/urandom | fold -w 120 | head -n 1 | base64 -w 0 | tr -dc '0-9A-Za-z'
 
 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
-homeassistant:
-  customize:
-    master_bedroom_light:
-      google_assistant: true
-      google_assistant_name: bedroom light
-    bedroom_blinds:
-      aliases:
-        - bedroom shades
-        - bedroom covers
-    hallway_ceiling_switch:
-      google_assistant: true
-      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.
-
 ### {% linkable_title Setup %}
 
 1. Download the [gactions CLI](https://developers.google.com/actions/tools/gactions-cli) (you'll use this later) - you can download and run this anywhere and on any machine, just remember where you put it for later (and don't forget to run `chmod +x gactions`to make it executable on mac or linux)
@@ -132,8 +158,8 @@ Entity Customization Keys:
 8. If you haven't already added the component configuration to `configuration.yaml` and restarted Home Assistant, you'll be unable to continue until you have.
 8. Open the Google Assistant app and go into `Settings > Home Control`
 9. Click the `+` sign, and near the bottom, you should have `[test] your app name`. Selecting that should lead to you the screen where you can set rooms for your devices or nicknames for your devices.
-10. If you want to allow other houshold users to control the devices:
+10. If you want to allow other household users to control the devices:
-	1. Go to the developer console using address from point 4.
+	1. Go to the developer console using the address from point 4.
 	2. Under the gear icon, click `Permissions`
 	3. Click `Add`, type the new user's e-mail address and choose `Project -> Editor` role
 	4. Have the new user go to [developer console](https://console.actions.google.com/) and repeat steps starting from point 7.
@@ -143,11 +169,14 @@ Entity Customization Keys:
 	3. Go to Credentials and select API Key from Create Credentials
 	4. Note down the generated API Key and use this in the configuration
 
-*Note:* The request_sync service requires that the initial sync from Google includes the agent_user_id. If not, the service will log an error that reads something like "Request contains an invalid argument". If this happens, then [unlink the account](https://support.google.com/googlehome/answer/7506443?hl=en-GB) from Home Control and relink. 
+### {% linkable_title Troubleshooting the request_sync service %}
 
-*Note:* The request_sync service may fail with a 404 if the project_id of the Homegraph API differs from the project_id of the Actions SDK found in the preferences of your project on [developer console](https://console.actions.google.com). Resolve this by:
+The request_sync service requires that the initial sync from Google includes the agent_user_id. If not, the service will log an error that reads something like "Request contains an invalid argument". If this happens, then [unlink the account](https://support.google.com/googlehome/answer/7506443?hl=en-GB) from Home Control and relink.
-	1. Removing your project on the [developer console](https://console.actions.google.com).
+
-	2. Add a new project in the [cloud console](https://console.cloud.google.com). Here you get a new project_id.
+The request_sync service may fail with a 404 if the project_id of the Homegraph API differs from the project_id of the Actions SDK found in the preferences of your project on [developer console](https://console.actions.google.com). Resolve this by:
-	3. Enable Homegraph API to the new project.
+
-	4. Generete a new API key.
+  1. Removing your project from the [developer console](https://console.actions.google.com).
-	5. Again create a new project in the [developer console](https://console.actions.google.com/). Described above. But at the step 'Build under the Actions SDK box' choose your newly created project. By this they share the same project_id.
+  2. Add a new project to the [cloud console](https://console.cloud.google.com). Here you get a new project_id.
+  3. Enable Homegraph API to the new project.
+  4. Generate a new API key.
+  5. Again create a new project in the [developer console](https://console.actions.google.com/). Described above. But at the step 'Build under the Actions SDK box' choose your newly created project. By this, they share the same project_id.

source/_components/history.markdown

@@ -71,7 +71,7 @@ history:
       - media_player
 ```
 
-Use the `include` list to define the domains/entities to display, and exclude some of them with in the `exclude` list. This makes sense if you for instance include the `sensor` domain, but want to exclude some specific sensors. Instead of adding every sensor entity to the `include` `entities` list just include the `sensor` domain and exclude the sensor entities you are not interested in.
+Use the `include` list to define the domains/entities to display, and exclude some of them within the `exclude` list. This makes sense if you, for instance, include the `sensor` domain, but want to exclude some specific sensors. Instead of adding every sensor entity to the `include` `entities` list just include the `sensor` domain and exclude the sensor entities you are not interested in.  Note that the order of any `include` `entities` will be displayed as listed in the configuration, otherwise, the display order is arbitrary.
 
 ```yaml
 # Example configuration.yaml entry with include and exclude

source/_components/hive.markdown

@@ -49,6 +49,7 @@ The Hive Home Assistant platform currently supports the following Hive devices:
 - Hive Active Heating (including hot water and Hive Multizone)
 - Hive Active Light Dimmable
 - Hive Active Light Cool to Warm White
+- Hive Active Light Colour Changing
 - Hive Active Plug
 - Hive Window or Door Sensor
 - Hive Motion Sensor

source/_components/insteon_local.markdown

@@ -33,9 +33,9 @@ Configuration variables:
 - **timeout** (*Optional*): Timeout to wait for connections. Defaults to 10 seconds.
 - **port** (*Optional*): The port your hub is configured to listen to. Defaults to `25105`.
 
-### {% linkable_title Full configuration %} 
+### {% linkable_title Full configuration %}
 
-The `insteon_local` component currently supports both lights (dimmers) and switches. A full configuration may look like so:
+The `insteon_local` component currently supports lights (dimmers), switches and fans.
 
 ```yaml
 insteon_local:
@@ -44,14 +44,4 @@ insteon_local:
   password: YOUR HUB PASSWORD
   timeout: 10
   port: 25105
-
-light:
-  - platform: insteon_local
-  
-switch:
-  - platform: insteon_local
-  
-fan:
-  - platform: insteon_local
 ```
-

source/_components/isy994.markdown

@@ -35,7 +35,8 @@ Configuration variables:
 - **username** (*Required*): The username that used to access the ISY interface.
 - **password** (*Required*): The password that used to access the ISY interface.
 - **sensor_string** (*Optional*): This is the string that is used to identify which devices are to be assumed to be sensors instead of lights of switches. By default, this string is 'sensor'. If this string is found in the device name or folder, Home Assistant will assume it is as a sensor or binary sensor (if the device has on/off or true/false states). This is only necessary for nodes that are not automatically detected as sensors by Home Assistant. Insteon door, window, motion and leak sensors should all be detected automatically.
-- **hidden_string** (*Optional*): The HIDDEN_STRING is a string that is used to identify which devices are to be hidden on Home Assistant's front page. This string will be stripped from the device's name before being used. By default, this value is '{HIDE ME}'.
+- **ignore_string** (*Optional*): Any devices that contain this string in their name (or folder path) will be ignored by Home Assistant. They will not become entities at all. The default value is `{IGNORE ME}`.
+- **enable_climate** (*Optional*): When enabled, climate measurements from the optional climate module in the ISY994 will show up in Home Assistant as sensors. The default value is `True`.
 - **tls** (*Optional*): This entry should reflect the version of TLS that the ISY controller is using for HTTPS encryption. This value can be either 1.1 or 1.2. If this value is not set, it is assumed to be version 1.1. This is the default for most users. ISY994 Pro users may likely be using 1.2. When using HTTPS in the host entry, it is best practice to set this value.
 
 Once the ISY controller is configured, it will automatically import any binary sensors, covers, fans, lights, locks, sensors and switches it can locate.

source/_components/light.deconz.markdown

@@ -0,0 +1,29 @@
+---
+layout: page
+title: "deCONZ lights"
+description: "Instructions on how to integrate Zigbee lights from deCONZ into Home Assistant."
+date: 2017-11-12 16:30
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: deconz.jpeg
+ha_category: Light
+ha_release: "0.61"
+ha_iot_class: "Local Push"
+---
+
+See the [deCONZ main component](/components/deconz/) for configuration instructions.
+
+Entity Ids names will be light.device_name, where device_name is defined in deCONZ. Light groups created in deCONZ will be created in Home Assistant as lights named light.group_name_in_deconz, allowing the user to control groups of lights with only a single API call to deCONZ.
+
+#### {% linkable_title Verified to be supported sensors %}
+
+- IKEA Trådfri bulb E14 WS opal 400lm
+- IKEA Trådfri Bulb E27 WS Opal 980lm
+- IKEA Trådfri Bulb E27 WS Opal 1000lm
+- IKEA Trådfri Bulb GU10 W 400lm
+- OSRAM Flex RGBW
+- OSRAM Gardenpole RGBW
+- Philips Hue White A19
+- Philips Hue White Ambiance A19

source/_components/light.greenwave.markdown

@@ -0,0 +1,41 @@
+---
+layout: page
+title: Greenwave Reality (TCP Connected) Lights
+description: "Instructions on how to set up Greenwave Reality lights within Home Assistant."
+date: 2017-11-17 18:50
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: greenwavereality.png
+ha_category: Light
+ha_release: 0.61
+ha_iot_class: "Local Polling"
+---
+
+This component communicates with the Greenwave Reality (TCP Connected) Gateway to allow control of all lights and fixtures registered to the gateway. Bulbs and Fixtures can be created and modified inside the TCP Lighting App for Android and iOS.
+
+This component has been tested on firmware revisions:
+
+- 2.0.105
+
+To configure the connection to the gateway, add the following to your `configuration.yaml` file:
+
+```yaml
+light:
+  - platform: greenwave
+    host: XXX.XXX.XXX.XXX
+    version: 3
+```
+The version option is the major revision of your firmware, which should be 2 or 3. If you are running Version 2, there are no extra steps. If you are running Version 3, you must press the Sync button on the gateway prior to the first launch of Home Assistant, so a token can be grabbed. Once home assistant has started, you can either press the Sync button again or wait for it to time out manually.
+
+{% configuration %}
+host:
+  description: The IP Address of your Gateway
+  required: true
+  type: string
+version:
+  description: Major version of the gateway firmware
+  required: true
+  type: integer
+{% endconfiguration %}

source/_components/light.hive.markdown

@@ -19,6 +19,7 @@ The 'hive' light component integrates your Hive lights into Home Assistant, enab
 The Hive light component supports the following Hive products:
 - **Hive Active Light Dimmable**
 - **Hive Active Light Cool to Warm White**
+- **Hive Active Light Colour Changing**
 
 
 <p class='note'>

source/_components/light.iglo.markdown

@@ -0,0 +1,42 @@
+---
+layout: page
+title: "iGlo"
+description: "Instructions on how to integrate iGlo lights into Home Assistant."
+date: 2017-12-17 08:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: iglo.png
+ha_category: Light
+ha_iot_class: "Local Polling"
+ha_release: 0.61
+---
+
+The `iglo` platform allows you to integrate your [iGlo Lights](https://www.youtube.com/watch?v=oHTS9ji_v-s) into Home Assistant.
+
+To use your iGlo light in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+light:
+  - platform: iglo
+    host: 192.168.1.10
+```
+
+{% configuration %}
+host:
+  required: true
+  description: The IP address for connecting to the light.
+  type: string
+name:
+  required: false
+  description: The name for this light.
+  default: iGlo Light
+  type: string
+port:
+  required: false
+  description: The port used to connect to the light.
+  default: 8080
+  type: integer
+{% endconfiguration %}

source/_components/light.insteon_local.markdown

@@ -15,22 +15,4 @@ ha_iot_class: "Local Push"
 
 The `insteon_local` light component lets you control your lights connected to an [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant.
 
-To integrate add a light, configure your hub Insteon(local) with Home Assistant, add the following section to your `configuration.yaml` file:
+To get your insteon lights working with Home Assistant, follow the instructions for the general [Insteon local component](/components/insteon_local/). The lights will be automatically disovered and added to Home Assistant. The device names will be the Insteon address of the lights.
-
-```yaml
-# Example configuration.yaml platform entry
-insteon_local:
-  host: YOUR HUB IP
-  username: YOUR HUB USERNAME
-  password: YOUR HUB PASSWORD
-  timeout: 10
-  port: 25105
-```
-
-To add lights (dimmers) to your set-up, add the platform to your light configuration:
-
-```yaml
-light:
-  - platform: insteon_local
-```
-

source/_components/light.mqtt.markdown

@@ -27,39 +27,153 @@ light:
     command_topic: "office/rgb1/light/switch"
 ```
 
-Configuration variables:
+{% configuration %}
-
+name:
-- **command_topic** (*Required*): The MQTT topic to publish commands to change the light's state.
+  description: The name of the light.
-- **brightness_command_topic** (*Optional*): The MQTT topic to publish commands to change the light's brightness.
+  required: false
-- **brightness_scale** (*Optional*): Defines the maximum brightness value (i.e. 100%) of the MQTT device (defaults to 255).
+  type: string
-- **brightness_state_topic** (*Optional*): The MQTT topic subscribed to receive brightness state updates.
+  default: MQTT Light
-- **brightness_value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the brightness value.
+command_topic:
-- **color_temp_command_topic** (*Optional*): The MQTT topic to publish commands to change the light's color temperature state.  The color temperature command slider has a range of 157 to 500 mireds (micro reciprocal degrees).
+  description: The MQTT topic to publish commands to change the switch state.
-- **color_temp_state_topic** (*Optional*): The MQTT topic subscribed to receive color temperature state updates.
+  required: true
-- **color_temp_value_template** (*Optional*): Defines a [template](/topics/templating/) to extract the color temperature value.
+  type: string
-- **effect_command_topic** (*Optional*): The MQTT topic to publish commands to change the light's effect state.
+brightness_command_topic:
-- **effect_state_topic** (*Optional*): The MQTT topic subscribed to receive effect state updates.
+  description: The MQTT topic to publish commands to change the light’s brightness.
-- **effect_value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the effect value.
+  required: false
-- **effect_list** (*Optional*): The list of effects the light supports.
+  type: string
-- **name** (*Optional*): The name of the switch. Default is 'MQTT Switch'.
+brightness_scale:
-- **on_command_type** (*Optional*): Defines when on the payload_on is sent. Using `last` (the default) will send any style (brightness, color, etc) topics first and then a `payload_on` to the `command_topic`. Using `first` will send the `payload_on` and then any style topics. Using `brightness` will only send brightness commands instead of the `payload_on` to turn the light on.
+  description: "Defines the maximum brightness value (i.e. 100%) of the MQTT device."
-- **optimistic** (*Optional*): Flag that defines if switch works in optimistic mode. Default is true if no state topic defined, else false.
+  required: false
-- **payload_off** (*Optional*): The payload that represents disabled state. Default is "OFF".
+  type: integer
-- **payload_on** (*Optional*): The payload that represents enabled state. Default is "ON".
+  default: 255
-- **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
+brightness_state_topic:
-- **retain** (*Optional*): If the published message should have the retain flag on or not.
+  description: The MQTT topic subscribed to receive brightness state updates.
-- **rgb_command_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to compose message which will be sent to `rgb_command_topic`. Available variables: `red`, `green` and `blue`.
+  required: false
-- **rgb_command_topic** (*Optional*): The MQTT topic to publish commands to change the light's RGB state.
+  type: string
-- **rgb_state_topic** (*Optional*): The MQTT topic subscribed to receive RGB state updates.
+brightness_value_template:
-- **rgb_value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the RGB value.
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the brightness value."
-- **state_topic** (*Optional*): The MQTT topic subscribed to receive state updates.
+  required: false
-- **state_value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the state value. The template should match the payload "on" and "off" values, so if your light uses "power on" to turn on, your `state_value_template` string should return "power on" when the switch is on. For example if the message is just "on", your `state_value_template` should be `power {{ value }}`.
+  type: string
-- **white_value_command_topic** (*Optional*): The MQTT topic to publish commands to change the light's white value.
+color_temp_command_topic:
-- **white_value_state_topic** (*Optional*): The MQTT topic subscribed to receive white value updates.
+  description: The MQTT topic to publish commands to change the light’s color temperature state. The color temperature command slider has a range of 157 to 500 mireds (micro reciprocal degrees).
-- **white_value_value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the white value.
+  required: false
-- **xy_command_topic** (*Optional*): The MQTT topic to publish commands to change the light's XY state.
+  type: string
-- **xy_state_topic** (*Optional*): The MQTT topic subscribed to receive XY state updates.
+color_temp_state_topic:
-- **xy_value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the XY value.
+  description: The MQTT topic subscribed to receive color temperature state updates.
+  required: false
+  type: string
+color_temp_value_template:
+  description: "Defines a [template](/topics/templating/) to extract the color temperature value."
+  required: false
+  type: string
+effect_command_topic:
+  description: "The MQTT topic to publish commands to change the light's effect state."
+  required: false
+  type: string
+effect_state_topic:
+  description: The MQTT topic subscribed to receive effect state updates.
+  required: false
+  type: string
+effect_value_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the effect value."
+  required: false
+  type: string
+effect_list:
+  description: The list of effects the light supports.
+  required: false
+  type: string list
+on_command_type:
+  description: "Defines when on the payload_on is sent. Using `last` (the default) will send any style (brightness, color, etc) topics first and then a `payload_on` to the `command_topic`. Using `first` will send the `payload_on` and then any style topics. Using `brightness` will only send brightness commands instead of the `payload_on` to turn the light on."
+  required: false
+  type: string
+optimistic:
+  description: Flag that defines if switch works in optimistic mode.
+  required: false
+  type: boolean
+  default: "`true` if no state topic defined, else `false`."
+payload_on:
+  description: The payload that represents enabled state.
+  required: false
+  type: string
+  default: ON
+payload_off:
+  description: The payload that represents disabled state.
+  required: false
+  type: string
+  default: OFF
+qos:
+  description: The maximum QoS level of the state topic.
+  required: false
+  type: integer
+  default: 0
+retain:
+  description: If the published message should have the retain flag on or not.
+  required: false
+  type: boolean
+  default: false
+rgb_command_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to compose message which will be sent to `rgb_command_topic`. Available variables: `red`, `green` and `blue`."
+  required: false
+  type: string
+rgb_command_topic:
+  description: "The MQTT topic to publish commands to change the light's RGB state."
+  required: false
+  type: string
+rgb_state_topic:
+  description: The MQTT topic subscribed to receive RGB state updates.
+  required: false
+  type: string
+rgb_value_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the RGB value."
+  required: false
+  type: string
+state_topic:
+  description: The MQTT topic subscribed to receive state updates.
+  required: false
+  type: string
+state_value_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the state value. The template should match the payload `on` and `off` values, so if your light uses `power on` to turn on, your `state_value_template` string should return `power on` when the switch is on. For example if the message is just `on`, your `state_value_template` should be `power {{ value }}`."
+  required: false
+  type: string
+white_value_command_topic:
+  description: "The MQTT topic to publish commands to change the light's white value."
+  required: false
+  type: string
+white_value_state_topic:
+  description: The MQTT topic subscribed to receive white value updates.
+  required: false
+  type: string
+white_value_value_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the white value."
+  required: false
+  type: string
+xy_command_topic:
+  description: "The MQTT topic to publish commands to change the light's XY state."
+  required: false
+  type: string
+xy_state_topic:
+  description: The MQTT topic subscribed to receive XY state updates.
+  required: false
+  type: string
+xy_value_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the XY value."
+  required: false
+  type: string
+availability_topic:
+  description: The MQTT topic subscribed to receive availability (online/offline) updates.
+  required: false
+  type: string
+payload_available:
+  description: The payload that represents the available state.
+  required: false
+  type: string
+  default: online
+payload_not_available:
+  description: The payload that represents the unavailable state.
+  required: false
+  type: string
+  default: offline
+{% endconfiguration %}
 
 <p class='note warning'>
   Make sure that your topics match exactly. `some-topic/` and `some-topic` are different topics.

source/_components/light.mqtt_json.markdown

@@ -48,23 +48,94 @@ light:
     command_topic: "home/rgb1/set"
 ```
 
-Configuration variables:
+{% configuration %}
-
+name:
-- **command_topic** (*Required*): The MQTT topic to publish commands to change the light's state.
+  description: The name of the light.
-- **brightness** (*Optional*): Flag that defines if the light supports brightness. Default is false.
+  required: false
-- **color_temp** (*Optional*): Flag that defines if the light supports color temperature. Default is false.
+  type: string
-- **effect** (*Optional*): Flag that defines if the light supports effects. Default is false.
+  default: MQTT JSON Light
-- **effect_list** (*Optional*): The list of effects the light supports.
+command_topic:
-- **flash_time_long** (*Optional*): The duration, in seconds, of a "long" flash. Default is 10.
+  description: The MQTT topic to publish commands to change the light’s state.
-- **flash_time_short** (*Optional*): The duration, in seconds, of a "short" flash. Default is 2.
+  required: true
-- **name** (*Optional*): The name of the light. Default is "MQTT JSON Light."
+  type: string
-- **optimistic** (*Optional*): Flag that defines if the light works in optimistic mode. Default is true if no state topic defined, else false.
+brightness:
-- **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
+  description: Flag that defines if the light supports brightness.
-- **retain** (*Optional*): If the published message should have the retain flag on or not.
+  required: false
-- **rgb** (*Optional*): Flag that defines if the light supports RGB colors. Default is false.
+  type: boolean
-- **state_topic** (*Optional*): The MQTT topic subscribed to receive state updates.
+  default: false
-- **white_value** (*Optional*): Flag that defines if the light supports white values. Default is false.
+color_temp:
-- **xy** (*Optional*): Flag that defines if the light supports XY colors. Default is false.
+  description: Flag that defines if the light supports color temperature.
+  required: false
+  type: boolean
+  default: false
+effect:
+  description: Flag that defines if the light supports effects.
+  required: false
+  type: boolean
+  default: false
+effect_list:
+  description: The list of effects the light supports.
+  required: false
+  type: string list
+flash_time_long:
+  description: The duration, in seconds, of a “long” flash.
+  required: false
+  type: integer
+  default: 10
+flash_time_short:
+  description: The duration, in seconds, of a “short” flash.
+  required: false
+  type: integer
+  default: 2
+optimistic:
+  description: Flag that defines if the light works in optimistic mode.
+  required: false
+  type: boolean
+  default: "`true` if no state topic defined, else `false`."
+qos:
+  description: The maximum QoS level of the state topic.
+  required: false
+  type: integer
+  default: 0
+retain:
+  description: If the published message should have the retain flag on or not.
+  required: false
+  type: boolean
+  default: false
+rgb:
+  description: Flag that defines if the light supports RGB colors.
+  required: false
+  type: boolean
+  default: false
+state_topic:
+  description: The MQTT topic subscribed to receive state updates.
+  required: false
+  type: string
+white_value:
+  description: Flag that defines if the light supports white values.
+  required: false
+  type: boolean
+  default: false
+xy:
+  description: Flag that defines if the light supports XY colors.
+  required: false
+  type: boolean
+  default: false
+availability_topic:
+  description: The MQTT topic subscribed to receive availability (online/offline) updates.
+  required: false
+  type: string
+payload_available:
+  description: The payload that represents the available state.
+  required: false
+  type: string
+  default: online
+payload_not_available:
+  description: The payload that represents the unavailable state.
+  required: false
+  type: string
+  default: offline
+{% endconfiguration %}
 
 <p class='note warning'>
   Make sure that your topics match exact. `some-topic/` and `some-topic` are different topics.

source/_components/light.mqtt_template.markdown

@@ -33,24 +33,89 @@ light:
     command_off_template: "off"
 ```
 
-Configuration variables:
+{% configuration %}
-
+name:
-- **name** (*Optional*): The name of the light. Default is "MQTT Template Light."
+  description: The name of the light.
-- **effect_list** (*Optional*): List of possible effects.
+  required: false
-- **command_topic** (*Required*): The MQTT topic to publish commands to change the light's state.
+  type: string
-- **state_topic** (*Optional*): The MQTT topic subscribed to receive state updates.
+  default: MQTT Template Light
-- **command_on_template** (*Required*): The [template](/docs/configuration/templating/#processing-incoming-data) for *on* state changes. Available variables: `state`, `brightness`, `red`, `green`, `blue`, `flash`, `transition` and `effect`.
+effect_list:
-- **command_off_template** (*Required*): The [template](/docs/configuration/templating/#processing-incoming-data) for *off* state changes. Available variables: `state` and `transition`.
+  description: List of possible effects.
-- **state_template** (*Optional*): [Template](/docs/configuration/templating/#processing-incoming-data) to extract state from the state payload value.
+  required: false
-- **brightness_template** (*Optional*): [Template](/docs/configuration/templating/#processing-incoming-data) to extract brightness from the state payload value.
+  type: string list
-- **red_template** (*Optional*): [Template](/docs/configuration/templating/#processing-incoming-data) to extract red color from the state payload value.
+command_topic:
-- **green_template** (*Optional*): [Template](/docs/configuration/templating/#processing-incoming-data) to extract green color from the state payload value.
+  description: The MQTT topic to publish commands to change the light’s state.
-- **blue_template** (*Optional*): [Template](/docs/configuration/templating/#processing-incoming-data) to extract blue color from the state payload value.
+  required: true
-- **color_temp_template** (*Optional*): [Template](/docs/configuration/templating/#processing-incoming-data) to extract color temperature from the state payload value.
+  type: string
-- **effect_template** (*Optional*): [Template](/docs/configuration/templating/#processing-incoming-data) to extract effect from the state payload value.
+state_topic:
-- **white_value_template** (*Optional*): [Template](/docs/configuration/templating/#processing-incoming-data) to extract white value from the state payload value.
+  description: The MQTT topic subscribed to receive state updates.
-- **optimistic** (*Optional*): Flag that defines if the light works in optimistic mode. Default is true if no state topic or state template is defined, else false.
+  required: false
-- **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
+  type: string
+command_on_template:
+  description: "The [template](/docs/configuration/templating/#processing-incoming-data) for *on* state changes. Available variables: `state`, `brightness`, `red`, `green`, `blue`, `flash`, `transition` and `effect`."
+  required: true
+  type: string
+command_off_template:
+  description: "The [template](/docs/configuration/templating/#processing-incoming-data) for *off* state changes. Available variables: `state` and `transition`."
+  required: true
+  type: string
+state_template:
+  description: "[Template](/docs/configuration/templating/#processing-incoming-data) to extract state from the state payload value."
+  required: false
+  type: string
+brightness_template:
+  description: "[Template](/docs/configuration/templating/#processing-incoming-data) to extract brightness from the state payload value."
+  required: false
+  type: string
+red_template:
+  description: "[Template](/docs/configuration/templating/#processing-incoming-data) to extract red color from the state payload value."
+  required: false
+  type: string
+green_template:
+  description: "[Template](/docs/configuration/templating/#processing-incoming-data) to extract green color from the state payload value."
+  required: false
+  type: string
+blue_template:
+  description: "[Template](/docs/configuration/templating/#processing-incoming-data) to extract blue color from the state payload value."
+  required: false
+  type: string
+color_temp_template:
+  description: "[Template](/docs/configuration/templating/#processing-incoming-data) to extract color temperature from the state payload value."
+  required: false
+  type: string
+effect_template:
+  description: "[Template](/docs/configuration/templating/#processing-incoming-data) to extract effect from the state payload value."
+  required: false
+  type: string
+white_value_template:
+  description: "[Template](/docs/configuration/templating/#processing-incoming-data) to extract white value from the state payload value."
+  required: false
+  type: string
+optimistic:
+  description: Flag that defines if the light works in optimistic mode.
+  required: false
+  type: string
+  default: "`true` if no state topic or state template is defined, else `false`."
+qos:
+  description: The maximum QoS level of the state topic.
+  required: false
+  type: integer
+  default: 0
+availability_topic:
+  description: The MQTT topic subscribed to receive availability (online/offline) updates.
+  required: false
+  type: string
+payload_available:
+  description: The payload that represents the available state.
+  required: false
+  type: string
+  default: online
+payload_not_available:
+  description: The payload that represents the unavailable state.
+  required: false
+  type: string
+  default: offline
+{% endconfiguration %}
 
 <p class='note warning'>
   Make sure that your topics match exact. `some-topic/` and `some-topic` are different topics.

source/_components/light.tplink.markdown

@@ -1,7 +1,7 @@
 ---
 layout: page
-title: "TPLink Bulb"
+title: "TP-Link Bulb"
-description: "Instructions how to integrate TPLink bulbs into Home Assistant."
+description: "Instructions how to integrate TP-Link bulbs into Home Assistant."
 date: 2017-07-25 08:00
 sidebar: true
 comments: false
@@ -14,7 +14,7 @@ ha_release: "0.50"
 ---
 
 
-The `tplink` light platform allows you to control the state of your [TPLink smart bulb](http://www.tp-link.com/en/products/list-5609.html).
+The `tplink` light platform allows you to control the state of your [TP-Link smart bulb](http://www.tp-link.com/en/products/list-5609.html).
 
 Supported units:
 
@@ -23,7 +23,7 @@ Supported units:
 - LB120
 - LB130
 
-To use your TPLink light in your installation, add the following to your `configuration.yaml` file:
+To use your TP-Link light in your installation, add the following to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
@@ -32,9 +32,15 @@ light:
     host: IP_ADDRESS
 ```
 
-Configuration variables:
+{% configuration %}
-
+name:
-- **host** (*Required*): The IP address of your TP-Link bulb, eg. `192.168.1.32`.
+  description: The name to use when displaying this bulb.
-- **name** (*Optional*): The name to use when displaying this bulb.
+  required: false
-
+  type: string
+  default: TP-Link Light
+host:
+  description: "The IP address of your TP-Link bulb, eg. `192.168.1.32`."
+  required: true
+  type: string
+{% endconfiguration %}
 

source/_components/lock.mqtt.markdown

@@ -30,17 +30,64 @@ lock:
     command_topic: "home/frontdoor/set"
 ```
 
-Configuration variables:
+{% configuration %}
-
+name:
-- **command_topic** (*Required*): The MQTT topic to publish commands to change the lock state.
+  description: The name of the lock.
-- **name** (*Optional*): The name of the lock. Default is 'MQTT Lock'.
+  required: false
-- **state_topic** (*Optional*): The MQTT topic subscribed to receive state updates.
+  type: string
-- **payload_lock** (*Optional*): The payload that represents enabled/locked state. Default is "LOCK".
+  default: MQTT Lock
-- **payload_unlock** (*Optional*): The payload that represents disabled/unlocked state. Default is "UNLOCK".
+command_topic:
-- **optimistic** (*Optional*): Flag that defines if lock works in optimistic mode. Default is `true` if no `state_topic` defined, else `false`.
+  description: The MQTT topic to publish commands to change the lock state.
-- **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
+  required: true
-- **retain** (*Optional*): If the published message should have the retain flag on or not.
+  type: string
-- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
+state_topic:
+  description: The MQTT topic subscribed to receive state updates.
+  required: false
+  type: string
+payload_lock:
+  description: The payload that represents enabled/locked state.
+  required: false
+  type: string
+  default: LOCK
+payload_unlock:
+  description: The payload that represents disabled/unlocked state.
+  required: false
+  type: string
+  default: UNLOCK
+optimistic:
+  description: Flag that defines if lock works in optimistic mode.
+  required: false
+  type: string
+  default: "`true` if no `state_topic` defined, else `false`."
+qos:
+  description: The maximum QoS level of the state topic.
+  required: false
+  type: integer
+  default: 0
+retain:
+  description: If the published message should have the retain flag on or not.
+  required: false
+  type: boolean
+  default: false
+value_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload."
+  required: false
+  type: string
+availability_topic:
+  description: The MQTT topic subscribed to receive availability (online/offline) updates.
+  required: false
+  type: string
+payload_available:
+  description: The payload that represents the available state.
+  required: false
+  type: string
+  default: online
+payload_not_available:
+  description: The payload that represents the unavailable state.
+  required: false
+  type: string
+  default: offline
+{% endconfiguration %}
 
 <p class='note warning'>
 Make sure that your topics match exactly. `some-topic/` and `some-topic` are different topics.
@@ -58,7 +105,7 @@ The example below shows a full configuration for a MQTT lock.
 # Example configuration.yml entry
 lock:
   - platform: mqtt
-    name: Frontdoor 
+    name: Frontdoor
     state_topic: "home-assistant/frontdoor/"
     command_topic: "home-assistant/frontdoor/set"
     payload_lock: "LOCK"
@@ -69,7 +116,7 @@ lock:
     value_template: '{% raw %}{{ value.x }}{% endraw %}'
 ```
 
-Keep an eye on retaining messages to keep the state as you don't want to unlock your door by accident when you restart something. 
+Keep an eye on retaining messages to keep the state as you don't want to unlock your door by accident when you restart something.
 
 For a check you can use the command line tools `mosquitto_pub` shipped with `mosquitto` to send MQTT messages. This allows you to operate your lock manually:
 

source/_components/media_player.markdown

@@ -58,7 +58,7 @@ Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`,
 
 #### {% linkable_title Service `media_player/shuffle_set` %}
 
-Currently only supported on [Spotify](/components/media_player.spotify/), [MPD](/components/media_player.mpd/), [Kodi](/components/media_player.kodi/), and [Universal](/components/media_player.universal/).
+Currently only supported on [Spotify](/components/media_player.spotify/), [MPD](/components/media_player.mpd/), [Kodi](/components/media_player.kodi/), [Squeezebox](/components/media_player.squeezebox/) and [Universal](/components/media_player.universal/).
 
 | Service data attribute | Optional | Description                                          |
 | ---------------------- | -------- | ---------------------------------------------------- |

source/_components/media_player.monoprice.markdown

@@ -47,3 +47,25 @@ Configuration variables:
 - **port** (*Required*): The serial port to which Monoprice amplifier is connected
 - **zones** (*Required*): This is the list of zones available. Valid zones are 11,12,13,14,15,16. In case multiple Monoprice devices are stacked together the list of valid zones is extended by 21,22,23,24,25,26 for the second device and 31,32,33,34,35,36 for the third device. Each zone must have a name assigned to it.
 - **sources** (*Required*): The list of sources available. Valid source numbers are 1,2,3,4,5,6. Each source number corresponds to the input number on the Monoprice amplifier. Similar to zones, each source must have a name assigned to it.
+
+### {% linkable_title Service `snapshot` %}
+
+Take a snapshot of one or more zones' states. This service, and the following one are useful if you want to play a doorbell or notification sound and resume playback afterward. If no `entity_id` is provided, all zones are snapshotted.
+
+The following attributes are stored in a snapshot:
+- Power status (On/Off)
+- Mute status (On/Off)
+- Volume level
+- Source
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | yes | String or list of strings that point at `entity_id`s of zones.
+
+### {% linkable_title Service `restore` %}
+
+Restore a previously taken snapshot of one or more speakers. If no `entity_id` is provided, all zones are restored.
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | yes | String or list of strings that point at `entity_id`s of zones.

source/_components/media_player.squeezebox.markdown

@@ -33,3 +33,25 @@ Configuration variables:
 - **password** (*Optional*): The password, if password protection is enabled.
 
 <p class='note'>This platform now uses the web interface of the Logitech Media Server to send commands. The default port of the web interface is 9000. It is the same port that you use to access the LMS through your web browser. Originally, this platform used the telnet interface, which defaults to 9090. If you previously specified the port in your configuration file, you will likely need to update it.</p>
+
+### {% linkable_title Service `squeezebox_call_method` %}
+
+Call a custom Squeezebox JSONRPC API.
+
+See documentation for this interface on http://HOST:PORT/html/docs/cli-api.html?player= where HOST and PORT are the host name and port for your Logitech Media Server. 
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | no | Name(s) of the Squeezebox entities where to run the API method.
+| `command` | no | Command to pass to Logitech Media Server (p0 in the CLI documentation).
+| `parameters` | yes | Array of additional parameters to pass to Logitech Media Server (p1, ..., pN in the CLI documentation).
+
+This service can be used to integrate any Squeezebox action to an automation.
+
+It can also be used to target a Squeezebox from IFTT (or DialogFlow, Alexa...).
+
+For example, to play an album from your collection, create an IFTT applet like this:
+- Trigger: Google assistant, with sentence: `I want to listen to album $`
+- Action: JSON post query with such JSON body:  
+`{ "entity_id": "media_player.squeezebox_radio", "command": "playlist", "parameters": ["loadtracks", "album.titlesearch={{TextField}}"] }`  
+This can work with title search and basically any thing. The same wouldn't have worked by calling directly Squeezebox server as IFTT cannot escape the text field.

source/_components/media_player.yamaha.markdown

@@ -36,7 +36,9 @@ Configuration variables:
   default name (often model number) that is returned by the device.
 - **host** (*Optional*): IP address or hostname of the device
 - **source_ignore** (*Optional*): List of sources to hide in the front-end
-- **source_names** (*Optional*): Mapping of internal AVR source names to custom ones, allowing to rename e.g. `HDMI1` to `ChromeCast`
+- **source_names** (*Optional*): Mapping of internal AVR source names to custom ones, allowing one to rename e.g. `HDMI1` to `ChromeCast`
+- **zone_ignore** (*Optional*): List of zones to hide in the front-end
+- **zone_names** (*Optional*): Mapping of zone names to custom ones, allowing one to rename e.g. `Main_Zone` to `Family Room`
 
 ### {% linkable_title Discovery notes %}
 
@@ -76,6 +78,10 @@ media_player:
     source_names:
       HDMI1: "ChromeCast"
       AV4: "Vinyl"
+    zone_ignore:
+      - "Zone_2"
+    zone_names:
+      Main_Zone: "Family Room"
 ```
 
 ### {% linkable_title Example `play_media` script %}

source/_components/modbus.markdown

@@ -30,7 +30,10 @@ modbus:
 
 Configuration variables:
 
-- **type** (*Required*): Type of the connection to Modbus.
+- **type** (*Required*): Type of the connection to Modbus. Possible values are:
+  - *tcp*: Modbus TCP protocol according to "MODBUS Messaging Implementation Guide version 1.0b" provided by Schneider Automation, 
+  - *udp*: Modbus TCP form, but using UDP for transport (removes the overheads required for TCP),
+  - *rtuovertcp*: Modbus RTU message transmitted with a TCP/IP wrapper and sent over a network instead of serial lines.
 - **host** (*Required*): The IP address of your Modbus device, eg. 192.168.1.1.
 - **port** (*Required*): The port for the communication.
 - **timeout** (*Optional*): Timeout for slave response in seconds. (default: 3)
@@ -51,7 +54,7 @@ modbus:
 
 Configuration variables:
 
-- **type** (*Required*): Type of the connection to Modebus.
+- **type** (*Required*): Type of the connection to Modbus.
 - **method** (*Required*): Method of the connection to Modbus.
 - **port** (*Required*): The port where your Modbus device is connected to your Home Assistant host.
 - **baudrate** (*Required*): The speed for the serial connection.

source/_components/notify.pushsafer.markdown

@@ -2,7 +2,7 @@
 layout: page
 title: "Pushsafer"
 description: "Instructions how to add Pushsafer notifications to Home Assistant."
-date: 2017-02-17 20:46
+date: 2018-01-05 11:15
 sidebar: true
 comments: false
 sharing: true
@@ -27,11 +27,78 @@ notify:
     private_key: ABCDEFGHJKLMNOPQRSTUVXYZ
 ```
 
-Configuration variables:
+**Configuration variables:**
 
 - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
 - **private_key** (*Required*): Your private or alias key. Private key = send the notification to all devices with standard params, alias key send the notification to the devices stored in the alias with predefined params.
 
+### {% linkable_title Examples %}
+
+Message to two devices with formated text.
+
+```json
+{
+  "title": "Test to 2 devices",
+  "message": "Attention [b]bold[/b] text[br][url=https://www.pushsafer.com]Link to Pushsafer[/url]",
+  "target": ["1111", "2222"],
+  "data": {
+    "icon": "2", 
+    "iconcolor": "#FF0000",
+    "sound": "2",
+    "vibration": "1",
+    "url": "https://home-assistant.io/",
+    "urltitle": "Open Home Assistant",
+    "time2live": "0"
+  }
+}
+```
+
+Message to one device with formated text and image from an external URL.
+
+```json
+{
+  "title": "Test to 1 device with image from an url",
+  "message": "Attention [i]italic[/i] Text[br][url=https://home-assistant.io/]Testlink[/url]",
+  "target": ["1111"],
+  "data": {
+    "icon": "14", 
+    "iconcolor": "#FFFF00",
+    "sound": "22",
+    "vibration": "3",
+    "url": "https://home-assistant.io/",
+    "urltitle": "Open Home Assistant",
+    "time2live": "60",
+    "picture1": {
+       "url":"https://home-assistant.io/images/components/alexa/alexa-512x512.png"
+     }
+  }
+}
+```
+
+Message to two devices and one device group with formated text and local image.
+
+```json
+{
+  "title": "Test to 3 devices with local image",
+  "message": "Attention [i]italic[/i] Text[br][url=https://home-assistant.io/]Testlink[/url]",
+  "target": ["1111","2222","gs3333"],
+  "data": {
+    "icon": "20", 
+    "iconcolor": "#FF00FF",
+    "sound": "33",
+    "vibration": "0",
+    "url": "https://home-assistant.io/",
+    "urltitle": "Open Home Assistant",
+    "time2live": "10",
+    "picture1": {
+       "path":"C:\\Users\\Kevin\\AppData\\Roaming\\.homeassistant\\image-760-testimage.jpg"
+     }
+  }
+}
+```
+
+To customize your push-notification you can take a look at the [Pushsafer API description](https://www.pushsafer.com/en/pushapi).
+
 When setting up the application you can use this [icon](https://home-assistant.io/images/favicon-192x192.png).
 
 To use notifications, please see the [getting started with automation page](/getting-started/automation/).

source/_components/notify.webostv.markdown

@@ -33,7 +33,7 @@ Configuration variables:
 - **host** (*Required*): The IP of the LG WebOS Smart TV, e.g. 192.168.0.10
 - **name** (*Required*): The name you would like to give to the LG WebOS Smart TV.
 - **filename** (*Optional*): The filename where the pairing key with the TV should be stored. This path is relative to Home Assistant's config directory. It defaults to `webostv.conf`.
-- **icon** (*Optional*): The path to an image file to use as the icon in notifications. If provided, this image will override the Home Assistant logo.
+- **icon** (*Optional*): The path to an image file to use as the icon in notifications.
 
 A possible automation could be:
 

source/_components/nuheat.markdown

@@ -0,0 +1,51 @@
+---
+layout: page
+title: "NuHeat"
+description: "Instructions how to integrate your NuHeat Signature thermostats within Home Assistant."
+date: 2017-11-11 18:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: nuheat.png
+ha_category: Hub
+ha_release: 0.61
+ha_iot_class: "Cloud Polling"
+---
+
+The `nuheat` component lets you control connected floor heating thermostats from [NuHeat](http://www.nuheat.com/).
+
+First, you will need to obtain your thermostat's numeric serial number or ID by logging into [MyNuHeat.com](https://mynuheat.com/) and selecting your thermostat(s).
+
+Once you have the Thermostat ID(s), add the following information to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+nuheat:
+  username: you@example.com
+  password: very-secure-password
+  devices: 12345
+
+# Example configuration.yaml entry with multiple thermostats
+nuheat:
+  username: you@example.com
+  password: very-secure-password
+  devices:
+    - 12345
+    - 67890
+```
+
+{% configuration %}
+username:
+  description: The username for accessing your MyNuHeat account.
+  required: true
+  type: string
+password:
+  description: The password for accessing your MyNuHeat account.
+  required: true
+  type: string
+devices:
+  description: The serial number/ID of each thermostat you would like to integrate.
+  required: true
+  type: [string, int]
+{% endconfiguration %}

source/_components/rainbird.markdown

@@ -0,0 +1,33 @@
+---
+layout: page
+title: "Rain Bird"
+description: "Instructions on how to integrate your Rain Bird LNK WiFi Module within Home Assistant."
+date: 2017-12-07 12:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: rainbird.png
+ha_category: Hub
+ha_release: 0.61
+ha_iot_class: "Local Polling"
+---
+
+This `rainbird` component allows interacting with [LNK WiFi](http://www.rainbird.com/landscape/products/controllers/LNK-WiFi.htm) module of the Rain Bird Irrigation system in Home Assistant.
+
+To enable it, add the following to your `configuration.yaml` file:
+
+```yaml
+rainbird:
+  host: '1.1.1.1'
+  password: 'XXXXXXX'
+```
+
+Configuration variables:
+
+- **host** (*Required*): The IP address of your LNK WiFi Module.
+- **password** (*Required*): The password for accessing the module.
+
+Finish its configuration by visiting the [Rain Bird sensor](/components/sensor.rainbird/) and [Rain Bird switch](/components/switch.rainbird/) documentation.
+
+Please note that due to the implementation of the API within the LNK Module, there is a concurrency issue. For example, the Rain Bird app will give connection issues (like already a connection active).

source/_components/remember_the_milk.markdown

@@ -59,12 +59,61 @@ If the registration was successful, the Configuration panel will disappear from
 
 In the background Home Assistant downloaded a "token" from the Remember The Milk server which is stored in the `remember_the_milk.conf` file locally. So you only need to register once. After that the token is used to authenticate with the server.
 
-## {% linkable_title Creating tasks %}
+## {% linkable_title Creating/updating tasks with service ```create_task```%}
 
-This component offers a new service domain ```remember_the_milk``` with the service ```create_task```. You can call this service with the argument ```name``` to create a new task in your Remember The Milk account. You can call this service from your usual automations.
+This component offers a new service domain ```remember_the_milk``` with the services ```<account>_create_task```. You can call this service with the argument ```name``` and the optional parameter ```id``` to create a new task in your Remember The Milk account. You can call this service from your usual automations.
+
+If you set an ```id``` and a task with that id exists already, the existing task is updated, rather than creating a new task. This way you can change the name of the task. If you do not set an ```id```, a new task is created with every call. If you're using this from an automation, you could use the name of your automation as id or the entity that triggered the task to be created. This way you can later on update or complete this task.
 
 The task creation supports the "smart syntax", so to create a task with the tag "from_hass" which is due today you can create a task with the name ```test task created in Home Assistant ^today #from_hass```. More info about the smart syntax is available on the [Remember The Milk documentation](https://www.rememberthemilk.com/help/answer/basics-smartadd-howdoiuse).
 
+**Note:**
+At the moment, smart syntax is *not* supported when updating tasks. All smart syntax commands are ignored during the update and will end up as normal text in the name of the task.
+
+|Service data attribute	| Optional | Description | Example |
+|-----------------------|----------|-------------|---------|
+| name | no  | Name of the new task, you can use the smart syntax here. | "do this ^today #from_hass" |
+| id   | yes | Identifier for the task you're creating, can be used to update or complete the task later on | "myid" |
+
+## {% linkable_title Completing tasks with service  ```complete_task```%}
+
+Complete a tasks that was privously created from Home Assistant. You can not complete tasks that were created outside of Home Assistant.
+
+If you have created your task with an ```id```, calling ```<account>_complete_task``` with the parameter ```id``` will then complete your task. 
+
+|Service data attribute	| Optional | Description | Example |
+|-----------------------|----------|-------------|---------|
+| id | no | Identifier that was defined when creating the task | "myid" |
+
+## {% linkable_title Automation example %}
+
+Here's an example for an automation that creates a new task whenever ```sensor.mysensor``` is ```on``` and completes it when the sensor reports ```off```. This way it reminds you to switch it off. By using the ```entity_id``` as id for the task, you can use the same rule also for multiple sensors.
+
+
+```yaml
+- id: mysensor_on
+  trigger:
+    platform: state
+    entity_id: sensor.mysensor
+    to: on
+  action:
+    - service: remember_the_milk.myaccount_create_task
+      data_template:
+        name: "Please switch of {{trigger.entity_id}}"
+        id: "{{trigger.entity_id}}"
+- id: mysensor_off
+  trigger:
+    platform: state
+    entity_id: sensor.mysensor
+    to: off
+  action:
+    - service: remember_the_milk.myaccount_complete_task
+      data_template:
+        id: "{{trigger.entity_id}}"
+
+```
+
+
 
 ## {% linkable_title Disclaimer %}
 This product uses the Remember The Milk API but is not endorsed or certified by Remember The Milk.

source/_components/scene.deconz.markdown

@@ -0,0 +1,18 @@
+---
+layout: page
+title: "deCONZ scenes"
+description: "Instructions on how to integrate deCONZ scenes into Home Assistant."
+date: 2017-11-19 20:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: deconz.jpeg
+ha_category: Scene
+ha_release: "0.61"
+ha_iot_class: "Local Push"
+---
+
+See the [deCONZ main component](/components/deconz/) for configuration instructions.
+
+Entity Ids will be scene.group_scene_name, where group is which group the scene belongs to and the name of the scene, both group and name are defined in deCONZ.

source/_components/sensor.alpha_vantage.markdown

@@ -33,21 +33,58 @@ api_key:
 symbols:
   description: List of stock market symbols for given companies.
   required: false
-  type: string, list
   default: GOOGL
+  type: map
+  keys:
+    name:
+      description: The name of the sensor to use for the frontend.
+      required: false
+      type: string
+    currency:
+      description: The name of the sensor to use for the frontend.
+      required: false
+      type: string
+      default: USD
+    symbol:
+      description: The stock market symbol for the given company.
+      required: required
+      type: string
+foreign_exchange:
+  description: List of currencies.
+  type: map
+  required: false
+  keys:
+    name:
+      description: The name of the sensor to use for the frontend.
+      required: false
+      type: string
+    from:
+      description: The source currency.
+      required: required
+      type: string
+    to:
+      description: The target currency.
+      required: required
+      type: string
 {% endconfiguration %}
 
 ## {% linkable_title Examples %}
 
 In this section you find some real life examples of how to use this sensor.
 
-### {% linkable_title Red Hat and Google %}
+### {% linkable_title Google and the exchange rate for Bitcoin %}
 
 ```yaml
 sensor:
   - platform: alpha_vantage
+    api_key: YOUR_API_KEY
     symbols:
-      - RHT
+      - name: Google
-      - GOOGL
+        currency: USD
+        symbol: GOOGL
+    foreign_exchange:
+      - from: BTC
+        to: USD
+        name: Bitcoin
 ```
 

source/_components/sensor.coinbase.markdown

@@ -0,0 +1,15 @@
+---
+layout: page
+title: "Coinbase Sensor"
+description: "Instructions how to setup Coinbase sensors within Home Assistant."
+date: 2017-12-08 18:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: coinbase.png
+ha_category: Sensor
+ha_release: 0.61
+---
+
+To get your coinbase sensors working with Home Assistant, follow the instructions for the general [Coinbase component](/components/coinbase/).

source/_components/sensor.daikin.markdown

@@ -0,0 +1,61 @@
+---
+layout: page
+title: "Daikin AC"
+description: "Instructions on how to integrate Daikin AC(s) with Home Assistant."
+date: 2017-12-03 05:00
+sidebar: false
+comments: false
+sharing: true
+footer: true
+logo: N/A
+ha_category: Climate
+ha_release: 0.59
+ha_iot_class: "Local Polling"
+---
+
+### Description ###
+
+The sensor component integrates Daikin air conditioning systems into Home Assistant, enabling displaying the following parameters:
+- **inside temperature**
+- **outside temperature**
+
+<p class='note warning'>
+    Please note, the `daikin` platform integrates **ONLY the european versions of Daikin ACs (models BRP069A41, 42, 43, 45)** into Home Assistant
+</p>
+
+### Configuration ###
+
+Manual configuration and customization is possible by using the sample configuration from below:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: daikin
+      host: 10.0.0.1
+      name: optional name
+      monitored_conditions:
+        - inside_temperature  
+        - outside_temperature  
+      
+```
+
+{% configuration %}
+host:
+  description: IP or hostname of the device.
+  required: true
+  type: string
+monitored_conditions:
+  description: List of items you want to monitor for each device.
+  required: false
+  detault: All conditions
+  type: list
+  keys:
+    inside_temperature:
+      description: The current temperature measured inside the house.
+    outside_temperature:
+      description: The current temperature measured outside the house.
+{% endconfiguration %}
+
+<p class='note warning'>
+    Please note that some AC devices may report outside temperature only when they are turned on.
+</p>

source/_components/sensor.darksky.markdown

@@ -1,6 +1,6 @@
 ---
 layout: page
-title: "Dark Sky"
+title: "Dark Sky Sensor"
 description: "How to integrate Dark Sky within Home Assistant."
 date: 2016-09-26 08:00
 sidebar: true
@@ -20,7 +20,7 @@ The `darksky` platform uses the [Dark Sky](https://darksky.net/) web service as
 You need an API key which is free but requires [registration](https://darksky.net/dev/register). You can make up to 1000 calls per day for free which means that you could make one approximately every 86 seconds.
 
 <p class='note warning'>
-[Dark Sky](https://darksky.net/) will charge you $0.0001 per API call if you enter your credit card details and create more than 1000 calls per day.
+[Dark Sky](https://darksky.net/dev/) will charge you $0.0001 per API call if you enter your credit card details and create more than 1000 calls per day.
 </p>
 
 To add Dark Sky to your installation, add the following to your `configuration.yaml` file:
@@ -67,7 +67,7 @@ Configuration variables:
   - **apparent_temperature_min**: Today's expected apparent low temperature.
   - **precip_intensity_max**: Today's expected maximum intensity of precipitation.
   - **uv_index**: The current UV index.
-- **units** (*Optional*): Specify the unit system. Default to `si` or `us` based on the temperature preference in Home Assistant. Other options are `auto`, `us`, `si`, `ca`, and `uk2`.
+- **units** (*Optional*): Specify the unit system. Default to `si` or `us` based on the temperature preference in Home Assistant. Other options are `auto`, `us`, `si`, `ca`, `uk` and `uk2`.
 `auto` will let Dark Sky decide the unit system based on location.
 - **update_interval** (*Optional*): Minimum time interval between updates. Default is 2 minutes. Supported formats:
   - `update_interval: 'HH:MM:SS'`

source/_components/sensor.deconz.markdown

@@ -0,0 +1,45 @@
+---
+layout: page
+title: deCONZ Sensor
+description: "Instructions on how to integrate Zigbee sensors from deCONZ into Home Assistant."
+date: 2017-11-12 16:30
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: deconz.jpeg
+ha_category: Sensor
+ha_release: "0.61"
+ha_iot_class: "Local Push"
+---
+
+See the [deCONZ main component](/components/deconz/) for configuration instructions.
+
+The following sensor types are supported:
+
+ * Humidity sensor
+ * Light level sensor
+ * Pressure sensor
+ * Switches
+ * Temperature sensor
+
+Entity ids will be sensor.device_name, where device_name is defined in deCONZ. Switches aren't exposed as ordinary entities, see the [deCONZ main component](/components/deconz/) for more details.
+
+#### {% linkable_title Verified to be supported sensors %}
+
+- Humidity Sensor
+  - Xiaomi Aqara Humidity/Temperature Sensor
+  - Xiaomi MiJia Smart Temperature & Humidity Sensor
+- Light Level Sensor
+- Pressure Sensor
+- Switches
+  - IKEA Trådfri Wireless Dimmer
+  - Philips Hue Motion Sensor
+  - IKEA Trådfri Remote
+  - Philips Hue Dimmer Switch
+  - Xiaomi Cube
+  - Xiaomi Aqara Smart Light Switch
+  - Xiaomi Aqara Smart Wireless Switch
+  - Xiaomi Smart Home Wireless Switch
+- Temperature Sensor
+  - Xiaomi Temperature/Humidity Sensor

source/_components/sensor.discogs.markdown

@@ -0,0 +1,40 @@
+---
+layout: page
+title: Discogs Sensor
+description: "Instructions on how to set up Discogs sensors within Home Assistant."
+date: 2017-12-04 22:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: https://www.magneticmag.com/.image/t_share/MTQ5OTE1NzU4NTczMzk3OTYw/discogs-vinyl-record-mark.png
+ha_category: Sensor
+ha_release: 0.61
+logo: discogs.png
+ha_iot_class: "Cloud Polling"
+---
+
+The `discogs` platform allows you to see the current amount of records in your [Discogs](https://discogs.com) collection.
+
+First, you'll need to get a personal access token from your Discogs account.
+You can generate a token from your profile's [Developer settings](https://www.discogs.com/settings/developers).
+
+To enable this sensor, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: discogs
+    token: YOUR_TOKEN
+```
+
+{% configuration %}
+token:
+  description: The Discogs API token to use as identification to get your collection.
+  required: true
+  type: string
+name:
+  description: Name to use in the frontend.
+  required: false
+  type: string
+{% endconfiguration %}

source/_components/sensor.eliqonline.markdown

@@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling"
 ---
 
 
-Integrate your [ELIQ Online](http://eliq.se) smart meter information into Home Assistant. To get an [access token](https://my.eliq.se/user/settings/api) and the [Channel ID](https://my.eliq.se/user/settings/data), log in to your account.
+Integrate your [ELIQ Online](http://eliq.io) smart meter information into Home Assistant. To get an [access token](https://my.eliq.io/user/settings/api) and the [Channel ID](https://my.eliq.io/user/settings/locations), log in to your account.
 
 To enable this sensor in your installation, add the following to your `configuration.yaml` file:
 
@@ -23,6 +23,7 @@ To enable this sensor in your installation, add the following to your `configura
 sensor:
   - platform: eliqonline
     access_token: ACCESS_TOKEN
+    channel_id: CHANNEL_ID
 ```
 
 Configuration variables:
@@ -31,5 +32,5 @@ Configuration variables:
 - **channel_id** (*Required*): Channel ID (as integer) of your device.
 - **name** (*Optional*): The name of the sensor, eg. the city.
 
-For details please check the [API documentation](https://my.eliq.se/knowledge/sv-SE/49-eliq-online/299-eliq-online-api).
+For details please check the [API documentation](https://eliq.zendesk.com/hc/en-us/articles/115002708449-API-Eliq-Online).
 

source/_components/sensor.imap_email_content.markdown

@@ -38,7 +38,7 @@ Configuration variables:
 - **username** (*Required*): Username for the IMAP server.
 - **password** (*Required*): Password for the IMAP server.
 - **senders** (*Required*): A list of sender email addresses that are allowed to report state via email. Only emails received from these addresses will be processed.
-- **value_template** (*Optional*): If specified this template will be used to render the state of sensor. If a template is not supplied the raw message body will be used for the sensor value. The following attributes will be supplied to the template:
+- **value_template** (*Optional*): If specified this template will be used to render the state of the sensor. If a template is not supplied the message subject will be used for the sensor value. The following attributes will be supplied to the template:
 
    * **from**: The from address of the email
    * **body**: The body of the email

source/_components/sensor.metoffice.markdown

@@ -15,8 +15,8 @@ ha_iot_class: "Cloud Polling"
 
 The `metoffice` sensor platform uses the Met Office's [DataPoint API][datapoint] for weather data.
 
-- Each sensor will be given the `device_id` of "Met Office [condition]"
+- Each sensor will be given the `device_id` of "Met Office [condition]" if `name:` is not set.
-- The sensor checks for new data every minute, starting 30 minutes after the timestamp of the most recent data as the data is updated every half-hour.
+- The sensor checks for new data every minute, starting 30 minutes after the timestamp of the most recent data as the data is updated every half hour.
 
 To add the Met Office weather to your installation you'll need to register for a free api key at the link above and then add the following to your `configuration.yaml` file:
 
@@ -24,7 +24,7 @@ To add the Met Office weather to your installation you'll need to register for a
 # Example configuration.yaml entry
 sensor:
   - platform: metoffice
-    api_key: "my-api-key"
+    api_key: YOUR_API_KEY
     monitored_conditions:
       - weather
       - temperature
@@ -43,12 +43,25 @@ Your location will be detected from your home `latitude` and `longitude` setting
 
 Configuration variables:
 
-- **api_key** (*Required*): Your personal API key from the [Datapoint website][datapoint].
+- **api_key** (*Required*): Your personal API key from the [Datapoint website](http://www.metoffice.gov.uk/datapoint).
-- **name** (*Optional*): Name to use in the frontend, will be the prefix.
+- **name** (*Optional*): Additional name for the sensors. Default to platform name.
+- **latitude** (*Optional*): Latitude coordinate to monitor weather of (required if **longitude** is specified), defaults to coordinates defined in your `configuration.yaml`.
+- **longitude** (*Optional*): Longitude coordinate to monitor weather of (required if **latitude** is specified), defaults to coordinates defined in your `configuration.yaml`.
+- **monitored_conditions** array (*Required*): Conditions to display in the frontend.
+  - **weather**: A human-readable text summary of the current conditions.
+  - **temperature**: The current temperature.
+  - **feels_like_temperature**: A numerical value representing the apparent (or "feels like") temperature.
+  - **wind_speed**: The wind speed.
+  - **wind_direction**: Where the wind is coming from.
+  - **wind_gust**: If there are wind gusts.
+  - **visibility**: The average visibility.
+  - **visibility_distance**: The visibility distance.
+  - **uv**: The UV index.
+  - **precipitation**: The average expected intensity of precipitation occurring.
+  - **humidity**: The relative humidity.
 
 <p class='note'>
 This sensor is an alternative to the [`metoffice`](/components/weather.metoffice/) weather platform.
 The weather platform is easier to configure but less customizable.
 </p>
 
-[datapoint]: http://www.metoffice.gov.uk/datapoint

source/_components/sensor.mqtt.markdown

@@ -58,6 +58,24 @@ force_update:
   reqired: false
   type: boolean
   default: False
+availability_topic:
+  description: The MQTT topic subscribed to receive availability (online/offline) updates.
+  required: false
+  type: string
+payload_available:
+  description: The payload that represents the available state.
+  required: false
+  type: string
+  default: online
+payload_not_available:
+  description: The payload that represents the unavailable state.
+  required: false
+  type: string
+  default: offline
+json_attributes:
+  description: A list of keys to extract values from a JSON dictionary payload and then set as sensor attributes.
+  reqired: false
+  type: list, string
 {% endconfiguration %}
 
 ## {% linkable_title Examples %}

source/_components/sensor.plex.markdown

@@ -36,3 +36,4 @@ Configuration variables:
 - **password** (*Optional*): The password for your given account on the remote Plex server.
 - **server** (*Optional*): The name of your remote Plex server.
 - **token** (*Optional*): X-Plex-Token of your remote Plex server.
+- **ssl** (*Optional*): Use HTTPS to connect to Plex server, *NOTE* host *must not* be an IP when this option is enabled. Defaults to "False"

source/_components/sensor.rainbird.markdown

@@ -0,0 +1,32 @@
+---
+layout: page
+title: "Rain Bird Sensor"
+description: "Instructions on how to integrate your Rain Bird LNK WiFi Module rain sensor within Home Assistant."
+date: 2017-08-25 12:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: rainbird.png
+ha_category: Hub
+ha_release: 0.61
+ha_iot_class: "Local Polling"
+---
+
+This `rainbird` sensor allows interacting with [LNK WiFi](http://www.rainbird.com/landscape/products/controllers/LNK-WiFi.htm) module of the Rain Bird Irrigation system in Home Assistant.
+
+Once you have enabled the [Rain Bird component](/components/rainburd), add the following to your `configuration.yaml` file to enable the rain sensor:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: rainbird
+    monitored_conditions:
+      - rainsensor
+```
+
+Configuration variables:
+
+- **monitored_conditions**: Currently only rainsensor is supported. Returns the sensor level.
+
+Please note that due to the implementation of the API within the LNK Module, there is a concurrency issue. For example, the Rain Bird app will give connection issues (like already a connection active).

source/_components/sensor.sochain.markdown

@@ -0,0 +1,50 @@
+---
+layout: page
+title: "SoChain"
+description: "Instructions how to integrate chain.so data within Home Assistant."
+date: 2017-06-01 16:20
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: sochain.png
+ha_category: Finance
+ha_release: 0.61
+ha_iot_class: "Cloud Polling"
+---
+
+
+The `SoChain` sensor platform displays supported cryptocurrency wallet balances from [SoChain](https://chain.so).
+
+To add the SoChain sensor to your installation, specify a network and address to watch in the `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: sochain
+    network: LTC
+    address: 'M9m37h3dVkLDS13wYK7vcs7ck6MMMX6yhK'
+```
+
+{% configuration %}
+network:
+  description: The network or blockchain of the cryptocurrency to watch.
+  required: true
+  type: string
+address:
+  description: Cryptocurrency wallet address to watch.
+  required: true
+  type: string
+name:
+  description: The name of the sensor used in the frontend. (recommended)
+  required: false
+  type: string
+  default: Crypto Balance
+{% endconfiguration %}
+
+Supported networks (which can also be found [here](https://chain.so/api#networks-supported)) are:
+
+* BTC
+* LTC
+* DOGE
+* DASH

source/_components/sensor.zoneminder.markdown

@@ -32,3 +32,10 @@ sensor:
 Configuration variables:
 
 - **include_archived** (*Optional*): Whether to include archived ZoneMinder events in event counts. Default is `false`.
+- **monitored_conditions** array (*Optional*): Event count sensors to display in the frontend. Default is 'all'.
+  - **all**: All events.
+  - **month**: Events in the last month.
+  - **week**: Events in the last week.
+  - **day**: Events in the last day.
+  - **hour**: Events in the last hour.
+

source/_components/switch.insteon_local.markdown

@@ -14,20 +14,4 @@ ha_version: 0.36
 
 The `insteon_local` switch component lets you control your switches connected to an [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant.
 
-To integrate add a switch, configure your hub Insteon(local) with Home Assistant, add the following section to your `configuration.yaml` file:
+To get your insteon switches working with Home Assistant, follow the instructions for the general [Insteon local component](/components/insteon_local/). The switches will be automatically disovered and added to Home Assistant. The device names will be the Insteon address of the switch.
-```yaml
-# Example configuration.yaml platform entry
-insteon_local:
-  host: YOUR HUB IP
-  username: YOUR HUB USERNAME
-  password: YOUR HUB PASSWORD
-  timeout: 10
-  port: 25105
-```
-
-To add switches to your set-up, add the platform to your light configuration:
-```yaml
-switch:
-  - platform: insteon_local
-```
-

source/_components/switch.mqtt.markdown

@@ -30,20 +30,64 @@ switch:
     command_topic: "home/bedroom/switch1/set"
 ```
 
-Configuration variables:
+{% configuration %}
-
+name:
-- **name** (*Optional*): The name of the switch. Default is 'MQTT Switch'.
+  description: The name to use when displaying this switch.
-- **state_topic** (*Optional*): The MQTT topic subscribed to receive state updates.
+  required: false
-- **command_topic** (*Required*): The MQTT topic to publish commands to change the switch state.
+  type: string
-- **availability_topic** (*Optional*): The MQTT topic subscribed to receive availability (online/offline) updates.
+  default: MQTT Switch
-- **payload_on** (*Optional*): The payload that represents enabled state. Default is "ON".
+state_topic:
-- **payload_off** (*Optional*): The payload that represents disabled state. Default is "OFF".
+  description: The MQTT topic subscribed to receive state updates.
-- **payload_available** (*Optional*): The payload that represents the available state, e.g. 'online'. Default is "ON".
+  required: false
-- **payload_not_available** (*Optional*): The payload that represents the unavailable state, e.g. 'offline'. Default is "OFF".
+  type: string
-- **optimistic** (*Optional*): Flag that defines if switch works in optimistic mode. Default is `true` if no `state_topic` defined, else `false`.
+command_topic:
-- **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
+  description: The MQTT topic to publish commands to change the switch state.
-- **retain** (*Optional*): If the published message should have the retain flag on or not.
+  required: false
-- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
+  type: string
+availability_topic:
+  description: The MQTT topic subscribed to receive availability (online/offline) updates.
+  required: false
+  type: string
+payload_on:
+  description: The payload that represents enabled state.
+  required: false
+  type: string
+  default: ON
+payload_off:
+  description: The payload that represents disabled state.
+  required: false
+  type: string
+  default: OFF
+payload_available:
+  description: The payload that represents the available state.
+  required: false
+  type: string
+  default: online
+payload_not_available:
+  description: The payload that represents the unavailable state.
+  required: false
+  type: string
+  default: offline
+optimistic:
+  description: Flag that defines if switch works in optimistic mode.
+  required: false
+  type: boolean
+  default: "`true` if no `state_topic` defined, else `false`."
+qos:
+  description: The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
+  required: false
+  type: integer
+  default: 0
+retain:
+  description: If the published message should have the retain flag on or not.
+  required: false
+  type: boolean
+  default: false
+value_template:
+  description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload."
+  required: false
+  type: string
+{% endconfiguration %}
 
 <p class='note warning'>
 Make sure that your topic matches exactly. `some-topic/` and `some-topic` are different topics.

source/_components/switch.rainbird.markdown

@@ -15,13 +15,10 @@ ha_iot_class: "Local Polling"
 
 This `rainbird` switch platform allows interacting with [LNK WiFi](http://www.rainbird.com/landscape/products/controllers/LNK-WiFi.htm) module of the Rain Bird Irrigation system in Home Assistant.
 
-To enable stations as switches inside Home Assistant, add the following to your `configuration.yaml` file:
+Once you have enabled the [Rain Bird component](/components/rainbird), add the following to your `configuration.yaml` file:
 
 ```yaml
 switch:
-    platform: rainbird
-    host: '1.1.1.1'
-    password: 'secretpassword'
     sprinkler_1:
       zone: 1
       friendly_name: "Front sprinklers"
@@ -36,8 +33,6 @@ switch:
 
 Configuration variables:
 
-- **stickip** (*Required*): The IP address of your LNK WiFi Module.
-- **password** (*Required*): The password for accessing the module.
 - **zone** (*Required*): Station zone identifier.
 - **friendly_name** (*Optional*): Just a friendly name for the station.
 - **trigger_time** (*Required*): The default duration to sprinkle the zone.

source/_components/switch.tplink.markdown

@@ -1,7 +1,7 @@
 ---
 layout: page
-title: "TPLink Switch"
+title: "TP-Link Switch"
-description: "Instructions how to integrate TPLink switches into Home Assistant."
+description: "Instructions how to integrate TP-Link switches into Home Assistant."
 date: 2016-07-13 08:00
 sidebar: true
 comments: false
@@ -14,7 +14,7 @@ ha_release: "0.24"
 ---
 
 
-The `tplink` switch platform allows you to control the state of your [TPLink smart switch](http://www.tp-link.com/en/products/list-5258.html).
+The `tplink` switch platform allows you to control the state of your [TP-Link smart switch](http://www.tp-link.com/en/products/list-5258.html).
 
 Supported units:
 
@@ -23,7 +23,7 @@ Supported units:
 - HS110
 - HS200
 
-To use your TPLink switch in your installation, add the following to your `configuration.yaml` file:
+To use your TP-Link switch in your installation, add the following to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
@@ -37,7 +37,7 @@ name:
   description: The name to use when displaying this switch.
   required: false
   type: string
-  default: Random Sensor
+  default: TP-Link Switch
 host:
   description: "The IP address of your TP-Link switch, eg. `192.168.1.32`."
   required: true
@@ -46,8 +46,5 @@ enable_leds:
   description: If the LEDs on the switch (WiFi and power) should be lit.
   required: false
   type: boolean
-  default: true
 {% endconfiguration %}
 
-
-

source/_components/vacuum.mqtt.markdown

@@ -53,36 +53,133 @@ vacuum:
     send_command_topic: 'vacuum/send_command'
 ```
 
-Basic Configuration variables:
+{% configuration %}
-
+name:
-- **name** (*Optional*): The name of the vacuum. Defaults to `MQTT Vacuum`.
+  description: The name of the vacuum.
-- **supported_features** (*Optional*): List of features that the vacuum supports (possible values are `turn_on`, `turn_off`, `pause`, `stop`, `return_home`, `battery`, `status`, `locate`, `clean_spot`, `fan_speed`, `send_command`). Defaults to `turn_on`, `turn_off`, `stop`, `return_home`, `status`, `battery`, `clean_spot`.
+  required: false
-- **command_topic** (*Optional*): The MQTT topic to publish commands to control the vacuum.
+  type: string
-
+  default: MQTT Vacuum
-Advanced Configuration variables:
+supported_features:
-
+  description: "List of features that the vacuum supports (possible values are `turn_on`, `turn_off`, `pause`, `stop`, `return_home`, `battery`, `status`, `locate`, `clean_spot`, `fan_speed`, `send_command`)."
-- **qos** (*Optional*): The maximum QoS level of the state topic. Defaults to `0`. Will also be used when publishing messages.
+  required: false
-- **retain** (*Optional*): If the published message should have the retain flag on or not. Defaults to `false`.
+  type: string list
-- **payload_turn_on** (*Optional*): The payload to send to the `command_topic` to begin the cleaning cycle. Defaults to `turn_on`.
+  default: "`turn_on`, `turn_off`, `stop`, `return_home`, `status`, `battery`, `clean_spot`"
-- **payload_turn_off** (*Optional*): The payload to send to the `command_topic` to turn the vacuum off. Defaults to `turn_off`.
+command_topic:
-- **payload_return_to_base** (*Optional*): The payload to send to the `command_topic` to tell the vacuum to return to base. Defaults to `return_to_base`.
+  description: The MQTT topic to publish commands to control the vacuum.
-- **payload_stop** (*Optional*): The payload to send to the `command_topic` to stop the vacuum. Defaults to `stop`.
+  required: false
-- **payload_clean_spot** (*Optional*): The payload to send to the `command_topic` to begin a spot cleaning cycle. Defaults to `clean_spot`.
+  type: string
-- **payload_locate** (*Optional*): The payload to send to the `command_topic` to locate the vacuum (typically plays a song). Defaults to `locate`.
+qos:
-- **payload_start_pause** (*Optional*): The payload to send to the `command_topic` to start or pause the vacuum. Defaults to `start_pause`.
+  description: The maximum QoS level of the state topic.
-- **battery_level_topic** (*Optional*): The MQTT topic subscribed to receive battery level values from the vacuum.
+  required: false
-- **battery_level_template** (*Optional*): Defines a [template](/topics/templating/) to define the battery level of the vacuum.
+  type: integer
-- **charging_topic** (*Optional*): The MQTT topic subscribed to receive charging state values from the vacuum.
+  default: 0
-- **charging_template** (*Optional*): Defines a [template](/topics/templating/) to define the charging state of the vacuum.
+retain:
-- **cleaning_topic** (*Optional*): The MQTT topic subscribed to receive cleaning state values from the vacuum.
+  description: If the published message should have the retain flag on or not.
-- **cleaning_template** (*Optional*): Defines a [template](/topics/templating/) to define the cleaning state of the vacuum.
+  required: false
-- **docked_topic** (*Optional*): The MQTT topic subscribed to receive docked state values from the vacuum.
+  type: boolean
-- **docked_template** (*Optional*): Defines a [template](/topics/templating/) to define the docked state of the vacuum.
+  default: false
-- **fan_speed_topic** (*Optional*): The MQTT topic subscribed to receive fan speed values from the vacuum.
+payload_turn_on:
-- **fan_speed_template** (*Optional*): Defines a [template](/topics/templating/) to define the fan speed of the vacuum.
+  description: "The payload to send to the `command_topic` to begin the cleaning cycle."
-- **set_fan_speed_topic** (*Optional*): The MQTT topic to publish commands to control the vacuum's fan speed.
+  required: false
-- **fan_speed_list** (*Optional*): List of possible fan speeds for the vacuum.
+  type: string
-- **send_command_topic** (*Optional*): The MQTT topic to publish custom commands to the vacuum.
+  default: turn_on
+payload_turn_off:
+  description: "The payload to send to the `command_topic` to turn the vacuum off."
+  required: false
+  type: string
+  default: turn_off
+payload_return_to_base:
+  description: The payload to send to the `command_topic` to tell the vacuum to return to base.
+  required: false
+  type: string
+  default: return_to_base
+payload_stop:
+  description: The payload to send to the `command_topic` to stop the vacuum.
+  required: false
+  type: string
+  default: stop
+payload_clean_spot:
+  description: The payload to send to the `command_topic` to begin a spot cleaning cycle.
+  required: false
+  type: string
+  default: clean_spot
+payload_locate:
+  description: The payload to send to the `command_topic` to locate the vacuum (typically plays a song).
+  required: false
+  type: string
+  default: locate
+payload_start_pause:
+  description: The payload to send to the `command_topic` to start or pause the vacuum.
+  required: false
+  type: string
+  default: start_pause
+battery_level_topic:
+  description: The MQTT topic subscribed to receive battery level values from the vacuum.
+  required: false
+  type: string
+battery_level_template:
+  description: "Defines a [template](/topics/templating/) to define the battery level of the vacuum."
+  required: false
+  type: string
+charging_topic:
+  description: The MQTT topic subscribed to receive charging state values from the vacuum.
+  required: false
+  type: string
+charging_template:
+  description:  "Defines a [template](/topics/templating/) to define the charging state of the vacuum."
+  required: false
+  type: string
+cleaning_topic:
+  description: The MQTT topic subscribed to receive cleaning state values from the vacuum.
+  required: false
+  type: string
+cleaning_template:
+  description: "Defines a [template](/topics/templating/) to define the cleaning state of the vacuum."
+  required: false
+  type: string
+docked_topic:
+  description: The MQTT topic subscribed to receive docked state values from the vacuum.
+  required: false
+  type: string
+docked_template:
+  description: "Defines a [template](/topics/templating/) to define the docked state of the vacuum."
+  required: false
+  type: string
+fan_speed_topic:
+  description: The MQTT topic subscribed to receive fan speed values from the vacuum.
+  required: false
+  type: string
+fan_speed_template:
+  description: "Defines a [template](/topics/templating/) to define the fan speed of the vacuum."
+  required: false
+  type: string
+set_fan_speed_topic:
+  description: The MQTT topic to publish commands to control the vacuum's fan speed.
+  required: false
+  type: string
+fan_speed_list:
+  description: List of possible fan speeds for the vacuum.
+  required: false
+  type: string list
+send_command_topic:
+  description: The MQTT topic to publish custom commands to the vacuum.
+  required: false
+  type: string
+availability_topic:
+  description: The MQTT topic subscribed to receive availability (online/offline) updates.
+  required: false
+  type: string
+payload_available:
+  description: The payload that represents the available state.
+  required: false
+  type: string
+  default: online
+payload_not_available:
+  description: The payload that represents the unavailable state.
+  required: false
+  type: string
+  default: offline
+{% endconfiguration %}
 
 ### {% linkable_title Default MQTT Protocol %}
 

source/_components/vacuum.xiaomi_miio.markdown

@@ -155,7 +155,7 @@ To fetch the token follow these instructions depending on your mobile phone plat
 
 Follow the pairing process using your phone and Mi-Home app. You will be able to retrieve the token from a SQLite file inside your phone.
 
-Before you begin you need to install `libffi-dev` and `libssl-dev` by running the command below. This is needed for `python-mirobo` to be installed correctly.
+Before you begin you need to install `libffi-dev` and `libssl-dev` by running the command below. This is needed for `python-miio` to be installed correctly.
 
 ```bash
 $ sudo apt-get install libffi-dev libssl-dev
@@ -185,7 +185,7 @@ To fetch the token follow these instructions depending on your mobile phone plat
 
 Follow the pairing process using your phone and Mi-Home app. You will be able to retrieve the token from a SQLite file inside your phone.
 
-Before you begin you need to install `libffi-dev` and `libssl-dev` by running the command below. This is needed for `python-mirobo` to be installed correctly.
+Before you begin you need to install `libffi-dev` and `libssl-dev` by running the command below. This is needed for `python-miio` to be installed correctly.
 
 ```bash
 $ sudo apt-get install libffi-dev libssl-dev

source/_components/weather.darksky.markdown

@@ -0,0 +1,70 @@
+---
+layout: page
+title: "Dark Sky"
+description: "Instructions how to integrate Dark Sky within Home Assistant."
+date: 2016-09-29 09:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: dark_sky.png
+ha_category: Weather
+ha_release: 0.61
+ha_iot_class: "Cloud Polling"
+---
+
+The `darksky` platform uses the [Dark Sky](https://darksky.net/) web service as
+a source for meteorological data for your location.
+
+You need an API key which is free but requires
+[registration](https://darksky.net/dev/register). The free tier allows up to
+1000 calls per day, this platform updates at most every 3 minutes, using up to
+480 of those calls.
+
+<p class='note warning'>
+[Dark Sky](https://darksky.net/dev/) will charge you $0.0001 per API call if you
+enter your credit card details and create more than 1000 calls per day.
+</p>
+
+To add Dark Sky to your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+weather:
+  - platform: darksky
+    api_key: YOUR_API_KEY
+```
+
+{% configuration %}
+api_key:
+  description: "Your API key for [Dark Sky](https://darksky.net/dev/)."
+  required: true
+  type: string
+latitude:
+  description: Manually specify latitude. By default the value will be taken from the Home Assistant configuration.
+  required: false
+  type: number
+  default: Provided by Home Assistant configuration
+longitude:
+  description: Manually specify longitude. By default the value will be taken from the Home Assistant configuration.
+  required: false
+  type: number
+  default: Provided by Home Assistant configuration
+units:
+  description: "Manually specify unit system. Valid values are: `auto`, `us`, `si`, `ca`, `uk` and `uk2`."
+  required: false
+  type: string
+  default: "`si` if Home Assistant unit system is metric, `us` if imperial."
+name:
+  description: Name to use in the frontend.
+  required: false
+  type: string
+  default: Open Sky
+{% endconfiguration %}
+
+<p class='note'>
+This platform is an alternative to the [`darksky`](/components/sensor.darksky/)
+sensor.
+</p>
+
+Details about the API are available in the [Dark Sky documentation](https://darksky.net/dev/docs).

source/_components/weather.metoffice.markdown

@@ -20,16 +20,15 @@ To add the Met Office weather platform to your installation, you'll need to regi
 ```yaml
 weather:
   - platform: metoffice
-    api_key: "my-api-key"
+    api_key: YOUR_API_KEY
 ```
 
 Configuration variables:
 
-- **api_key** (*Required*): Your personal API key from the [Datapoint website][datapoint].
+- **api_key** (*Required*): Your personal API key from the [Datapoint website](http://www.metoffice.gov.uk/datapoint).
 
 <p class='note'>
 This platform is an alternative to the [`metoffice`](/components/sensor.metoffice/) sensor.
 The weather platform is easier to configure but less customizable.
 </p>
 
-[datapoint]: http://www.metoffice.gov.uk/datapoint

source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown

@@ -14,7 +14,9 @@ Today we’re introducing the next step in the Home Assistant saga: the Home Ass
 
 The first service that is supported via the Home Assistant Cloud is the Amazon Alexa Smart Home skill. This integration will allow you to control all your devices in Home Assistant via Amazon Alexa. You will be able to say _“Alexa, turn on the kitchen lights”_ and your local Home Assistant will turn on the lights. Because Alexa talks to Home Assistant, it doesn’t matter what kind of lights they are! Anything that is linked to Home Assistant will work. IKEA lights, a 10 year old X10 switch or something you’ve made yourself. As long as Home Assistant can control it, you can control it via Alexa.
 
-We have designed the Home Assistant Cloud with security in mind. When you activate the new Cloud component, your instance will setup a secure connection to the Home Assistant Cloud. Alexa will deliver messages to our cloud which we will forward to your local instance for processing. We just forward the response back to Alexa. This means that we do not have to store the state of your house in our cloud, we’re just the messenger!
+We have designed the Home Assistant Cloud with security in mind. When you activate the new Cloud component, your instance will create a secure connection to the Home Assistant Cloud. There is no need for any further configuration or to expose your instance to the internet.
+
+Integrations like Alexa will deliver messages to our cloud which we will forward to your local instance for processing. We just forward the response back to Alexa. This means that we do not have to store the state of your house in our cloud, we’re just the messenger!
 
 We are making the beta of the Home Assistant Cloud publicly available today. During the beta period the Home Assistant Cloud will be free to use. We are currently planning to run a beta till March 1, 2018 0:00 UTC. Once the beta ends, the Home Assistant Cloud will be part of our Community Support package which will run at $5 USD/month.
 

source/_posts/2018-01-14-release-61.markdown

@@ -0,0 +1,732 @@
+---
+layout: post
+title: "0.61: Coinbase, Discogs, iGlo, Sochain"
+description: "New crypto currency sensors and other new stuff including breaking changes."
+date: 2018-01-14 18:00:00
+date_formatted: "January 14, 2018"
+author: Fabian Affolter
+author_twitter: fabaff
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2018-01-0.61/components.png
+---
+
+<a href='/components/#version/0.61'><img src='/images/blog/2018-01-0.61/components.png' style='border: 0;box-shadow: none;'></a>
+
+Almost a 100 contributors to this release 🎉  That's what you get when you skip a release. It's a little late but "Happy New Year" and welcome to 0.61 the first release 2018.
+
+This release contain some breaking changes. Please make sure that you check the section below if you are running into trouble.
+
+There is not much more to tell and I don't want to make something up.
+
+
+## {% linkable_title New Platforms %}
+
+- Add Discogs Sensor platform ([@thibmaek] - [#10957]) ([sensor.discogs docs]) (new-platform)
+- Greenwave Reality (TCP Connected) Lighting Component ([@dfiel] - [#11282]) ([light.greenwave docs]) (new-platform)
+- Added rainsensor ([@jbarrancos] - [#11023]) ([rainbird docs]) ([sensor.rainbird docs]) ([switch.rainbird docs]) (new-platform)
+- Sochain cryptocurrency sensor ([@Klathmon] - [#11335]) ([sensor.sochain docs]) (new-platform)
+- Support for EcoNet water heaters ([@w1ll1am23] - [#11260]) ([climate.econet docs]) (new-platform)
+- Add deCONZ component ([@Kane610] - [#10321]) ([deconz docs]) ([binary_sensor.deconz docs]) ([light.deconz docs]) ([sensor.deconz docs]) (new-platform)
+- Added new climate component from Daikin ([@rofrantz] - [#10983]) ([climate.daikin docs]) (new-platform)
+- Add Touchline climate platform ([@abondoe] - [#10547]) ([climate.touchline docs]) (new-platform)
+- Add new iGlo component ([@jesserockz] - [#11171]) ([light.iglo docs]) (new-platform)
+- Add Dark Sky weather component ([@DanNixon] - [#11435]) ([weather.darksky docs]) (new-platform)
+- Coinbase.com sensor platform ([@nkgilley] - [#11036]) ([coinbase docs]) ([sensor.coinbase docs]) (new-platform)
+
+## {% linkable_title If you need help... %}
+
+...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+
+## {% linkable_title Reporting Issues %}
+
+Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
+
+<!--more-->
+
+## {% linkable_title Breaking Changes %}
+
+- Extend Threshold binary sensor to support ranges. This means that you can now set `up` and `lower`. ([@DanNixon] - [#11110]) ([binary_sensor.threshold docs]) (breaking change)
+- The Steam game platform contains changes:
+  - `game` attribute no longer set in `device_state_attributes` if no game is currently being played as the string "None" is no longer passed if no current game is being played, instead the `game` attribute is not present.
+  - States now use lower snake case.
+  - The "Play" and "Trade" states has been renamed to "looking_to_play" and "looking_to_trade".
+    ([@frwickst] - [#11182]) ([sensor.steam_online docs]) (breaking change)
+- The [`tile`][device_tracker.tile docs] platform now shows only active Tiles by default; to show all Tiles, including expired/inactive ones, `show_inactive` must be `True`. The following state attributes have been removed: `last_seen` and `last_updated`. ([@bachya] - [#11172]) ([device_tracker.tile docs]) (breaking change)
+- The `hidden_string` feature has been removed from the isy994 component. Previously, this allowed entities to be "hidden" in Home Assistant if a configured string was present in an ISY device's name or folder path. This was removed because hiding devices is now done via the customization feature.
+Note however, that this feature was replaced by a new ignore_string config option, which will now cause Home Assistant to completely ignore devices with the matching string so that they will not be imported as a Home Assistant device at all. This can be helpful if you have nodes in the ISY that aren't useful at all in Hass (IR transmitter nodes are a good example.) ([@OverloadUT] - [#11243]) ([isy994 docs]) ([binary_sensor.isy994 docs]) ([cover.isy994 docs]) ([fan.isy994 docs]) ([light.isy994 docs]) ([lock.isy994 docs]) ([sensor.isy994 docs]) ([switch.isy994 docs]) (breaking change)
+- The [`egardia` alarm panel][alarm_control_panel.egardia docs] platform no longer a need the users to run a separate Egardiaserver component. It can now also run on HASS.io. ([@jeroenterheerdt] - [#11344]) ([alarm_control_panel.egardia docs]) (breaking change)
+- The binary sensor platform of the DoorBird integration has been deleted, so remove DoorBird from your `binary_sensor` configuration. Instead, set the `doorbell_events` option of the `doorbird` component to `True`. The `last_visitor` option has been removed from the camera component, as it is now always added as an entity. ([@Klikini] - [#11193]) ([camera.doorbird docs]) (breaking change)
+- The following attributes of the TP-Link switch and light platform have been renamed:
+  - Light: `current_consumption` -> `current_power_w`, `daily_consumption` -> `daily_energy_kwh` and `monthly_consumption` -> `monthly_energy_kwh`
+  - Switch: `current` -> `current_a`, `current_consumption` -> `current_power_w`, `total_consumption` -> `total_energy_kwh` and `daily_consumption` -> `today_energy_kwh` ([@DanNixon] - [#10979]) ([light.tplink docs]) ([switch.tplink docs]) (breaking change)
+- Move IMAP Email Content body to an attribute ([@notoriousbdg] - [#11096]) ([sensor.imap_email_content docs]) (breaking change)
+- Automations which were using `state` that was returning `target_temperature` of the `netatmo` climate platform needs an update. ([@ciotlosm] - [#11345]) ([climate.netatmo docs]) (breaking change)
+- The default availability payloads for the `MQTT` switch platform have changed from "ON" and "OFF" to "online" and "offline" (in order to match the majority of MQTT platforms that already supported availability reporting). ([@DanNixon] - [#11336]) (breaking change)
+- Customizations for how entities are exposed to Alexa are no longer set via `customize`. Instead they are set via the configuration of the cloud component:
+
+    ```yaml
+    cloud:
+      alexa:
+        entity_config:
+          switch.kitchen:
+            name: 'Name for Alexa'
+            description: 'Description for Alexa'
+            display_categories: 'LIGHT'
+    ```
+  ([@balloob] - [#11461]) ([cloud docs]) ([alexa.smart_home docs]) (breaking change)
+- The extension of the `alpha_vantage` requires an update of the configuration as now are exchange data available as well. ([@ChristianKuehnel] - [#11427]) ([sensor.alpha_vantage docs]) (breaking change)
+- The `prometheus` component now supports pushing all sensors and fixes wrong metrics. If may require that you update your configuration. ([@michaelkuty] - [#11159]) ([prometheus docs]) (breaking change)
+- Insteon local devices will now use their address as the `entity_id` and `name`. The friendly name can be customized using the [standard customization configuration](https://home-assistant.io/docs/configuration/customizing-devices/). ([@camrun91] - [#11088]) ([insteon_local docs]) ([fan.insteon_local docs]) ([light.insteon_local docs]) ([switch.insteon_local docs]) (breaking change)
+- Google Assistant is no longer configured via `customize` but instead has its configuration under the `google_assistant` entry in your `configuration.yaml`. The attributes will no longer have to be prefixed with `google_assistant_` either.
+
+    | Old option | New option |
+    | ---------- | ------------ |
+    | google_assistant | expose |
+    | aliases | aliases |
+    | google_assistant_name | name |
+    | google_assistant_type | type |
+
+    Before:
+
+    ```yaml
+    homeassistant:
+      customize:
+        switch.kitchen:
+          google_assistant: false
+          google_assistant_name: nice lights
+          google_assistant_type: light
+          aliases:
+            - roof lights
+
+    google_assistant:
+    ```
+
+    After:
+
+    ```yaml
+    google_assistant:
+      entity_config:
+        switch.kitchen:
+          expose: false
+          alias: roof lights
+          name: nice lights
+          type: light
+    ```
+([@balloob] - [#11499]) ([cloud docs]) ([google_assistant docs]) (breaking change)
+- The `climate.set_aux_heat` service is no longer available for the Sensibo cliamte platform. Now call `climate.turn_on` or `climate.turn_off`. ([@andrey-git] - [#11579]) ([climate.sensibo docs]) (breaking change)
+
+## {% linkable_title All changes %}
+
+- Try multiple methods of getting data in asuswrt. ([@PeWu] - [#11140]) ([device_tracker.asuswrt docs])
+- Hydroquebec component use now asyncio ([@titilambert] - [#10795]) ([sensor.hydroquebec docs])
+- Hive Component Release Two ([@KJonline] - [#11053]) ([hive docs]) ([climate.hive docs]) ([light.hive docs])
+- Add Discogs Sensor platform ([@thibmaek] - [#10957]) ([sensor.discogs docs]) (new-platform)
+- Fix statistics sensor mean and median when only one sample is available. ([@markferry] - [#11180]) ([sensor.statistics docs])
+- Extend Threshold binary sensor to support ranges ([@DanNixon] - [#11110]) ([binary_sensor.threshold docs]) (breaking change)
+- Bump python-miio version ([@djchen] - [#11232]) ([fan.xiaomi_miio docs]) ([light.xiaomi_miio docs]) ([switch.xiaomi_miio docs]) ([vacuum.xiaomi_miio docs])
+- Backup configuration files before overwriting ([@cgarwood] - [#11216])
+- Upgrade to new miflora version 0.2.0 ([@ChristianKuehnel] - [#11250]) ([sensor.miflora docs])
+- Add workaround for running tox on Windows platforms ([@veleek] - [#11188])
+- added myself to become code owner for miflora and plant ([@ChristianKuehnel] - [#11251])
+- Proper Steam game names and small fixes ([@frwickst] - [#11182]) ([sensor.steam_online docs]) (breaking change)
+- Bugfix: 10509 - http is hard coded in plex sensor ([@ryanm101] - [#11072]) ([sensor.plex docs])
+- Adding MotionIP to BinarySensors for HMIP-SMI ([@schnoetz] - [#11268]) ([homematic docs])
+- Revert "Backup configuration files before overwriting" ([@pvizeli] - [#11269])
+- Functinality to save/restore snapshots for monoprice platform ([@etsinko] - [#10296]) ([media_player.monoprice docs])
+- Change manifest path to /states as this is the path / actually sets. ([@andrey-git] - [#11274])
+- Report Sensibo as off when it is off ([@andrey-git] - [#11281]) ([climate.sensibo docs])
+- Added password for GPS logger endpoint ([@foxel] - [#11245]) ([device_tracker.gpslogger docs])
+- Greenwave Reality (TCP Connected) Lighting Component ([@dfiel] - [#11282]) ([light.greenwave docs]) (new-platform)
+- Adds support for disabled Tiles and automatic session renewal ([@bachya] - [#11172]) ([device_tracker.tile docs]) (breaking change)
+- Plex refactor ([@ryanm101] - [#11235]) ([media_player.plex docs])
+- alexa: Add handling for covers ([@philk] - [#11242]) ([alexa.smart_home docs])
+- Added rainsensor ([@jbarrancos] - [#11023]) ([rainbird docs]) ([sensor.rainbird docs]) ([switch.rainbird docs]) (new-platform)
+- Store raw state of RF sensors from alarmdecoder ([@PhracturedBlue] - [#10841]) ([alarmdecoder docs]) ([binary_sensor.alarmdecoder docs])
+- Add Chime status and control to Alarm Decoder component ([@goyney] - [#11271]) ([alarm_control_panel.alarmdecoder docs])
+- Better error handling ([@rofrantz] - [#11297]) ([sensor.transmission docs]) ([switch.transmission docs])
+- Removed error log used as debug ([@cmsimike] - [#11301]) ([octoprint docs])
+- Huge ISY994 platform cleanup, fixes support for 5.0.10 firmware ([@OverloadUT] - [#11243]) ([isy994 docs]) ([binary_sensor.isy994 docs]) ([cover.isy994 docs]) ([fan.isy994 docs]) ([light.isy994 docs]) ([lock.isy994 docs]) ([sensor.isy994 docs]) ([switch.isy994 docs]) (breaking change)
+- Add heartbeat to websocket connections ([@balloob] - [#11298]) ([cloud.iot docs])
+- Fix typo in bitcoin.py component for mined blocks. ([@awkwardDuck] - [#11318]) ([sensor.bitcoin docs])
+- xiaomi_aqara: Fix covers never being closed ([@cnrd] - [#11319]) ([cover.xiaomi_aqara docs])
+- Fix for track_new_devices BC ([@masarliev] - [#11202]) ([device_tracker docs])
+- Upgrade aiohttp_cors to 0.6.0 ([@fabaff] - [#11310]) ([http docs])
+- Upgrade pysnmp to 4.4.3 ([@fabaff] - [#11317]) ([device_tracker.snmp docs]) ([sensor.snmp docs]) ([switch.snmp docs])
+- Upgrade luftdaten to 0.1.3 ([@fabaff] - [#11316]) ([sensor.luftdaten docs])
+- Upgrade yahooweather to 0.10 ([@fabaff] - [#11309]) ([weather.yweather docs])
+- Upgrade distro to 1.2.0 ([@fabaff] - [#11312]) ([updater docs])
+- Upgrade python-digitalocean to 1.13.2 ([@fabaff] - [#11311]) ([digital_ocean docs])
+- Upgrade youtube_dl to 2017.12.23 ([@fabaff] - [#11308]) ([media_extractor docs])
+- Upgrade alpha_vantage to 1.6.0 ([@fabaff] - [#11307]) ([sensor.alpha_vantage docs])
+- Bugfix for HA Issue 7292, 9412 - switch to gamertag to receive ssl image url ([@ReneNulschDE] - [#11315]) ([sensor.xbox_live docs])
+- closes #11314 by not restricting the voice to anything but a string ([@Human] - [#11326]) ([tts.marytts docs])
+- Additional device classes for binary sensors ([@schmittx] - [#11280]) ([binary_sensor docs])
+- Remove need for separate EgardiaServer setup ([@jeroenterheerdt] - [#11344]) ([alarm_control_panel.egardia docs]) (breaking change)
+- Add default names and validation for TP-Link devices ([@DanNixon] - [#11346]) ([light.tplink docs]) ([switch.tplink docs])
+- Sochain cryptocurrency sensor ([@Klathmon] - [#11335]) ([sensor.sochain docs]) (new-platform)
+- pass stops_at to get_station_by_name ([@ttroy50] - [#11304]) ([sensor.irish_rail_transport docs])
+- Move data instance to setup ([@fabaff] - [#11350]) ([sensor.swiss_public_transport docs])
+- Update modbus.py ([@goldminenine] - [#11238]) ([modbus docs])
+- DoorBird feature update ([@Klikini] - [#11193]) ([camera.doorbird docs]) (breaking change)
+- Upgrade aiohttp to 2.3.7 ([@fabaff] - [#11329])
+- Upgrade fuzzywuzzy to 0.16.0 ([@fabaff] - [#11331]) ([conversation docs])
+- Upgrade pyowm to 2.8.0 ([@fabaff] - [#11332]) ([sensor.openweathermap docs]) ([weather.openweathermap docs])
+- Upgrade sqlalchemy to 1.2.0 ([@fabaff] - [#11333])
+- Upgrade mypy to 0.560 ([@fabaff] - [#11334])
+- Upgrade python-telegram-bot to 9.0.0 ([@fabaff] - [#11341]) ([telegram_bot docs])
+- Upgrade youtube_dl to 2017.12.28 ([@fabaff] - [#11357]) ([media_extractor docs])
+- Correct units used in TP-Link energy monioring ([@DanNixon] - [#10979]) ([light.tplink docs]) ([switch.tplink docs]) (breaking change)
+- Add HTTP endpoint for resending email confirmation ([@balloob] - [#11354]) ([cloud.auth_api docs]) ([cloud.http_api docs])
+- Fix RGB template ordering in MQTT Light ([@DanNixon] - [#11362]) ([light.mqtt docs])
+- Ping device tracker now respects interval_seconds ([@tschmidty69] - [#11348]) ([device_tracker.ping docs])
+- Fido component use now asyncio ([@titilambert] - [#11244]) ([sensor.fido docs])
+- Support for EcoNet water heaters ([@w1ll1am23] - [#11260]) ([climate.econet docs]) (new-platform)
+- Remember the Milk - updating and completing tasks ([@ChristianKuehnel] - [#11069]) ([remember_the_milk docs])
+- Reverts unit conversions in TP-Link bulb ([@DanNixon] - [#11381]) ([light.tplink docs])
+- Clean up Google Assistant ([@balloob] - [#11375]) ([google_assistant docs]) ([google_assistant.http docs]) ([google_assistant.smart_home docs])
+- Adding support for Egardia / Woonveilig version GATE-03 ([@jeroenterheerdt] - [#11397]) ([alarm_control_panel.egardia docs])
+- Add deCONZ component ([@Kane610] - [#10321]) ([deconz docs]) ([binary_sensor.deconz docs]) ([light.deconz docs]) ([sensor.deconz docs]) (new-platform)
+- Fix broken tests ([@balloob] - [#11395])
+- Upgrade pychromecast to 1.0.3 ([@OttoWinter] - [#11410]) ([media_player.cast docs])
+- Bump pywemo to fix request include problems. ([@pavoni] - [#11401]) ([wemo docs])
+- Log exceptions that happen during service call ([@balloob] - [#11394])
+- Move IMAP Email Content body to an attribute ([@notoriousbdg] - [#11096]) ([sensor.imap_email_content docs]) (breaking change)
+- Notify webos timeout error fix ([@masarliev] - [#11027]) ([notify.webostv docs])
+- Removed status block to allow https://github.com/home-assistant/home-assistant-polymer/pull/766 with no impact ([@ciotlosm] - [#11345]) ([climate.netatmo docs]) (breaking change)
+- More support for availability reporting on MQTT components ([@DanNixon] - [#11336]) (breaking change)
+- Do not purge the most recent state for an entity ([@tinloaf] - [#11039])
+- Performance optimization of TP-Link switch ([@amelchio] - [#11416]) ([switch.tplink docs])
+- Fixing OpenWeatherMap Sensor. Current weather is 'unknown' if forecast: false. It was reported as #8640. ([@tomaszduda23] - [#11417]) ([sensor.openweathermap docs])
+- Silence redundant warnings about slow setup ([@amelchio] - [#11352])
+- Account for User-Agent being non-existent, causing a TypeError ([@akatrevorjay] - [#11064])
+- Cloud Updates ([@balloob] - [#11404]) ([cloud docs])
+- Add support for the renaming of Yamaha Receiver Zones via configuration file. Added a test to cover the change, plus previously untested options. ([@dfinlay] - [#11402]) ([media_player.yamaha docs])
+- Plex api update ([@ryanm101] - [#11423]) ([media_player.plex docs]) ([sensor.plex docs])
+- fix: hmip-etrv-2 now working with homeassistant ([@daenny] - [#11175]) ([homematic docs]) ([climate.homematic docs])
+- Fix errors in zigbee push state ([@SteveEasley] - [#11386]) ([zigbee docs])
+- Add on/off supported feature to climate ([@andrey-git] - [#11379]) ([climate docs]) ([climate.demo docs]) ([climate.sensibo docs])
+- Fix CONF_FRIENDLY_NAME ([@cdce8p] - [#11438]) ([cover.template docs]) ([light.template docs])
+- Climate: fix missing "|" ([@andrey-git] - [#11441]) ([climate.demo docs])
+- Google Assistant -> Google Actions ([@balloob] - [#11442]) ([cloud.iot docs])
+- Added new climate component from Daikin ([@rofrantz] - [#10983]) ([climate.daikin docs]) (new-platform)
+- Updated generic thermostat to respect operation_mode and added away mode ([@ciotlosm] - [#11445]) ([climate.generic_thermostat docs])
+- Reconnect to alarmdecoder on disconnect ([@PhracturedBlue] - [#11383]) ([alarmdecoder docs])
+- Set tahoma cover scan interval to 60 seconds ([@bakedraccoon] - [#11447]) ([cover.tahoma docs])
+- Add some tests to the cloud component ([@balloob] - [#11460]) ([cloud docs]) ([cloud.iot docs])
+- Input Select - Added service description ([@cdce8p] - [#11456]) ([input_select docs])
+- Input Boolean - Deleted 'DEFAULT_INITIAL' ([@cdce8p] - [#11453]) ([input_boolean docs])
+- Updated gitignore file ([@cdce8p] - [#11452])
+- Update hydroquebec component to use hass httpsession ([@titilambert] - [#11412]) ([sensor.hydroquebec docs])
+- Catch everything when calling to OctoPrint API to fix #10557 ([@w1ll1am23] - [#11457]) ([octoprint docs])
+- Update PULL_REQUEST_TEMPLATE.md ([@danielhiversen] - [#11465])
+- Alexa to not use customize for entity config ([@balloob] - [#11461]) ([cloud docs]) ([alexa.smart_home docs]) (breaking change)
+- Don't duplicate html5 registrations ([@Chris-V] - [#11451]) ([notify.html5 docs])
+- AlarmDecoder remove icon function as BinarySensorDevice handles it correctly now ([@hawk259] - [#11467]) ([binary_sensor.alarmdecoder docs])
+- Upgrade psutil to 5.4.3 ([@fabaff] - [#11468]) ([sensor.systemmonitor docs])
+- Upgrade alpha_vantage to 1.8.0 ([@fabaff] - [#11476]) ([sensor.alpha_vantage docs])
+- Fix vultr tests ([@balloob] - [#11477])
+- Upgrade yarl to 0.17.0 ([@fabaff] - [#11478])
+- Add Touchline climate platform ([@abondoe] - [#10547]) ([climate.touchline docs]) (new-platform)
+- Upgrade pysnmp to 4.4.4 ([@fabaff] - [#11485]) ([device_tracker.snmp docs]) ([sensor.snmp docs]) ([switch.snmp docs])
+- Add new iGlo component ([@jesserockz] - [#11171]) ([light.iglo docs]) (new-platform)
+- Add missing configuration variables ([@fabaff] - [#11390]) ([sensor.metoffice docs])
+- Clean up Alexa.intent and DialogFlow.intent ([@balloob] - [#11492]) ([alexa.intent docs])
+- Fix time functions would throw errors in python scripts ([@tomwaters] - [#11414]) ([python_script docs])
+- Upgrade pywebpush to 1.5.0 ([@Chris-V] - [#11497]) ([notify.html5 docs])
+- upgrade schiene to 0.20 ([@JulianKahnert] - [#11504]) ([sensor.deutsche_bahn docs])
+- timer: include the remaining time in the state attributes ([@Julio-Guerra] - [#11510]) ([timer docs])
+- More tolerant KNX component if gateway cant be connected ([@Julius2342] - [#11511]) ([knx docs]) ([binary_sensor.knx docs]) ([climate.knx docs]) ([cover.knx docs]) ([light.knx docs]) ([sensor.knx docs]) ([switch.knx docs])
+- Snips (new) added speech response, parse snips/duration ([@tschmidty69] - [#11513]) ([snips docs])
+- Add Dark Sky weather component ([@DanNixon] - [#11435]) ([weather.darksky docs]) (new-platform)
+- Lazy loading of service descriptions ([@amelchio] - [#11479]) ([api docs]) ([websocket_api docs]) ([light.lifx docs])
+- Fix canary flaky test ([@balloob] - [#11519])
+- Address missed review comments for Dark Sky weather ([@DanNixon] - [#11520]) ([weather.darksky docs])
+- New features for Owntracks device_tracker ([@cpcowart] - [#11480]) ([device_tracker.owntracks docs])
+- Reconnect before mochad switch send command ([@aosadchyy] - [#11296]) ([switch.mochad docs])
+- Fix Kodi channels media type ([@florianj1] - [#11505]) ([media_player.kodi docs])
+- Extension sensor alpha_vantage ([@ChristianKuehnel] - [#11427]) ([sensor.alpha_vantage docs]) (breaking change)
+- MQTT json attributes ([@timstanley1985] - [#11439]) ([sensor.mqtt docs])
+- Support pushing all sensors and fix wrong metrics. ([@michaelkuty] - [#11159]) ([prometheus docs]) (breaking change)
+- Add options feature to Baidu TTS. ([@yienxu] - [#11462]) ([tts.baidu docs])
+- Insteon local update ([@camrun91] - [#11088]) ([insteon_local docs]) ([fan.insteon_local docs]) ([light.insteon_local docs]) ([switch.insteon_local docs]) (breaking change)
+- Snips: (fix) support new intentName format ([@tschmidty69] - [#11509]) ([snips docs])
+- Upgrade numpy to 1.14.0 ([@fabaff] - [#11542]) ([binary_sensor.trend docs]) ([image_processing.opencv docs])
+- Upgrade python-etherscan-api to 0.0.2 ([@fabaff] - [#11535]) ([sensor.etherscan docs])
+- Upgrade Sphinx to 1.6.6 ([@fabaff] - [#11534])
+- ZoneMinder event sensor updates ([@swilson] - [#11369]) ([sensor.zoneminder docs])
+- Move Google Assistant entity config out of customize ([@balloob] - [#11499]) ([cloud docs]) ([google_assistant docs]) (breaking change)
+- Upgrade lightify to 1.0.6.1 ([@fabaff] - [#11545]) ([light.osramlightify docs])
+- Improved test runtime ([@cdce8p] - [#11553]) ([binary_sensor.workday docs])
+- Add 2 media_player services and 1 custom service to Squeezebox platform ([@ericpignet] - [#10969]) ([media_player.squeezebox docs])
+- Fix error on entity_config missing ([@philk] - [#11561]) ([google_assistant.http docs])
+- Upgrade keyring to 10.3.2 ([@fabaff] - [#11531])
+- Coinbase.com sensor platform ([@nkgilley] - [#11036]) ([coinbase docs]) ([sensor.coinbase docs]) (new-platform)
+- Try to fix crashes after Hue refactoring ([@andreacampi] - [#11270]) ([light.hue docs])
+- Remove execution file perm ([@balloob] - [#11563])
+- Deprecate explicit entity_id in template platforms ([@amelchio] - [#11123]) ([binary_sensor.template docs]) ([cover.template docs]) ([light.template docs]) ([sensor.template docs]) ([switch.template docs])
+- Test tweaks ([@balloob] - [#11560])
+- Add Velux Windows to Tahoma ([@bakedraccoon] - [#11538]) ([tahoma docs]) ([cover.tahoma docs])
+- Extend hass.io services / updater ([@pvizeli] - [#11549]) ([hassio docs])
+- Add sensibo_assume_state service to Sensibo climate ([@andrey-git] - [#11567]) ([climate.sensibo docs])
+- Tracking all groups to allow changing of existing groups ([@randellhodges] - [#11444]) ([group docs])
+- Fix new squeezebox service descriptions for lazy loading ([@amelchio] - [#11574]) ([media_player.squeezebox docs])
+- Mark REST binary_sensor unavailable if request fails ([@DanNixon] - [#11506]) ([binary_sensor.rest docs])
+- Tado improvements - hot water zone sensors and climate precision ([@andersonshatch] - [#11521]) ([climate.tado docs]) ([sensor.tado docs])
+- Make the rpi_rf component thread-safe using an RLock ([@ulido] - [#11487]) ([switch.rpi_rf docs])
+- Update pyhomematic, support new devices ([@danielperna84] - [#11578]) ([homematic docs])
+- Alarmdecoder add validation of the zone types ([@hawk259] - [#11488]) ([alarmdecoder docs])
+- Support OSRAM lights on ZHA ([@armills] - [#11522]) ([light.zha docs])
+- Fix bluetooth tracker source ([@swilson] - [#11469]) ([device_tracker docs]) ([device_tracker.bluetooth_le_tracker docs]) ([device_tracker.bluetooth_tracker docs])
+- Fix for asuswrt, telnet not working and presence-detection for router mode ([@kennedyshead] - [#11422]) ([device_tracker.asuswrt docs])
+- Remove aux_heat support from Sensibo now that UI supports on/off ([@andrey-git] - [#11579]) ([climate.sensibo docs]) (breaking change)
+- Changed device type of media player and cover to switch ([@Laqoore] - [#11483]) ([google_assistant.smart_home docs])
+- Control ordering of display in history component ([@rwa] - [#11340]) ([history docs])
+- Pr/11430 ([@balloob] - [#11587])
+- Cast return values and add unit tests for the yahoo weather component. ([@cgtobi] - [#10699]) ([weather.yweather docs])
+- add velux roller shutter to tahoma ([@bakedraccoon] - [#11586]) ([tahoma docs])
+- Added support for enable/disable motion detection ([@abjorshammar] - [#11583]) ([camera.uvc docs])
+- Avoid returning empty media_image_url string ([@JackWindows] - [#11557]) ([media_player.cast docs])
+- Core support for hass.io calls & Bugfix check_config ([@pvizeli] - [#11571]) ([__init__ docs]) ([hassio docs]) ([updater docs])
+- Fix Tahoma stop command for 2 types of shutters ([@bakedraccoon] - [#11588]) ([cover.tahoma docs])
+- Pushbullet email support (fix) ([@tschmidty69] - [#11590]) ([notify.pushbullet docs])
+- Fix state for trigger with forced updates ([@armills] - [#11595]) ([automation.state docs])
+- Snips add say and say_actions services (new) ([@tschmidty69] - [#11596]) ([snips docs])
+- Concord232 alarm arm away fix ([@rwa] - [#11597]) ([alarm_control_panel.concord232 docs]) ([binary_sensor.concord232 docs])
+- Bugfix and cleanup for Rfxtrx ([@danielhiversen] - [#11600])
+- Xiaomi lib upgrade ([@danielhiversen] - [#11603])
+- Upgrade yarl to 0.18.0 ([@fabaff] - [#11609])
+- patch stop command ([@bakedraccoon] - [#11612]) ([cover.tahoma docs])
+- Use kelvin/mireds correctly for setting iglo white ([@jesserockz] - [#11622])
+- Update Pyarlo to 0.1.2 ([@arsaboo] - [#11626])
+
+[#10296]: https://github.com/home-assistant/home-assistant/pull/10296
+[#10321]: https://github.com/home-assistant/home-assistant/pull/10321
+[#10547]: https://github.com/home-assistant/home-assistant/pull/10547
+[#10699]: https://github.com/home-assistant/home-assistant/pull/10699
+[#10795]: https://github.com/home-assistant/home-assistant/pull/10795
+[#10841]: https://github.com/home-assistant/home-assistant/pull/10841
+[#10957]: https://github.com/home-assistant/home-assistant/pull/10957
+[#10969]: https://github.com/home-assistant/home-assistant/pull/10969
+[#10979]: https://github.com/home-assistant/home-assistant/pull/10979
+[#10983]: https://github.com/home-assistant/home-assistant/pull/10983
+[#11023]: https://github.com/home-assistant/home-assistant/pull/11023
+[#11027]: https://github.com/home-assistant/home-assistant/pull/11027
+[#11036]: https://github.com/home-assistant/home-assistant/pull/11036
+[#11039]: https://github.com/home-assistant/home-assistant/pull/11039
+[#11053]: https://github.com/home-assistant/home-assistant/pull/11053
+[#11064]: https://github.com/home-assistant/home-assistant/pull/11064
+[#11069]: https://github.com/home-assistant/home-assistant/pull/11069
+[#11072]: https://github.com/home-assistant/home-assistant/pull/11072
+[#11088]: https://github.com/home-assistant/home-assistant/pull/11088
+[#11096]: https://github.com/home-assistant/home-assistant/pull/11096
+[#11110]: https://github.com/home-assistant/home-assistant/pull/11110
+[#11123]: https://github.com/home-assistant/home-assistant/pull/11123
+[#11140]: https://github.com/home-assistant/home-assistant/pull/11140
+[#11159]: https://github.com/home-assistant/home-assistant/pull/11159
+[#11171]: https://github.com/home-assistant/home-assistant/pull/11171
+[#11172]: https://github.com/home-assistant/home-assistant/pull/11172
+[#11175]: https://github.com/home-assistant/home-assistant/pull/11175
+[#11180]: https://github.com/home-assistant/home-assistant/pull/11180
+[#11182]: https://github.com/home-assistant/home-assistant/pull/11182
+[#11188]: https://github.com/home-assistant/home-assistant/pull/11188
+[#11193]: https://github.com/home-assistant/home-assistant/pull/11193
+[#11202]: https://github.com/home-assistant/home-assistant/pull/11202
+[#11216]: https://github.com/home-assistant/home-assistant/pull/11216
+[#11232]: https://github.com/home-assistant/home-assistant/pull/11232
+[#11235]: https://github.com/home-assistant/home-assistant/pull/11235
+[#11238]: https://github.com/home-assistant/home-assistant/pull/11238
+[#11242]: https://github.com/home-assistant/home-assistant/pull/11242
+[#11243]: https://github.com/home-assistant/home-assistant/pull/11243
+[#11244]: https://github.com/home-assistant/home-assistant/pull/11244
+[#11245]: https://github.com/home-assistant/home-assistant/pull/11245
+[#11250]: https://github.com/home-assistant/home-assistant/pull/11250
+[#11251]: https://github.com/home-assistant/home-assistant/pull/11251
+[#11260]: https://github.com/home-assistant/home-assistant/pull/11260
+[#11268]: https://github.com/home-assistant/home-assistant/pull/11268
+[#11269]: https://github.com/home-assistant/home-assistant/pull/11269
+[#11270]: https://github.com/home-assistant/home-assistant/pull/11270
+[#11271]: https://github.com/home-assistant/home-assistant/pull/11271
+[#11274]: https://github.com/home-assistant/home-assistant/pull/11274
+[#11280]: https://github.com/home-assistant/home-assistant/pull/11280
+[#11281]: https://github.com/home-assistant/home-assistant/pull/11281
+[#11282]: https://github.com/home-assistant/home-assistant/pull/11282
+[#11296]: https://github.com/home-assistant/home-assistant/pull/11296
+[#11297]: https://github.com/home-assistant/home-assistant/pull/11297
+[#11298]: https://github.com/home-assistant/home-assistant/pull/11298
+[#11301]: https://github.com/home-assistant/home-assistant/pull/11301
+[#11304]: https://github.com/home-assistant/home-assistant/pull/11304
+[#11307]: https://github.com/home-assistant/home-assistant/pull/11307
+[#11308]: https://github.com/home-assistant/home-assistant/pull/11308
+[#11309]: https://github.com/home-assistant/home-assistant/pull/11309
+[#11310]: https://github.com/home-assistant/home-assistant/pull/11310
+[#11311]: https://github.com/home-assistant/home-assistant/pull/11311
+[#11312]: https://github.com/home-assistant/home-assistant/pull/11312
+[#11315]: https://github.com/home-assistant/home-assistant/pull/11315
+[#11316]: https://github.com/home-assistant/home-assistant/pull/11316
+[#11317]: https://github.com/home-assistant/home-assistant/pull/11317
+[#11318]: https://github.com/home-assistant/home-assistant/pull/11318
+[#11319]: https://github.com/home-assistant/home-assistant/pull/11319
+[#11326]: https://github.com/home-assistant/home-assistant/pull/11326
+[#11329]: https://github.com/home-assistant/home-assistant/pull/11329
+[#11331]: https://github.com/home-assistant/home-assistant/pull/11331
+[#11332]: https://github.com/home-assistant/home-assistant/pull/11332
+[#11333]: https://github.com/home-assistant/home-assistant/pull/11333
+[#11334]: https://github.com/home-assistant/home-assistant/pull/11334
+[#11335]: https://github.com/home-assistant/home-assistant/pull/11335
+[#11336]: https://github.com/home-assistant/home-assistant/pull/11336
+[#11340]: https://github.com/home-assistant/home-assistant/pull/11340
+[#11341]: https://github.com/home-assistant/home-assistant/pull/11341
+[#11344]: https://github.com/home-assistant/home-assistant/pull/11344
+[#11345]: https://github.com/home-assistant/home-assistant/pull/11345
+[#11346]: https://github.com/home-assistant/home-assistant/pull/11346
+[#11348]: https://github.com/home-assistant/home-assistant/pull/11348
+[#11350]: https://github.com/home-assistant/home-assistant/pull/11350
+[#11352]: https://github.com/home-assistant/home-assistant/pull/11352
+[#11354]: https://github.com/home-assistant/home-assistant/pull/11354
+[#11357]: https://github.com/home-assistant/home-assistant/pull/11357
+[#11362]: https://github.com/home-assistant/home-assistant/pull/11362
+[#11369]: https://github.com/home-assistant/home-assistant/pull/11369
+[#11375]: https://github.com/home-assistant/home-assistant/pull/11375
+[#11379]: https://github.com/home-assistant/home-assistant/pull/11379
+[#11381]: https://github.com/home-assistant/home-assistant/pull/11381
+[#11383]: https://github.com/home-assistant/home-assistant/pull/11383
+[#11386]: https://github.com/home-assistant/home-assistant/pull/11386
+[#11390]: https://github.com/home-assistant/home-assistant/pull/11390
+[#11394]: https://github.com/home-assistant/home-assistant/pull/11394
+[#11395]: https://github.com/home-assistant/home-assistant/pull/11395
+[#11397]: https://github.com/home-assistant/home-assistant/pull/11397
+[#11401]: https://github.com/home-assistant/home-assistant/pull/11401
+[#11402]: https://github.com/home-assistant/home-assistant/pull/11402
+[#11404]: https://github.com/home-assistant/home-assistant/pull/11404
+[#11410]: https://github.com/home-assistant/home-assistant/pull/11410
+[#11412]: https://github.com/home-assistant/home-assistant/pull/11412
+[#11414]: https://github.com/home-assistant/home-assistant/pull/11414
+[#11416]: https://github.com/home-assistant/home-assistant/pull/11416
+[#11417]: https://github.com/home-assistant/home-assistant/pull/11417
+[#11422]: https://github.com/home-assistant/home-assistant/pull/11422
+[#11423]: https://github.com/home-assistant/home-assistant/pull/11423
+[#11427]: https://github.com/home-assistant/home-assistant/pull/11427
+[#11435]: https://github.com/home-assistant/home-assistant/pull/11435
+[#11438]: https://github.com/home-assistant/home-assistant/pull/11438
+[#11439]: https://github.com/home-assistant/home-assistant/pull/11439
+[#11441]: https://github.com/home-assistant/home-assistant/pull/11441
+[#11442]: https://github.com/home-assistant/home-assistant/pull/11442
+[#11444]: https://github.com/home-assistant/home-assistant/pull/11444
+[#11445]: https://github.com/home-assistant/home-assistant/pull/11445
+[#11447]: https://github.com/home-assistant/home-assistant/pull/11447
+[#11451]: https://github.com/home-assistant/home-assistant/pull/11451
+[#11452]: https://github.com/home-assistant/home-assistant/pull/11452
+[#11453]: https://github.com/home-assistant/home-assistant/pull/11453
+[#11456]: https://github.com/home-assistant/home-assistant/pull/11456
+[#11457]: https://github.com/home-assistant/home-assistant/pull/11457
+[#11460]: https://github.com/home-assistant/home-assistant/pull/11460
+[#11461]: https://github.com/home-assistant/home-assistant/pull/11461
+[#11462]: https://github.com/home-assistant/home-assistant/pull/11462
+[#11465]: https://github.com/home-assistant/home-assistant/pull/11465
+[#11467]: https://github.com/home-assistant/home-assistant/pull/11467
+[#11468]: https://github.com/home-assistant/home-assistant/pull/11468
+[#11469]: https://github.com/home-assistant/home-assistant/pull/11469
+[#11476]: https://github.com/home-assistant/home-assistant/pull/11476
+[#11477]: https://github.com/home-assistant/home-assistant/pull/11477
+[#11478]: https://github.com/home-assistant/home-assistant/pull/11478
+[#11479]: https://github.com/home-assistant/home-assistant/pull/11479
+[#11480]: https://github.com/home-assistant/home-assistant/pull/11480
+[#11483]: https://github.com/home-assistant/home-assistant/pull/11483
+[#11485]: https://github.com/home-assistant/home-assistant/pull/11485
+[#11487]: https://github.com/home-assistant/home-assistant/pull/11487
+[#11488]: https://github.com/home-assistant/home-assistant/pull/11488
+[#11492]: https://github.com/home-assistant/home-assistant/pull/11492
+[#11497]: https://github.com/home-assistant/home-assistant/pull/11497
+[#11499]: https://github.com/home-assistant/home-assistant/pull/11499
+[#11504]: https://github.com/home-assistant/home-assistant/pull/11504
+[#11505]: https://github.com/home-assistant/home-assistant/pull/11505
+[#11506]: https://github.com/home-assistant/home-assistant/pull/11506
+[#11509]: https://github.com/home-assistant/home-assistant/pull/11509
+[#11510]: https://github.com/home-assistant/home-assistant/pull/11510
+[#11511]: https://github.com/home-assistant/home-assistant/pull/11511
+[#11513]: https://github.com/home-assistant/home-assistant/pull/11513
+[#11519]: https://github.com/home-assistant/home-assistant/pull/11519
+[#11520]: https://github.com/home-assistant/home-assistant/pull/11520
+[#11521]: https://github.com/home-assistant/home-assistant/pull/11521
+[#11522]: https://github.com/home-assistant/home-assistant/pull/11522
+[#11531]: https://github.com/home-assistant/home-assistant/pull/11531
+[#11534]: https://github.com/home-assistant/home-assistant/pull/11534
+[#11535]: https://github.com/home-assistant/home-assistant/pull/11535
+[#11538]: https://github.com/home-assistant/home-assistant/pull/11538
+[#11542]: https://github.com/home-assistant/home-assistant/pull/11542
+[#11545]: https://github.com/home-assistant/home-assistant/pull/11545
+[#11549]: https://github.com/home-assistant/home-assistant/pull/11549
+[#11553]: https://github.com/home-assistant/home-assistant/pull/11553
+[#11557]: https://github.com/home-assistant/home-assistant/pull/11557
+[#11560]: https://github.com/home-assistant/home-assistant/pull/11560
+[#11561]: https://github.com/home-assistant/home-assistant/pull/11561
+[#11563]: https://github.com/home-assistant/home-assistant/pull/11563
+[#11567]: https://github.com/home-assistant/home-assistant/pull/11567
+[#11571]: https://github.com/home-assistant/home-assistant/pull/11571
+[#11574]: https://github.com/home-assistant/home-assistant/pull/11574
+[#11578]: https://github.com/home-assistant/home-assistant/pull/11578
+[#11579]: https://github.com/home-assistant/home-assistant/pull/11579
+[#11583]: https://github.com/home-assistant/home-assistant/pull/11583
+[#11586]: https://github.com/home-assistant/home-assistant/pull/11586
+[#11587]: https://github.com/home-assistant/home-assistant/pull/11587
+[#11588]: https://github.com/home-assistant/home-assistant/pull/11588
+[#11590]: https://github.com/home-assistant/home-assistant/pull/11590
+[#11595]: https://github.com/home-assistant/home-assistant/pull/11595
+[#11596]: https://github.com/home-assistant/home-assistant/pull/11596
+[#11597]: https://github.com/home-assistant/home-assistant/pull/11597
+[#11600]: https://github.com/home-assistant/home-assistant/pull/11600
+[#11603]: https://github.com/home-assistant/home-assistant/pull/11603
+[#11609]: https://github.com/home-assistant/home-assistant/pull/11609
+[#11612]: https://github.com/home-assistant/home-assistant/pull/11612
+[#11622]: https://github.com/home-assistant/home-assistant/pull/11622
+[#11626]: https://github.com/home-assistant/home-assistant/pull/11626
+[@Chris-V]: https://github.com/Chris-V
+[@ChristianKuehnel]: https://github.com/ChristianKuehnel
+[@DanNixon]: https://github.com/DanNixon
+[@Human]: https://github.com/Human
+[@JackWindows]: https://github.com/JackWindows
+[@JulianKahnert]: https://github.com/JulianKahnert
+[@Julio-Guerra]: https://github.com/Julio-Guerra
+[@Julius2342]: https://github.com/Julius2342
+[@KJonline]: https://github.com/KJonline
+[@Kane610]: https://github.com/Kane610
+[@Klathmon]: https://github.com/Klathmon
+[@Klikini]: https://github.com/Klikini
+[@Laqoore]: https://github.com/Laqoore
+[@OttoWinter]: https://github.com/OttoWinter
+[@OverloadUT]: https://github.com/OverloadUT
+[@PeWu]: https://github.com/PeWu
+[@PhracturedBlue]: https://github.com/PhracturedBlue
+[@ReneNulschDE]: https://github.com/ReneNulschDE
+[@SteveEasley]: https://github.com/SteveEasley
+[@abjorshammar]: https://github.com/abjorshammar
+[@abondoe]: https://github.com/abondoe
+[@akatrevorjay]: https://github.com/akatrevorjay
+[@amelchio]: https://github.com/amelchio
+[@andersonshatch]: https://github.com/andersonshatch
+[@andreacampi]: https://github.com/andreacampi
+[@andrey-git]: https://github.com/andrey-git
+[@aosadchyy]: https://github.com/aosadchyy
+[@armills]: https://github.com/armills
+[@arsaboo]: https://github.com/arsaboo
+[@awkwardDuck]: https://github.com/awkwardDuck
+[@bachya]: https://github.com/bachya
+[@bakedraccoon]: https://github.com/bakedraccoon
+[@balloob]: https://github.com/balloob
+[@camrun91]: https://github.com/camrun91
+[@cdce8p]: https://github.com/cdce8p
+[@cgarwood]: https://github.com/cgarwood
+[@cgtobi]: https://github.com/cgtobi
+[@ciotlosm]: https://github.com/ciotlosm
+[@cmsimike]: https://github.com/cmsimike
+[@cnrd]: https://github.com/cnrd
+[@cpcowart]: https://github.com/cpcowart
+[@daenny]: https://github.com/daenny
+[@danielhiversen]: https://github.com/danielhiversen
+[@danielperna84]: https://github.com/danielperna84
+[@dfiel]: https://github.com/dfiel
+[@dfinlay]: https://github.com/dfinlay
+[@djchen]: https://github.com/djchen
+[@ericpignet]: https://github.com/ericpignet
+[@etsinko]: https://github.com/etsinko
+[@fabaff]: https://github.com/fabaff
+[@florianj1]: https://github.com/florianj1
+[@foxel]: https://github.com/foxel
+[@frwickst]: https://github.com/frwickst
+[@goldminenine]: https://github.com/goldminenine
+[@goyney]: https://github.com/goyney
+[@hawk259]: https://github.com/hawk259
+[@jbarrancos]: https://github.com/jbarrancos
+[@jeroenterheerdt]: https://github.com/jeroenterheerdt
+[@jesserockz]: https://github.com/jesserockz
+[@kennedyshead]: https://github.com/kennedyshead
+[@markferry]: https://github.com/markferry
+[@masarliev]: https://github.com/masarliev
+[@michaelkuty]: https://github.com/michaelkuty
+[@nkgilley]: https://github.com/nkgilley
+[@notoriousbdg]: https://github.com/notoriousbdg
+[@pavoni]: https://github.com/pavoni
+[@philk]: https://github.com/philk
+[@pvizeli]: https://github.com/pvizeli
+[@randellhodges]: https://github.com/randellhodges
+[@rofrantz]: https://github.com/rofrantz
+[@rwa]: https://github.com/rwa
+[@ryanm101]: https://github.com/ryanm101
+[@schmittx]: https://github.com/schmittx
+[@schnoetz]: https://github.com/schnoetz
+[@swilson]: https://github.com/swilson
+[@thibmaek]: https://github.com/thibmaek
+[@timstanley1985]: https://github.com/timstanley1985
+[@tinloaf]: https://github.com/tinloaf
+[@titilambert]: https://github.com/titilambert
+[@tomaszduda23]: https://github.com/tomaszduda23
+[@tomwaters]: https://github.com/tomwaters
+[@tschmidty69]: https://github.com/tschmidty69
+[@ttroy50]: https://github.com/ttroy50
+[@ulido]: https://github.com/ulido
+[@veleek]: https://github.com/veleek
+[@w1ll1am23]: https://github.com/w1ll1am23
+[@yienxu]: https://github.com/yienxu
+[__init__ docs]: https://home-assistant.io/components/__init__/
+[alarm_control_panel.alarmdecoder docs]: https://home-assistant.io/components/alarm_control_panel.alarmdecoder/
+[alarm_control_panel.concord232 docs]: https://home-assistant.io/components/alarm_control_panel.concord232/
+[alarm_control_panel.egardia docs]: https://home-assistant.io/components/alarm_control_panel.egardia/
+[alarmdecoder docs]: https://home-assistant.io/components/alarmdecoder/
+[alexa.intent docs]: https://home-assistant.io/components/alexa.intent/
+[alexa.smart_home docs]: https://home-assistant.io/components/alexa.smart_home/
+[api docs]: https://home-assistant.io/components/api/
+[automation.state docs]: https://home-assistant.io/docs/automation/trigger/#state-trigger
+[binary_sensor docs]: https://home-assistant.io/components/binary_sensor/
+[binary_sensor.alarmdecoder docs]: https://home-assistant.io/components/binary_sensor.alarmdecoder/
+[binary_sensor.concord232 docs]: https://home-assistant.io/components/binary_sensor.concord232/
+[binary_sensor.deconz docs]: https://home-assistant.io/components/binary_sensor.deconz/
+[binary_sensor.isy994 docs]: https://home-assistant.io/components/binary_sensor.isy994/
+[binary_sensor.knx docs]: https://home-assistant.io/components/binary_sensor.knx/
+[binary_sensor.rest docs]: https://home-assistant.io/components/binary_sensor.rest/
+[binary_sensor.template docs]: https://home-assistant.io/components/binary_sensor.template/
+[binary_sensor.threshold docs]: https://home-assistant.io/components/binary_sensor.threshold/
+[binary_sensor.trend docs]: https://home-assistant.io/components/binary_sensor.trend/
+[binary_sensor.workday docs]: https://home-assistant.io/components/binary_sensor.workday/
+[camera.doorbird docs]: https://home-assistant.io/components/camera.doorbird/
+[camera.uvc docs]: https://home-assistant.io/components/camera.uvc/
+[climate docs]: https://home-assistant.io/components/climate/
+[climate.daikin docs]: https://home-assistant.io/components/climate.daikin/
+[climate.demo docs]: https://home-assistant.io/components/climate.demo/
+[climate.econet docs]: https://home-assistant.io/components/climate.econet/
+[climate.generic_thermostat docs]: https://home-assistant.io/components/climate.generic_thermostat/
+[climate.hive docs]: https://home-assistant.io/components/climate.hive/
+[climate.homematic docs]: https://home-assistant.io/components/climate.homematic/
+[climate.knx docs]: https://home-assistant.io/components/climate.knx/
+[climate.netatmo docs]: https://home-assistant.io/components/climate.netatmo/
+[climate.sensibo docs]: https://home-assistant.io/components/climate.sensibo/
+[climate.tado docs]: https://home-assistant.io/components/climate.tado/
+[climate.touchline docs]: https://home-assistant.io/components/climate.touchline/
+[cloud docs]: https://home-assistant.io/components/cloud/
+[cloud.auth_api docs]: https://home-assistant.io/components/cloud.auth_api/
+[cloud.http_api docs]: https://home-assistant.io/components/cloud.http_api/
+[cloud.iot docs]: https://home-assistant.io/components/cloud.iot/
+[coinbase docs]: https://home-assistant.io/components/coinbase/
+[conversation docs]: https://home-assistant.io/components/conversation/
+[cover.isy994 docs]: https://home-assistant.io/components/cover.isy994/
+[cover.knx docs]: https://home-assistant.io/components/cover.knx/
+[cover.tahoma docs]: https://home-assistant.io/components/cover.tahoma/
+[cover.template docs]: https://home-assistant.io/components/cover.template/
+[cover.xiaomi_aqara docs]: https://home-assistant.io/components/cover.xiaomi_aqara/
+[deconz docs]: https://home-assistant.io/components/deconz/
+[device_tracker docs]: https://home-assistant.io/components/device_tracker/
+[device_tracker.asuswrt docs]: https://home-assistant.io/components/device_tracker.asuswrt/
+[device_tracker.bluetooth_le_tracker docs]: https://home-assistant.io/components/device_tracker.bluetooth_le_tracker/
+[device_tracker.bluetooth_tracker docs]: https://home-assistant.io/components/device_tracker.bluetooth_tracker/
+[device_tracker.gpslogger docs]: https://home-assistant.io/components/device_tracker.gpslogger/
+[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
+[device_tracker.ping docs]: https://home-assistant.io/components/device_tracker.ping/
+[device_tracker.snmp docs]: https://home-assistant.io/components/device_tracker.snmp/
+[device_tracker.tile docs]: https://home-assistant.io/components/device_tracker.tile/
+[digital_ocean docs]: https://home-assistant.io/components/digital_ocean/
+[fan.insteon_local docs]: https://home-assistant.io/components/fan.insteon_local/
+[fan.isy994 docs]: https://home-assistant.io/components/fan.isy994/
+[fan.xiaomi_miio docs]: https://home-assistant.io/components/fan.xiaomi_miio/
+[google_assistant docs]: https://home-assistant.io/components/google_assistant/
+[google_assistant.http docs]: https://home-assistant.io/components/google_assistant.http/
+[google_assistant.smart_home docs]: https://home-assistant.io/components/google_assistant.smart_home/
+[group docs]: https://home-assistant.io/components/group/
+[hassio docs]: https://home-assistant.io/components/hassio/
+[history docs]: https://home-assistant.io/components/history/
+[hive docs]: https://home-assistant.io/components/hive/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[http docs]: https://home-assistant.io/components/http/
+[image_processing.opencv docs]: https://home-assistant.io/components/image_processing.opencv/
+[input_boolean docs]: https://home-assistant.io/components/input_boolean/
+[input_select docs]: https://home-assistant.io/components/input_select/
+[insteon_local docs]: https://home-assistant.io/components/insteon_local/
+[isy994 docs]: https://home-assistant.io/components/isy994/
+[knx docs]: https://home-assistant.io/components/knx/
+[light.deconz docs]: https://home-assistant.io/components/light.deconz/
+[light.greenwave docs]: https://home-assistant.io/components/light.greenwave/
+[light.hive docs]: https://home-assistant.io/components/light.hive/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[light.iglo docs]: https://home-assistant.io/components/light.iglo/
+[light.insteon_local docs]: https://home-assistant.io/components/light.insteon_local/
+[light.isy994 docs]: https://home-assistant.io/components/light.isy994/
+[light.knx docs]: https://home-assistant.io/components/light.knx/
+[light.lifx docs]: https://home-assistant.io/components/light.lifx/
+[light.mqtt docs]: https://home-assistant.io/components/light.mqtt/
+[light.osramlightify docs]: https://home-assistant.io/components/light.osramlightify/
+[light.template docs]: https://home-assistant.io/components/light.template/
+[light.tplink docs]: https://home-assistant.io/components/light.tplink/
+[light.xiaomi_miio docs]: https://home-assistant.io/components/light.xiaomi_miio/
+[light.zha docs]: https://home-assistant.io/components/light.zha/
+[lock.isy994 docs]: https://home-assistant.io/components/lock.isy994/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player.cast docs]: https://home-assistant.io/components/media_player.cast/
+[media_player.kodi docs]: https://home-assistant.io/components/media_player.kodi/
+[media_player.monoprice docs]: https://home-assistant.io/components/media_player.monoprice/
+[media_player.plex docs]: https://home-assistant.io/components/media_player.plex/
+[media_player.squeezebox docs]: https://home-assistant.io/components/media_player.squeezebox/
+[media_player.yamaha docs]: https://home-assistant.io/components/media_player.yamaha/
+[modbus docs]: https://home-assistant.io/components/modbus/
+[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
+[notify.pushbullet docs]: https://home-assistant.io/components/notify.pushbullet/
+[notify.webostv docs]: https://home-assistant.io/components/notify.webostv/
+[octoprint docs]: https://home-assistant.io/components/octoprint/
+[prometheus docs]: https://home-assistant.io/components/prometheus/
+[python_script docs]: https://home-assistant.io/components/python_script/
+[rainbird docs]: https://home-assistant.io/components/rainbird/
+[remember_the_milk docs]: https://home-assistant.io/components/remember_the_milk/
+[sensor.alpha_vantage docs]: https://home-assistant.io/components/sensor.alpha_vantage/
+[sensor.bitcoin docs]: https://home-assistant.io/components/sensor.bitcoin/
+[sensor.coinbase docs]: https://home-assistant.io/components/sensor.coinbase/
+[sensor.deconz docs]: https://home-assistant.io/components/sensor.deconz/
+[sensor.deutsche_bahn docs]: https://home-assistant.io/components/sensor.deutsche_bahn/
+[sensor.discogs docs]: https://home-assistant.io/components/sensor.discogs/
+[sensor.etherscan docs]: https://home-assistant.io/components/sensor.etherscan/
+[sensor.fido docs]: https://home-assistant.io/components/sensor.fido/
+[sensor.hydroquebec docs]: https://home-assistant.io/components/sensor.hydroquebec/
+[sensor.imap_email_content docs]: https://home-assistant.io/components/sensor.imap_email_content/
+[sensor.irish_rail_transport docs]: https://home-assistant.io/components/sensor.irish_rail_transport/
+[sensor.isy994 docs]: https://home-assistant.io/components/sensor.isy994/
+[sensor.knx docs]: https://home-assistant.io/components/sensor.knx/
+[sensor.luftdaten docs]: https://home-assistant.io/components/sensor.luftdaten/
+[sensor.metoffice docs]: https://home-assistant.io/components/sensor.metoffice/
+[sensor.miflora docs]: https://home-assistant.io/components/sensor.miflora/
+[sensor.mqtt docs]: https://home-assistant.io/components/sensor.mqtt/
+[sensor.openweathermap docs]: https://home-assistant.io/components/sensor.openweathermap/
+[sensor.plex docs]: https://home-assistant.io/components/sensor.plex/
+[sensor.rainbird docs]: https://home-assistant.io/components/sensor.rainbird/
+[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/
+[sensor.sochain docs]: https://home-assistant.io/components/sensor.sochain/
+[sensor.statistics docs]: https://home-assistant.io/components/sensor.statistics/
+[sensor.steam_online docs]: https://home-assistant.io/components/sensor.steam_online/
+[sensor.swiss_public_transport docs]: https://home-assistant.io/components/sensor.swiss_public_transport/
+[sensor.systemmonitor docs]: https://home-assistant.io/components/sensor.systemmonitor/
+[sensor.tado docs]: https://home-assistant.io/components/sensor.tado/
+[sensor.template docs]: https://home-assistant.io/components/sensor.template/
+[sensor.transmission docs]: https://home-assistant.io/components/sensor.transmission/
+[sensor.xbox_live docs]: https://home-assistant.io/components/sensor.xbox_live/
+[sensor.zoneminder docs]: https://home-assistant.io/components/sensor.zoneminder/
+[snips docs]: https://home-assistant.io/components/snips/
+[switch.insteon_local docs]: https://home-assistant.io/components/switch.insteon_local/
+[switch.isy994 docs]: https://home-assistant.io/components/switch.isy994/
+[switch.knx docs]: https://home-assistant.io/components/switch.knx/
+[switch.mochad docs]: https://home-assistant.io/components/switch.mochad/
+[switch.rainbird docs]: https://home-assistant.io/components/switch.rainbird/
+[switch.rpi_rf docs]: https://home-assistant.io/components/switch.rpi_rf/
+[switch.snmp docs]: https://home-assistant.io/components/switch.snmp/
+[switch.template docs]: https://home-assistant.io/components/switch.template/
+[switch.tplink docs]: https://home-assistant.io/components/switch.tplink/
+[switch.transmission docs]: https://home-assistant.io/components/switch.transmission/
+[switch.xiaomi_miio docs]: https://home-assistant.io/components/switch.xiaomi_miio/
+[tahoma docs]: https://home-assistant.io/components/tahoma/
+[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
+[timer docs]: https://home-assistant.io/components/timer/
+[tts.baidu docs]: https://home-assistant.io/components/tts.baidu/
+[tts.marytts docs]: https://home-assistant.io/components/tts.marytts/
+[updater docs]: https://home-assistant.io/components/updater/
+[vacuum.xiaomi_miio docs]: https://home-assistant.io/components/vacuum.xiaomi_miio/
+[weather.darksky docs]: https://home-assistant.io/components/weather.darksky/
+[weather.openweathermap docs]: https://home-assistant.io/components/weather.openweathermap/
+[weather.yweather docs]: https://home-assistant.io/components/weather.yweather/
+[websocket_api docs]: https://home-assistant.io/components/websocket_api/
+[wemo docs]: https://home-assistant.io/components/wemo/
+[zigbee docs]: https://home-assistant.io/components/zigbee/

source/index.html

@@ -38,7 +38,7 @@ description: Open-source home automation platform running on Python 3. Track and
         Use Alexa to control Home Assistant.
 
         <div class='links'>
-          <a href='/blog/2017/12/17/introducing-home-assistant-cloud/'>LEARN MORE</a>
+          <a href='/components/cloud/'>LEARN MORE</a>
         </div>
       </div>