The source code of our updater AWS Lambda function is now available here.
-]]> -How are you? Having a good day? We sure are. If you aren’t having a good day, this might cheer you up…
- -Every other weekend around here gets a little hectic leading to a big sigh of relief as we release a new version of Home Assistant to the world. And this time is no different. Our developer community has once again built us a beautiful new release with lots of new features and improvements. We hope you like it.
- -One last thing before we get going though, I should warn you… @balloob got a bit lazy this week and let me (@robbiet480) step up to the plate again to write the blog post and do the release. I guess I didn’t do such a bad job in 0.27. You’ll never know what surprises I have in store. Now that i’ve got all that stuff out of the way, let’s get started…
- -Sadly, no big amazing stats to update you with this time, but we did recently pass 7,000 commits! This release featured submissions from 45 contributors. Hopefully with the new updater component we will be able to give you some really good stats in the 0.32 blog post.
- -
October means Hacktoberfest time and our community has really come through with some excellent improvements and additions. As of this writing, we have 194 merged and 41 open pull requests to the home-assistant repository and 209 merged/28 open pull requests submitted to the home-assistant.github.io repository. If you want to get in on the fun check out our Hacktoberfest blog post or the Hacktoberfest website. You get an awesome t-shirt for free if you have 4 pull requests merged in the month of October! We even have tasks that a non-developer can easily accomplish with a tiny bit of work. Better hurry up though, only 9 days left and most of the easy tasks are gone!
- -This release includes an update to our updater component. The responsibility of the updater component is to check if a new version is available and notify the user if this is the case.
- -It used to be that this component would check with PyPi (the Python package manager) to see if a new update was available. This had a couple of problems:
- -So to work around these problems, we decided to start hosting the version check service ourselves. Since we had to get some infrastructure spun up anyway, we figured we would take it a step further. Which leads me to this bit of the update (the most important part):
- -Remember how I mentioned that up there in the title that there is some serious business in this release? Well, we also added some basic analytics to the updater component which get sent to the server and stored so that we get a better idea of our user base.
- -Each Home Assistant instance running the updater component will generate a unique ID (based on UUIDv4) that will be used for the updater to be able to differentiate between instances. This UUID will be stored in your config directory in a file called .uuid.
There are two ways to opt-out. The first way is by using the new opt_out option for the updater. This way the updater will continue to check for updates, but no information about your system will be shared with us.
updater:
- reporting: no
-You can also disable the updater component entirely by removing updater: from your configuration.yaml although we would not suggest you do this as you would miss any critical updates.
Finally, you can also reset your unique identifier by deleting the .uuid file and restarting Home Assistant.
Here is what my production Home Assistant instance looks like from the server side:
- -| Name | -Description | -Example | -
|---|---|---|
arch |
- CPU Architecture | -x86_64 |
-
distribution |
- Linux Distribution name (only Linux) | -Ubuntu |
-
docker |
- True if running inside Docker | -false |
-
os_name |
- Operating system name | -Darwin |
-
os_version |
- Operating system version | -10.12 |
-
python_version |
- Python version | -3.5.2 |
-
timezone |
- Timezone | -America/Los_Angeles |
-
user_agent |
- User agent used to submit analytics | -python-requests/2.11.1 |
-
uuid |
- Unique identifier | -10321ee6094d4a2ebb5ed55c675d5f5e |
-
version |
- Home Assistant version | -0.31.0 |
-
virtualenv |
- True if running inside virtualenv | -true |
-
In addition to the above collected data, the server will also use your IP address to do a geographic IP address lookup to determine the city that you are from. To be extremely, extremely clear about this bit: The Home Assistant updater does not: store your IP address in a database and also does not submit the location information from your configuration.yaml.
- 
- Geo-lookup on my IP resolves to Oakland with latitude/longitude pointing at the geographical center of the city.
-
The server also adds two timestamps to the data: the original date your instance UUID was first seen and the timestamp of the last time we have seen your instance. This gives us the following extra data:
- -| Name | -Description | -Example | -
|---|---|---|
first_seen_datetime |
- First time instance ID was submitted | -2016-10-22T19:56:03.542Z |
-
geo_city |
- GeoIP determined city | -Oakland |
-
geo_country_code |
- GeoIP determined country code | -US |
-
geo_country_name |
- GeoIP determined country name | -United States |
-
geo_latitude |
- GeoIP determined latitude (of the city) | -37.8047 |
-
geo_longitude |
- GeoIP determined longitude (of the city) | --122.2124 |
-
geo_metro_code |
- GeoIP determined metro code | -807 |
-
geo_region_code |
- GeoIP determined region code | -CA |
-
geo_region_name |
- GeoIP determined region name | -California |
-
geo_time_zone |
- GeoIP determined time zone | -America/Los_Angeles |
-
geo_zip_code |
- GeoIP determined zip code | -94602 |
-
last_seen_datetime |
- Most recent time instance ID was submitted | -2016-10-22T19:56:03.542Z |
-
This data is held in the highest security. The update system runs in a secured Amazon Web Services account owned by me (@robbiet480). I personally have 5 years of experience with complex AWS deployments and have an extensive security background. I have audited the entire system and made sure to take every step to protect the data, including limiting who has access (just @balloob and myself). While not directly personally identifiable we absolutely understand some users hesistance to giving this information out. Please understand that we are only collecting this information to better understand our user base to provide better long term support and feature development then is currently possible.
- -We currently have no plans to publicly expose any of this information. If we did do such a thing in the future we would of course notify you in advance. It must also be stated that we will never sell or allow the use of this information for non-Home Assistant purposes.
- -We thank you for understanding why we are collecting this data and hope that you leave the feature enabled but fully understand if you feel uncomfortable with this.
- -This section was updated on October 24 to be more clear about geo-lookups being on the city level. See original version.
- -Now, back to the fun stuff…
- -Home Assistant got a crazy idea recently that it couldn’t do enough already and wanted to challenge itself even more. I really don’t understand how it came up with this kooky idea, but it now thinks that its newest hobby should be a minor career in journalism.
- -0.31 adds support for the brand spanking new Alexa Flash Briefing API, allowing you to get updates from Home Assistant anytime you ask Alexa to read your flash briefing. What’s the use case you ask? Well, now when I wake up in the morning and get my flash briefing, Home Assistant adds this to the end of it for me:
- --- -Drive time with traffic is 35 minutes. There is an UberPOOL that will cost $11.52, estimated to be 2 minutes away, for a total of 37 minutes. BART is currently estimated to take 29 minutes. You should take BART, as it is estimated to be faster by 8 minutes.
-
Now I know how to best get to my real job (no, Home Assistant is not my real job, it does seem like it sometimes though) every morning. Obviously not the best home automation example, but I think you get the idea. I could see this being used to tell you any major events that happened in your home overnight or reading you your hyperlocal weather report. Thanks to the audio support you could even replace all of the default Alexa Flash Briefing sources with your own news feeds. Home Assistant supports both text and audio content as well as displaying data in the Alexa app. I also want to point out that unlike the existing Skill integration, the Flash Briefing API does not require HTTPS (but you should still be using HTTPS if possible). For more information, check out the new docs.
- -
- 
- You stay classy, San Diego. (It’s funny, because balloob lives in San Diego))
-
A rather nasty Z-Wave issue was discovered recently by @lukas-hetzenecker. There was a somewhat large chance that if you had multiple of the same model Z-Wave device they may both try to use the same entity IDs. To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs.
- -What this means for all you Z-Wave users is that you will need to update your configurations to reflect the change. I personally have quite a few (17) Z-Wave devices and went through the process this week. Here’s what I had to do:
- -zwave.customize sectionemulated_hue with Alexa and emulated_hue uses the entity ID as a unique identifier I also had to remove all Z-Wave devices from Alexa and re-add them.Your todo list may be a little different from mine, I just wanted to outline the steps I took to give you an idea of what you need to think about. It’s not a very hard process, especially when using global find and replace in Sublime Text but did take me about 20 minutes to complete.
- -This is super annoying, I know, especially since we had said in 0.12 that Z-Wave IDs should hopefully never change again, but we are now forced to eat those words. I will state again that Z-Wave IDs shouldn’t change in the future but obviously we see how that went. To sum up on this section… sorry but it had to happen.
- -approved_ips from string to CIDR validation (@mweinelt)known_devices.yaml reading and writing tweaks and fixes (@kellerza)fail filter added to templates to raise on UndefinedError (@jaharkes)…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 for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
- -– Robbie
- ]]>--open-ui and
--open-ui and
Recent Posts
+ -
+ OpenSourceCraft interviews our founder Paulus Schoutsen
+
-
0.40.2 and broken dependencies
@@ -244,9 +247,6 @@ We change the platform name for binary sensor in 0.38 from
Home Assistant t-shirts have arrived!
- -
- Workshop at CLT 2017
-
diff --git a/blog/2017/02/04/hassbian-toybox/index.html b/blog/2017/02/04/hassbian-toybox/index.html
index ba22af0f77..b6cc12cfea 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
Recent Posts
+ -
+ OpenSourceCraft interviews our founder Paulus Schoutsen
+
-
0.40.2 and broken dependencies
@@ -170,9 +173,6 @@ On the close horizon from @Landrash th
-
Home Assistant t-shirts have arrived!
- -
- Workshop at CLT 2017
-
diff --git a/blog/2017/02/11/alert-appletv-mqtt-yeelight/index.html b/blog/2017/02/11/alert-appletv-mqtt-yeelight/index.html
index 783f91994a..8af4c72374 100644
--- a/blog/2017/02/11/alert-appletv-mqtt-yeelight/index.html
+++ b/blog/2017/02/11/alert-appletv-mqtt-yeelight/index.html
@@ -245,6 +245,9 @@
Recent Posts
diff --git a/blog/2017/02/14/clt-workshop/index.html b/blog/2017/02/14/clt-workshop/index.html
index 2f971bd258..40cd4236ac 100644
--- a/blog/2017/02/14/clt-workshop/index.html
+++ b/blog/2017/02/14/clt-workshop/index.html
@@ -128,6 +128,9 @@
Recent Posts
+ -
+ OpenSourceCraft interviews our founder Paulus Schoutsen
+
-
0.40.2 and broken dependencies
diff --git a/blog/2017/02/22/home-assistant-tshirts-have-arrived/index.html b/blog/2017/02/22/home-assistant-tshirts-have-arrived/index.html
index b18057d9ea..fd55ae9c80 100644
--- a/blog/2017/02/22/home-assistant-tshirts-have-arrived/index.html
+++ b/blog/2017/02/22/home-assistant-tshirts-have-arrived/index.html
@@ -162,6 +162,9 @@
Recent Posts
diff --git a/blog/2017/02/25/config-panel-and-state-restoration/index.html b/blog/2017/02/25/config-panel-and-state-restoration/index.html
index 09c16edcbc..80a81c8047 100644
--- a/blog/2017/02/25/config-panel-and-state-restoration/index.html
+++ b/blog/2017/02/25/config-panel-and-state-restoration/index.html
@@ -300,6 +300,9 @@
Recent Posts
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 ff15245eda..377678789a 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.
Recent Posts
+ -
+ OpenSourceCraft interviews our founder Paulus Schoutsen
+
-
0.40.2 and broken dependencies
@@ -342,9 +345,6 @@ Screenshot of all the different functionality the IP webcam integration offers.
-
Home Assistant t-shirts have arrived!
- -
- Workshop at CLT 2017
-
diff --git a/blog/2017/03/22/broken-dependencies/index.html b/blog/2017/03/22/broken-dependencies/index.html
index ab27715e02..a0dc9cce59 100644
--- a/blog/2017/03/22/broken-dependencies/index.html
+++ b/blog/2017/03/22/broken-dependencies/index.html
@@ -130,6 +130,9 @@
Recent Posts
diff --git a/blog/2017/03/23/opensourcecraft-interview-with-founder-paulus-schoutsen/index.html b/blog/2017/03/23/opensourcecraft-interview-with-founder-paulus-schoutsen/index.html
new file mode 100644
index 0000000000..85c0cd5291
--- /dev/null
+++ b/blog/2017/03/23/opensourcecraft-interview-with-founder-paulus-schoutsen/index.html
@@ -0,0 +1,183 @@
+
+
+
+
+
+
+
+
+ OpenSourceCraft interviews our founder Paulus Schoutsen - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ OpenSourceCraft interviews our founder Paulus Schoutsen
+
+
+ Last month Gregg Pollack from OpenSourceCraft visited me in San Diego to talk about Home Assistant. We talked about the community and how all these awesome people make Home Assistant possible. The main interview is embedded below but make sure to check out the full article including extra video material.
+
+
+
+
+
+ Comments
+
+
+
+
+
+
+
+
+
+
+
diff --git a/blog/archives/index.html b/blog/archives/index.html
index 37a4fd42a3..104942f8e0 100644
--- a/blog/archives/index.html
+++ b/blog/archives/index.html
@@ -2338,6 +2338,27 @@
+
+
+
+
+
+
+
+
@@ -2378,6 +2399,9 @@
Recent Posts
+ -
+ OpenSourceCraft interviews our founder Paulus Schoutsen
+
-
0.40.2 and broken dependencies
@@ -2390,9 +2414,6 @@
-
Home Assistant t-shirts have arrived!
- -
- Workshop at CLT 2017
-
diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml
index dfae2539f7..b210ee4404 100644
--- a/blog/categories/community/atom.xml
+++ b/blog/categories/community/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Community | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Octopress
+
+ <![CDATA[OpenSourceCraft interviews our founder Paulus Schoutsen]]>
+
+ 2017-03-23T08:04:05+00:00
+ https://home-assistant.io/blog/2017/03/23/opensourcecraft-interview-with-founder-paulus-schoutsen
+
+
+
+
+[OpenSourceCraft]: http://codepop.com/open-sourcecraft
+[article]: http://codepop.com/open-sourcecraft/episodes/paulus-schoutsen/
+]]>
+
+
<![CDATA[Workshop at CLT 2017]]>
@@ -126,43 +142,6 @@ We're taking a well deserved break and we will be back again in 2017 with more a
[TravisCI]: https://Travis-ci.org
[CloudFlare]: https://CloudFlare.com
[Discourse]: https://Discourse.com
-]]>
-
-
-
- <![CDATA[Participating in Hacktoberfest]]>
-
- 2016-10-02T00:04:05+00:00
- https://home-assistant.io/blog/2016/10/02/hacktoberfest
-
diff --git a/blog/categories/community/index.html b/blog/categories/community/index.html
index 34e88103fc..7ac783aca5 100644
--- a/blog/categories/community/index.html
+++ b/blog/categories/community/index.html
@@ -71,6 +71,27 @@
2017
+
+
+
+
+
+
+
+
diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml
index 368e50a685..cb9f301680 100644
--- a/blog/categories/device-tracking/atom.xml
+++ b/blog/categories/device-tracking/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Device-Tracking | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml
index 65cb4eb2a0..5b6406821b 100644
--- a/blog/categories/esp8266/atom.xml
+++ b/blog/categories/esp8266/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: ESP8266 | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml
index 7d735edc16..211ada26be 100644
--- a/blog/categories/how-to/atom.xml
+++ b/blog/categories/how-to/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: How-To | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml
index 79a6fbe203..9c198f1344 100644
--- a/blog/categories/ibeacons/atom.xml
+++ b/blog/categories/ibeacons/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: iBeacons | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml
index 38e9f9c3b0..75a03c664a 100644
--- a/blog/categories/internet-of-things/atom.xml
+++ b/blog/categories/internet-of-things/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Internet-of-Things | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml
index 5fec2df329..c8d5c0fab5 100644
--- a/blog/categories/iot-data/atom.xml
+++ b/blog/categories/iot-data/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: IoT-Data | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/merchandise/atom.xml b/blog/categories/merchandise/atom.xml
index 2f214d76a4..cf502f2c1a 100644
--- a/blog/categories/merchandise/atom.xml
+++ b/blog/categories/merchandise/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Merchandise | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml
index 5b457ecf08..4976371afe 100644
--- a/blog/categories/micropython/atom.xml
+++ b/blog/categories/micropython/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Micropython | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml
index bb2ee7d108..35863cf3ea 100644
--- a/blog/categories/mqtt/atom.xml
+++ b/blog/categories/mqtt/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: MQTT | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml
index 75beb198d8..26f127dfa2 100644
--- a/blog/categories/organisation/atom.xml
+++ b/blog/categories/organisation/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Organisation | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml
index afa52ba669..b488ddae51 100644
--- a/blog/categories/owntracks/atom.xml
+++ b/blog/categories/owntracks/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: OwnTracks | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml
index 0883b4a680..a230867a10 100644
--- a/blog/categories/presence-detection/atom.xml
+++ b/blog/categories/presence-detection/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Presence-Detection | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/public-service-announcement/atom.xml b/blog/categories/public-service-announcement/atom.xml
index 07bc082537..8e03b80fde 100644
--- a/blog/categories/public-service-announcement/atom.xml
+++ b/blog/categories/public-service-announcement/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Public-Service-Announcement | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index 214bfc0d12..13dc065229 100644
--- a/blog/categories/release-notes/atom.xml
+++ b/blog/categories/release-notes/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Release-Notes | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
+ -
+ OpenSourceCraft interviews our founder Paulus Schoutsen
+
-
0.40.2 and broken dependencies
@@ -1298,9 +1301,6 @@
-
Home Assistant t-shirts have arrived!
- -
- Workshop at CLT 2017
-
diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml
index d82982bc3e..9b640d430a 100644
--- a/blog/categories/survey/atom.xml
+++ b/blog/categories/survey/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Survey | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml
index c01c71748e..46b42af839 100644
--- a/blog/categories/talks/atom.xml
+++ b/blog/categories/talks/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Talks | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml
index 38637ac8b1..76ce4562d9 100644
--- a/blog/categories/technology/atom.xml
+++ b/blog/categories/technology/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Technology | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml
index 60e3582acf..a26a2eb598 100644
--- a/blog/categories/user-stories/atom.xml
+++ b/blog/categories/user-stories/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: User-Stories | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml
index 7e491f4bb3..b13498ae66 100644
--- a/blog/categories/video/atom.xml
+++ b/blog/categories/video/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Video | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml
index cd24500edb..8960c13433 100644
--- a/blog/categories/website/atom.xml
+++ b/blog/categories/website/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Website | Home Assistant]]>
- 2017-03-23T15:40:45+00:00
+ 2017-03-23T15:49:36+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/index.html b/blog/index.html
index 3022ebd8a7..a79fa1e0e6 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -59,6 +59,34 @@
+
+
+
+ OpenSourceCraft interviews our founder Paulus Schoutsen
+
+
+
+
+ Last month Gregg Pollack from OpenSourceCraft visited me in San Diego to talk about Home Assistant. We talked about the community and how all these awesome people make Home Assistant possible. The main interview is embedded below but make sure to check out the full article including extra video material.
+
+
+
+
+
+
@@ -754,37 +782,6 @@ On the close horizon from @Landrash th
-
-
-
- Home Assistant Governance [updated]
-
-
-
-
- UPDATE JAN 28, 2017
-After feedback from the community we have updated the CLA and the license that Home Assistant is distributed under. For the CLA, instead of enforcing requirements on the grants and code, we now require contributions to be licensed under the Apache 2.0 license. Special thanks to Matthew Garrett for his feedback and advice.
-Starting with release 0.37, Home Assistant will re-license the current code under the Apache 2.0 license. This is the license that will be used moving forward for all projects under our organization.
-
-The Home Assistant project and community has seen enormous growth in the last three years. Many volunteers work tirelessly everyday to give you all the awesomeness that you see today. Much more work is involved than many people realize. Beyond simply coding Home Assistant, volunteers continually maintain related projects, update documentation, post examples, author blog posts, and moderate the forums and chat. This is something that we want to keep safe and functional, even as we grow.
-Starting today we are announcing a few initiatives to help protect our users, contributors and community members.
- Read on →
-
-
-
diff --git a/blog/posts/10/index.html b/blog/posts/10/index.html
index 9fdb0b1666..d820dd4990 100644
--- a/blog/posts/10/index.html
+++ b/blog/posts/10/index.html
@@ -59,6 +59,45 @@
+
+
+
+ MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported
+
+
+
+
+ It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to @balloob. If you’re a developer, make sure you read up on the deprecation notices. @fabaff did another great round of documentating all the various components.
+MQTT Support
+
The big new addition in this release is the support for the MQTT protocol by @fabaff with some help from @balloob. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (see the example) and also support for the automation component has been added. For more information, see the MQTT component page.
+# Example configuration.yaml entry
+mqtt:
+ broker: IP_ADDRESS_BROKER
+ # All the other options are optional:
+ port: 1883
+ keepalive: 60
+ qos: 0
+ username: your_username
+ password: your_secret_password
+
+
+ Read on →
+
+
+
@@ -414,34 +453,6 @@ The old logo, the new detailed logo and the new simple logo.
-
-
-
- Streaming updates
-
-
-
-
- Home Assistant has learned a new trick to get the latest information from the server: streaming updates. No longer will the frontend poll every 30 seconds for updates but instead it will keep a connection open and get the latest changes pushed as soon as they happen.
-A new toggle has been added ot the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.
-
- Read on →
-
-
-
← Older
Newer →
diff --git a/blog/posts/11/index.html b/blog/posts/11/index.html
index ddb294ca57..09a8e566e7 100644
--- a/blog/posts/11/index.html
+++ b/blog/posts/11/index.html
@@ -59,6 +59,34 @@
+
+
+
+ Streaming updates
+
+
+
+
+ Home Assistant has learned a new trick to get the latest information from the server: streaming updates. No longer will the frontend poll every 30 seconds for updates but instead it will keep a connection open and get the latest changes pushed as soon as they happen.
+A new toggle has been added ot the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.
+
+ Read on →
+
+
+
diff --git a/blog/posts/2/index.html b/blog/posts/2/index.html
index 827b59ea0d..d2c085063a 100644
--- a/blog/posts/2/index.html
+++ b/blog/posts/2/index.html
@@ -59,6 +59,37 @@
+
+
+
+ Home Assistant Governance [updated]
+
+
+
+
+ UPDATE JAN 28, 2017
+After feedback from the community we have updated the CLA and the license that Home Assistant is distributed under. For the CLA, instead of enforcing requirements on the grants and code, we now require contributions to be licensed under the Apache 2.0 license. Special thanks to Matthew Garrett for his feedback and advice.
+Starting with release 0.37, Home Assistant will re-license the current code under the Apache 2.0 license. This is the license that will be used moving forward for all projects under our organization.
+
+The Home Assistant project and community has seen enormous growth in the last three years. Many volunteers work tirelessly everyday to give you all the awesomeness that you see today. Much more work is involved than many people realize. Beyond simply coding Home Assistant, volunteers continually maintain related projects, update documentation, post examples, author blog posts, and moderate the forums and chat. This is something that we want to keep safe and functional, even as we grow.
+Starting today we are announcing a few initiatives to help protect our users, contributors and community members.
+ Read on →
+
+
+
@@ -736,302 +767,6 @@ You have to note:
-
-
-
- 0.31: Reading you the news, some serious business, spooky hackery and a breaking Z-Wave change
-
-
-
-
- Hello again friend,
-How are you? Having a good day? We sure are. If you aren’t having a good day, this might cheer you up…
-Every other weekend around here gets a little hectic leading to a big sigh of relief as we release a new version of Home Assistant to the world. And this time is no different. Our developer community has once again built us a beautiful new release with lots of new features and improvements. We hope you like it.
-One last thing before we get going though, I should warn you… @balloob got a bit lazy this week and let me (@robbiet480) step up to the plate again to write the blog post and do the release. I guess I didn’t do such a bad job in 0.27. You’ll never know what surprises I have in store. Now that i’ve got all that stuff out of the way, let’s get started…
- Stats Update
-Sadly, no big amazing stats to update you with this time, but we did recently pass 7,000 commits! This release featured submissions from 45 contributors. Hopefully with the new updater component we will be able to give you some really good stats in the 0.32 blog post.
- Hacktoberfest
-
-October means Hacktoberfest time and our community has really come through with some excellent improvements and additions. As of this writing, we have 194 merged and 41 open pull requests to the home-assistant repository and 209 merged/28 open pull requests submitted to the home-assistant.github.io repository. If you want to get in on the fun check out our Hacktoberfest blog post or the Hacktoberfest website. You get an awesome t-shirt for free if you have 4 pull requests merged in the month of October! We even have tasks that a non-developer can easily accomplish with a tiny bit of work. Better hurry up though, only 9 days left and most of the easy tasks are gone!
- ⚠️ A greatly improved updater component (Please read this!) ⚠️
-This release includes an update to our updater component. The responsibility of the updater component is to check if a new version is available and notify the user if this is the case.
-It used to be that this component would check with PyPi (the Python package manager) to see if a new update was available. This had a couple of problems:
-
- - We are unable to do a slow rollout
- - We are unable to show the user extra information (like a link to a changelog or the release date)
- - We are unable to warn users for critical security updates
-
-So to work around these problems, we decided to start hosting the version check service ourselves. Since we had to get some infrastructure spun up anyway, we figured we would take it a step further. Which leads me to this bit of the update (the most important part):
- What you need to know (the important bit!)
-Remember how I mentioned that up there in the title that there is some serious business in this release? Well, we also added some basic analytics to the updater component which get sent to the server and stored so that we get a better idea of our user base.
-Each Home Assistant instance running the updater component will generate a unique ID (based on UUIDv4) that will be used for the updater to be able to differentiate between instances. This UUID will be stored in your config directory in a file called .uuid.
-Opting out
-There are two ways to opt-out. The first way is by using the new opt_out option for the updater. This way the updater will continue to check for updates, but no information about your system will be shared with us.
-updater:
- reporting: no
-
-
-You can also disable the updater component entirely by removing updater: from your configuration.yaml although we would not suggest you do this as you would miss any critical updates.
-Finally, you can also reset your unique identifier by deleting the .uuid file and restarting Home Assistant.
-Data stored on the Home Assistant update server
-Here is what my production Home Assistant instance looks like from the server side:
-
-
-
- Name
- Description
- Example
-
-
-
-
- archCPU Architecture
- x86_64
-
- distributionLinux Distribution name (only Linux)
- Ubuntu
-
- dockerTrue if running inside Docker
- false
-
- os_nameOperating system name
- Darwin
-
- os_versionOperating system version
- 10.12
-
- python_versionPython version
- 3.5.2
-
- timezoneTimezone
- America/Los_Angeles
-
- user_agentUser agent used to submit analytics
- python-requests/2.11.1
-
- uuidUnique identifier
- 10321ee6094d4a2ebb5ed55c675d5f5e
-
- versionHome Assistant version
- 0.31.0
-
- virtualenvTrue if running inside virtualenv
- true
-
-
-In addition to the above collected data, the server will also use your IP address to do a geographic IP address lookup to determine the city that you are from. To be extremely, extremely clear about this bit: The Home Assistant updater does not: store your IP address in a database and also does not submit the location information from your configuration.yaml.
-
- 
- Geo-lookup on my IP resolves to Oakland with latitude/longitude pointing at the geographical center of the city.
-
-The server also adds two timestamps to the data: the original date your instance UUID was first seen and the timestamp of the last time we have seen your instance. This gives us the following extra data:
-
-
-
- Name
- Description
- Example
-
-
-
-
- first_seen_datetimeFirst time instance ID was submitted
- 2016-10-22T19:56:03.542Z
-
- geo_cityGeoIP determined city
- Oakland
-
- geo_country_codeGeoIP determined country code
- US
-
- geo_country_nameGeoIP determined country name
- United States
-
- geo_latitudeGeoIP determined latitude (of the city)
- 37.8047
-
- geo_longitudeGeoIP determined longitude (of the city)
- -122.2124
-
- geo_metro_codeGeoIP determined metro code
- 807
-
- geo_region_codeGeoIP determined region code
- CA
-
- geo_region_nameGeoIP determined region name
- California
-
- geo_time_zoneGeoIP determined time zone
- America/Los_Angeles
-
- geo_zip_codeGeoIP determined zip code
- 94602
-
- last_seen_datetimeMost recent time instance ID was submitted
- 2016-10-22T19:56:03.542Z
-
-
-This data is held in the highest security. The update system runs in a secured Amazon Web Services account owned by me (@robbiet480). I personally have 5 years of experience with complex AWS deployments and have an extensive security background. I have audited the entire system and made sure to take every step to protect the data, including limiting who has access (just @balloob and myself). While not directly personally identifiable we absolutely understand some users hesistance to giving this information out. Please understand that we are only collecting this information to better understand our user base to provide better long term support and feature development then is currently possible.
-We currently have no plans to publicly expose any of this information. If we did do such a thing in the future we would of course notify you in advance. It must also be stated that we will never sell or allow the use of this information for non-Home Assistant purposes.
-We thank you for understanding why we are collecting this data and hope that you leave the feature enabled but fully understand if you feel uncomfortable with this.
-This section was updated on October 24 to be more clear about geo-lookups being on the city level. See original version.
-Now, back to the fun stuff…
- Good evening. I’m Ron Burgundy and here’s what happening in your world tonight.
-Home Assistant got a crazy idea recently that it couldn’t do enough already and wanted to challenge itself even more. I really don’t understand how it came up with this kooky idea, but it now thinks that its newest hobby should be a minor career in journalism.
-0.31 adds support for the brand spanking new Alexa Flash Briefing API, allowing you to get updates from Home Assistant anytime you ask Alexa to read your flash briefing. What’s the use case you ask? Well, now when I wake up in the morning and get my flash briefing, Home Assistant adds this to the end of it for me:
-
- Drive time with traffic is 35 minutes. There is an UberPOOL that will cost $11.52, estimated to be 2 minutes away, for a total of 37 minutes. BART is currently estimated to take 29 minutes. You should take BART, as it is estimated to be faster by 8 minutes.
-
-Now I know how to best get to my real job (no, Home Assistant is not my real job, it does seem like it sometimes though) every morning. Obviously not the best home automation example, but I think you get the idea. I could see this being used to tell you any major events that happened in your home overnight or reading you your hyperlocal weather report. Thanks to the audio support you could even replace all of the default Alexa Flash Briefing sources with your own news feeds. Home Assistant supports both text and audio content as well as displaying data in the Alexa app. I also want to point out that unlike the existing Skill integration, the Flash Briefing API does not require HTTPS (but you should still be using HTTPS if possible). For more information, check out the new docs.
-
- 
- You stay classy, San Diego. (It’s funny, because balloob lives in San Diego))
-
- Major breaking Z-Wave changes ahead
-A rather nasty Z-Wave issue was discovered recently by @lukas-hetzenecker. There was a somewhat large chance that if you had multiple of the same model Z-Wave device they may both try to use the same entity IDs. To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs.
-What this means for all you Z-Wave users is that you will need to update your configurations to reflect the change. I personally have quite a few (17) Z-Wave devices and went through the process this week. Here’s what I had to do:
-
- - Update customizations
- - Update groups
- - Update my
zwave.customize section
- - Update my Alexa skills that used old entity IDs
- - Because I use
emulated_hue with Alexa and emulated_hue uses the entity ID as a unique identifier I also had to remove all Z-Wave devices from Alexa and re-add them.
-
-Your todo list may be a little different from mine, I just wanted to outline the steps I took to give you an idea of what you need to think about. It’s not a very hard process, especially when using global find and replace in Sublime Text but did take me about 20 minutes to complete.
-This is super annoying, I know, especially since we had said in 0.12 that Z-Wave IDs should hopefully never change again, but we are now forced to eat those words. I will state again that Z-Wave IDs shouldn’t change in the future but obviously we see how that went. To sum up on this section… sorry but it had to happen.
- All changes
-
- - Updater component (@infamy, @robbiet480, @kellerza)
- - Continue to setup other platforms when 1 platform config is invalid (@kellerza)
- - Create persistent notifications when a platform contains invalid config (@kellerza)
- - Logbook: Allow filtering domains and entities to be shown (@wokar)
- - HTTP: Change
approved_ips from string to CIDR validation (@mweinelt)
- - Persistent Notifications: Allow using markdown (@justweb1)
- - Netatmo: Add discovery support (@jabesq)
- - Netatmo Welcome camera: Add binary sensor (@jabesq)
- - Support added for HaveIBeenPwned (@joyrider3774)
- - Device tracker:
known_devices.yaml reading and writing tweaks and fixes (@kellerza)
- - Fix climate platforms showing the wrong temperature unit (@rcloran)
- - Lots of voluptuous love (@fabaff)
- - Ensure proper attribution for weather platforms (@fabaff)
- - Fix Telegram in Docker (@jeanregisser)
- - Support recursive config inclusions in YAML (@lwis)
- - Camera: Synology SS cameras now supported (@jgriff2)
- - History: Allow filtering domains and entities to be shown (@wokar)
- - Media Player - Squeezebox: Now able to show artist and album (@ih8gates)
- - Alexa: Flash Briefing skill support added (@robbiet480)
- - Device Tracker: Add support for Bbox Modem Router (@HydrelioxGithub)
- - Sensor: Add support for Bbox Modem Router (@HydrelioxGithub)
- - Input select: Services added to pick next and prev option (@persandstrom)
- - Sensor: ARWN now supported (@sdague)
- - Pushbullet: Push an URL note if an url is provided inside data (@jabesq)
- - Z-Wave: Allow certain devices to be not added to Home Assistant (@lukas-hetzenecker)
- - New support for Zoneminder added (@Khabi)
- - Weather: Allow tracking severe weather alerts with WUnderground (@tchellomello)
- - Sensor: New support added to track min/max/mean (@fabaff)
- - Convert EntityComponent to be async (@pvizeli, @balloob)
- - Z-Wave: Add assocation service (@turbokongen)
- - Frontend - Services dev tool: persist state and tweak UI (@justweb1)
- - Sensor: Support added for scraping websites (@fabaff)
- - Clean up of tests (@capellini)
- - New
fail filter added to templates to raise on UndefinedError (@jaharkes)
- - Support added for Emoncms history (@joyrider3774)
- - Support for Apple Push Notifications Service (@sam-io)
- - Thermostat: Netatmo now supported (@gieljnssns)
- - Alarm control panel: Concord232 now supported (@JasonCarter80)
- - Notify: Matrix support added (@mweinelt)
- - Device tracker - nmap: Allow specifying multiple inputs for nmap (@hcooper)
- - Device Tracker - snmp: SNMPv3 now supported (@T3m3z)
- - Notify: Telstra SMS now supported (@nvella)
- - Camera: Verisure now supported (@turbokongen)
- - Support added for Neato Connected Robot (@jabesq)
- - Media player: More options for Yamaha AVR (@ehagan)
- - Sensor: Support for Pilight sensor (@DavidLP)
- - iOS support (@robbiet480)
- - Minor features and bug fixes by @mtl010957, @molobrakos, @flyte, @fabaff, @phardy, @sander76, @T3m3z, @c-w, @balloob, @robbiet480, @StaticCube, @vittoriom, @hartmms, @kirichkov, @mezz64, @ishults, @Danielhiversen and @tchellomello.
-
- Release 0.31.1 - October 24
-
- - Identify special character encoding error in YAML files (@kellerza, @lwis)
- - iOS app component bug fixes (@robbiet480)
- - Fix a spelling problem on user-facing error (@robbiet480)
- - YAML includes will ignore dirs/files prefixed with . (@lwis)
-
- Breaking changes
-
- - The HTTP component now takes a different format for authenticating IPs
- - Configuration format has changed for Proximity
- - The Arduino platform are now covered by the configuration check. Please check the documentation to see how.
- - The Z-Wave entity ID change mentioned above
-
- If you need help…
-…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
- Until next time
-Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
-– Robbie
-
-
-
← Older
Newer →
diff --git a/blog/posts/3/index.html b/blog/posts/3/index.html
index b6fbba2c58..5a436958e8 100644
--- a/blog/posts/3/index.html
+++ b/blog/posts/3/index.html
@@ -59,6 +59,302 @@
+
+
+
+ 0.31: Reading you the news, some serious business, spooky hackery and a breaking Z-Wave change
+
+
+
+
+ Hello again friend,
+How are you? Having a good day? We sure are. If you aren’t having a good day, this might cheer you up…
+Every other weekend around here gets a little hectic leading to a big sigh of relief as we release a new version of Home Assistant to the world. And this time is no different. Our developer community has once again built us a beautiful new release with lots of new features and improvements. We hope you like it.
+One last thing before we get going though, I should warn you… @balloob got a bit lazy this week and let me (@robbiet480) step up to the plate again to write the blog post and do the release. I guess I didn’t do such a bad job in 0.27. You’ll never know what surprises I have in store. Now that i’ve got all that stuff out of the way, let’s get started…
+ Stats Update
+Sadly, no big amazing stats to update you with this time, but we did recently pass 7,000 commits! This release featured submissions from 45 contributors. Hopefully with the new updater component we will be able to give you some really good stats in the 0.32 blog post.
+ Hacktoberfest
+
+October means Hacktoberfest time and our community has really come through with some excellent improvements and additions. As of this writing, we have 194 merged and 41 open pull requests to the home-assistant repository and 209 merged/28 open pull requests submitted to the home-assistant.github.io repository. If you want to get in on the fun check out our Hacktoberfest blog post or the Hacktoberfest website. You get an awesome t-shirt for free if you have 4 pull requests merged in the month of October! We even have tasks that a non-developer can easily accomplish with a tiny bit of work. Better hurry up though, only 9 days left and most of the easy tasks are gone!
+ ⚠️ A greatly improved updater component (Please read this!) ⚠️
+This release includes an update to our updater component. The responsibility of the updater component is to check if a new version is available and notify the user if this is the case.
+It used to be that this component would check with PyPi (the Python package manager) to see if a new update was available. This had a couple of problems:
+
+ - We are unable to do a slow rollout
+ - We are unable to show the user extra information (like a link to a changelog or the release date)
+ - We are unable to warn users for critical security updates
+
+So to work around these problems, we decided to start hosting the version check service ourselves. Since we had to get some infrastructure spun up anyway, we figured we would take it a step further. Which leads me to this bit of the update (the most important part):
+ What you need to know (the important bit!)
+Remember how I mentioned that up there in the title that there is some serious business in this release? Well, we also added some basic analytics to the updater component which get sent to the server and stored so that we get a better idea of our user base.
+Each Home Assistant instance running the updater component will generate a unique ID (based on UUIDv4) that will be used for the updater to be able to differentiate between instances. This UUID will be stored in your config directory in a file called .uuid.
+Opting out
+There are two ways to opt-out. The first way is by using the new opt_out option for the updater. This way the updater will continue to check for updates, but no information about your system will be shared with us.
+updater:
+ reporting: no
+
+
+You can also disable the updater component entirely by removing updater: from your configuration.yaml although we would not suggest you do this as you would miss any critical updates.
+Finally, you can also reset your unique identifier by deleting the .uuid file and restarting Home Assistant.
+Data stored on the Home Assistant update server
+Here is what my production Home Assistant instance looks like from the server side:
+
+
+
+ Name
+ Description
+ Example
+
+
+
+
+ archCPU Architecture
+ x86_64
+
+ distributionLinux Distribution name (only Linux)
+ Ubuntu
+
+ dockerTrue if running inside Docker
+ false
+
+ os_nameOperating system name
+ Darwin
+
+ os_versionOperating system version
+ 10.12
+
+ python_versionPython version
+ 3.5.2
+
+ timezoneTimezone
+ America/Los_Angeles
+
+ user_agentUser agent used to submit analytics
+ python-requests/2.11.1
+
+ uuidUnique identifier
+ 10321ee6094d4a2ebb5ed55c675d5f5e
+
+ versionHome Assistant version
+ 0.31.0
+
+ virtualenvTrue if running inside virtualenv
+ true
+
+
+In addition to the above collected data, the server will also use your IP address to do a geographic IP address lookup to determine the city that you are from. To be extremely, extremely clear about this bit: The Home Assistant updater does not: store your IP address in a database and also does not submit the location information from your configuration.yaml.
+
+
+ Geo-lookup on my IP resolves to Oakland with latitude/longitude pointing at the geographical center of the city.
+
+The server also adds two timestamps to the data: the original date your instance UUID was first seen and the timestamp of the last time we have seen your instance. This gives us the following extra data:
+
+
+
+ Name
+ Description
+ Example
+
+
+
+
+ first_seen_datetimeFirst time instance ID was submitted
+ 2016-10-22T19:56:03.542Z
+
+ geo_cityGeoIP determined city
+ Oakland
+
+ geo_country_codeGeoIP determined country code
+ US
+
+ geo_country_nameGeoIP determined country name
+ United States
+
+ geo_latitudeGeoIP determined latitude (of the city)
+ 37.8047
+
+ geo_longitudeGeoIP determined longitude (of the city)
+ -122.2124
+
+ geo_metro_codeGeoIP determined metro code
+ 807
+
+ geo_region_codeGeoIP determined region code
+ CA
+
+ geo_region_nameGeoIP determined region name
+ California
+
+ geo_time_zoneGeoIP determined time zone
+ America/Los_Angeles
+
+ geo_zip_codeGeoIP determined zip code
+ 94602
+
+ last_seen_datetimeMost recent time instance ID was submitted
+ 2016-10-22T19:56:03.542Z
+
+
+This data is held in the highest security. The update system runs in a secured Amazon Web Services account owned by me (@robbiet480). I personally have 5 years of experience with complex AWS deployments and have an extensive security background. I have audited the entire system and made sure to take every step to protect the data, including limiting who has access (just @balloob and myself). While not directly personally identifiable we absolutely understand some users hesistance to giving this information out. Please understand that we are only collecting this information to better understand our user base to provide better long term support and feature development then is currently possible.
+We currently have no plans to publicly expose any of this information. If we did do such a thing in the future we would of course notify you in advance. It must also be stated that we will never sell or allow the use of this information for non-Home Assistant purposes.
+We thank you for understanding why we are collecting this data and hope that you leave the feature enabled but fully understand if you feel uncomfortable with this.
+This section was updated on October 24 to be more clear about geo-lookups being on the city level. See original version.
+Now, back to the fun stuff…
+ Good evening. I’m Ron Burgundy and here’s what happening in your world tonight.
+Home Assistant got a crazy idea recently that it couldn’t do enough already and wanted to challenge itself even more. I really don’t understand how it came up with this kooky idea, but it now thinks that its newest hobby should be a minor career in journalism.
+0.31 adds support for the brand spanking new Alexa Flash Briefing API, allowing you to get updates from Home Assistant anytime you ask Alexa to read your flash briefing. What’s the use case you ask? Well, now when I wake up in the morning and get my flash briefing, Home Assistant adds this to the end of it for me:
+
+ Drive time with traffic is 35 minutes. There is an UberPOOL that will cost $11.52, estimated to be 2 minutes away, for a total of 37 minutes. BART is currently estimated to take 29 minutes. You should take BART, as it is estimated to be faster by 8 minutes.
+
+Now I know how to best get to my real job (no, Home Assistant is not my real job, it does seem like it sometimes though) every morning. Obviously not the best home automation example, but I think you get the idea. I could see this being used to tell you any major events that happened in your home overnight or reading you your hyperlocal weather report. Thanks to the audio support you could even replace all of the default Alexa Flash Briefing sources with your own news feeds. Home Assistant supports both text and audio content as well as displaying data in the Alexa app. I also want to point out that unlike the existing Skill integration, the Flash Briefing API does not require HTTPS (but you should still be using HTTPS if possible). For more information, check out the new docs.
+
+
+ You stay classy, San Diego. (It’s funny, because balloob lives in San Diego))
+
+ Major breaking Z-Wave changes ahead
+A rather nasty Z-Wave issue was discovered recently by @lukas-hetzenecker. There was a somewhat large chance that if you had multiple of the same model Z-Wave device they may both try to use the same entity IDs. To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs.
+What this means for all you Z-Wave users is that you will need to update your configurations to reflect the change. I personally have quite a few (17) Z-Wave devices and went through the process this week. Here’s what I had to do:
+
+ - Update customizations
+ - Update groups
+ - Update my
zwave.customize section
+ - Update my Alexa skills that used old entity IDs
+ - Because I use
emulated_hue with Alexa and emulated_hue uses the entity ID as a unique identifier I also had to remove all Z-Wave devices from Alexa and re-add them.
+
+Your todo list may be a little different from mine, I just wanted to outline the steps I took to give you an idea of what you need to think about. It’s not a very hard process, especially when using global find and replace in Sublime Text but did take me about 20 minutes to complete.
+This is super annoying, I know, especially since we had said in 0.12 that Z-Wave IDs should hopefully never change again, but we are now forced to eat those words. I will state again that Z-Wave IDs shouldn’t change in the future but obviously we see how that went. To sum up on this section… sorry but it had to happen.
+ All changes
+
+ - Updater component (@infamy, @robbiet480, @kellerza)
+ - Continue to setup other platforms when 1 platform config is invalid (@kellerza)
+ - Create persistent notifications when a platform contains invalid config (@kellerza)
+ - Logbook: Allow filtering domains and entities to be shown (@wokar)
+ - HTTP: Change
approved_ips from string to CIDR validation (@mweinelt)
+ - Persistent Notifications: Allow using markdown (@justweb1)
+ - Netatmo: Add discovery support (@jabesq)
+ - Netatmo Welcome camera: Add binary sensor (@jabesq)
+ - Support added for HaveIBeenPwned (@joyrider3774)
+ - Device tracker:
known_devices.yaml reading and writing tweaks and fixes (@kellerza)
+ - Fix climate platforms showing the wrong temperature unit (@rcloran)
+ - Lots of voluptuous love (@fabaff)
+ - Ensure proper attribution for weather platforms (@fabaff)
+ - Fix Telegram in Docker (@jeanregisser)
+ - Support recursive config inclusions in YAML (@lwis)
+ - Camera: Synology SS cameras now supported (@jgriff2)
+ - History: Allow filtering domains and entities to be shown (@wokar)
+ - Media Player - Squeezebox: Now able to show artist and album (@ih8gates)
+ - Alexa: Flash Briefing skill support added (@robbiet480)
+ - Device Tracker: Add support for Bbox Modem Router (@HydrelioxGithub)
+ - Sensor: Add support for Bbox Modem Router (@HydrelioxGithub)
+ - Input select: Services added to pick next and prev option (@persandstrom)
+ - Sensor: ARWN now supported (@sdague)
+ - Pushbullet: Push an URL note if an url is provided inside data (@jabesq)
+ - Z-Wave: Allow certain devices to be not added to Home Assistant (@lukas-hetzenecker)
+ - New support for Zoneminder added (@Khabi)
+ - Weather: Allow tracking severe weather alerts with WUnderground (@tchellomello)
+ - Sensor: New support added to track min/max/mean (@fabaff)
+ - Convert EntityComponent to be async (@pvizeli, @balloob)
+ - Z-Wave: Add assocation service (@turbokongen)
+ - Frontend - Services dev tool: persist state and tweak UI (@justweb1)
+ - Sensor: Support added for scraping websites (@fabaff)
+ - Clean up of tests (@capellini)
+ - New
fail filter added to templates to raise on UndefinedError (@jaharkes)
+ - Support added for Emoncms history (@joyrider3774)
+ - Support for Apple Push Notifications Service (@sam-io)
+ - Thermostat: Netatmo now supported (@gieljnssns)
+ - Alarm control panel: Concord232 now supported (@JasonCarter80)
+ - Notify: Matrix support added (@mweinelt)
+ - Device tracker - nmap: Allow specifying multiple inputs for nmap (@hcooper)
+ - Device Tracker - snmp: SNMPv3 now supported (@T3m3z)
+ - Notify: Telstra SMS now supported (@nvella)
+ - Camera: Verisure now supported (@turbokongen)
+ - Support added for Neato Connected Robot (@jabesq)
+ - Media player: More options for Yamaha AVR (@ehagan)
+ - Sensor: Support for Pilight sensor (@DavidLP)
+ - iOS support (@robbiet480)
+ - Minor features and bug fixes by @mtl010957, @molobrakos, @flyte, @fabaff, @phardy, @sander76, @T3m3z, @c-w, @balloob, @robbiet480, @StaticCube, @vittoriom, @hartmms, @kirichkov, @mezz64, @ishults, @Danielhiversen and @tchellomello.
+
+ Release 0.31.1 - October 24
+
+ - Identify special character encoding error in YAML files (@kellerza, @lwis)
+ - iOS app component bug fixes (@robbiet480)
+ - Fix a spelling problem on user-facing error (@robbiet480)
+ - YAML includes will ignore dirs/files prefixed with . (@lwis)
+
+ Breaking changes
+
+ - The HTTP component now takes a different format for authenticating IPs
+ - Configuration format has changed for Proximity
+ - The Arduino platform are now covered by the configuration check. Please check the documentation to see how.
+ - The Z-Wave entity ID change mentioned above
+
+ If you need help…
+…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
+ Until next time
+Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
+– Robbie
+
+
+
@@ -746,86 +1042,6 @@ Heatmap
-
-
-
- 0.26: Foursquare, Fast.com, FFMPEG and GPSD
-
-
-
-
- It’s time for 0.26 and it’s again full of new features and fixes. First I want to highlight that we are now having 500 000 monthly pageviews on the website. A big milestone for us! It’s been an amazing journey. Big thanks to the Home Assistant community for being such a delightful bunch.
-This release includes code contributed by 31 different people. The biggest change in this release is a new unit system. Instead of picking Celsius or Fahrenheit you’ll have to pick imperial or metric now. This influences the units for your temperature, distance, and weight. This will simplify any platform or component that needs to know this information. Big thanks to @Teagan42 for her hard work on this!
-
-
- - Core: Introduce notion of unit system (deprecates temperature unit option) (@Teagan42)
- - Front end: Speed improvements (@balloob)
- - Front end: Improve layout of state dev tool (@balloob)
- - Proximity: Allow definition of unit of measurement (@Teagan42)
- - Flux: Add mired and kelvin mode (@HBDK)
- - Thermostat - Proliphix: Support for cooling (@sdague)
- - Media Player - LG Netcast TV: Show screenshot of what is currently playing (@shmuelzon)
- - Z-Wave improvements (@jnewland, @turbokongen)
- - Thermostat - heat control: now also able to control an AC (@mtreinish)
- - Thermostat - heat control: allow specifying a minimum duration before switching (@mtreinish)
- - InfluxDB: Whitelist entities option added (@tchellomello)
- - Sensor: Serial particulate matters sensors now supported (@open-homeautomation)
- - Sensor - Fitbit: Fix unit system (@tchellomello)
- - Light - Flux LED: Add support for [color and brightness][color] (@Danielhiversen)
- - Media Player - Plex: Now able to report on music (@abcminiuser)
- - Alarm Control Panel - Verisure: Now able to see who changed the alarm (@persandtrom)
- - Thermostat - Honeywell: Add option to read and control HVAC mode (@Teagan42)
- - Foursquare component to receive instant notifications of checkins (@robbiet480)
- - Camera: New FFMPEG platform allows to stream anything through front end (@pvizeli)
- - Manage secrets with new command line script (@kellerza)
- - Notify - SMTP: Allow embedding of images (@partofthething)
- - Sensor: OhmConnect is now supported (@robbiet480)
- - panel_custom component allows the registering of new panels (@balloob)
- - Light: New mqtt_json platform for working with JSON payload (@corbanmailloux)
- - Sensor: New Fast.com platform to measure network bandwidth performance (@nkgilley)
- - New pilight component to control 433 Mz devices (@DavidLP)
- - Sensor: GPSD now supported (@fabaff)
-
- Hotfix 0.26.1 - August 14
-
- - Fix serial_pm config validation (@open-homeautomation)
- - Check for existence of system mode on Honeywell thermostats (@mKeRix)
- - Fix unknown unit of measurement for hvac and thermostat component (@turbokongen)
-
- Hotfix 0.26.2 - August 15
-
- - Fix Wemo: have PyWemo play nicely with the latest Requests (@pavoni)
-
- Hotfix 0.26.3 - August 19
-
- - Media Player cover art would not work when an API password was set. Thanks to @maddox for reporting it and @balloob for the fix.
-
- Breaking changes
-
- - A new unit system has superseded the temperature unit option in the core configuration. For now it is backwards compatible, but you should update soon:
-
-# Configuration.yaml example
-homeassistant:
- # 'metric' for the metric system, 'imperial' for the imperial system
- unit_system: metric
-
-
-
-
-
← Older
Newer →
diff --git a/blog/posts/4/index.html b/blog/posts/4/index.html
index 85dc26c899..faed1ccfaf 100644
--- a/blog/posts/4/index.html
+++ b/blog/posts/4/index.html
@@ -59,6 +59,86 @@
+
+
+
+ 0.26: Foursquare, Fast.com, FFMPEG and GPSD
+
+
+
+
+ It’s time for 0.26 and it’s again full of new features and fixes. First I want to highlight that we are now having 500 000 monthly pageviews on the website. A big milestone for us! It’s been an amazing journey. Big thanks to the Home Assistant community for being such a delightful bunch.
+This release includes code contributed by 31 different people. The biggest change in this release is a new unit system. Instead of picking Celsius or Fahrenheit you’ll have to pick imperial or metric now. This influences the units for your temperature, distance, and weight. This will simplify any platform or component that needs to know this information. Big thanks to @Teagan42 for her hard work on this!
+
+
+ - Core: Introduce notion of unit system (deprecates temperature unit option) (@Teagan42)
+ - Front end: Speed improvements (@balloob)
+ - Front end: Improve layout of state dev tool (@balloob)
+ - Proximity: Allow definition of unit of measurement (@Teagan42)
+ - Flux: Add mired and kelvin mode (@HBDK)
+ - Thermostat - Proliphix: Support for cooling (@sdague)
+ - Media Player - LG Netcast TV: Show screenshot of what is currently playing (@shmuelzon)
+ - Z-Wave improvements (@jnewland, @turbokongen)
+ - Thermostat - heat control: now also able to control an AC (@mtreinish)
+ - Thermostat - heat control: allow specifying a minimum duration before switching (@mtreinish)
+ - InfluxDB: Whitelist entities option added (@tchellomello)
+ - Sensor: Serial particulate matters sensors now supported (@open-homeautomation)
+ - Sensor - Fitbit: Fix unit system (@tchellomello)
+ - Light - Flux LED: Add support for [color and brightness][color] (@Danielhiversen)
+ - Media Player - Plex: Now able to report on music (@abcminiuser)
+ - Alarm Control Panel - Verisure: Now able to see who changed the alarm (@persandtrom)
+ - Thermostat - Honeywell: Add option to read and control HVAC mode (@Teagan42)
+ - Foursquare component to receive instant notifications of checkins (@robbiet480)
+ - Camera: New FFMPEG platform allows to stream anything through front end (@pvizeli)
+ - Manage secrets with new command line script (@kellerza)
+ - Notify - SMTP: Allow embedding of images (@partofthething)
+ - Sensor: OhmConnect is now supported (@robbiet480)
+ - panel_custom component allows the registering of new panels (@balloob)
+ - Light: New mqtt_json platform for working with JSON payload (@corbanmailloux)
+ - Sensor: New Fast.com platform to measure network bandwidth performance (@nkgilley)
+ - New pilight component to control 433 Mz devices (@DavidLP)
+ - Sensor: GPSD now supported (@fabaff)
+
+ Hotfix 0.26.1 - August 14
+
+ - Fix serial_pm config validation (@open-homeautomation)
+ - Check for existence of system mode on Honeywell thermostats (@mKeRix)
+ - Fix unknown unit of measurement for hvac and thermostat component (@turbokongen)
+
+ Hotfix 0.26.2 - August 15
+
+ - Fix Wemo: have PyWemo play nicely with the latest Requests (@pavoni)
+
+ Hotfix 0.26.3 - August 19
+
+ - Media Player cover art would not work when an API password was set. Thanks to @maddox for reporting it and @balloob for the fix.
+
+ Breaking changes
+
+ - A new unit system has superseded the temperature unit option in the core configuration. For now it is backwards compatible, but you should update soon:
+
+# Configuration.yaml example
+homeassistant:
+ # 'metric' for the metric system, 'imperial' for the imperial system
+ unit_system: metric
+
+
+
+
+
@@ -468,34 +548,6 @@ Over a year ago I participated in the
-
-
- Using USB webcams with Home Assistant
-
-
-
-
- 
-In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like pygame or SimpleCV but I never finished something. With the Local File camera platform by Landrash and motion you could integrate a local USB webcam with a few very easy steps.
-In this blog post I am using a Fedora 24 (will most likely work on other distributions too) installation with Home Assistant 0.22.1 on a Foxconn nT-330i with an old Logitech QuickCam Orbit AF and a Logitech HD Webcam C270. As a start only the Quickcam is used. No multi-camera setup for now.
- Read on →
-
-
-
← Older
Newer →
diff --git a/blog/posts/5/index.html b/blog/posts/5/index.html
index d1b8aaa8ab..fd687d4cef 100644
--- a/blog/posts/5/index.html
+++ b/blog/posts/5/index.html
@@ -59,6 +59,34 @@
+
+
+
+ Using USB webcams with Home Assistant
+
+
+
+
+
+In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like pygame or SimpleCV but I never finished something. With the Local File camera platform by Landrash and motion you could integrate a local USB webcam with a few very easy steps.
+In this blog post I am using a Fedora 24 (will most likely work on other distributions too) installation with Home Assistant 0.22.1 on a Foxconn nT-330i with an old Logitech QuickCam Orbit AF and a Logitech HD Webcam C270. As a start only the Quickcam is used. No multi-camera setup for now.
+ Read on →
+
+
+
@@ -459,109 +487,6 @@
Make sure to subscribe to his YouTube channel for more Home Assistant video’s.
-
-
-
-
-
-
-
- 0.19: Empowering scripts and Alexa
-
-
-
-
- This release is big. Until now, our automations and scripts have been very static. Starting today it should all be a bit more dynamic.
-Scripts are now available in automations and when responding to Alexa/Amazon Echo. Both of these components will now expose data to be used in script templates (including from_state !). Passing data to script entities is available by passing the data to the script services.
-automation:
- trigger:
- platform: mqtt
- topic: some/notify/topic
- action:
- service: notify.notify
- data_template:
- message:
-
-automation 2:
- trigger:
- platform: state
- entity_id: light.hue
- action:
- service: notify.notify
- data_template:
- message: is now
-
-
-Entity Namespaces allow you to influence the entity ids for a specific platform. For example you can turn light.living_room into light.holiday_home_living_room with the following config:
-light:
- platform: hue
- entity_namespace: holiday_home
-
-
-
- - Automation: allow script syntax for action (@balloob)
- - Automation: expose
trigger variable to script templates (@balloob)
- - Script: allow passing variables for script templates in the script service calls (@balloob)
- - Alexa/Amazon Echo: allow script syntax for action (@balloob)
- - Alexa/Amazon Echo: expose intent variables to script templates (@balloob)
- - Script syntax: conditions now supported to interrupt execution (@balloob)
- - Automation: use new condition syntax (@balloob)
- - Script syntax: two new conditions
and and or to combine conditions (@balloob)
- - Any platform: Allow setting entity namespace to prefix entity_ids. (@balloob)
- - Switch: Raspberry Pi generic 433 Mhz GPIO adapters now supported (@milaq)
- - Z-Wave: use more sane defaults (@danieljkemp)
- - Media Player: Snapcast now supports picking a source (@happyleavesaoc)
- - MySensors: major cleanup (@MartinHjelmare)
- - Binary Sensor: Command line sensor now supports classes (@fabaff)
- - MQTT: allow client key authentication (@timharton)
- - Sensor: Forecast.io now supports minutely, hourly and daily summaries (@aceat64)
- - Media Player: Pioneer AVR now supported (@kylehendricks)
- - Switch: Acer Projectors now supported (@deisi)
- - New HVAC component added with Z-Wave support (@turbokongen)
- - Support added for OctoPrint (@w1ll1am23)
- - Configuration.yaml can now refer to environment variables using
!env_var (@bah2830)
- - Lock: Z-Wave now supported (@devdelay)
- - New Dweet component to export data (@fabaff)
- - Media Player now supports stop command + initial kodi support (@hmronline)
- - Zigbee: push updates now supported (@flyte)
- - Wink devices with battery level will now show these (@w1ll1am23)
- - Templates: new
as_timestamp method now available (@srcLurker)
- - API: Add [
/api/discovery_info] with basic instance info (@robbiet480)
- - Sensor: Google Maps travel time added (@Danielhiversen)
- - HTTP: Allow adding CORS headers (@robbiet480)
- - Sensor: Fitbit support added (@robbiet480)
- - Bug fixes and tweaks by @turbokongen, @danieljkemp, @Danielhiversen, @TheRealLink, @persandstrom, @sander76, @fabaff, @ishults, @Bart274, @robbiet480, @Cinntax, @blackdog70, @gwendalg, @JshWright, @kylehendricks, @bradsk88, @shaftoe, @molobrakos, @bah2830, @nkgilley
-
-Deprecations
-
- - Conditions in automations should now specify which condition to use with
condition: instead of platform:. For example condition: state.
- - RFXtrx has a new config format.
-
-Old RFXtrx config format:
- devices:
- 123efab1:
- name: My DI.0 light device
- packetid: 1b2200000890efab1213f60
-
-
-New RFXtrx config format:
- devices:
- 1b2200000890efab1213f60:
- name: My DI.0 light device
-
diff --git a/blog/posts/6/index.html b/blog/posts/6/index.html
index 8412872e29..32d60843a1 100644
--- a/blog/posts/6/index.html
+++ b/blog/posts/6/index.html
@@ -59,6 +59,109 @@
+
+
+
+ 0.19: Empowering scripts and Alexa
+
+
+
+
+ This release is big. Until now, our automations and scripts have been very static. Starting today it should all be a bit more dynamic.
+Scripts are now available in automations and when responding to Alexa/Amazon Echo. Both of these components will now expose data to be used in script templates (including from_state !). Passing data to script entities is available by passing the data to the script services.
+automation:
+ trigger:
+ platform: mqtt
+ topic: some/notify/topic
+ action:
+ service: notify.notify
+ data_template:
+ message:
+
+automation 2:
+ trigger:
+ platform: state
+ entity_id: light.hue
+ action:
+ service: notify.notify
+ data_template:
+ message: is now
+
+
+Entity Namespaces allow you to influence the entity ids for a specific platform. For example you can turn light.living_room into light.holiday_home_living_room with the following config:
+light:
+ platform: hue
+ entity_namespace: holiday_home
+
+
+
+ - Automation: allow script syntax for action (@balloob)
+ - Automation: expose
trigger variable to script templates (@balloob)
+ - Script: allow passing variables for script templates in the script service calls (@balloob)
+ - Alexa/Amazon Echo: allow script syntax for action (@balloob)
+ - Alexa/Amazon Echo: expose intent variables to script templates (@balloob)
+ - Script syntax: conditions now supported to interrupt execution (@balloob)
+ - Automation: use new condition syntax (@balloob)
+ - Script syntax: two new conditions
and and or to combine conditions (@balloob)
+ - Any platform: Allow setting entity namespace to prefix entity_ids. (@balloob)
+ - Switch: Raspberry Pi generic 433 Mhz GPIO adapters now supported (@milaq)
+ - Z-Wave: use more sane defaults (@danieljkemp)
+ - Media Player: Snapcast now supports picking a source (@happyleavesaoc)
+ - MySensors: major cleanup (@MartinHjelmare)
+ - Binary Sensor: Command line sensor now supports classes (@fabaff)
+ - MQTT: allow client key authentication (@timharton)
+ - Sensor: Forecast.io now supports minutely, hourly and daily summaries (@aceat64)
+ - Media Player: Pioneer AVR now supported (@kylehendricks)
+ - Switch: Acer Projectors now supported (@deisi)
+ - New HVAC component added with Z-Wave support (@turbokongen)
+ - Support added for OctoPrint (@w1ll1am23)
+ - Configuration.yaml can now refer to environment variables using
!env_var (@bah2830)
+ - Lock: Z-Wave now supported (@devdelay)
+ - New Dweet component to export data (@fabaff)
+ - Media Player now supports stop command + initial kodi support (@hmronline)
+ - Zigbee: push updates now supported (@flyte)
+ - Wink devices with battery level will now show these (@w1ll1am23)
+ - Templates: new
as_timestamp method now available (@srcLurker)
+ - API: Add [
/api/discovery_info] with basic instance info (@robbiet480)
+ - Sensor: Google Maps travel time added (@Danielhiversen)
+ - HTTP: Allow adding CORS headers (@robbiet480)
+ - Sensor: Fitbit support added (@robbiet480)
+ - Bug fixes and tweaks by @turbokongen, @danieljkemp, @Danielhiversen, @TheRealLink, @persandstrom, @sander76, @fabaff, @ishults, @Bart274, @robbiet480, @Cinntax, @blackdog70, @gwendalg, @JshWright, @kylehendricks, @bradsk88, @shaftoe, @molobrakos, @bah2830, @nkgilley
+
+Deprecations
+
+ - Conditions in automations should now specify which condition to use with
condition: instead of platform:. For example condition: state.
+ - RFXtrx has a new config format.
+
+Old RFXtrx config format:
+ devices:
+ 123efab1:
+ name: My DI.0 light device
+ packetid: 1b2200000890efab1213f60
+
+
+New RFXtrx config format:
+ devices:
+ 1b2200000890efab1213f60:
+ name: My DI.0 light device
+
+
+
+
+
@@ -426,69 +529,6 @@
lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
-
-
-
-
-
-
- 0.15: Unforked Open Z-Wave, templated service calls, extended scene support and PEP257 compliance.
-
-
-
-
- Two weeks has past so here is 0.15! We have been focussing a lot on quality. Making sure the system is more stable and reliable. I usually try to highlight one cool thing in the release notes but this release has 4 exciting announcements!
-
- - @fabaff has upgraded the codebase to follow the PEP257 documentation standard.
- - @partofthething has migrated us to use the main Python Open Z-Wave library instead of our forked version.
- - To make our automations more powerful, @persandstrom added the option to use templates to dynamically create service calls. This works for automation, Alexa, universal media player, template switch. Learn more.
- - @MartinHjelmare has upgraded our scene support to now support all built-in services and components.
-
-Besides bug fixes, this release also brings:
-
-
- - Scene: Converted to a platform based component (@sander76)
- - Scene: Hunter Douglas Powerview now supported (@sander76)
- - Lock: MQTT platform added (@fabaff)
- - Device Tracker: OwnTracks will allow filtering inaccurate GPS locations (@HydrelioxGitHub)
- - Binary Sensor: Wemo Motion now supported (@pavoni, @ryanlaux)
-
-# Example using templates for service and data in service call.
-# Works for automation, Alexa, universal media player, template switch.
-automation:
- - trigger:
- - platform: state
- entity_id: switch.bathroom
- action:
- service_template: >
- {% if is_state('switch.bathroom', 'on') %}
- switch.turn_on
- {% else %}
- switch.turn_off
- {% endif %}
- data_template:
- entity_id: switch.{{ states('input_select.is') }}
-
-
-Breaking Changes
-
- - Media Player: Attributes to call service play_media has been renamed to
-
media_content_type and media_content_id, to match the corresponding media
-player state attributes. This change affects automations, scripts and scenes.
-
diff --git a/blog/posts/7/index.html b/blog/posts/7/index.html
index 03f8918d1e..f20c7ad2ad 100644
--- a/blog/posts/7/index.html
+++ b/blog/posts/7/index.html
@@ -59,6 +59,69 @@
+
+
+
+ 0.15: Unforked Open Z-Wave, templated service calls, extended scene support and PEP257 compliance.
+
+
+
+
+ Two weeks has past so here is 0.15! We have been focussing a lot on quality. Making sure the system is more stable and reliable. I usually try to highlight one cool thing in the release notes but this release has 4 exciting announcements!
+
+ - @fabaff has upgraded the codebase to follow the PEP257 documentation standard.
+ - @partofthething has migrated us to use the main Python Open Z-Wave library instead of our forked version.
+ - To make our automations more powerful, @persandstrom added the option to use templates to dynamically create service calls. This works for automation, Alexa, universal media player, template switch. Learn more.
+ - @MartinHjelmare has upgraded our scene support to now support all built-in services and components.
+
+Besides bug fixes, this release also brings:
+
+
+ - Scene: Converted to a platform based component (@sander76)
+ - Scene: Hunter Douglas Powerview now supported (@sander76)
+ - Lock: MQTT platform added (@fabaff)
+ - Device Tracker: OwnTracks will allow filtering inaccurate GPS locations (@HydrelioxGitHub)
+ - Binary Sensor: Wemo Motion now supported (@pavoni, @ryanlaux)
+
+# Example using templates for service and data in service call.
+# Works for automation, Alexa, universal media player, template switch.
+automation:
+ - trigger:
+ - platform: state
+ entity_id: switch.bathroom
+ action:
+ service_template: >
+ {% if is_state('switch.bathroom', 'on') %}
+ switch.turn_on
+ {% else %}
+ switch.turn_off
+ {% endif %}
+ data_template:
+ entity_id: switch.{{ states('input_select.is') }}
+
+
+Breaking Changes
+
+ - Media Player: Attributes to call service play_media has been renamed to
+
media_content_type and media_content_id, to match the corresponding media
+player state attributes. This change affects automations, scripts and scenes.
+
+
+
+
@@ -527,50 +590,6 @@ Example of the new views in the frontend. Learn mor
-
-
-
- 0.10: Amazon Echo, iCloud, Dweet.io, Twitch and templating support!
-
-
-
-
- Alrighty, it’s time for Home Assistant 0.10. A lot amazing things have changed and sadly we also had to introduce a bunch of backwards incompatible changes. I would like to give a big shoutout to Philip Lundrigan (@philipbl) who put a lot in effort in helping the migration to move towards using templates for a wide variety of platforms.
-
-
-
-
-
- - Device tracker: iCloud platform added (@xorso, @kevinpanaro)
- - Frontend: Improved caching using service workers if served over SSL (@balloob)
- - Sensor: Twitch platform added (@happyleavesaoc)
- - Template support (@balloob, @philipbl, @fabaff)
- - Thermostat: Heatmiser platform added (@andylockran)
- - Sensor: Dweet.io platform added (@fabaff)
- - Alexa/Amazon echo component added (@balloob)
- - Device Tracker: FritzBox platform added (@deisi, @caiuspb)
- - Sensor: Wink now supports the Egg minders (@w1ll1am23)
- - Sensor: ELIQ Online platform added (@molobrakos)
- - Binary sensor: REST platform added (@fabaff)
- - Sensor: Torque (OBD2) platform added (@happyleavesaoc)
-
- Read on →
-
-
-
← Older
Newer →
diff --git a/blog/posts/8/index.html b/blog/posts/8/index.html
index 83bb2c04b9..0fadbcab8a 100644
--- a/blog/posts/8/index.html
+++ b/blog/posts/8/index.html
@@ -59,6 +59,50 @@
+
+
+
+ 0.10: Amazon Echo, iCloud, Dweet.io, Twitch and templating support!
+
+
+
+
+ Alrighty, it’s time for Home Assistant 0.10. A lot amazing things have changed and sadly we also had to introduce a bunch of backwards incompatible changes. I would like to give a big shoutout to Philip Lundrigan (@philipbl) who put a lot in effort in helping the migration to move towards using templates for a wide variety of platforms.
+
+
+
+
+
+ - Device tracker: iCloud platform added (@xorso, @kevinpanaro)
+ - Frontend: Improved caching using service workers if served over SSL (@balloob)
+ - Sensor: Twitch platform added (@happyleavesaoc)
+ - Template support (@balloob, @philipbl, @fabaff)
+ - Thermostat: Heatmiser platform added (@andylockran)
+ - Sensor: Dweet.io platform added (@fabaff)
+ - Alexa/Amazon echo component added (@balloob)
+ - Device Tracker: FritzBox platform added (@deisi, @caiuspb)
+ - Sensor: Wink now supports the Egg minders (@w1ll1am23)
+ - Sensor: ELIQ Online platform added (@molobrakos)
+ - Binary sensor: REST platform added (@fabaff)
+ - Sensor: Torque (OBD2) platform added (@happyleavesaoc)
+
+ Read on →
+
+
+
@@ -375,43 +419,6 @@ The InfluxDB database is a so-called time se
-
-
-
- Report the temperature with ESP8266 to MQTT
-
-
-
-
-I recently learned about the ESP8266, a $5 chip that includes WiFi and is Arduino compatible. This means that all your DIY projects can now be done for a fraction of the price.
-For this tutorial, I’ll walk through how to get going with ESP8266, get the temperature and humidity and report it to MQTT where Home Asssistant can pick it up.
-
-
-Picture of the final setup (+ 2 LED for decoration)
-
-
-
-Home Assistant will keep track of historical values and allow you to integrate it into automation.
-
- Read on →
-
-
-
← Older
Newer →
diff --git a/blog/posts/9/index.html b/blog/posts/9/index.html
index 72ddbebb28..88e5bac457 100644
--- a/blog/posts/9/index.html
+++ b/blog/posts/9/index.html
@@ -59,6 +59,43 @@
+
+
+
+ Report the temperature with ESP8266 to MQTT
+
+
+
+
+I recently learned about the ESP8266, a $5 chip that includes WiFi and is Arduino compatible. This means that all your DIY projects can now be done for a fraction of the price.
+For this tutorial, I’ll walk through how to get going with ESP8266, get the temperature and humidity and report it to MQTT where Home Asssistant can pick it up.
+
+
+Picture of the final setup (+ 2 LED for decoration)
+
+
+
+Home Assistant will keep track of historical values and allow you to integrate it into automation.
+
+ Read on →
+
+
+
@@ -394,45 +431,6 @@ Inspried by a
-
-
- MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported
-
-
-
-
- It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to @balloob. If you’re a developer, make sure you read up on the deprecation notices. @fabaff did another great round of documentating all the various components.
-MQTT Support
- The big new addition in this release is the support for the MQTT protocol by @fabaff with some help from @balloob. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (see the example) and also support for the automation component has been added. For more information, see the MQTT component page.
-# Example configuration.yaml entry
-mqtt:
- broker: IP_ADDRESS_BROKER
- # All the other options are optional:
- port: 1883
- keepalive: 60
- qos: 0
- username: your_username
- password: your_secret_password
-
-
- Read on →
-
-
-
← Older
Newer →
diff --git a/images/blog/2017-03-opensourcecraft/social.jpg b/images/blog/2017-03-opensourcecraft/social.jpg
new file mode 100644
index 0000000000..3ee111c7cd
Binary files /dev/null and b/images/blog/2017-03-opensourcecraft/social.jpg differ
diff --git a/index.html b/index.html
index c70c10290e..1e782fd562 100644
--- a/index.html
+++ b/index.html
@@ -105,6 +105,10 @@ Home Assistant is an open-source home automation platform running on Python 3. T
Recent Blog Posts
+ -
+ OpenSourceCraft interviews our founder Paulus Schoutsen
+ March 23, 2017
+
-
0.40.2 and broken dependencies
March 22, 2017
@@ -113,10 +117,6 @@ Home Assistant is an open-source home automation platform running on Python 3. T
Home Assistant 0.40: Turn any Android phone into an IP Webcam
March 11, 2017
- -
- 0.39: Configuration panel, state restoration and improved docs
- February 25, 2017
-
diff --git a/sitemap.xml b/sitemap.xml
index 8483855f86..788b508939 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1,6 +1,10 @@
+https://home-assistant.io/blog/2017/03/23/opensourcecraft-interview-with-founder-paulus-schoutsen/
+2017-03-23T08:04:05+00:00
+
+
https://home-assistant.io/blog/2017/03/22/broken-dependencies/
2017-03-22T08:04:05+00:00
@@ -3025,62 +3029,62 @@
https://home-assistant.io/demo/frontend.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/demo/index.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2017-03-23T15:39:56+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2017-03-23T15:39:57+00:00
+2017-03-23T15:48:05+00:00
https://home-assistant.io/static/mdi-demo.html
-2017-03-23T15:39:57+00:00
+2017-03-23T15:48:05+00:00
+