Welcome to another great release of Home Assistant! While some of contributors and users are gathering at PyCon US 2017, we still managed to get a great release together!
+
+
First thing for this release is a feature that has been requested a lot: an automation editor! It’s still experimental - and many things are still in progress - but it works! You can create new automations and edit existing ones. If you start a new config, you’re all good to go. Otherwise check these instructions to get your automations ready for editing in the UI.
As the editor is experimental, there are some limitations. These include that Chrome/Chromium is the only supported browser, we don’t support all triggers and actions and there is no support for conditions yet. But the foundation is there and so if you want to contribute to this, come help!
+
+
On the Z-Wave front a lot has happened. The biggest one is that we have a major extension of the Z-Wave panel thanks to @turbokongen! You will now be able to change config parameters and manage your devices.
+
+
+
+
+
Thanks to the work by the Python Open Z-Wave team we are now able to install it on demand from PyPi! There is no longer a need to pre-compile it yourself. This should give us the guarantee that we work with the Python Open Z-Wave version that the code expects.
+
+
+If you have a security key set in your Open Z-Wave options.xml, copy options.xml to your Home Assistant configuration directory. This is the only place where options will get persisted.
+
+
+
Next to that @armills has lead the charge and managed to get full test coverage for Z-Wave! Thanks for all the hard work!
+
+
This release also contains two integrations which could help you to make non-smart devices a little smarter. The file sensor and the seven_segments OCR image processing platform. The first simply reads a plain-text file which was created by a logger or alike. The latter one extracts the value from a captured image that shows a seven-segments display.
+
+
+
+
+
+
And last, but not least, our Docker image is now based off Python 3.6. This version is faster and uses less memory than Python 3.5. Win!
+
+
If you are using our experimental Hass.io image, we made a breaking change in how the panel is served. If you have an existing installation, make sure you update your supervisor to the latest version before updating Home Assistant. If you are going to flash a new Hass.io image, make sure to only flash the new 0.8 image as linked on the installation page.
…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.
Fix automation failing to setup if no automations specified (@balloob - #7647) ([automation.init docs])
+
+
+]]>
+
+
<![CDATA[Home Assistant at PyCon US 2017]]>
@@ -1838,246 +2020,6 @@ Screenshot of all the different functionality the IP webcam integration offers.
-]]>
-
-
-
- <![CDATA[0.39: Configuration panel, state restoration and improved docs]]>
-
- 2017-02-25T08:04:05+00:00
- https://home-assistant.io/blog/2017/02/25/config-panel-and-state-restoration
- It’s time for 0.39 and this release has some amazing new features!
-
-
-
-
T-Shirts
-
-
First off, in case you haven’t seen it yet: we have t-shirts now and they are beautiful. All proceeds from the shirts will be donated to the Electronic Frontier Foundation. The first three days all of you have already raised $400! Still waiting for Teespring to get back to me so stay tuned for the EU store.
-
-
Configuration panel
-
-
Yep, you read that right. We have a configuration panel. It’s just the first of many small steps. Putting in a foundation is important and gives us something to iterate on.
-
-
To start, we have three simple configuration panels:
-
-
-
Core: allows you to validate config, reload core/group/automation config and restart/stop Home Assistant
-
Group: allows you to rename groups, change type between group/view and reorder entities.
-
Z-Wave: allows you to set device specific configuration settings
-
-
-
-
- Screenshot of our new configuration panel.
-
-
-
As a security measure, the configuration panel will need to be activated in the config file to be activated. This can be done by adding the following to your configuration.yaml:
-
-
config:
-
-
-
-
Using our configuration panels will require you to structure your groups and Z-Wave device config according to how the configuration panel expects it. This is on purpose as it we will not be aiming to build a system that supports both our extended set of configuration extend hooks and our configuration panels. It’s one or the other.
-
-
To activate them in your config, create empty files groups.yaml and zwave_device_config.yaml in your config dir and add the following entries to your config:
Note that this is the first release. Things will be missing, things might be broken.
-
-
Reorganized documentation
-
-
Thanks to Fabian we have a great re-organized documentation. Is it perfect yet? No. But we are getting close. We put a lot of focus on making sure the Raspberry Pi is the main focus of our getting started. The other instructions are still available, just not as part of the main getting started.
-
-
State restoration
-
-
Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. Johann has added the foundation for state restoration to Home Assistant. For the initial release support has been added to to input_select and input_boolean components. We will be adding this to more integrations in the future.
-
-
Breaking changes to customize and Z-Wave “customize”
-
-
A couple of releases ago we introduced a new way of doing customize. It became a list that allowed different ways of matching the config to the entity.
-
-
We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn’t like config panels?
-
-
So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.
Ever wondered why the Z-Wave customize was called customize? Yeah, so did we. So when migrating this to the new config format, we decided to upgrade the name too:
…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.
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 11b0d521b1..4eb4868e3e 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
@@ -154,6 +154,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 01e86c55f2..cf30290712 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -142,6 +142,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 7d05848cf6..73175dd5d6 100644
--- a/blog/2015/03/08/new-logo/index.html
+++ b/blog/2015/03/08/new-logo/index.html
@@ -125,6 +125,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 469a73e56f..518b6aef5e 100644
--- a/blog/2015/03/11/release-notes/index.html
+++ b/blog/2015/03/11/release-notes/index.html
@@ -150,6 +150,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 4b8ac1fe3c..b2fc093521 100644
--- a/blog/2015/03/22/release-notes/index.html
+++ b/blog/2015/03/22/release-notes/index.html
@@ -186,6 +186,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 dd9919f7ee..9dd7754bff 100644
--- a/blog/2015/05/14/release-notes/index.html
+++ b/blog/2015/05/14/release-notes/index.html
@@ -208,6 +208,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 4ea99ff5a0..21ab407f8e 100644
--- a/blog/2015/06/10/release-notes/index.html
+++ b/blog/2015/06/10/release-notes/index.html
@@ -254,6 +254,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 12bcf48ae2..a7de780146 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
@@ -218,6 +218,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 117b88394c..ad5ea4084b 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
@@ -201,6 +201,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 33047cb34d..3dc9ba047c 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
@@ -238,6 +238,9 @@ The automation and script syntax here is using a deprecated and no longer suppor
diff --git a/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html b/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
index 9bb058adb6..32ea930760 100644
--- a/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
+++ b/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
@@ -165,6 +165,9 @@ Glances web server started on http://0.0.0.0:61208/
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 511c02fb24..054bc1c66d 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
@@ -161,6 +161,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 78bf131982..a6699d6266 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
@@ -144,6 +144,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 485daa37f3..3e87a1d3c3 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
@@ -329,6 +329,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 93465680d1..53a09cf61c 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
@@ -151,6 +151,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 8999594ab7..8ec041d799 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
@@ -156,6 +156,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 5a997c62e3..6abb22eeb7 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
@@ -153,6 +153,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 8f019bee76..c71f5a87e7 100644
--- a/blog/2016/02/20/community-highlights/index.html
+++ b/blog/2016/02/20/community-highlights/index.html
@@ -155,6 +155,9 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
diff --git a/blog/2016/03/12/z-wave-pep257-templated-service-calls/index.html b/blog/2016/03/12/z-wave-pep257-templated-service-calls/index.html
index 9a9d93f208..0ab400527f 100644
--- a/blog/2016/03/12/z-wave-pep257-templated-service-calls/index.html
+++ b/blog/2016/03/12/z-wave-pep257-templated-service-calls/index.html
@@ -158,6 +158,9 @@ player state attributes. This change affects automations, scripts and scenes.
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 0aa8d4a77d..b34e49b742 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
@@ -200,6 +200,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 76b0b91c45..5a53283990 100644
--- a/blog/2016/07/06/pocketchip-running-home-assistant/index.html
+++ b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
@@ -153,6 +153,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 92b332b216..77d288c85a 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
@@ -163,6 +163,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 1f272b9115..c21057ced8 100644
--- a/blog/2016/07/28/esp8266-and-micropython-part1/index.html
+++ b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
@@ -243,6 +243,9 @@ If a module is missing then you need to download it from the
diff --git a/blog/2016/08/31/esp8266-and-micropython-part2/index.html b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
index 2b2fbf5d85..1a42ead7c8 100644
--- a/blog/2016/08/31/esp8266-and-micropython-part2/index.html
+++ b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
@@ -201,6 +201,9 @@ So, part 1 of ESP8266
diff --git a/blog/2017/01/14/iss-usps-images-packages/index.html b/blog/2017/01/14/iss-usps-images-packages/index.html
index 54139b30c0..4149c5847e 100644
--- a/blog/2017/01/14/iss-usps-images-packages/index.html
+++ b/blog/2017/01/14/iss-usps-images-packages/index.html
@@ -207,6 +207,9 @@ You have to note:
diff --git a/blog/2017/02/03/babyphone/index.html b/blog/2017/02/03/babyphone/index.html
index 92d743f76d..320bff71c8 100644
--- a/blog/2017/02/03/babyphone/index.html
+++ b/blog/2017/02/03/babyphone/index.html
@@ -232,6 +232,9 @@ We change the platform name for binary sensor in 0.38 from
diff --git a/blog/2017/02/04/hassbian-toybox/index.html b/blog/2017/02/04/hassbian-toybox/index.html
index 7625c0fcb4..e456bcd74f 100644
--- a/blog/2017/02/04/hassbian-toybox/index.html
+++ b/blog/2017/02/04/hassbian-toybox/index.html
@@ -158,6 +158,9 @@ On the close horizon from @Landrash th
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 d9e0f95a94..9211b15bb9 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
@@ -333,6 +333,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 25130b5ebc..1eb03fc42b 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
@@ -188,6 +188,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 3e1a863c61..a1ef9ce142 100644
--- a/blog/2017/04/22/ikea-tradfri-spotify/index.html
+++ b/blog/2017/04/22/ikea-tradfri-spotify/index.html
@@ -333,6 +333,9 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
Welcome to another great release of Home Assistant! While some of contributors and users are gathering at PyCon US 2017, we still managed to get a great release together!
+
First thing for this release is a feature that has been requested a lot: an automation editor! It’s still experimental - and many things are still in progress - but it works! You can create new automations and edit existing ones. If you start a new config, you’re all good to go. Otherwise check these instructions to get your automations ready for editing in the UI.
As the editor is experimental, there are some limitations. These include that Chrome/Chromium is the only supported browser, we don’t support all triggers and actions and there is no support for conditions yet. But the foundation is there and so if you want to contribute to this, come help!
+
On the Z-Wave front a lot has happened. The biggest one is that we have a major extension of the Z-Wave panel thanks to @turbokongen! You will now be able to change config parameters and manage your devices.
+
+
+
+
Thanks to the work by the Python Open Z-Wave team we are now able to install it on demand from PyPi! There is no longer a need to pre-compile it yourself. This should give us the guarantee that we work with the Python Open Z-Wave version that the code expects.
+
+If you have a security key set in your Open Z-Wave options.xml, copy options.xml to your Home Assistant configuration directory. This is the only place where options will get persisted.
+
+
Next to that @armills has lead the charge and managed to get full test coverage for Z-Wave! Thanks for all the hard work!
+
This release also contains two integrations which could help you to make non-smart devices a little smarter. The file sensor and the seven_segments OCR image processing platform. The first simply reads a plain-text file which was created by a logger or alike. The latter one extracts the value from a captured image that shows a seven-segments display.
+
+
+
+
And last, but not least, our Docker image is now based off Python 3.6. This version is faster and uses less memory than Python 3.5. Win!
+
If you are using our experimental Hass.io image, we made a breaking change in how the panel is served. If you have an existing installation, make sure you update your supervisor to the latest version before updating Home Assistant. If you are going to flash a new Hass.io image, make sure to only flash the new 0.8 image as linked on the installation page.
…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.
+
+Welcome to another great release of Home Assistant! While some of contributors and users are gathering at PyCon US 2017, we still managed to get a great release together!
+
+First thing for this release is a feature that has been requested a lot: an automation editor! It's still experimental - and many things are still in progress - but it works! You can create new automations and edit existing ones. If you start a new config, you're all good to go. Otherwise check [these instructions](https://home-assistant.io/docs/automation/editor/) to get your automations ready for editing in the UI.
+
+
+
+
+
+Check this [video](https://youtu.be/0j_hWdCTip4) by [Ben](https://twitter.com/BRUHautomation) from [BRUHautomation](http://www.bruhautomation.com/) to see the new release in action.
+
+As the editor is experimental, there are some limitations. These include that Chrome/Chromium is the only supported browser, we don't support all triggers and actions and there is no support for conditions yet. But the foundation is there and so if you want to contribute to this, come help!
+
+On the Z-Wave front a lot has happened. The biggest one is that we have a major extension of the Z-Wave panel thanks to [@turbokongen]! You will now be able to change config parameters and manage your devices.
+
+
+
+
+Thanks to the work by the Python Open Z-Wave team we are now able to install it on demand from PyPi! There is no longer a need to pre-compile it yourself. This should give us the guarantee that we work with the Python Open Z-Wave version that the code expects.
+
+
+If you have a security key set in your Open Z-Wave `options.xml`, copy `options.xml` to your Home Assistant configuration directory. This is the only place where options will get persisted.
+
+
+Next to that [@armills] has lead the charge and managed to get full test coverage for Z-Wave! Thanks for all the hard work!
+
+This release also contains two integrations which could help you to make non-smart devices a little smarter. The [`file` sensor][sensor.file docs] and the [`seven_segments` OCR image processing platform][image_processing.seven_segments docs]. The first simply reads a plain-text file which was created by a logger or alike. The latter one extracts the value from a captured image that shows a seven-segments display.
+
+
+
+
+
+And last, but not least, our Docker image is now based off Python 3.6. This version is faster and uses less memory than Python 3.5. Win!
+
+If you are using our [experimental Hass.io image][hass.io], we made a breaking change in how the panel is served. If you have an existing installation, make sure you update your supervisor to the latest version before updating Home Assistant. If you are going to flash a new Hass.io image, make sure to only flash the new 0.8 image as linked on [the installation page][hass.io-install].
+
+[hass.io]: https://community.home-assistant.io/t/introducing-hass-io/17296
+[hass.io-install]: https://home-assistant.io/hassio/installation/
+
+## New integrations
+
+- Add new raspihats component ([@florincosta] - [#7392]) ([raspihats docs]) (new-platform)
+- Add datadog component ([@nunofgs] - [#7158]) ([datadog docs]) (new-platform)
+- Add support for automation config panel ([@balloob] - [#7509]) ([config.automation docs]) (new-platform)
+- Z-Wave panel API ([@turbokongen] - [#7456]) ([zwave docs]) ([zwave.api docs]) (new-platform)
+- myStrom Buttons support ([@fabaff] - [#7099]) ([binary_sensor.mystrom docs]) (new-platform)
+- Support for the PiFace Digital I/O module ([@basschipper] - [#7494]) ([rpi_pfio docs]) ([binary_sensor.rpi_pfio docs]) ([switch.rpi_pfio docs]) (new-platform)
+- Add raspihats binary sensor ([@florincosta] - [#7508]) ([binary_sensor.raspihats docs]) (new-platform)
+- Support lutron serena shades ([@gurumitts] - [#7565]) ([lutron_caseta docs]) ([cover.lutron_caseta docs]) (new-platform)
+- Add Kira component to sensor and remote platforms ([@stu-gott] - [#7479]) ([kira docs]) ([remote.kira docs]) ([sensor.kira docs]) (new-platform)
+- File sensor ([@fabaff] - [#7569]) ([sensor.file docs]) (new-platform)
+- Seven segments OCR image processing ([@fabaff] - [#7632]) ([image_processing.seven_segments docs]) (new-platform)
+- Axis component ([@Kane610] - [#7381]) ([axis docs]) (new-platform)
+
+## If you need help...
+...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+
+## Reporting Issues
+Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
+
+
+## Breaking changes
+
+- PyPI Openzwave ([@JshWright] - [#7415]) ([zwave docs]) (breaking change)
+- Remove listening to `homeassistant_start` with event automation ([@balloob] - [#7474]) ([automation.event docs]) (breaking change)
+
+## All changes
+
+- Add hass to rfxtrx object ([@danielhiversen] - [#6844])
+- Add new raspihats component ([@florincosta] - [#7392]) ([raspihats docs]) (new-platform)
+- sensor.envirophat: add missing requirement ([@imrehg] - [#7451]) ([sensor.envirophat docs])
+- PyPI Openzwave ([@JshWright] - [#7415]) ([zwave docs]) (breaking change)
+- Add datadog component ([@nunofgs] - [#7158])
+- Add tests for deprecation helpers ([@armills] - [#7452])
+- Forecasts for weather underground ([@pezinek] - [#7062]) ([sensor.wunderground docs])
+- sensor.envirophat: add missing requirement ([@imrehg] - [#7451]) ([sensor.envirophat docs])
+- Switch russound, pymysensors, and pocketcasts to pypi ([@andrey-git] - [#7449])
+- Upgrade pymysensors to 0.10.0 ([@MartinHjelmare] - [#7469])
+- Upgrade Dockerfile to Python 3.6 ([@balloob] - [#7471])
+- Test only dependencies ([@balloob] - [#7472])
+- Update to pyunifi 2.12 ([@finish06] - [#7468]) ([device_tracker.unifi docs])
+- Remove listening to homeassistant_start with event automation ([@balloob] - [#7474]) ([automation.event docs]) (breaking change)
+- Fix plant MIN_TEMPERATURE, MAX_TEMPERATURE validation ([@frog32] - [#7476]) ([plant docs])
+- Forecasts for weather underground ([@pezinek] - [#7062]) ([sensor.wunderground docs])
+- Upgrade pymysensors to 0.10.0 ([@MartinHjelmare] - [#7469])
+- Fix plant MIN_TEMPERATURE, MAX_TEMPERATURE validation ([@frog32] - [#7476]) ([plant docs])
+- Update to pyunifi 2.12 ([@finish06] - [#7468]) ([device_tracker.unifi docs])
+- Uses pypi for deps ([@gurumitts] - [#7485]) ([lutron_caseta docs])
+- 0.44.2 ([@balloob] - [#7488])
+- LIFX: avoid out-of-bounds hue aborting the colorloop effect ([@amelchio] - [#7495])
+- Upgrade async_timeout to 1.2.1 ([@fabaff] - [#7490])
+- Prevent printing of packets. ([@aequitas] - [#7492]) ([rflink docs])
+- Upgrade beautifulsoup4 to 4.6.0 ([@fabaff] - [#7491]) ([device_tracker.linksys_ap docs]) ([sensor.scrape docs])
+- Switch onkyo to pypi ([@andrey-git] - [#7497]) ([media_player.onkyo docs])
+- Fixed potential AttributeError when checking for deleted sources ([@scarface-4711] - [#7502]) ([media_player.denonavr docs])
+- Refactor sun component for correctness ([@armills] - [#7295])
+- new source only forces "play" if the current state is "playing" ([@abmantis] - [#7506]) ([media_player.spotify docs])
+- Correct retrieval of spotify shuffle state ([@andersonshatch] - [#7505]) ([media_player.spotify docs])
+- Fix sonos sleep timer ([@frog32] - [#7503]) ([media_player.sonos docs])
+- Add support for automation config panel ([@balloob] - [#7509]) ([automation.__init__ docs]) ([config.automation docs]) ([config.__init__ docs]) (new-platform)
+- Zwave panel api ([@turbokongen] - [#7456]) ([zwave docs]) ([zwave.api docs]) (new-platform)
+- Update docker dev environment to python3.6 ([@frog32] - [#7520])
+- Switch basicmodem and python-roku to pypi ([@andrey-git] - [#7514]) ([media_player.roku docs]) ([sensor.modem_callerid docs])
+- sensor.envirophat: do not set up platform if hardware is not attached ([@imrehg] - [#7438]) ([sensor.envirophat docs])
+- Telegram Bot enhancements with callback queries and new notification services ([@azogue] - [#7454]) ([telegram_bot docs]) ([notify.telegram docs]) ([telegram_bot.polling docs]) ([telegram_bot.services.yaml docs]) ([telegram_bot.webhooks docs])
+- Add password parameter to uvc component ([@nunofgs] - [#7499]) ([camera.uvc docs])
+- Don't interact with hass directly ([@fabaff] - [#7099]) ([binary_sensor.mystrom docs]) (new-platform)
+- Support for the PiFace Digital I/O module ([@basschipper] - [#7494]) ([rpi_pfio docs]) ([binary_sensor.rpi_pfio docs]) ([switch.rpi_pfio docs]) (new-platform)
+- Upgrade limitlessled to 1.0.7 ([@corneyl] - [#7525]) ([light.limitlessled docs])
+- Update docstrings and log messages ([@fabaff] - [#7526]) ([light.blinksticklight docs]) ([light.enocean docs]) ([light.flux_led docs]) ([light.insteon_local docs]) ([light.insteon_plm docs]) ([light.isy994 docs]) ([light.limitlessled docs]) ([light.mystrom docs])
+- Try to request current_location Automatic scope ([@armills] - [#7447]) ([device_tracker.automatic docs])
+- Add myStrom binary sensor ([@fabaff] - [#7530])
+- Add not-context-manager ([@fabaff] - [#7523])
+- Threadsafe configurator ([@Kane610] - [#7536]) ([configurator docs])
+- Fix for #7459 ([@jumpkick] - [#7544]) ([alexa docs])
+- Upgrade sendgrid to 4.1.0 ([@fabaff] - [#7538]) ([notify.sendgrid docs])
+- Automatic version bump ([@armills] - [#7555]) ([device_tracker.automatic docs])
+- Upgrade dweepy to 0.3.0 ([@fabaff] - [#7550]) ([dweet docs]) ([sensor.dweet docs])
+- Add SSL support to NZBGet sensor ([@tboyce021] - [#7553]) ([sensor.nzbget docs])
+- Do not install all dependencies in dev mode ([@balloob] - [#7548])
+- Hide proximity updates in logbook ([@armills] - [#7549]) ([logbook docs])
+- Only install tox in dev mode ([@balloob] - [#7557])
+- Support adding different server locations for Microsoft face component ([@tsvi] - [#7532]) ([microsoft_face docs])
+- Treat swing and fan level as optional in Sensibo Climate. ([@andrey-git] - [#7560]) ([climate.sensibo docs])
+- LIFX: add lifx_set_state service call ([@amelchio] - [#7552]) ([light.lifx docs])
+- Add raspihats binary sensor ([@florincosta] - [#7508]) ([binary_sensor.raspihats docs]) (new-platform)
+- update pywebpush to 1.0.0 ([@perosb] - [#7561]) ([notify.html5 docs])
+- Initialize sun with correct values. ([@aequitas] - [#7559]) ([sun docs])
+- Comment RasPi specific requirements ([@Juggels] - [#7562]) ([sensor.envirophat docs])
+- Update netdisco ([@balloob] - [#7563])
+- Support lutron serena shades ([@gurumitts] - [#7565]) ([lutron_caseta docs]) ([cover.lutron_caseta docs]) (new-platform)
+- Tests for zwave discovery logic ([@armills] - [#7566])
+- Tests for zwave setup features ([@armills] - [#7570])
+- Blink version bump ([@fronzbot] - [#7571]) ([blink docs]) ([sensor.blink docs])
+- Fix systematic warning in influxdb sensor ([@bestlibre] - [#7541]) ([sensor.influxdb docs])
+- Fix Kodi specific services registry and add descriptions ([@azogue] - [#7551]) ([media_player.kodi docs])
+- Add Kira component to sensor and remote platforms ([@stu-gott] - [#7479]) ([kira docs]) ([remote.kira docs]) ([sensor.kira docs]) (new-platform)
+- Add tests for zwave network events ([@armills] - [#7573])
+- Additional Wink lock features ([@w1ll1am23] - [#7445])
+- Websocket_api: avoid parallel drain ([@balloob] - [#7576]) ([websocket_api docs])
+- Remove more test requirements ([@balloob] - [#7574])
+- camera.zoneminder: Handle old versions of zoneminder ([@mnoorenberghe] - [#7589]) ([camera.zoneminder docs])
+- Pass additional arguments to tox in test_docker ([@frog32] - [#7591])
+- Fix websocket api reaching queue ([@balloob] - [#7590]) ([websocket_api docs])
+- SMTP notify enhancements: full HTML emails and custom `product_name` in email headers ([@azogue] - [#7533]) ([notify.smtp docs])
+- Automation State Change For timer attribute fix ([@armills] - [#7584]) ([automation.state docs])
+- Add posibility to specify snmp protocol version ([@jhemzal] - [#7564]) ([sensor.snmp docs])
+- Add sonos alarm clock update service ([@frog32] - [#7521]) ([media_player.sonos docs])
+- Fix handling of single user ([@mezz64] - [#7587]) ([eight_sleep docs])
+- File sensor ([@fabaff] - [#7569]) ([sensor.file docs]) (new-platform)
+- Make miflora monitored_conditions parameter optional ([@frog32] - [#7598]) ([sensor.miflora docs])
+- Force automation ids to always be a string ([@balloob] - [#7612]) ([automation.__init__ docs])
+- Update Docker base image to python 3.6 ([@pschmitt] - [#7613])
+- Add Content-type: image/jpeg for camera proxy ([@olekenneth] - [#7581]) ([camera.__init__ docs])
+- Fix typo and update style to match the other platforms ([@fabaff] - [#7621]) ([image_processing.opencv docs])
+- Bump pyvera - fixes issue with % in brightness levels. ([@pavoni] - [#7622]) ([vera docs])
+- Add kelvin/brightness_pct alternatives to light.turn_on ([@amelchio] - [#7596]) ([light.lifx docs]) ([light.__init__ docs])
+- Add support for disabling tradfri groups ([@cnrd] - [#7593]) ([tradfri docs]) ([light.tradfri docs])
+- Update docstrings and comments ([@fabaff] - [#7626]) ([image_processing.openalpr_cloud docs]) ([image_processing.openalpr_local docs])
+- Upgrade Sphinx to 1.6.1 ([@fabaff] - [#7624])
+- Update docstrings ([@fabaff] - [#7630]) ([image_processing.demo docs]) ([image_processing.dlib_face_detect docs]) ([image_processing.dlib_face_identify docs]) ([image_processing.microsoft_face_detect docs]) ([image_processing.microsoft_face_identify docs]) ([image_processing.opencv docs])
+- Kodi specific service to call Kodi API methods ([@azogue] - [#7603]) ([media_player.kodi docs])
+- Updated limitlessled requirement to v1.0.8 ([@corneyl] - [#7629])
+- Osram lightify Removed wrong assignment ([@commento] - [#7615]) ([light.osramlightify docs])
+- Updated dependency ([@danielperna84] - [#7638]) ([homematic docs])
+- Seven segments OCR image processing ([@fabaff] - [#7632]) ([image_processing.seven_segments docs]) ([image_processing.__init__ docs]) (new-platform)
+- Abort tests when instances leaked ([@balloob] - [#7623])
+- Coerce color_temp to int even when passed in as kelvin ([@amelchio] - [#7640]) ([light.__init__ docs])
+- Fix automation failing to setup if no automations specified ([@balloob] - [#7647]) ([automation.__init__ docs])
+
+[#6844]: https://github.com/home-assistant/home-assistant/pull/6844
+[#7062]: https://github.com/home-assistant/home-assistant/pull/7062
+[#7099]: https://github.com/home-assistant/home-assistant/pull/7099
+[#7158]: https://github.com/home-assistant/home-assistant/pull/7158
+[#7295]: https://github.com/home-assistant/home-assistant/pull/7295
+[#7381]: https://github.com/home-assistant/home-assistant/pull/7381
+[#7392]: https://github.com/home-assistant/home-assistant/pull/7392
+[#7415]: https://github.com/home-assistant/home-assistant/pull/7415
+[#7438]: https://github.com/home-assistant/home-assistant/pull/7438
+[#7445]: https://github.com/home-assistant/home-assistant/pull/7445
+[#7447]: https://github.com/home-assistant/home-assistant/pull/7447
+[#7449]: https://github.com/home-assistant/home-assistant/pull/7449
+[#7451]: https://github.com/home-assistant/home-assistant/pull/7451
+[#7452]: https://github.com/home-assistant/home-assistant/pull/7452
+[#7454]: https://github.com/home-assistant/home-assistant/pull/7454
+[#7456]: https://github.com/home-assistant/home-assistant/pull/7456
+[#7468]: https://github.com/home-assistant/home-assistant/pull/7468
+[#7469]: https://github.com/home-assistant/home-assistant/pull/7469
+[#7471]: https://github.com/home-assistant/home-assistant/pull/7471
+[#7472]: https://github.com/home-assistant/home-assistant/pull/7472
+[#7474]: https://github.com/home-assistant/home-assistant/pull/7474
+[#7476]: https://github.com/home-assistant/home-assistant/pull/7476
+[#7479]: https://github.com/home-assistant/home-assistant/pull/7479
+[#7485]: https://github.com/home-assistant/home-assistant/pull/7485
+[#7488]: https://github.com/home-assistant/home-assistant/pull/7488
+[#7490]: https://github.com/home-assistant/home-assistant/pull/7490
+[#7491]: https://github.com/home-assistant/home-assistant/pull/7491
+[#7492]: https://github.com/home-assistant/home-assistant/pull/7492
+[#7494]: https://github.com/home-assistant/home-assistant/pull/7494
+[#7495]: https://github.com/home-assistant/home-assistant/pull/7495
+[#7497]: https://github.com/home-assistant/home-assistant/pull/7497
+[#7499]: https://github.com/home-assistant/home-assistant/pull/7499
+[#7502]: https://github.com/home-assistant/home-assistant/pull/7502
+[#7503]: https://github.com/home-assistant/home-assistant/pull/7503
+[#7505]: https://github.com/home-assistant/home-assistant/pull/7505
+[#7506]: https://github.com/home-assistant/home-assistant/pull/7506
+[#7508]: https://github.com/home-assistant/home-assistant/pull/7508
+[#7509]: https://github.com/home-assistant/home-assistant/pull/7509
+[#7514]: https://github.com/home-assistant/home-assistant/pull/7514
+[#7520]: https://github.com/home-assistant/home-assistant/pull/7520
+[#7521]: https://github.com/home-assistant/home-assistant/pull/7521
+[#7523]: https://github.com/home-assistant/home-assistant/pull/7523
+[#7525]: https://github.com/home-assistant/home-assistant/pull/7525
+[#7526]: https://github.com/home-assistant/home-assistant/pull/7526
+[#7530]: https://github.com/home-assistant/home-assistant/pull/7530
+[#7532]: https://github.com/home-assistant/home-assistant/pull/7532
+[#7533]: https://github.com/home-assistant/home-assistant/pull/7533
+[#7536]: https://github.com/home-assistant/home-assistant/pull/7536
+[#7538]: https://github.com/home-assistant/home-assistant/pull/7538
+[#7541]: https://github.com/home-assistant/home-assistant/pull/7541
+[#7544]: https://github.com/home-assistant/home-assistant/pull/7544
+[#7548]: https://github.com/home-assistant/home-assistant/pull/7548
+[#7549]: https://github.com/home-assistant/home-assistant/pull/7549
+[#7550]: https://github.com/home-assistant/home-assistant/pull/7550
+[#7551]: https://github.com/home-assistant/home-assistant/pull/7551
+[#7552]: https://github.com/home-assistant/home-assistant/pull/7552
+[#7553]: https://github.com/home-assistant/home-assistant/pull/7553
+[#7555]: https://github.com/home-assistant/home-assistant/pull/7555
+[#7557]: https://github.com/home-assistant/home-assistant/pull/7557
+[#7559]: https://github.com/home-assistant/home-assistant/pull/7559
+[#7560]: https://github.com/home-assistant/home-assistant/pull/7560
+[#7561]: https://github.com/home-assistant/home-assistant/pull/7561
+[#7562]: https://github.com/home-assistant/home-assistant/pull/7562
+[#7563]: https://github.com/home-assistant/home-assistant/pull/7563
+[#7564]: https://github.com/home-assistant/home-assistant/pull/7564
+[#7565]: https://github.com/home-assistant/home-assistant/pull/7565
+[#7566]: https://github.com/home-assistant/home-assistant/pull/7566
+[#7569]: https://github.com/home-assistant/home-assistant/pull/7569
+[#7570]: https://github.com/home-assistant/home-assistant/pull/7570
+[#7571]: https://github.com/home-assistant/home-assistant/pull/7571
+[#7573]: https://github.com/home-assistant/home-assistant/pull/7573
+[#7574]: https://github.com/home-assistant/home-assistant/pull/7574
+[#7576]: https://github.com/home-assistant/home-assistant/pull/7576
+[#7581]: https://github.com/home-assistant/home-assistant/pull/7581
+[#7584]: https://github.com/home-assistant/home-assistant/pull/7584
+[#7587]: https://github.com/home-assistant/home-assistant/pull/7587
+[#7589]: https://github.com/home-assistant/home-assistant/pull/7589
+[#7590]: https://github.com/home-assistant/home-assistant/pull/7590
+[#7591]: https://github.com/home-assistant/home-assistant/pull/7591
+[#7593]: https://github.com/home-assistant/home-assistant/pull/7593
+[#7596]: https://github.com/home-assistant/home-assistant/pull/7596
+[#7598]: https://github.com/home-assistant/home-assistant/pull/7598
+[#7603]: https://github.com/home-assistant/home-assistant/pull/7603
+[#7612]: https://github.com/home-assistant/home-assistant/pull/7612
+[#7613]: https://github.com/home-assistant/home-assistant/pull/7613
+[#7615]: https://github.com/home-assistant/home-assistant/pull/7615
+[#7621]: https://github.com/home-assistant/home-assistant/pull/7621
+[#7622]: https://github.com/home-assistant/home-assistant/pull/7622
+[#7623]: https://github.com/home-assistant/home-assistant/pull/7623
+[#7624]: https://github.com/home-assistant/home-assistant/pull/7624
+[#7626]: https://github.com/home-assistant/home-assistant/pull/7626
+[#7629]: https://github.com/home-assistant/home-assistant/pull/7629
+[#7630]: https://github.com/home-assistant/home-assistant/pull/7630
+[#7632]: https://github.com/home-assistant/home-assistant/pull/7632
+[#7638]: https://github.com/home-assistant/home-assistant/pull/7638
+[#7640]: https://github.com/home-assistant/home-assistant/pull/7640
+[#7647]: https://github.com/home-assistant/home-assistant/pull/7647
+[@JshWright]: https://github.com/JshWright
+[@Juggels]: https://github.com/Juggels
+[@Kane610]: https://github.com/Kane610
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[@abmantis]: https://github.com/abmantis
+[@aequitas]: https://github.com/aequitas
+[@amelchio]: https://github.com/amelchio
+[@andersonshatch]: https://github.com/andersonshatch
+[@andrey-git]: https://github.com/andrey-git
+[@armills]: https://github.com/armills
+[@azogue]: https://github.com/azogue
+[@balloob]: https://github.com/balloob
+[@basschipper]: https://github.com/basschipper
+[@bestlibre]: https://github.com/bestlibre
+[@cnrd]: https://github.com/cnrd
+[@commento]: https://github.com/commento
+[@corneyl]: https://github.com/corneyl
+[@cribbstechnologies]: https://github.com/cribbstechnologies
+[@danielhiversen]: https://github.com/danielhiversen
+[@danielperna84]: https://github.com/danielperna84
+[@fabaff]: https://github.com/fabaff
+[@finish06]: https://github.com/finish06
+[@florincosta]: https://github.com/florincosta
+[@frog32]: https://github.com/frog32
+[@fronzbot]: https://github.com/fronzbot
+[@gurumitts]: https://github.com/gurumitts
+[@imrehg]: https://github.com/imrehg
+[@jhemzal]: https://github.com/jhemzal
+[@jminardi]: https://github.com/jminardi
+[@jumpkick]: https://github.com/jumpkick
+[@mezz64]: https://github.com/mezz64
+[@mnoorenberghe]: https://github.com/mnoorenberghe
+[@nunofgs]: https://github.com/nunofgs
+[@olekenneth]: https://github.com/olekenneth
+[@pavoni]: https://github.com/pavoni
+[@perosb]: https://github.com/perosb
+[@pezinek]: https://github.com/pezinek
+[@pschmitt]: https://github.com/pschmitt
+[@robbiet480]: https://github.com/robbiet480
+[@scarface-4711]: https://github.com/scarface-4711
+[@stu-gott]: https://github.com/stu-gott
+[@tboyce021]: https://github.com/tboyce021
+[@tsvi]: https://github.com/tsvi
+[@turbokongen]: https://github.com/turbokongen
+[@w1ll1am23]: https://github.com/w1ll1am23
+[alexa docs]: https://home-assistant.io/components/alexa/
+[axis docs]: https://home-assistant.io/components/axis/
+[config.automation docs]: https://home-assistant.io/docs/automation/editor/
+[automation.event docs]: https://home-assistant.io/components/automation.event/
+[automation.state docs]: https://home-assistant.io/components/automation.state/
+[binary_sensor.mystrom docs]: https://home-assistant.io/components/binary_sensor.mystrom/
+[binary_sensor.raspihats docs]: https://home-assistant.io/components/binary_sensor.raspihats/
+[binary_sensor.rpi_pfio docs]: https://home-assistant.io/components/binary_sensor.rpi_pfio/
+[blink docs]: https://home-assistant.io/components/blink/
+[camera.__init__ docs]: https://home-assistant.io/components/camera.__init__/
+[camera.uvc docs]: https://home-assistant.io/components/camera.uvc/
+[camera.zoneminder docs]: https://home-assistant.io/components/camera.zoneminder/
+[climate.sensibo docs]: https://home-assistant.io/components/climate.sensibo/
+[config.__init__ docs]: https://home-assistant.io/components/config.__init__/
+[config.automation docs]: https://home-assistant.io/components/config.automation/
+[configurator docs]: https://home-assistant.io/components/configurator/
+[cover.lutron_caseta docs]: https://home-assistant.io/components/cover.lutron_caseta/
+[datadog docs]: https://home-assistant.io/components/datadog/
+[device_tracker.automatic docs]: https://home-assistant.io/components/device_tracker.automatic/
+[device_tracker.linksys_ap docs]: https://home-assistant.io/components/device_tracker.linksys_ap/
+[device_tracker.unifi docs]: https://home-assistant.io/components/device_tracker.unifi/
+[dweet docs]: https://home-assistant.io/components/dweet/
+[eight_sleep docs]: https://home-assistant.io/components/eight_sleep/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[image_processing.__init__ docs]: https://home-assistant.io/components/image_processing.__init__/
+[image_processing.demo docs]: https://home-assistant.io/components/image_processing.demo/
+[image_processing.dlib_face_detect docs]: https://home-assistant.io/components/image_processing.dlib_face_detect/
+[image_processing.dlib_face_identify docs]: https://home-assistant.io/components/image_processing.dlib_face_identify/
+[image_processing.microsoft_face_detect docs]: https://home-assistant.io/components/image_processing.microsoft_face_detect/
+[image_processing.microsoft_face_identify docs]: https://home-assistant.io/components/image_processing.microsoft_face_identify/
+[image_processing.openalpr_cloud docs]: https://home-assistant.io/components/image_processing.openalpr_cloud/
+[image_processing.openalpr_local docs]: https://home-assistant.io/components/image_processing.openalpr_local/
+[image_processing.opencv docs]: https://home-assistant.io/components/image_processing.opencv/
+[image_processing.seven_segments docs]: https://home-assistant.io/components/image_processing.seven_segments/
+[kira docs]: https://home-assistant.io/components/kira/
+[light.__init__ docs]: https://home-assistant.io/components/light.__init__/
+[light.blinksticklight docs]: https://home-assistant.io/components/light.blinksticklight/
+[light.enocean docs]: https://home-assistant.io/components/light.enocean/
+[light.flux_led docs]: https://home-assistant.io/components/light.flux_led/
+[light.insteon_local docs]: https://home-assistant.io/components/light.insteon_local/
+[light.insteon_plm docs]: https://home-assistant.io/components/light.insteon_plm/
+[light.isy994 docs]: https://home-assistant.io/components/light.isy994/
+[light.lifx docs]: https://home-assistant.io/components/light.lifx/
+[light.limitlessled docs]: https://home-assistant.io/components/light.limitlessled/
+[light.mystrom docs]: https://home-assistant.io/components/light.mystrom/
+[light.osramlightify docs]: https://home-assistant.io/components/light.osramlightify/
+[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
+[logbook docs]: https://home-assistant.io/components/logbook/
+[lutron_caseta docs]: https://home-assistant.io/components/lutron_caseta/
+[media_player.denonavr docs]: https://home-assistant.io/components/media_player.denonavr/
+[media_player.kodi docs]: https://home-assistant.io/components/media_player.kodi/
+[media_player.onkyo docs]: https://home-assistant.io/components/media_player.onkyo/
+[media_player.roku docs]: https://home-assistant.io/components/media_player.roku/
+[media_player.sonos docs]: https://home-assistant.io/components/media_player.sonos/
+[media_player.spotify docs]: https://home-assistant.io/components/media_player.spotify/
+[microsoft_face docs]: https://home-assistant.io/components/microsoft_face/
+[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
+[notify.sendgrid docs]: https://home-assistant.io/components/notify.sendgrid/
+[notify.smtp docs]: https://home-assistant.io/components/notify.smtp/
+[notify.telegram docs]: https://home-assistant.io/components/notify.telegram/
+[plant docs]: https://home-assistant.io/components/plant/
+[raspihats docs]: https://home-assistant.io/components/raspihats/
+[remote.kira docs]: https://home-assistant.io/components/remote.kira/
+[rflink docs]: https://home-assistant.io/components/rflink/
+[rpi_pfio docs]: https://home-assistant.io/components/rpi_pfio/
+[sensor.blink docs]: https://home-assistant.io/components/sensor.blink/
+[sensor.dweet docs]: https://home-assistant.io/components/sensor.dweet/
+[sensor.envirophat docs]: https://home-assistant.io/components/sensor.envirophat/
+[sensor.file docs]: https://home-assistant.io/components/sensor.file/
+[sensor.influxdb docs]: https://home-assistant.io/components/sensor.influxdb/
+[sensor.kira docs]: https://home-assistant.io/components/sensor.kira/
+[sensor.miflora docs]: https://home-assistant.io/components/sensor.miflora/
+[sensor.modem_callerid docs]: https://home-assistant.io/components/sensor.modem_callerid/
+[sensor.nzbget docs]: https://home-assistant.io/components/sensor.nzbget/
+[sensor.scrape docs]: https://home-assistant.io/components/sensor.scrape/
+[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/
+[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/
+[sun docs]: https://home-assistant.io/components/sun/
+[switch.rpi_pfio docs]: https://home-assistant.io/components/switch.rpi_pfio/
+[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
+[telegram_bot.polling docs]: https://home-assistant.io/components/telegram_bot.polling/
+[telegram_bot.services.yaml docs]: https://home-assistant.io/components/telegram_bot.services.yaml/
+[telegram_bot.webhooks docs]: https://home-assistant.io/components/telegram_bot.webhooks/
+[tradfri docs]: https://home-assistant.io/components/tradfri/
+[vera docs]: https://home-assistant.io/components/vera/
+[websocket_api docs]: https://home-assistant.io/components/websocket_api/
+[zwave docs]: https://home-assistant.io/components/zwave/
+[zwave.api docs]: https://home-assistant.io/components/zwave.api/
+[forum]: https://community.home-assistant.io/
+[gitter]: https://gitter.im/home-assistant/home-assistant
+[issue]: https://github.com/home-assistant/home-assistant/issues
+]]>
+
+
<![CDATA[Home Assistant 0.44: ZigBee, OpenCV and DLib]]>
@@ -1790,25 +2202,4 @@ Experiencing issues introduced by this release? Please report them in our [issue
]]>
-
- <![CDATA[0.40.2 and broken dependencies]]>
-
- 2017-03-22T08:04:05+00:00
- https://home-assistant.io/blog/2017/03/22/broken-dependencies
- /deps` directory and stop using the above mentioned integrations. In the case of AppleTV, you will also have to disable the discovery component to prevent it from being auto-detected.]]>
-
-
diff --git a/blog/categories/release-notes/index.html b/blog/categories/release-notes/index.html
index 3e91ec17bb..23261dbadf 100644
--- a/blog/categories/release-notes/index.html
+++ b/blog/categories/release-notes/index.html
@@ -71,6 +71,27 @@
Welcome to another great release of Home Assistant! While some of contributors and users are gathering at PyCon US 2017, we still managed to get a great release together!
+
First thing for this release is a feature that has been requested a lot: an automation editor! It’s still experimental - and many things are still in progress - but it works! You can create new automations and edit existing ones. If you start a new config, you’re all good to go. Otherwise check these instructions to get your automations ready for editing in the UI.
As the editor is experimental, there are some limitations. These include that Chrome/Chromium is the only supported browser, we don’t support all triggers and actions and there is no support for conditions yet. But the foundation is there and so if you want to contribute to this, come help!
+
On the Z-Wave front a lot has happened. The biggest one is that we have a major extension of the Z-Wave panel thanks to @turbokongen! You will now be able to change config parameters and manage your devices.
+
+
+
+
Thanks to the work by the Python Open Z-Wave team we are now able to install it on demand from PyPi! There is no longer a need to pre-compile it yourself. This should give us the guarantee that we work with the Python Open Z-Wave version that the code expects.
+
+If you have a security key set in your Open Z-Wave options.xml, copy options.xml to your Home Assistant configuration directory. This is the only place where options will get persisted.
+
+
Next to that @armills has lead the charge and managed to get full test coverage for Z-Wave! Thanks for all the hard work!
+
This release also contains two integrations which could help you to make non-smart devices a little smarter. The file sensor and the seven_segments OCR image processing platform. The first simply reads a plain-text file which was created by a logger or alike. The latter one extracts the value from a captured image that shows a seven-segments display.
+
+
+
+
And last, but not least, our Docker image is now based off Python 3.6. This version is faster and uses less memory than Python 3.5. Win!
+
If you are using our experimental Hass.io image, we made a breaking change in how the panel is served. If you have an existing installation, make sure you update your supervisor to the latest version before updating Home Assistant. If you are going to flash a new Hass.io image, make sure to only flash the new 0.8 image as linked on the installation page.
…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.
Oooh yeah. It’s time for 0.43 and this is going to be a killer release. For the people that have been following on social media, you might have noticed that we got pretty excited about the new IKEA Trådfri line up. And so we are very happy to announce that thanks to the work by @ggravlingen, @MartinHjelmare and myself that this will be the first release to support the IKEA light bulbs. Home Assistant will automatically detect the gateway on your network and after following the instructions, allow you to control your lights.
-
-
-After automatic discovery, Home Assistant will ask the user to finish pairing with the gateway.
-
-
And in case you have missed the other big news: @robbiet480 released the first version of our iOS app! It took a little over a year but it offers some great ways to make your iDevice work with Home Assistant. Big congrats to Robbie for shipping! As with our other parts, the app is open-sourced under APACHE 2 and contributors are welcome. Check it out.
-
A big shout out this release to @happyleavesaoc for his constant stream of great contributions to Home Assistant. The first contribution was back in October 2015 and since then @happyleavesaoc has been responsible for many platforms and bug fixes including the Spotify platform this release. Thanks @happyleavesaoc, you’re a great example of what makes our community awesome.
-
The new Spotify integration is based on the new Spotify Connect Playback API. It supports playback, album art and switching which Spotify device you’re controlling.
+In this tutorial I will explain how you can activate Tasker tasks from Home Assistant command line switches. We are going to set up a switch that when toggled will make your Android device say either “On” or “Off”.
+
You could also do this with the automation component instead so whenever you put your house to sleep mode for example your Android device will open up Google Play Books or the Kindle app ready for you to read as well as dimming your lights, but this tutorial is all about the switches.
It’s like someone opened a can of rock solid developers and emptied it above our chat channel because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
Migration note: the scheduler component has been removed in favor of the automation component.
-
Sonos
- Sonos support has been added by @rhooper and @SEJeff. Home Assistant is now able to automatically detect Sonos devices in your network and set them up for you. It will allow you to control music playing on your Sonos and change the volume.
-
iTunes and airplay speakers
-@maddox has contributed support for controlling iTunes and airplay speakers. For this to work you will have to run itunes-api on your Mac as middleware.
It’s like someone opened a can of rock solid developers and emptied it above our chat channel because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
Migration note: the scheduler component has been removed in favor of the automation component.
+
Sonos
+ Sonos support has been added by @rhooper and @SEJeff. Home Assistant is now able to automatically detect Sonos devices in your network and set them up for you. It will allow you to control music playing on your Sonos and change the volume.
+
iTunes and airplay speakers
+@maddox has contributed support for controlling iTunes and airplay speakers. For this to work you will have to run itunes-api on your Mac as middleware.
Almost three busy weeks have past since the last release. We used this time to finally make the overhaul to use UTC as the internal date time format. We added a bunch of test coverage in the process to make sure the transition went smoothly. Pleas see the blog post about the UTC refactor for backwards incompatible changes.
-
This release includes a significant startup boost for the frontend and a fix for Wemo discovery after their latest firmware upgrade.
-
I would like to give a big shout out to our newest contributor fabaff for taking the time to improve the documentation.
-
-To update to the latest version, run scripts/update. Please report any issues on GitHub.
-
Almost three busy weeks have past since the last release. We used this time to finally make the overhaul to use UTC as the internal date time format. We added a bunch of test coverage in the process to make sure the transition went smoothly. Pleas see the blog post about the UTC refactor for backwards incompatible changes.
+
This release includes a significant startup boost for the frontend and a fix for Wemo discovery after their latest firmware upgrade.
+
I would like to give a big shout out to our newest contributor fabaff for taking the time to improve the documentation.
+
+To update to the latest version, run scripts/update. Please report any issues on GitHub.
+
@@ -415,42 +446,6 @@ The getting started instructions have been split into separate pages per compone
Home Assistant should now throw better errors and offer solutions if you do not have the right version of Python 3, forgot to clone the git submodules or install the dependencies.
Streamlined first launch
Home Assistant now supports --open-ui and --demo-mode command line properties to open the browser automatically and have something to show. Home Assistant now supports to be run without a password, allowing the interface to login automatically on launch.
For thet majority of its existence, Home Assistant primary focus was on presence detection, lights and switches. But not anymore as we’re expanding the supported devices. Today, we’re proud to introduce Nest Thermostat integration for Home Assistant contributed by Stefano Fiorini!
-
-
-
-
The new integration exists out of two parts: a generic thermostat component and a Nest platform implementation. The initial version implements provides a read-only card and services to control it. The plan is in the future to add temperature and away mode controls from the thermostat card and more info dialog. Internally, we are using the Python package python-nest by jkoelker to talk to the Nest.
-
If you own a Nest thermostat, add the following lines to your home-assistant.conf:
For thet majority of its existence, Home Assistant primary focus was on presence detection, lights and switches. But not anymore as we’re expanding the supported devices. Today, we’re proud to introduce Nest Thermostat integration for Home Assistant contributed by Stefano Fiorini!
+
+
+
+
The new integration exists out of two parts: a generic thermostat component and a Nest platform implementation. The initial version implements provides a read-only card and services to control it. The plan is in the future to add temperature and away mode controls from the thermostat card and more info dialog. Internally, we are using the Python package python-nest by jkoelker to talk to the Nest.
+
If you own a Nest thermostat, add the following lines to your home-assistant.conf:
Oooh yeah. It’s time for 0.43 and this is going to be a killer release. For the people that have been following on social media, you might have noticed that we got pretty excited about the new IKEA Trådfri line up. And so we are very happy to announce that thanks to the work by @ggravlingen, @MartinHjelmare and myself that this will be the first release to support the IKEA light bulbs. Home Assistant will automatically detect the gateway on your network and after following the instructions, allow you to control your lights.
+
+
+After automatic discovery, Home Assistant will ask the user to finish pairing with the gateway.
+
+
And in case you have missed the other big news: @robbiet480 released the first version of our iOS app! It took a little over a year but it offers some great ways to make your iDevice work with Home Assistant. Big congrats to Robbie for shipping! As with our other parts, the app is open-sourced under APACHE 2 and contributors are welcome. Check it out.
+
A big shout out this release to @happyleavesaoc for his constant stream of great contributions to Home Assistant. The first contribution was back in October 2015 and since then @happyleavesaoc has been responsible for many platforms and bug fixes including the Spotify platform this release. Thanks @happyleavesaoc, you’re a great example of what makes our community awesome.
+
The new Spotify integration is based on the new Spotify Connect Playback API. It supports playback, album art and switching which Spotify device you’re controlling.
It’s time for 0.39 and this release has some amazing new features!
-
-
T-Shirts
-
First off, in case you haven’t seen it yet: we have t-shirts now and they are beautiful. All proceeds from the shirts will be donated to the Electronic Frontier Foundation. The first three days all of you have already raised $400! Still waiting for Teespring to get back to me so stay tuned for the EU store.
-
Configuration panel
-
Yep, you read that right. We have a configuration panel. It’s just the first of many small steps. Putting in a foundation is important and gives us something to iterate on.
-
To start, we have three simple configuration panels:
-
-
Core: allows you to validate config, reload core/group/automation config and restart/stop Home Assistant
-
Group: allows you to rename groups, change type between group/view and reorder entities.
-
Z-Wave: allows you to set device specific configuration settings
-
-
-
- Screenshot of our new configuration panel.
-
-
As a security measure, the configuration panel will need to be activated in the config file to be activated. This can be done by adding the following to your configuration.yaml:
-
config:
-
-
-
Using our configuration panels will require you to structure your groups and Z-Wave device config according to how the configuration panel expects it. This is on purpose as it we will not be aiming to build a system that supports both our extended set of configuration extend hooks and our configuration panels. It’s one or the other.
-
To activate them in your config, create empty files groups.yaml and zwave_device_config.yaml in your config dir and add the following entries to your config:
Note that this is the first release. Things will be missing, things might be broken.
-
Reorganized documentation
-
Thanks to Fabian we have a great re-organized documentation. Is it perfect yet? No. But we are getting close. We put a lot of focus on making sure the Raspberry Pi is the main focus of our getting started. The other instructions are still available, just not as part of the main getting started.
-
State restoration
-
Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. Johann has added the foundation for state restoration to Home Assistant. For the initial release support has been added to to input_select and input_boolean components. We will be adding this to more integrations in the future.
-
Breaking changes to customize and Z-Wave “customize”
-
A couple of releases ago we introduced a new way of doing customize. It became a list that allowed different ways of matching the config to the entity.
-
We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn’t like config panels?
-
So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.
Ever wondered why the Z-Wave customize was called customize? Yeah, so did we. So when migrating this to the new config format, we decided to upgrade the name too:
It’s time for 0.39 and this release has some amazing new features!
+
+
T-Shirts
+
First off, in case you haven’t seen it yet: we have t-shirts now and they are beautiful. All proceeds from the shirts will be donated to the Electronic Frontier Foundation. The first three days all of you have already raised $400! Still waiting for Teespring to get back to me so stay tuned for the EU store.
+
Configuration panel
+
Yep, you read that right. We have a configuration panel. It’s just the first of many small steps. Putting in a foundation is important and gives us something to iterate on.
+
To start, we have three simple configuration panels:
+
+
Core: allows you to validate config, reload core/group/automation config and restart/stop Home Assistant
+
Group: allows you to rename groups, change type between group/view and reorder entities.
+
Z-Wave: allows you to set device specific configuration settings
+
+
+
+ Screenshot of our new configuration panel.
+
+
As a security measure, the configuration panel will need to be activated in the config file to be activated. This can be done by adding the following to your configuration.yaml:
+
config:
+
+
+
Using our configuration panels will require you to structure your groups and Z-Wave device config according to how the configuration panel expects it. This is on purpose as it we will not be aiming to build a system that supports both our extended set of configuration extend hooks and our configuration panels. It’s one or the other.
+
To activate them in your config, create empty files groups.yaml and zwave_device_config.yaml in your config dir and add the following entries to your config:
Note that this is the first release. Things will be missing, things might be broken.
+
Reorganized documentation
+
Thanks to Fabian we have a great re-organized documentation. Is it perfect yet? No. But we are getting close. We put a lot of focus on making sure the Raspberry Pi is the main focus of our getting started. The other instructions are still available, just not as part of the main getting started.
+
State restoration
+
Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. Johann has added the foundation for state restoration to Home Assistant. For the initial release support has been added to to input_select and input_boolean components. We will be adding this to more integrations in the future.
+
Breaking changes to customize and Z-Wave “customize”
+
A couple of releases ago we introduced a new way of doing customize. It became a list that allowed different ways of matching the config to the entity.
+
We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn’t like config panels?
+
So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.
Ever wondered why the Z-Wave customize was called customize? Yeah, so did we. So when migrating this to the new config format, we decided to upgrade the name too:
I am not Paulus. My name is Ben. I’m the creator of the BRUH Automation YouTube channel. If you’ve ever seen any of my videos then you’ll know I love home automation and Home Assistant.
-
I wanted to share some exciting stats from one of my latest projects - Control My Christmas tree! For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publically accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.
-
I added three devices to the Home Assistant instance - a Wemo Insight, Sonoff Switch (running MQTT firmware), and a DIY MQTT Digital LED strip. After adding a few 3D printed Star War decorations, the tree was ready to go!
I am not Paulus. My name is Ben. I’m the creator of the BRUH Automation YouTube channel. If you’ve ever seen any of my videos then you’ll know I love home automation and Home Assistant.
+
I wanted to share some exciting stats from one of my latest projects - Control My Christmas tree! For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publically accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.
+
I added three devices to the Home Assistant instance - a Wemo Insight, Sonoff Switch (running MQTT firmware), and a DIY MQTT Digital LED strip. After adding a few 3D printed Star War decorations, the tree was ready to go!
It’s based on Raspbian Lite and generated with a fork of the same script that builds the official Raspbian images. For installation of HASS it follows the same install instructions as the Manual installation. Please note that this project has no association with the Raspberry Pi foundation or their projects.
-
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.
It’s based on Raspbian Lite and generated with a fork of the same script that builds the official Raspbian images. For installation of HASS it follows the same install instructions as the Manual installation. Please note that this project has no association with the Raspberry Pi foundation or their projects.
+
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.
When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!
-
Starting with this release, we are extending our extensability to the frontend. Starting this release, any component can add it’s own page to the frontend. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!
-
We have also seen an exciting trend of people starting to visualize their Internet of Things data using Jupyter Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the blog post by @kireyeu shows an advanced usecase while our Notebooks in the Home Assistant Notebooks repository cover the basics.
-
This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant can talk to 26 different media players!
-
The brand-new iFrame panel component allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.
-
I would like to do a shoutout to @fabianhjr. He has started adding typing data (PEP484) to the Home Assistant core. This will help us identify issues before they are released.
When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!
+
Starting with this release, we are extending our extensability to the frontend. Starting this release, any component can add it’s own page to the frontend. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!
+
We have also seen an exciting trend of people starting to visualize their Internet of Things data using Jupyter Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the blog post by @kireyeu shows an advanced usecase while our Notebooks in the Home Assistant Notebooks repository cover the basics.
+
This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant can talk to 26 different media players!
+
The brand-new iFrame panel component allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.
+
I would like to do a shoutout to @fabianhjr. He has started adding typing data (PEP484) to the Home Assistant core. This will help us identify issues before they are released.
It’s time for release 0.21 and it contains massive core improvements: replacement of our home grown HTTP stack with a standardized WSGI stack. This will improve performance, speed, security and make future development of advanced HTTP features a breeze.
-
This work was driven by the amazing Josh Wright. His knowledge, high standards and drive for security has helped improve Home Assistant a lot ever since he started helping out. Hip hip hurray for Josh!
Media Player: Kodi now supports different turn off commands (@armills)
-
-
Breaking Changes
-
-
Our work in the WSGI stack is not fully done yet. We still have a minor issues where retrieving the error log in the about screen can raise an encoding error
-
The API used to incorrectly accept a JSON body with form-url-encoded headers. Our cURL examples on the website used to be wrong and have been updated.
-
Make sure your configuration.yaml file contains frontend: to serve the frontend
-
-
Hotfixes 0.21.1 and 0.21.2
-
We released two hotfixes to address some issues that couldn’t wait till the next release.
-
0.21.1 - June 12
-
-
Add eventlet to base requirements to resolve some installation issues (@balloob)
-
GTFS will filter out routes in the wrong direction (@imrehg)
-
Recover from rare error condition from LIRC (@partofthething)
-
Z-Wave autoheal will no longer raise exception (@balloob)
-
Alexa will now execute the script before making reply (@balloob)
It’s time for release 0.21 and it contains massive core improvements: replacement of our home grown HTTP stack with a standardized WSGI stack. This will improve performance, speed, security and make future development of advanced HTTP features a breeze.
+
This work was driven by the amazing Josh Wright. His knowledge, high standards and drive for security has helped improve Home Assistant a lot ever since he started helping out. Hip hip hurray for Josh!
Media Player: Kodi now supports different turn off commands (@armills)
+
+
Breaking Changes
+
+
Our work in the WSGI stack is not fully done yet. We still have a minor issues where retrieving the error log in the about screen can raise an encoding error
+
The API used to incorrectly accept a JSON body with form-url-encoded headers. Our cURL examples on the website used to be wrong and have been updated.
+
Make sure your configuration.yaml file contains frontend: to serve the frontend
+
+
Hotfixes 0.21.1 and 0.21.2
+
We released two hotfixes to address some issues that couldn’t wait till the next release.
+
0.21.1 - June 12
+
+
Add eventlet to base requirements to resolve some installation issues (@balloob)
+
GTFS will filter out routes in the wrong direction (@imrehg)
+
Recover from rare error condition from LIRC (@partofthething)
+
Z-Wave autoheal will no longer raise exception (@balloob)
+
Alexa will now execute the script before making reply (@balloob)
It’s time for 0.18. This release cycle is 2 days shorter than usual as I’ll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.
-
Since the last release we have moved all Home Assistant source code etc into it’s own organisation on GitHub. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.
Media player: Plex will now monitor the server and add clients as they pop up (@infamy)
-
Core: We now use iso8601 for datetimes (@balloob).
-
Media Player: MPD now supports service to play playlists (@Cinntax)
-
Z-Wave should be a little bit more stable (@Turbokongen)
-
Media Player: Sonos will now only add visible devices (@jpmossin)
-
Light: Wink will now allow controlling the colors (@bradsk88)
-
-
Breaking changes
-
-
We have migrated our datetime format to be iso8601. This will only impact you if you are consuming the date times from the API directly. You can ignore this if you are just using Home Assistant via configuration and the frontend.
-
The constant TEMP_CELCIUS is now correctly called TEMP_CELSIUS. Old one is deprecated and will eventually be removed.
-
The location of the Docker image has changed. There was no possibility for us to keep maintaining the old image (as it was bound to the GitHub repo under my name) or to make a redirect. So if you are using the Home Assistant Docker image, change it to run homeassistant/home-assistant:latest for the latest release and homeassistant/home-assistant:dev for the latest dev version.
-
MySensors received two big changes that will cause you to update your configs. See component page for new example config.
-
-
All MySensors entity IDs are different! There was an error in the naming that caused MySensors to append node ID and child ID instead of separating them with an underscore. This has been fixed but will cause all your MySensors entity IDs to change. This is a one time breaking change.
-
The second change is that we now support the TCP ethernet gateway. This is causing a slight change to the config format: you have to change port: under gateways to device:.
It’s time for 0.18. This release cycle is 2 days shorter than usual as I’ll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.
+
Since the last release we have moved all Home Assistant source code etc into it’s own organisation on GitHub. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.
Media player: Plex will now monitor the server and add clients as they pop up (@infamy)
+
Core: We now use iso8601 for datetimes (@balloob).
+
Media Player: MPD now supports service to play playlists (@Cinntax)
+
Z-Wave should be a little bit more stable (@Turbokongen)
+
Media Player: Sonos will now only add visible devices (@jpmossin)
+
Light: Wink will now allow controlling the colors (@bradsk88)
+
+
Breaking changes
+
+
We have migrated our datetime format to be iso8601. This will only impact you if you are consuming the date times from the API directly. You can ignore this if you are just using Home Assistant via configuration and the frontend.
+
The constant TEMP_CELCIUS is now correctly called TEMP_CELSIUS. Old one is deprecated and will eventually be removed.
+
The location of the Docker image has changed. There was no possibility for us to keep maintaining the old image (as it was bound to the GitHub repo under my name) or to make a redirect. So if you are using the Home Assistant Docker image, change it to run homeassistant/home-assistant:latest for the latest release and homeassistant/home-assistant:dev for the latest dev version.
+
MySensors received two big changes that will cause you to update your configs. See component page for new example config.
+
+
All MySensors entity IDs are different! There was an error in the naming that caused MySensors to append node ID and child ID instead of separating them with an underscore. This has been fixed but will cause all your MySensors entity IDs to change. This is a one time breaking change.
+
The second change is that we now support the TCP ethernet gateway. This is causing a slight change to the config format: you have to change port: under gateways to device:.
+
+
+
+
+
+
@@ -489,39 +552,6 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
Would you like to listen to music in every room in your home, controlled from one source? Then multi-room audio is for you.
-
Multi-room audio can be achieved by having a computer attached to speakers in every room. On each computer, services run to play and/or control the audio. With this DIY approach, the kind of computer and speakers is very much up to you. It could be your desktop computer with attached powered speakers, your HTPC hooked up to your TV and receiver, a Raspberry Pi with Amp or DAC, or even an Android device.
-
You’ll need two key software packages, besides Home Assistant. The first is Mopidy, a music server that can play local files, or connect to streaming music services like Spotify. The second is Snapcast, which enables synchronized audio streaming across your network. Both can be integrated into Home Assistant. Each room audio device will run an instance of the Snapcast client, and optionally a Mopidy instance. Your server will run a special instance of Mopidy and the Snapcast server.
-
Finally, you also need a player to control Mopidy. Any MPD-compatible player will work, and there are several Mopidy-only web-based options available. On Android, Remotedy is particularly nice since you can access multiple Mopidy instances in one place.
-
Home Assistant will provide device status, and volume control for each room. If you want to play music in all your rooms (on all your clients), access the server instance of Mopidy. If you want to play music only in a specific room, access that specific Mopidy instance. If you’re using a web UI for Mopidy, you can add links to each instance in Home Assistant with the weblink component.
Would you like to listen to music in every room in your home, controlled from one source? Then multi-room audio is for you.
+
Multi-room audio can be achieved by having a computer attached to speakers in every room. On each computer, services run to play and/or control the audio. With this DIY approach, the kind of computer and speakers is very much up to you. It could be your desktop computer with attached powered speakers, your HTPC hooked up to your TV and receiver, a Raspberry Pi with Amp or DAC, or even an Android device.
+
You’ll need two key software packages, besides Home Assistant. The first is Mopidy, a music server that can play local files, or connect to streaming music services like Spotify. The second is Snapcast, which enables synchronized audio streaming across your network. Both can be integrated into Home Assistant. Each room audio device will run an instance of the Snapcast client, and optionally a Mopidy instance. Your server will run a special instance of Mopidy and the Snapcast server.
+
Finally, you also need a player to control Mopidy. Any MPD-compatible player will work, and there are several Mopidy-only web-based options available. On Android, Remotedy is particularly nice since you can access multiple Mopidy instances in one place.
+
Home Assistant will provide device status, and volume control for each room. If you want to play music in all your rooms (on all your clients), access the server instance of Mopidy. If you want to play music only in a specific room, access that specific Mopidy instance. If you’re using a web UI for Mopidy, you can add links to each instance in Home Assistant with the weblink component.
-In this tutorial I will explain how you can activate Tasker tasks from Home Assistant command line switches. We are going to set up a switch that when toggled will make your Android device say either “On” or “Off”.
-
You could also do this with the automation component instead so whenever you put your house to sleep mode for example your Android device will open up Google Play Books or the Kindle app ready for you to read as well as dimming your lights, but this tutorial is all about the switches.
diff --git a/components/arduino/index.html b/components/arduino/index.html
index 9ea300bed1..142dfaa09f 100644
--- a/components/arduino/index.html
+++ b/components/arduino/index.html
@@ -160,9 +160,15 @@ A word of caution: The Arduino boards are not storing states. This means that wi
Axis Communications devices are surveillance cameras and other security related network connected hardware. Sensor API works with firmware 5.50 and newer.
+
Home Assistant will automatically discover their presence on your network.
+
You can also manually configure your devices by adding the following lines to your configuration.yaml file:
host (Required): The IP address to your Axis device.
+
username (Optional): The username to your Axis device. Default ‘root’.
+
password (Optional): The password to your Axis device. Default ‘pass’.
+
trigger_time (Optional): Minimum time (in seconds) a sensor should keep its positive value. Default 0.
+
+
location (Optional): Physical location of your Axis device. Default not set.
+
+
include (Required): This cannot be empty else there would be no use adding the device at all.
+
+
camera: Stream MJPEG video to Home Assistant
+
motion: The Built in motion detection in Axis cameras
+
vmd3: ACAP Motion Detection app which has better algorithms for motion detection
+
pir: PIR sensor that can trigger on motion
+
sound: Sound detector
+
daynight: Certain cameras have day/night mode if they have built-in IR lights
+
tampering: signals when camera believes that it has been tampered with
+
input: trigger on whatever you have connected to device input port
+
+
+
+
+Any specific levels for triggers needs to be configured on the device.
+
+
+ It is recommended that you create a user on your Axis device specifically for Home Assistant. For all current functionality it is enough to create a user belonging to user group viewer.
+
diff --git a/components/binary_sensor.arest/index.html b/components/binary_sensor.arest/index.html
index 2438a2f6e1..53b8514067 100644
--- a/components/binary_sensor.arest/index.html
+++ b/components/binary_sensor.arest/index.html
@@ -140,6 +140,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 ee0ed792e8..1769147e74 100644
--- a/components/binary_sensor.blink/index.html
+++ b/components/binary_sensor.blink/index.html
@@ -111,6 +111,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 e6f91cfbf4..1cf88ad29b 100644
--- a/components/binary_sensor.ffmpeg_motion/index.html
+++ b/components/binary_sensor.ffmpeg_motion/index.html
@@ -130,6 +130,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 7e9667b1b0..a3ac7e671e 100644
--- a/components/binary_sensor.ffmpeg_noise/index.html
+++ b/components/binary_sensor.ffmpeg_noise/index.html
@@ -121,6 +121,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 89fd035a9f..40a9118bf1 100644
--- a/components/binary_sensor.http/index.html
+++ b/components/binary_sensor.http/index.html
@@ -156,6 +156,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
The mystrom binary sensor platform allows you to use myStrom Wifi Buttons with Home Assistant. The myStrom Wifi Buttons support three and the myStrom WiFi Button + four different push pattern:
+
+
single: Short push (approx. 1/2 seconds)
+
double: 2x sequential short pushes (within 2 seconds)
+
long: Long push (approx. 2 seconds)
+
touch: Touch of the button’s surface (only affective for WiFi Button +)
+
+
The first usage of the pattern will create the binary sensor for the pattern. If the WiFi Button is pushed one time then a binary sensor for the single pattern will be created. The same applies for the other patterns. With the second usage of the pattern the binary sensors become fully functional.
+
The buttons will give you feedback with its built-in LED:
+
+
white then green: Pattern was submitted successfully
+
white then red: There is a problem with the communication
+
+
To use your myStrom WiFi Button in your installation, add the following to your configuration.yaml file:
+
# Example configuration.yaml entry
+binary_sensor:
+ -platform:mystrom
+
+
+
Setup of the myStrom Buttons
+
After the Wifi Buttons are connected to your Wireless network, you have three minutes to set the actions for the push patterns. The fastest way is to use curl. Check the documentation of the WiFi Button for further details about implementation (http:// is replaced by get:// or post://). action is the name of the corresponding push pattern.
+
$ curl -d "[action]=get://[IP address Home Assistant]:8123/api/mystrom?single%3D[ID of the button]" http://[IP address of the button]/api/v1/device/[MAC address of the button]
+{
+ "[MAC address of the button]": {
+ "type": "button",
+ "battery": true,
+ "reachable": true,
+ "meshroot": false,
+ "charge": true,
+ "voltage": 4.292,
+ "fw_version": "2.26",
+ "single": "get://[IP address Home Assistant]:8123/api/mystrom?single=[if of the button]",
+ "double": "",
+ "long": "",
+ "touch": ""
+ }
+}
+
+
+
A complete command to set the URL for a double click could look like the example below:
+The firmware version 2.26 doesn’t support TLS/SSL. This means that you are only able to use the WiFi Buttons if you are using plain-text communication between Home Assistant and the clients/entities.
+
+
+
+
+
+
+
+
+
+
diff --git a/components/binary_sensor.nest/index.html b/components/binary_sensor.nest/index.html
index 96f4e5842a..06f7fa2baf 100644
--- a/components/binary_sensor.nest/index.html
+++ b/components/binary_sensor.nest/index.html
@@ -154,6 +154,9 @@ You must have the Nest component configured to u
diff --git a/components/binary_sensor.octoprint/index.html b/components/binary_sensor.octoprint/index.html
index f17b171d71..8813afd79e 100644
--- a/components/binary_sensor.octoprint/index.html
+++ b/components/binary_sensor.octoprint/index.html
@@ -130,6 +130,9 @@ You must have the OctoPrint component confi
diff --git a/components/binary_sensor.pilight/index.html b/components/binary_sensor.pilight/index.html
index 5912e4d173..bd09cd9f0f 100644
--- a/components/binary_sensor.pilight/index.html
+++ b/components/binary_sensor.pilight/index.html
@@ -133,6 +133,9 @@ Two type of pilight binary sensor configuration available. A normal sensor which
diff --git a/components/binary_sensor.ping/index.html b/components/binary_sensor.ping/index.html
index 8974273cd7..9d290a5308 100644
--- a/components/binary_sensor.ping/index.html
+++ b/components/binary_sensor.ping/index.html
@@ -126,6 +126,9 @@ When run on Windows systems, the round trip time attributes are rounded to the n
diff --git a/components/binary_sensor.wink/index.html b/components/binary_sensor.wink/index.html
index 45c22f5368..969ad58bd7 100644
--- a/components/binary_sensor.wink/index.html
+++ b/components/binary_sensor.wink/index.html
@@ -151,6 +151,9 @@ The above devices are confimed 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 847c1e2cb6..ea8b08430e 100644
--- a/components/binary_sensor.workday/index.html
+++ b/components/binary_sensor.workday/index.html
@@ -131,6 +131,9 @@ If you use the sensor for Canada (CA) wit
A sensor per camera that reports unread notification (ie. detected motion events).
-
Since the cameras are battery operated, the images are only updated in Home Assistant when the user manually forces a new photo. The image can only be updated in Home Assistant every 60 seconds in order to not overwhelm Blink’s servers with API requests.
+
Since the cameras are battery operated, the images are only updated in Home Assistant when the user manually forces a new photo. This image can be updated with the blink.snap_picture service followed by a blink.force_update service call to force Home Assistant to request an update from Blink’s servers. If the blink.force_update service is not called, the image will be updated within a 180 second interval, set so that automatic server requests don’t overwhelm the Blink API. As a note, all of the camera-specific sensors are only polled when a new image is requested from the camera. This means that relying on any of these sensors to provide timely and accurate data is not recommended.
Services:
There are three services availiabe for the blink platform:
arm_system
arm_camera
snap_picture
+
force_update
-
For arm_system, the value sent can be either “True” or “False” and will arm and disarm the whole blink system, respectively
+
For blink.arm_system, the value sent can be either “True” or “False” and will arm and disarm the whole blink system, respectively
Arm system example
{"device_armed":"True"}
-
Arm camera follows a similar structure, but each indidivual camera can have motion detection enabled or disabled. Because of this, you also need to supply a name. For example, if I have a camera named “Living Room” and I want to turn off motion detection on that camera, I’d call the blink.arm_camera service with the following payload:
+
Arm camera follows a similar structure, but each indidivual camera can have motion detection enabled or disabled. Because of this, you also need to supply a name. For example, if I have a camera named “Living Room” and I want to turn off motion detection on that camera, I’d call the blink.arm_camera service with the following payload:
name (Optional): This parameter allows you to override the name of your camera. The default is “Amcrest Camera”.
port (Optional): The port that the camera is running on. The default is 80.
resolution (Optional): This parameter allows you to specify the camera resolution. For a high resolution (1080/720p), specify the option high. For VGA resolution (640x480p), specify the option low. If omitted, it defaults to high.
-
stream_source (Optional): The data source for the live stream. mjpeg will use the camera’s native MJPEG stream, whereas snapshot will use the camera’s snapshot API to create a stream from still images. If omitted, it defaults to mjpeg.
+
stream_source (Optional): The data source for the live stream. mjpeg will use the camera’s native MJPEG stream, whereas snapshot will use the camera’s snapshot API to create a stream from still images. You can also set the rtsp option to generate the streaming via RTSP protocol. If omitted, it defaults to mjpeg.
+
ffmpeg_arguments: (Optional): Extra options to pass to ffmpeg, e.g. image quality or video filter options.
Note: Amcrest cameras with newer firmwares no longer have the ability to stream high definition video with MJPEG encoding. You may need to use low resolution stream or the snapshot stream source instead. If the quality seems too poor, lower the Frame Rate (FPS) and max out the Bit Rate settings in your camera’s configuration manager.
+
Note: If you set the stream_source option to rtsp, make sure to follow the steps mentioned at
+FFMPEG documentation to install the ffmpeg.
To check if your Amcrest camera is supported/tested, visit the supportability matrix link from the python-amcrest project.
The Axis camera platform allows you to stream video from your Axis cameras.
+
The requirement is that you have setup your Axis camera.
+
+
+
+
+
+
+
+
+
diff --git a/components/camera.blink/index.html b/components/camera.blink/index.html
index c2c7baf272..31a682807f 100644
--- a/components/camera.blink/index.html
+++ b/components/camera.blink/index.html
@@ -105,6 +105,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 1ac4876425..b8c0a3471d 100644
--- a/components/camera.foscam/index.html
+++ b/components/camera.foscam/index.html
@@ -108,6 +108,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 f7dcce6520..1fb9eee8d0 100644
--- a/components/camera.local_file/index.html
+++ b/components/camera.local_file/index.html
@@ -108,6 +108,9 @@ The given file_path must be an existing f
diff --git a/components/camera.mjpeg/index.html b/components/camera.mjpeg/index.html
index 7ea1e1a58f..213f660e7b 100644
--- a/components/camera.mjpeg/index.html
+++ b/components/camera.mjpeg/index.html
@@ -108,6 +108,9 @@ There is a Nest component configured to u
diff --git a/components/camera.synology/index.html b/components/camera.synology/index.html
index e18c1f0b8b..3e3ddcaccb 100644
--- a/components/camera.synology/index.html
+++ b/components/camera.synology/index.html
@@ -122,6 +122,9 @@ Most users will need to set verify_ssl to
diff --git a/components/camera.zoneminder/index.html b/components/camera.zoneminder/index.html
index 2236bc1647..40e32819f9 100644
--- a/components/camera.zoneminder/index.html
+++ b/components/camera.zoneminder/index.html
@@ -112,6 +112,9 @@ You must have the ZoneMinder component con
To get your Lutron Caseta covers working with Home Assistant, follow the instructions for the general Lutron Caseta component.
+
+
+
+
+
+
+
+
+
diff --git a/components/cover.mqtt/index.html b/components/cover.mqtt/index.html
index 00d8d7838b..9dba99b3d0 100644
--- a/components/cover.mqtt/index.html
+++ b/components/cover.mqtt/index.html
@@ -222,6 +222,9 @@ state from state_topic. If these messages
diff --git a/components/cover.wink/index.html b/components/cover.wink/index.html
index 889193c984..64cd6dfa7e 100644
--- a/components/cover.wink/index.html
+++ b/components/cover.wink/index.html
@@ -149,6 +149,9 @@ The above devices are confimed to work, but others may work as well.
Datadog allows you to analyze, monitor, cross-reference and alert upon your data. You can use it to detect statistical anomalies, see graphs across multiple sources in real-time, send critical alerts to Slack, etc.
+
+
+
+
The component also sends events from the logbook into Datadog, allowing you to correlate these events with your data.
+
+
+
+
To use the datadog component in your installation, add the following to your configuration.yaml file:
+
# Example configuration.yaml entry
+datadog:
+
+
+
Configuration variables:
+
+
host (Optional): The IP address or hostname of your Datadog host, e.g. 192.168.1.23. Defaults to localhost.
+
port (Optional): Port to use. Defaults to 8125.
+
prefix (Optional): Prefix to use. Defaults to hass.
+
rate (Optional): The sample rate of UDP packets sent to Datadog. Defaults to 1.
The automatic platform offers presence detection by retrieving your car’s information from the Automatic cloud service.
To use Automatic with Home Assistant, first you must create a free development account. Automatic will generate a Client ID and Secret for you to use in your Home Assistant configuration. You will also need to update your Event Delivery preferences to ensure Home Assistant can receive updates. On the developer page, under App Settings / Event Delivery, select “Websocket” for Event Delivery Preference.
+
Home Assistant will also take advantage of scope:current_location if available. This will allow Home Assistant to receive periodic location updates during a trip. In order to use this functionality, you must request the scope for your application from Automatic. Once scope:current_location is available, Home Assistant will automatically make use of it after the next restart.
Once your developer account is created, add the following to your configuration.yaml file:
# Example configuration.yaml entrydevice_tracker:
diff --git a/components/device_tracker.mikrotik/index.html b/components/device_tracker.mikrotik/index.html
index 50844fc596..ee22517fb1 100644
--- a/components/device_tracker.mikrotik/index.html
+++ b/components/device_tracker.mikrotik/index.html
@@ -66,15 +66,14 @@
-
The Mikrotik platform offers presence detection by looking at connected devices to a Mikrotik Routerboard based router.
+
The mikrotik platform offers presence detection by looking at connected devices to a Mikrotik Routerboard based router.
To use an Mikrotik router in your installation, add the following to your configuration.yaml file:
- Introduced in release: 0.43
+ Introduced in release: 0.44
This is a platform for
diff --git a/components/digital_ocean/index.html b/components/digital_ocean/index.html
index 025abebb8a..36e393f433 100644
--- a/components/digital_ocean/index.html
+++ b/components/digital_ocean/index.html
@@ -116,6 +116,9 @@
diff --git a/components/emulated_hue/index.html b/components/emulated_hue/index.html
index 8a5f4d826f..e1bf483382 100644
--- a/components/emulated_hue/index.html
+++ b/components/emulated_hue/index.html
@@ -193,6 +193,9 @@ The virtual bridge has the ability to turn entities on or off, or change the bri
Introduction
diff --git a/components/history/index.html b/components/history/index.html
index 154c09e205..60f83aa7dc 100644
--- a/components/history/index.html
+++ b/components/history/index.html
@@ -173,6 +173,9 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D
diff --git a/components/homematic/index.html b/components/homematic/index.html
index 7089352c43..d9c16e7d4d 100644
--- a/components/homematic/index.html
+++ b/components/homematic/index.html
@@ -282,6 +282,9 @@ Using this service provides you direct access to the setValue-method of the prim
Introduction
diff --git a/components/ifttt.manything/index.html b/components/ifttt.manything/index.html
index 5cdcb4cb46..6b82edf866 100644
--- a/components/ifttt.manything/index.html
+++ b/components/ifttt.manything/index.html
@@ -151,6 +151,9 @@ For ManyThing support, you need to set up an on<
The seven_segments image processing platform allows you to read physical seven segments displays through Home Assistant. ssocr is used to extract the value shown on the display which is observed by a camera. ssocr need to be available on your system. Check the installation instruction for Fedora below or use $ sudo apt-get install ssocr on a Debian-based system:
+
$ sudo dnf -y install imlib2-devel
+$ git clone https://github.com/auerswal/ssocr.git
+$ cd ssocr
+$ make
+$ sudo make PREFIX=/usr install
+
+
+
To enable the OCR of a seven segement display in your installation, add the following to your configuration.yaml file:
ssocr_bin (Optional): The command line tool ssocr. Set it if you use a different name for the executable. Defaults to ssorc.
+
x_position (Optional): X coordinate of the upper left corner of the area to crop. Defaults to 0.
+
y_position (Optional): Y coordinate of the upper left corner of the area to crop. Defaults to 0.
+
height (Optional): Height of the area to crop. Defaults to 0.
+
width (Optional): Width of the area to crop. Defaults to 0.
+
threshold (Optional): Threshold for the difference between the digits and the background. Defaults to 0.
+
digits (Optional): Number of digits in the display. Defaults to -1.
+
source array (Required): List of image sources.
+
+
entity_id (Required): A camera entity id to get picture from.
+
name (Optional): This parameter allows you to override the name of your image_processing entity.
+
+
+
+
Setup process
+
It’s suggested that the first attempt to determine the needed parameters is using ssocr directly. This may require a couple of iterations to get the result
+
+
+
+
diff --git a/components/image_processing/index.html b/components/image_processing/index.html
index d625c3d1cd..219d95c1d7 100644
--- a/components/image_processing/index.html
+++ b/components/image_processing/index.html
@@ -137,6 +137,9 @@ If you are running Home Assistant over SSL or from within a container, you will
diff --git a/components/index.html b/components/index.html
index 9738f800e9..0a404f6a1f 100644
--- a/components/index.html
+++ b/components/index.html
@@ -72,39 +72,39 @@ Support for these components is provided by the Home Assistant community.
diff --git a/components/insteon_hub/index.html b/components/insteon_hub/index.html
index f35e28e9d8..c55805c352 100644
--- a/components/insteon_hub/index.html
+++ b/components/insteon_hub/index.html
@@ -117,6 +117,9 @@ This component has been disabled due to a complaint by Insteon. It will be enabl
The kira component is the main component to integrate Keene Electronics IR over IP Kira modules with Home Assistant.
+
Example Configuration
+
# Example configuration.yaml entry
+kira:
+
+
+
Kira modules have no built-in mechanism for auto-discovery, so will need to be configured to send packets to Home Assistant. Documentation for this can be found on the manufacturer’s website Here.
code (Required): The data for this code (see below).
+
device (Optional): The device this code is associated with. Default is “unknown”.
+
type (Optional): The type of this code. If this field is omitted, the type will be autodetected if possible.
+
repeat (Optional): The number of times to repeat this code (on transmit). Default is 1.
+
+
Some manufacturers (e.g. Samsung) require an IR code to be sent a number of times in a row in rapid succession (usually 3). This doesn’t apply to the vast majority of devices, but it can be helpful if needed.
+
Code Types
+
When creating an entry in kira_codes.yaml, a few different kinds of codes can be used.
+
+
kira: This is the native wire protocol used by Kira modules. These can be captured using netcat.
+
pronto: Pronto codes are supported.
+
nec: If the device uses NEC IR codes and the manufacturer has published them, they can be used here.
+
+
NOTE: NEC codes by themselves contain enough information to recognize an IR sequence, but not enough to reconstruct it. Codes of this type are receive-only (usable by sensors but not remotes).
diff --git a/components/light.knx/index.html b/components/light.knx/index.html
index 566ae73b76..c67db52ef8 100644
--- a/components/light.knx/index.html
+++ b/components/light.knx/index.html
@@ -165,9 +165,15 @@ For switching/light actuators that are only controlled by a single group address
server (Optional): Your server address. Only needed if using more than one network interface. Omit if you are unsure.
+
Set state
+
The LIFX bulbs allow a change of color and brightness even when they are turned off. This way you can control the light during the day so its settings are correct when events for turning on are received, for example from motion detectors or external buttons.
+
The normal light.turn_on call cannot be used for this because it always turns the power on. Thus, LIFX has its own service call that allows color changes without affecting the current power state.
+
Service light.lifx_set_state
+
Change the light to a new state.
+
+
+
+
Service data attribute
+
Description
+
+
+
+
+
entity_id
+
String or list of strings that point at entity_ids of lights. Else targets all.
+
+
+
transition
+
Duration (in seconds) for the light to fade to the new state.
+
+
+
power
+
Turn the light on (True) or off (False). Leave out to keep the power as it is.
+
+
+
...
+
Use color_name, brightness etc. from light.turn_on to specify the new state.
+
+
+
Light effects
The LIFX platform supports several light effects. You can start these effects with default options by using the effect attribute of the normal light.turn_on service, for example like this:
The rpi_gpio_pwm platform allows to control multiple lights using pulse-width modulation, for example led strips. It supports one-color, RGB and RGBW LEDs driven by GPIOs of a Raspberry Pi or a PCA9685 controller.
+
For controlling the GPIOs, the platform connects to the pigpio-daemon, which must be running. On Raspbian Jessie 2016-05-10 or newer the pigpio library is already included. On other operating systems it needs to be installed first (see installation instructions).
To enable this platform, add the following lines to your configuration.yaml:
# Example configuration.yaml entrylight:
diff --git a/components/light/index.html b/components/light/index.html
index b83de4ba3f..0e71ef5580 100644
--- a/components/light/index.html
+++ b/components/light/index.html
@@ -118,6 +118,11 @@ The light component supports multiple entries in configuration.yaml
yes
An INT in mireds representing the color temperature you want the light to be.
+
+
kelvin
+
yes
+
Alternatively, you can specify the color temperature in Kelvin.
+
color_name
yes
@@ -128,6 +133,11 @@ The light component supports multiple entries in configuration.yaml
yes
Integer between 0 and 255 for how bright the color should be.
+
+
brightness_pct
+
yes
+
Alternatively, you can specify brightness in percent (a number between 0 and 100).
If supported by your lock, a binary sensor will be created for each user key code you have defined. These key codes will turn on when the code is entered and automatically turn off after a few seconds.
diff --git a/components/logbook/index.html b/components/logbook/index.html
index cdd658121b..e5857181e1 100644
--- a/components/logbook/index.html
+++ b/components/logbook/index.html
@@ -155,6 +155,9 @@ To exclude these entities just add them to the e
Introduction
diff --git a/components/lutron/index.html b/components/lutron/index.html
index 9a8fed71a8..023d135658 100644
--- a/components/lutron/index.html
+++ b/components/lutron/index.html
@@ -118,6 +118,9 @@ It is recommended to assign a static IP address to your Main Repeater. This ensu
Lutron is an American lighting control company. They have several lines of home automation devices that manage light switches/dimmers, occupancy sensors, HVAC controls, etc. The lutron_caseta component in Home Assistant is responsible for communicating with the Lutron SmartBridge for these systems.
-
This component only supports the Caseta line of products. Current only supports Caseta dimmers as Home Assistant lights and caseta wall switches as Home Assistant switches.
-
When configured, the lutron_caseta component will automatically discover dimmers and switches as setup in the Lutron SmartBridge.
+
Lutron is an American lighting control company. They have several lines of home automation devices that manage light switches/dimmers, occupancy sensors, HVAC controls, etc. The lutron_caseta component in Home Assistant is responsible for communicating with the Lutron SmartBridge for these systems. Both ‘pro’ and ‘standard’ models are supported.
+
This component only supports the Caseta line of products. The current supported Caseta devices are:
+
+
Dimmers as Home Assistant lights
+
Wall switches as Home Assistant switches
+
Serena shades as Home Assistant covers
+
+
When configured, the lutron_caseta component will automatically discover the currently support devices as setup in the Lutron SmartBridge.
To use Lutron Caseta devices in your installation, add the following to your configuration.yaml file using the IP of your lutron Smartbridge:
# Example configuration.yaml entrylutron_caseta:
@@ -97,6 +102,9 @@ It is recommended to assign a static IP address to your Lutron SmartBridge. This
turn_off_action (Optional): The desired turn off action. Options are none, quit, hibernate, suspend, reboot, or shutdown. Default none.
enable_websocket (Optional): Enable websocket connections to Kodi via the TCP port. Defaults to true. The websocket connection allows Kodi to push updates to Home Assistant and removes the need for Home Assistant to poll. If websockets don’t work on your installation this can be set to false.
+
timeout (Optional): Set timeout for connections to Kodi. Defaults to 5 seconds.
+
Service kodi_add_to_playlist
+
Add music to the default playlist (i.e. playlistid=0).
+
+
+
+
Service data attribute
+
Optional
+
Description
+
+
+
+
+
entity_id
+
no
+
Name(s) of the Kodi entities where to add the media.
+
+
+
media_type
+
yes
+
Media type identifier. It must be one of SONG or ALBUM.
+
+
+
media_id
+
no
+
Unique Id of the media entry to add (songid or albumid). If not defined, media_name and artist_name are needed to search the Kodi music library.
+
+
+
media_name
+
no
+
Optional media name for filtering media. Can be ‘ALL’ when media_type is ‘ALBUM’ and artist_name is specified, to add all songs from one artist.
+
+
+
artist_name
+
no
+
Optional artist name for filtering media.
+
+
+
+
Service kodi_call_method
+
Call a Kodi JSONRPC API method with optional parameters. Results of the Kodi API call will be redirected in a Home Assistant event: kodi_call_method_result.
+
+
+
+
Service data attribute
+
Optional
+
Description
+
+
+
+
+
entity_id
+
no
+
Name(s) of the Kodi entities where to run the API method.
+
+
+
method
+
yes
+
Name of the Kodi JSONRPC API method to be called.
+
+
+
any other parameter
+
no
+
Optional parameters for the Kodi API call.
+
+
+
+
Event triggering
+
When calling the kodi_call_method service, if the Kodi JSONRPC API returns data, when received by Home Assistant it will fire a kodi_call_method_result event on the event bus with the following event_data:
+
entity_id:"<Kodimedia_playerentity_id>"
+result_ok:<boolean>
+input:<input parameters of the service call>
+result:<data received from the Kodi API>
+
+
+
Kodi services samples
+
Simple script to turn on the TV with the Kodi JSON-CEC Addon
+
script:
+ activate_tv:
+ alias:Turn on TV
+ sequence:
+ -alias:TV on
+ service:media_player.kodi_call_method
+ data:
+ entity_id:media_player.kodi
+ method:Addons.ExecuteAddon
+ addonid:script.json-cec
+ params:
+ command:activate
+
+
+
For a more complex usage of the kodi_call_method service, with event triggering of Kodi API results, you can have a look at this example
+
Service sonos_update_alarm
+
Update an existing sonos alarm.
+
+
+
+
Service data attribute
+
Optional
+
Description
+
+
+
+
+
entity_id
+
no
+
String or list of entity_ids that will have their timers cleared. Must be a coordinator speaker.
+
+
+
alarm_id
+
no
+
Integer that is used in Sonos to refer to your alarm.
+
+
+
time
+
yes
+
Time to set the alarm.
+
+
+
volume
+
yes
+
Float for volume level.
+
+
+
enabled
+
yes
+
Boolean for whether or not to enable this alarm.
+
+
+
include_linked_zones
+
yes
+
Boolean that defines if the alarm also plays on grouped players.
+
+
+
- Screenshot of our new configuration panel.
-
+ 
+
+
+
-After automatic discovery, Home Assistant will ask the user to finish pairing with the gateway.
-
+In this tutorial I will explain how you can activate Tasker tasks from Home Assistant command line switches. We are going to set up a switch that when toggled will make your Android device say either “On” or “Off”.
Sonos support has been added by 
-
- Screenshot of our new configuration panel.
-
- The Christmas tree in action.
-
-
+
+
+