As mentioned in the 0.57 release notes, Home Assistant has launched a translated frontend. With the immediate influx of translations, we’ve made integration with a translation tool a top priority. @c727 took the initiative to evaluate several tools, and we’re happy to announce that Home Assistant will be partnering with Lokalise to manage our translations!
+
+
Lokalise allows us to open up translations for all of our multilingual users willing to contribute. Users can join the project using our public signup link, and start translating right away. We’ve created a translation startup guide with additional details about how to contribute. Instructions are provided there for how to request a new language.
+
+
Now that we have a system in place, expect a lot more of the interface to be translatable soon. We still have some technical hurdles to overcome, but the hardest work is behind us now. The community has already done an outstanding job of providing translations. The future is looking bright!
+
+]]>
+
+
@@ -1981,219 +2002,6 @@ Screenshot of the new customize editor.
Last Wednesday we released Hass.io, an operating system to take care of all the updating hassles that come with running home automation at home and so much more. This is a major milestone for Home Assistant as it is our first step to offering a fully integrated solution using a bring your own hardware approach.
-
-
The launch has been crazy successful. The 20 minute introduction video by BRUHAutomation already has 12.5k views in just 4 days with no less than 150 comments.
-
-
Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.
-
-
Adding the power of voice to integrations
-
-
But enough about Hass.io, let’s not forget about Home Assistant. This release has completely revamped the way how we deal with voice integrations. We turned Home Assistant into a platform to write voice apps, no matter where the processing of the voice happens. This can be done by Alexa, Google Assistant or in the Home Assistant user interface.
-
-
We are super excited about the new functionality and hope that it will trigger a new type of applications and systems to be built on top of Home Assistant. This release includes a shopping list to show the new functionality. As a user you can add any item to the shopping list with your voice and also ask what is on your shopping list.
-
-
# Example configuration.yaml entry
-shopping_list:
-
-
-
-
To make testing these applications easier, we’ve updated the conversation component. The component will now allow sentences to be configured that hook directly into the new voice functionality. Combined with the new interface it will allow for some great interactions! Check out the developer docs for more information.
-
-
-
-
-
-
History improvements
-
-
@OverloadUT has been recently spending a lot of time on optimizing the history database queries. This release includes PR #8632, the first in a list of improvements that he is working on. This PR greatly improves requests for single entities by using an optimized query for this use case.
-
-
The performance change in some of his tests shows this change to be about 300x faster (30 seconds to 0.1 seconds!) (There is no theoretical upper limit due to the issue with multi-entity queries getting worse the longer the current recorder run has been going.)
-
-
Xiaomi integration
-
-
Yes, it has happened! After being in beta for a while, the Xiaomi support is now available to all. @danielhiversen did an amazing job and we now support sensors, switches, lights and covers.
-
-
Velbus integration
-
-
Another awesome integration is that of the Velbus home automation system which has been contributed by @thomasdelaet. It integrates their sensors, covers, fans, lights and switches.
-
-
Manual alarm with MQTT control
-
-
A new version of the manual alarm component is now available with full MQTT control thanks to @colinodell. Using this you can build your own control panel to remotely arm/disarm the alarm. For example, using a Raspberry Pi to create an alarm.
…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.
-
-
-
Breaking Changes
-
-
-
Automations: The state trigger keyword state and the time trigger keyword after were deprecated in 0.46. They have now been removed. Use to and at instead. (@amelchio - #8510) (automation.state docs) (automation.time docs) (breaking change)
-
Wink: the component is no longer supporting the access_token in the config. Use the new OAuth authentication or add your username and password to the config. (@w1ll1am23 - #8208) (wink docs) (breaking change)
-
Alexa/API.AI/Snips.ai/Conversation: configuring responses to intents/sentences has been moved to a new component called intent_script. Conversation now allows configuring sentences to map to intents. (@balloob - #8434) (alexa docs) (intent docs) (intent_script docs)
- (shopping_list docs) (snips docs) (breaking change) (new-platform)
-
-
-
alexa:
-snips:
-apiai:
-
-intent_script:
- LightKitchen:
- speech:
- type:plain
- text:I did the work, yay.
- card:
- type:simple
- title:Lights Card
- content:I have turned on the lights.
- action:
- service:light.turn_on
- data:
- entity_id:light.kitchen
-
-conversation:
- intents:
- LightKitchen:
- -The kitchen is magic
-
Yahoo Weather: no longer allow configuring forecasts but include all instead. (@fanthos - #8626) (weather.yweather docs) (breaking change)
-
The Home Assistant Z-Wave Cover implementation has been updated to support the latest development version of OpenZWave. If you are currently applying a workaround to your OpenZWave installation to support the barrier command class, you’ll need to make sure you update your workaround to the latest development version of OpenZWave. (@firstof9 - #8574) (cover docs) (cover.zwave docs) (breaking change)
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 fcfbcc5907..7d29c61be6 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
@@ -162,6 +162,9 @@ This article will try to explain how they all relate.
diff --git a/blog/2015/02/08/looking-at-the-past/index.html b/blog/2015/02/08/looking-at-the-past/index.html
index eca7b334ae..804bb53962 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -150,6 +150,9 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D
diff --git a/blog/2015/03/08/new-logo/index.html b/blog/2015/03/08/new-logo/index.html
index cf8a374471..3f2556eb54 100644
--- a/blog/2015/03/08/new-logo/index.html
+++ b/blog/2015/03/08/new-logo/index.html
@@ -133,6 +133,9 @@ The old logo, the new detailed logo and the new simple logo.
diff --git a/blog/2015/03/11/release-notes/index.html b/blog/2015/03/11/release-notes/index.html
index 880915cb31..c4886c768c 100644
--- a/blog/2015/03/11/release-notes/index.html
+++ b/blog/2015/03/11/release-notes/index.html
@@ -158,6 +158,9 @@ An initial version of voice control for Home Assistant has landed. The current i
diff --git a/blog/2015/03/22/release-notes/index.html b/blog/2015/03/22/release-notes/index.html
index fc383544e5..475b09c4f9 100644
--- a/blog/2015/03/22/release-notes/index.html
+++ b/blog/2015/03/22/release-notes/index.html
@@ -194,6 +194,9 @@ I (Paulus) have contributed a scene component. A user can create scenes that cap
diff --git a/blog/2015/05/14/release-notes/index.html b/blog/2015/05/14/release-notes/index.html
index 087300ad71..0b9a9eca85 100644
--- a/blog/2015/05/14/release-notes/index.html
+++ b/blog/2015/05/14/release-notes/index.html
@@ -216,6 +216,9 @@ Before diving into the newly supported devices and services, I want to highlight
diff --git a/blog/2015/06/10/release-notes/index.html b/blog/2015/06/10/release-notes/index.html
index 745d1e15e5..6f3805a1c5 100644
--- a/blog/2015/06/10/release-notes/index.html
+++ b/blog/2015/06/10/release-notes/index.html
@@ -262,6 +262,9 @@ This switch platform allows you to control your motion detection setting on your
diff --git a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
index f1b4d1bcd4..61416e30fc 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
@@ -226,6 +226,9 @@ Fabian has added support for Forecast.io to g
diff --git a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
index 577b8d4e9d..edf05d7bfb 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
@@ -209,6 +209,9 @@ Support for Temper temperature sensors has been contributed by
diff --git a/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html b/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
index 9121701027..3dcd2081d2 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
@@ -246,6 +246,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 8eede0562b..92fd1dc8a8 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
@@ -173,6 +173,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 0ccb162f7f..f28113d99b 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
@@ -169,6 +169,9 @@ Automation has gotten a lot of love. It now supports conditions, multiple trigge
diff --git a/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html b/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
index 6ab10e14ed..48158a1518 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
@@ -152,6 +152,9 @@ Map in Home Assistant showing two people and three zones (home, school, work)
diff --git a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
index 069e6272b6..0654809ca1 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
@@ -337,6 +337,9 @@ Home Assistant will keep track of historical values and allow you to integrate i
diff --git a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
index af7b249d02..3e180c3e59 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
@@ -159,6 +159,9 @@ This makes more sense as most people run Home Assistant as a daemon
diff --git a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
index 27a75e3d32..c29bdb2d98 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
@@ -164,6 +164,9 @@ This is where we’ll configure our task, so select the plus icon to select an a
diff --git a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
index 7839792544..1b5c24e756 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
@@ -161,6 +161,9 @@ Example of the new views in the frontend. Learn mor
diff --git a/blog/2016/02/20/community-highlights/index.html b/blog/2016/02/20/community-highlights/index.html
index cb669db55e..0f9f69f328 100644
--- a/blog/2016/02/20/community-highlights/index.html
+++ b/blog/2016/02/20/community-highlights/index.html
@@ -163,6 +163,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 5414f18582..9175cd8a65 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
@@ -166,6 +166,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 69e7ce5a3f..6c821784e3 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
@@ -208,6 +208,9 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
diff --git a/blog/2016/07/06/pocketchip-running-home-assistant/index.html b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
index 0be165d550..79c78f893a 100644
--- a/blog/2016/07/06/pocketchip-running-home-assistant/index.html
+++ b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
@@ -161,6 +161,9 @@ Over a year ago I participated in the
diff --git a/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html b/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
index 14eff14d8f..a5809735cb 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
@@ -171,6 +171,9 @@ One of the graphs created with this tutorial.
diff --git a/blog/2016/07/28/esp8266-and-micropython-part1/index.html b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
index 5a96b6dbea..76b8e128e4 100644
--- a/blog/2016/07/28/esp8266-and-micropython-part1/index.html
+++ b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
@@ -251,6 +251,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 9c3c166606..dda6ad7983 100644
--- a/blog/2016/08/31/esp8266-and-micropython-part2/index.html
+++ b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
@@ -209,6 +209,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 3b07112030..7332cb4028 100644
--- a/blog/2017/01/14/iss-usps-images-packages/index.html
+++ b/blog/2017/01/14/iss-usps-images-packages/index.html
@@ -215,6 +215,9 @@ You have to note:
diff --git a/blog/2017/02/03/babyphone/index.html b/blog/2017/02/03/babyphone/index.html
index 7d4acef437..72eec75f8f 100644
--- a/blog/2017/02/03/babyphone/index.html
+++ b/blog/2017/02/03/babyphone/index.html
@@ -240,6 +240,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 52bf23cc53..1c5e1f8dcf 100644
--- a/blog/2017/02/04/hassbian-toybox/index.html
+++ b/blog/2017/02/04/hassbian-toybox/index.html
@@ -166,6 +166,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 6e149cdc0b..09db5d806c 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
@@ -341,6 +341,9 @@ Screenshot of all the different functionality the IP webcam integration offers.
diff --git a/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html b/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html
index edb2e54353..21a6dab2bc 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
@@ -196,6 +196,9 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
diff --git a/blog/2017/04/22/ikea-tradfri-spotify/index.html b/blog/2017/04/22/ikea-tradfri-spotify/index.html
index cdc25be2c0..867e658530 100644
--- a/blog/2017/04/22/ikea-tradfri-spotify/index.html
+++ b/blog/2017/04/22/ikea-tradfri-spotify/index.html
@@ -341,6 +341,9 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
diff --git a/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html b/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html
index bea32f8e98..6206a0f822 100644
--- a/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html
+++ b/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html
@@ -289,6 +289,9 @@ If you have a security key set in your Open Z-Wave
diff --git a/blog/2017/07/15/release-49/index.html b/blog/2017/07/15/release-49/index.html
index ad6fd2a4b6..33697339e6 100644
--- a/blog/2017/07/15/release-49/index.html
+++ b/blog/2017/07/15/release-49/index.html
@@ -328,6 +328,9 @@ Screenshot of a green dashboard
diff --git a/blog/2017/09/16/hassbian-1.3-a-bit-of-a-stretch/index.html b/blog/2017/09/16/hassbian-1.3-a-bit-of-a-stretch/index.html
index a795ba76d2..77ce3f24de 100644
--- a/blog/2017/09/16/hassbian-1.3-a-bit-of-a-stretch/index.html
+++ b/blog/2017/09/16/hassbian-1.3-a-bit-of-a-stretch/index.html
@@ -139,6 +139,9 @@ Other than that the changes are mostly to our tool
diff --git a/blog/2017/11/04/release-57/index.html b/blog/2017/11/04/release-57/index.html
index a8ad2f453e..343677c162 100644
--- a/blog/2017/11/04/release-57/index.html
+++ b/blog/2017/11/04/release-57/index.html
@@ -372,6 +372,9 @@ The Home Assistant sidebar in 12 different languages.
+
+The Home Assistant sidebar in 12 different languages.
+
+
Translations
+
As mentioned in the 0.57 release notes, Home Assistant has launched a translated frontend. With the immediate influx of translations, we’ve made integration with a translation tool a top priority. @c727 took the initiative to evaluate several tools, and we’re happy to announce that Home Assistant will be partnering with Lokalise to manage our translations!
+
Lokalise allows us to open up translations for all of our multilingual users willing to contribute. Users can join the project using our public signup link, and start translating right away. We’ve created a translation startup guide with additional details about how to contribute. Instructions are provided there for how to request a new language.
+
Now that we have a system in place, expect a lot more of the interface to be translatable soon. We still have some technical hurdles to overcome, but the hardest work is behind us now. The community has already done an outstanding job of providing translations. The future is looking bright!
diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml
index ab878d6cee..2ef787151e 100644
--- a/blog/categories/community/atom.xml
+++ b/blog/categories/community/atom.xml
@@ -4,7 +4,7 @@
- 2017-11-06T15:35:09+00:00
+ 2017-11-06T16:02:30+00:00https://home-assistant.io/
@@ -13,6 +13,28 @@
Octopress
+
+
+
+ 2017-11-06T01:00:00+00:00
+ https://home-assistant.io/blog/2017/11/05/frontend-translations
+
+
+The Home Assistant sidebar in 12 different languages.
+
+
+## Translations
+
+As mentioned in the [0.57 release notes](https://home-assistant.io/blog/2017/11/04/release-57/), Home Assistant has launched a translated frontend. With the immediate influx of translations, we’ve made integration with a translation tool a top priority. [@c727] took the initiative to evaluate several tools, and we’re happy to announce that Home Assistant will be partnering with [Lokalise](https://lokalise.co/) to manage our translations!
+
+Lokalise allows us to open up translations for all of our multilingual users willing to contribute. Users can join the project using our [public signup link](https://lokalise.co/signup/3420425759f6d6d241f598.13594006/all/), and start translating right away. We’ve created a [translation startup guide](https://home-assistant.io/developers/frontend_translation/) with additional details about how to contribute. Instructions are provided there for how to request a new language.
+
+Now that we have a system in place, expect a lot more of the interface to be translatable soon. We still have some technical hurdles to overcome, but the hardest work is behind us now. The community has already done an outstanding job of providing translations. The future is looking bright!
+
+[@c727]: https://github.com/c727
+]]>
+
+
@@ -186,23 +208,6 @@ Just like last year, we'll be hosting a [Home Assistant Open Space](https://us.p
We will also be taken part in the [development sprints](https://us.pycon.org/2017/community/sprints/) from Monday-Wednesday. You only need to bring a laptop. We'll help you get set up with a dev environment and you can be coding on top of Home Assistant in no time. ~~Exact location inside the conference center to be announced.~~ **We are sitting in room A108.**
On a final note, the Home Assistant community is very very active so don't take it personal if we don't remember your name, issue or contribution.
-]]>
-
-
-
-
-
- 2017-05-07T02:00:00+00:00
- https://home-assistant.io/blog/2017/05/07/grazer-linuxtage-2017-talk-python-everywhere
-
-
-
-
-[MicroPython]: https://micropython.org
]]>
diff --git a/blog/categories/community/index.html b/blog/categories/community/index.html
index a4f1f64e72..777967949b 100644
--- a/blog/categories/community/index.html
+++ b/blog/categories/community/index.html
@@ -79,6 +79,27 @@
+
+The Home Assistant sidebar in 12 different languages.
+
+
Translations
+
As mentioned in the 0.57 release notes, Home Assistant has launched a translated frontend. With the immediate influx of translations, we’ve made integration with a translation tool a top priority. @c727 took the initiative to evaluate several tools, and we’re happy to announce that Home Assistant will be partnering with Lokalise to manage our translations!
+
Lokalise allows us to open up translations for all of our multilingual users willing to contribute. Users can join the project using our public signup link, and start translating right away. We’ve created a translation startup guide with additional details about how to contribute. Instructions are provided there for how to request a new language.
+
Now that we have a system in place, expect a lot more of the interface to be translatable soon. We still have some technical hurdles to overcome, but the hardest work is behind us now. The community has already done an outstanding job of providing translations. The future is looking bright!
+
+
+
@@ -473,34 +505,6 @@ The Home Assistant sidebar in 12 different languages.
If you’re on Windows, you’re fine as our minimum version for Windows has been 3.5 for a while now.
Other Debian based systems
If you’re running a Debian based system, follow these instructions to upgrade.
Dale (dale3h) joins Rohan and Dan to talk about Dale’s involvement in the project as a community
- leader and his contributions. Dale and Rohan also cover off the 0.54 release.
It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.
+
This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.
+
Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.
+
On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!
Core: new elevation config option added (@balloob)
+
Sensor: OneWire support extended with support for DS18S20, DS1822, DS1825 and DS28EA00 temperature sensors + support for bus masters which use fuse to mount device tree. (@Ardetus)
HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems (@balloob)
+
+
Breaking changes
+
+
Homematic thermostat configuration has changed and now depends on the new Homematic component.
+
+
Hotfix 0.23.1 - July 2
+
+
Bump PyVera to 0.2.13 to fix traceback and pyvera thread dying related to bug (@rhooper)
+
HTTP - SSL: Check for OP_NO_COMPRESSION support before trying to use it (@AlucardZero)
+
Wink: Downgraded pubnub to work around pycryptodome conflicts (@w1ll1am23)
+
+
FAQ
+
+
elevation: was introduced to the configuration for weather/sunrise data. For existing configurations add the value shown in the warning [homeassistant.config] Incomplete core config. Auto detected elevation: 665 to your configuration.yaml file.
+
+
+
+
@@ -470,35 +538,6 @@ In the past month I was thinking about ways to integrate USB webcams into Home A
Ben from BRUH Automation authors a lot of great video’s about how he is using Home Assistant and how you can get started with it too. The video below will walk you through how to configure Home Assistant. Enjoy!
-
Make sure to subscribe to his YouTube channel for more Home Assistant video’s.
Ben from BRUH Automation authors a lot of great video’s about how he is using Home Assistant and how you can get started with it too. The video below will walk you through how to configure Home Assistant. Enjoy!
+
Make sure to subscribe to his YouTube channel for more Home Assistant video’s.
+
+
+
+
+
+
@@ -466,77 +495,6 @@
Your hub should not be affected when your internet breaks down or the company that sold you your hub goes out of business. It should work locally so that it can continue to work even long after the vendor goes out of business or decides to kill it. Preferably, your hub should also be open so that the community can take over development after the vendor stops caring.
Unless you can afford losing a product here and there, be cautious when buying IoT products that depend on the cloud from companies that are not well established. The chances are high that they go bankrupt or get acquired and closed. This however is easier said than done as Gartner predicts that by 2017, 50 percent of IoT solutions will originate in startups that are less than three years old.
Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: hbMQTT. Just add mqtt: to your config and a broker is launched and connected with Home Assistant. See the documentation for more info.
-
Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).
-
Rock on.
-
-
-
Device Tracker - OwnTracks: Allow entry into passive zones using iBeacons (@pavoni)
Automation: support for old deprecated config has been removed
-
-
-
Tellstick configuration has changed
-
-
-
tellstick:
- signal_repetitions:X
-
-
-
-
Vera configuration has changed
-
-
vera:
- vera_controller_url:http://192.168.1.161:3480/
- # Optional to exclude devices - this is a list of vera device ids
- exclude:[13,14,16,20,23,72,73,74,75,76,77,78,88,89,99]
- # Optional to import switches as lights - this is a list of vera device ids
- lights:[15,17,19,21,22,24,26,43,64,70,87]
-
Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: hbMQTT. Just add mqtt: to your config and a broker is launched and connected with Home Assistant. See the documentation for more info.
+
Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).
+
Rock on.
+
+
+
Device Tracker - OwnTracks: Allow entry into passive zones using iBeacons (@pavoni)
Automation: support for old deprecated config has been removed
+
+
+
Tellstick configuration has changed
+
+
+
tellstick:
+ signal_repetitions:X
+
+
+
+
Vera configuration has changed
+
+
vera:
+ vera_controller_url:http://192.168.1.161:3480/
+ # Optional to exclude devices - this is a list of vera device ids
+ exclude:[13,14,16,20,23,72,73,74,75,76,77,78,88,89,99]
+ # Optional to import switches as lights - this is a list of vera device ids
+ lights:[15,17,19,21,22,24,26,43,64,70,87]
+
+
+
+
+
@@ -543,61 +614,6 @@ Example of the new views in the frontend. Learn mor
First release of 2016 and we are on 🔥! The main repository has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a record number of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘.
First release of 2016 and we are on 🔥! The main repository has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a record number of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘.
After two weeks of hard work I’m proud to announce the release of Home Assistant v0.7.6. For this release the main focus was bugs, test coverage and documentation. And we exceeded expectations on all three fronts. Bugs have been squashed, test coverage increased to 85% and thanks to the hard work by @fabaff and myself the component section on the website has gotten a complete revamp.
After two weeks of hard work I’m proud to announce the release of Home Assistant v0.7.6. For this release the main focus was bugs, test coverage and documentation. And we exceeded expectations on all three fronts. Bugs have been squashed, test coverage increased to 85% and thanks to the hard work by @fabaff and myself the component section on the website has gotten a complete revamp.
A minor bug fix release to fix some issues that have come up since the last release. Please upgrade as soon as possible by running git pull from the Home Assistant directory.
-
This release is a major milestone in our test coverage as we’ve crossed into the 80s! It has to be noted that this covers mainly the core and automation components. Platforms that communicate with IoT devices have been excluded.
-
As we didn’t want to just push out bug fixes, this release includes a few additions:
-
-
Support for modern TP-Link routers like the ArcherC9 line has been contributed by @chrisvis.
-
Improved support for MQTT topic subscriptions has been contributed by @qrtn
-
-
Verisure Support
- Home Assistant support to integrate your Verisure alarms, hygrometers, sensors and thermometers has been contributed by @persandstrom.
A minor bug fix release to fix some issues that have come up since the last release. Please upgrade as soon as possible by running git pull from the Home Assistant directory.
+
This release is a major milestone in our test coverage as we’ve crossed into the 80s! It has to be noted that this covers mainly the core and automation components. Platforms that communicate with IoT devices have been excluded.
+
As we didn’t want to just push out bug fixes, this release includes a few additions:
+
+
Support for modern TP-Link routers like the ArcherC9 line has been contributed by @chrisvis.
+
Improved support for MQTT topic subscriptions has been contributed by @qrtn
+
+
Verisure Support
+ Home Assistant support to integrate your Verisure alarms, hygrometers, sensors and thermometers has been contributed by @persandstrom.
@@ -430,34 +473,6 @@ An initial version of voice control for Home Assistant has landed. The current i
The old logo, the new detailed logo and the new simple logo.
-
Home Assistant is now using YAML for it’s configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.
-
The new file is named configuration.yaml and if it can’t be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.
Home Assistant is now using YAML for it’s configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.
+
The new file is named configuration.yaml and if it can’t be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.
Dale (dale3h) joins Rohan and Dan to talk about Dale’s involvement in the project as a community
+ leader and his contributions. Dale and Rohan also cover off the 0.54 release.
Last Wednesday we released Hass.io, an operating system to take care of all the updating hassles that come with running home automation at home and so much more. This is a major milestone for Home Assistant as it is our first step to offering a fully integrated solution using a bring your own hardware approach.
-
The launch has been crazy successful. The 20 minute introduction video by BRUHAutomation already has 12.5k views in just 4 days with no less than 150 comments.
-
Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.
-
Adding the power of voice to integrations
-
But enough about Hass.io, let’s not forget about Home Assistant. This release has completely revamped the way how we deal with voice integrations. We turned Home Assistant into a platform to write voice apps, no matter where the processing of the voice happens. This can be done by Alexa, Google Assistant or in the Home Assistant user interface.
-
We are super excited about the new functionality and hope that it will trigger a new type of applications and systems to be built on top of Home Assistant. This release includes a shopping list to show the new functionality. As a user you can add any item to the shopping list with your voice and also ask what is on your shopping list.
-
# Example configuration.yaml entry
-shopping_list:
-
-
-
To make testing these applications easier, we’ve updated the conversation component. The component will now allow sentences to be configured that hook directly into the new voice functionality. Combined with the new interface it will allow for some great interactions! Check out the developer docs for more information.
-
-
-
-
History improvements
-
@OverloadUT has been recently spending a lot of time on optimizing the history database queries. This release includes PR #8632, the first in a list of improvements that he is working on. This PR greatly improves requests for single entities by using an optimized query for this use case.
-
The performance change in some of his tests shows this change to be about 300x faster (30 seconds to 0.1 seconds!) (There is no theoretical upper limit due to the issue with multi-entity queries getting worse the longer the current recorder run has been going.)
-
Xiaomi integration
-
Yes, it has happened! After being in beta for a while, the Xiaomi support is now available to all. @danielhiversen did an amazing job and we now support sensors, switches, lights and covers.
-
Velbus integration
-
Another awesome integration is that of the Velbus home automation system which has been contributed by @thomasdelaet. It integrates their sensors, covers, fans, lights and switches.
-
Manual alarm with MQTT control
-
A new version of the manual alarm component is now available with full MQTT control thanks to @colinodell. Using this you can build your own control panel to remotely arm/disarm the alarm. For example, using a Raspberry Pi to create an alarm.
…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.
Last Wednesday we released Hass.io, an operating system to take care of all the updating hassles that come with running home automation at home and so much more. This is a major milestone for Home Assistant as it is our first step to offering a fully integrated solution using a bring your own hardware approach.
+
The launch has been crazy successful. The 20 minute introduction video by BRUHAutomation already has 12.5k views in just 4 days with no less than 150 comments.
+
Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.
+
Adding the power of voice to integrations
+
But enough about Hass.io, let’s not forget about Home Assistant. This release has completely revamped the way how we deal with voice integrations. We turned Home Assistant into a platform to write voice apps, no matter where the processing of the voice happens. This can be done by Alexa, Google Assistant or in the Home Assistant user interface.
+
We are super excited about the new functionality and hope that it will trigger a new type of applications and systems to be built on top of Home Assistant. This release includes a shopping list to show the new functionality. As a user you can add any item to the shopping list with your voice and also ask what is on your shopping list.
+
# Example configuration.yaml entry
+shopping_list:
+
+
+
To make testing these applications easier, we’ve updated the conversation component. The component will now allow sentences to be configured that hook directly into the new voice functionality. Combined with the new interface it will allow for some great interactions! Check out the developer docs for more information.
+
+
+
+
History improvements
+
@OverloadUT has been recently spending a lot of time on optimizing the history database queries. This release includes PR #8632, the first in a list of improvements that he is working on. This PR greatly improves requests for single entities by using an optimized query for this use case.
+
The performance change in some of his tests shows this change to be about 300x faster (30 seconds to 0.1 seconds!) (There is no theoretical upper limit due to the issue with multi-entity queries getting worse the longer the current recorder run has been going.)
+
Xiaomi integration
+
Yes, it has happened! After being in beta for a while, the Xiaomi support is now available to all. @danielhiversen did an amazing job and we now support sensors, switches, lights and covers.
+
Velbus integration
+
Another awesome integration is that of the Velbus home automation system which has been contributed by @thomasdelaet. It integrates their sensors, covers, fans, lights and switches.
+
Manual alarm with MQTT control
+
A new version of the manual alarm component is now available with full MQTT control thanks to @colinodell. Using this you can build your own control panel to remotely arm/disarm the alarm. For example, using a Raspberry Pi to create an alarm.
…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.
ZWave entity_ids have long been a source of frustration in Home Assistant. The first problem we faced was that depending on the order of node discovery, entity_ids could be discovered with different names on each run. To solve this we added the node id as a suffix to the entity_id. This ensured that entity_ids were generated deterministically on each run, but additional suffixes had to be added to handle edge cases where there would otherwise be a conflict. The resulting entity_ids worked, but have been difficult to work with and makes ZWave a strange exception among other Home Assistant components.
-
Thanks to the awesome work of @turbokongen, a growing number of ZWave configuration options are now available from the new ZWave panel in the Home Assistant frontend. Among these new features is support for renaming of ZWave nodes and their underlying values. (These renames are persisted in zwcfg_*.xml) This is important, because these items are combined to form the Home Assistant entity name, which is used to generate the entity_id. Now that these options are available, ZWave users can rename nodes and values, influencing the entity_ids that are generated by Home Assistant.
-
Now that users are able to control these names, we will be making changes to how the entity_ids are generated for ZWave entities. The ZWave entity_ids are going to switch back to using the standard entity_id generation from Home Assistant core, based on the entity names. Moving forward, if there is a conflict when generating entity_ids, a suffix will be added, and it will be the responsibility of the user to rename their nodes and values to avoid the conflict. This is the same as any other platform in Home Assistant where two devices are discovered with the same name.
-
With the release of 0.47, this feature will be opt-in. Setting new_entity_ids: true under zwave: in your configuration.yaml will enable the new generation. After 0.48 this feature will become opt-out. From 0.48 onward, unless you’ve declared new_entity_ids: false you will switch to the new entity_id generation. At an undecided point in the future, the old entity_id generation will be removed completely.
-
I’m sure all ZWave users understand that the current entity_ids aren’t easy to use. They’re annoying to type in configuration.yaml, and break if a node needs to be re-included to the network. We know that breaking changes are painful, and so we’re doing what we can to roll this change out as smoothly as possible. The end result should be a dramatic simplification of most ZWave configurations. We hope that this change will ultimately make ZWave much easier to work with, and bring ZWave configuration just a little closer to the rest of the Home Assistant platforms.
ZWave entity_ids have long been a source of frustration in Home Assistant. The first problem we faced was that depending on the order of node discovery, entity_ids could be discovered with different names on each run. To solve this we added the node id as a suffix to the entity_id. This ensured that entity_ids were generated deterministically on each run, but additional suffixes had to be added to handle edge cases where there would otherwise be a conflict. The resulting entity_ids worked, but have been difficult to work with and makes ZWave a strange exception among other Home Assistant components.
+
Thanks to the awesome work of @turbokongen, a growing number of ZWave configuration options are now available from the new ZWave panel in the Home Assistant frontend. Among these new features is support for renaming of ZWave nodes and their underlying values. (These renames are persisted in zwcfg_*.xml) This is important, because these items are combined to form the Home Assistant entity name, which is used to generate the entity_id. Now that these options are available, ZWave users can rename nodes and values, influencing the entity_ids that are generated by Home Assistant.
+
Now that users are able to control these names, we will be making changes to how the entity_ids are generated for ZWave entities. The ZWave entity_ids are going to switch back to using the standard entity_id generation from Home Assistant core, based on the entity names. Moving forward, if there is a conflict when generating entity_ids, a suffix will be added, and it will be the responsibility of the user to rename their nodes and values to avoid the conflict. This is the same as any other platform in Home Assistant where two devices are discovered with the same name.
+
With the release of 0.47, this feature will be opt-in. Setting new_entity_ids: true under zwave: in your configuration.yaml will enable the new generation. After 0.48 this feature will become opt-out. From 0.48 onward, unless you’ve declared new_entity_ids: false you will switch to the new entity_id generation. At an undecided point in the future, the old entity_id generation will be removed completely.
+
I’m sure all ZWave users understand that the current entity_ids aren’t easy to use. They’re annoying to type in configuration.yaml, and break if a node needs to be re-included to the network. We know that breaking changes are painful, and so we’re doing what we can to roll this change out as smoothly as possible. The end result should be a dramatic simplification of most ZWave configurations. We hope that this change will ultimately make ZWave much easier to work with, and bring ZWave configuration just a little closer to the rest of the Home Assistant platforms.
+
+
+
@@ -454,70 +483,6 @@ If you have a security key set in your Open Z-Wave Podcast.__init__ about Python and Home Assistant. Just realized that we never shared this on the blog, oops. Here it is, enjoy!
-
Saw the announcement yesterday for HASSbian 1.21 and got super excited?
-
Today we’ll flash the latest HASSbian to a Raspbery Pi Zero W.
-With an added bonus that besides for an USB cable for power, there’s no need for any cables!
-
What you’ll need:
-
-
a Raspberry Pi Zero W (an amazing tiny computer with built-in wifi)
-
a microSD card
-
some source of USB power
-
Wifi
-
a desktop or laptop
-
-
Let’s get to it!
-
First, download the HASSbian 1.21 image from here.
-
Unzip it.
-
Flash it to the microSD card. If you need a flash tool, try Etcher
-
When the flashing finishes, remove it and plug it back in. You should see a drive called “boot”.
-
Right in there, not in any folders, create a file called wpa_supplicant.conf.
-
The contents of the configuration file should be something like this:
-(You may have to adjust for your configuration, hints here )
Next stick your SD card into the Raspberry Pi Zero W, and plug it in.
-
After about a minute, use your SSH client to connect to HASSbian (or hassbian.local from a Mac), with the username pi. The default password is raspberry.
-
It’s a good idea to change the password. To do so, use the passwd command.
-
Next, type the following two commands into the SSH console:
Saw the announcement yesterday for HASSbian 1.21 and got super excited?
+
Today we’ll flash the latest HASSbian to a Raspbery Pi Zero W.
+With an added bonus that besides for an USB cable for power, there’s no need for any cables!
+
What you’ll need:
+
+
a Raspberry Pi Zero W (an amazing tiny computer with built-in wifi)
+
a microSD card
+
some source of USB power
+
Wifi
+
a desktop or laptop
+
+
Let’s get to it!
+
First, download the HASSbian 1.21 image from here.
+
Unzip it.
+
Flash it to the microSD card. If you need a flash tool, try Etcher
+
When the flashing finishes, remove it and plug it back in. You should see a drive called “boot”.
+
Right in there, not in any folders, create a file called wpa_supplicant.conf.
+
The contents of the configuration file should be something like this:
+(You may have to adjust for your configuration, hints here )
Next stick your SD card into the Raspberry Pi Zero W, and plug it in.
+
After about a minute, use your SSH client to connect to HASSbian (or hassbian.local from a Mac), with the username pi. The default password is raspberry.
+
It’s a good idea to change the password. To do so, use the passwd command.
+
Next, type the following two commands into the SSH console:
Welcome to 0.41. There was a lot going on in the last two weeks. Not only from the code side but also from the social one of Home Assistant. Paulus did an interview with OpenSourceCraft, Fabian did a workshop at the Chemnitzer Linux Tage, and we are now an award-winning Open source project (I will cover that in a separate blog post).
-
Plex
-
@JesseWebDotCom made massive changes to the Plex media player platform. From better metadata support over new configuration options to improved controls and non-controllable clients.
-
Component overview
-
The Components overview is now powered by search/filtering feature. This will make it faster to get the component/platform you are looking for more quickly. Thanks again, @bdurrer for this.
-
Changelog
-
The new format of the changelog which was introduced with 0.40 will provide a link to the related pull request. We are not covering everything in our release notes but we think that this addition will make it easier to find details about the change.
The frontend is now using Shadow DOM and this could break your custom panels (#228).
-
-
If you need help…
-
…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 0.41. There was a lot going on in the last two weeks. Not only from the code side but also from the social one of Home Assistant. Paulus did an interview with OpenSourceCraft, Fabian did a workshop at the Chemnitzer Linux Tage, and we are now an award-winning Open source project (I will cover that in a separate blog post).
+
Plex
+
@JesseWebDotCom made massive changes to the Plex media player platform. From better metadata support over new configuration options to improved controls and non-controllable clients.
+
Component overview
+
The Components overview is now powered by search/filtering feature. This will make it faster to get the component/platform you are looking for more quickly. Thanks again, @bdurrer for this.
+
Changelog
+
The new format of the changelog which was introduced with 0.40 will provide a link to the related pull request. We are not covering everything in our release notes but we think that this addition will make it easier to find details about the change.
The frontend is now using Shadow DOM and this could break your custom panels (#228).
+
+
If you need help…
+
…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.
No stats, no numbers, and alike this time. Ok, just one number: 0.37. We are back on track with our bi-weekly release cycle. Beside some organizational changes is this release shipping again cool features and new integrations. Please keep an eye on the “Breaking changes” section because there are also massive improvements for some platforms and components.
-
Governance
-
As announced, the new Governance requires for developers to sign the CLA. Code of Conduct, Contributor License Agreement, and proper Licensing will to protect all involved parties in the Home Assistant eco-system from users and community members to contributors.
-
Face recognition using the Microsoft Face API
-
@pvizeli has been on a roll with the image processing integrations. This time it’s the Microsoft Face API. This means that now it will be possible to train the API with the people you want to recognize and send images from your camera to the API as another source of automation.
-
Want to play a personalized tune when someone enters the house? It is now possible 😎
-
Improved camera security
-
After a security audit by Stephen O’Conner, he found that our source for randomly generated access tokens for camera feeds were reasonable predictable and could be brute force attacked in 2.5 weeks. A fix has been included in this release that uses the system provided random number generator for maximum randomness and rotates the keys every 10 minutes to reduce the window in which a brute force attack can happen.
-
Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged.
-
New customization options
-
@Andrey-git has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain.
-
Major Wink and HDMI CEC improvements
-
@w1ll1am23 did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your configuration.yaml file, no client_id and client_secret are needed, and token which was generated with the generator located in the Wink documentation.
-
The new Wink support will cause renaming of all the binary sensors and will also create new sensors for devices that weren’t previously detected or supported in the older version.
-
Thanks to @konikvranik the HDMI CEC integration got a huge update with a lot of improvements. This update should make it easier to work with HDMI CEC and give you more control.
A major breaking change in the emulated_hue component means that unless you set type: alexa before starting up the newer Home Assistant version you will lose all devices that Alexa has discovered and will need to re-add them as well as create new groups.
-
The platform of the ISS integration was change to binary_sensor. Please check the platform documentation.
-
The Roku media uses now a new format for the entity IDs.
Due to massive improvements of the Wink integration, the names of your binary sensors will change and new devices can show up.
-
The MySensors component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you.
-
The Sonos service sonos_group_players was removed. Use now sonos_join for this function.
-
TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. HASH_LANG_PLATFORM.xxx -> HASH_LANG_OPTIONS_PLATFORM.xxx, replace OPTIONS with - on exiting platforms.
-
-
If you need help…
-
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you 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.
No stats, no numbers, and alike this time. Ok, just one number: 0.37. We are back on track with our bi-weekly release cycle. Beside some organizational changes is this release shipping again cool features and new integrations. Please keep an eye on the “Breaking changes” section because there are also massive improvements for some platforms and components.
+
Governance
+
As announced, the new Governance requires for developers to sign the CLA. Code of Conduct, Contributor License Agreement, and proper Licensing will to protect all involved parties in the Home Assistant eco-system from users and community members to contributors.
+
Face recognition using the Microsoft Face API
+
@pvizeli has been on a roll with the image processing integrations. This time it’s the Microsoft Face API. This means that now it will be possible to train the API with the people you want to recognize and send images from your camera to the API as another source of automation.
+
Want to play a personalized tune when someone enters the house? It is now possible 😎
+
Improved camera security
+
After a security audit by Stephen O’Conner, he found that our source for randomly generated access tokens for camera feeds were reasonable predictable and could be brute force attacked in 2.5 weeks. A fix has been included in this release that uses the system provided random number generator for maximum randomness and rotates the keys every 10 minutes to reduce the window in which a brute force attack can happen.
+
Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged.
+
New customization options
+
@Andrey-git has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain.
+
Major Wink and HDMI CEC improvements
+
@w1ll1am23 did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your configuration.yaml file, no client_id and client_secret are needed, and token which was generated with the generator located in the Wink documentation.
+
The new Wink support will cause renaming of all the binary sensors and will also create new sensors for devices that weren’t previously detected or supported in the older version.
+
Thanks to @konikvranik the HDMI CEC integration got a huge update with a lot of improvements. This update should make it easier to work with HDMI CEC and give you more control.
A major breaking change in the emulated_hue component means that unless you set type: alexa before starting up the newer Home Assistant version you will lose all devices that Alexa has discovered and will need to re-add them as well as create new groups.
+
The platform of the ISS integration was change to binary_sensor. Please check the platform documentation.
+
The Roku media uses now a new format for the entity IDs.
Due to massive improvements of the Wink integration, the names of your binary sensors will change and new devices can show up.
+
The MySensors component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you.
+
The Sonos service sonos_group_players was removed. Use now sonos_join for this function.
+
TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. HASH_LANG_PLATFORM.xxx -> HASH_LANG_OPTIONS_PLATFORM.xxx, replace OPTIONS with - on exiting platforms.
+
+
If you need help…
+
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you 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.
On Saturday, we released Home Assistant 0.31 which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.
On Saturday, we released Home Assistant 0.31 which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.
I have been working on a new subsystem to complement Home Assistant’s Automation and Scripting components. AppDaemon is a python daemon that consumes events from Home Assistant and feeds them to snippets of python code called “Apps”. An App is a Python class that is instantiated possibly multiple times from AppDaemon and registers callbacks for various system events. It is also able to inspect and set state and call services. The API provides a rich environment suited to home automation tasks that can also leverage all the power of Python.
I have been working on a new subsystem to complement Home Assistant’s Automation and Scripting components. AppDaemon is a python daemon that consumes events from Home Assistant and feeds them to snippets of python code called “Apps”. An App is a Python class that is instantiated possibly multiple times from AppDaemon and registers callbacks for various system events. It is also able to inspect and set state and call services. The API provides a rich environment suited to home automation tasks that can also leverage all the power of Python.
It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.
-
This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.
-
Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.
-
On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!
Core: new elevation config option added (@balloob)
-
Sensor: OneWire support extended with support for DS18S20, DS1822, DS1825 and DS28EA00 temperature sensors + support for bus masters which use fuse to mount device tree. (@Ardetus)
HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems (@balloob)
-
-
Breaking changes
-
-
Homematic thermostat configuration has changed and now depends on the new Homematic component.
-
-
Hotfix 0.23.1 - July 2
-
-
Bump PyVera to 0.2.13 to fix traceback and pyvera thread dying related to bug (@rhooper)
-
HTTP - SSL: Check for OP_NO_COMPRESSION support before trying to use it (@AlucardZero)
-
Wink: Downgraded pubnub to work around pycryptodome conflicts (@w1ll1am23)
-
-
FAQ
-
-
elevation: was introduced to the configuration for weather/sunrise data. For existing configurations add the value shown in the warning [homeassistant.config] Incomplete core config. Auto detected elevation: 665 to your configuration.yaml file.
-
-
-
-
← OlderNewer →
diff --git a/index.html b/index.html
index c0f09cda51..61ec0dab27 100644
--- a/index.html
+++ b/index.html
@@ -115,6 +115,10 @@ Home Assistant is an open-source home automation platform running on Python 3. T