Merge pull request #4119 from home-assistant/release-0-59

0.59

_config.yml

@@ -139,12 +139,12 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 58
-current_patch_version: 1
-date_released: 2017-11-21
+current_minor_version: 59
+current_patch_version: 0
+date_released: 2017-12-03
 
 # 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-0581---november-21"
+patch_version_notes: "#"
 # Minor release (Example #release-0431---april-25):

source/_addons/tellstick.markdown

@@ -0,0 +1,80 @@
+---
+layout: page
+title: "TellStick"
+description: "Telldus TellStick service enabler and tools."
+date: 2017-11-30 21:43
+sidebar: true
+comments: false
+sharing: true
+footer: true
+featured: false
+---
+
+Setting up the [Tellstick](http://telldus.com) service and tools contained in the [telldus-core](http://developer.telldus.com/) package and adding configuration to enable Tellstick and Tellstick Duo to work on your Hass.io.
+
+
+To use this add-on, you first install it from the list of Built-in add-ons in Hass.io.
+After installation you are presented with a default and example configuration, to alter this you must follow both the JSON format and also be aligned with the [valid parameters for Tellstick configuration file (tellstick.conf)](https://developer.telldus.com/wiki/TellStick_conf).
+
+After any changes has been made to the configuration you need to restart the add-on for the changes to take effect.
+
+
+Configuration variables:
+
+- **id** (*Required*): This is a number and must be unique for each device. 
+- **name** (*Required*): A name for easy identification of the device. 
+- **protocol** (*Required*): This is the protocol the device uses. More on the different protocols later down. 
+- **model** (*Optional*): The parameter model is only used by some protocols where there exists different types of devices using the same protocol. This can be dimmers versus non-dimmers, codeswitch versus selflearning etc.
+- **house** (*Optional*): Depending on protocol the values here can vary a lot to identify or group per house or type.
+- **unit** (*Optional*): Unit identifier, in most cases a value between 1 to 16 and often used in combination with house.
+- **fade** (*Optional*): Fade is either `true` or `false` and tells a dimmer if is should fade smooth or instant between values (only for IKEA protocol as it seems).
+- **code** (*Optional*): A number series based on ones and zeroes often used for dip-switch based devices.
+
+
+
+
+In order to communicate with the add-on you will also need to add Hass.io specific data in the `configuration.yaml` file.
+For regular Home Assistant you only add `tellstick:` but for Hass.io and this add-on you need to add internal communication details.
+
+
+```yaml
+# Example configuration.yaml entry
+
+tellstick:
+    host: core-tellstick
+    port: [50800, 50801]
+    
+```
+
+
+
+To add [lights](https://home-assistant.io/components/light.tellstick/), [sensors](https://home-assistant.io/components/sensor.tellstick/) and [switches](https://home-assistant.io/components/switch.tellstick/) you follow the guidelines for each type individually that is [described for Home Assistant](https://home-assistant.io/components/tellstick/)
+
+
+## {% linkable_title Examples %}
+
+
+Example for adding more devices in the add-on configuration (note the comma separator between devices):
+
+```json
+{
+  "devices": [
+    {
+      "id": 1,
+      "name": "Outdoor light",
+      "protocol": "everflourish",
+      "model": "selflearning-switch",
+      "house": "A",
+      "unit": "1"
+    },
+    {
+      "id": 2,
+      "name": "Hallway dimmer",
+      "protocol": "risingsun",
+      "model": "selflearning-dimmer",
+      "house": "A",
+      "unit": "2"
+    }
+  ]
+}
+```

source/_components/alarm_control_panel.arlo.markdown

@@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling"
 ---
 
 
-The `arlo` control panel platform allows you to control your [Arlo](https://arlo.netgear.com/) base stations.
+The `arlo` alarm control panel allows you to control your [Arlo](https://arlo.netgear.com/) base stations. You can use it to switch modes and trigger alarms from Home Assistant.
 
 To get your [Arlo](https://arlo.netgear.com/) base stations working within Home Assistant, please follow the instructions for the general [Arlo component](/components/arlo).
 
@@ -26,6 +26,53 @@ alarm_control_panel:
   - platform: arlo
 ```
 
-Configuration variables:
+{% configuration %}
+home_mode_name:
+  description: "Arlo base station does not have a built-in home mode. You can map one of your custom modes to home assistant's home mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match exactly as you set it up in the Arlo app."
+  required: false
+  type: string
+away_mode_name:
+  description: "Arlo base station does not have a built-in away mode. You can map one of your custom modes to home assistant's away mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match eactly as you set it up in the Arlo app."
+  required: false
+  type: string
+  default: "`Armed` mode in Arlo"
+{% endconfiguration %}
+
+## {% linkable_title Examples %}
+
+These examples are based on an Arlo base station named `my_arlo_base_station`. Replace this with the name of your base station's `entity_id`.
+
+Arming the Arlo Base Station when leaving.
+
+```yaml
+- id: arm_arlo_when_leaving
+  alias: Arm Arlo cameras when leaving
+  trigger:
+    platform: state
+    entity_id: group.family
+    from: home
+    to: not_home
+  action:
+    service: alarm_control_panel.alarm_arm_away
+    entity_id: alarm_control_panel.my_arlo_base_station
+```
+
+Setting Arlo to a custom mode (mapped to `home_mode_name` in `configuration.yaml`) when arriving.
+
+```yaml
+- id: disarm_arlo_when_arriving
+  alias: Set Arlo cameras to Home mode when arriving
+  trigger:
+    platform: state
+    entity_id: group.family
+    from: not_home
+    to: home
+  action:
+    service: alarm_control_panel.alarm_arm_home
+    entity_id: alarm_control_panel.my_arlo_base_station
+```
+
+You can also completely disarm the Arlo base station by calling the `alarm_control_panel.alarm_disarm` service, and trigger the alarm by calling the `alarm_control_panel.alarm_trigger` service.
+
+More examples and configuration options can be found on the [Manual Alarm Control page](/components/alarm_control_panel.manual/#examples).
 
-- **home_mode_name**: (*Optional*): Arlo base station does not have a built-in home mode. You can map one of your custom modes to home assistant's home mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match exactly as you set it up in the Arlo app.

source/_components/binary_sensor.hive.markdown

@@ -0,0 +1,28 @@
+---
+layout: page
+title: "Hive Sensor"
+description: "Instructions on how to integrate Hive Sensors with Home Assistant."
+date: 2017-09-24 21:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: hive.png
+ha_category: Binary Sensor
+ha_release: 0.59
+ha_iot_class: "Cloud Polling"
+---
+
+
+The 'hive' binary sensor component integrates your Hive sensors into Home Assistant.
+
+The Hive sensor component supports the following Hive products:
+- **Hive Window or Door Sensor**
+- **Hive Motion Sensor**
+
+
+<p class='note'>
+Full configuration details can be found on the main [Hive component](/components/hive/) page.
+</p>
+
+

source/_components/binary_sensor.markdown

@@ -14,6 +14,7 @@ Binary sensors gather information about the state of devices which have a "digit
 The way these sensors are displayed in the frontend can be modified in the [customize section](/getting-started/customizing-devices/). The following device classes are supported for binary sensors:
 
 - **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
 - **connectivity**: `On` means connection present, `Off` means no connection
 - **gas**: `On` means gas detected
@@ -26,6 +27,7 @@ The way these sensors are displayed in the frontend can be modified in the [cust
 - **opening**: `On` means open, `Off` means closed
 - **plug**: `On` means device is plugged in, `Off` means device is unplugged
 - **power**: Power, over-current, etc.
+- **presence**: `On` means Home, `Off` means Away
 - **safety**: `On` means unsafe, `Off` means safe
 - **smoke**: `On` means smoke detected
 - **sound**: `On` means sound detected, `Off` means no sound

source/_components/climate.hive.markdown

@@ -0,0 +1,29 @@
+---
+layout: page
+title: "Hive Thermostat"
+description: "Instructions on how to integrate Hive thermostat(s) with Home Assistant."
+date: 2017-09-24 21:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: hive.png
+ha_category: Climate
+ha_release: 0.59
+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**.
+
+The Hive climate component supports the following Hive products:
+- **Hive Active Heating**
+- **Hive Multizone**
+- **Hot water control**
+
+
+<p class='note'>
+Full configuration details can be found on the main [Hive component](/components/hive/) page.
+</p>
+
+

source/_components/cover.tahoma.markdown

@@ -0,0 +1,21 @@
+---
+layout: page
+title: "Tahoma Cover"
+description: "Instructions how to integrate Tahoma covers into Home Assistant."
+date: 2017-07-18 12:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: tahoma.png
+ha_category: Cover
+ha_release: 0.59
+---
+
+To use your tahoma covers in your installation, add the following to your `configuration.yaml` file:
+
+``yaml
+# Example configuration.yml entry
+cover:
+  platform: tahoma
+```

source/_components/device_tracker.unifi_direct.markdown

@@ -0,0 +1,45 @@
+---
+layout: page
+title: "Ubiquiti Unifi direct AP"
+description: "Instructions how to use a Unifi WAP as a device tracker."
+date: 2017-11-17 14:59
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: ubiquiti.png
+ha_category: Presence Detection
+ha_release: 0.59
+---
+
+
+This platform allows you to detect presence by looking at devices connected to a [UniFi AP](http://ubnt.com/unifi-ap/). This device tracker differs form [Ubiquiti Unifi WAP](https://home-assistant.io/components/device_tracker.unifi/) because it doesn't require the Unifi controller software.
+
+To use this device tracker in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+device_tracker:
+  - platform: unifi_direct
+    host: YOUR_AP_IP_ADDRESS
+    username: YOUR_USERNAME
+    password: YOUR_PASSWORD
+```
+
+{% configuration %}
+host:
+  description: The hostname or IP address of your Unifi AP.
+  required: true
+  type: string
+username:
+  description: The username used to connect to your Unifi AP.
+  required: true
+  type: string
+password:
+  description: The password used to connect to your Unifi AP.
+  required: true
+  type: string
+{% endconfiguration %}
+
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
+

source/_components/discovery.markdown

@@ -35,6 +35,7 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
  * [SABnzbd downloader](https://home-assistant.io/components/sensor.sabnzbd/)
  * [Samsung TVs](https://home-assistant.io/components/media_player.samsungtv/)
  * [Sonos speakers](https://home-assistant.io/components/media_player.sonos/)
+ * [Telldus Live](https://home-assistant.io/components/tellduslive/)
  * [Yamaha media player](https://home-assistant.io/components/media_player.yamaha/)
  * [Yeelight Sunflower bulb](https://home-assistant.io/components/light.yeelightsunflower/)
 
@@ -77,6 +78,7 @@ Valid values for ignore are:
  * `sabnzbd`: SABnzbd downloader
  * `samsung_tv`: Samsung TVs
  * `sonos`: Sonos speakers
+ * `tellduslive`: Telldus Live
  * `yamaha`: Yamaha media player
  * `yeelight`: Yeelight Sunflower bulb
  

source/_components/dominos.markdown

@@ -0,0 +1,80 @@
+---
+layout: page
+title: "Dominos Pizza"
+description: "Instructions on how to setup Dominos Pizza ordering within Home Assistant."
+date: 2017-11-05 17:30
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: dominos.png
+ha_category: Other
+ha_version: 0.59
+---
+
+The `Dominos` component allows you to order Dominos Pizza from within your Home Assistant scripts and automations.
+
+At present, this component only supports ordering within Canada and the US.
+
+To enable the component, you need to set up your customer information and define some orders.
+
+Orders are a group of product codes. You can get these product codes by inspecting an order request from the Dominos web app, or you can [add this custom panel by following this readme](https://github.com/wardcraigj/hass-dominos-panel) to see the available product codes in a separate panel in your install.
+
+Currently, there is no support in this component for toppings, coupons or order tracking.
+
+```yaml
+dominos:
+  country_code: ca
+  first_name: Justin
+  last_name: Trudeau
+  email: justin.trudeau@parl.gc.ca
+  phone: 6139950253
+  address: 24 Sussex Dr, Ottawa, ON, K1M1M4
+  orders:
+  - name: Medium Pan
+    codes:
+      - P12IPAZA
+```
+
+Now you can use the Dominos service to order pizza within your automations:
+
+```yaml
+- service: dominos.order
+  data:
+    order_entity_id: dominos.medium_pan
+```
+
+{% configuration %}
+  country_code:
+    required: true
+    description: \'ca\' or \'us\', depending on your location
+    type: string
+  first_name:
+    required: true
+    description: Your first name
+    type: string
+  last_name:
+    required: true
+    description: Your last name
+    type: string
+  email:
+    required: true
+    description: Your email address
+    type: string
+  phone:
+    required: true
+    description: Your phone number
+    type: string
+  address:
+    required: true
+    description: Your delivery address
+    type: string
+  show_menu:
+    required: false
+    description: Dumps product codes from your nearest store into your log (for use in with the custom panel)
+    type: integer
+  orders:
+    required: false
+    description: Sets of product codes to use for ordering
+    type: list
+{% endconfiguration %}

source/_components/frontend.markdown

@@ -39,7 +39,11 @@ frontend:
             required: true
             type: [list, string]
   extra_html_url:
-    description: "List of addtional [resources](/developers/frontend_creating_custom_ui/) to load."
+    description: "List of addtional [resources](/developers/frontend_creating_custom_ui/) to load in `latest` javascript mode."
+    required: false
+    type: list
+  extra_html_url_es5:
+    description: "List of addtional [resources](/developers/frontend_creating_custom_ui/) to load in `es5` javascript mode."
     required: false
     type: list
   development_repo:

source/_components/hive.markdown

@@ -0,0 +1,54 @@
+---
+layout: page
+title: "Hive"
+description: "Instructions on how to integrate Hive devices with Home Assistant."
+date: 2017-09-24 21:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: hive.png
+ha_category: Hub
+ha_release: 0.59
+ha_iot_class: "Cloud Polling"
+---
+
+
+This Hive component is the main component to set up and integrate all supported Hive devices. Once configured with the minimum required details it will detect and add all your Hive devices into Home Assistant, including support for multizone heating.
+
+This component uses the unofficial API used in the official Hive website [https://my.hivehome.com](https://my.hivehome.com), and you will need to use the same Username and Password you use on the Hive website to configure this Hive component in Home Assistant.
+
+To add your Hive devices into your Home Assistant installation, using the default scan_interval, add the following to your 'configuration.yaml' file:
+
+```yaml
+# Example configuration.yaml entry
+hive:
+  username: YOUR_USERNAME
+  password: YOUR_PASSWORD
+```
+
+{% configuration %}
+username:
+  description: Your username from [https://my.hivehome.com](https://my.hivehome.com).
+  required: true
+  type: string
+password:
+  description: Your password from [https://my.hivehome.com](https://my.hivehome.com).
+  required: true
+  type: string
+scan_interval:
+  description: The time in minutes between Hive API calls
+  required: false
+  type: int
+  default: 2
+{% endconfiguration %}
+
+
+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 Plug
+- Hive Window or Door Sensor
+- Hive Motion Sensor

source/_components/influxdb.markdown

@@ -34,6 +34,8 @@ Configuration variables:
 - **database** (*Optional*): Name of the database to use. Defaults to `home_assistant`. The database must already exist.
 - **ssl** (*Optional*): Use https instead of http to connect. Defaults to false.
 - **verify_ssl** (*Optional*): Verify SSL certificate for https request. Defaults to false.
+- **max_retries** (*Optional*): Allow the component to retry if there was a network error when transmitting data
+- **retry_queue_limit** (*Optional*): If retry enabled, specify how much calls are allowed to be queued for retry.
 - **default_measurement** (*Optional*): Measurement name to use when an entity doesn't have a unit. Defaults to entity id.
 - **override_measurement** (*Optional*): Measurement name to use instead of unit or default measurement. This will store all data points in a single measurement.
 - **component_config**, **component_config_domain**, **component_config_glob** (*Optional*): These attributes contains component-specific override values. See [Customizing devices and services](https://home-assistant.io/getting-started/customizing-devices/) for format.
@@ -175,6 +177,7 @@ influxdb:
   password: MY_PASSWORD
   ssl: true
   verify_ssl: true
+  max_retries: 3
   default_measurement: state
   exclude:
     entities:

source/_components/knx.markdown

@@ -83,6 +83,7 @@ knx:
 - **fire_event** (*Optional*): If set to True, platform will write all received KNX messages to event bus
 - **fire_event_filter** (*Optional*): If `fire_event` is set `fire_event_filter` has to be specified. `fire_event_filter` defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HOme Assistant event bus. 
 - **state_updater** (*Optional*): The component will collect the current state of each configured device from the KNX bus to display it correctly within Home-Assistant. Set this option to False to prevent this behaviour.
+- **time_address** (*Optional*): Broadcast current local time to KNX bus with configured group address.
 
 ### {% linkable_title Services %}
 

source/_components/light.hive.markdown

@@ -0,0 +1,28 @@
+---
+layout: page
+title: "Hive Light"
+description: "Instructions on how to integrate Hive lights with Home Assistant."
+date: 2017-09-24 21:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: hive.png
+ha_category: Light
+ha_release: 0.59
+ha_iot_class: "Cloud Polling"
+---
+
+
+The 'hive' light component integrates your Hive lights into Home Assistant, enabling control of various settings, depending on the model light.
+
+The Hive light component supports the following Hive products:
+- **Hive Active Light Dimmable**
+- **Hive Active Light Cool to Warm White**
+
+
+<p class='note'>
+Full configuration details can be found on the main [Hive component](/components/hive/) page.
+</p>
+
+

source/_components/notify.lametric.markdown

@@ -12,17 +12,71 @@ ha_category: Notifications
 ha_release: 0.49
 ---
 
-This component allows to send notification to a LaMetric device. It need the LaMetric platform to be configured first.
+The `lametric` notification platform allows to send notification to a LaMetric device. It needs the LaMetric platform to be configured first.
+
+To enable LaMetric notifications in your installation, add the following to your `configuration.yaml` file:
 
 ```yaml
+# Example configuration.yaml entry
 notify:
-  name: lametric1
+  name: NOTIFIER_NAME
   platform: lametric
-  display_time: 20
-  icon: i555
 ```
 
-- **name** (*Optional*): The name of the LaMetric device. Usually it is "My Lametric"
-- **display_time** (*Optional*): Defines how long the message should be displayed (in seconds).
-- **icon** (*Optional*): An icon or animation. Check out the list of all icons her: https://developer.lametric.com/icons 
-Note that icons always begin with "i" while animations begin with "a". This is part of the name, you can't just use the number.
+{% configuration %}
+name:
+  description: "The optional parameter `name` allows multiple notifiers to be created. The notifier will bind to the service `notify.NOTIFIER_NAME`."
+  required: false
+  type: string
+  default: notify
+lifetime:
+  description: Defines how long the message remains in LaMetric notification queue (in seconds).
+  required: false
+  type: int
+  default: 10
+icon:
+  description: An icon or animation.
+  required: false
+  type: string
+cycles:
+  description: Defines how often the notification is displayed.
+  required: false
+  type: int
+  default: 1
+{% endconfiguration %}
+
+Check out the list of all icons at [https://developer.lametric.com/icons](https://developer.lametric.com/icons). Note that icons always begin with "i" while animations begin with "a". This is part of the name, you can't just use the number!
+
+## {% linkable_title Examples %}
+
+### {% linkable_title Full configuration example %}
+
+```yaml
+# Example configuration.yaml entry
+notify:
+  name: NOTIFIER_NAME
+  platform: lametric
+  lifetime: 20
+  icon: a7956
+  cycles: 3
+```
+
+### {% linkable_title Changing sounds and icons %}
+
+To add a notification sound or an icon override, it has to be done via service data.
+
+```yaml
+- alias: "Send notification on arrival at school"
+  trigger:
+    platform: state
+    entity_id: device_tracker.son_mobile
+    from: 'not_home'
+    to: 'school'
+  action:
+    service: notify.lametric
+    data:
+      message: "Son has arrived at school!"
+      data:
+        sound: 'notification'
+        icon: 'i51'
+ ```

source/_components/sensor.fail2ban.markdown

@@ -14,10 +14,10 @@ ha_release: 0.57
 ---
 
 
-The `fail2ban` sensor allows for IPs banned by [fail2ban](https://www.fail2ban.org/wiki/index.php/Main_Page) to be displayed in the Home Assistant front-end.  
+The `fail2ban` sensor allows for IPs banned by [fail2ban](https://www.fail2ban.org/wiki/index.php/Main_Page) to be displayed in the Home Assistant frontend.  
 
 <p class='note'>
-Your system must have fail2ban installed and correctly configured for this sensor to work.  In addition, Home Assistant must be able to read the fail2ban log file.
+Your system must have `fail2ban` installed and correctly configured for this sensor to work. In addition, Home Assistant must be able to read the `fail2ban` log file.
 </p>
 
 To enable this sensor, add the following lines to your `configuration.yaml`:
@@ -29,29 +29,38 @@ sensor:
     jails:
       - ssh
       - hass-iptables
-    file_path: /var/log/fail2ban.log
 ```
 
-Configuration variables:
-
-- **jails** (*Required*): List of configured jails you want to display (each jail is its own sensor).
-- **name** (*Optional*): Name of the sensor. Defaults to `fail2ban`.
-- **file_path** (*Optional*): Path to the fail2ban log.  Defaults to `/var/log/fail2ban.log`.
-- **scan_interval** (*Optional*): Used to limit how often log file is read and must be a positive integer (representing number of seconds to wait).  Defaults to 120.
+{% configuration %}
+jails:
+  description: List of configured jails you want to display.
+  required: true
+  type: list
+name:
+  description: Name of the sensor.
+  required: false
+  type: string
+  default: fail2ban
+file_path:
+  description: Path to the fail2ban log.
+  required: false
+  type: string
+  default: /var/log/fail2ban.log
+{% endconfiguration %}
 
 ### {% linkable_title Set up Fail2Ban %}
 
-For most set-ups, you can follow [this tutorial](https://home-assistant.io/cookbook/fail2ban/) to set up fail2ban on your system.  It will walk you through creating jails and filters, allowing you to monitor IPs that have been banned for too many failed ssh login attempts, as well as too many failed Home Assistant log in attempts.
+For most setups, you can follow [this tutorial](/cookbook/fail2ban/) to set up `fail2ban` on your system. It will walk you through creating jails and filters, allowing you to monitor IP addresses that have been banned for too many failed SSH login attempts, as well as too many failed Home Assistant login attempts.
 
 ### {% linkable_title Fail2Ban with Docker %}
 
 <p class='note'>
-These steps assume you already have the Home Assistant docker running behind nginx and that it is externally accessible.  It also assumes the docker is running with the `--net='host'` flag.
+These steps assume you already have the Home Assistant docker running behind NGINX and that it is externally accessible. It also assumes the docker is running with the `--net='host'` flag.
 </p>
 
-For those of us using Docker, the above tutorial may not be sufficient.  The following steps specifically outline how to set up `fail2ban` and Home Assistant when running Home Assistant within a Docker behind nginx.  The setup this was tested on was an unRAID server using the [let's encrypt docker](https://github.com/linuxserver/docker-letsencrypt) from linuxserver.io.
+For those of us using Docker, the above tutorial may not be sufficient. The following steps specifically outline how to set up `fail2ban` and Home Assistant when running Home Assistant within a Docker behind NGINX. The setup this was tested on was an unRAID server using the [let's encrypt docker](https://github.com/linuxserver/docker-letsencrypt) from linuxserver.io.
 
-#### Set http logger
+#### {% linkable_title Set http logger %}
 
 In your `configuration.yaml` file, add the following to the `logger` component to ensure that Home Assistant prints failed login attempts to the log.
 
@@ -61,7 +70,7 @@ logger:
     homeassistant.components.http.ban: warning
 ```
 
-#### Edit the `jail.local` file
+#### {% linkable_title Edit the `jail.local` file %}
 
 Next, we need to edit the `jail.local` file that is included with the Let's Encrypt docker linked above.  Note, for this tutorial, we'll only be implementing the `[hass-iptables]` jail from the [previously linked tutorial](https://home-assistant.io/cookbook/fail2ban/).
 
@@ -76,7 +85,7 @@ logpath = /hass/home-assistant.log
 maxretry = 5
 ```
 
-#### Create a filter for the Home Assistant jail
+#### {% linkable_title Create a filter for the Home Assistant jail %}
 
 Now we need to create a filter for `fail2ban` so that it can properly parse the log.  This is done with a `failregex`.  Create a file called `hass.local` within the `filter.d` directory in `/mnt/user/appdata/letsencrypt/fail2ban` and add the following:
 
@@ -93,7 +102,7 @@ ignoreregex =
 datepattern = ^%%Y-%%m-%%d %%H:%%M:%%S
 ```
 
-#### Map log file directories
+#### {% linkable_title Map log file directories %}
 
 First, we need to make sure that fail2ban log can be passed to Home Assistant and that the Home Assistant log can be passed to fail2ban.  When starting the Let's Encrypt docker, you need to add the following argument (adjust paths based on your setup):
 
@@ -110,20 +119,20 @@ Now do the same for the Home Assistant docker, but this time we'll be mapping th
 ```
 
 
-#### Send client IP to Home Assistant
+#### {% linkable_title Send client IP to Home Assistant %}
 
 By default, the IP address that Home Assistant sees will be that of the container (something like `172.17.0.16`).  What this means is that for any failed login attempt, assuming you have correctly configured `fail2ban`, the Docker IP will be logged as banned, but the originating IP is still allowed to make attempts.  We need `fail2ban` to recognize the originating IP to properly ban it.
 
 First, we have to add the following to the nginx configuration file located in `/mnt/user/appdata/letsencrypt/nginx/site-confs/default`.  
 
-```
+```bash
 proxy_set_header X-Real-IP $remote_addr;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 ```
 
 This snippet should be added within your Home Assistant server config, so you have something like the following:
 
-```
+```bash
 server {
     ...
     location / {
@@ -158,7 +167,7 @@ http:
 
 At this point, once the Let's Encrypt and Home Assistant dockers are restarted, Home Assistant should be correctly logging the originating IP of any failed login attempt.  Once that's done and verified, we can move onto the final step.
 
-#### Add the fail2ban sensor
+#### {% linkable_title Add the fail2ban sensor %}
 
 Now that we've correctly set everything up for Docker, we can add our sensors to `configuration.yaml` with the following:
 
@@ -174,7 +183,7 @@ Assuming you've followed all of the steps, you should have one fail2ban sensor,
 
 ### {% linkable_title Other debug tips %}
 
-If, after following these steps, you're unable to get the fail2ban sensor working, here are some other steps you can take that may help:
+If, after following these steps, you're unable to get the `fail2ban` sensor working, here are some other steps you can take that may help:
 
 - Add `logencoding = utf-8` to the `[hass-iptables]` entry
 - Ensure the `failregex` you added to `filter.d/hass.local` matches the output within `home-assistant.log`

source/_components/sensor.hive.markdown

@@ -0,0 +1,24 @@
+---
+layout: page
+title: "Hive Sensor"
+description: "Instructions on how to integrate Hive Sensors with Home Assistant."
+date: 2017-09-24 21:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: hive.png
+ha_category: Sensor
+ha_release: 0.59
+ha_iot_class: "Cloud Polling"
+---
+
+
+The 'hive' sensor component can expose as a sensor the current online status of your Hive Hub.
+
+
+<p class='note'>
+Full configuration details can be found on the main [Hive component](/components/hive/) page.
+</p>
+
+

source/_components/sensor.sabnzbd.markdown

@@ -40,6 +40,7 @@ sensor:
     - 'queue_remaining'
     - 'disk_size'
     - 'disk_free'
+    - 'queue_count'
 ```
 
 Configuration variables:
@@ -56,6 +57,7 @@ Configuration variables:
   - **queue_remaining**: Remaining elements in the queue
   - **disk_size**: Disk size of the storage location
   - **disk_free**: Free disk space at the storage location
+  - **queue_count**: Number of items in the queue
 
 Note that this will create the following sensors:
 
@@ -66,6 +68,7 @@ Note that this will create the following sensors:
  - sensor.sabnzbd_left
  - sensor.sabnzbd_disk
  - sensor.sabnzbd_disk_free
+ - sensor.sabnzdb_queue_count
 ```
 
 As always, you can determine the names of sensors by looking at the dev-state page `< >` in the web interface.

source/_components/sensor.tahoma.markdown

@@ -0,0 +1,21 @@
+---
+layout: page
+title: "Tahoma Sensor"
+description: "Instructions how to integrate Tahoma sensors into Home Assistant."
+date: 2017-07-18 12:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: tahoma.png
+ha_category: Cover
+ha_release: 0.59
+---
+
+To use your tahoma sensors in your installation, add the following to your `configuration.yaml` file:
+
+``yaml
+# Example configuration.yml entry
+sensor:
+  platform: tahoma
+```

source/_components/switch.hive.markdown

@@ -0,0 +1,27 @@
+---
+layout: page
+title: "Hive Switch"
+description: "Instructions on how to integrate Hive Plugs with Home Assistant."
+date: 2017-09-24 21:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: hive.png
+ha_category: Switch
+ha_release: 0.59
+ha_iot_class: "Cloud Polling"
+---
+
+
+The 'hive' switch component integrates your Hive plugs into Home Assistant, enabling control of your devices.
+
+The Hive switch component supports the following Hive products:
+- **Hive Active Plug**
+
+
+<p class='note'>
+Full configuration details can be found on the main [Hive component](/components/hive/) page.
+</p>
+
+

source/_components/tahoma.markdown

@@ -0,0 +1,41 @@
+---
+layout: page
+title: "Tahoma"
+description: "Instructions on how to integrate Somfy Tahoma devices with Home Assistant."
+date: 2017-07-18 12:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: tahoma.png
+ha_category: Hub
+ha_release: 0.59
+---
+
+
+The `Tahoma` component platform is used as an interface to the [tahomalink.com](https://www.tahomalink.com) website. It adds actually covers and the sun sensor from tahoma platform.
+
+To use your Tahoma devices in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+tahoma:
+  username: YOUR_USERNAME
+  password: YOUR_PASSWORD
+  exclude: [BridgeHUEComponent, HueLampHUEComponent, PodComponent]
+```
+
+{% configuration %}
+username:
+  description: Username for tahomalink.com
+  required: true
+  type: string
+password:
+  description: Password for tahomalink.com
+  required: true
+  type: string
+exclude:
+  description: Excludes devices
+  required: false
+  type: list
+{% endconfiguration %}

source/_components/tts.baidu.markdown

@@ -0,0 +1,62 @@
+---
+layout: page
+title: "Baidu Text-to-Speech"
+description: "Instructions how to setup Baidu TTS with Home Assistant."
+date: 2017-11-21 09:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: baiducloud.png
+ha_category: Text-to-speech
+ha_release: 0.59
+---
+
+The `baidu` text-to-speech platform uses [Baidu TTS engine](https://cloud.baidu.com/product/speech/tts) to read a text with natural sounding voices.
+
+To get started, add the following lines to your `configuration.yaml`:
+
+```yaml
+#Example configuration.yaml entry
+tts:
+  - platform: baidu
+    app_id: YOUR_APPID
+    api_key: YOUR_APIKEY
+    secret_key: YOUR_SECRETKEY
+```
+
+{% configuration %}
+app_id:
+  description: The App ID for the use this service, must be already registered on Baidu.
+  required: true
+  type: string
+api_key:
+  description: The API key from Baidu.
+  required: true
+  type: string
+secret_key:
+  description: The secret key from Baidu.
+  required: true
+  type: string
+speed:
+  description: Audio speed from 0 to 9.
+  required: false
+  type: int
+  default: 5
+pitch:
+  description: Audio pitch from 0 to 9.
+  required: false
+  type: int
+  default: 5
+volume:
+  description: Audio volume from 0 to 15.
+  required: false
+  type: int
+  default: 5
+person:
+  description: Voice type. You choose one from 0, 1, 3 or 4.
+  required: false
+  type: int
+  default: 0
+{% endconfiguration %}
+

source/_components/weather.ecobee.markdown

@@ -0,0 +1,16 @@
+---
+layout: page
+title: "Ecobee Weather"
+description: "Instructions how to setup the Ecobee weather within Home Assistant."
+date: 2017-11-29 21:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: ecobee.png
+ha_category: Weather
+ha_release: 0.59
+ha_iot_class: "Local Push"
+---
+
+To get your Ecobee weather component working with Home Assistant, follow the instructions for the general [Ecobee component](/components/ecobee/).

source/_data/glossary.yml

@@ -27,17 +27,17 @@
 - topic: Template
   description: "A [template](/docs/automation/templating/) is an automation definition that can include variables for the service or data from the trigger values. This allows automations to generate dynamic actions."
 - topic: Script
-  description: "[Scripts](/docs/scripts/) are components that allow users to specify a sequence of actions to be executed by Home Assistant when turned on"
+  description: "[Scripts](/docs/scripts/) are components that allow users to specify a sequence of actions to be executed by Home Assistant when turned on."
 - topic: Scene
   description: "[Scenes](/components/scene/) capture the states you want certain entities to be. For example a scene can specify that light A should be turned on and light B should be bright red." 
 - topic: HADashboard
   description: "[HADashboard](/docs/ecosystem/hadashboard/) is a modular, skinnable dashboard for Home Assistant that is intended to be wall mounted, and is optimized for distance viewing."
 - topic: hass
-  description: "HASS or [hass](/docs/tools/hass/) is often used as an abbreviation for Home Assistant. It is aslo the comand line tool for accessing"
+  description: "HASS or [hass](/docs/tools/hass/) is often used as an abbreviation for Home Assistant. It is also the command line tool."
 - topic: Hass.io
-  description: "[Hass.io](/hassio/) is an operating system that will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows creating/restoring snapshots of your configuration, and can easily be extended"
+  description: "[Hass.io](/hassio/) is an operating system that will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows creating/restoring snapshots of your configuration, and can easily be extended."
 - topic: Cookbook
-  description: "The [Cookbook](/cookbook/) contains a set of configuration examples of Home Assistant from the community"
+  description: "The [Cookbook](/cookbook/) contains a set of configuration examples of Home Assistant from the community."
 - topic: Packages
   description: "[Packages](/docs/configuration/packages/) allow you to bundle different component configuations together."
 - topic: Customize

source/_docs/configuration/templating.markdown

@@ -78,6 +78,7 @@ Home Assistant adds extensions to allow templates to access all of the current s
 - `relative_time(timestamp)` will format the date time as relative time vs now (ie 7 seconds)
 - `float` will format the output as float.
 - `strptime(string, format)` will parse a string to a datetime based on a [format][strp-format].
+- `log(value, base)` will take the logarithm of the input. When the base is omitted, it defaults to `e` - the natural logarithm. Can also be used as a filter.
 - Filter `round(x)` will convert the input to a number and round it to `x` decimals.
 - Filter `timestamp_local`  will convert an UNIX timestamp to local time/data.
 - Filter `timestamp_utc` will convert an UNIX timestamp to UTC time/data.
@@ -254,6 +255,8 @@ The following overview contains a couple of options to get the needed values:
 # Math
 {% raw %}{{ value_json | float * 1024 }}{% endraw %}
 {% raw %}{{ float(value_json) * (2**10) }}{% endraw %}
+{% raw %}{{ value_json | log }}{% endraw %}
+{% raw %}{{ log(1000, 10) }}{% endraw %}
 
 # Timestamps
 {% raw %}{{ value_json.tst | timestamp_local }}{% endraw %}

source/_docs/z-wave/control-panel.markdown

@@ -112,6 +112,25 @@ You can set the *wakeup* interval (in seconds) of the device, this is shown for
 
 Underneath that you can select any supported configuration parameter to see the current setting. You can then change this and select **Set Config Parameter** to updated it. Battery powered devices will be updated the next time they wake.
 
+## {% linkable_title Node user codes %}
+
+If your node has user codes, you can set and delete them. The format is raw hex Ascii code. Bellow the input you will see your actual code. For normal nodes this is as follows:
+```yaml
+\x30 = 0
+\x31 = 1
+\x32 = 2
+\x33 = 3
+\x34 = 4
+\x35 = 5
+\x36 = 6
+\x37 = 7
+\x38 = 8
+\x39 = 9
+```
+Some non compliant device like tag readers, have implemented to use raw hex code.
+Please refer to a hex ascii table to set your code. Example: http://www.asciitable.com/
+
+
 ## {% linkable_title OZW Log %}
 
 If you want to only retrieve some lines at the end of the log, you can specify that with the selection field. Max is the last 1000 lines and minimum is 0 which equals the whole log. If this is not specified, you will retrieve the whole log.

source/_posts/2017-12-03-release-59.markdown

@@ -0,0 +1,391 @@
+---
+layout: post
+title: "0.59: Order pizza, Entity Picker, Color Wheel"
+description: "If you don't want to create items on our shopping list with HTTP requests, just order pizza!"
+date: 2017-12-03 02:00:00
+date_formatted: "December 3, 2017"
+author: Fabian Affolter
+author_twitter: fabaff
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2017-12-0.59/components.png
+---
+
+<a href='/components/#version/0.59'><img src='/images/blog/2017-12-0.59/components.png' style='border: 0;box-shadow: none;'></a>
+
+We are proud to announce the availability of Home Assistant 0.59. To keep you in the loop: This is the second last release in 2017. We have stuck to our bi-weekly release cycle for another year but we decided that we will take a little break between Christmas and New Year.
+
+## {% linkable_title Dominos Pizza platform %}
+With the Dominos Pizza integration made by [@wardcraigj] your home is now taking care that you don't  starve. In combination with a [Skybell](/components/skybell/) or a [DoorBird](/components/skybell/) you will know exactly when the pizza is in front of your door.
+
+## {% linkable_title Color picker %}
+@NovapaX created a new color picker. While dragging the color badge with your finger, a badge will appear above your finger so you can see the current color.
+
+<p class='img'>
+    <img src='/images/blog/2017-12-0.59/color-wheel.png' alt='Screenshot of the color wheel.'>
+    Screenshot of the color wheel.
+</p>
+
+## {% linkable_title Shopping list tweaks %}
+New items for the [`shopping_list`][shopping_list docs] can now be created with HTTP requests.  [@balloob] extented the component with this feature. 
+
+## {% linkable_title Entity picker %}
+[@balloob] improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it's much easier to identify the right one! The automation editor will only suggest relevant entities.
+
+<p class='img'>
+    <img src='/images/blog/2017-12-0.59/picker.png' alt='Screenshot of the Entity Picker.'>
+    Screenshot of the of the Enitity Picker.
+</p>
+
+## {% linkable_title Hass.io Add-ons %}
+If you follow our [twitter feed](https://twitter.com/home_assistant) then you may already know that [@frenck](https://github.com/frenck) spent some time to bring new stuff to the [Community Hass.io Add-ons repository](https://github.com/hassio-addons/repository).
+
+- [Cloud9 IDE](https://github.com/hassio-addons/addon-ide)
+- [Terminal support](https://github.com/hassio-addons/addon-terminal)
+- New release of the [Tor add-on](https://github.com/hassio-addons/addon-tor)
+
+## {% linkable_title New Platforms %}
+
+- Support for Unifi direct access device tracker (No unifi controller software) ([@w1ll1am23] - [#10097]) ([device_tracker.unifi_direct docs]) (new-platform)
+- Tahoma platform for Somfy Covers and Sensors ([@philklei] - [#10652]) ([tahoma docs]) ([cover.tahoma docs]) ([sensor.tahoma docs]) (new-platform)
+- New Hive Component / Platforms ([@Rendili] - [#9804]) ([hive docs]) ([climate.hive docs]) ([light.hive docs]) ([sensor.hive docs]) ([switch.hive docs]) (new-platform)
+- Add Dominos Pizza platform ([@wardcraigj] - [#10379]) ([dominos docs]) (new-platform)
+- Add tts.baidu platform ([@zhujisheng] - [#10724]) ([tts.baidu docs]) (new-platform)
+- Create ecobee weather platform ([@PhracturedBlue] - [#10869]) ([ecobee docs]) ([weather.ecobee 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 %}
+
+- Added cycles config option to LaMetric notifications ([@frittes] - [#10656]) ([notify.lametric docs]) (breaking change)
+- Fix name collision when using multiple Hue bridges ([@zBart] - [#10486]) ([light.hue docs]) (breaking change)
+- Single LEDs in Blinkt support ([@matemaciek] - [#10581]) ([light.blinkt docs]) (breaking change)
+- Tellduslive update with support for auto config and Local api ([@fredrike] - [#10435]) ([tellduslive docs]) (breaking change)
+- Add useragent-based detection of JS version ([@andrey-git] - [#10776]) (breaking change)
+
+## {% linkable_title All changes %}
+
+- Added unit_of_measurement to Currencylayer ([@arsaboo] - [#10598]) ([sensor.currencylayer docs])
+- Change generic thermostat - any toggle device as heater switch ([@milanvo] - [#10597]) ([climate.generic_thermostat docs])
+- Add hddtemp sensor device even if unreachable. ([@cgtobi] - [#10623]) ([sensor.hddtemp docs])
+- Restore target temperature for generic thermostat ([@tinloaf] - [#10635]) ([climate.generic_thermostat docs])
+- Update lnetatmo ([@gieljnssns] - [#10631]) ([netatmo docs])
+- Support for Unifi direct access device tracker (No unifi controller software) ([@w1ll1am23] - [#10097]) ([device_tracker.unifi_direct docs]) (new-platform)
+- Add Facebook Notification tests ([@broox] - [#10642])
+- Change some warnings to info ([@cgarwood] - [#10386]) ([emulated_hue docs])
+- Added cycles config option to LaMetric notifications ([@frittes] - [#10656]) ([notify.lametric docs]) (breaking change)
+- Netatmo httperror403 fix ([@gieljnssns] - [#10659]) ([netatmo docs])
+- Bump dev to 0.59.0.dev0 ([@fabaff] - [#10675])
+- Include unit_of_measurement as InfluxDb field ([@PeteBa] - [#9790]) ([influxdb docs])
+- Tahoma platform for Somfy Covers and Sensors ([@philklei] - [#10652]) ([tahoma docs]) ([cover.tahoma docs]) ([sensor.tahoma docs]) (new-platform)
+- Populate measurement state field for HA states like home/not_home ([@PeteBa] - [#9833]) ([influxdb docs])
+- Reorganize lint travis builds ([@balloob] - [#10670])
+- Refactored to new global json saving and loading ([@mnigbur] - [#10677])
+- Convert configurator to use markdown ([@balloob] - [#10668]) ([configurator docs]) ([light.hue docs])
+- index.html improvements ([@balloob] - [#10696])
+- Add Arm Custom Bypass to alarm_control_panel ([@uchagani] - [#10697]) ([alarm_control_panel docs])
+- Fix conversation ([@balloob] - [#10686]) ([conversation docs])
+- Shopping list: add item HTTP API ([@balloob] - [#10674]) ([shopping_list docs])
+- Add presence device_class ([@arsaboo] - [#10705]) ([binary_sensor docs])
+- python-miio version bumped for improved device support. ([@syssi] - [#10720]) ([fan.xiaomi_miio docs]) ([light.xiaomi_miio docs]) ([switch.xiaomi_miio docs]) ([vacuum.xiaomi_miio docs])
+- Adding Queue count sensor ([@bigwoof] - [#10723]) ([sensor.sabnzbd docs])
+- Bump pychromecast to 1.0.2 ([@OttoWinter] - [#10728]) ([media_player.cast docs])
+- Fix unit conversion for Sensibo A/C units ([@bryanyork] - [#10692]) ([climate.sensibo docs])
+- Optimised images. Saved 80 KB out of 656 KB. 12.3% overall (up to 32.1% per file) ([@grischard] - [#10735])
+- Add transmission rate ([@svenstaro] - [#10740]) ([sensor.fritzbox_netmonitor docs])
+- Update pytradfri to 4.1.0 ([@lwis] - [#10521]) ([tradfri docs]) ([light.tradfri docs])
+- Use new DoorBirdPy (v0.1.0) ([@Klikini] - [#10734]) ([doorbird docs])
+- Add fan and reduce I/O calls in radiotherm ([@TD22057] - [#10437]) ([climate.radiotherm docs])
+- New Hive Component / Platforms ([@Rendili] - [#9804]) ([hive docs]) ([climate.hive docs]) ([light.hive docs]) ([sensor.hive docs]) ([switch.hive docs]) (new-platform)
+- Temporarily fix yahoo weather API issue and add unit test. ([@cgtobi] - [#10737]) ([sensor.yweather docs])
+- Google assistant climate mode fix ([@braddparker] - [#10726]) ([google_assistant.smart_home docs])
+- Protect sensitive information for Amcrest cameras ([@tchellomello] - [#10569]) ([amcrest docs]) ([camera.amcrest docs]) ([sensor.amcrest docs])
+- InfluxDB send retry after IOError ([@janLo] - [#10263]) ([influxdb docs])
+- Add Dominos Pizza platform ([@wardcraigj] - [#10379]) ([dominos docs]) (new-platform)
+- Fix name collision when using multiple Hue bridges ([@zBart] - [#10486]) ([light.hue docs]) (breaking change)
+- Make shell_command async ([@n8henrie] - [#10741]) ([shell_command docs])
+- Update CODEOWNERS with hive Component / Platforms ([@Rendili] - [#10775])
+- Bump total-connect-client version ([@uchagani] - [#10769]) ([alarm_control_panel.totalconnect docs])
+- Fix scene description formatting. ([@balloob] - [#10785])
+- Fixes #10773: Demo Alarm Broken ([@uchagani] - [#10777]) ([alarm_control_panel.demo docs])
+- Load Ring camera only with Ring Protect plan activated ([@tchellomello] - [#10739]) ([ring docs]) ([camera.ring docs])
+- system_log improvements ([@andrey-git] - [#10709]) ([system_log docs])
+- Fix WUnderground error handling, rework entity methods ([@milanvo] - [#10295]) ([sensor.wunderground docs])
+- Add away_mode_name to arlo alarm control panel ([@bcl1713] - [#10796]) ([alarm_control_panel.arlo docs])
+- Add missing docstring ([@fabaff] - [#10812]) ([notify.pushbullet docs])
+- Cloud cognito switch ([@balloob] - [#10823]) ([cloud docs]) ([cloud.auth_api docs]) ([cloud.iot docs])
+- Added sensor types from telldus server src ([@rasmusbe] - [#10787]) ([sensor.tellduslive docs])
+- Add tts.baidu platform ([@zhujisheng] - [#10724]) ([tts.baidu docs]) (new-platform)
+- make RGB values consistent as int. fixes #10766 ([@perosb] - [#10782])
+- Single LEDs in Blinkt support ([@matemaciek] - [#10581]) ([light.blinkt docs]) (breaking change)
+- Add debug ([@dgomes] - [#10828]) ([sensor.serial docs])
+- Fix "recently pair device" ([@stephenyeargin] - [#10832])
+- Fixed Yeelight's color temperature conversion to RGB ([@chocomega] - [#10831]) ([light.yeelight docs])
+- Fix for Sensibo with missing temperature ([@andrey-git] - [#10801]) ([climate.sensibo docs])
+- upgrade somecomfort to 0.5.0 ([@dferrante] - [#10834]) ([climate.honeywell docs])
+- Add support for logarithm in templates ([@odinuge] - [#10824])
+- Changing handling for google_assistant groups to treat them as lights. ([@snowzach] - [#10111])
+- Tellduslive update with support for auto config and Local api ([@fredrike] - [#10435]) ([tellduslive docs]) (breaking change)
+- KNX: Added config option for broadcasting current time to KNX bus. ([@Julius2342] - [#10654]) ([knx docs])
+- Ecobee set humidity level ([@cbulock] - [#10780]) ([ecobee docs]) ([climate.ecobee docs])
+- Add device class for low battery ([@schmittx] - [#10829]) ([binary_sensor docs])
+- Tellduslive: Use magic constants for battery level. Also, the previous formula for battery level was wrong. ([@molobrakos] - [#10788]) ([tellduslive docs])
+- Add useragent-based detection of JS version ([@andrey-git] - [#10776]) (breaking change)
+- add support for multiple execution per execute request ([@perosb] - [#10844]) ([google_assistant.http docs])
+- Upgrade HomeMatic, add devices ([@danielperna84] - [#10845]) ([homematic docs]) ([binary_sensor.homematic docs]) ([sensor.homematic docs])
+- Climate component: add supported_features ([@tinloaf] - [#10658]) ([climate docs]) ([climate.generic_thermostat docs]) ([climate.mqtt docs])
+- Upgrade mutagen to 1.39 ([@fabaff] - [#10851]) ([tts docs])
+- Updated codeowner for Tile device tracker ([@bachya] - [#10861])
+- Revert "KNX: Added config option for broadcasting current time to KNX bus. (#10654)" ([@Julius2342] - [#10874]) ([knx docs])
+- Upgrade distro to 1.1.0 ([@fabaff] - [#10850]) ([updater docs])
+- Bugfix trigger state with multible entities ([@pvizeli] - [#10857]) ([automation.state docs])
+- tellstick fix DEPENDENCIES and update tellcore-net ([@pvizeli] - [#10859]) ([tellstick docs]) ([sensor.tellstick docs])
+- Upgrade aiohttp to 2.3.5 ([@fabaff] - [#10889])
+- Upgrade fastdotcom to 0.0.3 ([@fabaff] - [#10886]) ([sensor.fastdotcom docs])
+- Upgrade schiene to 0.19 ([@fabaff] - [#10887]) ([sensor.deutsche_bahn docs])
+- Xiaomi Vacuum: remove deprecated calls ([@rytilahti] - [#10839]) ([vacuum.xiaomi_miio docs])
+- Create ecobee weather platform ([@PhracturedBlue] - [#10869]) ([ecobee docs]) ([weather.ecobee docs]) (new-platform)
+- Microsoft Text-to-speech: Fixing missing en-gb support bug ([@jeroenterheerdt] - [#10429]) ([tts.microsoft docs])
+- Upgrade youtube_dl to 2017.11.26 ([@fabaff] - [#10890]) ([media_extractor docs])
+- Upgrade yarl to 0.15.0 ([@fabaff] - [#10888])
+- Fix tests ([@pvizeli] - [#10891])
+- Refactored WHOIS sensor to resolve assumed key errors ([@GenericStudent] - [#10662]) ([sensor.whois docs])
+- Serve latest extra_html in dev mode ([@andrey-git] - [#10863])
+- Reload groups after saving a change via config API ([@andrey-git] - [#10877]) ([config.group docs])
+- Fix issues from review of ecobee weather component ([@PhracturedBlue] - [#10903]) ([weather.ecobee docs])
+- Bugfix #10902 ([@turbokongen] - [#10904]) ([zwave docs])
+
+[#10097]: https://github.com/home-assistant/home-assistant/pull/10097
+[#10111]: https://github.com/home-assistant/home-assistant/pull/10111
+[#10263]: https://github.com/home-assistant/home-assistant/pull/10263
+[#10295]: https://github.com/home-assistant/home-assistant/pull/10295
+[#10379]: https://github.com/home-assistant/home-assistant/pull/10379
+[#10386]: https://github.com/home-assistant/home-assistant/pull/10386
+[#10429]: https://github.com/home-assistant/home-assistant/pull/10429
+[#10435]: https://github.com/home-assistant/home-assistant/pull/10435
+[#10437]: https://github.com/home-assistant/home-assistant/pull/10437
+[#10486]: https://github.com/home-assistant/home-assistant/pull/10486
+[#10521]: https://github.com/home-assistant/home-assistant/pull/10521
+[#10569]: https://github.com/home-assistant/home-assistant/pull/10569
+[#10581]: https://github.com/home-assistant/home-assistant/pull/10581
+[#10597]: https://github.com/home-assistant/home-assistant/pull/10597
+[#10598]: https://github.com/home-assistant/home-assistant/pull/10598
+[#10623]: https://github.com/home-assistant/home-assistant/pull/10623
+[#10631]: https://github.com/home-assistant/home-assistant/pull/10631
+[#10635]: https://github.com/home-assistant/home-assistant/pull/10635
+[#10642]: https://github.com/home-assistant/home-assistant/pull/10642
+[#10652]: https://github.com/home-assistant/home-assistant/pull/10652
+[#10654]: https://github.com/home-assistant/home-assistant/pull/10654
+[#10656]: https://github.com/home-assistant/home-assistant/pull/10656
+[#10658]: https://github.com/home-assistant/home-assistant/pull/10658
+[#10659]: https://github.com/home-assistant/home-assistant/pull/10659
+[#10662]: https://github.com/home-assistant/home-assistant/pull/10662
+[#10668]: https://github.com/home-assistant/home-assistant/pull/10668
+[#10670]: https://github.com/home-assistant/home-assistant/pull/10670
+[#10674]: https://github.com/home-assistant/home-assistant/pull/10674
+[#10675]: https://github.com/home-assistant/home-assistant/pull/10675
+[#10677]: https://github.com/home-assistant/home-assistant/pull/10677
+[#10686]: https://github.com/home-assistant/home-assistant/pull/10686
+[#10692]: https://github.com/home-assistant/home-assistant/pull/10692
+[#10696]: https://github.com/home-assistant/home-assistant/pull/10696
+[#10697]: https://github.com/home-assistant/home-assistant/pull/10697
+[#10705]: https://github.com/home-assistant/home-assistant/pull/10705
+[#10709]: https://github.com/home-assistant/home-assistant/pull/10709
+[#10720]: https://github.com/home-assistant/home-assistant/pull/10720
+[#10723]: https://github.com/home-assistant/home-assistant/pull/10723
+[#10724]: https://github.com/home-assistant/home-assistant/pull/10724
+[#10726]: https://github.com/home-assistant/home-assistant/pull/10726
+[#10728]: https://github.com/home-assistant/home-assistant/pull/10728
+[#10734]: https://github.com/home-assistant/home-assistant/pull/10734
+[#10735]: https://github.com/home-assistant/home-assistant/pull/10735
+[#10737]: https://github.com/home-assistant/home-assistant/pull/10737
+[#10739]: https://github.com/home-assistant/home-assistant/pull/10739
+[#10740]: https://github.com/home-assistant/home-assistant/pull/10740
+[#10741]: https://github.com/home-assistant/home-assistant/pull/10741
+[#10769]: https://github.com/home-assistant/home-assistant/pull/10769
+[#10775]: https://github.com/home-assistant/home-assistant/pull/10775
+[#10776]: https://github.com/home-assistant/home-assistant/pull/10776
+[#10777]: https://github.com/home-assistant/home-assistant/pull/10777
+[#10780]: https://github.com/home-assistant/home-assistant/pull/10780
+[#10782]: https://github.com/home-assistant/home-assistant/pull/10782
+[#10785]: https://github.com/home-assistant/home-assistant/pull/10785
+[#10787]: https://github.com/home-assistant/home-assistant/pull/10787
+[#10788]: https://github.com/home-assistant/home-assistant/pull/10788
+[#10796]: https://github.com/home-assistant/home-assistant/pull/10796
+[#10801]: https://github.com/home-assistant/home-assistant/pull/10801
+[#10812]: https://github.com/home-assistant/home-assistant/pull/10812
+[#10823]: https://github.com/home-assistant/home-assistant/pull/10823
+[#10824]: https://github.com/home-assistant/home-assistant/pull/10824
+[#10828]: https://github.com/home-assistant/home-assistant/pull/10828
+[#10829]: https://github.com/home-assistant/home-assistant/pull/10829
+[#10831]: https://github.com/home-assistant/home-assistant/pull/10831
+[#10832]: https://github.com/home-assistant/home-assistant/pull/10832
+[#10834]: https://github.com/home-assistant/home-assistant/pull/10834
+[#10839]: https://github.com/home-assistant/home-assistant/pull/10839
+[#10844]: https://github.com/home-assistant/home-assistant/pull/10844
+[#10845]: https://github.com/home-assistant/home-assistant/pull/10845
+[#10850]: https://github.com/home-assistant/home-assistant/pull/10850
+[#10851]: https://github.com/home-assistant/home-assistant/pull/10851
+[#10857]: https://github.com/home-assistant/home-assistant/pull/10857
+[#10859]: https://github.com/home-assistant/home-assistant/pull/10859
+[#10861]: https://github.com/home-assistant/home-assistant/pull/10861
+[#10863]: https://github.com/home-assistant/home-assistant/pull/10863
+[#10869]: https://github.com/home-assistant/home-assistant/pull/10869
+[#10874]: https://github.com/home-assistant/home-assistant/pull/10874
+[#10877]: https://github.com/home-assistant/home-assistant/pull/10877
+[#10886]: https://github.com/home-assistant/home-assistant/pull/10886
+[#10887]: https://github.com/home-assistant/home-assistant/pull/10887
+[#10888]: https://github.com/home-assistant/home-assistant/pull/10888
+[#10889]: https://github.com/home-assistant/home-assistant/pull/10889
+[#10890]: https://github.com/home-assistant/home-assistant/pull/10890
+[#10891]: https://github.com/home-assistant/home-assistant/pull/10891
+[#10903]: https://github.com/home-assistant/home-assistant/pull/10903
+[#10904]: https://github.com/home-assistant/home-assistant/pull/10904
+[#9790]: https://github.com/home-assistant/home-assistant/pull/9790
+[#9804]: https://github.com/home-assistant/home-assistant/pull/9804
+[#9833]: https://github.com/home-assistant/home-assistant/pull/9833
+[@GenericStudent]: https://github.com/GenericStudent
+[@Julius2342]: https://github.com/Julius2342
+[@Klikini]: https://github.com/Klikini
+[@OttoWinter]: https://github.com/OttoWinter
+[@PeteBa]: https://github.com/PeteBa
+[@PhracturedBlue]: https://github.com/PhracturedBlue
+[@Rendili]: https://github.com/Rendili
+[@TD22057]: https://github.com/TD22057
+[@andrey-git]: https://github.com/andrey-git
+[@arsaboo]: https://github.com/arsaboo
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@bcl1713]: https://github.com/bcl1713
+[@bigwoof]: https://github.com/bigwoof
+[@braddparker]: https://github.com/braddparker
+[@broox]: https://github.com/broox
+[@bryanyork]: https://github.com/bryanyork
+[@cbulock]: https://github.com/cbulock
+[@cgarwood]: https://github.com/cgarwood
+[@cgtobi]: https://github.com/cgtobi
+[@chocomega]: https://github.com/chocomega
+[@danielperna84]: https://github.com/danielperna84
+[@dferrante]: https://github.com/dferrante
+[@dgomes]: https://github.com/dgomes
+[@fabaff]: https://github.com/fabaff
+[@fredrike]: https://github.com/fredrike
+[@frittes]: https://github.com/frittes
+[@gieljnssns]: https://github.com/gieljnssns
+[@grischard]: https://github.com/grischard
+[@janLo]: https://github.com/janLo
+[@jeroenterheerdt]: https://github.com/jeroenterheerdt
+[@lwis]: https://github.com/lwis
+[@matemaciek]: https://github.com/matemaciek
+[@milanvo]: https://github.com/milanvo
+[@mnigbur]: https://github.com/mnigbur
+[@molobrakos]: https://github.com/molobrakos
+[@n8henrie]: https://github.com/n8henrie
+[@odinuge]: https://github.com/odinuge
+[@perosb]: https://github.com/perosb
+[@philklei]: https://github.com/philklei
+[@pvizeli]: https://github.com/pvizeli
+[@rasmusbe]: https://github.com/rasmusbe
+[@rytilahti]: https://github.com/rytilahti
+[@schmittx]: https://github.com/schmittx
+[@snowzach]: https://github.com/snowzach
+[@stephenyeargin]: https://github.com/stephenyeargin
+[@svenstaro]: https://github.com/svenstaro
+[@syssi]: https://github.com/syssi
+[@tchellomello]: https://github.com/tchellomello
+[@tinloaf]: https://github.com/tinloaf
+[@turbokongen]: https://github.com/turbokongen
+[@uchagani]: https://github.com/uchagani
+[@w1ll1am23]: https://github.com/w1ll1am23
+[@wardcraigj]: https://github.com/wardcraigj
+[@zBart]: https://github.com/zBart
+[@zhujisheng]: https://github.com/zhujisheng
+[alarm_control_panel docs]: https://home-assistant.io/components/alarm_control_panel/
+[alarm_control_panel.arlo docs]: https://home-assistant.io/components/alarm_control_panel.arlo/
+[alarm_control_panel.demo docs]: https://home-assistant.io/components/alarm_control_panel.demo/
+[alarm_control_panel.totalconnect docs]: https://home-assistant.io/components/alarm_control_panel.totalconnect/
+[amcrest docs]: https://home-assistant.io/components/amcrest/
+[automation.state docs]: https://home-assistant.io/docs/automation/trigger/#state-trigger
+[binary_sensor docs]: https://home-assistant.io/components/binary_sensor/
+[binary_sensor.homematic docs]: https://home-assistant.io/components/binary_sensor.homematic/
+[camera.amcrest docs]: https://home-assistant.io/components/camera.amcrest/
+[camera.ring docs]: https://home-assistant.io/components/camera.ring/
+[climate docs]: https://home-assistant.io/components/climate/
+[climate.ecobee docs]: https://home-assistant.io/components/climate.ecobee/
+[climate.generic_thermostat docs]: https://home-assistant.io/components/climate.generic_thermostat/
+[climate.hive docs]: https://home-assistant.io/components/climate.hive/
+[climate.honeywell docs]: https://home-assistant.io/components/climate.honeywell/
+[climate.mqtt docs]: https://home-assistant.io/components/climate.mqtt/
+[climate.radiotherm docs]: https://home-assistant.io/components/climate.radiotherm/
+[climate.sensibo docs]: https://home-assistant.io/components/climate.sensibo/
+[cloud docs]: https://home-assistant.io/components/cloud/
+[cloud.auth_api docs]: https://home-assistant.io/components/cloud.auth_api/
+[cloud.iot docs]: https://home-assistant.io/components/cloud.iot/
+[config.group docs]: https://home-assistant.io/components/config.group/
+[configurator docs]: https://home-assistant.io/components/configurator/
+[conversation docs]: https://home-assistant.io/components/conversation/
+[cover.tahoma docs]: https://home-assistant.io/components/cover.tahoma/
+[device_tracker.unifi_direct docs]: https://home-assistant.io/components/device_tracker.unifi_direct/
+[dominos docs]: https://home-assistant.io/components/dominos/
+[doorbird docs]: https://home-assistant.io/components/doorbird/
+[ecobee docs]: https://home-assistant.io/components/ecobee/
+[emulated_hue docs]: https://home-assistant.io/components/emulated_hue/
+[fan.xiaomi_miio docs]: https://home-assistant.io/components/fan.xiaomi_miio/
+[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/
+[hive docs]: https://home-assistant.io/components/hive/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[influxdb docs]: https://home-assistant.io/components/influxdb/
+[knx docs]: https://home-assistant.io/components/knx/
+[light.blinkt docs]: https://home-assistant.io/components/light.blinkt/
+[light.hive docs]: https://home-assistant.io/components/light.hive/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
+[light.xiaomi_miio docs]: https://home-assistant.io/components/light.xiaomi_miio/
+[light.yeelight docs]: https://home-assistant.io/components/light.yeelight/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player.cast docs]: https://home-assistant.io/components/media_player.cast/
+[netatmo docs]: https://home-assistant.io/components/netatmo/
+[notify.lametric docs]: https://home-assistant.io/components/notify.lametric/
+[notify.pushbullet docs]: https://home-assistant.io/components/notify.pushbullet/
+[ring docs]: https://home-assistant.io/components/ring/
+[sensor.amcrest docs]: https://home-assistant.io/components/sensor.amcrest/
+[sensor.currencylayer docs]: https://home-assistant.io/components/sensor.currencylayer/
+[sensor.deutsche_bahn docs]: https://home-assistant.io/components/sensor.deutsche_bahn/
+[sensor.fastdotcom docs]: https://home-assistant.io/components/sensor.fastdotcom/
+[sensor.fritzbox_netmonitor docs]: https://home-assistant.io/components/sensor.fritzbox_netmonitor/
+[sensor.hddtemp docs]: https://home-assistant.io/components/sensor.hddtemp/
+[sensor.hive docs]: https://home-assistant.io/components/sensor.hive/
+[sensor.homematic docs]: https://home-assistant.io/components/sensor.homematic/
+[sensor.sabnzbd docs]: https://home-assistant.io/components/sensor.sabnzbd/
+[sensor.serial docs]: https://home-assistant.io/components/sensor.serial/
+[sensor.tahoma docs]: https://home-assistant.io/components/sensor.tahoma/
+[sensor.tellduslive docs]: https://home-assistant.io/components/sensor.tellduslive/
+[sensor.tellstick docs]: https://home-assistant.io/components/sensor.tellstick/
+[sensor.whois docs]: https://home-assistant.io/components/sensor.whois/
+[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/
+[sensor.yweather docs]: https://home-assistant.io/components/sensor.yweather/
+[shell_command docs]: https://home-assistant.io/components/shell_command/
+[shopping_list docs]: https://home-assistant.io/components/shopping_list/
+[switch.hive docs]: https://home-assistant.io/components/switch.hive/
+[switch.xiaomi_miio docs]: https://home-assistant.io/components/switch.xiaomi_miio/
+[system_log docs]: https://home-assistant.io/components/system_log/
+[tahoma docs]: https://home-assistant.io/components/tahoma/
+[tellduslive docs]: https://home-assistant.io/components/tellduslive/
+[tellstick docs]: https://home-assistant.io/components/tellstick/
+[tradfri docs]: https://home-assistant.io/components/tradfri/
+[tts docs]: https://home-assistant.io/components/tts/
+[tts.baidu docs]: https://home-assistant.io/components/tts.baidu/
+[tts.microsoft docs]: https://home-assistant.io/components/tts.microsoft/
+[updater docs]: https://home-assistant.io/components/updater/
+[vacuum.xiaomi_miio docs]: https://home-assistant.io/components/vacuum.xiaomi_miio/
+[weather.ecobee docs]: https://home-assistant.io/components/weather.ecobee/
+[zwave docs]: https://home-assistant.io/components/zwave/