Merge branch 'current' into next

_config.yml

@@ -127,10 +127,10 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 38
+current_minor_version: 39
-current_patch_version: 4
+current_patch_version: 0
-date_released: 2017-02-21
+date_released: 2017-02-25
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
-patch_version_notes: "#release-0384---february-21"
+patch_version_notes: "#"

sass/custom/_paulus.scss

@@ -18,7 +18,6 @@
 }
 
 .material-card {
-  // display: inline-block;
   background-color: #fefefe;
   border-radius: 2px;
   box-shadow: 0 2px 2px 0 rgba(0,0,0,0.14),0 1px 5px 0 rgba(0,0,0,0.12),0 3px 1px -2px rgba(0,0,0,0.2);
@@ -77,6 +76,33 @@
     }
   }
 
+  .shirt-promo {
+    display: block;
+    padding-top: 30%;
+    background-image: url(/images/merchandise/shirt-frontpage.png);
+    background-size: cover;
+    background-position: center;
+    text-decoration: none;
+
+    .caption {
+      padding: 16px 12px 12px;
+      background-color: rgba(0, 0, 0, .54);
+      color: white;
+      border-bottom-left-radius: 2px;
+      border-bottom-right-radius: 2px;
+
+      .title {
+        font-size: 20px;
+        font-weight: 400;
+      }
+
+      .subtitle {
+        font-size: 12px;
+        font-weight: initial;
+      }
+    }
+  }
+
   .supported-brands {
     text-align: center;
 

source/_components/binary_sensor.enocean.markdown

@@ -13,7 +13,7 @@ ha_release: 0.21
 ha_iot_class: "Local Push"
 ---
 
-This can typically be one of those batteryless wall switches. Currently only one type has been tested: Eltako FT55. Other devices will most likely not work without changing the Home Assistant code.
+This can typically be one of those batteryless wall switches. Currently only one type has been tested: Eltako FT55 which uses the EnOcean PTM 215 module. All switches using this module are expected to work. Other devices will most likely not work without changing the Home Assistant code.
 
 To use your EnOcean device, you first have to set up your [EnOcean hub](/components/enocean/) and then add the following to your `configuration.yaml` file:
 

source/_components/lock.nuki.markdown

@@ -16,7 +16,7 @@ ha_iot_class: "Local Polling"
 
 The `nuki` platform allows you to control [Nuki Smart Locks](https://nuki.io/en/smart-lock/) via either a [software bridge](https://play.google.com/store/apps/details?id=io.nuki.bridge) or a [physical bridge](https://nuki.io/en/bridge/).
 
-To add a Nuki bridge to your installation, you need to enable developper mode on your bridge and define a port and an access token. This can be achieved using the [Android app](https://play.google.com/store/apps/details?id=io.nuki). Please note that the API token should be 6-20 characters long, even though the app allows you to set a longer one.
+To add a Nuki bridge to your installation, you need to enable developer mode on your bridge and define a port and an access token. This can be achieved using the [Android app](https://play.google.com/store/apps/details?id=io.nuki). Please note that the API token should be 6-20 characters long, even though the app allows you to set a longer one.
 Then add the following to your `configuration.yaml` file:
 
 ```yaml

source/_components/mqtt.markdown

@@ -16,7 +16,7 @@ ha_iot_class: depends
 
 MQTT (aka MQ Telemetry Transport) is a machine-to-machine or "Internet of Things" connectivity protocol on top of TCP/IP. It allows extremely lightweight publish/subscribe messaging transport.
 
-Your first step to get MQTT and Home Assistant working is the choose a [broker](/docs/mqtt/broker).
+Your first step to get MQTT and Home Assistant working is to choose a [broker](/docs/mqtt/broker).
 
 To integrate MQTT into Home Assistant, add the following section to your `configuration.yaml` file. Keep in mind that the minimal setup will run with [an embedded MQTT broker](/docs/mqtt/broker#embedded-broker):
 

source/_components/sensor.broadlink.markdown

@@ -19,7 +19,7 @@ To enable it, add the following lines to your `configuration.yaml`:
 
 ```yaml
 # Example configuration.yaml entry
-switch:
+sensor:
   - platform: broadlink
     host: IP_ADDRESS
     mac: 'MAC_ADDRESS'

source/_cookbook/configuration_yaml_by_aneisch

@@ -0,0 +1,13 @@
+---
+layout: page
+title: "Configuration.yaml by aneisch"
+description: ""
+date: 2017-2-23 20:27
+sidebar: true
+comments: false
+sharing: true
+footer: true
+ha_category: Example configuration.yaml
+ha_external_link: https://github.com/aneisch/home-assistant/
+---
+

source/_cookbook/turn_on_light_for_10_minutes_when_motion_detected.markdown

@@ -16,37 +16,23 @@ This recipe will turn on a light when there is motion and turn off the light whe
 
 ```yaml
 automation:
-  alias: Turn on kitchen lights when there is movement
+- alias: Turn on kitchen light when there is movement
   trigger:
-    - platform: state
+    platform: state
-      entity_id: sensor.motion_sensor
+    entity_id: sensor.motion_sensor
-      to: 'on'
+    to: 'on'
   action:
     service: homeassistant.turn_on
-    entity_id: script.timed_lamp
+    entity_id: light.kitchen
 
-script:
+- alias: Turn off kitchen light 10 minutes after last movement
-  timed_lamp:
+  trigger:
-    alias: "Turn on lamp and set timer"
+    platform: state
-    sequence:
+    entity_id: sensor.motion_sensor
-      # Cancel ev. old timers
+    to: 'off'
-      - service: script.turn_off
+    for:
-        data:
+      minutes: 10
-           entity_id: script.timer_off
+  action:
-      - service: light.turn_on
+    service: homeassistant.turn_off
-        data:
+    entity_id: light.kitchen_light
-          entity_id: light.kitchen
-      # Set new timer
-      - service: script.turn_on
-        data:
-          entity_id: script.timer_off
-
-  timer_off:
-    alias: "Turn off lamp after 10 minutes"
-    sequence:
-      - delay:
-          minutes: 10
-      - service: light.turn_off
-        data:
-          entity_id: light.kitchen
 ```

source/_docs/automation.markdown

@@ -9,7 +9,7 @@ sharing: true
 footer: true
 ---
 
-Home Assistant offers a wide range of automation configurations. In this section, we'll try to guide you through all the different possibilities and options. Besides this documentation, there are also a couple of people who have made their automations [publicly available][/cookbook/#example-configurationyaml].
+Home Assistant offers a wide range of automation configurations. In this section, we'll try to guide you through all the different possibilities and options. Besides this documentation, there are also a couple of people who have made their automations [publicly available](/cookbook/#example-configurationyaml).
 
 ### {% linkable_title Automation basics %}
 

source/_docs/configuration/customizing-devices.markdown

@@ -33,6 +33,13 @@ homeassistant:
       icon: mdi:kettle
     switch.rfxtrx_switch:
       assumed_state: false
+  customize_domain:
+    light:
+      icon: mdi:home
+  customize_glob:
+    "light.kitchen_*":
+      icon: mid:description
+
 ```
 
 ### {% linkable_title Possible values %}

source/_docs/configuration/splitting_configuration.markdown

@@ -7,7 +7,7 @@ sidebar: true
 comments: false
 sharing: true
 footer: true
-redirect_from: /getting-started/yaml/
+redirect_from: /topics/splitting_configuration/
 ---
 
 So you've been using Home Assistant for a while now and your [configuration.yaml file brings people to tears](https://home-assistant.io/cookbook/configuration_yaml_from_bassclarinetl2/) or you simply want to start off with the distributed approach, here's how to "split the configuration.yaml" into more manageable (read: humanly readable) pieces.

source/_docs/frontend/webserver.markdown

@@ -10,11 +10,11 @@ footer: true
 redirect_from: /details/webserver/
 ---
 
-It was only a matter of time till the first queries for tools like [https://www.shodan.io](https://www.shodan.io/search?query=Home+Assistant) to search for Home Assistant instances showed up.
+It was only a matter of time until the first queries for tools like [https://www.shodan.io](https://www.shodan.io/search?query=Home+Assistant) to search for Home Assistant instances showed up.
 
-To get an idea about how your Home Assistant instance looks like for network scanner, you can use `nmap`. The `nmap` tool is already available if you are using the [nmap device tracker](/components/device_tracker/). 
+To get an idea about how your Home Assistant instance looks to a network scanner, you can use `nmap`. The `nmap` tool is already available if you are using the [nmap device tracker](/components/device_tracker/). 
 
-```yaml
+```bash
 $ nmap -sV -p 8123 --script=http-title,http-headers 192.168.1.3
 
 Starting Nmap 7.12 ( https://nmap.org ) at 2016-10-06 10:01 CEST

source/_docs/installation/docker.markdown

@@ -28,6 +28,35 @@ Additionally, if your expectation is that you will be able to browse directly to
 $ docker run -d --name="home-assistant" -v /path/to/your/config:/config -e "TZ=America/Los_Angeles" -p 8123:8123 homeassistant/home-assistant
 ```
 
+### {% linkable_title Windows %}
+
+When running Home Assistant in Docker on Windows, you may have some difficulty getting ports to map for routing (since the `--net=host` switch actually applies to the hypervisor's network interface). To get around this, you will need to add port proxy ipv4 rules to your local Windows machine, like so (Replacing '192.168.1.10' with whatever your Windows IP is, and '10.0.50.2' with whatever your Docker container's IP is):
+```
+netsh interface portproxy add v4tov4 listenaddress=192.168.1.10 listenport=8123 connectaddress=10.0.50.2 connectport=8123
+netsh interface portproxy add v4tov4 listenaddress=0.0.0.0 listenport=8123 connectaddress=10.0.50.2 connectport=8123
+```
+
+This will let you access your Home Assistant portal from http://localhost:8123, and if you forward port 8123 on your router to your machine IP, the traffic will be forwarded on through to the docker container.
+
+### {% linkable_title Synology NAS %}
+
+As Synology within DSM now supports Docker (with a neat UI), you can simply install Home Assistant using docker without the need for command-line. For details about the package (including compatability-information, if your NAS is supported), see https://www.synology.com/en-us/dsm/app_packages/Docker
+
+The steps would be:
+* Install "Docker" package on your Synology NAS
+* Launch Docker-app and move to "Registry"-section
+* Find "homeassistant/home-assistant" with registry and click on "Download"
+* Wait for some time until your NAS has pulled the image
+* Move to the "Image"-section of the Docker-app
+* Click on "Launch"
+* Choose a container-name you want (e.g. "homeassistant")
+* Click on "Advanced Settings"
+* Set "Enable auto-restart" if you like
+* Within "Volume" click on "Add Folder" and choose either an existing folder or add a new folder. The "mount point" has to be "/config", so that Home Assistant will use it for the configs and logs.
+* Confirm the "Advanced Settings"
+* Click on "Next" and then "Apply"
+* Your Home Assistant within Docker should now run :)
+
 ### {% linkable_title Restart %}
 
 This will launch Home Assistant and serve the web interface from port 8123 on your Docker host.

source/_docs/installation/synology.markdown

@@ -10,6 +10,13 @@ footer: true
 redirect_from: /getting-started/installation-synology/
 ---
 
+There are 2 alternatives, when using Home Assistant on Synology NAS:
+1. using Docker
+2. directly running on DSM
+
+Option 1 is described on the [Docker installation page](/docs/installation/docker/), whereas Option 2 is described below.
+
+
 The following configuration has been tested on Synology 413j running DSM 6.0-7321 Update 1.
 
 Running these commands will:
@@ -35,27 +42,28 @@ $ sudo -i
 Check the path to python3 (assumed to be /volume1/@appstore/py3k/usr/local/bin)
 
 ```bash
-$ cd /volume1/@appstore/py3k/usr/local/bin
+# cd /volume1/@appstore/py3k/usr/local/bin
 ```
 
 Install PIP (Python's package management system)
 
 ```bash
-$ ./python3 -m ensurepip
+# ./python3 -m ensurepip
 ```
 
 Use PIP to install Homeassistant package
 
 ```bash
-$ ./python3 -m pip install homeassistant
+# ./python3 -m pip install homeassistant
 ```
 
 Create homeassistant config directory & switch to it
 
 ```bash
-$ mkdir /volume1/homeassistant
+# mkdir /volume1/homeassistant
-$ cd /volume1/homeassistant
+# cd /volume1/homeassistant
 ```
+Hint: alternatively you can also create a "Shared Folder" via Synology WebUI (e.g. via "File Station") - this has the advantage that the folder is visible via "File Station".
 
 Create hass-daemon file using the following code (edit the variables in uppercase if necessary)
 
@@ -167,21 +175,21 @@ esac
 Create links to python folders to make things easier in the future:
 
 ```bash
-$ ln -s /volume1/@appstore/py3k/usr/local/bin python3
+# ln -s /volume1/@appstore/py3k/usr/local/bin python3
-$ ln -s /volume1/@appstore/py3k/usr/local/lib/python3.5/site-packages/homeassistant
+# ln -s /volume1/@appstore/py3k/usr/local/lib/python3.5/site-packages/homeassistant
 ```
 
 Set the owner and permissions on your config folder
 
 ```bash
-$ chown -R homeassistant:users /volume1/homeassistant
+# chown -R homeassistant:users /volume1/homeassistant
-$ chmod -R 664 /volume1/homeassistant
+# chmod -R 664 /volume1/homeassistant
 ```
 
 Make the daemon file executable:
 
 ```bash
-$ chmod 777 /volume1/homeassistant/hass-daemon
+# chmod 777 /volume1/homeassistant/hass-daemon
 ```
 
 Update your firewall (if it is turned on on the Synology device):

source/_docs/installation/updating.markdown

@@ -7,7 +7,7 @@ sidebar: true
 comments: false
 sharing: true
 footer: true
-redirect_from: /getting-started/hassbian-upgrading/
+redirect_from: /getting-started/updating/
 ---
 
 <p class='note warning'>

source/_docs/mqtt/birth_will.markdown

@@ -10,7 +10,7 @@ footer: true
 logo: mqtt.png
 ---
 
-MQTT support so-called Birth and Last Will and Testament (LWT) messages. The former is used to sned a message after the service has started. the latter is here to notify other clients about an ungracefully disconnected client or alike.
+MQTT supports so-called Birth and Last Will and Testament (LWT) messages. The former is used to send a message after the service has started, and the latter is used to notify other clients about an ungracefully disconnected client.
 
 To integrate MQTT Birth and Last Will messages into Home Assistant, add the following section to your `configuration.yaml` file:
 
@@ -37,4 +37,3 @@ Configuration variables:
   - **payload** (*Required*): The message content.
   - **qos** (*Optional*): The maximum QoS level of the topic. Default is 0.
   - **retain** (*Optional*): If the published message should have the retain flag on or not. Defaults to `True`.
-

source/_docs/mqtt/discovery.markdown

@@ -44,12 +44,12 @@ A motion detection device which can be represented by a [binary sensor](/compone
 
 - Configuration topic: `homeassistant/binary_sensor/garden/config`
 - State topic: `homeassistant/binary_sensor/garden/state`
-- Payload:  `{"name": "garden", "sensor_class": "motion"}`
+- Payload:  `{"name": "garden", "device_class": "motion"}`
 
 To create a new sensor manually. For more details please refer to the [MQTT testing section](/component/mqtt_testing).
 
 ```bash
-$ mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/binary_sensor/garden/config" -m '{"name": "garden", "sensor_class": "motion"}'
+$ mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/binary_sensor/garden/config" -m '{"name": "garden", "device_class": "motion"}'
 ```
 Update the state.
 

source/_posts/2017-02-25-config-panel-and-state-restoration.markdown

@@ -0,0 +1,297 @@
+---
+layout: post
+title: "0.39: Configuration panel, state restoration and improved docs"
+description: "0.39 is by far our best release yet."
+date: 2017-02-25 08:04:05 +0000
+date_formatted: "February 25, 2017"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2017-02-0.39/social.png
+---
+
+It's time for 0.39 and this release has some amazing new features!
+
+<a href='/components/#added_in_current_version'><img src='/images/blog/2017-02-0.39/social.png' style='border: 0;box-shadow: none;'></a>
+
+## T-Shirts
+
+First off, in case you haven't seen it yet: [we have t-shirts][t-shirt] now and they are beautiful. All proceeds from the shirts will be donated to the Electronic Frontier Foundation. The first three days all of you have already raised $400! Still waiting for Teespring to get back to me so stay tuned for the EU store.
+
+## Configuration panel
+
+Yep, you read that right. We have a configuration panel. It's just the first of many small steps. Putting in a foundation is important and gives us something to iterate on.
+
+To start, we have three simple configuration panels:
+
+ - Core: allows you to validate config, reload core/group/automation config and restart/stop Home Assistant
+ - Group: allows you to rename groups, change type between group/view and reorder entities.
+ - Z-Wave: allows you to set device specific configuration settings
+
+<p class='img'>
+  <img src='/images/blog/2017-02-0.39/config.png'>
+  Screenshot of our new configuration panel.
+</p>
+
+As a security measure, the configuration panel will need to be activated in the config file to be activated. This can be done by adding the following to your `configuration.yaml`:
+
+```yaml
+config:
+```
+
+Using our configuration panels will require you to structure your groups and Z-Wave device config according to how the configuration panel expects it. This is on purpose as it we will not be aiming to build a system that supports both our extended set of configuration extend hooks and our configuration panels. It's one or the other.
+
+To activate them in your config, create empty files `groups.yaml` and `zwave_device_config.yaml` in your config dir and add the following entries to your config:
+
+```yaml
+groups: !include groups.yaml
+
+zwave:
+  device_config: !include zwave_device_config.yaml
+```
+
+_Note that this is the first release. Things will be missing, things might be broken._
+
+## Reorganized documentation
+
+Thanks to [Fabian][@fabaff] we have a great re-organized documentation. Is it perfect yet? No. But we are getting close. We put a lot of focus on making sure the Raspberry Pi is the main focus of our getting started. The other instructions are still available, just not as part of the main getting started.
+
+## State restoration
+
+Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don't worry any longer. [Johann][@kellerza] has added the foundation for state restoration to Home Assistant. For the initial release support has been added to to `input_select` and `input_boolean` components. We will be adding this to more integrations in the future.
+
+## Breaking changes to customize and Z-Wave "customize"
+
+A couple of releases ago we introduced a new way of doing `customize`. It became a list that allowed different ways of matching the config to the entity.
+
+We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn't like config panels?
+
+So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.
+
+#### Customize has been reverted to it's original config
+
+The old customize is back. The options to match by domain or using glob have been moved to it's own options. It will now look like this:
+
+```yaml
+homeassistant:
+  customize:
+    light.kitchen:
+      hidden: true
+  customize_domain:
+    light:
+      icon: mdi:home
+  customize_glob:
+    "light.kitchen_*":
+      icon: mid:description
+```
+
+#### Z-Wave customize is now device config
+
+Ever wondered why the Z-Wave customize was called customize? Yeah, so did we. So when migrating this to the new config format, we decided to upgrade the name too:
+
+```yaml
+zwave:
+  device_config:
+    light.kitchen:
+      ignored: true
+  device_config_domain:
+    light:
+      polling_intensity: 2
+  device_config_glob:
+    "light.kitchen_*":
+      polling_intensity: 0
+```
+
+## Speed improvements
+
+And a final shout out to [Pascal][@pvizeli]. He keeps improving the performance of components and platforms all over Home Assistant.
+
+<!--more-->
+
+## All changes
+
+#### New platforms/components
+
+- [Telegram] webhooks ([@scipioni])
+- Added [Openhome][openhome] support ([@bazwilliams])
+- [UPS][ups] sensor ([@happyleavesaoc])
+- [FEDex][fedex] sensor ([@happyleavesaoc])
+- [Gstreamer][gstreamer] media player ([@happyleavesaoc])
+- [iTach Remote][itach] Platform ([@alanfischer])
+- [myq] cover component ([@arraylabs])
+- Support for the [Open Energy Monitor Thermostat][oemt] ([@Cadair])
+- Added Fritzbox [Netmonitor][netmonitor] ([@PetePriority])
+- Add platform for [Yeelight Sunflower lights][sunflowers] ([@lindsaymarkward])
+- Support for [Pocket Casts][pocket] ([@molobrakos])
+- [VolvoOnCall][volvo] component with support for sensors, heater and lock ([@molobrakos])
+- Add [pushsafer.com][pushsafer] notification service ([@appzer])
+- [Websocket push][kodi] notifications for Kodi ([@armills])
+- New component 'insteon_plm' and related platforms ([@nugget])
+- Add [aurora][aurora] sensor ([@walkerdb])
+- Add [Ebox][ebox] sensor platform ([@titilambert])
+- Mediaplayer [clementine][clementine] remote ([@jjmontesl])
+- Add [Fido][fido] sensor ([@titilambert])
+
+#### Improvements
+
+- Tellduslive: Don't thow exception if connection to server is lost ([@molobrakos])
+- Core: Convert config.components to a set ([@balloob])
+- Media Player - Apple TV: Handle connection errors when connecting to Apple TVs, re-use aiohttp session , add fake support for turn on/off ([@postlund])
+- Zoneminder: Refactoring and JSON decode error handling ([@pschmitt])
+- Recorder: Add tests for full schema migration, limit to session scope ([@armills])
+- Tests: Add history_stats sensor ([@bokub])
+- Device tracker - Tado: Add support for multiple devices to Tado device tracker ([@markoudev])
+- Z-Wave: Fix zwave helper getter not to fail on some None results. ([@andrey-git])
+- Core: `sensor_class` migrate to `device_class` ([@armills])
+- Sensor - Amcrest: Avoid traceback for Amcrest cameras/firmware that does not have the software_information API call ([@tchellomello])
+- Media Player - MPD: Adds play URL support to mpd ([@jjmontesl])
+- Logbook: Component set add using OR ([@kellerza])
+- Config: Add config component and hassbian example panel ([@balloob])
+- Proximity: Fixed proximity zone incorrectly using name instead of zone setting ([@jjmontesl])
+- Z-Wave: Add device_class support to cover component ([@armills])
+- Config: Add check_config API ([@balloob])
+- Media player: Add media_image to media_player component ([@postlund])
+- Sensor- Vasttrafik.py: vasttrafik: update token on read error ([@persandstrom])
+- Z-Wave.py: force_update zwave sensors ([@andrey-git])
+- Core: Two stage shutdown ([@pvizeli])
+- Z-Wave: Rename customize to device_config ([@balloob])
+- Thingspeak: Use the correct API key ([@fabaff])
+- Lock - Nuki: Reduce battery drain on Nuki Lock ([@pschmitt])
+- Notify - Webostv: Only try to pair notify.webostv when not paired ([@andersonshatch])
+- KNX: Fix slow status updates from the knx bus ([@keerts])
+- HDMI CEC: HDMI_CEC customization [Breaking change] ([@balloob], [@andrey-git])
+- Sensor - Moon: Remove unit of measurement ([@fabaff])
+- Z-Wave: Add initial Z-Wave config panel ([@balloob])
+- History: Allow printing the number of states returned by history and time it took to extract and add day ([@andrey-git])
+- MQTT: Enable sensor for discovery ([@fabaff])
+- Light - Limitlessled: Added limitlessled support for bridge v6 and RGBWW bulbs. ([@soldag])
+- Config - Hassbian: Update hassbian component with real output ([@balloob])
+- Media Player -Sonos: Bugfix sonos favorite_source after lost connection ([@pvizeli])
+- Sensor - SenseHAT: Add flag to declare if SenseHAT is attached  ([@nodinosaur])
+- RFLink: Reconnect robustness, expose connection state. ([@aequitas])
+- Media player - CMUS: Remove IO from properties ([@armills])
+- Light - Litejet: Lights should have the option to dim in the UI. ([@joncar])
+- Light - Hue: Add effect_list to hue light ([@armills])
+- Meida player - Liveboxplaytv: Update liveboxplaytv and catch connection errors ([@pschmitt])
+- Llight - Lifx: Fix colortemp conversion for lifx lights ([@kitcorey])
+- Light - Flux_LED: Update FLUX_LED by adding Effects ([@dramamoose])
+- Alarm control panel - Simplisafe: SimpliSafe updates ([@w1ll1am23])
+- Cover Add supported_features to cover component ([@armills])
+- Wink: Added tamper detection to Wink devices. ([@w1ll1am23])
+- Sensor - onewire: Add support for aliased owfs sensors ([@normakm])
+- Weather: Forecast ([@Tommatheussen])
+- Device tracker - ASUSwrt: Added support for alternate SSH ports in AsusWRT ([@swbradshaw])
+- Zoneminder: Add camera mjpeg stream support ([@mnoorenberghe])
+- Restore: Restore_state helper to restore entity states from the DB on startup ([@kellerza])
+- Sensor - Darksky: Add 'entity_picture' to Darksky component ([@aronsky])
+- Media Player - Samsungtv: Add support for waking up Samsung TVs over the network ([@justin8])
+- MQTT: Convert MQTT platforms to async ([@pvizeli])
+- tests/components/device_tracker/test_init.py: Restore for device_tracker ([@kellerza])
+- Discovery: Make it possible to ignore platforms in discovery ([@postlund])
+- Image processing: Add `device_class` ([@pvizeli])
+
+#### Breaking changes
+ - VolvoOnCall has been extended with more features and had to be converted to a component
+ - Limitlessled support for Bridge v6 and RGBWW bulbs require users to specify `version` and `port
+ - hdmi_cec config now requires users to set the types in the hdmi_cec config instead of using `customize`:
+
+```yaml
+hdmi_cec:
+  types:
+    hdmi_cec.hdmi_5: media_player
+```
+
+#### Bugfixes: 
+[@pvizeli], [@LinuxChristian], [@molobrakos], [@balloob], [@rytilahti], [@fabaff], [@andrey-git], [@aequitas], [@konikvranik], [@Danielhiversen], [@colinodell], [@pschmitt], [@bachp], [@bachp],[@w1ll1am23], [@valentinalexeev], [@robbiet480], [@MartinHjelmare], [@happyleavesaoc], [@tdickman], [@arraylabs], [@lwis], [@titilambert]
+
+### If you need help...
+...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+
+### Reporting Issues
+Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
+
+[@turbokongen]: https://github.com/turbokongen
+[@w1ll1am23]: https://github.com/w1ll1am23
+[@nugget]: https://github.com/nugget
+[@PetePriority]: https://github.com/PetePriority
+[@dramamoose]: https://github.com/dramamoose
+[@fabaff]: https://github.com/fabaff
+[@joncar]: https://github.com/joncar
+[@alanfischer]: https://github.com/alanfischer
+[@LinuxChristian]: https://github.com/LinuxChristian
+[@justin8]: https://github.com/justin8
+[@jjmontesl]: https://github.com/jjmontesl
+[@tdickman]: https://github.com/tdickman
+[@Danielhiversen]: https://github.com/Danielhiversen
+[@pavoni]: https://github.com/pavoni
+[@Tommatheussen]: https://github.com/Tommatheussen
+[@pvizeli]: https://github.com/pvizeli
+[@keerts]: https://github.com/keerts
+[@arraylabs]: https://github.com/arraylabs
+[@soldag]: https://github.com/soldag
+[@walkerdb]: https://github.com/walkerdb
+[@kellerza]: https://github.com/kellerza
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[@bazwilliams]: https://github.com/bazwilliams
+[@appzer]: https://github.com/appzer
+[@tchellomello]: https://github.com/tchellomello
+[@aronsky]: https://github.com/aronsky
+[@swbradshaw]: https://github.com/swbradshaw
+[@colinodell]: https://github.com/colinodell
+[@nodinosaur]: https://github.com/nodinosaur
+[@happyleavesaoc]: https://github.com/happyleavesaoc
+[@bokub]: https://github.com/bokub
+[@markoudev]: https://github.com/markoudev
+[@titilambert]: https://github.com/titilambert
+[@aequitas]: https://github.com/aequitas
+[@mnoorenberghe]: https://github.com/mnoorenberghe
+[@Cadair]: https://github.com/Cadair
+[@postlund]: https://github.com/postlund
+[@konikvranik]: https://github.com/konikvranik
+[@scipioni]: https://github.com/scipioni
+[@andrey-git]: https://github.com/andrey-git
+[@persandstrom]: https://github.com/persandstrom
+[@lwis]: https://github.com/lwis
+[@balloob]: https://github.com/balloob
+[@bachp]: https://github.com/bachp
+[@robbiet480]: https://github.com/robbiet480
+[@lindsaymarkward]: https://github.com/lindsaymarkward
+[@valentinalexeev]: https://github.com/valentinalexeev
+[@armills]: https://github.com/armills
+[@molobrakos]: https://github.com/molobrakos
+[@normakm]: https://github.com/normakm
+[@rytilahti]: https://github.com/rytilahti
+[@pschmitt]: https://github.com/pschmitt
+[@kitcorey]: https://github.com/kitcorey
+[@andersonshatch]: https://github.com/andersonshatch
+
+[telegram]: https://home-assistant.io/componet/telegram_webhook/
+[pushsafer]: https://home-assistant.io/components/notify.pushsafer/
+[openhome]: https://home-assistant.io/components/media_player.openhome/
+[ups]: https://home-assistant.io/components/sensor.ups/
+[fedex]: https://home-assistant.io/components/sensor.fedex/
+[fido]: https://home-assistant.io/components/sensor.fido/ 
+[gstreamer]: https://home-assistant.io/components/media_player.gstreamer/
+[clementine]: https://home-assistant.io/components/media_player.clementine/
+[ebox]: https://home-assistant.io/components/sensor.ebox/
+[aurora]: https://home-assistant.io/components/binary_sensor.aurora/
+[netmonitor]: https://home-assistant.io/components/sensor.fritzbox_netmonitor/
+[itach]: https://home-assistant.io/components/remote.itach/
+[sunflowers]: https://home-assistant.io/components/light.yeelight-sunflower
+[kodi]: https://home-assistant.io/components/media_player.kodi/
+[myq]: https://home-assistant.io/components/cover.myq/
+[oemt]: https://home-assistant.io/components/climate.oem/
+[volvo]: https://home-assistant.io/components/volvooncall/
+[pocket]: https://home-assistant.io/components/sensor.pocketcasts/
+[config]: https://home-assistant.io/components/config/
+
+
+[docs]: https://home-assistant.io/docs/
+[getting-started]: https://home-assistant.io/getting-started/
+[docs-issue]: https://github.com/home-assistant/home-assistant.github.io/issues/1603
+
+[forum]: https://community.home-assistant.io/
+[gitter]: https://gitter.im/home-assistant/home-assistant
+[issue]: https://github.com/home-assistant/home-assistant/issues
+[t-shirt]: https://home-assistant.io/blog/2017/02/22/home-assistant-tshirts-have-arrived/

source/developers/development_testing.markdown

@@ -62,3 +62,7 @@ The `flake8-docstrings` extension will check docstrings according to [PEP257](ht
 ### {% linkable_title Notes on PyLint and PEP8 validation %}
 
 If you can't avoid a PyLint warning, add a comment to disable the PyLint check for that line with `# pylint: disable=YOUR-ERROR-NAME`. An example of an unavoidable PyLint warning is not using the passed-in datetime if you're listening for a time change.
+
+### {% linkable_title Maximum Line Length %}
+
+As part of the linting process, all code is checked for a maximum line length of 79 characters. This comes directly from the [PEP8 style guide](https://www.python.org/dev/peps/pep-0008/#maximum-line-length), and is also used by the Python standard library. All code must pass these linting checks, and no exceptions will be made. There have already been numerous requests to increase the maximum line length, but after evaluating the options, the Home Assistant maintainers have decided to stay at 79 characters. This decision is final.

source/index.html

@@ -47,6 +47,17 @@ hide_github_edit: true
           </li>
         {% endfor %}
       </div>
+
+      <a class='material-card shirt-promo' href='/blog/2017/02/22/home-assistant-tshirts-have-arrived/'>
+        <div class='caption'>
+          <div class='title'>
+            Join the Home Assistant t-shirt revolution!
+          </div>
+          <div class='subtitle'>
+            All proceeds will be donated to the Electronic Frontier Foundation.
+          </div>
+        </div>
+      </a>
     </div>
   </div>