Merge branch 'current' into next

_config.yml

@@ -139,14 +139,14 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 70
+current_minor_version: 71
-current_patch_version: 1
+current_patch_version: 0
-date_released: 2018-05-31
+date_released: 2018-06-08
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
 # Major release:
-patch_version_notes: "#release-0701---may-31"
+patch_version_notes: "#"
 # Minor release (Example #release-0431---april-25):
 
 # Date we moved to Discourse for comments

source/_components/camera.uvc.markdown

@@ -14,9 +14,20 @@ ha_iot_class: "Local Polling"
 ---
 
 
-The `uvc` component allows you to integrate [UniFi Video Camera (UVC)](https://www.ubnt.com/unifi-video/unifi-video-camera/) into Home Assistant.
+The `uvc` camera platform allows you to integrate [UniFi Video Camera (UVC)](https://www.ubnt.com/products/#unifivideo) into Home Assistant.
 
-To enable a UVC camera in your installation, add the following to your `configuration.yaml` file:
+The platform connects to the Unifi NVR software and automatically discovers/adds any camera connected to the NVR.
+
+### {% linkable_title Setup %}
+
+It is recommended that you create a new user for this platform in the NVR software and only give the user the permissions it need to operate.
+
+- The API key is found in the specific user's `API Access` tab in the NVR software.
+- The camera password is found in `Settings` -> `Camera Settings` -> `Camera Password` in the NVR software.
+
+### {% linkable_title Configuration %}
+
+To enable, add the following to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
@@ -26,9 +37,24 @@ camera:
     key: API_KEY
 ```
 
-Configuration variables:
+{% configuration %}
+nvr:
+  description: The IP or hostname of the NVR (Network Video Recorder) server.
+  required: true
+  type: string
+key:
+  description: The API key available from the NVR web interface.
+  required: true
+  type: string
+port:
+  description: The port number to use for accessing the NVR.
+  required: false
+  type: int
+  default: 7080
+name:
+  description: The camera password.
+  required: false
+  type: string
+  default: ubnt
+{% endconfiguration %}
 
-- **nvr** (*Required*): The IP or hostname of the NVR (Network Video Recorder) server.
-- **key** (*Required*): The API key available from the NVR web interface.
-- **port** (*Optional*): The port number to use for accessing the NVR.
-- **password** (*Optional*): The camera password. Defaults to `ubnt` if not given.

source/_components/device_tracker.automatic.markdown

@@ -56,5 +56,8 @@ automation:
     action:
       - service: light.turn_off
 ```
+<p class='note'>
+  You can obtain the correct ID for your vehicle from your known_devices.yaml file. Be sure to lower-case any letters contained in your vehicle's ID when using it in an automation trigger.
+</p>
 
 See the [device tracker component page](/components/device_tracker/) for instructions how to configure the cars to be tracked.

source/_components/homekit.markdown

@@ -175,6 +175,8 @@ automation:
     trigger:
       - platform: event
         event_type: zwave.network_ready
+      - platform: event
+        event_type: zwave.network_complete
     action:
       - service: homekit.start
 ```

source/_components/http.markdown

@@ -67,14 +67,20 @@ The [Set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-us
 
 Or use a self signed certificate following the instructions here [Self-signed certificate for SSL/TLS](/docs/ecosystem/certificates/tls_self_signed_certificate/).
 
+## {% linkable_title APIs %}
+
 On top of the `http` component is a [REST API](/developers/rest_api/), [Python API](/developers/python_api/) and [WebSocket API](/developers/websocket_api/) available. There is also support for [Server-sent events](/developers/server_sent_events/).
 
 The `http` platforms are not real platforms within the meaning of the terminology used around Home Assistant. Home Assistant's [REST API](/developers/rest_api/) sends and receives messages over HTTP.
 
+## {% linkable_title HTTP sensors %}
+
 To use those kind of [sensors](/components/sensor.http/) or [binary sensors](components/binary_sensor.http/) in your installation no configuration in Home Assistant is needed. All configuration is done on the devices themselves. This means that you must be able to edit the target URL or endpoint and the payload. The entity will be created after the first message has arrived.
 
 All [requests](/developers/rest_api/#post-apistatesltentity_id) need to be sent to the endpoint of the device and must be **POST**.
 
+## {% linkable_title IP filtering and banning %}
+
 If you want to apply additional IP filtering, and automatically ban brute force attempts, set `ip_ban_enabled` to `True` and the maximum number of attempts. After the first ban, an `ip_bans.yaml` file will be created in the root configuration folder. It will have the banned IP address and time in UTC when it was added:
 
 ```yaml

source/_components/keyboard_remote.markdown

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

source/_components/nest.markdown

@@ -27,7 +27,7 @@ The Nest component is the main component to integrate all [Nest](https://nest.co
   - Product name must be unique. We recommend [email] - Home Assistant.
   - The description, users, URLs can all be anything you want.
   - Leave the "Redirect URI" Field blank
-7. For permissions check every box and if it's an option select the read/write option.
+7. For permissions check every box and if it's an option select the read/write option. Note: there are important permissions under the "Other Permissions" category. If you are only adding a thermostat, do not just select the permissions under "Thermostat". You still need to check the boxes under "Other Permissions" in order to give you access to features like away mode, ETA, structure read/write, and postal code.
   - The description requires a specific format to be accepted.
     - Use "[Home Assistant] [Edit] [For Home Automation]" as the description as it is not super important.
 8. Click "Create Product"

source/_components/notify.nma.markdown

@@ -1,40 +0,0 @@
----
-layout: page
-title: "Notify My Android"
-description: "Instructions on how to add NMA notifications to Home Assistant."
-date: 2015-05-01 18:00
-sidebar: true
-comments: false
-sharing: true
-footer: true
-logo: nma.png
-ha_category: Notifications
-ha_release: pre 0.7
----
-
-<p class='note warning'>
-As of May 24th 2018 [NMA has shut down](https://notifymyandroid.com/), this was due to the new GDPR european regulations. 
-</p>
-
-The `nma` platform uses [Notify My Android (NMA)](http://www.notifymyandroid.com/) to delivery notifications from Home Assistant to your Android device.
-
-Go to the [NMA website](https://www.notifymyandroid.com) and create a new API key. If you are using the trial offer then keep in mind that your limit is five messages per day.
-
-To add NMA to your installation, add the following to your `configuration.yaml` file:
-
-```yaml
-# Example configuration.yaml entry
-notify:
-  - name: NOTIFIER_NAME
-    platform: nma
-    api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
-```
-
-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`.
-- **api_key** (*Required*): The API key for NMA.
-
-Details for the [API](https://www.notifymyandroid.com/api.jsp).
-
-To use notifications, please see the [getting started with automation page](/getting-started/automation/).

source/_components/recorder.markdown

@@ -2,7 +2,7 @@
 layout: page
 title: "Recorder"
 description: "Instructions on how to configure the data recorder for Home Assistant."
-date: 2017-09-24 09:00
+date: 2018-06-03 11:30
 sidebar: true
 comments: false
 sharing: true
@@ -189,7 +189,7 @@ Not all Python bindings for the chosen database engine can be installed directly
 If you are in a virtual environment, don't forget to activate it before installing the `mysqlclient` Python package described below.
 
 ```bash
-pi@homeassistant:~ $ sudo su homeassistant -s /bin/bash  
+pi@homeassistant:~ $ sudo -u homeassistant -H -s
 homeassistant@homeassistant:~$ source /srv/homeassistant/bin/activate
 (homeassistant) homeassistant@homeassistant:~$ pip3 install mysqlclient
 ```
@@ -235,7 +235,7 @@ $ pip3 install pymssql
 If you are in a virtual environment, don't forget to activate it before installing the pymssql package.
 
 ```bash
-$ sudo su -s /bin/bash homeassistant
+$ sudo -u homeassistant -H -s
 $ source /srv/homeassistant/bin/activate
 $ pip3 install pymssql
 ```

source/_components/sensor.sensehat.markdown

@@ -2,7 +2,7 @@
 layout: page
 title: "Sense HAT"
 description: "Instructions on how to integrate Sense HAT within Home Assistant."
-date: 2017-06-03 04:00
+date: 2018-06-03 11:30
 sidebar: true
 comments: false
 sharing: true
@@ -109,7 +109,7 @@ Here are the steps to make the _SenseHAT_ sensor work _successfully_ with the vi
 #### Install SenseHAT package to _homeassistant_venv_
 ```bash
 # switch to the homeassistant_venv environment
-sudo su -s /bin/bash homeassistant
+sudo -u homeassistant -H -s
 source /srv/homeassistant/homeassistant_venv/bin/activate
 
 # install the sense-hat lib

source/_components/sensor.zabbix.markdown

@@ -35,6 +35,6 @@ Configuration variables:
 
 - **triggers** array(*Required*): Specifies that this sensor is for Zabbix 'triggers'. In the future there will be other Zabbix sensors.
 - **name** (*Optional*): Allows you to specify the name for the Sensor, otherwise the host name, as stored in Zabbix, is used.  This is useful when you are specifying a list of hostids to monitor as a single count.
-- **hostids** (*Optional*): This is a list of Zabbis hostids that we want to filter our count on.
+- **hostids** (*Optional*): This is a list of Zabbix hostids that we want to filter our count on.
 - **individual** (*Optional*): A 'true'/'false' to specify whether we should show individual sensors when a list of hostids is provided.  If false, the sensor state will be the count of all triggers for the specified hosts (or all hosts within the Zabbix instance, if hostids isn't provided).
 

source/_components/vacuum.markdown

@@ -1,7 +1,7 @@
 ---
 layout: page
 title: "Vacuum cleaner robots"
-description: "Instructions on how to setup a botvac in Home Assistant."
+description: "Instructions on how to setup and use vacuum's in Home Assistant."
 date: 2017-07-28 15:00
 sidebar: true
 comments: false
@@ -25,7 +25,7 @@ vacuum:
 
 Available services: `turn_on`, `turn_off`, `start_pause`, `stop`, `return_to_home`, `locate`, `clean_spot`, `set_fanspeed` and `send_command`.
 
-Before calling one of these services, make sure your botvac platform supports it.
+Before calling one of these services, make sure your vacuum platform supports it.
 
 #### {% linkable_title Service `vacuum.turn_on` %}
 
@@ -33,7 +33,7 @@ Start a new cleaning task.
 
 | Service data attribute    | Optional | Description                                           |
 |---------------------------|----------|-------------------------------------------------------|
-| `entity_id`               |      yes | Only act on specific botvac. Else targets all.        |
+| `entity_id`               |      yes | Only act on specific vacuum. Else targets all.        |
 
 #### {% linkable_title Service `vacuum.turn_off` %}
 
@@ -41,7 +41,7 @@ Stop the current cleaning task and return to the dock.
 
 | Service data attribute    | Optional | Description                                           |
 |---------------------------|----------|-------------------------------------------------------|
-| `entity_id`               |      yes | Only act on specific botvac. Else targets all.        |
+| `entity_id`               |      yes | Only act on specific vacuum. Else targets all.        |
 
 #### {% linkable_title Service `vacuum.start_pause` %}
 
@@ -49,23 +49,23 @@ Start, pause or resume a cleaning task.
 
 | Service data attribute    | Optional | Description                                           |
 |---------------------------|----------|-------------------------------------------------------|
-| `entity_id`               |      yes | Only act on specific botvac. Else targets all.        |
+| `entity_id`               |      yes | Only act on specific vacuum. Else targets all.        |
 
 #### {% linkable_title Service `vacuum.stop` %}
 
-Stop the current activity of the botvac.
+Stop the current activity of the vacuum.
 
 | Service data attribute    | Optional | Description                                           |
 |---------------------------|----------|-------------------------------------------------------|
-| `entity_id`               |      yes | Only act on specific botvac. Else targets all.        |
+| `entity_id`               |      yes | Only act on specific vacuum. Else targets all.        |
 
 #### {% linkable_title Service `vacuum.return_to_home` %}
 
-Tell the botvac to return home.
+Tell the vacuum to return home.
 
 | Service data attribute    | Optional | Description                                           |
 |---------------------------|----------|-------------------------------------------------------|
-| `entity_id`               |      yes | Only act on specific botvac. Else targets all.        |
+| `entity_id`               |      yes | Only act on specific vacuum. Else targets all.        |
 
 #### {% linkable_title Service `vacuum.locate` %}
 
@@ -73,7 +73,7 @@ Locate the vacuum cleaner robot.
 
 | Service data attribute    | Optional | Description                                           |
 |---------------------------|----------|-------------------------------------------------------|
-| `entity_id`               |      yes | Only act on specific botvac. Else targets all.        |
+| `entity_id`               |      yes | Only act on specific vacuum. Else targets all.        |
 
 #### {% linkable_title Service `vacuum.clean_spot` %}
 
@@ -81,15 +81,15 @@ Tell the vacuum cleaner to do a spot clean-up.
 
 | Service data attribute    | Optional | Description                                           |
 |---------------------------|----------|-------------------------------------------------------|
-| `entity_id`               |      yes | Only act on specific botvac. Else targets all.        |
+| `entity_id`               |      yes | Only act on specific vacuum. Else targets all.        |
 
 #### {% linkable_title Service `vacuum.set_fanspeed` %}
 
-Set the fan speed of the botvac. The `fanspeed` can be a label, as `balanced` or `turbo`, or be a number; it depends on the `vacuum` platform.
+Set the fan speed of the vacuum. The `fanspeed` can be a label, as `balanced` or `turbo`, or be a number; it depends on the `vacuum` platform.
 
 | Service data attribute    | Optional | Description                                           |
 |---------------------------|----------|-------------------------------------------------------|
-| `entity_id`               |      yes | Only act on specific botvac. Else targets all.        |
+| `entity_id`               |      yes | Only act on specific vacuum. Else targets all.        |
 | `fanspeed`                |       no | Platform dependent vacuum cleaner fan speed, with speed steps, like 'medium', or by percentage, between 0 and 100. |
 
 #### {% linkable_title Service `vacuum.send_command` %}
@@ -98,6 +98,6 @@ Send a platform-specific command to the vacuum cleaner.
 
 | Service data attribute    | Optional | Description                                           |
 |---------------------------|----------|-------------------------------------------------------|
-| `entity_id`               |      yes | Only act on specific botvac. Else targets all.        |
+| `entity_id`               |      yes | Only act on specific vacuum. Else targets all.        |
 | `command`                 |       no | Command to execute.                                   |
 | `params`                  |      yes | Parameters for the command.                           |

source/_components/vacuum.xiaomi_miio.markdown

@@ -2,7 +2,7 @@
 layout: page
 title: "Xiaomi Mi Robot Vacuum"
 description: "Instructions on how to integrate your Xiaomi Mi Robot Vacuum within Home Assistant."
-date: 2017-05-05 18:11
+date: 2018-06-03 11:30
 sidebar: true
 comments: false
 sharing: true
@@ -189,7 +189,7 @@ $ sudo apt-get install libffi-dev libssl-dev
 If your Home Assistant installation is running in a [Virtualenv](/docs/installation/virtualenv/#upgrading-home-assistant), make sure you activate it by running the commands below.
 
 ```bash
-$ sudo su -s /bin/bash homeassistant
+$ sudo -u homeassistant -H -s
 $ source /srv/homeassistant/bin/activate
 ```
 
@@ -219,7 +219,7 @@ $ sudo apt-get install libffi-dev libssl-dev
 If your Home Assistant installation is running in a [Virtualenv](/docs/installation/virtualenv/#upgrading-home-assistant), make sure you activate it by running the commands below.
 
 ```bash
-$ sudo su -s /bin/bash homeassistant
+$ sudo -u homeassistant -H -s
 $ source /srv/homeassistant/bin/activate
 ```
 

source/_docs/ecosystem/certificates/lets_encrypt.markdown

@@ -2,7 +2,7 @@
 layout: page
 title: "Remote Access with TLS/SSL via Let's Encrypt"
 description: "A guide to remotely accessing Home Assistant and securing the connection with an SSL certificate from Let's Encrypt"
-date: 2017-03-16 17:00
+date: 2018-06-03 11:00
 sidebar: true
 comments: false
 sharing: true
@@ -245,17 +245,17 @@ In cases where your ISP blocks port 80 you will need to change the port forward
 Now SSH in to the device your Home Assistant is running on.
 
 <p class='note'>
-If you're running the 'standard' setup on a Raspberry Pi the chances are you just logged in as the 'pi' user. If not, you may have logged in as the Home Assistant user. There are commands below that require the Home Assistant user to be on the `sudoers` list. If you are not using the 'standard' Pi setup it is presumed you will know how to get your Home Assistant user on the `sudoers` list before continuing.  If you are running the 'standard' Pi setup, from your 'pi' user issue the following command (where `hass` is the Home Assistant user):
+If you're running the 'standard' setup on a Raspberry Pi the chances are you just logged in as the 'pi' user. If not, you may have logged in as the Home Assistant user. There are commands below that require the Home Assistant user to be on the `sudoers` list. If you are not using the 'standard' Pi setup it is presumed you will know how to get your Home Assistant user on the `sudoers` list before continuing.  If you are running the 'standard' Pi setup, from your 'pi' user issue the following command (where `homeassistant` is the Home Assistant user):
 
 ```
-$ sudo adduser hass sudo
+$ sudo adduser homeassistant sudo
 ```
 </p>
 
-If you did not already log in as the user that currently runs Home Assistant, change to that user (usually `hass` or `homeassistant` - you may have used a command similar to this in the past):
+If you did not already log in as the user that currently runs Home Assistant, change to that user (usually `homeassistant` or `hass` - you may have used a command similar to this in the past):
 
 ```bash
-$ sudo su -s /bin/bash hass
+$ sudo -u homeassistant -H -s
 ```
 
 Make sure you are in the home directory for the Home Assistant user:
@@ -449,10 +449,10 @@ Your certificate can be renewed as a 'cron job' - cron jobs are background tasks
 To set a cron job to run the script at regular intervals:
 
  * SSH in to your device running Home Assistant.
- * Change to your Home Assistant user (command similar to):
+ * Change to your Home Assistant user (where `homeassistant` is the name of the user):
 
 ```bash
-$ sudo su -s /bin/bash hass
+$ sudo -u homeassistant -H -s
 ```
 
  * Open the crontab:
@@ -506,10 +506,10 @@ You can manually update the certificate when your certificate is less than 30 da
 To manually update:
 
  * SSH in to your device running Home Assistant.
- * Change to your Home Assistant user (command similar to):
+ * Change to your Home Assistant user (where `homeassistant` is the name of the user):
 
 ```bash
-$ su - s /bin/bash hass
+$ sudo -u homeassistant -H -s
 ```
 
  * Change to your certbot folder

source/_docs/installation/hassbian/common-tasks.markdown

@@ -2,7 +2,7 @@
 layout: page
 title: "Common tasks on Hassbian"
 description: "Instructions on how to do common tasks on Hassbian."
-date: 2016-09-26 21:00
+date: 2018-06-03 11:00
 sidebar: true
 comments: false
 sharing: true
@@ -44,7 +44,7 @@ Log in as the `pi` account and execute the following commands:
 
 ```bash
 $ sudo systemctl stop home-assistant@homeassistant.service
-$ sudo su -s /bin/bash homeassistant
+$ sudo -u homeassistant -H -s
 $ source /srv/homeassistant/bin/activate
 $ pip3 install --upgrade homeassistant
 $ exit
@@ -64,7 +64,7 @@ This will in order do the following:
 Log in as the `pi` account and execute the following commands:
 
 ```bash
-$ sudo su -s /bin/bash homeassistant
+$ sudo -u homeassistant -H -s
 $ source /srv/homeassistant/bin/activate
 $ hass
 ```
@@ -75,7 +75,7 @@ This will start Home Assistant in your shell and output anything that ends up in
 Log in as the `pi` account and execute the following commands:
 
 ```bash
-$ sudo su -s /bin/bash homeassistant
+$ sudo -u homeassistant -H -s
 $ source /srv/homeassistant/bin/activate
 $ hass --script check_config
 ```
@@ -86,7 +86,7 @@ This will output any errors in your configuration files to console.
 Log in as the `pi` account and execute the following commands:
 
 ```bash
-$ sudo su -s /bin/bash homeassistant
+$ sudo -u homeassistant -H -s
 $ cd /home/homeassistant/.homeassistant
 $ nano home-assistant.log
 ```
@@ -109,7 +109,7 @@ $ sudo journalctl -fu home-assistant@homeassistant.service
 Log in as the `pi` account and execute the following commands:
 
 ```bash
-$ sudo su -s /bin/bash homeassistant
+$ sudo -u homeassistant -H -s
 $ cd /home/homeassistant/.homeassistant
 $ nano configuration.yaml
 ```

source/_docs/installation/hassbian/upgrading.markdown

@@ -2,7 +2,7 @@
 layout: page
 title: "Upgrading Hassbian"
 description: "Instructions on how to upgrade Hassbian to the latest version."
-date: 2016-09-26 21:00
+date: 2018-06-03 11:00
 sidebar: true
 comments: false
 sharing: true
@@ -27,7 +27,7 @@ To update the Home Assistant installation execute the following command as the `
 
 ```bash
 $ sudo systemctl stop home-assistant@homeassistant.service
-$ sudo su -s /bin/bash homeassistant
+$ sudo -u homeassistant -H -s
 $ source /srv/homeassistant/bin/activate
 $ pip3 install --upgrade homeassistant
 $ exit

source/_docs/installation/raspberry-pi.markdown

@@ -2,7 +2,7 @@
 layout: page
 title: "Manual installation on a Raspberry Pi"
 description: "Instructions to install Home Assistant on a Raspberry Pi running Raspbian Lite."
-date: 2016-09-05 16:00
+date: 2018-06-03 11:00
 sidebar: true
 comments: false
 sharing: true
@@ -66,7 +66,7 @@ $ sudo chown homeassistant:homeassistant homeassistant
 Next up is to create and change to a virtual environment for Home Assistant. This will be done as the `homeassistant` account.
 
 ```bash
-$ sudo su -s /bin/bash homeassistant
+$ sudo -u homeassistant -H -s
 $ cd /srv/homeassistant
 $ python3 -m venv .
 $ source bin/activate
@@ -101,7 +101,7 @@ If you want setup `hass` as a daemon and autostart it on boot please refer to [A
 To update to the latest version of Home Assistant follow these simple steps:
 
 ```bash
-$ sudo su -s /bin/bash homeassistant
+$ sudo -u homeassistant -H -s
 $ source /srv/homeassistant/bin/activate
 $ pip3 install --upgrade homeassistant
 ```

source/_docs/z-wave/device-specific.markdown

@@ -194,6 +194,49 @@ Triple tap on|1|4
 
 Tap and hold wakes up the Button.
 
+### {% linkable_title Fibaro Keyfob FGKF-601 %}
+
+
+For the Fibaro Keyfob, you may need to update the `COMMAND_CLASS_CENTRAL_SCENE` for each node in your `zwcfg` file with the following:
+
+```xml
+      <CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="6">
+	<Instance index="1" />
+	<Value type="int" genre="system" instance="1" index="0" label="Scene Count" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="6" />
+	<Value type="int" genre="user" instance="1" index="1" label="Square" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
+	<Value type="int" genre="user" instance="1" index="2" label="Circle" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
+	<Value type="int" genre="user" instance="1" index="3" label="X" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
+	<Value type="int" genre="user" instance="1" index="4" label="Triangle" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
+	<Value type="int" genre="user" instance="1" index="5" label="Minus" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
+	<Value type="int" genre="user" instance="1" index="6" label="Plus" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
+</CommandClass>
+```
+
+Below is a table of the action/scenes for the Keyfob (as a reference for other similar devices):
+
+**Action**|**scene\_id**|**scene\_data**
+:-----:|:-----:|:-----:
+Button one (Square) single tap|1|7680
+Button one (Square) hold|1|7800
+Button one (Square) release|1|7740
+Button two (Circle) single tap|2|7680
+Button two (Circle) hold|2|7800
+Button two (Circle) release|2|7740
+Button three (X) single tap|3|7680
+Button three (X) hold|3|7800
+Button three (X) release|3|7740
+Button four (Triangle) single tap|4|7680
+Button four (Triangle) hold|4|7800
+Button four (Triangle) release|4|7740
+Button five (Triangle) single tap|5|7680
+Button five (Triangle) hold|5|7800
+Button five (Triangle) release|5|7740
+Button six (Triangle) single tap|6|7680
+Button six (Triangle) hold|6|7800
+Button six (Triangle) release|6|7740
+
+Press circle and plus simultaneously to wake up the device.
+
 ### {% linkable_title Aeotec Wallmote %}
 
 <!-- from https://hastebin.com/esodiweduq.cs -->

source/_posts/2018-06-04-esphomelib.markdown

@@ -0,0 +1,89 @@
+---
+layout: post
+title: "esphomelib - A comprehensive solution for using ESPs with Home Assistant"
+description: "Use the esphomelib suite to make using ESPs really simple."
+date: 2018-06-05 06:24:55 +0000
+date_formatted: "June 5, 2018"
+author: Otto Winter
+author_twitter: OttoWinter_
+comments: true
+categories: How-To ESP8266
+og_image: /images/blog/2018-06-esphomelib/social.png
+---
+
+The [ESP8266](https://www.espressif.com/en/products/hardware/esp8266ex/overview) and [ESP32](https://www.espressif.com/en/products/hardware/esp32/overview) are dirt cheap WiFi-enabled microcontrollers that have established themselves as the base for many DIY home automation projects. Even quite a few manufacturers like iTead with their Sonoff devices have chosen these controllers because of their competitive price.
+
+Setting up these microcontrollers for some basic functionality has also gotten really easy over the years with popular projects like ESPEasy or Sonoff-Tasmota: You just download their firmware and flash it onto your chip. But if you’ve ever tried to go a bit beyond the basic set of functions of those frameworks and tried to do some customization, you will have probably noticed that it’s not that easy. Often times you’ll end up having to download some Arduino code project from the internet and customizing it to your needs.
+
+This is where esphomlib comes in: The [esphomelib suite](https://esphomelib.com/esphomeyaml/index.html) is a set of tools that are designed with the goal of achieving the best possible user experience.  esphomelib a) allows for lots of customization without touching *a single line* of code and b) has complete Home Assistant integration. Inside the esphomelib ecosystem, you essentially just have to write a simple YAML configuration file. The rest like compiling, flashing, uploading etc. will then be taken care of automatically.
+
+<!--more-->
+
+## {% linkable_title Installation %}
+
+An example probably illustrates this the best. To use esphomeyaml, there are two main ways: From a [HassIO add-on](https://esphomelib.com/esphomeyaml/guides/getting_started_hassio.html), or from the [command line](https://esphomelib.com/esphomeyaml/guides/getting_started_command_line.html). For the esphomeyaml add-on, you just have to add "[https://github.com/ottowinter/esphomeyaml](https://github.com/ottowinter/esphomeyaml)" as an add-on repository (see [Installing third party add-ons](/hassio/installing_third_party_addons/)). Then select and install “esphomeyaml” and wait for the installation to complete. After that, you will be able to start the add-on and view the web interface.
+
+From the command line you just need to install the **Python 2** package using the pip command seen below. Then visit `localhost:6052` to view the dashboard.
+
+```bash
+pip2 install esphomeyaml
+esphomeyaml config/ dashboard
+# Alternative for docker users:
+docker run --rm -p 6052:6052 -p 6123:6123 -v "$PWD":/config ottowinter/esphomeyaml /config dashboard
+```
+
+<div class="videoWrapper">
+  <iframe width="853" height="480" src="https://www.youtube-nocookie.com/embed/uWZmc_MjSWs?rel=0&amp;showinfo=0loop=1&amp;autoplay=1" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
+</div>
+
+Once in the dashboard interface, you will be greeted by a small setup wizard that will help you get started with esphomeyaml and create a basic configuration. You should end up with a configuration file like this.
+
+```yaml
+esphomeyaml:
+  name: livingroom
+  platform: ESP8266
+  board: nodemcuv2
+
+wifi:
+  ssid: 'MySSID'
+  password: 'MyPassword'
+
+mqtt:
+  broker: '192.168.178.83'
+  username: ''
+  password: ''
+
+logger:
+ota:
+```
+
+At this point, you can already flash the firmware. To do this, first plug in the USB cable of the ESP into a USB port of the device esphomeyaml is running on and wait until you see a “Discovered new serial port” message (in some cases you need to restart the add-on). Select the upload port in the top navigation bar and press the big "UPLOAD" button. If everything succeeds, you should now have a functioning esphomelib node and see the debug logs 🎉
+
+## {% linkable_title Adding some basic functionality %}
+
+Above configuration is, let’s face it, pretty dull. It really only connects to WiFi and MQTT and sits idle. So let’s add a basic [GPIO switch](https://esphomelib.com/esphomeyaml/components/switch/gpio.html)! The GPIO switch component in esphomelib allows you to control the ON/OFF state of any of the pins on your ESP. For example, if you add this configuration to the bottom of your YAML file, you’re setting up the pin `GPIO5` to be controlled as a switch with the name "Living Room Dehumidifer".
+
+```yaml
+switch:
+  - platform: gpio
+    name: "Living Room Dehumidifer"
+    pin: GPIO5
+```
+If you now press upload again (this time the ESP doesn't need to be connected via USB, as updates [can be done over WiFi](https://esphomelib.com/esphomeyaml/components/ota.html)), you will see a switch show up in Home Assisstant automatically through [MQTT discovery](/docs/mqtt/discovery/).
+
+<p class='img'>
+  <img
+    src='/images/blog/2018-06-esphomelib/switch.png'
+    alt='esphomeyamls setup wizard.'>
+  How the newly configured switch will show up in Home Assistant if <a href='/docs/mqtt/discovery/'>MQTT
+  discovery</a> is enabled and a <a href='/components/group/'>default view</a> is used.
+</p>
+
+Granted, this functionality would have been pretty simple with other projects too. But once you start adding [lights](https://esphomelib.com/esphomeyaml/index.html#light-components), [covers](https://esphomelib.com/esphomeyaml/index.html#cover-components) and [other sensors](https://esphomelib.com/esphomeyaml/index.html#sensor-components), esphomelib’s modular design really starts to shine.
+
+## {% linkable_title See Also %}
+
+- [View the full getting started guide (including how to migrate from other projects)](https://esphomelib.com/esphomeyaml/index.html#guides)
+- [Device-specific setup guides](https://esphomelib.com/esphomeyaml/index.html#devices)
+- [List of supported sensors/actuators](https://esphomelib.com/esphomeyaml/index.html)
+- Join the [discord server](https://discord.gg/KhAMKrd) if you need help.

source/_posts/2018-06-10-release-71.markdown

@@ -0,0 +1,418 @@
+---
+layout: post
+title: "0.71: Lagute LW-12, Iperf3, Hydrawise, Ryobi Garage Doors"
+description: "Enjoy the weekend with this shiny new release."
+date: 2018-06-08 00:01:00
+date_formatted: "June 8, 2018"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2018-06-0.71/components.png
+---
+
+<a href='/components/#version/0.71'><img src='/images/blog/2018-06-0.71/components.png' style='border: 0;box-shadow: none;'></a>
+
+0.71 has arrived. My favorite feature in this release is the conversion of the Nest component from cloud poll to cloud push. Sure, it's still through the cloud but changes are now made available in Home Assistnat as soon as they happen. Thanks [@awarecan]!
+
+We've continued the frontend tweaks after the major overhaul in the last release. We've had some issues with the Hass.io panel on both Firefox and Safari. They have been addressed and all browsers should hopefully work again.
+
+On the frontend side, custom panels have gotten some new tricks, including support for building panels using React. So if you're a developer, [check it out](https://developers.home-assistant.io/blog/2018/06/01/071-custom-panels.html). And thanks to [@c727] a lot more strings can now be translated. More info on how to help with translating the frontend can be found [here](https://developers.home-assistant.io/docs/en/internationalization_translation.html).
+
+HomeKit support also keeps growing. This release includes support for media players, automations and outlets thanks to [@schmittx].
+
+And in case you missed it, [@OttoWinter] has created [esphomeyaml], which allows you to program and deploy ESP chips throughout your house by using a Home Assistant inspired `configuration.yaml`. [Check it out](/blog/2018/06/05/esphomelib/).
+
+Have a good weekend everyone!
+
+## {% linkable_title New Platforms %}
+
+- Lagute LW-12 Wifi LED control ([@jaypikay] - [#13307]) ([light.lw12wifi docs]) (new-platform)
+- Add Xiaomi Aqara Lock support ([@SchumyHao] - [#14419]) ([xiaomi_aqara docs]) ([lock.xiaomi_aqara docs]) (new-platform)
+- Add Iperf3 client sensor ([@tchellomello] - [#14213]) ([sensor.iperf3 docs]) (new-platform)
+- Add homematicip cloud climate platform ([@mxworm] - [#14388]) ([homematicip_cloud docs]) ([climate.homematicip_cloud docs]) (new-platform)
+- Add Hydrawise component ([@ptcryan] - [#14055]) ([hydrawise docs]) ([binary_sensor.hydrawise docs]) ([sensor.hydrawise docs]) ([switch.hydrawise docs]) (new-platform)
+- Adding ryobi garage door opener ([@guillaume1410] - [#14618]) ([cover.ryobi_gdo docs]) (new-platform)
+- Add sensors and services to RainMachine ([@bachya] - [#14326]) ([rainmachine docs]) ([binary_sensor.rainmachine docs]) ([sensor.rainmachine docs]) ([switch.rainmachine docs]) (new-platform)
+- Add Flock notification platform ([@fabaff] - [#14533]) ([notify docs]) (new-platform)
+
+## {% linkable_title New Features %}
+
+- Add HomeKit support for media players ([@schmittx] - [#14446]) ([homekit docs]) (new-feature)
+- Add HomeKit support for automations ([@schmittx] - [#14595]) ([homekit docs]) (new-feature)
+- Extend package support ([@cdce8p] - [#14611]) (new-feature)
+- Change nest to cloud push ([@awarecan] - [#14656]) ([nest docs]) ([binary_sensor.nest docs]) ([climate.nest docs]) ([sensor.nest docs]) (new-feature)
+- Add support for outlets in HomeKit ([@schmittx] - [#14628]) ([homekit docs]) (new-feature)
+
+## {% 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 %}
+
+- BOM sensor: `'Wind Direction kt'` to `'Wind Speed kt'` (fixes #14535) ([@fabaff] - [#14541]) ([sensor.bom docs]) (breaking change)
+- Removed attribute current_time from Raincloudy sensors to avoid being triggered by recorder component ([@tchellomello] - [#14584]) ([raincloud docs]) ([switch.raincloud docs]) (breaking change)
+- Remove Notify My Android component as it shut down on May 24 ([@cgarwood] - [#14594]) ([notify docs]) (breaking change)
+- CoinMarketCap sensor: It is no longer possible to query a ticker by the name of the currency (i.e. bitcoin). The API instead uses IDs (integers) for these tickers (i.e. bitcoin -> 1). Rounding of decimals is now configurable, because it made no sense to round to 2 decimals if display_currency was set to BTC, some values showed up as 0.00. (#14437) ([@kotlarz] - [#14604]) ([sensor.coinmarketcap docs]) (breaking change)
+- Give unknown zwave nodes a better name and don't add them to entity registry ([@andrey-git] - [#14353]) ([zwave docs]) (breaking change)
+- The `netdata` sensor was re-worked to support all available details from [Netdata](https://my-netdata.io/). This requires you to adjust the your existing configuration if you use the `netdata` sensor.
+ ([@fabaff] - [#14613]) ([sensor.netdata docs]) (breaking change)
+- Disallow automation.trigger without entity_id. Triggering all automations at once is most likely a user mistake but if it is really needed, one can use `entity_id: group.all_automations`. ([@amelchio] - [#14724]) ([automation docs]) (breaking change)
+
+## {% linkable_title Beta Fixes %}
+
+- Use hass iconset ([@balloob] - [#14185]) ([config docs]) ([frontend docs]) ([hassio docs]) ([history docs]) ([logbook docs]) (beta fix)
+- Zone - Hass configuration name is optional ([@Kane610] - [#14449]) ([zone docs]) (beta fix)
+
+## {% linkable_title All changes %}
+
+- Upgrade aiohttp to 3.2.1 ([@fabaff] - [#14517])
+- Upgrade youtube_dl to 2018.05.18 ([@fabaff] - [#14519]) ([media_extractor docs])
+- Upgrade keyring to 12.2.1 ([@fabaff] - [#14521])
+- Upgrade restrictedpython to 4.0b4 ([@fabaff] - [#14537]) ([python_script docs])
+- Bump pyvera version (improve stability of poll loop). ([@pavoni] - [#14540]) ([vera docs])
+- Fix sensor name (fixes #14535) ([@fabaff] - [#14541]) ([sensor.bom docs]) (breaking change)
+- Add support to ignore a xiaomi aqara gateway ([@ileler] - [#14428]) ([xiaomi_aqara docs])
+- Pushed to version 0.7.2 of denonavr ([@scarface-4711] - [#14551]) ([media_player.denonavr docs])
+- Add auto discovery for nanoleaf aurora lights ([@Oro] - [#14301]) ([light.nanoleaf_aurora docs])
+- zha: Don't poll switch devices ([@dmulcahey] - [#14560]) ([binary_sensor.zha docs])
+- zha: Add metering sensor ([@dmulcahey] - [#14562]) ([zha docs]) ([sensor.zha docs])
+- zha: Set default binary_sensor state to false ([@damarco] - [#14553]) ([binary_sensor.zha docs])
+- Add IlluminanceMeasurementSensor to ZHA ([@dmulcahey] - [#14563]) ([zha docs]) ([sensor.zha docs])
+- zha: Bump to zigpy-xbee 0.1.1 ([@rcloran] - [#14566]) ([zha docs])
+- Update pyhomematic to 0.1.43 ([@danielperna84] - [#14583]) ([homematic docs])
+- Removed attribute current_time from Raincloudy sensors to avoid being triggered by recorder component ([@tchellomello] - [#14584]) ([raincloud docs]) ([switch.raincloud docs]) (breaking change)
+- Lagute LW-12 Wifi LED control ([@jaypikay] - [#13307]) ([light.lw12wifi docs]) (new-platform)
+- Add new transmission sensor types ([@fabaff] - [#14530]) ([sensor.transmission docs])
+- Add Xiaomi Aqara Lock support ([@SchumyHao] - [#14419]) ([xiaomi_aqara docs]) ([lock.xiaomi_aqara docs]) (new-platform)
+- Upgrade TwitterAPI to 2.5.3 ([@fabaff] - [#14596]) ([notify docs])
+- Remove nma component ([@cgarwood] - [#14594]) ([notify docs]) (breaking change)
+- Add Nest away binary sensor and eta sensor ([@awarecan] - [#14406])
+- Adds a device class of 'garage' to MyQ covers ([@bachya] - [#14602]) ([cover.myq docs])
+- Add Iperf3 client sensor ([@tchellomello] - [#14213]) ([sensor.iperf3 docs]) (new-platform)
+- Upgrade linode-api to 4.1.9b1 (#13863) ([@robertbeal] - [#14610]) ([linode docs])
+- Update pyrainbird ([@Klathmon] - [#14617]) ([rainbird docs])
+- Add support container status for Glances on RPi3 ([@bastshoes] - [#14529]) ([sensor.glances docs])
+- Adding illumination sensor ([@nklever] - [#14615]) ([sensor.onewire docs])
+- Add HomeKit support for media players ([@schmittx] - [#14446]) ([homekit docs]) (new-feature)
+- Add HomeKit support for automations ([@schmittx] - [#14595]) ([homekit docs]) (new-feature)
+- Add configurable decimal rounding of display value for CoinMarketCap sensor and upgrade to 5.0.3 (#14437) ([@kotlarz] - [#14604]) ([sensor.coinmarketcap docs]) (breaking change)
+- Extend package support ([@cdce8p] - [#14611]) (new-feature)
+- Added option to connect via SSL for OpenWRT(luci) device tracker ([@lorenzschmid] - [#14627]) ([device_tracker docs])
+- Added UDP and parallel streams support to Iperf3 ([@tchellomello] - [#14629]) ([sensor.iperf3 docs])
+- Add services for adding and removing items to shopping list ([@mammuth] - [#14574]) ([shopping_list docs])
+- Add homematicip cloud climate platform ([@mxworm] - [#14388]) ([homematicip_cloud docs]) ([climate.homematicip_cloud docs]) (new-platform)
+- Upgrade speedtest-cli to 2.0.2 ([@fabaff] - [#14633]) ([sensor.speedtest docs])
+- Add Hydrawise component ([@ptcryan] - [#14055]) ([hydrawise docs]) ([binary_sensor.hydrawise docs]) ([sensor.hydrawise docs]) ([switch.hydrawise docs]) (new-platform)
+- Adding ryobi garage door opener ([@guillaume1410] - [#14618]) ([cover.ryobi_gdo docs]) (new-platform)
+- Add electrical measurement sensor to ZHA ([@dmulcahey] - [#14561]) ([zha docs]) ([sensor.zha docs])
+- Upgrade luftdaten to 0.2.0 ([@fabaff] - [#14620]) ([sensor.luftdaten docs])
+- Upgrade python-nest to 4.0.0 ([@awarecan] - [#14638]) ([nest docs])
+- Upgrade gitterpy to 0.1.7 ([@fabaff] - [#14643]) ([sensor.gitter docs])
+- Upgrade TwitterAPI to 2.5.4 ([@fabaff] - [#14639]) ([notify docs])
+- Use constants ([@fabaff] - [#14647]) ([api docs])
+- Upgrade locationsharinglib to 2.0.7 ([@fabaff] - [#14640]) ([device_tracker docs])
+- Upgrade youtube_dl to 2018.05.26 ([@fabaff] - [#14654]) ([media_extractor docs])
+- Upgrade python_opendata_transport to 0.1.0 ([@fabaff] - [#14652]) ([sensor.swiss_public_transport docs])
+- Remove docker prereqs scripts that only install a package. Add informational message for this. ([@michaelarnauts] - [#14661])
+- Reduce log churn from Envisalink binary sensors ([@koreth] - [#14659]) ([binary_sensor.envisalink docs])
+- Force update ZHA electrical sensor ([@dmulcahey] - [#14649]) ([sensor.zha docs])
+- Improve Homekit media_player options ([@cdce8p] - [#14637]) ([homekit docs])
+- zha/light: Properly parse currentX and currentY on async_update() ([@Adminiuga] - [#14605]) ([light.zha docs])
+- Add tv channel and volume level for philips js API 5 ([@treehoof] - [#14276]) ([media_player.philips_js docs])
+- Give unknown zwave nodes a better name ([@andrey-git] - [#14353]) ([zwave docs]) (breaking change)
+- Add pin pad to alarm panel ([@raccettura] - [#14178]) ([alarm_control_panel.manual docs])
+- Update mfi.py ([@Bakkoda] - [#14667]) ([sensor.mfi docs])
+- Increase Eufy's requirement on lakeside ([@mjg59] - [#14671]) ([eufy docs])
+- Allow hassio frontend development ([@balloob] - [#14675]) ([hassio docs])
+- zha: fix temperature rounding for ZHA temperature sensors. ([@Adminiuga] - [#14669]) ([sensor.zha docs])
+- Allow user-defined sensors ([@fabaff] - [#14613]) ([sensor.netdata docs]) (breaking change)
+- deCONZ - Option to load or not to load clip sensors on start ([@Kane610] - [#14480]) ([binary_sensor.deconz docs]) ([sensor.deconz docs])
+- Add asyncio support for Ebox ([@titilambert] - [#14183])
+- Add sensors and services to RainMachine ([@bachya] - [#14326]) ([rainmachine docs]) ([binary_sensor.rainmachine docs]) ([sensor.rainmachine docs]) ([switch.rainmachine docs]) (new-platform)
+- Update HAP-python to 2.2.2 ([@cdce8p] - [#14674]) ([homekit docs])
+- Fix deprecated code ([@balloob] - [#14681]) ([cloud docs])
+- Homekit Bugfixes ([@cdce8p] - [#14689]) ([homekit docs])
+- Netatmo Sensor: Implement device_class ([@heinemml] - [#14634]) ([sensor.netatmo docs])
+- Change ACP code_format to None|"Number"|"Any" ([@c727] - [#14686])
+- Fixes (and stabilizes) some incorrect zone codes in RainMachine ([@bachya] - [#14719]) ([switch.rainmachine docs])
+- Add Flock notification platform ([@fabaff] - [#14533]) ([notify docs]) (new-platform)
+- Revert "Remove simplepush.io ([@balloob] - [#14358]) ([notify docs]) (breaking change)
+- Add device_descriptor and device_name to keyboard event ([@glenn20] - [#14642]) ([keyboard_remote docs])
+- Upgrade shodan to 1.8.0 ([@fabaff] - [#14717]) ([sensor.shodan docs])
+- Homekit Thermostat: Better support for temperature ranges ([@roiff] - [#14679]) ([homekit docs])
+- Custom panel ([@balloob] - [#14708]) ([panel_custom docs])
+- Disallow automation.trigger without entity_id ([@amelchio] - [#14724]) ([automation docs]) (breaking change)
+- Change nest to cloud push ([@awarecan] - [#14656]) ([nest docs]) ([binary_sensor.nest docs]) ([climate.nest docs]) ([sensor.nest docs]) (new-feature)
+- Add support for outlets in HomeKit ([@schmittx] - [#14628]) ([homekit docs]) (new-feature)
+- Add battery attribute to Sensibo ([@michaeldavie] - [#14735]) ([climate.sensibo docs])
+- Update syntax ([@fabaff] - [#14742]) ([counter docs])
+- Upgrade blockchain to 1.4.4 ([@fabaff] - [#14738]) ([sensor.bitcoin docs])
+- Added option to block Osram Lightify individual lights in the same way that groups can be ([@austinlg96] - [#14470]) ([light.osramlightify docs])
+- Upgrade directpy to 0.5 ([@Bahnburner] - [#14750]) ([media_player.directv docs])
+- Update syntax of platform random ([@fabaff] - [#14767]) ([binary_sensor.random docs]) ([sensor.random docs])
+- Update postnl api to 1.0.2 ([@iMicknl] - [#14769]) ([sensor.postnl docs])
+- Remove swagger file ([@fabaff] - [#14762])
+- Update syntax ([@fabaff] - [#14771]) ([sensor.version docs])
+- Update syntax ([@fabaff] - [#14768]) ([sensor.worldclock docs])
+- Update syntax ([@fabaff] - [#14770]) ([sensor.uptime docs])
+- Upgrade Sphinx to 1.7.5 ([@fabaff] - [#14764])
+- Upgrade youtube_dl to 2018.06.02 ([@fabaff] - [#14763]) ([media_extractor docs])
+- Upgrade sqlalchemy to 1.2.8 ([@fabaff] - [#14765])
+- Upgrade shodan to 1.8.1 ([@fabaff] - [#14760]) ([sensor.shodan docs])
+- Update syntax ([@fabaff] - [#14772]) ([sensor.simulated docs])
+- Assign device class to nest sensors ([@awarecan] - [#14746]) ([nest docs]) ([binary_sensor.nest docs]) ([sensor.nest docs])
+- Ignore the mistaken long_click event of the 86sw (Closes: #14694) ([@syssi] - [#14785]) ([binary_sensor.xiaomi_aqara docs])
+- Update total-connect-client to 0.18 for Honeywell Lynx Touch-Wifi support ([@jwood55812] - [#14778]) ([alarm_control_panel.totalconnect docs])
+- Add Kodi OnResume event ([@quthla] - [#14790]) ([media_player.kodi docs])
+- Fix media_title empty when title is empty but label is set ([@quthla] - [#14791]) ([media_player.kodi docs])
+- Add homematicip_cloud illuminance sensor ([@mxworm] - [#14720]) ([sensor.homematicip_cloud docs])
+- Use hass iconset ([@balloob] - [#14185]) ([config docs]) ([frontend docs]) ([hassio docs]) ([history docs]) ([logbook docs]) (beta fix)
+- Zone - Hass configuration name is optional ([@Kane610] - [#14449]) ([zone docs]) (beta fix)
+
+[#13307]: https://github.com/home-assistant/home-assistant/pull/13307
+[#14055]: https://github.com/home-assistant/home-assistant/pull/14055
+[#14178]: https://github.com/home-assistant/home-assistant/pull/14178
+[#14183]: https://github.com/home-assistant/home-assistant/pull/14183
+[#14185]: https://github.com/home-assistant/home-assistant/pull/14185
+[#14213]: https://github.com/home-assistant/home-assistant/pull/14213
+[#14276]: https://github.com/home-assistant/home-assistant/pull/14276
+[#14301]: https://github.com/home-assistant/home-assistant/pull/14301
+[#14326]: https://github.com/home-assistant/home-assistant/pull/14326
+[#14353]: https://github.com/home-assistant/home-assistant/pull/14353
+[#14358]: https://github.com/home-assistant/home-assistant/pull/14358
+[#14388]: https://github.com/home-assistant/home-assistant/pull/14388
+[#14406]: https://github.com/home-assistant/home-assistant/pull/14406
+[#14419]: https://github.com/home-assistant/home-assistant/pull/14419
+[#14428]: https://github.com/home-assistant/home-assistant/pull/14428
+[#14446]: https://github.com/home-assistant/home-assistant/pull/14446
+[#14449]: https://github.com/home-assistant/home-assistant/pull/14449
+[#14470]: https://github.com/home-assistant/home-assistant/pull/14470
+[#14480]: https://github.com/home-assistant/home-assistant/pull/14480
+[#14517]: https://github.com/home-assistant/home-assistant/pull/14517
+[#14519]: https://github.com/home-assistant/home-assistant/pull/14519
+[#14521]: https://github.com/home-assistant/home-assistant/pull/14521
+[#14529]: https://github.com/home-assistant/home-assistant/pull/14529
+[#14530]: https://github.com/home-assistant/home-assistant/pull/14530
+[#14533]: https://github.com/home-assistant/home-assistant/pull/14533
+[#14537]: https://github.com/home-assistant/home-assistant/pull/14537
+[#14540]: https://github.com/home-assistant/home-assistant/pull/14540
+[#14541]: https://github.com/home-assistant/home-assistant/pull/14541
+[#14551]: https://github.com/home-assistant/home-assistant/pull/14551
+[#14553]: https://github.com/home-assistant/home-assistant/pull/14553
+[#14560]: https://github.com/home-assistant/home-assistant/pull/14560
+[#14561]: https://github.com/home-assistant/home-assistant/pull/14561
+[#14562]: https://github.com/home-assistant/home-assistant/pull/14562
+[#14563]: https://github.com/home-assistant/home-assistant/pull/14563
+[#14566]: https://github.com/home-assistant/home-assistant/pull/14566
+[#14574]: https://github.com/home-assistant/home-assistant/pull/14574
+[#14583]: https://github.com/home-assistant/home-assistant/pull/14583
+[#14584]: https://github.com/home-assistant/home-assistant/pull/14584
+[#14594]: https://github.com/home-assistant/home-assistant/pull/14594
+[#14595]: https://github.com/home-assistant/home-assistant/pull/14595
+[#14596]: https://github.com/home-assistant/home-assistant/pull/14596
+[#14602]: https://github.com/home-assistant/home-assistant/pull/14602
+[#14604]: https://github.com/home-assistant/home-assistant/pull/14604
+[#14605]: https://github.com/home-assistant/home-assistant/pull/14605
+[#14610]: https://github.com/home-assistant/home-assistant/pull/14610
+[#14611]: https://github.com/home-assistant/home-assistant/pull/14611
+[#14613]: https://github.com/home-assistant/home-assistant/pull/14613
+[#14615]: https://github.com/home-assistant/home-assistant/pull/14615
+[#14617]: https://github.com/home-assistant/home-assistant/pull/14617
+[#14618]: https://github.com/home-assistant/home-assistant/pull/14618
+[#14620]: https://github.com/home-assistant/home-assistant/pull/14620
+[#14627]: https://github.com/home-assistant/home-assistant/pull/14627
+[#14628]: https://github.com/home-assistant/home-assistant/pull/14628
+[#14629]: https://github.com/home-assistant/home-assistant/pull/14629
+[#14633]: https://github.com/home-assistant/home-assistant/pull/14633
+[#14634]: https://github.com/home-assistant/home-assistant/pull/14634
+[#14637]: https://github.com/home-assistant/home-assistant/pull/14637
+[#14638]: https://github.com/home-assistant/home-assistant/pull/14638
+[#14639]: https://github.com/home-assistant/home-assistant/pull/14639
+[#14640]: https://github.com/home-assistant/home-assistant/pull/14640
+[#14642]: https://github.com/home-assistant/home-assistant/pull/14642
+[#14643]: https://github.com/home-assistant/home-assistant/pull/14643
+[#14647]: https://github.com/home-assistant/home-assistant/pull/14647
+[#14649]: https://github.com/home-assistant/home-assistant/pull/14649
+[#14652]: https://github.com/home-assistant/home-assistant/pull/14652
+[#14654]: https://github.com/home-assistant/home-assistant/pull/14654
+[#14656]: https://github.com/home-assistant/home-assistant/pull/14656
+[#14659]: https://github.com/home-assistant/home-assistant/pull/14659
+[#14661]: https://github.com/home-assistant/home-assistant/pull/14661
+[#14667]: https://github.com/home-assistant/home-assistant/pull/14667
+[#14669]: https://github.com/home-assistant/home-assistant/pull/14669
+[#14671]: https://github.com/home-assistant/home-assistant/pull/14671
+[#14674]: https://github.com/home-assistant/home-assistant/pull/14674
+[#14675]: https://github.com/home-assistant/home-assistant/pull/14675
+[#14679]: https://github.com/home-assistant/home-assistant/pull/14679
+[#14681]: https://github.com/home-assistant/home-assistant/pull/14681
+[#14686]: https://github.com/home-assistant/home-assistant/pull/14686
+[#14689]: https://github.com/home-assistant/home-assistant/pull/14689
+[#14708]: https://github.com/home-assistant/home-assistant/pull/14708
+[#14717]: https://github.com/home-assistant/home-assistant/pull/14717
+[#14719]: https://github.com/home-assistant/home-assistant/pull/14719
+[#14720]: https://github.com/home-assistant/home-assistant/pull/14720
+[#14724]: https://github.com/home-assistant/home-assistant/pull/14724
+[#14735]: https://github.com/home-assistant/home-assistant/pull/14735
+[#14738]: https://github.com/home-assistant/home-assistant/pull/14738
+[#14742]: https://github.com/home-assistant/home-assistant/pull/14742
+[#14746]: https://github.com/home-assistant/home-assistant/pull/14746
+[#14750]: https://github.com/home-assistant/home-assistant/pull/14750
+[#14760]: https://github.com/home-assistant/home-assistant/pull/14760
+[#14762]: https://github.com/home-assistant/home-assistant/pull/14762
+[#14763]: https://github.com/home-assistant/home-assistant/pull/14763
+[#14764]: https://github.com/home-assistant/home-assistant/pull/14764
+[#14765]: https://github.com/home-assistant/home-assistant/pull/14765
+[#14767]: https://github.com/home-assistant/home-assistant/pull/14767
+[#14768]: https://github.com/home-assistant/home-assistant/pull/14768
+[#14769]: https://github.com/home-assistant/home-assistant/pull/14769
+[#14770]: https://github.com/home-assistant/home-assistant/pull/14770
+[#14771]: https://github.com/home-assistant/home-assistant/pull/14771
+[#14772]: https://github.com/home-assistant/home-assistant/pull/14772
+[#14778]: https://github.com/home-assistant/home-assistant/pull/14778
+[#14785]: https://github.com/home-assistant/home-assistant/pull/14785
+[#14790]: https://github.com/home-assistant/home-assistant/pull/14790
+[#14791]: https://github.com/home-assistant/home-assistant/pull/14791
+[@Adminiuga]: https://github.com/Adminiuga
+[@Bahnburner]: https://github.com/Bahnburner
+[@Bakkoda]: https://github.com/Bakkoda
+[@Kane610]: https://github.com/Kane610
+[@Klathmon]: https://github.com/Klathmon
+[@Oro]: https://github.com/Oro
+[@SchumyHao]: https://github.com/SchumyHao
+[@amelchio]: https://github.com/amelchio
+[@andrey-git]: https://github.com/andrey-git
+[@austinlg96]: https://github.com/austinlg96
+[@awarecan]: https://github.com/awarecan
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@bastshoes]: https://github.com/bastshoes
+[@c727]: https://github.com/c727
+[@cdce8p]: https://github.com/cdce8p
+[@cgarwood]: https://github.com/cgarwood
+[@damarco]: https://github.com/damarco
+[@danielperna84]: https://github.com/danielperna84
+[@dmulcahey]: https://github.com/dmulcahey
+[@fabaff]: https://github.com/fabaff
+[@glenn20]: https://github.com/glenn20
+[@guillaume1410]: https://github.com/guillaume1410
+[@heinemml]: https://github.com/heinemml
+[@iMicknl]: https://github.com/iMicknl
+[@ileler]: https://github.com/ileler
+[@jaypikay]: https://github.com/jaypikay
+[@jwood55812]: https://github.com/jwood55812
+[@koreth]: https://github.com/koreth
+[@kotlarz]: https://github.com/kotlarz
+[@lorenzschmid]: https://github.com/lorenzschmid
+[@mammuth]: https://github.com/mammuth
+[@michaelarnauts]: https://github.com/michaelarnauts
+[@michaeldavie]: https://github.com/michaeldavie
+[@mjg59]: https://github.com/mjg59
+[@mxworm]: https://github.com/mxworm
+[@nklever]: https://github.com/nklever
+[@pavoni]: https://github.com/pavoni
+[@ptcryan]: https://github.com/ptcryan
+[@quthla]: https://github.com/quthla
+[@raccettura]: https://github.com/raccettura
+[@rcloran]: https://github.com/rcloran
+[@robertbeal]: https://github.com/robertbeal
+[@roiff]: https://github.com/roiff
+[@scarface-4711]: https://github.com/scarface-4711
+[@schmittx]: https://github.com/schmittx
+[@syssi]: https://github.com/syssi
+[@tchellomello]: https://github.com/tchellomello
+[@titilambert]: https://github.com/titilambert
+[@treehoof]: https://github.com/treehoof
+[alarm_control_panel.manual docs]: /components/alarm_control_panel.manual/
+[alarm_control_panel.totalconnect docs]: /components/alarm_control_panel.totalconnect/
+[api docs]: /components/api/
+[automation docs]: /components/automation/
+[binary_sensor.deconz docs]: /components/binary_sensor.deconz/
+[binary_sensor.envisalink docs]: /components/binary_sensor.envisalink/
+[binary_sensor.hydrawise docs]: /components/binary_sensor.hydrawise/
+[binary_sensor.nest docs]: /components/binary_sensor.nest/
+[binary_sensor.rainmachine docs]: /components/binary_sensor.rainmachine/
+[binary_sensor.random docs]: /components/binary_sensor.random/
+[binary_sensor.xiaomi_aqara docs]: /components/binary_sensor.xiaomi_aqara/
+[binary_sensor.zha docs]: /components/binary_sensor.zha/
+[climate.homematicip_cloud docs]: /components/climate.homematicip_cloud/
+[climate.nest docs]: /components/climate.nest/
+[climate.sensibo docs]: /components/climate.sensibo/
+[cloud docs]: /components/cloud/
+[config docs]: /components/config/
+[counter docs]: /components/counter/
+[cover.myq docs]: /components/cover.myq/
+[cover.ryobi_gdo docs]: /components/cover.ryobi_gdo/
+[device_tracker docs]: /components/device_tracker/
+[eufy docs]: /components/eufy/
+[frontend docs]: /components/frontend/
+[hassio docs]: /components/hassio/
+[history docs]: /components/history/
+[homekit docs]: /components/homekit/
+[homematic docs]: /components/homematic/
+[homematicip_cloud docs]: /components/homematicip_cloud/
+[hydrawise docs]: /components/hydrawise/
+[keyboard_remote docs]: /components/keyboard_remote/
+[light.lw12wifi docs]: /components/light.lw12wifi/
+[light.nanoleaf_aurora docs]: /components/light.nanoleaf_aurora/
+[light.osramlightify docs]: /components/light.osramlightify/
+[light.zha docs]: /components/light.zha/
+[linode docs]: /components/linode/
+[lock.xiaomi_aqara docs]: /components/lock.xiaomi_aqara/
+[logbook docs]: /components/logbook/
+[media_extractor docs]: /components/media_extractor/
+[media_player.denonavr docs]: /components/media_player.denonavr/
+[media_player.directv docs]: /components/media_player.directv/
+[media_player.kodi docs]: /components/media_player.kodi/
+[media_player.philips_js docs]: /components/media_player.philips_js/
+[nest docs]: /components/nest/
+[notify docs]: /components/notify/
+[panel_custom docs]: /components/panel_custom/
+[python_script docs]: /components/python_script/
+[rainbird docs]: /components/rainbird/
+[raincloud docs]: /components/raincloud/
+[rainmachine docs]: /components/rainmachine/
+[sensor.bitcoin docs]: /components/sensor.bitcoin/
+[sensor.bom docs]: /components/sensor.bom/
+[sensor.coinmarketcap docs]: /components/sensor.coinmarketcap/
+[sensor.deconz docs]: /components/sensor.deconz/
+[sensor.gitter docs]: /components/sensor.gitter/
+[sensor.glances docs]: /components/sensor.glances/
+[sensor.homematicip_cloud docs]: /components/sensor.homematicip_cloud/
+[sensor.hydrawise docs]: /components/sensor.hydrawise/
+[sensor.iperf3 docs]: /components/sensor.iperf3/
+[sensor.luftdaten docs]: /components/sensor.luftdaten/
+[sensor.mfi docs]: /components/sensor.mfi/
+[sensor.nest docs]: /components/sensor.nest/
+[sensor.netatmo docs]: /components/sensor.netatmo/
+[sensor.netdata docs]: /components/sensor.netdata/
+[sensor.onewire docs]: /components/sensor.onewire/
+[sensor.postnl docs]: /components/sensor.postnl/
+[sensor.rainmachine docs]: /components/sensor.rainmachine/
+[sensor.random docs]: /components/sensor.random/
+[sensor.shodan docs]: /components/sensor.shodan/
+[sensor.simulated docs]: /components/sensor.simulated/
+[sensor.speedtest docs]: /components/sensor.speedtest/
+[sensor.swiss_public_transport docs]: /components/sensor.swiss_public_transport/
+[sensor.transmission docs]: /components/sensor.transmission/
+[sensor.uptime docs]: /components/sensor.uptime/
+[sensor.version docs]: /components/sensor.version/
+[sensor.worldclock docs]: /components/sensor.worldclock/
+[sensor.zha docs]: /components/sensor.zha/
+[shopping_list docs]: /components/shopping_list/
+[switch.hydrawise docs]: /components/switch.hydrawise/
+[switch.raincloud docs]: /components/switch.raincloud/
+[switch.rainmachine docs]: /components/switch.rainmachine/
+[vera docs]: /components/vera/
+[xiaomi_aqara docs]: /components/xiaomi_aqara/
+[zha docs]: /components/zha/
+[zone docs]: /components/zone/
+[zwave docs]: /components/zwave/
+[@OttoWinter]: https://github.com/OttoWinter
+[esphomeyaml]: https://esphomelib.com/esphomeyaml/index.html
+[@c727]: https://github.com/c727

source/getting-started/index.markdown

@@ -54,4 +54,8 @@ We will need a few things to get started with installing Home Assistant. Links b
 
 [local]: http://hassio.local:8123
 
+<p class='note warning'>
+When you're done, remember to set up regular backups of your configuration. This will protect you from hardware failure and mistakes. On Hass.io you have snapshots, but you can back up to [GitHub](/docs/ecosystem/backup/backup_github/), [DropBox](/docs/ecosystem/backup/backup_usb/) and many other ways. All that matters is that you set them up and test them regularly.
+</p>
+
 ### [Next step: Configuring Home Assistant &raquo;](/getting-started/configuration/)

source/help/index.markdown

@@ -31,6 +31,7 @@ Have you found an issue in your Home Assistant installation? Please report it. R
 
 ### {% linkable_title Videos, talks, workshops and alike %}
 
+- [Build your own smart home with Home Assistant](https://zmonkey.org/blog/files/Home%20Assistant%202018%20v1.0.pdf) at [OpenWest](https://openwest.org) - June 2018
 - [Automate your home with Home Assistant](https://www.youtube.com/watch?v=SSrgi4iHGbs) at [foss-north 2018](http://foss-north.se/2018/speakers-and-talks.html#jparadies) - March 2018
 - [Home Assistant](https://github.com/home-assistant/home-assistant-assets/tree/master/english/2017-qecampX) at QECampX 2017 - October 2017
 - [Open Source Heimautomation mit Home Assistant](https://github.com/home-assistant/home-assistant-assets/tree/master/german/2017-maker-faire-zurich) at [Mini Maker Faire Zurich 2017](https://www.makerfairezurich.ch/en/) - September 2017