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 d00cc66609..10d02c9372 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 0b2171e629..e1d29c5e84 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 ba25c1af48..f6202fa861 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 ac020a6b46..04f8ff71d4 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 93fe4b3c9f..6d394bfee0 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 6bc5084ba1..17d0dd3ce9 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 f3fab68b8a..88b9deca8d 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 bb06fe42ab..ecb2e21487 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 c9cecbcefe..86eea5e809 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 3b75b6877a..4727c2a7c5 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 b98ca5a8ff..bcb52385fb 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 547819c216..560f848eef 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 f0877057ef..7b354736e8 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 e8eb15ccb7..c2639475fa 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 d8d7614b05..0683f5a8d7 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 b2034a1a40..a46a36562b 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 d226bb008f..3e765d5714 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 dbb3fda406..90ee090155 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 541ccc3712..fe436e75f1 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 9e7e2aac23..4693c88b10 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 f26c02e9a0..73e1bb6a01 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 be15b244e8..d4b15f306a 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 33e9ddcd82..d5d2954aef 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 9c1c3f656f..7e9c4aed3a 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 bbcc8a7338..166ee7309d 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 f028d580f6..2cc10adbac 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 cf1404b3be..0edf19a918 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 b8f4491f2f..4521510b0c 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 1f930c81a9..5b0c1696f1 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
This release brings some great new integrations. The biggest one is the native ZigBee integration by Russell Cloran. This will allow Home Assistant to natively control Philips Hue lights without the need for a hub! (IKEA Tradfri lights not yet due to implementing a different profile)
Another great new addition is OpenCV by Teagan Glenn. So now you’ll be able to unlock all the cool stuff from OpenCV right in Home Assistant. And if OpenCV is not your style, you can try out the new DLib integration added by Pascal Vizeli in this release.
This release also includes a new component to dynamically generate RSS feeds based on a template. This means that any RSS widget on your phone, tablet or computer can now be used to show Home Assistant data!
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.
@@ -281,6 +281,9 @@ If you have a security key set in your Open Z-Wave
In this release a ton of new stuff! And who doesn’t like new stuff? This release we’re passing the 700 integrations for Home Assistant. As of today we’re 1369 days old, which means that roughly every two days a new integration gets added!
+
Python Scripts
+
The biggest change is a new type of script component: Python scripts. This new component will allow you to write scripts to manipulate Home Assistant: call services, set states and fire events. Each Python script is made available as a service. Head over to the docs to see how to get started.
+
Updater
+
The updater has received a new opt-in option to let us know which components you use. This will allow us to focus development efforts on the components that are popular.
+
updater:
+ include_used_components:true
+
+
+
And as a reminder. We will never share gathered data in a manner that can be used to identify anyone. We do plan on making aggregate data public soon. This will include total number of users and which hardware/software platform people use to run Home Assistant.
+
Z-Wave
+
Z-Wave is also getting a big update in this release. The confusing entity_ids will be on their way out. There is a zwave blog post that gives more detail, but the upgrade steps will be as follows:
+
+
Run Home Assistant as normal and the old IDs will still be used.
+
The new entity IDs will be shown in the more-info dialog for each entity. Check to make sure none of them will have conflicts once the new names are applied.
+
Rename entities using the ui card as described in the blog post to avoid conflicts. Restart Home Assistant to observe the changes.
+
Update all places mentioning IDs (groups, automation, customization, etc.) in configuration.yaml.
+
Add new_entity_ids: true to your zwave config.
+
Restart Home Assistant to run with new IDs.
+
The old entity IDs will be available in the more info dialog to trace down any remaining errors.
…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.
LIFX: add multiple modes to pulse effect. The lifx_effect_breathe call has been deprecated. Use lifx_effect_pulse with the new mode: breathe attribute instead. (@amelchio - #8016) (light.lifx docs) (breaking change)
+
Use standard entity_ids for zwave entities. This also introduces a small API breakage, where EVENT_SCENE_ACTIVATED and EVENT_NODE_EVENT will no longer supply an object_id. They will now be tied to the node entity_id. (@armills - #7786) (zwave docs) (light.zwave docs) (breaking change)
+
Fix attribute entities. Home Assistant will no longer filter out entities that are ‘falsey’. So you might see more entity attributes show up. (@pvizeli - #8066) (breaking change)
Fix EntityComponent handle entities without a name (@balloob - #8065)
+
Update pyunifi component to use APIError passed from pyunifi 2.13. Better accommodate login failures with wrapper in pyunifi 2.13. (@finish06 - #7899) (device_tracker.unifi docs)
In this release a ton of new stuff! And who doesn’t like new stuff? This release we’re passing the 700 integrations for Home Assistant. As of today we’re 1369 days old, which means that roughly every two days a new integration gets added!
+
Python Scripts
+
The biggest change is a new type of script component: Python scripts. This new component will allow you to write scripts to manipulate Home Assistant: call services, set states and fire events. Each Python script is made available as a service. Head over to the docs to see how to get started.
+
Updater
+
The updater has received a new opt-in option to let us know which components you use. This will allow us to focus development efforts on the components that are popular.
+
updater:
+ include_used_components:true
+
+
+
And as a reminder. We will never share gathered data in a manner that can be used to identify anyone. We do plan on making aggregate data public soon. This will include total number of users and which hardware/software platform people use to run Home Assistant.
+
Z-Wave
+
Z-Wave is also getting a big update in this release. The confusing entity_ids will be on their way out. There is a zwave blog post that gives more detail, but the upgrade steps will be as follows:
+
+
Run Home Assistant as normal and the old IDs will still be used.
+
The new entity IDs will be shown in the more-info dialog for each entity. Check to make sure none of them will have conflicts once the new names are applied.
+
Rename entities using the ui card as described in the blog post to avoid conflicts. Restart Home Assistant to observe the changes.
+
Update all places mentioning IDs (groups, automation, customization, etc.) in configuration.yaml.
+
Add new_entity_ids: true to your zwave config.
+
Restart Home Assistant to run with new IDs.
+
The old entity IDs will be available in the more info dialog to trace down any remaining errors.
…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.
It’s time for 0.46! This release does not have too many new integrations, instead it focussed on bug fixes.
New platforms
@@ -236,7 +305,7 @@
-
+
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.
@@ -405,7 +474,7 @@ If you have a security key set in your Open Z-Wave
-
+
This release brings some great new integrations. The biggest one is the native ZigBee integration by Russell Cloran. This will allow Home Assistant to natively control Philips Hue lights without the need for a hub! (IKEA Tradfri lights not yet due to implementing a different profile)
Another great new addition is OpenCV by Teagan Glenn. So now you’ll be able to unlock all the cool stuff from OpenCV right in Home Assistant. And if OpenCV is not your style, you can try out the new DLib integration added by Pascal Vizeli in this release.
This release also includes a new component to dynamically generate RSS feeds based on a template. This means that any RSS widget on your phone, tablet or computer can now be used to show Home Assistant data!
@@ -449,35 +518,6 @@ If you have a security key set in your Open Z-Wave
-
-
Earlier this year I was interviewed by Tobias Macey from Podcast.__init__ about Python and Home Assistant. Just realized that we never shared this on the blog, oops. Here it is, enjoy!
People often ask me about my vision for Home Assistant. Before I can describe where I want to go with Home Assistant, I should first talk about how home automation would look in my ideal world. This will be the aim of this post. I’m not going to focus on protocols, networks or specific hubs. That’s all implementation details. Instead, this post will focus on what is most important: the interaction between the users and their home.
+
You should not have to adapt to technology.
+
When people start using home automation, they always experience home control first: being able to control devices in new ways using a phone or computer. They believe the future is now and their app will be their remote for their lives. They only focus on what they are getting, not on what they are losing. You install some light bulbs and all of a sudden you are no longer able to use the light switches. You’ll arrive at home at night and have to pull out your phone, open the app, let it connect and finally you’ll be able to turn on the light. All while turning the light on could have been a switch away.
+
Yes, you can solve this with presence detection. What if your phone runs out of battery? You’ll have to resort to the switch again.
+
If you find that using your new home devices is cumbersome, the promise of home automation technology has failed you. Your lights should work with both a switch (or button) at the entrance of your room and via presence detection. Honestly, there are hardly any valid use cases for being able to control lights from your phone except for showing off.
We have all been hard at work to get this latest release ready. One of the big highlights in this release is the introduction of an extended iconset to be used in the frontend (credits to @happyleavesaoc for idea and prototype). To get started with customizing, pick any icon from MaterialDesignIcons.com, prefix the name with mdi: and stick it into your customize section in configuration.yaml:
We have all been hard at work to get this latest release ready. One of the big highlights in this release is the introduction of an extended iconset to be used in the frontend (credits to @happyleavesaoc for idea and prototype). To get started with customizing, pick any icon from MaterialDesignIcons.com, prefix the name with mdi: and stick it into your customize section in configuration.yaml:
This is a guest post by Home Assistant user and contributor Nolan Gilley.
-
In our house, laundry has been a struggle for quite some time. Our washer and dryer both lack a buzzer which leads to forgotten laundry, and stinky mess that needs to be rewashed. I decided to create a solution by monitoring the washer and dryer myself with some cheap electronics.
-
As an avid user of Home Assistant, I decided it would be the perfect application to manage the UI and notification system. Now all I needed was a way to monitor the washer and dryer. I tried using sound sensors but found them unreliable. I ended up opting for an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect if the doors are open or closed. I connected the accelerometers and reed switches to a Moteino, an arduino clone with an RF transceiver. The Moteino can perform the logic to figure out which state the appliances are in and wirelessly communicate that data with another Moteino that is connected via serial to my Raspberry Pi. The Raspberry Pi reads the serial data and repeats it over MQTT for Home Assistant to use. This is great because I don’t have to run Home Assistant on the Raspberry Pi. I can run it on a faster machine and point the MQTT component to my Raspberry Pi.
-
After taking some sample data from the accelerometers while each appliance was in operation, I decided to plot the data to help determine the proper thresholds of when the devices were running or off. I had to do this in order to get precise ranges so the dryer sensor wouldn’t get tripped by the washer or vice versa. In the plot below you can see the acceleration in the x direction for the accelerometer connected to the washing machine. It’s easy to see when the washing machine is in operation here. I used the same technique for the dryer’s accelerometer.
This is a guest post by Home Assistant user and contributor Nolan Gilley.
+
In our house, laundry has been a struggle for quite some time. Our washer and dryer both lack a buzzer which leads to forgotten laundry, and stinky mess that needs to be rewashed. I decided to create a solution by monitoring the washer and dryer myself with some cheap electronics.
+
As an avid user of Home Assistant, I decided it would be the perfect application to manage the UI and notification system. Now all I needed was a way to monitor the washer and dryer. I tried using sound sensors but found them unreliable. I ended up opting for an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect if the doors are open or closed. I connected the accelerometers and reed switches to a Moteino, an arduino clone with an RF transceiver. The Moteino can perform the logic to figure out which state the appliances are in and wirelessly communicate that data with another Moteino that is connected via serial to my Raspberry Pi. The Raspberry Pi reads the serial data and repeats it over MQTT for Home Assistant to use. This is great because I don’t have to run Home Assistant on the Raspberry Pi. I can run it on a faster machine and point the MQTT component to my Raspberry Pi.
+
After taking some sample data from the accelerometers while each appliance was in operation, I decided to plot the data to help determine the proper thresholds of when the devices were running or off. I had to do this in order to get precise ranges so the dryer sensor wouldn’t get tripped by the washer or vice versa. In the plot below you can see the acceleration in the x direction for the accelerometer connected to the washing machine. It’s easy to see when the washing machine is in operation here. I used the same technique for the dryer’s accelerometer.
It is well known that you are either a good programmer or a good designer. It’s rare you’ll meet someone that is both. That’s why it wasn’t surprising to anyone that the logo that I made was mediocre — at best. Luckily, Jeremy Geltman has come to the rescue and contributed a brand new logo for Home Assistant.
-
The new logo follows Googles material design spec. It uses the blue color that Home Assistant uses in the interface and it comes in two versions: a high detailed version (for homescreen icon etc) and a simple version (for favicon etc).
-
-
-The old logo, the new detailed logo and the new simple logo.
-
It is well known that you are either a good programmer or a good designer. It’s rare you’ll meet someone that is both. That’s why it wasn’t surprising to anyone that the logo that I made was mediocre — at best. Luckily, Jeremy Geltman has come to the rescue and contributed a brand new logo for Home Assistant.
+
The new logo follows Googles material design spec. It uses the blue color that Home Assistant uses in the interface and it comes in two versions: a high detailed version (for homescreen icon etc) and a simple version (for favicon etc).
+
+
+The old logo, the new detailed logo and the new simple logo.
+
Earlier this year I was interviewed by Tobias Macey from Podcast.__init__ about Python and Home Assistant. Just realized that we never shared this on the blog, oops. Here it is, enjoy!
+
+
+
+
@@ -486,33 +515,6 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
The idea of creating HTTP to MQTT bridge appeared when I was trying to integrate Google Assistant with my Home Assistant after watching BRUH Automation video. Right now there is no MQTT service available in IFTTT. Existing integration solution uses Maker Webhooks which requires that your Home Assistant instance is publically accessible, which I think brings some security concerns or simply not always possible to set up.
-
The HTTP to MQTT bridge should fill that gap. The idea is to receive messages using HTTP requests and transfer them to your MQTT broker, which can be contacted by Home Assistant. The HTTP to MQTT bridge is written using Node.js with Express for the server part and MQTT.js for the client.
The idea of creating HTTP to MQTT bridge appeared when I was trying to integrate Google Assistant with my Home Assistant after watching BRUH Automation video. Right now there is no MQTT service available in IFTTT. Existing integration solution uses Maker Webhooks which requires that your Home Assistant instance is publically accessible, which I think brings some security concerns or simply not always possible to set up.
+
The HTTP to MQTT bridge should fill that gap. The idea is to receive messages using HTTP requests and transfer them to your MQTT broker, which can be contacted by Home Assistant. The HTTP to MQTT bridge is written using Node.js with Express for the server part and MQTT.js for the client.
One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.
-
Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.
One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.
+
Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.
Another two weeks have passed and we are pleased to present Home Assistant 0.32.
-
Hacktoberfest
-
The Hacktoberfest is over now. Home Assistant made the 2nd and the 3rd place out of almost 30’000 participating repositories with a total of 528 pull requests closed - that’s an average of 17 pull requests a day! Thanks to all the contributors but also to the team of reviewers. This wouldn’t been possible without you 👏 .
-
Improved error reporting
-
This release has improved the reporting when a config validation error occurs. Thanks to @kellerza you will now get a persistent notification added to your UI when this happens.
-
Asynchronous
-
This release contains the first asynchronous sensor and camera platforms. @pvizeli and @fabaff ported most of the “internal” sensors to async programming. We hope that you will enjoy the new speed.
-
@balloob and @pvizeli worked a lot on the improvement of the core itself.
-
Weather component
-
For a long time we have had a bunch of weather sensors but it’s getting better: There is now a Weather component. Sorry, not much more to tell right now. The plans are to create a weather UI element and to improve the initial implementation.
We’ve added a warning to 0.32 to catch platforms accidentally slowing down Home Assistant. Our aim is to fix these quickly when reported, so here is 0.32.1 with all reported platforms fixed.
-
-
Fix Sonos doing I/O inside the event loop (@pvizeli)
-
Fix Radiotherm doing I/O inside the event loop (@balloob)
-
Fix camera MJPEG streams when using HTTP 1.0 (@balloob)
-
-
Release 0.32.2 - November 7
-
-
Move Honeywell I/O out of the event loop (@balloob)
-
Use sequential updates for non-async entities to prevent race conditions (@pvizeli)
-
Fix setting temperature in Celsius on Radiotherm CT50 thermostats (@andyat)
Our website has now an additional category called “Ecosystem”. This will become the place where tools, apps, and other helper for the Home Assistant ecosystem can store their documentation or guides.
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
Another two weeks have passed and we are pleased to present Home Assistant 0.32.
+
Hacktoberfest
+
The Hacktoberfest is over now. Home Assistant made the 2nd and the 3rd place out of almost 30’000 participating repositories with a total of 528 pull requests closed - that’s an average of 17 pull requests a day! Thanks to all the contributors but also to the team of reviewers. This wouldn’t been possible without you 👏 .
+
Improved error reporting
+
This release has improved the reporting when a config validation error occurs. Thanks to @kellerza you will now get a persistent notification added to your UI when this happens.
+
Asynchronous
+
This release contains the first asynchronous sensor and camera platforms. @pvizeli and @fabaff ported most of the “internal” sensors to async programming. We hope that you will enjoy the new speed.
+
@balloob and @pvizeli worked a lot on the improvement of the core itself.
+
Weather component
+
For a long time we have had a bunch of weather sensors but it’s getting better: There is now a Weather component. Sorry, not much more to tell right now. The plans are to create a weather UI element and to improve the initial implementation.
We’ve added a warning to 0.32 to catch platforms accidentally slowing down Home Assistant. Our aim is to fix these quickly when reported, so here is 0.32.1 with all reported platforms fixed.
+
+
Fix Sonos doing I/O inside the event loop (@pvizeli)
+
Fix Radiotherm doing I/O inside the event loop (@balloob)
+
Fix camera MJPEG streams when using HTTP 1.0 (@balloob)
+
+
Release 0.32.2 - November 7
+
+
Move Honeywell I/O out of the event loop (@balloob)
+
Use sequential updates for non-async entities to prevent race conditions (@pvizeli)
+
Fix setting temperature in Celsius on Radiotherm CT50 thermostats (@andyat)
Our website has now an additional category called “Ecosystem”. This will become the place where tools, apps, and other helper for the Home Assistant ecosystem can store their documentation or guides.
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
Thanks to Anton Kireyeu we are able to present another awesome Jupyter notebook. I guess that you all know the graph which Github is using to visualize your commits per day over a time-line. It’s a so-called heatmap. If there are more commits, it’s getting hotter. The latest notebook is capable to do the same thing for your devices. To be more precise, for the hours your devices are home.
Thanks to Anton Kireyeu we are able to present another awesome Jupyter notebook. I guess that you all know the graph which Github is using to visualize your commits per day over a time-line. It’s a so-called heatmap. If there are more commits, it’s getting hotter. The latest notebook is capable to do the same thing for your devices. To be more precise, for the hours your devices are home.
+
+
+Heatmap
+
+
+
+
@@ -479,33 +509,6 @@ One of the graphs created with this tutorial.
-Over a year ago I participated in the kickstarter campaign for “CHIP - The World’s First Nine Dollar Computer” by Next Thing Co.. I went for the PocketCHIP because of the idea. Display, built-in storage (thus no need for SD cards), battery-powered, and a keyboard are pretty nice features. Last week a package arrives…
+Over a year ago I participated in the kickstarter campaign for “CHIP - The World’s First Nine Dollar Computer” by Next Thing Co.. I went for the PocketCHIP because of the idea. Display, built-in storage (thus no need for SD cards), battery-powered, and a keyboard are pretty nice features. Last week a package arrives…
I’ve been planning to write this post for a while now as we get questions like this a lot: “Why does Home Assistant use Polymer? Why not React, Redux and what not?”
-
It’s understandable, Polymer is quite the underdog in the world of web frameworks. A corporate backer does not guarantee popularity or an active community and this shows in the number of projects using Polymer.
-
Still, we use Polymer and it’s awesome. To explain why, I’ll be referencing the React workflow quite a bit, as they do a lot of things right, and show how it is done in Polymer.
-
Polymer gives us components for the web, just like React, but based on web standards: web components, CSS variables. These standards don’t have wide browser support yet but it’s being implemented by every major browser: It’s the future. For now they are being polyfilled and that works just fine but in the future the Home Assistant web app will be able to run native in the browsers == fast.
I’ve been planning to write this post for a while now as we get questions like this a lot: “Why does Home Assistant use Polymer? Why not React, Redux and what not?”
+
It’s understandable, Polymer is quite the underdog in the world of web frameworks. A corporate backer does not guarantee popularity or an active community and this shows in the number of projects using Polymer.
+
Still, we use Polymer and it’s awesome. To explain why, I’ll be referencing the React workflow quite a bit, as they do a lot of things right, and show how it is done in Polymer.
+
Polymer gives us components for the web, just like React, but based on web standards: web components, CSS variables. These standards don’t have wide browser support yet but it’s being implemented by every major browser: It’s the future. For now they are being polyfilled and that works just fine but in the future the Home Assistant web app will be able to run native in the browsers == fast.
Today the news spread that Google will be shutting down the Revolv hubs. And shutting down here doesn’t mean they stop selling or supporting them - no, they are sending an update to each hub to turn your perfectly fine home automation hub into a useless piece of plastic. The fact that this seemed like a good idea by Google astonishes me. If anything, they should have gone the same route as ninjasphere: open it all up and let people decide on the fate of their own hub.
The cloud should be treated as an extension to your smart home instead of running it.
-
-
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.
Today the news spread that Google will be shutting down the Revolv hubs. And shutting down here doesn’t mean they stop selling or supporting them - no, they are sending an update to each hub to turn your perfectly fine home automation hub into a useless piece of plastic. The fact that this seemed like a good idea by Google astonishes me. If anything, they should have gone the same route as ninjasphere: open it all up and let people decide on the fate of their own hub.
The cloud should be treated as an extension to your smart home instead of running it.
+
+
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.
+
+
+
@@ -576,36 +607,6 @@ Example of the new views in the frontend. Learn mor
People often ask me about my vision for Home Assistant. Before I can describe where I want to go with Home Assistant, I should first talk about how home automation would look in my ideal world. This will be the aim of this post. I’m not going to focus on protocols, networks or specific hubs. That’s all implementation details. Instead, this post will focus on what is most important: the interaction between the users and their home.
-
You should not have to adapt to technology.
-
When people start using home automation, they always experience home control first: being able to control devices in new ways using a phone or computer. They believe the future is now and their app will be their remote for their lives. They only focus on what they are getting, not on what they are losing. You install some light bulbs and all of a sudden you are no longer able to use the light switches. You’ll arrive at home at night and have to pull out your phone, open the app, let it connect and finally you’ll be able to turn on the light. All while turning the light on could have been a switch away.
-
Yes, you can solve this with presence detection. What if your phone runs out of battery? You’ll have to resort to the switch again.
-
If you find that using your new home devices is cumbersome, the promise of home automation technology has failed you. Your lights should work with both a switch (or button) at the entrance of your room and via presence detection. Honestly, there are hardly any valid use cases for being able to control lights from your phone except for showing off.
diff --git a/components/alarm_control_panel.wink/index.html b/components/alarm_control_panel.wink/index.html
index 9c61ea1563..4c2c1275b4 100644
--- a/components/alarm_control_panel.wink/index.html
+++ b/components/alarm_control_panel.wink/index.html
@@ -160,6 +160,9 @@ The above devices are confimed to work, but others may work as well.
diff --git a/components/axis/index.html b/components/axis/index.html
index 60de1a0bce..7da06c9232 100644
--- a/components/axis/index.html
+++ b/components/axis/index.html
@@ -193,6 +193,9 @@ Any specific levels for triggers needs to be configured on the device.
diff --git a/components/binary_sensor.arest/index.html b/components/binary_sensor.arest/index.html
index 53b8514067..f252e02c5e 100644
--- a/components/binary_sensor.arest/index.html
+++ b/components/binary_sensor.arest/index.html
@@ -161,6 +161,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 1769147e74..36b7280c70 100644
--- a/components/binary_sensor.blink/index.html
+++ b/components/binary_sensor.blink/index.html
@@ -132,6 +132,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 1cf88ad29b..577950e690 100644
--- a/components/binary_sensor.ffmpeg_motion/index.html
+++ b/components/binary_sensor.ffmpeg_motion/index.html
@@ -151,6 +151,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 a3ac7e671e..57dd3535c6 100644
--- a/components/binary_sensor.ffmpeg_noise/index.html
+++ b/components/binary_sensor.ffmpeg_noise/index.html
@@ -142,6 +142,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 40a9118bf1..46283a87c4 100644
--- a/components/binary_sensor.http/index.html
+++ b/components/binary_sensor.http/index.html
@@ -177,6 +177,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
diff --git a/components/binary_sensor.iss/index.html b/components/binary_sensor.iss/index.html
index 2a96216ed6..e17484e256 100644
--- a/components/binary_sensor.iss/index.html
+++ b/components/binary_sensor.iss/index.html
@@ -140,6 +140,9 @@ If you set show_on_mapshow_on_mapNest component configured to u
diff --git a/components/binary_sensor.octoprint/index.html b/components/binary_sensor.octoprint/index.html
index 8813afd79e..74314f294f 100644
--- a/components/binary_sensor.octoprint/index.html
+++ b/components/binary_sensor.octoprint/index.html
@@ -151,6 +151,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 f4fbe30c4b..409165d7bf 100644
--- a/components/binary_sensor.pilight/index.html
+++ b/components/binary_sensor.pilight/index.html
@@ -154,6 +154,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 9d290a5308..8c7d8543df 100644
--- a/components/binary_sensor.ping/index.html
+++ b/components/binary_sensor.ping/index.html
@@ -147,6 +147,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 242e1066e5..7a08428595 100644
--- a/components/binary_sensor.wink/index.html
+++ b/components/binary_sensor.wink/index.html
@@ -172,6 +172,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 a681912ee0..3e04de6664 100644
--- a/components/binary_sensor.workday/index.html
+++ b/components/binary_sensor.workday/index.html
@@ -152,6 +152,9 @@ If you use the sensor for Canada (CA) wit
diff --git a/components/camera.blink/index.html b/components/camera.blink/index.html
index 45fafd8416..05ad5f7003 100644
--- a/components/camera.blink/index.html
+++ b/components/camera.blink/index.html
@@ -153,6 +153,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 1dcf211879..4bdee35d2c 100644
--- a/components/camera.foscam/index.html
+++ b/components/camera.foscam/index.html
@@ -156,6 +156,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 339dd91fb1..9f891be941 100644
--- a/components/camera.local_file/index.html
+++ b/components/camera.local_file/index.html
@@ -153,6 +153,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 6153a462ba..7e71ea6238 100644
--- a/components/camera.mjpeg/index.html
+++ b/components/camera.mjpeg/index.html
@@ -156,6 +156,9 @@ There is a Nest component configured to u
diff --git a/components/camera.synology/index.html b/components/camera.synology/index.html
index 98fe6cf346..bfd8307987 100644
--- a/components/camera.synology/index.html
+++ b/components/camera.synology/index.html
@@ -170,6 +170,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 a604204ceb..f14ce9be1f 100644
--- a/components/camera.zoneminder/index.html
+++ b/components/camera.zoneminder/index.html
@@ -160,6 +160,9 @@ You must have the ZoneMinder component con
diff --git a/components/climate.honeywell/index.html b/components/climate.honeywell/index.html
index 3e9ebe5da1..cfd15ab2a2 100644
--- a/components/climate.honeywell/index.html
+++ b/components/climate.honeywell/index.html
@@ -116,6 +116,9 @@ Scan interval is expressed in seconds. Omitting scan_interval may result in too-
diff --git a/components/climate.nest/index.html b/components/climate.nest/index.html
index 88ba4c6b86..f21182d40c 100644
--- a/components/climate.nest/index.html
+++ b/components/climate.nest/index.html
@@ -115,6 +115,9 @@ You must have the Nest component configured to u
diff --git a/components/climate.proliphix/index.html b/components/climate.proliphix/index.html
index 789b655288..197c9f1cfd 100644
--- a/components/climate.proliphix/index.html
+++ b/components/climate.proliphix/index.html
@@ -115,6 +115,9 @@ of OID values. A complete collection of the API is available in this
IoT class: Cloud Polling
diff --git a/components/cover.mqtt/index.html b/components/cover.mqtt/index.html
index be97d077a0..f0fbe2dc8c 100644
--- a/components/cover.mqtt/index.html
+++ b/components/cover.mqtt/index.html
@@ -94,6 +94,8 @@ state from state_topic. If these messages
qos (Optional): The maximum QoS level of the state topic. Default is 0. Will also be used when publishing messages.
retain (Optional): If the published message should have the retain flag on or not. Default is false.
value_template (Optional): Defines a template to extract a value from the payload.
+
set_position_topic (Optional): The MQTT topic to publish position commands to.
+
set_position_template (Optional): Defines a template to define the position to be sent to the set_position_topic topic. Incoming position value is available for use in the template ``. If no template is defined, the numeric position (0-100) will be written directly to the topic.
tilt_command_topic (Optional): The MQTT topic to publish commands to control the cover tilt.
tilt_status_topic (Optional): The MQTT topic subscribed to receive tilt status update values.
tilt_min (Optional): The minimum tilt value. Default is 0
diff --git a/components/discovery/index.html b/components/discovery/index.html
index d0cf401f92..40d0c81602 100644
--- a/components/discovery/index.html
+++ b/components/discovery/index.html
@@ -172,7 +172,7 @@ If you see Not initializing discovery because co
HTTP
language (Required): Dyson account language country code. Known working codes: FR, NL, UK, AU. But others codes should work.
+
devices (Optional): List of devices
-
file_path (Required): The path to the HAARS or LBP classification file (xml).
-
name (Optional): The classification name, the default is Face.
-
min_size (Optional): The minimum size for detection as a tuple (width, height), the default is (30, 30).
-
color (Optional): The color, as a tuple (Blue, Green, Red) to draw the rectangle when linked to a dispatcher camera, the default is (255, 255, 0).
-
scale (Optional): The scale to perform when processing, this is a float value that must be greater than or equal to 1.0, default is 1.1.
-
neighbors (Optional): The minimum number of neighbors required for a match, default is 4. The higher this number, the more picky the matching will be; lower the number, the more false positives you may experience.
+
device_id (Required): Device ID. Available in the mobiles applications (Settings page)
+
device_ip (Required): Device IP address
-
Once OpenCV is configured, it will create an image_processing entity for each classification group/camera entity combination as well as a camera so you can see what Home Assistant sees.
-
The attributes on the image_processing entity will be:
devices list is optional but you’ll have to provide them if discovery is not working (warnings in the logs and the devices are not available in Home Assistant web interface).
+To find devices IP address, you can use your router or nmap: