We reached another milestone aka number: 10000. GitHub is assigning numbers to pull requests and issues and the “10000” is a PR. Our ratio is around 1/3 issues and 2/3 pull requests. To be more precise: 64% pull requests and 36% issues.
+
+
If you haven’t noticed, there is now a glossary that collects some Home Assistant relevant terms. Talking about the documentation: @DubhAd rewrote large parts of the Z-Wave section. More structure to get started and to find details during the setup and the configuration.
+
+
Google Assistant / Google Home integration
+
This release includes a new component to integrate Home Assistant with Google Assistant by Phil Kates. We integrate via the Smart Home API, this means that you will be able to control your devices in Home Assistant via any device that has Google Assistant. Learn more in the documentation.
+
+
Hacktoberfest
+
Hacktoberfest is still on and so far we have received a lot improvements. We can’t make any promises to review everything by the end of October, but we are trying to make sure that you will get your t-shirt.
+
+
Map
+
The map is now its own component. Similar to configuration (config:), it will not show up without adding it to your configuration.yaml file.
+
+
map:
+
+
+
+
Travis CI
+
Why not observe your Travis CI jobs with Home Assistant? @tchellomello created a Travis CI sensor which allows one to check on the current state of Travis jobs. Now you can make sure that the coffee is ready when the build passed.
…don’t hesitate to use our very active forums or join us for a little chat. 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. Make sure to fill in all fields of the issue template.
Beside the improved Wink support which was contributed by @w1ll1am23, ships this release a wide variety of new components and platforms. The input_slider components has received a makeover by @BioSehnsucht and is now input_number. @tinloaf added a feature that allows you to enter dates: input_datetime. Both will help you to improve your automation rules.
DuckDNS
-
Using Home Assistant with DuckDNS for Dynamic DNS (DDNS or DynDNS) is an old story. DuckDNS is also integrated in Hass.io. 0.55 ships a component for no Hass.io users to get a similar feature.
+
Using Home Assistant with DuckDNS for Dynamic DNS (DDNS or DynDNS) is an old story. DuckDNS is also integrated in Hass.io. 0.55 ships a component for non Hass.io users to get a similar feature.
Recorder
-
The purging of data was improved. With purge_interval you can schedule regular purges of older events and states. In combination you can specify with purge_keep_days the amount of days you want to keep. The new service recorder.purge allow to handle this task when needed.
+
The purging of data was improved. With purge_interval you can schedule regular purges of older events and states. In combination you can specify with purge_keep_days the amount of days you want to keep. The new service recorder.purge allows you to handle this task when needed.
Owntracks
Owntracks is an easy way to track your devices. For some times we have the device tracker which depends on MQTT but thanks to a new feature in Owntracks we can now offer support for HTTP. The new platform doesn’t require a MQTT broker but sends messages directly as HTTP requests to Home Assistant.
@@ -255,7 +471,7 @@
If you’re on Windows, you’re fine as our minimum version for Windows has been 3.5 for a while now.
Other Debian based systems
-
If you’re running a Debian based system , follow these instructions to upgrade.
+
If you’re running a Debian based system, follow these instructions to upgrade.
]]>
@@ -1734,18 +1950,6 @@ Screenshot of a green dashboard
-]]>
-
-
-
-
-
- 2017-07-05T00:01:00+00:00
- https://home-assistant.io/blog/2017/07/05/hasspodcast-ep-3
- The third episode of the Home Assistant Podcast is out. Paulus joins to talk about some stats and the release of 0.47 and Petar tells all about his Floorplan project for Home Assistant.
-
-
diff --git a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
index c3fbfb11bf..d309d6d709 100644
--- a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
+++ b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
@@ -24,7 +24,7 @@
-
+
@@ -162,6 +162,9 @@ This article will try to explain how they all relate.
diff --git a/blog/2015/02/08/looking-at-the-past/index.html b/blog/2015/02/08/looking-at-the-past/index.html
index 8110213b33..73e1a37c47 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -24,7 +24,7 @@
-
+
@@ -150,6 +150,9 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D
diff --git a/blog/2015/03/08/new-logo/index.html b/blog/2015/03/08/new-logo/index.html
index 93413a38f5..f9e10a6de2 100644
--- a/blog/2015/03/08/new-logo/index.html
+++ b/blog/2015/03/08/new-logo/index.html
@@ -24,7 +24,7 @@
-
+
@@ -133,6 +133,9 @@ The old logo, the new detailed logo and the new simple logo.
diff --git a/blog/2015/03/11/release-notes/index.html b/blog/2015/03/11/release-notes/index.html
index f9ba85b11d..1ff491e96c 100644
--- a/blog/2015/03/11/release-notes/index.html
+++ b/blog/2015/03/11/release-notes/index.html
@@ -24,7 +24,7 @@
-
+
@@ -158,6 +158,9 @@ An initial version of voice control for Home Assistant has landed. The current i
diff --git a/blog/2015/03/22/release-notes/index.html b/blog/2015/03/22/release-notes/index.html
index 916d97f109..e0a991fd06 100644
--- a/blog/2015/03/22/release-notes/index.html
+++ b/blog/2015/03/22/release-notes/index.html
@@ -24,7 +24,7 @@
-
+
@@ -194,6 +194,9 @@ I (Paulus) have contributed a scene component. A user can create scenes that cap
diff --git a/blog/2015/05/14/release-notes/index.html b/blog/2015/05/14/release-notes/index.html
index 8d6487c925..ace76b2e09 100644
--- a/blog/2015/05/14/release-notes/index.html
+++ b/blog/2015/05/14/release-notes/index.html
@@ -24,7 +24,7 @@
-
+
@@ -216,6 +216,9 @@ Before diving into the newly supported devices and services, I want to highlight
diff --git a/blog/2015/06/10/release-notes/index.html b/blog/2015/06/10/release-notes/index.html
index 29afa04430..c221c325e0 100644
--- a/blog/2015/06/10/release-notes/index.html
+++ b/blog/2015/06/10/release-notes/index.html
@@ -24,7 +24,7 @@
-
+
@@ -262,6 +262,9 @@ This switch platform allows you to control your motion detection setting on your
diff --git a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
index 8cf7f6a32d..da5f4e5cad 100644
--- a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
+++ b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
@@ -24,7 +24,7 @@
-
+
@@ -226,6 +226,9 @@ Fabian has added support for Forecast.io to g
diff --git a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
index 147325173d..cea42b23f2 100644
--- a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
+++ b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
@@ -24,7 +24,7 @@
-
+
@@ -209,6 +209,9 @@ Support for Temper temperature sensors has been contributed by
diff --git a/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html b/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
index ca6bed5d1f..002ca30918 100644
--- a/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
+++ b/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
@@ -23,7 +23,7 @@
-
+
@@ -246,6 +246,9 @@ The automation and script syntax here is using a deprecated and no longer suppor
diff --git a/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html b/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html
index 02d47e4851..f43196bfa3 100644
--- a/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html
+++ b/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html
@@ -24,7 +24,7 @@
-
+
@@ -169,6 +169,9 @@ Automation has gotten a lot of love. It now supports conditions, multiple trigge
diff --git a/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html b/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
index 00f75a30fa..f7ec7d0b16 100644
--- a/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
+++ b/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
@@ -24,7 +24,7 @@
-
+
@@ -152,6 +152,9 @@ Map in Home Assistant showing two people and three zones (home, school, work)
diff --git a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
index 451d6599cc..0affbff099 100644
--- a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
+++ b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
@@ -24,7 +24,7 @@
-
+
@@ -337,6 +337,9 @@ Home Assistant will keep track of historical values and allow you to integrate i
diff --git a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
index e58ea019bf..bced9bc996 100644
--- a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
+++ b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
@@ -24,7 +24,7 @@
-
+
@@ -159,6 +159,9 @@ This makes more sense as most people run Home Assistant as a daemon
diff --git a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
index 2cc898e619..9d8358d4c9 100644
--- a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
+++ b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
@@ -23,7 +23,7 @@
-
+
@@ -164,6 +164,9 @@ This is where we’ll configure our task, so select the plus icon to select an a
diff --git a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
index ba3d17afdb..3e397989c8 100644
--- a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
+++ b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
@@ -24,7 +24,7 @@
-
+
@@ -161,6 +161,9 @@ Example of the new views in the frontend. Learn mor
diff --git a/blog/2016/02/20/community-highlights/index.html b/blog/2016/02/20/community-highlights/index.html
index b266b10747..fb71502d1b 100644
--- a/blog/2016/02/20/community-highlights/index.html
+++ b/blog/2016/02/20/community-highlights/index.html
@@ -24,7 +24,7 @@
-
+
@@ -163,6 +163,9 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
diff --git a/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html b/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
index a6e30293b3..01b6356041 100644
--- a/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
+++ b/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
@@ -24,7 +24,7 @@
-
+
@@ -208,6 +208,9 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
diff --git a/blog/2016/07/06/pocketchip-running-home-assistant/index.html b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
index 82e477ba14..19c789babc 100644
--- a/blog/2016/07/06/pocketchip-running-home-assistant/index.html
+++ b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
@@ -24,7 +24,7 @@
-
+
@@ -161,6 +161,9 @@ Over a year ago I participated in the
diff --git a/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html b/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
index 451c79e8ff..b6b1999722 100644
--- a/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
+++ b/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
@@ -23,7 +23,7 @@
-
+
@@ -171,6 +171,9 @@ One of the graphs created with this tutorial.
diff --git a/blog/2016/07/28/esp8266-and-micropython-part1/index.html b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
index 2b2f1c11ee..56d68f59f6 100644
--- a/blog/2016/07/28/esp8266-and-micropython-part1/index.html
+++ b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
@@ -23,7 +23,7 @@
-
+
@@ -251,6 +251,9 @@ If a module is missing then you need to download it from the
diff --git a/blog/2017/02/03/babyphone/index.html b/blog/2017/02/03/babyphone/index.html
index fad545d436..8860c29b0d 100644
--- a/blog/2017/02/03/babyphone/index.html
+++ b/blog/2017/02/03/babyphone/index.html
@@ -23,7 +23,7 @@
-
+
@@ -240,6 +240,9 @@ We change the platform name for binary sensor in 0.38 from
diff --git a/blog/2017/03/11/repurpose-any-android-phone-as-ip-camera/index.html b/blog/2017/03/11/repurpose-any-android-phone-as-ip-camera/index.html
index 2712a36fb3..3f3f642762 100644
--- a/blog/2017/03/11/repurpose-any-android-phone-as-ip-camera/index.html
+++ b/blog/2017/03/11/repurpose-any-android-phone-as-ip-camera/index.html
@@ -24,7 +24,7 @@
-
+
@@ -341,6 +341,9 @@ Screenshot of all the different functionality the IP webcam integration offers.
diff --git a/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html b/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html
index 5b3ccc7497..ef7c4c61bf 100644
--- a/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html
+++ b/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html
@@ -24,7 +24,7 @@
-
+
@@ -196,6 +196,9 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
diff --git a/blog/2017/04/22/ikea-tradfri-spotify/index.html b/blog/2017/04/22/ikea-tradfri-spotify/index.html
index 1bef7c09af..5e0e1ddee9 100644
--- a/blog/2017/04/22/ikea-tradfri-spotify/index.html
+++ b/blog/2017/04/22/ikea-tradfri-spotify/index.html
@@ -24,7 +24,7 @@
-
+
@@ -341,6 +341,9 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
diff --git a/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html b/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html
index 0c6820220e..c5cee4a4e0 100644
--- a/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html
+++ b/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html
@@ -24,7 +24,7 @@
-
+
@@ -289,6 +289,9 @@ If you have a security key set in your Open Z-Wave
diff --git a/blog/2017/09/16/hassbian-1.3-a-bit-of-a-stretch/index.html b/blog/2017/09/16/hassbian-1.3-a-bit-of-a-stretch/index.html
index 59f521201f..e8bea55f50 100644
--- a/blog/2017/09/16/hassbian-1.3-a-bit-of-a-stretch/index.html
+++ b/blog/2017/09/16/hassbian-1.3-a-bit-of-a-stretch/index.html
@@ -23,7 +23,7 @@
-
+
@@ -139,6 +139,9 @@ Other than that the changes are mostly to our tool
Beside the improved Wink support which was contributed by @w1ll1am23, ships this release a wide variety of new components and platforms. The input_slider components has received a makeover by @BioSehnsucht and is now input_number. @tinloaf added a feature that allows you to enter dates: input_datetime. Both will help you to improve your automation rules.
DuckDNS
-
Using Home Assistant with DuckDNS for Dynamic DNS (DDNS or DynDNS) is an old story. DuckDNS is also integrated in Hass.io. 0.55 ships a component for no Hass.io users to get a similar feature.
+
Using Home Assistant with DuckDNS for Dynamic DNS (DDNS or DynDNS) is an old story. DuckDNS is also integrated in Hass.io. 0.55 ships a component for non Hass.io users to get a similar feature.
Recorder
-
The purging of data was improved. With purge_interval you can schedule regular purges of older events and states. In combination you can specify with purge_keep_days the amount of days you want to keep. The new service recorder.purge allow to handle this task when needed.
+
The purging of data was improved. With purge_interval you can schedule regular purges of older events and states. In combination you can specify with purge_keep_days the amount of days you want to keep. The new service recorder.purge allows you to handle this task when needed.
Owntracks
Owntracks is an easy way to track your devices. For some times we have the device tracker which depends on MQTT but thanks to a new feature in Owntracks we can now offer support for HTTP. The new platform doesn’t require a MQTT broker but sends messages directly as HTTP requests to Home Assistant.
We reached another milestone aka number: 10000. GitHub is assigning numbers to pull requests and issues and the “10000” is a PR. Our ratio is around 1/3 issues and 2/3 pull requests. To be more precise: 64% pull requests and 36% issues.
+
If you haven’t noticed, there is now a glossary that collects some Home Assistant relevant terms. Talking about the documentation: @DubhAd rewrote large parts of the Z-Wave section. More structure to get started and to find details during the setup and the configuration.
+
Google Assistant / Google Home integration
+
This release includes a new component to integrate Home Assistant with Google Assistant by Phil Kates. We integrate via the Smart Home API, this means that you will be able to control your devices in Home Assistant via any device that has Google Assistant. Learn more in the documentation.
+
Hacktoberfest
+
Hacktoberfest is still on and so far we have received a lot improvements. We can’t make any promises to review everything by the end of October, but we are trying to make sure that you will get your t-shirt.
+
Map
+
The map is now its own component. Similar to configuration (config:), it will not show up without adding it to your configuration.yaml file.
+
map:
+
+
+
Travis CI
+
Why not observe your Travis CI jobs with Home Assistant? @tchellomello created a Travis CI sensor which allows one to check on the current state of Travis jobs. Now you can make sure that the coffee is ready when the build passed.
…don’t hesitate to use our very active forums or join us for a little chat. 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. Make sure to fill in all fields of the issue template.
+
+
+We reached another milestone aka number: 10000. GitHub is assigning numbers to pull requests and issues and the "10000" is a [PR](https://github.com/home-assistant/home-assistant/pull/10000). Our ratio is around 1/3 issues and 2/3 pull requests. To be more precise: 64% pull requests and 36% issues.
+
+If you haven't noticed, there is now a [glossary](https://home-assistant.io/docs/glossary/) that collects some Home Assistant relevant terms. Talking about the documentation: [@DubhAd](https://github.com/DubhAd) rewrote large parts of the [Z-Wave section](https://home-assistant.io/docs/z-wave/). More structure to get started and to find details during the setup and the configuration.
+
+## Google Assistant / Google Home integration
+This release includes a new component to integrate Home Assistant with Google Assistant by [Phil Kates][@philk]. We integrate via the Smart Home API, this means that you will be able to control your devices in Home Assistant via any device that has Google Assistant. Learn more in [the documentation][googleactions docs].
+
+## Hacktoberfest
+[Hacktoberfest](https://home-assistant.io/blog/2017/09/29/hacktoberfest/) is still on and so far we have received a lot improvements. We can't make any promises to review everything by the end of October, but we are trying to make sure that you will get your t-shirt.
+
+## Map
+The [map][map docs] is now its own component. Similar to [configuration (`config:`)](https://home-assistant.io/components/config/), it will not show up without adding it to your `configuration.yaml` file.
+
+```yaml
+map:
+```
+
+## Travis CI
+Why not observe your [Travis CI](https://travis-ci.org) jobs with Home Assistant? [@tchellomello] created a [Travis CI][sensor.travisci docs] sensor which allows one to check on the current state of Travis jobs. Now you can make sure that the [coffee](https://home-assistant.io/blog/2017/01/28/face-coffee-wink/#first-coffee-maker-supported) is ready when the build passed.
+
+## New Platforms
+
+- Add Arlo alarm control panel component ([@vickyg3] - [#9711]) ([alarm_control_panel.arlo docs]) (new-platform)
+- Abode Temp, Humidity, and Light Sensor ([@MisterWil] - [#9709]) ([abode docs]) ([sensor.abode docs]) (new-platform)
+- Introducing support to Travis-CI ([@tchellomello] - [#9701]) ([sensor.travisci docs]) (new-platform)
+- Skybell ([@MisterWil] - [#9681]) ([skybell docs]) ([binary_sensor.skybell docs]) ([camera.skybell docs]) ([light.skybell docs]) ([sensor.skybell docs]) ([switch.skybell docs]) (new-platform)
+- Xiaomi Smart WiFi Socket and Smart Power Strip integration ([@syssi] - [#9138]) ([switch.xiaomi_plug docs]) (new-platform)
+- Add notification platform for Rocket.Chat ([@webworxshop] - [#9553]) ([notify.rocketchat docs]) (new-platform)
+- Tesla bug fixes. ([@zabuldon] - [#9774]) ([tesla docs]) ([binary_sensor.tesla docs]) ([climate.tesla docs]) ([lock.tesla docs]) ([sensor.tesla docs]) ([switch.tesla docs]) (new-platform)
+- Split map panel out into its own component ([@cgarwood] - [#9814]) ([map docs]) (breaking change) (new-platform)
+- Support for Yi cameras ([@bachya] - [#9787]) ([camera.yi docs]) (new-platform)
+- Add namecheap DNS component ([@Munsio] - [#9821]) ([namecheapdns docs]) (new-platform)
+- Uptime sensor ([@fronzbot] - [#9856]) ([sensor.uptime docs]) (new-platform)
+- Cloud connection via aiohttp ([@balloob] - [#9860]) (new-platform)
+- Google Actions for Assistant ([@philk] - [#9632]) ([googleactions docs]) ([http docs]) (new-platform)
+- A new platform for controlling Monoprice 6-Zone amplifier ([@etsinko] - [#9662]) ([media_player.monoprice docs]) (new-platform)
+- Add serial sensor ([@fabaff] - [#9861]) ([sensor.serial docs]) (new-platform)
+- Add Toon support ([@Boltgolt] - [#9483]) ([toon docs]) ([climate.toon docs]) ([sensor.toon docs]) ([switch.toon docs]) (new-platform)
+
+## 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.
+
+## 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.
+
+
+
+## Breaking Changes
+
+- Simplify track_same_state ([@balloob] - [#9795]) ([automation.numeric_state docs]) ([automation.state docs]) ([binary_sensor.template docs]) (breaking change)
+- Split map panel out into its own component ([@cgarwood] - [#9814]) ([map docs]) (breaking change) (new-platform)
+- Fix ISY994 fan platform overwriting state property ([@balloob] - [#9817]) (breaking change)
+- Changing name of clicksendaudio component to clicksend_tts ([@jeroenterheerdt] - [#9859]) ([notify.clicksend_tts docs]) (breaking change)
+- Fix load of components without any config from packages ([@azogue] - [#9901]) (breaking change)
+- Fix the resource naming in the UI ([@cgtobi] - [#9916]) ([sensor.systemmonitor docs]) (breaking change)
+- Align away state tag with device_trackers ([@PeteBa] - [#9884]) ([sensor.mqtt_room docs]) (breaking change)
+- Moved siren to Wink from switch ([@w1ll1am23] - [#9879]) ([wink docs]) ([switch.wink docs]) (breaking change)
+
+## All changes
+
+- fixed duplicate words ([@flowolf] - [#9705]) ([light.hue docs]) ([light.mqtt_json docs]) ([media_player.denon docs]) ([media_player.dunehd docs])
+- move icon battery function from util to helpers ([@happyleavesaoc] - [#9708]) ([vacuum docs]) ([sensor.android_ip_webcam docs]) ([sensor.fitbit docs]) ([sensor.ios docs]) ([sensor.raincloud docs]) ([vacuum.dyson docs]) ([vacuum.mqtt docs])
+- Updating helper's icon_for_battery_level location ([@tchellomello] - [#9594]) ([sensor.ring docs])
+- Upgrade pyhomematic, add path setting and HM-CC-VG-1 support ([@danielperna84] - [#9707]) ([homematic docs])
+- bump the version and catch all exceptions to avoid showing backtraces… ([@rytilahti] - [#9720]) ([climate.eq3btsmart docs])
+- More netdata sensors ([@fronzbot] - [#9719]) ([sensor.netdata docs])
+- Upgrade pysnmp to 4.3.10 ([@fabaff] - [#9722]) ([device_tracker.snmp docs]) ([sensor.snmp docs])
+- arlo: Add alarm control panel component ([@vickyg3] - [#9711]) ([alarm_control_panel.arlo docs]) (new-platform)
+- Abode Temp, Humidity, and Light Sensor ([@MisterWil] - [#9709]) ([abode docs]) ([sensor.abode docs]) (new-platform)
+- Arlo clean-up ([@fabaff] - [#9725]) ([arlo docs]) ([alarm_control_panel.arlo docs]) ([camera.arlo docs]) ([sensor.arlo docs])
+- Introducing support to Travis-CI ([@tchellomello] - [#9701]) ([sensor.travisci docs]) (new-platform)
+- Add show_on_map config option to AirVisual ([@bachya] - [#9654]) ([sensor.airvisual docs])
+- Move 'show_on_map' to const ([@fabaff] - [#9727]) ([binary_sensor.iss docs]) ([sensor.airvisual docs])
+- Bump release to 0.56.0dev ([@fabaff] - [#9726])
+- Add andrey-git to codeowners ([@andrey-git] - [#9718])
+- Fix: Last Played Media Title persists in plex ([@ryanm101] - [#9664]) ([media_player.plex docs])
+- Event trigger nested conditions ([@armills] - [#9732]) ([automation.event docs])
+- Rewrite Alexa Smart-Home skill to v3 ([@pvizeli] - [#9699]) ([alexa.smart_home docs])
+- Fix I/O in event loop by Arlo alarm control panel ([@balloob] - [#9738]) ([alarm_control_panel.arlo docs])
+- Make Arlo battery_level icon dynamic ([@tchellomello] - [#9747]) ([sensor.arlo docs])
+- Fix for TypeError in synology camera ([@snjoetw] - [#9754]) ([camera.synology docs])
+- switch.tplink, light.tplink: bump the pyhs100 version and adapt to api changes ([@rytilahti] - [#9454]) ([light.tplink docs]) ([switch.tplink docs])
+- RFC: Use bind_hass for helpers ([@balloob] - [#9745])
+- Skybell ([@MisterWil] - [#9681]) ([skybell docs]) ([binary_sensor.skybell docs]) ([camera.skybell docs]) ([light.skybell docs]) ([sensor.skybell docs]) ([switch.skybell docs]) (new-platform)
+- add myself to yeelight owners, too ([@rytilahti] - [#9759])
+- Update CODEOWNERS ([@danielhiversen] - [#9760])
+- Adding my contributions ([@bachya] - [#9761])
+- Initializing statistics sensor with data from database ([@ChristianKuehnel] - [#9753]) ([sensor.statistics docs])
+- Match test requirements by full package name. ([@andrey-git] - [#9764])
+- yeelight: implement min_mireds and max_mireds, fixes #9509 ([@rytilahti] - [#9763]) ([light.yeelight docs])
+- Bump raincloudy version 0.0.3 ([@tchellomello] - [#9767]) ([raincloud docs]) ([sensor.raincloud docs])
+- Xiaomi Smart WiFi Socket and Smart Power Strip integration ([@syssi] - [#9138]) ([switch.xiaomi_plug docs]) (new-platform)
+- fix for LocationParseError in netgear platform ([@etsinko] - [#9683]) ([device_tracker docs]) ([device_tracker.netgear docs])
+- Expose time module in Python Scripts ([@balloob] - [#9736]) ([python_script docs])
+- Add notification platform for Rocket.Chat. ([@webworxshop] - [#9553]) ([notify.rocketchat docs]) (new-platform)
+- Updating pythonegardia package requirement to .22 because of fixed bug in passing default value for parameter SSL for egardiaserver ([@jeroenterheerdt] - [#9770]) ([alarm_control_panel.egardia docs])
+- Adding myself as codeowner for egardia alarm control panel. ([@jeroenterheerdt] - [#9772])
+- WIP: Fix Arlo Camera blocking IO ([@bachya] - [#9758]) ([camera.arlo docs])
+- Tesla bug fixes. ([@zabuldon] - [#9774]) ([tesla docs]) ([binary_sensor.tesla docs]) ([climate.tesla docs]) ([lock.tesla docs]) ([sensor.tesla docs]) ([switch.tesla docs]) (new-platform)
+- Fix off by one error in arwn platform ([@sdague] - [#9781]) ([sensor.arwn docs])
+- missing is_closed ( rflink cover fix ) ([@passie] - [#9776]) ([cover.rflink docs])
+- Wink dome siren support ([@w1ll1am23] - [#9667]) ([wink docs]) ([switch.wink docs])
+- Bump rxv library to 0.5.1 ([@sdague] - [#9784]) ([media_player.yamaha docs])
+- Communication timeout support in modbus hub. ([@ziotibia81] - [#9780]) ([modbus docs])
+- [light.tradfri] Fix transition time ([@lwis] - [#9785]) ([light.tradfri docs])
+- OwnTracks: Fix handler is None checking ([@balloob] - [#9794]) ([device_tracker.owntracks docs])
+- Simplify track_same_state ([@balloob] - [#9795]) ([automation.numeric_state docs]) ([automation.state docs]) ([binary_sensor.template docs]) (breaking change)
+- Optimize event matcher ([@balloob] - [#9798])
+- Resolving bug that prevents ssl_verify option for Unifi device_tracker ([@GenericStudent] - [#9788]) ([device_tracker.unifi docs])
+- Upgrade pyasn1 to 0.3.7 and pyasn1-modules to 0.1.5 ([@fabaff] - [#9810])
+- Split map panel out into its own component ([@cgarwood] - [#9814]) ([map docs]) (breaking change) (new-platform)
+- Restore home-assistant-polymer pointer from #9720 ([@armills] - [#9825])
+- Fix ISY994 fan platform overwriting state property ([@balloob] - [#9817]) (breaking change)
+- Wait_template - support for 'trigger.entity_id' and data_template values ([@cdce8p] - [#9807])
+- Adds image attribute to html5 notify (#9832) ([@cgarwood] - [#9835]) ([notify.html5 docs])
+- OwnTracks: Handle lwt message ([@balloob] - [#9831]) ([device_tracker.owntracks docs])
+- Upgrade libnacl ([@fabaff] - [#9769]) ([device_tracker.owntracks docs])
+- Fixed reporting of vera UV sensors ([@alanfischer] - [#9838]) ([sensor.vera docs])
+- Update CODEOWNERS */axis.py ([@Kane610] - [#9823])
+- fix climate services (missing indentation, wrongly formatted example) ([@rytilahti] - [#9805])
+- Run initial generation for development mode ([@armills] - [#9826])
+- Add service descriptions ([@cgarwood] - [#9806]) ([__init__ docs])
+- Bugfix: Include MQTT schema ([@tinloaf] - [#9802]) ([climate.mqtt docs])
+- Bugfix/9811 jinja autoescape ([@GenericStudent] - [#9842])
+- Changed yaml.load into yaml.safe_load ([@GenericStudent] - [#9841])
+- New PR ([@bachya] - [#9787]) ([camera.yi docs]) (new-platform)
+- Do not auto-install credstash ([@balloob] - [#9844])
+- Add namecheap DNS component ([@Munsio] - [#9821]) ([namecheapdns docs]) (new-platform)
+- Remove namecheap dns service ([@balloob] - [#9845]) ([namecheapdns docs])
+- Use the Last Seen attribute in unify ([@rbflurry] - [#8998]) ([device_tracker.unifi docs])
+- Add CAPSman master to mikrotik presence detection ([@icovada] - [#9729]) ([device_tracker.mikrotik docs])
+- File permissions fix ([@cgarwood] - [#9847]) ([map docs])
+- HassIO - TimeZone / Host services ([@pvizeli] - [#9846]) ([hassio docs])
+- Changing name of clicksendaudio component to clicksend_tts ([@jeroenterheerdt] - [#9859]) ([notify.clicksend_tts docs]) (breaking change)
+- Upgrade youtube_dl to 2017.10.12 ([@fabaff] - [#9862]) ([media_extractor docs])
+- Uptime sensor ([@fronzbot] - [#9856]) ([sensor.uptime docs]) (new-platform)
+- Darksky enhancements ([@rdbahm] - [#9851]) ([sensor.darksky docs])
+- Upgrade psutil to 5.4.0 ([@fabaff] - [#9869]) ([sensor.systemmonitor docs])
+- minimal fixes in the owntracks mqtt device tracker ([@azogue] - [#9866]) ([device_tracker.owntracks docs])
+- Cloud connection via aiohttp ([@balloob] - [#9860]) (new-platform)
+- handle OWM API error calls ([@azogue] - [#9865]) ([sensor.openweathermap docs]) ([weather.openweathermap docs])
+- Upgrade paho-mqtt to 1.3.1 ([@fabaff] - [#9874]) ([mqtt docs]) ([shiftr docs])
+- Fix for TypeError in synology camera ([@snjoetw] - [#9754]) ([camera.synology docs])
+- missing is_closed ( rflink cover fix ) ([@passie] - [#9776]) ([cover.rflink docs])
+- [light.tradfri] Fix transition time ([@lwis] - [#9785]) ([light.tradfri docs])
+- OwnTracks: Fix handler is None checking ([@balloob] - [#9794]) ([device_tracker.owntracks docs])
+- Changed yaml.load into yaml.safe_load ([@GenericStudent] - [#9841])
+- Bugfix/9811 jinja autoescape ([@GenericStudent] - [#9842])
+- Fix #9839 ([@pschmitt] - [#9880]) ([media_player.liveboxplaytv docs])
+- Upgrade python-telegram-bot to 8.1.1 ([@azogue] - [#9882]) ([telegram_bot docs])
+- Xknx improvements ([@Julius2342] - [#9871]) ([knx docs]) ([climate.knx docs])
+- zha: Update to bellows 0.4.0 ([@rcloran] - [#9890]) ([zha docs]) ([sensor.zha docs])
+- Changing clicksendaudio to clicksend_tts in .coveragerc ([@jeroenterheerdt] - [#9900])
+- Added super attributes to Wink binary sensors ([@w1ll1am23] - [#9824]) ([binary_sensor.wink docs])
+- Release 0.55.2 ([@pvizeli] - [#9904])
+- Dependemcy version bump. ([@zabuldon] - [#9899]) ([device_tracker.mikrotik docs])
+- Update osramlightify.py ([@Bahnburner] - [#9905]) ([light.osramlightify docs])
+- Fixes ([@bachya] - [#9912]) ([switch.rainmachine docs])
+- Fix load of components without any config from packages ([@azogue] - [#9901]) (breaking change)
+- Fixes ([@bachya] - [#9911]) ([sensor.airvisual docs])
+- add last_action for xiaomi cube ([@danielhiversen] - [#9897]) ([binary_sensor.xiaomi_aqara docs])
+- Added support for Denon AVR-4810. ([@scarface-4711] - [#9887]) ([media_player.denonavr docs])
+- Recorder: Extra check to incoming connections which could be not sqlite3 ones ([@azogue] - [#9867])
+- Fix the resource naming in the UI ([@cgtobi] - [#9916]) ([sensor.systemmonitor docs]) (breaking change)
+- Update xiaomi_aqara.py ([@danielhiversen] - [#9920]) ([sensor.xiaomi_aqara docs])
+- Fix the resource naming in the UI ([@cgtobi] - [#9927]) ([sensor.glances docs])
+- Add transmission sensor: number of active torrents ([@mclem] - [#9914]) ([sensor.transmission docs])
+- Google Actions for Assistant ([@philk] - [#9632]) ([googleactions docs]) ([http docs]) (new-platform)
+- Allow flexible relayer url ([@balloob] - [#9939]) ([cloud.iot docs])
+- update async_timeout from v1.4.0 tp v2.0.0 ([@TopdRob] - [#9938])
+- Bump py-synology to 0.1.5 ([@arsaboo] - [#9932]) ([camera.synology docs])
+- Update aioimaplib from v0.7.12 to v0.7.13 ([@TopdRob] - [#9930]) ([sensor.imap docs])
+- A new platform for controlling Monoprice 6-Zone amplifier ([@etsinko] - [#9662]) ([media_player.monoprice docs]) (new-platform)
+- Align away state tag with device_trackers ([@PeteBa] - [#9884]) ([sensor.mqtt_room docs]) (breaking change)
+- Add serial sensor ([@fabaff] - [#9861]) ([sensor.serial docs]) (new-platform)
+- Fix missing timeout for Netatmo binary sensor ([@jabesq] - [#9850]) ([binary_sensor.netatmo docs])
+- Xiaomi config validation ([@danielhiversen] - [#9941]) ([xiaomi_aqara docs])
+- using defusedxml ElementTree for safer parsing of untrusted XML data ([@danielwelch] - [#9934]) ([device_tracker.upc_connect docs])
+- notify.xmpp - Add support for MUC ([@ldvc] - [#9931]) ([notify.xmpp docs])
+- FFmpeg 1.8 ([@pvizeli] - [#9944]) ([ffmpeg docs]) ([camera.ffmpeg docs]) ([camera.onvif docs]) ([camera.yi docs])
+- Changed returned attribute from "Game" to "game" ([@itchaboy] - [#9945]) ([sensor.steam_online docs])
+- Move 'lights' to const.py ([@fabaff] - [#9929]) ([abode docs]) ([vera docs]) ([light.template docs]) ([switch.flux docs])
+- Update directpy to 0.2 ([@arsaboo] - [#9948])
+- Update enocean to 0.40 ([@arsaboo] - [#9949]) ([enocean docs])
+- Update hikvision to 1.2 ([@arsaboo] - [#9953]) ([switch.hikvisioncam docs])
+- Update fritzhome to 1.0.3 ([@arsaboo] - [#9951]) ([switch.fritzdect docs])
+- Update fritzconnection to 0.6.5 ([@arsaboo] - [#9950]) ([device_tracker.fritz docs]) ([sensor.fritzbox_callmonitor docs]) ([sensor.fritzbox_netmonitor docs])
+- Upgraded pyhomematic ([@danielperna84] - [#9956]) ([homematic docs])
+- Add emeter attributes ([@gollo] - [#9903]) ([light.tplink docs])
+- Use default clientsession to stream synology video ([@snjoetw] - [#9959]) ([camera.synology docs])
+- Update ffmpeg 1.9 ([@pvizeli] - [#9963])
+- Improve SSL certs used by aiohttp ([@balloob] - [#9958]) ([cloud.iot docs])
+- Fix async probs ([@pvizeli] - [#9924])
+- Add Toon support ([@Boltgolt] - [#9483]) ([toon docs]) ([climate.toon docs]) ([sensor.toon docs]) ([switch.toon docs]) (new-platform)
+- [tradfri] Update pytradfri, simplify dependencies. ([@lwis] - [#9875]) ([tradfri docs]) ([light.tradfri docs]) ([sensor.tradfri docs])
+- Moved siren to Wink from switch ([@w1ll1am23] - [#9879]) ([wink docs]) ([switch.wink docs]) (breaking change)
+- Remove async_update ([@pvizeli] - [#9997])
+
+[#8998]: https://github.com/home-assistant/home-assistant/pull/8998
+[#9138]: https://github.com/home-assistant/home-assistant/pull/9138
+[#9454]: https://github.com/home-assistant/home-assistant/pull/9454
+[#9483]: https://github.com/home-assistant/home-assistant/pull/9483
+[#9553]: https://github.com/home-assistant/home-assistant/pull/9553
+[#9594]: https://github.com/home-assistant/home-assistant/pull/9594
+[#9632]: https://github.com/home-assistant/home-assistant/pull/9632
+[#9654]: https://github.com/home-assistant/home-assistant/pull/9654
+[#9662]: https://github.com/home-assistant/home-assistant/pull/9662
+[#9664]: https://github.com/home-assistant/home-assistant/pull/9664
+[#9667]: https://github.com/home-assistant/home-assistant/pull/9667
+[#9681]: https://github.com/home-assistant/home-assistant/pull/9681
+[#9683]: https://github.com/home-assistant/home-assistant/pull/9683
+[#9699]: https://github.com/home-assistant/home-assistant/pull/9699
+[#9701]: https://github.com/home-assistant/home-assistant/pull/9701
+[#9705]: https://github.com/home-assistant/home-assistant/pull/9705
+[#9707]: https://github.com/home-assistant/home-assistant/pull/9707
+[#9708]: https://github.com/home-assistant/home-assistant/pull/9708
+[#9709]: https://github.com/home-assistant/home-assistant/pull/9709
+[#9711]: https://github.com/home-assistant/home-assistant/pull/9711
+[#9718]: https://github.com/home-assistant/home-assistant/pull/9718
+[#9719]: https://github.com/home-assistant/home-assistant/pull/9719
+[#9720]: https://github.com/home-assistant/home-assistant/pull/9720
+[#9722]: https://github.com/home-assistant/home-assistant/pull/9722
+[#9725]: https://github.com/home-assistant/home-assistant/pull/9725
+[#9726]: https://github.com/home-assistant/home-assistant/pull/9726
+[#9727]: https://github.com/home-assistant/home-assistant/pull/9727
+[#9729]: https://github.com/home-assistant/home-assistant/pull/9729
+[#9732]: https://github.com/home-assistant/home-assistant/pull/9732
+[#9736]: https://github.com/home-assistant/home-assistant/pull/9736
+[#9738]: https://github.com/home-assistant/home-assistant/pull/9738
+[#9745]: https://github.com/home-assistant/home-assistant/pull/9745
+[#9747]: https://github.com/home-assistant/home-assistant/pull/9747
+[#9753]: https://github.com/home-assistant/home-assistant/pull/9753
+[#9754]: https://github.com/home-assistant/home-assistant/pull/9754
+[#9758]: https://github.com/home-assistant/home-assistant/pull/9758
+[#9759]: https://github.com/home-assistant/home-assistant/pull/9759
+[#9760]: https://github.com/home-assistant/home-assistant/pull/9760
+[#9761]: https://github.com/home-assistant/home-assistant/pull/9761
+[#9763]: https://github.com/home-assistant/home-assistant/pull/9763
+[#9764]: https://github.com/home-assistant/home-assistant/pull/9764
+[#9767]: https://github.com/home-assistant/home-assistant/pull/9767
+[#9769]: https://github.com/home-assistant/home-assistant/pull/9769
+[#9770]: https://github.com/home-assistant/home-assistant/pull/9770
+[#9772]: https://github.com/home-assistant/home-assistant/pull/9772
+[#9774]: https://github.com/home-assistant/home-assistant/pull/9774
+[#9776]: https://github.com/home-assistant/home-assistant/pull/9776
+[#9780]: https://github.com/home-assistant/home-assistant/pull/9780
+[#9781]: https://github.com/home-assistant/home-assistant/pull/9781
+[#9784]: https://github.com/home-assistant/home-assistant/pull/9784
+[#9785]: https://github.com/home-assistant/home-assistant/pull/9785
+[#9787]: https://github.com/home-assistant/home-assistant/pull/9787
+[#9788]: https://github.com/home-assistant/home-assistant/pull/9788
+[#9794]: https://github.com/home-assistant/home-assistant/pull/9794
+[#9795]: https://github.com/home-assistant/home-assistant/pull/9795
+[#9798]: https://github.com/home-assistant/home-assistant/pull/9798
+[#9802]: https://github.com/home-assistant/home-assistant/pull/9802
+[#9805]: https://github.com/home-assistant/home-assistant/pull/9805
+[#9806]: https://github.com/home-assistant/home-assistant/pull/9806
+[#9807]: https://github.com/home-assistant/home-assistant/pull/9807
+[#9810]: https://github.com/home-assistant/home-assistant/pull/9810
+[#9814]: https://github.com/home-assistant/home-assistant/pull/9814
+[#9817]: https://github.com/home-assistant/home-assistant/pull/9817
+[#9821]: https://github.com/home-assistant/home-assistant/pull/9821
+[#9823]: https://github.com/home-assistant/home-assistant/pull/9823
+[#9824]: https://github.com/home-assistant/home-assistant/pull/9824
+[#9825]: https://github.com/home-assistant/home-assistant/pull/9825
+[#9826]: https://github.com/home-assistant/home-assistant/pull/9826
+[#9831]: https://github.com/home-assistant/home-assistant/pull/9831
+[#9835]: https://github.com/home-assistant/home-assistant/pull/9835
+[#9838]: https://github.com/home-assistant/home-assistant/pull/9838
+[#9841]: https://github.com/home-assistant/home-assistant/pull/9841
+[#9842]: https://github.com/home-assistant/home-assistant/pull/9842
+[#9844]: https://github.com/home-assistant/home-assistant/pull/9844
+[#9845]: https://github.com/home-assistant/home-assistant/pull/9845
+[#9846]: https://github.com/home-assistant/home-assistant/pull/9846
+[#9847]: https://github.com/home-assistant/home-assistant/pull/9847
+[#9850]: https://github.com/home-assistant/home-assistant/pull/9850
+[#9851]: https://github.com/home-assistant/home-assistant/pull/9851
+[#9856]: https://github.com/home-assistant/home-assistant/pull/9856
+[#9859]: https://github.com/home-assistant/home-assistant/pull/9859
+[#9860]: https://github.com/home-assistant/home-assistant/pull/9860
+[#9861]: https://github.com/home-assistant/home-assistant/pull/9861
+[#9862]: https://github.com/home-assistant/home-assistant/pull/9862
+[#9865]: https://github.com/home-assistant/home-assistant/pull/9865
+[#9866]: https://github.com/home-assistant/home-assistant/pull/9866
+[#9867]: https://github.com/home-assistant/home-assistant/pull/9867
+[#9869]: https://github.com/home-assistant/home-assistant/pull/9869
+[#9871]: https://github.com/home-assistant/home-assistant/pull/9871
+[#9874]: https://github.com/home-assistant/home-assistant/pull/9874
+[#9875]: https://github.com/home-assistant/home-assistant/pull/9875
+[#9879]: https://github.com/home-assistant/home-assistant/pull/9879
+[#9880]: https://github.com/home-assistant/home-assistant/pull/9880
+[#9882]: https://github.com/home-assistant/home-assistant/pull/9882
+[#9884]: https://github.com/home-assistant/home-assistant/pull/9884
+[#9887]: https://github.com/home-assistant/home-assistant/pull/9887
+[#9890]: https://github.com/home-assistant/home-assistant/pull/9890
+[#9897]: https://github.com/home-assistant/home-assistant/pull/9897
+[#9899]: https://github.com/home-assistant/home-assistant/pull/9899
+[#9900]: https://github.com/home-assistant/home-assistant/pull/9900
+[#9901]: https://github.com/home-assistant/home-assistant/pull/9901
+[#9903]: https://github.com/home-assistant/home-assistant/pull/9903
+[#9904]: https://github.com/home-assistant/home-assistant/pull/9904
+[#9905]: https://github.com/home-assistant/home-assistant/pull/9905
+[#9911]: https://github.com/home-assistant/home-assistant/pull/9911
+[#9912]: https://github.com/home-assistant/home-assistant/pull/9912
+[#9914]: https://github.com/home-assistant/home-assistant/pull/9914
+[#9916]: https://github.com/home-assistant/home-assistant/pull/9916
+[#9920]: https://github.com/home-assistant/home-assistant/pull/9920
+[#9924]: https://github.com/home-assistant/home-assistant/pull/9924
+[#9927]: https://github.com/home-assistant/home-assistant/pull/9927
+[#9929]: https://github.com/home-assistant/home-assistant/pull/9929
+[#9930]: https://github.com/home-assistant/home-assistant/pull/9930
+[#9931]: https://github.com/home-assistant/home-assistant/pull/9931
+[#9932]: https://github.com/home-assistant/home-assistant/pull/9932
+[#9934]: https://github.com/home-assistant/home-assistant/pull/9934
+[#9938]: https://github.com/home-assistant/home-assistant/pull/9938
+[#9939]: https://github.com/home-assistant/home-assistant/pull/9939
+[#9941]: https://github.com/home-assistant/home-assistant/pull/9941
+[#9944]: https://github.com/home-assistant/home-assistant/pull/9944
+[#9945]: https://github.com/home-assistant/home-assistant/pull/9945
+[#9948]: https://github.com/home-assistant/home-assistant/pull/9948
+[#9949]: https://github.com/home-assistant/home-assistant/pull/9949
+[#9950]: https://github.com/home-assistant/home-assistant/pull/9950
+[#9951]: https://github.com/home-assistant/home-assistant/pull/9951
+[#9953]: https://github.com/home-assistant/home-assistant/pull/9953
+[#9956]: https://github.com/home-assistant/home-assistant/pull/9956
+[#9958]: https://github.com/home-assistant/home-assistant/pull/9958
+[#9959]: https://github.com/home-assistant/home-assistant/pull/9959
+[#9963]: https://github.com/home-assistant/home-assistant/pull/9963
+[#9997]: https://github.com/home-assistant/home-assistant/pull/9997
+[@Bahnburner]: https://github.com/Bahnburner
+[@Boltgolt]: https://github.com/Boltgolt
+[@ChristianKuehnel]: https://github.com/ChristianKuehnel
+[@GenericStudent]: https://github.com/GenericStudent
+[@Julius2342]: https://github.com/Julius2342
+[@Kane610]: https://github.com/Kane610
+[@MisterWil]: https://github.com/MisterWil
+[@Munsio]: https://github.com/Munsio
+[@PeteBa]: https://github.com/PeteBa
+[@TopdRob]: https://github.com/TopdRob
+[@alanfischer]: https://github.com/alanfischer
+[@andrey-git]: https://github.com/andrey-git
+[@armills]: https://github.com/armills
+[@arsaboo]: https://github.com/arsaboo
+[@azogue]: https://github.com/azogue
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@cdce8p]: https://github.com/cdce8p
+[@cgarwood]: https://github.com/cgarwood
+[@cgtobi]: https://github.com/cgtobi
+[@danielhiversen]: https://github.com/danielhiversen
+[@danielperna84]: https://github.com/danielperna84
+[@danielwelch]: https://github.com/danielwelch
+[@etsinko]: https://github.com/etsinko
+[@fabaff]: https://github.com/fabaff
+[@flowolf]: https://github.com/flowolf
+[@fronzbot]: https://github.com/fronzbot
+[@gollo]: https://github.com/gollo
+[@happyleavesaoc]: https://github.com/happyleavesaoc
+[@icovada]: https://github.com/icovada
+[@itchaboy]: https://github.com/itchaboy
+[@jabesq]: https://github.com/jabesq
+[@jeroenterheerdt]: https://github.com/jeroenterheerdt
+[@ldvc]: https://github.com/ldvc
+[@lwis]: https://github.com/lwis
+[@mclem]: https://github.com/mclem
+[@passie]: https://github.com/passie
+[@philk]: https://github.com/philk
+[@pschmitt]: https://github.com/pschmitt
+[@pvizeli]: https://github.com/pvizeli
+[@rbflurry]: https://github.com/rbflurry
+[@rcloran]: https://github.com/rcloran
+[@rdbahm]: https://github.com/rdbahm
+[@ryanm101]: https://github.com/ryanm101
+[@rytilahti]: https://github.com/rytilahti
+[@scarface-4711]: https://github.com/scarface-4711
+[@sdague]: https://github.com/sdague
+[@snjoetw]: https://github.com/snjoetw
+[@syssi]: https://github.com/syssi
+[@tchellomello]: https://github.com/tchellomello
+[@tinloaf]: https://github.com/tinloaf
+[@vickyg3]: https://github.com/vickyg3
+[@w1ll1am23]: https://github.com/w1ll1am23
+[@webworxshop]: https://github.com/webworxshop
+[@zabuldon]: https://github.com/zabuldon
+[@ziotibia81]: https://github.com/ziotibia81
+[__init__ docs]: https://home-assistant.io/components/__init__/
+[abode docs]: https://home-assistant.io/components/abode/
+[alarm_control_panel.arlo docs]: https://home-assistant.io/components/alarm_control_panel.arlo/
+[alarm_control_panel.egardia docs]: https://home-assistant.io/components/alarm_control_panel.egardia/
+[alexa.smart_home docs]: https://home-assistant.io/components/alexa.smart_home/
+[arlo docs]: https://home-assistant.io/components/arlo/
+[automation.event docs]: https://home-assistant.io/docs/automation/trigger/#event-trigger
+[automation.numeric_state docs]: https://home-assistant.io/docs/automation/trigger/#numeric-state-trigger
+[automation.state docs]: https://home-assistant.io/docs/automation/trigger/#state-trigger
+[binary_sensor.iss docs]: https://home-assistant.io/components/binary_sensor.iss/
+[binary_sensor.netatmo docs]: https://home-assistant.io/components/binary_sensor.netatmo/
+[binary_sensor.skybell docs]: https://home-assistant.io/components/binary_sensor.skybell/
+[binary_sensor.template docs]: https://home-assistant.io/components/binary_sensor.template/
+[binary_sensor.tesla docs]: https://home-assistant.io/components/binary_sensor.tesla/
+[binary_sensor.wink docs]: https://home-assistant.io/components/binary_sensor.wink/
+[binary_sensor.xiaomi_aqara docs]: https://home-assistant.io/components/binary_sensor.xiaomi_aqara/
+[camera.arlo docs]: https://home-assistant.io/components/camera.arlo/
+[camera.ffmpeg docs]: https://home-assistant.io/components/camera.ffmpeg/
+[camera.onvif docs]: https://home-assistant.io/components/camera.onvif/
+[camera.skybell docs]: https://home-assistant.io/components/camera.skybell/
+[camera.synology docs]: https://home-assistant.io/components/camera.synology/
+[camera.yi docs]: https://home-assistant.io/components/camera.yi/
+[climate.eq3btsmart docs]: https://home-assistant.io/components/climate.eq3btsmart/
+[climate.knx docs]: https://home-assistant.io/components/climate.knx/
+[climate.mqtt docs]: https://home-assistant.io/components/climate.mqtt/
+[climate.tesla docs]: https://home-assistant.io/components/climate.tesla/
+[climate.toon docs]: https://home-assistant.io/components/climate.toon/
+[cloud.iot docs]: https://home-assistant.io/components/cloud.iot/
+[cover.rflink docs]: https://home-assistant.io/components/cover.rflink/
+[device_tracker docs]: https://home-assistant.io/components/device_tracker/
+[device_tracker.fritz docs]: https://home-assistant.io/components/device_tracker.fritz/
+[device_tracker.mikrotik docs]: https://home-assistant.io/components/device_tracker.mikrotik/
+[device_tracker.netgear docs]: https://home-assistant.io/components/device_tracker.netgear/
+[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
+[device_tracker.snmp docs]: https://home-assistant.io/components/device_tracker.snmp/
+[device_tracker.unifi docs]: https://home-assistant.io/components/device_tracker.unifi/
+[device_tracker.upc_connect docs]: https://home-assistant.io/components/device_tracker.upc_connect/
+[enocean docs]: https://home-assistant.io/components/enocean/
+[ffmpeg docs]: https://home-assistant.io/components/ffmpeg/
+[googleactions docs]: https://home-assistant.io/components/googleactions/
+[hassio docs]: https://home-assistant.io/components/hassio/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[http docs]: https://home-assistant.io/components/http/
+[knx docs]: https://home-assistant.io/components/knx/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[light.mqtt_json docs]: https://home-assistant.io/components/light.mqtt_json/
+[light.osramlightify docs]: https://home-assistant.io/components/light.osramlightify/
+[light.skybell docs]: https://home-assistant.io/components/light.skybell/
+[light.template docs]: https://home-assistant.io/components/light.template/
+[light.tplink docs]: https://home-assistant.io/components/light.tplink/
+[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
+[light.yeelight docs]: https://home-assistant.io/components/light.yeelight/
+[lock.tesla docs]: https://home-assistant.io/components/lock.tesla/
+[map docs]: https://home-assistant.io/components/map/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player.denon docs]: https://home-assistant.io/components/media_player.denon/
+[media_player.denonavr docs]: https://home-assistant.io/components/media_player.denonavr/
+[media_player.dunehd docs]: https://home-assistant.io/components/media_player.dunehd/
+[media_player.liveboxplaytv docs]: https://home-assistant.io/components/media_player.liveboxplaytv/
+[media_player.monoprice docs]: https://home-assistant.io/components/media_player.monoprice/
+[media_player.plex docs]: https://home-assistant.io/components/media_player.plex/
+[media_player.yamaha docs]: https://home-assistant.io/components/media_player.yamaha/
+[modbus docs]: https://home-assistant.io/components/modbus/
+[mqtt docs]: https://home-assistant.io/components/mqtt/
+[namecheapdns docs]: https://home-assistant.io/components/namecheapdns/
+[notify.clicksend_tts docs]: https://home-assistant.io/components/notify.clicksend_tts/
+[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
+[notify.rocketchat docs]: https://home-assistant.io/components/notify.rocketchat/
+[notify.xmpp docs]: https://home-assistant.io/components/notify.xmpp/
+[python_script docs]: https://home-assistant.io/components/python_script/
+[raincloud docs]: https://home-assistant.io/components/raincloud/
+[sensor.abode docs]: https://home-assistant.io/components/sensor.abode/
+[sensor.airvisual docs]: https://home-assistant.io/components/sensor.airvisual/
+[sensor.android_ip_webcam docs]: https://home-assistant.io/components/sensor.android_ip_webcam/
+[sensor.arlo docs]: https://home-assistant.io/components/sensor.arlo/
+[sensor.arwn docs]: https://home-assistant.io/components/sensor.arwn/
+[sensor.darksky docs]: https://home-assistant.io/components/sensor.darksky/
+[sensor.fitbit docs]: https://home-assistant.io/components/sensor.fitbit/
+[sensor.fritzbox_callmonitor docs]: https://home-assistant.io/components/sensor.fritzbox_callmonitor/
+[sensor.fritzbox_netmonitor docs]: https://home-assistant.io/components/sensor.fritzbox_netmonitor/
+[sensor.glances docs]: https://home-assistant.io/components/sensor.glances/
+[sensor.imap docs]: https://home-assistant.io/components/sensor.imap/
+[sensor.ios docs]: https://home-assistant.io/components/sensor.ios/
+[sensor.mqtt_room docs]: https://home-assistant.io/components/sensor.mqtt_room/
+[sensor.netdata docs]: https://home-assistant.io/components/sensor.netdata/
+[sensor.openweathermap docs]: https://home-assistant.io/components/sensor.openweathermap/
+[sensor.raincloud docs]: https://home-assistant.io/components/sensor.raincloud/
+[sensor.ring docs]: https://home-assistant.io/components/sensor.ring/
+[sensor.serial docs]: https://home-assistant.io/components/sensor.serial/
+[sensor.skybell docs]: https://home-assistant.io/components/sensor.skybell/
+[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/
+[sensor.statistics docs]: https://home-assistant.io/components/sensor.statistics/
+[sensor.steam_online docs]: https://home-assistant.io/components/sensor.steam_online/
+[sensor.systemmonitor docs]: https://home-assistant.io/components/sensor.systemmonitor/
+[sensor.tesla docs]: https://home-assistant.io/components/sensor.tesla/
+[sensor.toon docs]: https://home-assistant.io/components/sensor.toon/
+[sensor.tradfri docs]: https://home-assistant.io/components/sensor.tradfri/
+[sensor.transmission docs]: https://home-assistant.io/components/sensor.transmission/
+[sensor.travisci docs]: https://home-assistant.io/components/sensor.travisci/
+[sensor.uptime docs]: https://home-assistant.io/components/sensor.uptime/
+[sensor.vera docs]: https://home-assistant.io/components/sensor.vera/
+[sensor.xiaomi_aqara docs]: https://home-assistant.io/components/sensor.xiaomi_aqara/
+[sensor.zha docs]: https://home-assistant.io/components/sensor.zha/
+[shiftr docs]: https://home-assistant.io/components/shiftr/
+[skybell docs]: https://home-assistant.io/components/skybell/
+[switch.flux docs]: https://home-assistant.io/components/switch.flux/
+[switch.fritzdect docs]: https://home-assistant.io/components/switch.fritzdect/
+[switch.hikvisioncam docs]: https://home-assistant.io/components/switch.hikvisioncam/
+[switch.rainmachine docs]: https://home-assistant.io/components/switch.rainmachine/
+[switch.skybell docs]: https://home-assistant.io/components/switch.skybell/
+[switch.tesla docs]: https://home-assistant.io/components/switch.tesla/
+[switch.toon docs]: https://home-assistant.io/components/switch.toon/
+[switch.tplink docs]: https://home-assistant.io/components/switch.tplink/
+[switch.wink docs]: https://home-assistant.io/components/switch.wink/
+[switch.xiaomi_plug docs]: https://home-assistant.io/components/switch.xiaomi_plug/
+[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
+[tesla docs]: https://home-assistant.io/components/tesla/
+[toon docs]: https://home-assistant.io/components/toon/
+[tradfri docs]: https://home-assistant.io/components/tradfri/
+[vacuum docs]: https://home-assistant.io/components/vacuum/
+[vacuum.dyson docs]: https://home-assistant.io/components/vacuum.dyson/
+[vacuum.mqtt docs]: https://home-assistant.io/components/vacuum.mqtt/
+[vera docs]: https://home-assistant.io/components/vera/
+[weather.openweathermap docs]: https://home-assistant.io/components/weather.openweathermap/
+[wink docs]: https://home-assistant.io/components/wink/
+[xiaomi_aqara docs]: https://home-assistant.io/components/xiaomi_aqara/
+[zha docs]: https://home-assistant.io/components/zha/
+
+]]>
+
+
@@ -23,10 +549,10 @@
Beside the improved Wink support which was contributed by [@w1ll1am23], ships this release a wide variety of new components and platforms. The `input_slider` components has received a makeover by [@BioSehnsucht] and is now [`input_number`][input_number docs]. [@tinloaf] added a feature that allows you to enter dates: [`input_datetime`][input_datetime docs]. Both will help you to improve your automation rules.
## DuckDNS
-Using Home Assistant with [DuckDNS](http://www.duckdns.org) for Dynamic DNS (DDNS or DynDNS) is an [old story](https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/). DuckDNS is also integrated in [Hass.io](https://home-assistant.io/addons/duckdns/). 0.55 ships a component for no Hass.io users to get a similar feature.
+Using Home Assistant with [DuckDNS](http://www.duckdns.org) for Dynamic DNS (DDNS or DynDNS) is an [old story](https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/). DuckDNS is also integrated in [Hass.io](https://home-assistant.io/addons/duckdns/). 0.55 ships a component for non Hass.io users to get a similar feature.
## Recorder
-The purging of data was [improved][recorder docs]. With `purge_interval` you can schedule regular purges of older events and states. In combination you can specify with `purge_keep_days` the amount of days you want to keep. The new service `recorder.purge` allow to handle this task when needed.
+The purging of data was [improved][recorder docs]. With `purge_interval` you can schedule regular purges of older events and states. In combination you can specify with `purge_keep_days` the amount of days you want to keep. The new service `recorder.purge` allows you to handle this task when needed.
## Owntracks
[Owntracks](http://owntracks.org/) is an easy way to track your devices. For some times we have the device tracker which depends on [MQTT][device_tracker.owntracks docs] but thanks to a new feature in Owntracks we can now offer support for HTTP. The [new platform][device_tracker.owntracks_http docs] doesn't require a MQTT broker but sends messages directly as HTTP requests to Home Assistant.
@@ -1619,467 +2145,6 @@ usps:
[camera.foscam docs]: https://home-assistant.io/components/camera.foscam/
[climate.ecobee docs]: https://home-assistant.io/components/climate.ecobee/
[device_tracker.icloud docs]: https://home-assistant.io/components/device_tracker.icloud/
-]]>
-
-
-
-
-
- 2017-08-12T00:11:05+00:00
- https://home-assistant.io/blog/2017/08/12/release-51
-
-
-
This release has to do a one time database migration which can take a long time on big databases (20 minutes). During this time the frontend will not work. Do not stop Home Assistant while it is in progress.
-
-Release 0.51 is around the corner and it contains some really great updates.
-
-## Database speed up
-
-The first one is more amazing database updates [#8748] by [@OverloadUT]. Every query that has been tested executes in well under 1 second, even on a RPi using MySQL with 6 million rows and around 300 entities. This is true even when you're getting an unrealistically huge date range!
-
-Updating the database will take some time when you start Home Assistant. During that time, the Home Assistant frontend is not accessible. Please let it complete and do not turn Home Assistant off.
-
-## Frontend update
-
-We have finished the migration of our frontend to be powered by Polymer 2. This has given us a big speed boost on Safari/iOS devices and has fixed a wide range of bugs.
-
-We have also finished the automation editor. All triggers and actions are now implemented and so are most conditions (missing are `and`, `or`). The automation editor is also no longer Chrome only, it can now also be used in Safari.
-
-Another change to the frontend is that we have reorganized the panels. The Z-Wave and automation configuration panels have been merged into the configuration panel.
-
-
-
-
-
-## Vacuum cleaners
-
-As we have seen more vacuum cleaners land in Home Assistant, it was time to create an official component for them. That's why [@azogue] introduced the new vacuum cleaner component in [#8623]. This allows first class integration of vacuum cleaners in Home Assistant. Out of the box we will have Dyson, Xiamo and Roomba as supported platforms.
-
-## New Platforms
-
-- Added Lutron Caseta Scene Support ([@809694+kfcook] - [#8690]) ([lutron_caseta docs]) ([scene.lutron_caseta docs]) (new-platform)
-- New media_player platform for Russound devices using the RIO protocol ([@wickerwaka] - [#8448]) ([media_player.russound_rio docs]) (new-platform)
-- New component: bluesound ([@thrawnarn] - [#7192]) ([media_player.bluesound docs]) (new-platform)
-- Add mochad light component ([@mtreinish] - [#8476]) ([light.mochad docs]) (new-platform)
-- geizhals sensor component ([@JulianKahnert] - [#8458]) ([sensor.geizhals docs]) (new-platform)
-- Xiaomi vacuum as platform of new `vacuum` component derived from ToggleEntity, and services ([@azogue] - [#8623]) (breaking change) (new-platform)
-- Wi-Fi enabled Roomba support ([@pschmitt] - [#8825]) ([vacuum.roomba docs]) (new-platform)
-- Add support to Dyson 360 Eye robot vacuum using new vacuum platform ([@CharlesBlonde] - [#8852]) ([dyson docs]) ([vacuum docs]) ([fan.dyson docs]) ([sensor.dyson docs]) ([vacuum.dyson docs]) (new-platform)
-- Add Initial Mailbox panel and sensor ([@PhracturedBlue] - [#8233]) ([asterisk_mbox docs]) (new-platform)
-- Add Leviton Decora Smart WiFi Device Platform ([@tlyakhov] - [#8529]) ([light.decora_wifi docs]) (new-platform)
-- Add RainMachine switch platform ([@bachya] - [#8827]) ([switch.rainmachine docs]) (new-platform)
-- Add new device tracker for Huawei Routers. ([@abmantis] - [#8488]) ([device_tracker.huawei_router docs]) (new-platform)
-- Add Shodan sensor ([@fabaff] - [#8902]) ([sensor.shodan docs]) (new-platform)
-
-## Release 0.51.1 - August 12
-
- - Fixed a bug in the automation editor that would break if no conditions available in the config file. ([@balloob])
-
-## Release 0.51.2 - August 14
-
-- Fix zwave power_consumption attribute ([@andrey-git] - [#8968]) ([zwave docs])
-- Turn foscam verbose mode off ([@andrey-git] - [#8967]) ([camera.foscam docs])
-- fix stack trace in pushbullet ([@Danielhiversen] - [#8965]) ([notify.pushbullet docs])
-- Harmoney remote: Fix call to ha_send_commands ([@MartinHjelmare] - [#8956]) ([remote.harmony docs])
-- fix DeviceException handling when updating xiaomi vacuum ([@azogue] - [#8954]) ([vacuum.xiaomi docs])
-- Sabnzbd: do not assume discovery info is a dict ([@balloob] - [#8951]) ([sensor.sabnzbd docs])
-- Fix login button ([@balloob])
-- Add workaround for broken toggles in Safari ([@balloob])
-- Fix weblink opening twice ([@azogue])
-
-## If you need help...
-...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. 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.
-
-
-## Breaking Changes
-
-- Efergy sensors: change units from KW to W ([@emlt] - [#8761]) ([sensor.efergy docs]) (breaking change)
-- Xiaomi vacuum is now a platform of new `vacuum` component derived from ToggleEntity, and services ([@azogue] - [#8623]) (breaking change) (new-platform)
-
-```yaml
-vacuum:
-- platform: xiaomi
- name: Vacuum cleaner
- host: !secret xiaomi_vacuum_robot_ip
- token: !secret xiaomi_vacuum_robot_token
-```
-
-## All changes
-
-- Upgrade pushbullet.py to 0.11.0 ([@fabaff] - [#8691]) ([notify.pushbullet docs])
-- Upgrade mypy to 0.521 ([@fabaff] - [#8692])
-- Added Lutron Caseta Scene Support ([@809694+kfcook] - [#8690]) ([lutron_caseta docs]) ([scene.lutron_caseta docs]) (new-platform)
-- Remove deprecated host and ssl logic from Kodi ([@armills] - [#8700]) ([media_player.kodi docs])
-- Remove deprecated substitute interfaces ([@armills] - [#8701]) ([binary_sensor docs]) ([media_player docs])
-- Remove deprecated sensor_class config options ([@armills] - [#8702])
-- directv: add configuration glue for Genie slaves ([@sielicki] - [#8713]) ([media_player.directv docs])
-- bump python-telegram-bot to 7.0.1 for fully support Bot API 3.2 ([@azogue] - [#8715]) ([telegram_bot docs])
-- Add proxy support for telegram_bot ([@azogue] - [#8717]) ([telegram_bot docs])
-- python-insteonplm module version bump ([@nugget] - [#8736]) ([insteon_plm docs])
-- New media_player platform for Russound devices using the RIO protocol ([@wickerwaka] - [#8448]) ([media_player.russound_rio docs]) (new-platform)
-- Add toggle to remotes ([@alanfischer] - [#8483]) ([remote docs]) ([remote.apple_tv docs]) ([remote.harmony docs]) ([remote.itach docs])
-- added invert_state optional parameter ([@gwhiteCL] - [#8695]) ([cover.rpi_gpio docs])
-- buienradar dates tz-aware ([@mjj4791] - [#8767]) ([sensor.buienradar docs]) ([weather.buienradar docs])
-- Change units from KW to W ([@emlt] - [#8761]) ([sensor.efergy docs]) (breaking change)
-- Clean up remote component ([@MartinHjelmare] - [#8728]) ([remote docs]) ([remote.apple_tv docs]) ([remote.harmony docs]) ([remote.itach docs]) ([remote.kira docs])
-- Wink discovery ([@w1ll1am23] - [#8739]) ([wink docs])
-- Enable/Disable Motion detection for Foscam Cameras ([@viswa-swami] - [#8582]) ([camera.foscam docs])
-- Allow sonos to select playlists as a source ([@mcolyer] - [#8258]) ([media_player.sonos docs])
-- mpd improvements ([@StevenLooman] - [#8655]) ([media_player.mpd docs])
-- Add support for file attachments in pushbullet ([@tsvi] - [#8763]) ([notify.pushbullet docs])
-- Honeywell fixes and improvements ([@dansarginson] - [#8756]) ([climate.honeywell docs])
-- Catch exception (fixes #8724) ([@fabaff] - [#8731]) ([sensor.google_wifi docs])
-- use updated osram lightify 1.0.6 component, including bugfix allowing more than 27 devices ([@tfriedel] - [#8774]) ([light.osramlightify docs])
-- flux_led: support for property "available" ([@pezinek] - [#8764]) ([light.flux_led docs])
-- New component: bluesound ([@thrawnarn] - [#7192]) ([media_player.bluesound docs]) (new-platform)
-- Add 'forecast' ability to yr weather sensor ([@tinloaf] - [#8650]) ([sensor.yr docs])
-- Feature alexa launch request ([@steverhoades] - [#8730]) ([alexa docs])
-- Fixes UnboundLocalError: local variable 'setting' referenced before assignment ([@syssi] - [#8782]) ([climate.tado docs])
-- Upgrade pyasn1 to 0.3.1 and pyasn1-modules to 0.0.10 ([@fabaff] - [#8787]) ([notify.xmpp docs])
-- Upgrade sphinx-autodoc-typehints to 1.2.1 ([@fabaff] - [#8783])
-- Improvements (configuration and validation) ([@fabaff] - [#8785]) ([sensor.yr docs])
-- Fix referencing unset variable in tado climate component (causes update to fail when tado zone is in manual mode) ([@luukd] - [#8723]) ([climate.tado docs])
-- mqtt switch: add voluptuous for availability topic ([@abmantis] - [#8797]) ([switch.mqtt docs])
-- Add mochad light component ([@mtreinish] - [#8476]) ([light.mochad docs]) (new-platform)
-- Update numpy 1.13.1 ([@pvizeli] - [#8806]) ([image_processing.opencv docs])
-- Upgrade aiohttp to 2.2.4 ([@fabaff] - [#8805])
-- Catch divide by zero errors when a sleep type is 0 ([@mezz64] - [#8809]) ([sensor.eight_sleep docs])
-- InfluxDB component improvements ([@hageltech] - [#8633]) ([influxdb docs])
-- When Sonos gets a tts source - dont't show an image ([@andrey-git] - [#8777]) ([media_player.sonos docs])
-- Polymer 2 ([@balloob] - [#8815]) ([group docs])
-- geizhals sensor component ([@JulianKahnert] - [#8458]) ([sensor.geizhals docs]) (new-platform)
-- Xiaomi vacuum as platform of new `vacuum` component derived from ToggleEntity, and services ([@azogue] - [#8623]) (breaking change) (new-platform)
-- Update yweather.py ([@fanthos] - [#8820]) ([weather.yweather docs])
-- Make HA discover sabnzbd and add it to the Configurator ([@Hellowlol] - [#8634]) ([sensor.sabnzbd docs])
-- Fix Dyson sensors if devices are configured without standby monitoring. Fixes #8569 ([@CharlesBlonde] - [#8826]) ([dyson docs]) ([fan.dyson docs]) ([sensor.dyson docs])
-- Block dependencies that depend on enum34 ([@balloob] - [#8698])
-- Upgrade aiohttp to 2.2.5 ([@fabaff] - [#8828])
-- History query and schema optimizations for huge performance boost ([@OverloadUT] - [#8748]) ([history docs]) (breaking change)
-- Update xiaomi vacuum tests and include in coverage ([@azogue] - [#8845]) ([vacuum docs]) ([vacuum.xiaomi docs])
-- Egardia ([@jeroenterheerdt] - [#8389])
-- Do not call update() in constructor. ([@fabaff] - [#8837]) ([sensor.systemmonitor docs])
-- Upgrade sendgrid to 4.2.1 ([@fabaff] - [#8839])
-- Do not call update() in constructor ([@fabaff] - [#8840]) ([sensor.vasttrafik docs])
-- Make 'monitored_conditions' optional ([@fabaff] - [#8843]) ([sensor.radarr docs])
-- Do not call update() in constructor ([@fabaff] - [#8849]) ([sensor.synologydsm docs])
-- Make 'monitored_conditions' optional ([@fabaff] - [#8848]) ([sensor.sonarr docs])
-- Do not call update() in constructor ([@fabaff] - [#8847]) ([sensor.pocketcasts docs])
-- Catch ConnectionRefusedError ([@fabaff] - [#8844]) ([sensor.supervisord docs])
-- Upgrade sqlalchemy to 1.1.13 ([@fabaff] - [#8850]) ([recorder docs])
-- Upgrade pylast to 1.9.0 ([@fabaff] - [#8854]) ([sensor.lastfm docs])
-- Wi-Fi enabled Roomba support ([@pschmitt] - [#8825]) ([vacuum.roomba docs]) (new-platform)
-- Add support to Dyson 360 Eye robot vacuum using new vacuum platform ([@CharlesBlonde] - [#8852]) ([dyson docs]) ([vacuum docs]) ([fan.dyson docs]) ([sensor.dyson docs]) ([vacuum.dyson docs]) (new-platform)
-- Upgrade pyasn1 to 0.3.2 and pyasn1-modules to 0.0.11 ([@fabaff] - [#8856]) ([notify.xmpp docs])
-- Allow to set coordinates ([@fabaff] - [#8858]) ([sensor.zamg docs]) ([weather.zamg docs])
-- Added rounding to Google Wifi ([@fronzbot] - [#8866]) ([sensor.google_wifi docs])
-- Fix off_delay for zwave trigger sensors ([@turbokongen] - [#8864]) ([zwave docs]) ([binary_sensor.zwave docs])
-- Do not use pychromecast.Chromecast for Cast Groups ([@foxel] - [#8786]) ([media_player.cast docs])
-- Allow get local ip to work without internet ([@balloob] - [#8855])
-- Do not call update() in constructor ([@fabaff] - [#8859])
-- Add new service `clean_spot` to vacuums ([@azogue] - [#8862]) ([vacuum docs]) ([vacuum.xiaomi docs])
-- Warn instead of raise on duplicate YAML key ([@balloob] - [#8834])
-- Add Initial Mailbox panel and sensor ([@PhracturedBlue] - [#8233]) ([asterisk_mbox docs]) (new-platform)
-- Add Leviton Decora Smart WiFi Device Platform ([@tlyakhov] - [#8529]) ([light.decora_wifi docs]) (new-platform)
-- Consolidate config panels ([@balloob] - [#8857]) ([automation docs]) ([zwave docs])
-- Fix spelling error and update link ([@Klikini] - [#8869])
-- Implement Roomba fan speed ([@pschmitt] - [#8863]) ([vacuum.roomba docs])
-- Add nuki lock'n'go and unlatch services and add attributes ([@pschmitt] - [#8687]) ([lock.nuki docs])
-- RFLink: Add send_command service ([@leppa] - [#8876]) ([rflink docs])
-- Do not call update() in constructor ([@fabaff] - [#8881]) ([binary_sensor.rest docs]) ([sensor.rest docs])
-- Add RainMachine switch platform ([@bachya] - [#8827]) ([switch.rainmachine docs]) (new-platform)
-- Allow usage of colorlog 3.0.1 ([@fabaff] - [#8885])
-- Change level ([@fabaff] - [#8883]) ([sensor.statistics docs])
-- Upgrade youtube_dl to 2017.8.6 ([@fabaff] - [#8880]) ([media_extractor docs])
-- Fix media_extractor for some sites ([@Spirit-X] - [#8887]) ([media_extractor docs])
-- Do not call update() in constructor ([@fabaff] - [#8878])
-- Do not call update() in constructor ([@fabaff] - [#8892]) ([binary_sensor.command_line docs]) ([sensor.command_line docs]) ([switch.command_line docs])
-- Changed Pi-hole graphs from stacked bar to line ([@bachya] - [#8896]) ([sensor.pi_hole docs])
-- Add longer text strings to mailbox demo to test string truncation ([@PhracturedBlue] - [#8893]) ([mailbox.demo docs]) ([mailbox.demo.txt docs])
-- added support for setting/getting position of lutron caseta covers ([@809694+kfcook] - [#8898]) ([cover.lutron_caseta docs])
-- Fix for Neato D3 Connected state obtaining ([@karlkar] - [#8817]) ([sensor.neato docs]) ([switch.neato docs])
-- Update simplisafe-python version ([@w1ll1am23] - [#8908]) ([alarm_control_panel.simplisafe docs])
-- LIFX: improve performance of multi-light transitions ([@amelchio] - [#8873]) ([light.lifx docs])
-- Support media position and media duration (will display progressbar in ui) ([@molobrakos] - [#8904]) ([media_player.squeezebox docs])
-- Add new device tracker for Huawei Routers. ([@abmantis] - [#8488]) ([device_tracker.huawei_router docs]) (new-platform)
-- Add Shodan sensor ([@fabaff] - [#8902]) ([sensor.shodan docs]) (new-platform)
-- Added possibilities to use template in the command_line sensor ([@mar-schmidt] - [#8505]) ([sensor.command_line docs])
-- Honor PEP8 naming convention ([@fabaff] - [#8909]) ([updater docs])
-- Remove not needed call to update ([@MartinHjelmare] - [#8930]) ([switch.rachio docs])
-- fixing emulated hue issue and testing it ([@cribbstechnologies] - [#8928]) ([emulated_hue docs])
-- Update roombapy to 1.3.1 to avoid installing all the mapping dependencies ([@pschmitt] - [#8925]) ([vacuum.roomba docs])
-- Update python-wink version to fix Dome water valve bug. ([@w1ll1am23] - [#8923]) ([wink docs]) ([switch.wink docs])
-- Fix SET_TEMPERATURE_SCHEMA in climate component ([@MartinHjelmare] - [#8879]) ([climate docs])
-
-[#7192]: https://github.com/home-assistant/home-assistant/pull/7192
-[#8233]: https://github.com/home-assistant/home-assistant/pull/8233
-[#8258]: https://github.com/home-assistant/home-assistant/pull/8258
-[#8389]: https://github.com/home-assistant/home-assistant/pull/8389
-[#8448]: https://github.com/home-assistant/home-assistant/pull/8448
-[#8458]: https://github.com/home-assistant/home-assistant/pull/8458
-[#8476]: https://github.com/home-assistant/home-assistant/pull/8476
-[#8483]: https://github.com/home-assistant/home-assistant/pull/8483
-[#8488]: https://github.com/home-assistant/home-assistant/pull/8488
-[#8505]: https://github.com/home-assistant/home-assistant/pull/8505
-[#8529]: https://github.com/home-assistant/home-assistant/pull/8529
-[#8582]: https://github.com/home-assistant/home-assistant/pull/8582
-[#8623]: https://github.com/home-assistant/home-assistant/pull/8623
-[#8633]: https://github.com/home-assistant/home-assistant/pull/8633
-[#8634]: https://github.com/home-assistant/home-assistant/pull/8634
-[#8650]: https://github.com/home-assistant/home-assistant/pull/8650
-[#8655]: https://github.com/home-assistant/home-assistant/pull/8655
-[#8687]: https://github.com/home-assistant/home-assistant/pull/8687
-[#8690]: https://github.com/home-assistant/home-assistant/pull/8690
-[#8691]: https://github.com/home-assistant/home-assistant/pull/8691
-[#8692]: https://github.com/home-assistant/home-assistant/pull/8692
-[#8695]: https://github.com/home-assistant/home-assistant/pull/8695
-[#8698]: https://github.com/home-assistant/home-assistant/pull/8698
-[#8700]: https://github.com/home-assistant/home-assistant/pull/8700
-[#8701]: https://github.com/home-assistant/home-assistant/pull/8701
-[#8702]: https://github.com/home-assistant/home-assistant/pull/8702
-[#8713]: https://github.com/home-assistant/home-assistant/pull/8713
-[#8715]: https://github.com/home-assistant/home-assistant/pull/8715
-[#8717]: https://github.com/home-assistant/home-assistant/pull/8717
-[#8723]: https://github.com/home-assistant/home-assistant/pull/8723
-[#8728]: https://github.com/home-assistant/home-assistant/pull/8728
-[#8730]: https://github.com/home-assistant/home-assistant/pull/8730
-[#8731]: https://github.com/home-assistant/home-assistant/pull/8731
-[#8736]: https://github.com/home-assistant/home-assistant/pull/8736
-[#8739]: https://github.com/home-assistant/home-assistant/pull/8739
-[#8748]: https://github.com/home-assistant/home-assistant/pull/8748
-[#8756]: https://github.com/home-assistant/home-assistant/pull/8756
-[#8761]: https://github.com/home-assistant/home-assistant/pull/8761
-[#8763]: https://github.com/home-assistant/home-assistant/pull/8763
-[#8764]: https://github.com/home-assistant/home-assistant/pull/8764
-[#8767]: https://github.com/home-assistant/home-assistant/pull/8767
-[#8774]: https://github.com/home-assistant/home-assistant/pull/8774
-[#8777]: https://github.com/home-assistant/home-assistant/pull/8777
-[#8782]: https://github.com/home-assistant/home-assistant/pull/8782
-[#8783]: https://github.com/home-assistant/home-assistant/pull/8783
-[#8785]: https://github.com/home-assistant/home-assistant/pull/8785
-[#8786]: https://github.com/home-assistant/home-assistant/pull/8786
-[#8787]: https://github.com/home-assistant/home-assistant/pull/8787
-[#8797]: https://github.com/home-assistant/home-assistant/pull/8797
-[#8805]: https://github.com/home-assistant/home-assistant/pull/8805
-[#8806]: https://github.com/home-assistant/home-assistant/pull/8806
-[#8809]: https://github.com/home-assistant/home-assistant/pull/8809
-[#8815]: https://github.com/home-assistant/home-assistant/pull/8815
-[#8817]: https://github.com/home-assistant/home-assistant/pull/8817
-[#8820]: https://github.com/home-assistant/home-assistant/pull/8820
-[#8825]: https://github.com/home-assistant/home-assistant/pull/8825
-[#8826]: https://github.com/home-assistant/home-assistant/pull/8826
-[#8827]: https://github.com/home-assistant/home-assistant/pull/8827
-[#8828]: https://github.com/home-assistant/home-assistant/pull/8828
-[#8834]: https://github.com/home-assistant/home-assistant/pull/8834
-[#8837]: https://github.com/home-assistant/home-assistant/pull/8837
-[#8839]: https://github.com/home-assistant/home-assistant/pull/8839
-[#8840]: https://github.com/home-assistant/home-assistant/pull/8840
-[#8843]: https://github.com/home-assistant/home-assistant/pull/8843
-[#8844]: https://github.com/home-assistant/home-assistant/pull/8844
-[#8845]: https://github.com/home-assistant/home-assistant/pull/8845
-[#8847]: https://github.com/home-assistant/home-assistant/pull/8847
-[#8848]: https://github.com/home-assistant/home-assistant/pull/8848
-[#8849]: https://github.com/home-assistant/home-assistant/pull/8849
-[#8850]: https://github.com/home-assistant/home-assistant/pull/8850
-[#8852]: https://github.com/home-assistant/home-assistant/pull/8852
-[#8854]: https://github.com/home-assistant/home-assistant/pull/8854
-[#8855]: https://github.com/home-assistant/home-assistant/pull/8855
-[#8856]: https://github.com/home-assistant/home-assistant/pull/8856
-[#8857]: https://github.com/home-assistant/home-assistant/pull/8857
-[#8858]: https://github.com/home-assistant/home-assistant/pull/8858
-[#8859]: https://github.com/home-assistant/home-assistant/pull/8859
-[#8862]: https://github.com/home-assistant/home-assistant/pull/8862
-[#8863]: https://github.com/home-assistant/home-assistant/pull/8863
-[#8864]: https://github.com/home-assistant/home-assistant/pull/8864
-[#8866]: https://github.com/home-assistant/home-assistant/pull/8866
-[#8869]: https://github.com/home-assistant/home-assistant/pull/8869
-[#8873]: https://github.com/home-assistant/home-assistant/pull/8873
-[#8876]: https://github.com/home-assistant/home-assistant/pull/8876
-[#8878]: https://github.com/home-assistant/home-assistant/pull/8878
-[#8879]: https://github.com/home-assistant/home-assistant/pull/8879
-[#8880]: https://github.com/home-assistant/home-assistant/pull/8880
-[#8881]: https://github.com/home-assistant/home-assistant/pull/8881
-[#8883]: https://github.com/home-assistant/home-assistant/pull/8883
-[#8885]: https://github.com/home-assistant/home-assistant/pull/8885
-[#8887]: https://github.com/home-assistant/home-assistant/pull/8887
-[#8892]: https://github.com/home-assistant/home-assistant/pull/8892
-[#8893]: https://github.com/home-assistant/home-assistant/pull/8893
-[#8896]: https://github.com/home-assistant/home-assistant/pull/8896
-[#8898]: https://github.com/home-assistant/home-assistant/pull/8898
-[#8902]: https://github.com/home-assistant/home-assistant/pull/8902
-[#8904]: https://github.com/home-assistant/home-assistant/pull/8904
-[#8908]: https://github.com/home-assistant/home-assistant/pull/8908
-[#8909]: https://github.com/home-assistant/home-assistant/pull/8909
-[#8923]: https://github.com/home-assistant/home-assistant/pull/8923
-[#8925]: https://github.com/home-assistant/home-assistant/pull/8925
-[#8928]: https://github.com/home-assistant/home-assistant/pull/8928
-[#8930]: https://github.com/home-assistant/home-assistant/pull/8930
-[@809694+kfcook]: https://github.com/809694+kfcook
-[@CharlesBlonde]: https://github.com/CharlesBlonde
-[@Hellowlol]: https://github.com/Hellowlol
-[@JulianKahnert]: https://github.com/JulianKahnert
-[@Klikini]: https://github.com/Klikini
-[@MartinHjelmare]: https://github.com/MartinHjelmare
-[@OverloadUT]: https://github.com/OverloadUT
-[@PhracturedBlue]: https://github.com/PhracturedBlue
-[@Spirit-X]: https://github.com/Spirit-X
-[@StevenLooman]: https://github.com/StevenLooman
-[@abmantis]: https://github.com/abmantis
-[@alanfischer]: https://github.com/alanfischer
-[@amelchio]: https://github.com/amelchio
-[@andrey-git]: https://github.com/andrey-git
-[@armills]: https://github.com/armills
-[@azogue]: https://github.com/azogue
-[@bachya]: https://github.com/bachya
-[@balloob]: https://github.com/balloob
-[@cribbstechnologies]: https://github.com/cribbstechnologies
-[@dansarginson]: https://github.com/dansarginson
-[@emlt]: https://github.com/emlt
-[@fabaff]: https://github.com/fabaff
-[@fanthos]: https://github.com/fanthos
-[@foxel]: https://github.com/foxel
-[@fronzbot]: https://github.com/fronzbot
-[@gwhiteCL]: https://github.com/gwhiteCL
-[@hageltech]: https://github.com/hageltech
-[@jeroenterheerdt]: https://github.com/jeroenterheerdt
-[@karlkar]: https://github.com/karlkar
-[@leppa]: https://github.com/leppa
-[@luukd]: https://github.com/luukd
-[@mar-schmidt]: https://github.com/mar-schmidt
-[@mcolyer]: https://github.com/mcolyer
-[@mezz64]: https://github.com/mezz64
-[@mjj4791]: https://github.com/mjj4791
-[@molobrakos]: https://github.com/molobrakos
-[@mtreinish]: https://github.com/mtreinish
-[@nugget]: https://github.com/nugget
-[@pezinek]: https://github.com/pezinek
-[@pschmitt]: https://github.com/pschmitt
-[@pvizeli]: https://github.com/pvizeli
-[@sielicki]: https://github.com/sielicki
-[@steverhoades]: https://github.com/steverhoades
-[@syssi]: https://github.com/syssi
-[@tfriedel]: https://github.com/tfriedel
-[@thrawnarn]: https://github.com/thrawnarn
-[@tinloaf]: https://github.com/tinloaf
-[@tlyakhov]: https://github.com/tlyakhov
-[@tsvi]: https://github.com/tsvi
-[@turbokongen]: https://github.com/turbokongen
-[@viswa-swami]: https://github.com/viswa-swami
-[@w1ll1am23]: https://github.com/w1ll1am23
-[@wickerwaka]: https://github.com/wickerwaka
-[alarm_control_panel.simplisafe docs]: https://home-assistant.io/components/alarm_control_panel.simplisafe/
-[alexa docs]: https://home-assistant.io/components/alexa/
-[asterisk_mbox docs]: https://home-assistant.io/components/asterisk_mbox/
-[automation docs]: https://home-assistant.io/components/automation/
-[binary_sensor docs]: https://home-assistant.io/components/binary_sensor/
-[binary_sensor.command_line docs]: https://home-assistant.io/components/binary_sensor.command_line/
-[binary_sensor.rest docs]: https://home-assistant.io/components/binary_sensor.rest/
-[binary_sensor.zwave docs]: https://home-assistant.io/components/binary_sensor.zwave/
-[camera.foscam docs]: https://home-assistant.io/components/camera.foscam/
-[climate docs]: https://home-assistant.io/components/climate/
-[climate.honeywell docs]: https://home-assistant.io/components/climate.honeywell/
-[climate.tado docs]: https://home-assistant.io/components/climate.tado/
-[config.zwave docs]: https://home-assistant.io/components/config.zwave/
-[cover.lutron_caseta docs]: https://home-assistant.io/components/cover.lutron_caseta/
-[cover.rpi_gpio docs]: https://home-assistant.io/components/cover.rpi_gpio/
-[device_tracker.huawei_router docs]: https://home-assistant.io/components/device_tracker.huawei_router/
-[dyson docs]: https://home-assistant.io/components/dyson/
-[emulated_hue docs]: https://home-assistant.io/components/emulated_hue/
-[fan.dyson docs]: https://home-assistant.io/components/fan.dyson/
-[group docs]: https://home-assistant.io/components/group/
-[history docs]: https://home-assistant.io/components/history/
-[image_processing.opencv docs]: https://home-assistant.io/components/image_processing.opencv/
-[influxdb docs]: https://home-assistant.io/components/influxdb/
-[insteon_plm docs]: https://home-assistant.io/components/insteon_plm/
-[light.decora_wifi docs]: https://home-assistant.io/components/light.decora_wifi/
-[light.flux_led docs]: https://home-assistant.io/components/light.flux_led/
-[light.lifx docs]: https://home-assistant.io/components/light.lifx/
-[light.mochad docs]: https://home-assistant.io/components/light.mochad/
-[light.osramlightify docs]: https://home-assistant.io/components/light.osramlightify/
-[lock.nuki docs]: https://home-assistant.io/components/lock.nuki/
-[lutron_caseta docs]: https://home-assistant.io/components/lutron_caseta/
-[mailbox.demo docs]: https://home-assistant.io/components/mailbox.demo/
-[mailbox.demo.txt docs]: https://home-assistant.io/components/mailbox.demo.txt/
-[media_extractor docs]: https://home-assistant.io/components/media_extractor/
-[media_player docs]: https://home-assistant.io/components/media_player/
-[media_player.bluesound docs]: https://home-assistant.io/components/media_player.bluesound/
-[media_player.cast docs]: https://home-assistant.io/components/media_player.cast/
-[media_player.directv docs]: https://home-assistant.io/components/media_player.directv/
-[media_player.kodi docs]: https://home-assistant.io/components/media_player.kodi/
-[media_player.mpd docs]: https://home-assistant.io/components/media_player.mpd/
-[media_player.russound_rio docs]: https://home-assistant.io/components/media_player.russound_rio/
-[media_player.sonos docs]: https://home-assistant.io/components/media_player.sonos/
-[media_player.squeezebox docs]: https://home-assistant.io/components/media_player.squeezebox/
-[notify.pushbullet docs]: https://home-assistant.io/components/notify.pushbullet/
-[notify.xmpp docs]: https://home-assistant.io/components/notify.xmpp/
-[recorder docs]: https://home-assistant.io/components/recorder/
-[recorder.migration docs]: https://home-assistant.io/components/recorder.migration/
-[recorder.models docs]: https://home-assistant.io/components/recorder.models/
-[recorder.purge docs]: https://home-assistant.io/components/recorder.purge/
-[recorder.util docs]: https://home-assistant.io/components/recorder.util/
-[remote docs]: https://home-assistant.io/components/remote/
-[remote.apple_tv docs]: https://home-assistant.io/components/remote.apple_tv/
-[remote.demo docs]: https://home-assistant.io/components/remote.demo/
-[remote.harmony docs]: https://home-assistant.io/components/remote.harmony/
-[remote.itach docs]: https://home-assistant.io/components/remote.itach/
-[remote.kira docs]: https://home-assistant.io/components/remote.kira/
-[rflink docs]: https://home-assistant.io/components/rflink/
-[scene.lutron_caseta docs]: https://home-assistant.io/components/scene.lutron_caseta/
-[sensor.asterisk_mbox docs]: https://home-assistant.io/components/sensor.asterisk_mbox/
-[sensor.buienradar docs]: https://home-assistant.io/components/sensor.buienradar/
-[sensor.command_line docs]: https://home-assistant.io/components/sensor.command_line/
-[sensor.dyson docs]: https://home-assistant.io/components/sensor.dyson/
-[sensor.efergy docs]: https://home-assistant.io/components/sensor.efergy/
-[sensor.eight_sleep docs]: https://home-assistant.io/components/sensor.eight_sleep/
-[sensor.geizhals docs]: https://home-assistant.io/components/sensor.geizhals/
-[sensor.google_wifi docs]: https://home-assistant.io/components/sensor.google_wifi/
-[sensor.lastfm docs]: https://home-assistant.io/components/sensor.lastfm/
-[sensor.neato docs]: https://home-assistant.io/components/sensor.neato/
-[sensor.pi_hole docs]: https://home-assistant.io/components/sensor.pi_hole/
-[sensor.pocketcasts docs]: https://home-assistant.io/components/sensor.pocketcasts/
-[sensor.radarr docs]: https://home-assistant.io/components/sensor.radarr/
-[sensor.rest docs]: https://home-assistant.io/components/sensor.rest/
-[sensor.sabnzbd docs]: https://home-assistant.io/components/sensor.sabnzbd/
-[sensor.shodan docs]: https://home-assistant.io/components/sensor.shodan/
-[sensor.sonarr docs]: https://home-assistant.io/components/sensor.sonarr/
-[sensor.statistics docs]: https://home-assistant.io/components/sensor.statistics/
-[sensor.supervisord docs]: https://home-assistant.io/components/sensor.supervisord/
-[sensor.synologydsm docs]: https://home-assistant.io/components/sensor.synologydsm/
-[sensor.systemmonitor docs]: https://home-assistant.io/components/sensor.systemmonitor/
-[sensor.vasttrafik docs]: https://home-assistant.io/components/sensor.vasttrafik/
-[sensor.yr docs]: https://home-assistant.io/components/sensor.yr/
-[sensor.zamg docs]: https://home-assistant.io/components/sensor.zamg/
-[switch.command_line docs]: https://home-assistant.io/components/switch.command_line/
-[switch.mqtt docs]: https://home-assistant.io/components/switch.mqtt/
-[switch.neato docs]: https://home-assistant.io/components/switch.neato/
-[switch.rachio docs]: https://home-assistant.io/components/switch.rachio/
-[switch.rainmachine docs]: https://home-assistant.io/components/switch.rainmachine/
-[switch.wink docs]: https://home-assistant.io/components/switch.wink/
-[switch.xiaomi_vacuum docs]: https://home-assistant.io/components/switch.xiaomi_vacuum/
-[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
-[updater docs]: https://home-assistant.io/components/updater/
-[vacuum docs]: https://home-assistant.io/components/vacuum/
-[vacuum.demo docs]: https://home-assistant.io/components/vacuum.demo/
-[vacuum.dyson docs]: https://home-assistant.io/components/vacuum.dyson/
-[vacuum.roomba docs]: https://home-assistant.io/components/vacuum.roomba/
-[vacuum.xiaomi docs]: https://home-assistant.io/components/vacuum.xiaomi/
-[weather.buienradar docs]: https://home-assistant.io/components/weather.buienradar/
-[weather.yweather docs]: https://home-assistant.io/components/weather.yweather/
-[weather.zamg docs]: https://home-assistant.io/components/weather.zamg/
-[wink docs]: https://home-assistant.io/components/wink/
-[zwave docs]: https://home-assistant.io/components/zwave/
-[forum]: https://community.home-assistant.io/
-[issue]: https://github.com/home-assistant/home-assistant/issues
-[discord]: https://discord.gg/c5DvZ4e
-[#8951]: https://github.com/home-assistant/home-assistant/pull/8951
-[#8954]: https://github.com/home-assistant/home-assistant/pull/8954
-[#8956]: https://github.com/home-assistant/home-assistant/pull/8956
-[#8965]: https://github.com/home-assistant/home-assistant/pull/8965
-[#8967]: https://github.com/home-assistant/home-assistant/pull/8967
-[#8968]: https://github.com/home-assistant/home-assistant/pull/8968
-[@Danielhiversen]: https://github.com/Danielhiversen
]]>
diff --git a/blog/categories/release-notes/index.html b/blog/categories/release-notes/index.html
index b5970e4a34..9550a4388c 100644
--- a/blog/categories/release-notes/index.html
+++ b/blog/categories/release-notes/index.html
@@ -23,7 +23,7 @@
-
+
@@ -79,6 +79,27 @@
diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml
index c44ed6914c..6066f8fabb 100644
--- a/blog/categories/technology/atom.xml
+++ b/blog/categories/technology/atom.xml
@@ -4,7 +4,7 @@
- 2017-10-21T21:10:30+00:00
+ 2017-10-21T23:25:10+00:00https://home-assistant.io/
@@ -34,7 +34,7 @@ If you're running Hassbian it's recommended that you make a backup of your confi
If you're on Windows, you're fine as our minimum version for Windows has been 3.5 for a while now.
#### Other Debian based systems
-If you're running a Debian based system , follow [these instructions][dist-upgrade] to upgrade.
+If you're running a Debian based system, follow [these instructions][dist-upgrade] to upgrade.
[dist-upgrade]: https://linuxconfig.org/raspbian-gnu-linux-upgrade-from-jessie-to-raspbian-stretch-9
]]>
diff --git a/blog/categories/technology/index.html b/blog/categories/technology/index.html
index c9d8abd0db..c491f1d18d 100644
--- a/blog/categories/technology/index.html
+++ b/blog/categories/technology/index.html
@@ -23,7 +23,7 @@
-
+
@@ -305,6 +305,9 @@
We reached another milestone aka number: 10000. GitHub is assigning numbers to pull requests and issues and the “10000” is a PR. Our ratio is around 1/3 issues and 2/3 pull requests. To be more precise: 64% pull requests and 36% issues.
+
If you haven’t noticed, there is now a glossary that collects some Home Assistant relevant terms. Talking about the documentation: @DubhAd rewrote large parts of the Z-Wave section. More structure to get started and to find details during the setup and the configuration.
+
Google Assistant / Google Home integration
+
This release includes a new component to integrate Home Assistant with Google Assistant by Phil Kates. We integrate via the Smart Home API, this means that you will be able to control your devices in Home Assistant via any device that has Google Assistant. Learn more in the documentation.
+
Hacktoberfest
+
Hacktoberfest is still on and so far we have received a lot improvements. We can’t make any promises to review everything by the end of October, but we are trying to make sure that you will get your t-shirt.
+
Map
+
The map is now its own component. Similar to configuration (config:), it will not show up without adding it to your configuration.yaml file.
+
map:
+
+
+
Travis CI
+
Why not observe your Travis CI jobs with Home Assistant? @tchellomello created a Travis CI sensor which allows one to check on the current state of Travis jobs. Now you can make sure that the coffee is ready when the build passed.
…don’t hesitate to use our very active forums or join us for a little chat. 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. Make sure to fill in all fields of the issue template.
Beside the improved Wink support which was contributed by @w1ll1am23, ships this release a wide variety of new components and platforms. The input_slider components has received a makeover by @BioSehnsucht and is now input_number. @tinloaf added a feature that allows you to enter dates: input_datetime. Both will help you to improve your automation rules.
DuckDNS
-
Using Home Assistant with DuckDNS for Dynamic DNS (DDNS or DynDNS) is an old story. DuckDNS is also integrated in Hass.io. 0.55 ships a component for no Hass.io users to get a similar feature.
+
Using Home Assistant with DuckDNS for Dynamic DNS (DDNS or DynDNS) is an old story. DuckDNS is also integrated in Hass.io. 0.55 ships a component for non Hass.io users to get a similar feature.
Recorder
-
The purging of data was improved. With purge_interval you can schedule regular purges of older events and states. In combination you can specify with purge_keep_days the amount of days you want to keep. The new service recorder.purge allow to handle this task when needed.
+
The purging of data was improved. With purge_interval you can schedule regular purges of older events and states. In combination you can specify with purge_keep_days the amount of days you want to keep. The new service recorder.purge allows you to handle this task when needed.
Owntracks
Owntracks is an easy way to track your devices. For some times we have the device tracker which depends on MQTT but thanks to a new feature in Owntracks we can now offer support for HTTP. The new platform doesn’t require a MQTT broker but sends messages directly as HTTP requests to Home Assistant.
Tibber
@@ -219,7 +281,7 @@
Windows
If you’re on Windows, you’re fine as our minimum version for Windows has been 3.5 for a while now.
Other Debian based systems
-
If you’re running a Debian based system , follow these instructions to upgrade.
+
If you’re running a Debian based system, follow these instructions to upgrade.
This new release finally brings us the release of Hassbian based on the release of Raspbian Stretch. The most significant change with this is that we now run Home Assistant on Python 3.5.
-Other than that the changes are mostly to our tool hassbian-config.
-
Hassbian-config
-
To allow you to customize your installation further, we have made a few additions to our tool called hassbian-config. Majority of these changes where contributed by @Ludeeus.
-
Upgrade scripts
-
@Ludeeus contributed the possibility to run upgrade scripts to the hassbian-config tool.
-
-
Upgrade Hassbian: Upgrades packages of the base operating system. Contributed by @Landrash.
-
Upgrade Hassbian-script: Downloads and upgrades the latest release of Hassbian-scripts. Contributed by @Ludeeus.
-
Upgrade Home-assistant: Upgrades the Home Assistant installation to the latest release. Contributed by @Ludeeus.
-
-
To follow discussions about the development of the HASSbian image or to contribute join our Discord chat server.
-
To get started with the new image, check out the installation instructions on the installing Hassbian page.
Our community is amazingly helpful and creative. If you haven’t been there yet, make sure to stop by our chat room and come hang out with us. In this blog post I want to highlight a few recent awesome projects and videos from the community.
+
SceneGen - cli for making scenes
+
SceneGen is a new command line utility developed by Andrew Cockburn that helps with creating scene configurations for Home Assistant. To use it, you put your house in the preferred state, run SceneGen and it will print the scene configuration for your current states.
+
Videos
+
Nick Touran has been working on integrating IR remotes with Home Assistant. He made it into a component which should be available in the next release which should arrive in a couple of days. In the meanwhile, he wrote up a blog post and has put out a video showing the new integration, very cool!
+
+
+
+
Ben from BRUH Automation has put out another great video how to get started tracking your location in Home Assistant using MQTT and OwnTracks.
+
+
+
+
Muhammed Kilic has created a video how to make your Home Assistant instance accessible from the internet using the free dynamic DNS service DuckDNS.
After 2.5 years I think we can proudly say: Home Assistant is a success. I write we because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own organisation on GitHub.
-
On our journey we’ve reached many noteworthy milestones:
-
-
#1 on HackerNews
-
Featured on ProductHunt
-
Trending repository on GitHub
-
3000 stars on GitHub
-
1.5 million page views on our website
-
Speaker at OpenIoT Summit 2016
-
-
All these accomplishments are a nice pat on the back but our journey is far from over. There are a lot of challenges ahead if we want to become the go to solution for home automation for everyone.
-
Until now the focus has been on making a platform that developers love to use. A platform that is simple but customizable. A platform that is both powerful and reliable. But most important: a platform that is local and open. Home Assistant does a great job at all these things.
-
There will be some major challenges ahead of us to target groups other than developers. Easy installation and easy configuration being the #1. I’m sure that we’ll be able to eventually achieve these goals. I can’t say yet how or when. As with everything Home Assistant, we’ll take tiny steps, gathering feedback along the way to make sure we’re solving the right problems.
-
I am confident that we will get there because we are set up for success: we have a robust architecture, high test coverage and an active community of world class developers and users. On top of that, we use Python which allows us to move fast and tackle complex problems in elegant ways. It is so easy to learn that it allows any programmer, experienced or not, to contribute support for devices and services. It’s as simple as filling in the blanks.
-
I would like to put out a big thank you to all our contributors who make Home Assistant what it is today. It doesn’t matter if it is form of code, documentation or giving support in our chat room or forums. You. all. rock.
After 2.5 years I think we can proudly say: Home Assistant is a success. I write we because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own organisation on GitHub.
+
On our journey we’ve reached many noteworthy milestones:
+
+
#1 on HackerNews
+
Featured on ProductHunt
+
Trending repository on GitHub
+
3000 stars on GitHub
+
1.5 million page views on our website
+
Speaker at OpenIoT Summit 2016
+
+
All these accomplishments are a nice pat on the back but our journey is far from over. There are a lot of challenges ahead if we want to become the go to solution for home automation for everyone.
+
Until now the focus has been on making a platform that developers love to use. A platform that is simple but customizable. A platform that is both powerful and reliable. But most important: a platform that is local and open. Home Assistant does a great job at all these things.
+
There will be some major challenges ahead of us to target groups other than developers. Easy installation and easy configuration being the #1. I’m sure that we’ll be able to eventually achieve these goals. I can’t say yet how or when. As with everything Home Assistant, we’ll take tiny steps, gathering feedback along the way to make sure we’re solving the right problems.
+
I am confident that we will get there because we are set up for success: we have a robust architecture, high test coverage and an active community of world class developers and users. On top of that, we use Python which allows us to move fast and tackle complex problems in elegant ways. It is so easy to learn that it allows any programmer, experienced or not, to contribute support for devices and services. It’s as simple as filling in the blanks.
+
I would like to put out a big thank you to all our contributors who make Home Assistant what it is today. It doesn’t matter if it is form of code, documentation or giving support in our chat room or forums. You. all. rock.
+
Cheers to the future!
+
Paulus
+
+
+
@@ -489,69 +530,6 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
The focus of 0.13 was on test coverage, big cheers to @rmkraus for his hard work on this. I’m proud to announce that we’ve hit the 90% test coverage of the core + important components. A big milestone for the project.
The focus of 0.13 was on test coverage, big cheers to @rmkraus for his hard work on this. I’m proud to announce that we’ve hit the 90% test coverage of the core + important components. A big milestone for the project.
-Inspried by a feature requests I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the systemmonitor sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.
+Inspried by a feature requests I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the systemmonitor sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.
I have recently merged code to refactor Home Assistant to use only UTC times internally. A much needed refactor. I’ve added some extra test coverage to time sensitive parts to ensure stability. The code has been live in the dev branch for the last 9 days and will be soon released to the master branch.
-
From now on all internal communication will be done in UTC: time changed events, datetime attributes of states, etc. To get the current time in UTC you can call homeassistant.util.dt.utcnow(). This is a timezone aware UTC datetime object. homeassistant.util.dt is a new util package with date helpers.
-
There is also such a thing as local time. Local time is based on the time zone that you have setup in your configuration.yaml. Local times should only be used for user facing information: logs, frontend and automation settings in configuration.yaml.
-
Setting up your time zone
-
Setting up a time zone happens in configuration.yaml. If you have no time zone setup, it will be auto detected using the existing detection code using freegeoip.net. You can find a list of compatible time zones on Wikipedia.
-
homeassistant:
- time_zone:America/Los_Angeles
-
-
-
Compatibility
-
The changes to the code are mostly backwards compatible. The old hass.track_time_change and hass.track_point_in_time use now internally two new methods: hass.track_utc_time_change and hass.track_point_in_utc_time. The usage of the old methods have not changed and should be backwards compatible.
-
This refactor adds a new migration for the database adding a utc_offset column to events and states. This information is currently not used but can prove useful in the future when we start analyzing the historical data.
-
Backwards incompatible stuff
-
All built-in components have been upgraded. The following list is only for people that run custom components:
-
-
hass.track_time_change and hass.track_point_in_time will now return a time zone aware datetime object. Python does not allow comparing a naive with an aware datetime object.
-
the sun attributes for rising and setting are now in UTC. The methods sun.next_rising(hass) and sun.next_setting(hass) are backwards compatible, just be careful if you used to read the raw attributes.
-
the API sends all times in UTC. If you use anything else besides the frontend to talk to HA, make sure it handles it differently.
I have recently merged code to refactor Home Assistant to use only UTC times internally. A much needed refactor. I’ve added some extra test coverage to time sensitive parts to ensure stability. The code has been live in the dev branch for the last 9 days and will be soon released to the master branch.
+
From now on all internal communication will be done in UTC: time changed events, datetime attributes of states, etc. To get the current time in UTC you can call homeassistant.util.dt.utcnow(). This is a timezone aware UTC datetime object. homeassistant.util.dt is a new util package with date helpers.
+
There is also such a thing as local time. Local time is based on the time zone that you have setup in your configuration.yaml. Local times should only be used for user facing information: logs, frontend and automation settings in configuration.yaml.
+
Setting up your time zone
+
Setting up a time zone happens in configuration.yaml. If you have no time zone setup, it will be auto detected using the existing detection code using freegeoip.net. You can find a list of compatible time zones on Wikipedia.
+
homeassistant:
+ time_zone:America/Los_Angeles
+
+
+
Compatibility
+
The changes to the code are mostly backwards compatible. The old hass.track_time_change and hass.track_point_in_time use now internally two new methods: hass.track_utc_time_change and hass.track_point_in_utc_time. The usage of the old methods have not changed and should be backwards compatible.
+
This refactor adds a new migration for the database adding a utc_offset column to events and states. This information is currently not used but can prove useful in the future when we start analyzing the historical data.
+
Backwards incompatible stuff
+
All built-in components have been upgraded. The following list is only for people that run custom components:
+
+
hass.track_time_change and hass.track_point_in_time will now return a time zone aware datetime object. Python does not allow comparing a naive with an aware datetime object.
+
the sun attributes for rising and setting are now in UTC. The methods sun.next_rising(hass) and sun.next_setting(hass) are backwards compatible, just be careful if you used to read the raw attributes.
+
the API sends all times in UTC. If you use anything else besides the frontend to talk to HA, make sure it handles it differently.
+
+
+
+
@@ -416,38 +459,6 @@ Home Assistant now supports --open-ui and
password=YOUR_PASSWORD
Most people do not like configuring things. Things just have to work, out of the box. Reaching this scenario is the goal of what we are about to introduce: our new discovery component.
-
The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The initial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.
-
Most devices still require some sort of interaction from the user after being discovered - be it a button being pressed or some sort of authentication. This is a challenge that will be solved in the future.
-
To enable the discovery component, add the following to your home-assistant.conf:
-
[discovery]
-
-
-
A new discovery section has been added to the Adding a new platform page with instructions how to make your platform discoverable.
Most people do not like configuring things. Things just have to work, out of the box. Reaching this scenario is the goal of what we are about to introduce: our new discovery component.
+
The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The initial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.
+
Most devices still require some sort of interaction from the user after being discovered - be it a button being pressed or some sort of authentication. This is a challenge that will be solved in the future.
+
To enable the discovery component, add the following to your home-assistant.conf:
+
[discovery]
+
+
+
A new discovery section has been added to the Adding a new platform page with instructions how to make your platform discoverable.
This new release finally brings us the release of Hassbian based on the release of Raspbian Stretch. The most significant change with this is that we now run Home Assistant on Python 3.5.
+Other than that the changes are mostly to our tool hassbian-config.
+
Hassbian-config
+
To allow you to customize your installation further, we have made a few additions to our tool called hassbian-config. Majority of these changes where contributed by @Ludeeus.
+
Upgrade scripts
+
@Ludeeus contributed the possibility to run upgrade scripts to the hassbian-config tool.
+
+
Upgrade Hassbian: Upgrades packages of the base operating system. Contributed by @Landrash.
+
Upgrade Hassbian-script: Downloads and upgrades the latest release of Hassbian-scripts. Contributed by @Ludeeus.
+
Upgrade Home-assistant: Upgrades the Home Assistant installation to the latest release. Contributed by @Ludeeus.
+
+
To follow discussions about the development of the HASSbian image or to contribute join our Discord chat server.
+
To get started with the new image, check out the installation instructions on the installing Hassbian page.
+
+
+
@@ -585,32 +622,6 @@ Screenshot of a green dashboard
The third episode of the Home Assistant Podcast is out. Paulus joins to talk about some stats and the release of 0.47 and Petar tells all about his Floorplan project for Home Assistant.
The third episode of the Home Assistant Podcast is out. Paulus joins to talk about some stats and the release of 0.47 and Petar tells all about his Floorplan project for Home Assistant.
In just 12 hours PyCon US 2017 starts. This is an exciting conference because there will be a bunch of Home Assistant developers and users there being able to meet in person.
-
Just like last year, we’ll be hosting a Home Assistant Open Space. Please stop by to ask any questions you have to the available developers. We haven’t reserved a slot yet but will do so tomorrow. We’ll update this post and announce it on social media as we know time and location.First open-space will be Friday at 4pm in room B112.
-
We will also be taken part in the development sprints from Monday-Wednesday. You only need to bring a laptop. We’ll help you get set up with a dev environment and you can be coding on top of Home Assistant in no time. Exact location inside the conference center to be announced.We are sitting in room A108.
-
On a final note, the Home Assistant community is very very active so don’t take it personal if we don’t remember your name, issue or contribution.
In just 12 hours PyCon US 2017 starts. This is an exciting conference because there will be a bunch of Home Assistant developers and users there being able to meet in person.
+
Just like last year, we’ll be hosting a Home Assistant Open Space. Please stop by to ask any questions you have to the available developers. We haven’t reserved a slot yet but will do so tomorrow. We’ll update this post and announce it on social media as we know time and location.First open-space will be Friday at 4pm in room B112.
+
We will also be taken part in the development sprints from Monday-Wednesday. You only need to bring a laptop. We’ll help you get set up with a dev environment and you can be coding on top of Home Assistant in no time. Exact location inside the conference center to be announced.We are sitting in room A108.
+
On a final note, the Home Assistant community is very very active so don’t take it personal if we don’t remember your name, issue or contribution.
+
+
+
@@ -492,45 +520,6 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
Last month IKEA released a new home automation lineup called Trådfri. It consists of white bulbs, dimming remotes, color temperature remotes and motion sensors. After almost two weeks of research, we have come to the conclusion that this is going to be the perfect companion hardware to work with Home Assistant. Here is the gist of our breakdown:
-
-
Works out of the box. You can get started by just buying the already paired light and remote. You only need to buy the gateway if you want to set time-based rules for your lights or use your phone as a remote.
-
Local only hub. No cloud that gathers data about how you live your life and it will keep working even if IKEA stops supporting it.
-
Based on open standards. It uses Zigbee between devices and CoAP/dTLS to talk to the gateway. This means that you are not locked into a single vendor. You can pair it with Philips Hue bulbs and other compatible vendors.
-
Affordable. Lights start at $12 standalone and $20 if bundled with a remote (USA prices).
-
Useful design. The gateway has built-in space to hide excess cables and remotes come with magnetic holders for on the wall.
-
Able to subscribe to changes (local push). Automations will be able to instantly respond to changes to device states by subscribing to the gateway for changes.
-
Full integration in Home Assistant 0.43 (scheduled for release April 22). Our community built a standalone library pytradfri and we use it in Home Assistant. Home Assistant will automatically discover gateways on your network and guide the user to set them up.
-
Downside: no integration with other systems yet. There are rumors that Homekit support will land in October and I expect both Google Home and Amazon Echo to eventually add support. Use Home Assistant to connect them all in the meanwhile.
-
Semi-downside: you can’t control your lights remotely. Because it’s local only, you won’t be able to control your lights remotely unless via a third-party integration.
-
-
Full breakdown available after clicking read more.
-
(Note: we are not affiliated with IKEA nor do we receive commission for sales. We are just big fans of their new line up!)
Last month IKEA released a new home automation lineup called Trådfri. It consists of white bulbs, dimming remotes, color temperature remotes and motion sensors. After almost two weeks of research, we have come to the conclusion that this is going to be the perfect companion hardware to work with Home Assistant. Here is the gist of our breakdown:
+
+
Works out of the box. You can get started by just buying the already paired light and remote. You only need to buy the gateway if you want to set time-based rules for your lights or use your phone as a remote.
+
Local only hub. No cloud that gathers data about how you live your life and it will keep working even if IKEA stops supporting it.
+
Based on open standards. It uses Zigbee between devices and CoAP/dTLS to talk to the gateway. This means that you are not locked into a single vendor. You can pair it with Philips Hue bulbs and other compatible vendors.
+
Affordable. Lights start at $12 standalone and $20 if bundled with a remote (USA prices).
+
Useful design. The gateway has built-in space to hide excess cables and remotes come with magnetic holders for on the wall.
+
Able to subscribe to changes (local push). Automations will be able to instantly respond to changes to device states by subscribing to the gateway for changes.
+
Full integration in Home Assistant 0.43 (scheduled for release April 22). Our community built a standalone library pytradfri and we use it in Home Assistant. Home Assistant will automatically discover gateways on your network and guide the user to set them up.
+
Downside: no integration with other systems yet. There are rumors that Homekit support will land in October and I expect both Google Home and Amazon Echo to eventually add support. Use Home Assistant to connect them all in the meanwhile.
+
Semi-downside: you can’t control your lights remotely. Because it’s local only, you won’t be able to control your lights remotely unless via a third-party integration.
+
+
Full breakdown available after clicking read more.
+
(Note: we are not affiliated with IKEA nor do we receive commission for sales. We are just big fans of their new line up!)
What time is it? Yep, t-shirt time. Today we’re launching the first two Home Assistant designs. We have a blue t-shirt (🇪🇺 EU – 🇺🇸 US) as pictured above and a design for on black/gray shirts (🇪🇺 EU – 🇺🇸 US) as pictured below.
And because we love the internet and all the things that it has brought us, we will start with having 100% of the profit from the sales be donated to the Electronic Frontier Foundation. If you buy a shirt you will hit two birds with one stone (figuratively): you get to wear a kick-ass Home Assistant t-shirt and you help fund defending civil liberties in the digital world.
-
The EFF is a nonprofit organization that aims to protect the rights of technology users. You might however be more familiar with one of their projects: Let’s Encrypt. Read more about what the EFF does.
-
- Family of 4 on a bench wearing the new black Home Assistant shirt. 🇪🇺 EU – 🇺🇸 US
-
-
We are using Teespring.com to manage all the sales, production and distribution of the shirts and they will also donate our profits to the EFF. It’s also how we got all these amazing stockphotos. Some extra things to note about our teespring shop:
-
-
Teespring shows that there is a number of days left until the end of the campaign for the shirts. Don’t worry about that, it should automatically relaunch.
What time is it? Yep, t-shirt time. Today we’re launching the first two Home Assistant designs. We have a blue t-shirt (🇪🇺 EU – 🇺🇸 US) as pictured above and a design for on black/gray shirts (🇪🇺 EU – 🇺🇸 US) as pictured below.
And because we love the internet and all the things that it has brought us, we will start with having 100% of the profit from the sales be donated to the Electronic Frontier Foundation. If you buy a shirt you will hit two birds with one stone (figuratively): you get to wear a kick-ass Home Assistant t-shirt and you help fund defending civil liberties in the digital world.
+
The EFF is a nonprofit organization that aims to protect the rights of technology users. You might however be more familiar with one of their projects: Let’s Encrypt. Read more about what the EFF does.
+
+ Family of 4 on a bench wearing the new black Home Assistant shirt. 🇪🇺 EU – 🇺🇸 US
+
+
We are using Teespring.com to manage all the sales, production and distribution of the shirts and they will also donate our profits to the EFF. It’s also how we got all these amazing stockphotos. Some extra things to note about our teespring shop:
+
+
Teespring shows that there is a number of days left until the end of the campaign for the shirts. Don’t worry about that, it should automatically relaunch.
A year ago Home Assistant 0.10 landed. Last weekend we released 0.35. Doing 25 releases in a year is a big accomplishment by the community and each release has moved us forwards leaps and bounds. In this year alone we have seen 2800 pull requests on the main repo alone, that’s more than 7 a day!
-
One of the things that Jon Walker, the founder of the company I work for (AppFolio), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Every time you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.
-
That’s why I structured Home Assistant around a two week release cycle. It makes sure that features get out fast and it also forces us to not accumulate a backlog of things to document or test properly. Every two weeks we can start fresh. This makes it easy for new people to start contributing because it’s clear when things go out and people are not afraid to miss a release.
-
However, being on a two week release cycle also means that the community has to rally each two weeks to make sure everything is ready to go. A lot of people are involved in making sure that all pieces are in place, to all of those: thank you! Thank you for all the time and effort you put in to make Home Assistant the best home automation software out there.
-
Another big thanks goes out to the developers of the Python language and all the open source libraries and tools that Home Assistant depends on. Making quality software is not a small feat and all of you can be proud of yourself.
-
Also a big thanks for the companies that offer their services for free to open source projects. Without these we would not be able to operate at our speed or scale. Thanks GitHub, TravisCI, CloudFlare and Discourse!
-
And finally thank you community for being so helpful and awesome 🙇.
-
We’re taking a well deserved break and we will be back again in 2017 with more awesomeness. Happy holidays!
A year ago Home Assistant 0.10 landed. Last weekend we released 0.35. Doing 25 releases in a year is a big accomplishment by the community and each release has moved us forwards leaps and bounds. In this year alone we have seen 2800 pull requests on the main repo alone, that’s more than 7 a day!
+
One of the things that Jon Walker, the founder of the company I work for (AppFolio), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Every time you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.
+
That’s why I structured Home Assistant around a two week release cycle. It makes sure that features get out fast and it also forces us to not accumulate a backlog of things to document or test properly. Every two weeks we can start fresh. This makes it easy for new people to start contributing because it’s clear when things go out and people are not afraid to miss a release.
+
However, being on a two week release cycle also means that the community has to rally each two weeks to make sure everything is ready to go. A lot of people are involved in making sure that all pieces are in place, to all of those: thank you! Thank you for all the time and effort you put in to make Home Assistant the best home automation software out there.
+
Another big thanks goes out to the developers of the Python language and all the open source libraries and tools that Home Assistant depends on. Making quality software is not a small feat and all of you can be proud of yourself.
+
Also a big thanks for the companies that offer their services for free to open source projects. Without these we would not be able to operate at our speed or scale. Thanks GitHub, TravisCI, CloudFlare and Discourse!
+
And finally thank you community for being so helpful and awesome 🙇.
+
We’re taking a well deserved break and we will be back again in 2017 with more awesomeness. Happy holidays!
+
– Paulus
+
+
+
@@ -1025,119 +1058,6 @@
On first boot the latest release of Home Assistant will be installed and can be reached after 3~5 minutes. Pre-installed on this image is the MQTT broker Mosquitto, Bluetooth support and settings for the homeassistant account to use the GPIO pins of the Raspberry Pi. Mosquitto is not activated by default.
Two weeks ago, September 17 marked our 3 year anniversary. In this time Home Assistant managed to grow from a simple script that turned on my lights when the sun set to a kick ass open source project with the best community an open-source project could wish for. This release contains features, bug fixes and performance tweaks by a total of 50 different people! We have also managed to cross the 1000 forks on GitHub. Talking about momentum!
-
This is a big release as we’ve completely overhauled the internals of Home Assistant. When I initially wrote Home Assistant, still figuring out the ins and outs of Python, I went for an approach that I was familiar with for an application with many moving parts: threads and locks. This approach has served us well over the years but it was slower than it needed to be, especially on limited hardware.
-
This all changed when @bbangert came around and took on the tough job to migrate the core over to use asynchronous programming. He did an amazing job and I am happy to say that the initial port has been done and is included in this release! On top of that, we have been able to keep our simple and straightforward API at the same time. We are still in the process of migrating more and more components over to the asynchronous API, so expect more speedups and awesome features in the upcoming releases.
-
SleepIQ and OpenALPR
-
There now is support for two new super cool things: Beds and license plates. @technicalpickles created a SleepIQ component that let you monitor the sensor data of your bed. @pvizeli has added license plate recognition based on OpenALPR! This means that you can now be notified about which car is parked on your driveway or in your garage. I also would like to use this opportunity to give a big shoutout to @pvizeli for being such an awesome member of our community. He joined us at the end of June and has helped crush bugs and add awesome features ever since (65 pull requests already!).
-
Configuration validation
-
On the voluptuous front we have also made great progress. We were able to fully remove the legacy config helpers and have migrated 323 of the 346 components and platforms that needed migrating! This does mean that for some components the configuration has slightly changed, make sure to check out the breaking changes section at the bottom for more info. Thanks everybody for reviewing the Pull requests, testing the changes, and reporting issues.
-
Delayed Release
-
As you might have noticed, this release has been delayed by 5 days. This was due to a rare, difficult to reproduce problem with the Python interpreter. A huuuuge thanks to all the people that have helped countless hours in researching, debugging and fixing this issue: @bbangert, @turbokongen, @lwis, @kellerza, @technicalpickles, @pvizeli, @persandstrom and @joyrider3774. I am grateful to have all of you as part of the Home Assistant community.
-
Hide automation rules
-
Since 0.28 automation rules can be reloaded directly from the frontend. By default all automation rules are shown. If you want to hide an automation rule, use hide_entity: True.
-
All changes
-
-
-
Convert core from thread-based to be async-based (@bbangert, @balloob)
For Wink, make sure your config only contains the access token as in the docs.
-
Nest sensor ‘mode’ has been renamed to ‘operation_mode’
-
-
If you need help…
-
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
Two weeks ago, September 17 marked our 3 year anniversary. In this time Home Assistant managed to grow from a simple script that turned on my lights when the sun set to a kick ass open source project with the best community an open-source project could wish for. This release contains features, bug fixes and performance tweaks by a total of 50 different people! We have also managed to cross the 1000 forks on GitHub. Talking about momentum!
+
This is a big release as we’ve completely overhauled the internals of Home Assistant. When I initially wrote Home Assistant, still figuring out the ins and outs of Python, I went for an approach that I was familiar with for an application with many moving parts: threads and locks. This approach has served us well over the years but it was slower than it needed to be, especially on limited hardware.
+
This all changed when @bbangert came around and took on the tough job to migrate the core over to use asynchronous programming. He did an amazing job and I am happy to say that the initial port has been done and is included in this release! On top of that, we have been able to keep our simple and straightforward API at the same time. We are still in the process of migrating more and more components over to the asynchronous API, so expect more speedups and awesome features in the upcoming releases.
+
SleepIQ and OpenALPR
+
There now is support for two new super cool things: Beds and license plates. @technicalpickles created a SleepIQ component that let you monitor the sensor data of your bed. @pvizeli has added license plate recognition based on OpenALPR! This means that you can now be notified about which car is parked on your driveway or in your garage. I also would like to use this opportunity to give a big shoutout to @pvizeli for being such an awesome member of our community. He joined us at the end of June and has helped crush bugs and add awesome features ever since (65 pull requests already!).
+
Configuration validation
+
On the voluptuous front we have also made great progress. We were able to fully remove the legacy config helpers and have migrated 323 of the 346 components and platforms that needed migrating! This does mean that for some components the configuration has slightly changed, make sure to check out the breaking changes section at the bottom for more info. Thanks everybody for reviewing the Pull requests, testing the changes, and reporting issues.
+
Delayed Release
+
As you might have noticed, this release has been delayed by 5 days. This was due to a rare, difficult to reproduce problem with the Python interpreter. A huuuuge thanks to all the people that have helped countless hours in researching, debugging and fixing this issue: @bbangert, @turbokongen, @lwis, @kellerza, @technicalpickles, @pvizeli, @persandstrom and @joyrider3774. I am grateful to have all of you as part of the Home Assistant community.
+
Hide automation rules
+
Since 0.28 automation rules can be reloaded directly from the frontend. By default all automation rules are shown. If you want to hide an automation rule, use hide_entity: True.
+
All changes
+
+
+
Convert core from thread-based to be async-based (@bbangert, @balloob)
For Wink, make sure your config only contains the access token as in the docs.
+
Nest sensor ‘mode’ has been renamed to ‘operation_mode’
+
+
If you need help…
+
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
-The first release of Micropython for ESP8266 was delivered a couple of weeks ago. The documentation covers a lot of ground. This post is providing only a little summary which should get you started.
-
Until a couple of weeks ago, the pre-built MicroPython binary for the ESP8266 was only available to backers of the Kickstarter campaign. This has changed now and it is available to the public for download.
+The first release of Micropython for ESP8266 was delivered a couple of weeks ago. The documentation covers a lot of ground. This post is providing only a little summary which should get you started.
+
Until a couple of weeks ago, the pre-built MicroPython binary for the ESP8266 was only available to backers of the Kickstarter campaign. This has changed now and it is available to the public for download.
Our community is amazingly helpful and creative. If you haven’t been there yet, make sure to stop by our chat room and come hang out with us. In this blog post I want to highlight a few recent awesome projects and videos from the community.
-
SceneGen - cli for making scenes
-
SceneGen is a new command line utility developed by Andrew Cockburn that helps with creating scene configurations for Home Assistant. To use it, you put your house in the preferred state, run SceneGen and it will print the scene configuration for your current states.
-
Videos
-
Nick Touran has been working on integrating IR remotes with Home Assistant. He made it into a component which should be available in the next release which should arrive in a couple of days. In the meanwhile, he wrote up a blog post and has put out a video showing the new integration, very cool!
-
-
-
-
Ben from BRUH Automation has put out another great video how to get started tracking your location in Home Assistant using MQTT and OwnTracks.
-
-
-
-
Muhammed Kilic has created a video how to make your Home Assistant instance accessible from the internet using the free dynamic DNS service DuckDNS.
Lock: Reports on Door Locks and can be used to lock and unlock the door.
Light: Reports on Dimmer lights and can be used to dim, change color, or turn the light on and off.
Switch: Reports on Power Switch devices and can be used to turn the power switch on and off. Also reports on Automations set up in the Abode system and allows you to activate or deactivate them.
+
Sensor: Reports on Temperature, Humidity, and Light sensors.
Configuration
To use Abode devices in your installation, add the following abode section to your configuration.yaml file:
The arlo control panel platform allows you to control your Arlo base stations.
+
To get your Arlo base stations working within Home Assistant, please follow the instructions for the general Arlo component.
+
Once you have enabled the Arlo component, add the following to your configuration.yaml file:
+
# Example configuration.yaml entry
+alarm_control_panel:
+ -platform:arlo
+
+
+
Configuration variables:
+
+
home_mode_name: (Optional): Arlo base station does not have a built-in home mode. You can map one of your custom modes to home assistant’s home mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match exactly as you set it up in the Arlo app.
diff --git a/components/alarm_control_panel.egardia/index.html b/components/alarm_control_panel.egardia/index.html
index 4077dd28c5..8581e0d8a2 100644
--- a/components/alarm_control_panel.egardia/index.html
+++ b/components/alarm_control_panel.egardia/index.html
@@ -23,7 +23,7 @@
-
+
@@ -101,7 +101,7 @@ You can change this, however, using the following procedure. This is a more adva
Log in into your alarm system’s control panel. You will need to access http://[IP of your control panel]. You know this already since you need it in the basic configuration from above. Log in to the control panel with your Egardia/Woonveilig username and password.
Once logged in, go to System Settings, Report and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. Also, update the port number 85 or to anything you like. The provided software that you will set up in the next steps runs on port 85 by default. Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia’s / Woonveilig services. Maybe, that is just what you want. Make sure to save your settings by selecting ‘OK’.
-
On your Home Assistant machine run $ sudo python3 egardiaserver.py. Refer to the python-egardia repository for detailed documentation on parameters. This will receive status codes from your alarm control panel and display them. You will need the codes to include in your configuration.yaml. Make sure to change the status of your alarm to all states (disarm, arm, armhome) as well as trigger the alarm in all ways possible to get 100% coverage. Before triggering the alarm it might be good to disable the siren temporarily (can be done in Panel Settings).
+
On your Home Assistant machine run $ sudo python3 egardiaserver.py. Refer to the python-egardia repository for detailed documentation on parameters. This will receive status codes from your alarm control panel and display them. You will need the codes to include in your configuration.yaml. Make sure to change the status of your alarm to all states (disarm, arm, armhome) by all means possible (all users, remotes, web login, app) as well as trigger the alarm in all ways possible to get 100% coverage. Before triggering the alarm it might be good to disable the siren temporarily (can be done in Panel Settings).
Once you have the codes, update your configuration.yaml:
# Example configuration.yaml entryalarm_control_panel:
@@ -117,23 +117,24 @@ You can change this, however, using the following procedure. This is a more adva
armhome:XXXXXXXXXXXXXXXXtriggered:XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXXignore:XXXXXXXXXXXXXXXX
-
-
-
Note that for triggered, arm and disarm multiple codes can be entered since each sensor triggers with a different code and each user of the system has its own arm and disarm codes. Also note that your system will do regular system checks which will be reported as well. Since Home Assistant provides no way of handling them properly, you can enter those codes as ignore (again, multiple codes can be used here). The egardia component will ignore these codes and continue returning the old status if it receives any of the codes that are listed as ignore. This is useful for example when you have armed your alarm at night: normally a system check will occur at least once during the night and if that code is not specified anywhere Home Assistant will set the status of the alarm to its default, which is unarmed. This is in fact wrong. Listing the code as ignore changes this behavior and Home Assistant will continue to show the status the alarm is in (disarm, arm, armhome, triggered) even when system checks occur.
-
-
Start the egardiaserver.py script on boot of your Home Assistant machine, for example by using systemd. To use this method, create a shell script named egardiaserver.sh that contains the following:
-
Note that for triggered, arm and disarm multiple codes can be entered since each sensor triggers with a different code and each user of the system has its own arm and disarm codes. Also note that your system will do regular system checks which will be reported as well. Since Home Assistant provides no way of handling them properly, you can enter those codes as ignore (again, multiple codes can be used here). The egardia component will ignore these codes and continue returning the old status if it receives any of the codes that are listed as ignore. This is useful for example when you have armed your alarm at night: normally a system check will occur at least once during the night and if that code is not specified anywhere Home Assistant will set the status of the alarm to its default, which is unarmed. This is in fact wrong. Listing the code as ignore changes this behavior and Home Assistant will continue to show the status the alarm is in (disarm, arm, armhome, triggered) even when system checks occur.
+
+
Start the egardiaserver.py script on boot of your Home Assistant machine, for example by using systemctl by systemd. To use this method, create a shell script named egardiaserver.sh that contains something like the following:
Mark it as executable ($ chmod +x) and run sudo nano /lib/systemd/system/egardiaserver.service. Enter the following into the egardiaserver.service file:
[Unit]
Description=Egardia Server Service
[Service]
-ExecStart=/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pythonegardia/egardiaserver.sh
+ExecStart=/bin/bash /srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/pythonegardia/egardiaserver.sh
StandardOutput=journal+console
[Install]
@@ -173,6 +174,9 @@ python3 /srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/python
When the state of the manual alarm changes, Home Assistant will publish one of the following states to the state_topic:
‘disarmed’
‘armed_home’
‘armed_away’
+
‘armed_night’
‘pending’
‘triggered’
@@ -105,6 +107,21 @@
pending_time (Optional): The time in seconds of the pending time before arming the alarm. Default is 60 seconds.
trigger_time (Optional): The time in seconds of the trigger time in which the alarm is firing. Default is 120 seconds.
disarm_after_trigger (Optional): If true, the alarm will automatically disarm after it has been triggered instead of returning to the previous state.
+
+
+
+
+
**armed_home
+
armed_away
+
armed_night
+
triggered** (Optional): State specific settings
+
+
+
+
+
pending_time: State specific pending time override.
+
+
Additionally, the following MQTT configuration variables are also available:
@@ -114,7 +131,22 @@
payload_disarm (Optional): The payload to disarm this Alarm Panel. Default is “DISARM”.
payload_arm_home (Optional): The payload to set armed-home mode on this Alarm Panel. Default is “ARM_HOME”.
payload_arm_away (Optional): The payload to set armed-away mode on this Alarm Panel. Default is “ARM_AWAY”.
+
payload_arm_night (Optional): The payload to set armed-night mode on this Alarm Panel. Default is “ARM_NIGHT”.
+
In the config example below, armed_home state will have no pending time and triggered state will have a pending time of 20 seconds whereas armed_away state will have a default pending time of 30 seconds.
diff --git a/components/alarm_control_panel.wink/index.html b/components/alarm_control_panel.wink/index.html
index 2c18bb2465..f51ecc0aac 100644
--- a/components/alarm_control_panel.wink/index.html
+++ b/components/alarm_control_panel.wink/index.html
@@ -23,7 +23,7 @@
-
+
@@ -147,6 +147,9 @@ The above devices are confirmed to work, but others may work as well.
diff --git a/components/apple_tv/index.html b/components/apple_tv/index.html
index d5ddd9d0f4..e4fff02d56 100644
--- a/components/apple_tv/index.html
+++ b/components/apple_tv/index.html
@@ -23,7 +23,7 @@
-
+
@@ -357,6 +357,9 @@ Turning the device on/off in the user interface will not turn the physi
The Arlo component also provides a service to enable/disable the motion detection sensor. The example below enables the motion detection every time the Home Assistant service starts.
#automation.yaml-alias:Enable Arlo upton HA start'
@@ -122,6 +122,9 @@
diff --git a/components/asterisk_mbox/index.html b/components/asterisk_mbox/index.html
index 2863f96b9f..1ff3457bc6 100644
--- a/components/asterisk_mbox/index.html
+++ b/components/asterisk_mbox/index.html
@@ -23,7 +23,7 @@
-
+
@@ -150,6 +150,9 @@ Communication between the Asterisk PBX server and the Home Assistant server is p
diff --git a/components/binary_sensor.apcupsd/index.html b/components/binary_sensor.apcupsd/index.html
index 3be0c9613c..6532f5fbb9 100644
--- a/components/binary_sensor.apcupsd/index.html
+++ b/components/binary_sensor.apcupsd/index.html
@@ -23,7 +23,7 @@
-
+
diff --git a/components/binary_sensor.arest/index.html b/components/binary_sensor.arest/index.html
index 89f918d8cf..17c57e0c12 100644
--- a/components/binary_sensor.arest/index.html
+++ b/components/binary_sensor.arest/index.html
@@ -23,7 +23,7 @@
-
+
@@ -274,6 +274,9 @@ This sensor is not suitable for fast state changes because there is a high possi
diff --git a/components/binary_sensor.blink/index.html b/components/binary_sensor.blink/index.html
index c4674e5338..c8f12e9413 100644
--- a/components/binary_sensor.blink/index.html
+++ b/components/binary_sensor.blink/index.html
@@ -23,7 +23,7 @@
-
+
@@ -245,6 +245,9 @@ To get your Blink binary sensors working with Home Assistant, follow the instruc
diff --git a/components/binary_sensor.ffmpeg_motion/index.html b/components/binary_sensor.ffmpeg_motion/index.html
index c5b69a4bbf..b2013764f7 100644
--- a/components/binary_sensor.ffmpeg_motion/index.html
+++ b/components/binary_sensor.ffmpeg_motion/index.html
@@ -23,7 +23,7 @@
-
+
@@ -264,6 +264,9 @@ If the ffmpeg process is broken, the sens
diff --git a/components/binary_sensor.ffmpeg_noise/index.html b/components/binary_sensor.ffmpeg_noise/index.html
index 4b30497f9f..31697db053 100644
--- a/components/binary_sensor.ffmpeg_noise/index.html
+++ b/components/binary_sensor.ffmpeg_noise/index.html
@@ -23,7 +23,7 @@
-
+
@@ -255,6 +255,9 @@ If the ffmpeg process is broken, the sens
diff --git a/components/binary_sensor.http/index.html b/components/binary_sensor.http/index.html
index 05cdd4d5e4..200937bf1e 100644
--- a/components/binary_sensor.http/index.html
+++ b/components/binary_sensor.http/index.html
@@ -23,7 +23,7 @@
-
+
@@ -292,6 +292,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
diff --git a/components/binary_sensor.wink/index.html b/components/binary_sensor.wink/index.html
index 5b5d76dc65..174a9e6073 100644
--- a/components/binary_sensor.wink/index.html
+++ b/components/binary_sensor.wink/index.html
@@ -23,7 +23,7 @@
-
+
@@ -285,6 +285,9 @@ The above devices are confirmed to work, but others may work as well.
diff --git a/components/binary_sensor.workday/index.html b/components/binary_sensor.workday/index.html
index b4ee350293..79de64f005 100644
--- a/components/binary_sensor.workday/index.html
+++ b/components/binary_sensor.workday/index.html
@@ -23,7 +23,7 @@
-
+
@@ -266,6 +266,9 @@ If you use the sensor for Canada (CA) wit
Available events are flip90, flip180, move, tap_twice, shake_air, swing, alert, free_fall and rotate.
+
Available events are flip90, flip180, move, tap_twice, shake_air, swing, alert, free_fall and rotate. The component stores the last action as the attribute last_action.
diff --git a/components/camera.blink/index.html b/components/camera.blink/index.html
index 1be2914002..ba78c960ab 100644
--- a/components/camera.blink/index.html
+++ b/components/camera.blink/index.html
@@ -23,7 +23,7 @@
-
+
@@ -173,6 +173,9 @@ To get your Blink cameras working with Home Assistant, follow the instructions f
diff --git a/components/camera.foscam/index.html b/components/camera.foscam/index.html
index 54eed8cf85..9180ceb073 100644
--- a/components/camera.foscam/index.html
+++ b/components/camera.foscam/index.html
@@ -23,7 +23,7 @@
-
+
@@ -176,6 +176,9 @@ There seems to be some issues within Foscam with lengthy passwords and passwords
diff --git a/components/camera.local_file/index.html b/components/camera.local_file/index.html
index 6b01269cb3..0db5cf0835 100644
--- a/components/camera.local_file/index.html
+++ b/components/camera.local_file/index.html
@@ -23,7 +23,7 @@
-
+
@@ -173,6 +173,9 @@ The given file_path must be an existing f
diff --git a/components/camera.nest/index.html b/components/camera.nest/index.html
index 891a44cc6f..4e76b8dd73 100644
--- a/components/camera.nest/index.html
+++ b/components/camera.nest/index.html
@@ -23,7 +23,7 @@
-
+
@@ -177,6 +177,9 @@ You must have the Nest component configured to u
diff --git a/components/camera.usps/index.html b/components/camera.usps/index.html
index a3f2a04fd2..30c1dc2e6d 100644
--- a/components/camera.usps/index.html
+++ b/components/camera.usps/index.html
@@ -23,7 +23,7 @@
-
+
@@ -179,6 +179,9 @@ You must have the USPS component configured to u
The yi camera platform allows you to utilize Yi Home Cameras within Home
+Assistant. Specifically, this platform supports the line of Yi Home Cameras
+that are based on the Hi3518e Chipset; these include:
+
+
Yi Home 17CN
+
Yi 1080p Home
+
Yi Dome
+
Yi 1080p Dome
+
+
To successfully implement this platform, the Home Assistant host should be
+capable of multiple simultaneous reads; for every concurrent Home Assistant
+user, a connection will be made to the camera every 10 seconds.
+This should normally not be a problem.
+
Preparing the Device
+
Installing Alternative Firmware
+
In order to integrate the camera with Home Assitant, it is necessary to install
+a custom firmware on the device. Instructions for doing so can be found via the
+yi-hack-v3 GitHub project.
+
Once installed, please ensure that you have enabled FTP and Telnet on your
+device.
+
+Some alternative Yi firmwares enable an experimental RTSP server, which will
+allow you to connect to your camera via other Home Assistant camera platforms.
+However, this RTSP server disables the ability to use the supremely-useful Yi
+Home app. In order to maintain both Home Assistant compatibility and the native
+app, this platform retrieves videos via FTP.
+
+
Changing the FTP Password
+
Once the custom firmware is installed, a password must be added to the FTP
+server. To do so:
+
+
Telnet into your camera: telnet <IP ADDRESS>.
+
Enter root as the username and <blank> as the password.
+
Type passwd and hit <Enter>.
+
Enter your new password twice.
+
Log out of Telnet.
+
+
Configuring the Platform
+
To enable the platform, add the following lines to your
+configuration.yaml file:
host (Required): the IP address or hostname of the camera
+
password (Required): the password to the FTP server on the camera (from above)
+
username (Optional): the user that can access the FTP server (default: root)
+
name (Optional): a human-friendly name for the camera
+
ffmpeg_arguments (Optional): extra options to pass to ffmpeg (e.g. image quality or video filter options)
+
+
Image quality
+
Any option supported by the ffmpeg client can be utilized via the
+ffmpeg_arguments configuration parameter.
+
One particularly useful adjustment deals with video size. Since Yi videos are
+fairly large (especially on the 1080p cameras), the following configuration will
+bring them down to a manageable size:
diff --git a/components/climate.nest/index.html b/components/climate.nest/index.html
index 19b1e6b3de..405cff5874 100644
--- a/components/climate.nest/index.html
+++ b/components/climate.nest/index.html
@@ -23,7 +23,7 @@
-
+
@@ -171,6 +171,9 @@ You must have the Nest component configured to u
diff --git a/components/climate.proliphix/index.html b/components/climate.proliphix/index.html
index c5a5ad9847..4946fef3df 100644
--- a/components/climate.proliphix/index.html
+++ b/components/climate.proliphix/index.html
@@ -23,7 +23,7 @@
-
+
@@ -171,6 +171,9 @@ of OID values. A complete collection of the API is available in this
-
+
@@ -178,6 +178,9 @@
diff --git a/components/climate.wink/index.html b/components/climate.wink/index.html
index dcc83035b1..0d12515dc8 100644
--- a/components/climate.wink/index.html
+++ b/components/climate.wink/index.html
@@ -23,7 +23,7 @@
-
+
@@ -201,6 +201,9 @@ The above devices are confirmed to work, but others may work as well.
diff --git a/components/climate.zwave/index.html b/components/climate.zwave/index.html
index 0662c0dc41..2f80c42530 100644
--- a/components/climate.zwave/index.html
+++ b/components/climate.zwave/index.html
@@ -23,7 +23,7 @@
-
+
@@ -234,6 +234,9 @@ If the thermostat support different operating modes, you will get one thermostat
diff --git a/components/comfoconnect/index.html b/components/comfoconnect/index.html
index 60b6a532fc..688023cfa6 100644
--- a/components/comfoconnect/index.html
+++ b/components/comfoconnect/index.html
@@ -23,7 +23,7 @@
-
+
@@ -287,6 +287,9 @@ Note that it’s not possible to have multiple connection to the bridge at the s
password (Required): The password for your given admin account.
site_id (Optional): Allows you to specify a site_id for device tracking. Defaults to default. Found in the URL of the controller (i.e. https://CONTROLLER:PORT/manage/site/SITE_ID/dashboard).
verify_ssl (Optional): Controls if the SSL certificate running on your Unifi webserver must be trusted by a known Certificate Authority on the server running Home Assistant. Defaults to ‘True’ but can also be a value that points to your custom cert “path/to/custom_cert.pem”.
+
detection_time (Optional): The Unifi component will not return a device that has not been seen by the controller in the last 180 seconds. You can adjust this threshold with this variable and accepts seconds or 00:00:00 time formats.
diff --git a/components/emoncms_history/index.html b/components/emoncms_history/index.html
index aaf39a501d..0c773b5252 100644
--- a/components/emoncms_history/index.html
+++ b/components/emoncms_history/index.html
@@ -23,7 +23,7 @@
-
+
diff --git a/components/emulated_hue/index.html b/components/emulated_hue/index.html
index 6f3aa317cb..204949b338 100644
--- a/components/emulated_hue/index.html
+++ b/components/emulated_hue/index.html
@@ -23,7 +23,7 @@
-
+
@@ -352,6 +352,9 @@ It is recommended to assign a static IP address to the computer running Home Ass
The Google Assistant component requires a bit more setup than most due to the way Google requires Assistant Apps to be set up.
+
Configuration
+
# Example configuration.yaml entry
+google_assistant:
+ project_id:someproject-2d0b8
+ client_id:[long URL safe random string]
+ access_token:[a different long URL safe random string]
+ exposed_domains:
+ -switch
+ -light
+ -group
+
+
+
Note: It’s very important that you use very long strings for client_id and access_token. Those are essentially the credentials to your Home Assistant instance.
+
Configuration Variables:
+
+
expose_by_default (Optional): Expose devices in all supported domains by default.
+
project_id (Required): Project ID from the Google Developer console (looks like words-2ab12)
+
client_id (Required): A long random URL safe string (no spaces or special characters) that will be used for Implicit OAuth.
+
access_token (Required): Another different long random URL safe string.
+
exposed_domains (Optional): An array of Home Assistant domains to expose to Google Assistant.
+
+
You can also customize your devices similar to other components by adding keys to entities:
Create a new file named project.json and replace the [YOUR HOME ASSISTANT URL] below with the URL you use to access Home Assistant.
+Note: This must be an HTTPS URL to work.
Copy the command that looks like:
+ gactions update --action_package PACKAGE_NAME --project doctest-2d0b8
+
+
+
Replace PACKAGE_NAME with project.json and run that command from the same directory you saved project.json in. It should output a URL like https://console.actions.google.com/project/doctest-2d0b8/overview Go there.
+
You’ll need to fill out most of the information on that page, but none of it really matters since you won’t be addressing the App directly, only through the Smart Home functionality built into Google Assistant.
+
The final item on that page Account linking is required for your app to interact with Home Assistant.
+
+
Grant type: Implicit
+
Client ID: Should be the same as client_id from your hass config above
+
Authorization URL (replace with your actual URL): https://[YOUR HOME ASSISTANT URL]/api/google_assistant/auth
+
Configure your client. Add scopes for email and name
+
Testing instructions: doesn’t matter since you won’t submit this app
+
+
+
Back on the main app draft page. Click Test Draft. That will take you to the simulator (which won’t work) so just close that window.
+
Open the Google Assistant app and go into Settings > Home Control
+
Click the + sign, and near the bottom, you should have [test] your app name. Selecting that should lead to you the screen where you can set rooms for your devices or nicknames for your devices.
The Homematic component provides bi-directional communication with your CCU/Homegear. It uses a XML-RPC connection to set values on devices and subscribes to receive events the devices and the CCU emit.
-
Device support is available for most of the wired and wireless devices, as well as a few IP devices. If you have a setup with mixed protocols, you have to configure additional hosts with the appropriate ports. The default is using port 2001, which are wireless devices. Wired devices usually are available through port 2000 and IP devices through port 2010.
+
The Homematic component provides bi-directional communication with your CCU/Homegear. It uses a XML-RPC connection to set values on devices and subscribes to receive events the devices and the CCU emit.
+If you are using Homegear with paired Intertechno devices, uni-directional communication is possible as well.
+
Device support is available for most of the wired and wireless devices, as well as a few IP devices. If you have a setup with mixed protocols, you have to configure additional hosts with the appropriate ports. The default is using port 2001, which are wireless devices. Wired devices usually are available through port 2000 and IP devices through port 2010. The virtual thermostatgroups the CCU provides use port 9292 and require you to set the path setting to /groups.
If you want to see if a specific device you have is supported, head over to the pyhomematic repository and browse through the source code. A dictionary with the device identifiers (e.g. HM-Sec-SC-2) can be found within the relevant modules near the bottom. If your device is not supported, feel free to contribute.
We automatically detect all devices we currently support and try to generate useful names. If you enable name-resolving, we try to fetch names from Metadata (Homegear), via JSON-RPC or the XML-API you may have installed on your CCU. Since this may fail this is disabled by default.
You can manually rename the created entities by using Home Assistants Customizing feature. With it you are also able to hide entities you don’t want to see in the UI.
diff --git a/components/ifttt.manything/index.html b/components/ifttt.manything/index.html
index 2982795a0e..0354c1c4d2 100644
--- a/components/ifttt.manything/index.html
+++ b/components/ifttt.manything/index.html
@@ -23,7 +23,7 @@
-
+
@@ -216,6 +216,9 @@ For ManyThing support, you need to set up an on<
fire_event (Optional) if set to True, platform will write all received KNX messages to event bus
-
fire_event_filter If fire_event is set fire_event_filter has to be specified. fire_event_filter defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HASS event bus.
+
fire_event (Optional): If set to True, platform will write all received KNX messages to event bus
+
+
fire_event_filter (Optional): If fire_event is set fire_event_filter has to be specified. fire_event_filter defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HASS event bus.
+
+
state_updater (Optional): The component will collect the current state of each configured device from the KNX bus to display it correctly within Home-Assistant. Set this option to False to prevent this behaviour.
Service
In order to directly interact with the KNX bus, you can now use the following service:
@@ -140,8 +143,8 @@ Service Data: {"address": "1/0/15", "payload": 0}
-
address : KNX group address
-
payload : payload, either an integer or an array of integers
+
address: KNX group address
+
payload: Payload, either an integer or an array of integers
Known issues:
Due to lame multicast support the routing abstraction and the gateway scanner
@@ -343,6 +346,9 @@ only work with python >=3.5.
diff --git a/components/light.flux_led/index.html b/components/light.flux_led/index.html
index aa127a6d47..59e6b5b6b0 100644
--- a/components/light.flux_led/index.html
+++ b/components/light.flux_led/index.html
@@ -23,7 +23,7 @@
-
+
@@ -338,6 +338,9 @@ The component defaults to rgbw. If your device has a separate white channel, you
diff --git a/components/light.hue/index.html b/components/light.hue/index.html
index 4d2f3360d2..e48d70b0c0 100644
--- a/components/light.hue/index.html
+++ b/components/light.hue/index.html
@@ -23,7 +23,7 @@
-
+
@@ -299,6 +299,9 @@ This will have all the bulbs transitioned at once, instead of one at a time usin
diff --git a/components/light.knx/index.html b/components/light.knx/index.html
index f8af7c2cf3..2b28db2e9d 100644
--- a/components/light.knx/index.html
+++ b/components/light.knx/index.html
@@ -23,7 +23,7 @@
-
+
@@ -254,6 +254,9 @@ For switching/light actuators that are only controlled by a single group address
diff --git a/components/light.mqtt_template/index.html b/components/light.mqtt_template/index.html
index 0e53aa58d5..fce76e7d89 100644
--- a/components/light.mqtt_template/index.html
+++ b/components/light.mqtt_template/index.html
@@ -23,7 +23,7 @@
-
+
@@ -352,6 +352,9 @@ It is format-agnostic so you can use any data format you want (i.e. string, JSON
diff --git a/components/light.template/index.html b/components/light.template/index.html
index 09a6ca0bd7..4647fe83bb 100644
--- a/components/light.template/index.html
+++ b/components/light.template/index.html
@@ -23,7 +23,7 @@
-
+
@@ -343,6 +343,9 @@ point percentage value from 0.0 to Sense HAT Light
+
diff --git a/components/light.wink/index.html b/components/light.wink/index.html
index b346793afe..5503e3ff8f 100644
--- a/components/light.wink/index.html
+++ b/components/light.wink/index.html
@@ -23,7 +23,7 @@
-
+
@@ -252,6 +252,9 @@ The above devices are confirmed to work, but others may work as well.
diff --git a/components/light.yeelight/index.html b/components/light.yeelight/index.html
index 68a298ba90..500843006a 100644
--- a/components/light.yeelight/index.html
+++ b/components/light.yeelight/index.html
@@ -23,7 +23,7 @@
-
+
@@ -245,6 +245,9 @@ This component is tested to work with the following models. If you have a differ
diff --git a/components/light.yeelightsunflower/index.html b/components/light.yeelightsunflower/index.html
index 0ea897e1c4..d0852fc33f 100644
--- a/components/light.yeelightsunflower/index.html
+++ b/components/light.yeelightsunflower/index.html
@@ -23,7 +23,7 @@
-
+
@@ -225,6 +225,9 @@ The Yeelight Sunflower hub supports SSDP discovery, but that has not been built
diff --git a/components/lutron/index.html b/components/lutron/index.html
index f6ac320e63..063dea70ea 100644
--- a/components/lutron/index.html
+++ b/components/lutron/index.html
@@ -23,7 +23,7 @@
-
+
@@ -273,6 +273,9 @@ It is recommended to assign a static IP address to your main repeater. This ensu
diff --git a/components/lutron_caseta/index.html b/components/lutron_caseta/index.html
index 6142afa4aa..aa9c3a9ffd 100644
--- a/components/lutron_caseta/index.html
+++ b/components/lutron_caseta/index.html
@@ -23,7 +23,7 @@
-
+
@@ -287,6 +287,9 @@ Use a DHCP reservation on your router to reserve the address or in the PRO model
diff --git a/components/media_extractor/index.html b/components/media_extractor/index.html
index c59e09bae7..47e7e402fb 100644
--- a/components/media_extractor/index.html
+++ b/components/media_extractor/index.html
@@ -23,7 +23,7 @@
-
+
@@ -221,6 +221,9 @@ Media extractor doesn’t transcode streams, it just tries to find stream that m
diff --git a/components/media_player.aquostv/index.html b/components/media_player.aquostv/index.html
index 4b644994fc..88ef624d22 100644
--- a/components/media_player.aquostv/index.html
+++ b/components/media_player.aquostv/index.html
@@ -23,7 +23,7 @@
-
+
@@ -193,6 +193,9 @@ Also, with power_on_enabled as True, the Aquos logo on your TV
diff --git a/components/media_player.denonavr/index.html b/components/media_player.denonavr/index.html
index 978993dc78..2b7d13e05c 100644
--- a/components/media_player.denonavr/index.html
+++ b/components/media_player.denonavr/index.html
@@ -23,7 +23,7 @@
-
+
@@ -211,6 +211,9 @@ If you have something else using the IP controller for your Denon AVR 3808CI, su
diff --git a/components/media_player.firetv/index.html b/components/media_player.firetv/index.html
index f350f03754..3ec74467bc 100644
--- a/components/media_player.firetv/index.html
+++ b/components/media_player.firetv/index.html
@@ -23,7 +23,7 @@
-
+
@@ -220,6 +220,9 @@ Note that python-firetv has support for multiple Amazon Fire TV devices. If you
diff --git a/components/media_player.frontier_silicon/index.html b/components/media_player.frontier_silicon/index.html
index 7477883609..74d11f1aa0 100644
--- a/components/media_player.frontier_silicon/index.html
+++ b/components/media_player.frontier_silicon/index.html
@@ -23,7 +23,7 @@
-
+
@@ -215,6 +215,9 @@ The Frontier Silicon API does not provide a multi-user environment. There is alw
diff --git a/components/media_player.kodi/index.html b/components/media_player.kodi/index.html
index 7d9e63db8c..37c09492e7 100644
--- a/components/media_player.kodi/index.html
+++ b/components/media_player.kodi/index.html
@@ -23,7 +23,7 @@
-
+
@@ -418,6 +418,9 @@ This example and the following requires to have the
-
+
@@ -179,6 +179,9 @@ The access token will not change until you factory reset your TV.
port (Required): The serial port to which Monoprice amplifier is connected
+
zones (Required): This is the list of zones available. Valid zones are 11,12,13,14,15,16. In case multiple Monoprice devices are stacked together the list of valid zones is extended by 21,22,23,24,25,26 for the second device and 31,32,33,34,35,36 for the third device. Each zone must have a name assigned to it.
+
sources (Required): The list of sources available. Valid source numbers are 1,2,3,4,5,6. Each source number corresponds to the input number on the Monoprice amplifier. Similar to zones, each source must have a name assigned to it.
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/media_player.mpchc/index.html b/components/media_player.mpchc/index.html
index e4c6d19ee6..9270c53875 100644
--- a/components/media_player.mpchc/index.html
+++ b/components/media_player.mpchc/index.html
@@ -23,7 +23,7 @@
-
+
@@ -181,6 +181,9 @@ The MPC-HC web interface is highly insecure, and allows remote clients full play
diff --git a/components/media_player.nad/index.html b/components/media_player.nad/index.html
index 1569ef487d..7870b6ca42 100644
--- a/components/media_player.nad/index.html
+++ b/components/media_player.nad/index.html
@@ -23,7 +23,7 @@
-
+
@@ -194,6 +194,9 @@ Be aware that the user might need to logout and logon again to activate these pe
diff --git a/components/media_player.samsungtv/index.html b/components/media_player.samsungtv/index.html
index e675200892..22f3d28594 100644
--- a/components/media_player.samsungtv/index.html
+++ b/components/media_player.samsungtv/index.html
@@ -23,7 +23,7 @@
-
+
@@ -212,6 +212,9 @@ If you add your model remember to remove these before adding them to the list.
diff --git a/components/media_player.soundtouch/index.html b/components/media_player.soundtouch/index.html
index a27a32356c..73479993d8 100644
--- a/components/media_player.soundtouch/index.html
+++ b/components/media_player.soundtouch/index.html
@@ -23,7 +23,7 @@
-
+
@@ -300,6 +300,9 @@ create a new zone in order to be able to add slave(s) again
diff --git a/components/media_player.webostv/index.html b/components/media_player.webostv/index.html
index 8a60d0486e..402b325c6e 100644
--- a/components/media_player.webostv/index.html
+++ b/components/media_player.webostv/index.html
@@ -23,7 +23,7 @@
-
+
@@ -210,6 +210,9 @@ Home Assistant is able to turn on a LG webOS Smart TV if you specify an action,
diff --git a/components/mqtt_statestream/index.html b/components/mqtt_statestream/index.html
index 5cd03f14dc..f50dd9d94f 100644
--- a/components/mqtt_statestream/index.html
+++ b/components/mqtt_statestream/index.html
@@ -23,7 +23,7 @@
-
+
@@ -149,6 +149,9 @@ The topic will be in the form base_topic/domain/
diff --git a/components/netatmo/index.html b/components/netatmo/index.html
index 34bd509f28..8a1ab20789 100644
--- a/components/netatmo/index.html
+++ b/components/netatmo/index.html
@@ -23,7 +23,7 @@
-
+
@@ -297,6 +297,9 @@ The Home Assistant Netatmo platform has only be tested with the classic indoor,
The clickatell platform uses Clickatell to deliver SMS notifications from Home Assistant.
+
Get your Clickatell API Credentials
+
Go to your Clickatell SMS Platform Portal section and create a new SMS integration. There are three screens of information required to creater an integration. Please ensure the following:
+
+
Give the new Integration an identification name
+
ensure it is set for ‘production’ use
+
select ‘HTTP’ as your API type
+
Ensure that the you select for the messaging type to be ‘one way messaging’
+
Be aware of the international number format option as this impacts the structure of the phone numbers you provide
+
Once you have completed entering your details an API key is generated. Copy the API key
+
+
Configuration
+
To add Clickatell to your installation, add the following to your Home Assistant configuration.yaml file:
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is Clickatell. The notifier will bind to the service notify.NOTIFIER_NAME.
+
api_key (Required): Your API Key.
+
recipient (Required): Your phone no. This is where you want to send your notification SMS messages. eg: 61444333444
The clicksend_tts platform uses ClickSend to deliver text-to-speech (TTS) notifications from Home Assistant.
+
Go to your ClickSend Dashboard section and create your new project. After creating your project, you should now be able to obtain your username and api_key.
+
To add ClickSend to your installation, add the following to your Home Assistant configuration.yaml file:
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is ClickSend. The notifier will bind to the service notify.NOTIFIER_NAME.
+
username (Required): Your username.
+
api_key (Required): Your API Key.
+
recipient (Required): Your phone no. This is where you want to send your notification SMS messages. eg: 09171234567
+
language (Optional): The language you want to use to convert the message to audio. Accepted values are found in the ClickSend Documentation. Default value is ‘en-us’.
+
voice (Optional): The voice that needs to be used to play the message to the recipient. Allowed values are ‘female’ or ‘male’. Default value is ‘female’.
The clicksendaudio platform uses ClickSend to deliver text-to-speech (TTS) notifications from Home Assistant.
-
Go to your ClickSend Dashboard section and create your new project. After creating your project, you should now be able to obtain your username and api_key.
-
To add ClickSend to your installation, add the following to your Home Assistant configuration.yaml file:
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is ClickSend. The notifier will bind to the service notify.NOTIFIER_NAME.
-
username (Required): Your username.
-
api_key (Required): Your API Key.
-
recipient (Required): Your phone no. This is where you want to send your notification SMS messages. eg: 09171234567
-
language (Optional): The language you want to use to convert the message to audio. Accepted values are found in the ClickSend Documentation. Default value is ‘en-us’.
-
voice (Optional): The voice that needs to be used to play the message to the recipient. Allowed values are ‘female’ or ‘male’. Default value is ‘female’.
diff --git a/components/notify.facebook/index.html b/components/notify.facebook/index.html
index 43cba134ca..acae633310 100644
--- a/components/notify.facebook/index.html
+++ b/components/notify.facebook/index.html
@@ -23,7 +23,7 @@
-
+
@@ -205,10 +205,13 @@ The phone number used in target should be registered with Faceb
Cisco Spark
diff --git a/components/notify.free_mobile/index.html b/components/notify.free_mobile/index.html
index 46c10293f6..cfa2436cc8 100644
--- a/components/notify.free_mobile/index.html
+++ b/components/notify.free_mobile/index.html
@@ -23,7 +23,7 @@
-
+
@@ -132,10 +132,13 @@ If you disable and re-enable the SMS API option, please be sure to update your t
Cisco Spark
Then, click the cogwheel on top left and select “Project settings”.
Select ‘Cloud Messaging’ tab, listed beneath Project Credentials will be your 152 character ‘Server Key’ and 12 digit ID ‘Sender ID’.
-
+
+
Verify your domain with Hass.io
+
+
For verifying your domain you need to download a file in step 2.
+
Create a dictionary named “www” in you Hass.io configuration dictionary.
+
Place the file (something like this: google*.html) in the “www” directory.
+
You can open it by going to https://yourdomain/local/exact_file_name.html
+
Proceed with step 3.
+
Requirements
The html5 platform can only function if all of the following requirements are met:
(On Hass.io these requirements are already met.)
-
You are using Chrome and/or Firefox on any desktop platform, ChromeOS, or Android.
+
You are using Chrome and/or Firefox on any desktop platform, ChromeOS or Android.
Your Home Assistant instance is exposed to the world.
If using a proxy, HTTP basic authentication must be off for registering or unregistering for push notifications. It can be re-enabled afterwards.
pywebpush must be installed. libffi-dev, libpython-dev, and libssl-dev must be installed prior to pywebpush (i.e. pywebpush probably won’t automatically install).
@@ -143,7 +151,7 @@
Data
-
Any parameters that you pass in the notify payload that aren’t valid for use in the HTML5 notification (actions, badge, body, dir, icon, lang, renotify, requireInteraction, tag, timestamp, vibrate) will be sent back to you in the callback events.
+
Any parameters that you pass in the notify payload that aren’t valid for use in the HTML5 notification (actions, badge, body, dir, icon, image, lang, renotify, requireInteraction, tag, timestamp, vibrate) will be sent back to you in the callback events.
{"title":"Front door","message":"The front door is open",
@@ -226,7 +234,7 @@
data
-
The data dictionary you originally passed in the notify payload, minus any parameters that were added to the HTML5 notification (actions, badge, body, dir, icon, lang, renotify, requireInteraction, tag, timestamp, vibrate).
+
The data dictionary you originally passed in the notify payload, minus any parameters that were added to the HTML5 notification (actions, badge, body, dir, icon, image, lang, renotify, requireInteraction, tag, timestamp, vibrate).
diff --git a/components/notify.lametric/index.html b/components/notify.lametric/index.html
index b9e588730d..c94f98e2e4 100644
--- a/components/notify.lametric/index.html
+++ b/components/notify.lametric/index.html
@@ -23,7 +23,7 @@
-
+
@@ -131,10 +131,13 @@ Note that icons always begin with “i” while animations begin with “a”. T
Cisco Spark
diff --git a/components/notify.nfandroidtv/index.html b/components/notify.nfandroidtv/index.html
index 3be702c06b..357954c730 100644
--- a/components/notify.nfandroidtv/index.html
+++ b/components/notify.nfandroidtv/index.html
@@ -23,7 +23,7 @@
-
+
@@ -148,10 +148,13 @@ This is a fully customized JSON you can use to test how the final notification w
Cisco Spark
diff --git a/components/notify.smtp/index.html b/components/notify.smtp/index.html
index 634f78a32d..5c2e693441 100644
--- a/components/notify.smtp/index.html
+++ b/components/notify.smtp/index.html
@@ -23,7 +23,7 @@
-
+
@@ -241,10 +241,13 @@ which need special attention. By default, the usage by external applications, es
Cisco Spark
The abode sensor platform allows you to monitor your Abode sensors.
+
This platform supports Abode Temperature, Humidity, and Light sensors.
+
The requirement is that you have setup your Abode hub.
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/sensor.airvisual/index.html b/components/sensor.airvisual/index.html
index 809c950c09..5ab0f9b772 100644
--- a/components/sensor.airvisual/index.html
+++ b/components/sensor.airvisual/index.html
@@ -23,7 +23,7 @@
-
+
@@ -100,6 +100,7 @@ following lines to your configuration.yamllatitude:42.81212longitude:108.12422radius:500
+ show_on_map:false
Configuration variables:
@@ -113,6 +114,8 @@ defined under the homeassistant key in homeassistant key in configuration.yaml will be used
radius (Optional): the radius (in meters) around the latitude/longitude to
search for the nearest city; defaults to 1000
+
show_on_map (Optional): whether to show a marker on the map at the specified
+location; defaults to true
Configuring the Platform via City/State/Country
To enable the platform and gather data via city/state/country, add the
@@ -126,6 +129,7 @@ following lines to your configuration.yamlcity:southend-on-seastate:essexcountry:uk
+ show_on_map:false
Configuration variables:
@@ -136,6 +140,8 @@ following lines to your configuration.yamlcity (Optional): the city to monitor
state (Optional): the state/region to monitor
country (Optional): the country to monitor
+
show_on_map (Optional): whether to show a marker on the map at the specified
+location; defaults to true
To easily determine the proper values for a particular location, use the
AirVisual region directory. Once you browse to the particular city you want,
diff --git a/components/sensor.alarmdecoder/index.html b/components/sensor.alarmdecoder/index.html
index 9b831db047..33823c6a16 100644
--- a/components/sensor.alarmdecoder/index.html
+++ b/components/sensor.alarmdecoder/index.html
@@ -23,7 +23,7 @@
-
+
@@ -114,6 +114,9 @@
diff --git a/components/sensor.bbox/index.html b/components/sensor.bbox/index.html
index 9f4a20668c..df413e8155 100644
--- a/components/sensor.bbox/index.html
+++ b/components/sensor.bbox/index.html
@@ -23,7 +23,7 @@
-
+
@@ -132,6 +132,9 @@ Due to third party limitation, the sensors will only be available if Home Assist
precip_intensity_max: Today’s expected maximum intensity of precipitation.
+
uv_index: The current UV index.
units (Optional): Specify the unit system. Default to si or us based on the temperature preference in Home Assistant. Other options are auto, us, si, ca, and uk2.
diff --git a/components/sensor.deutsche_bahn/index.html b/components/sensor.deutsche_bahn/index.html
index a8225ec018..641b6131b4 100644
--- a/components/sensor.deutsche_bahn/index.html
+++ b/components/sensor.deutsche_bahn/index.html
@@ -23,7 +23,7 @@
-
+
diff --git a/components/sensor.dht/index.html b/components/sensor.dht/index.html
index 5b03e5daf6..2805495c8b 100644
--- a/components/sensor.dht/index.html
+++ b/components/sensor.dht/index.html
@@ -23,7 +23,7 @@
-
+
diff --git a/components/sensor.dnsip/index.html b/components/sensor.dnsip/index.html
index 69a65a70e0..fac140a0da 100644
--- a/components/sensor.dnsip/index.html
+++ b/components/sensor.dnsip/index.html
@@ -23,7 +23,7 @@
-
+
@@ -129,6 +129,9 @@
diff --git a/components/sensor.gtfs/index.html b/components/sensor.gtfs/index.html
index c247d75190..c473a0cc46 100644
--- a/components/sensor.gtfs/index.html
+++ b/components/sensor.gtfs/index.html
@@ -23,7 +23,7 @@
-
+
diff --git a/components/sensor.haveibeenpwned/index.html b/components/sensor.haveibeenpwned/index.html
index 854ff0bb4d..036d202197 100644
--- a/components/sensor.haveibeenpwned/index.html
+++ b/components/sensor.haveibeenpwned/index.html
@@ -23,7 +23,7 @@
-
+
@@ -125,6 +125,9 @@ account has been breached as well as the added date of the breach data. This dat