jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Site updated at 2017-11-11 08:44:59 UTC

Browse source
This commit is contained in:
Travis CI 2017-11-11 08:44:59 +00:00
parent 9f2b7f571f
commit b6368d34b8
227 changed files with 2066 additions and 1370 deletions
Download patch file Download diff file Expand all files Collapse all files

56
blog/posts/10/index.html
View file

@ -67,6 +67,33 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/07/06/pocketchip-running-home-assistant/">PocketCHIP running Home Assistant</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-07-06T05:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> July 06, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter</span>
<span><i class='icon-time'></i> two minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/07/06/pocketchip-running-home-assistant/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><img src="/images/blog/2016-07-pocketchip/pocketchip-logo.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;" width="200" />
Over a year ago I participated in the <a href="https://www.kickstarter.com/projects/1598272670/chip-the-worlds-first-9-computer/description">kickstarter campaign</a> for “CHIP - The World’s First Nine Dollar Computer” by <a href="https://www.nextthing.co/">Next Thing Co.</a>. 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…</p>
<a class="btn pull-right" href="/blog/2016/07/06/pocketchip-running-home-assistant/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -509,35 +536,6 @@ In the past month I was thinking about ways to integrate USB webcams into Home A
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/05/18/why-we-use-polymer/">Why we use web components and Polymer</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-05-18T00:09:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> May 18, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> three minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Technology</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/05/18/why-we-use-polymer/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>I’ve been planning to write this post for a while now as we get questions like this a lot: <em>“Why does Home Assistant use Polymer? Why not React, Redux and what not?”</em></p>
<p>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.</p>
<p>Still, <a href="https://home-assistant.io/demo">we use Polymer and it’s awesome</a>. 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.</p>
<p>Polymer gives us components for the web, just like React, but based on web standards: <a href="https://www.w3.org/standards/techs/components#w3c_all">web components</a>, <a href="https://www.w3.org/TR/css-variables/">CSS variables</a>. 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.</p>
<a class="btn pull-right" href="/blog/2016/05/18/why-we-use-polymer/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<div class="pagination">
<a class="btn pull-left" href="/blog/posts/11">&larr; Older</a>
<a class="btn pull-right" href="/blog/posts/9">Newer &rarr;</a>

60
blog/posts/11/index.html
View file

@ -67,6 +67,35 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/05/18/why-we-use-polymer/">Why we use web components and Polymer</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-05-18T00:09:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> May 18, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> three minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Technology</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/05/18/why-we-use-polymer/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>I’ve been planning to write this post for a while now as we get questions like this a lot: <em>“Why does Home Assistant use Polymer? Why not React, Redux and what not?”</em></p>
<p>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.</p>
<p>Still, <a href="https://home-assistant.io/demo">we use Polymer and it’s awesome</a>. 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.</p>
<p>Polymer gives us components for the web, just like React, but based on web standards: <a href="https://www.w3.org/standards/techs/components#w3c_all">web components</a>, <a href="https://www.w3.org/TR/css-variables/">CSS variables</a>. 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.</p>
<a class="btn pull-right" href="/blog/2016/05/18/why-we-use-polymer/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -467,37 +496,6 @@
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/04/05/your-hub-should-be-local-and-open/">Your hub should be local and open</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-04-05T21:11:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> April 5, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 1 minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Internet-of-Things</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/04/05/your-hub-should-be-local-and-open/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>Today the news spread that Google will be <a href="https://medium.com/@arlogilbert/the-time-that-tony-fadell-sold-me-a-container-of-hummus-cb0941c762c1#.rmppks86a">shutting down the Revolv hubs</a>. 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 <a href="https://discuss.ninjablocks.com/t/ninja-blocks-whats-been-happening-whats-happening-next/3608">ninjasphere</a>: open it all up and let people decide on the fate of their <em>own</em> hub.</p>
<p>I’ve said it <a href="/blog/2016/01/19/perfect-home-automation/#your-system-should-run-at-home-not-in-the-cloud">before</a> but I’ll repeat it again:</p>
<blockquote>
<p>The cloud should be treated as an extension to your smart home instead of running it.</p>
</blockquote>
<p>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.</p>
<p>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 <a href="http://www.gartner.com/newsroom/id/2869521">Gartner</a> predicts that by 2017, 50 percent of IoT solutions will originate in startups that are less than three years old.</p>
</div>
</article>
<hr>
<div class="pagination">
<a class="btn pull-left" href="/blog/posts/12">&larr; Older</a>
<a class="btn pull-right" href="/blog/posts/10">Newer &rarr;</a>

61
blog/posts/12/index.html
View file

@ -67,6 +67,37 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/04/05/your-hub-should-be-local-and-open/">Your hub should be local and open</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-04-05T21:11:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> April 5, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 1 minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Internet-of-Things</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/04/05/your-hub-should-be-local-and-open/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>Today the news spread that Google will be <a href="https://medium.com/@arlogilbert/the-time-that-tony-fadell-sold-me-a-container-of-hummus-cb0941c762c1#.rmppks86a">shutting down the Revolv hubs</a>. 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 <a href="https://discuss.ninjablocks.com/t/ninja-blocks-whats-been-happening-whats-happening-next/3608">ninjasphere</a>: open it all up and let people decide on the fate of their <em>own</em> hub.</p>
<p>I’ve said it <a href="/blog/2016/01/19/perfect-home-automation/#your-system-should-run-at-home-not-in-the-cloud">before</a> but I’ll repeat it again:</p>
<blockquote>
<p>The cloud should be treated as an extension to your smart home instead of running it.</p>
</blockquote>
<p>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.</p>
<p>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 <a href="http://www.gartner.com/newsroom/id/2869521">Gartner</a> predicts that by 2017, 50 percent of IoT solutions will originate in startups that are less than three years old.</p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -584,36 +615,6 @@ Example of the new views in the frontend. <a href="/components/group/">Learn mor
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/01/19/perfect-home-automation/">Perfect Home Automation</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-01-19T08:20:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> January 19, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> five minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Internet-of-Things</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/01/19/perfect-home-automation/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>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.</p>
<h3><a class="title-link" name="you-should-not-have-to-adapt-to-technology" href="#you-should-not-have-to-adapt-to-technology"></a> You should not have to adapt to technology.</h3>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<a class="btn pull-right" href="/blog/2016/01/19/perfect-home-automation/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<div class="pagination">
<a class="btn pull-left" href="/blog/posts/13">&larr; Older</a>
<a class="btn pull-right" href="/blog/posts/11">Newer &rarr;</a>

84
blog/posts/13/index.html
View file

@ -67,6 +67,36 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/01/19/perfect-home-automation/">Perfect Home Automation</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-01-19T08:20:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> January 19, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> five minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Internet-of-Things</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/01/19/perfect-home-automation/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>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.</p>
<h3><a class="title-link" name="you-should-not-have-to-adapt-to-technology" href="#you-should-not-have-to-adapt-to-technology"></a> You should not have to adapt to technology.</h3>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<a class="btn pull-right" href="/blog/2016/01/19/perfect-home-automation/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -385,60 +415,6 @@ The <a href="https://influxdb.com/">InfluxDB</a> database is a so-called time se
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2015/11/16/zwave-switches-lights-and-honeywell-thermostats-now-supported/">0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights </a>
</h1>
<div class="meta clearfix">
<time datetime="2015-11-16T21:27:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> November 16, 2015</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 1 minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Release-Notes</li>
</ul>
</span>
<a class='comments'
href="/blog/2015/11/16/zwave-switches-lights-and-honeywell-thermostats-now-supported/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><img src="/images/screenshots/custom-icons.png" style="float: right;" />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 <a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> for idea and prototype). To get started with customizing, pick any icon from <a href="https://MaterialDesignIcons.com">MaterialDesignIcons.com</a>, prefix the name with <code class="highlighter-rouge">mdi:</code> and stick it into your <code class="highlighter-rouge">customize</code> section in <code class="highlighter-rouge">configuration.yaml</code>:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">homeassistant</span><span class="pi">:</span>
<span class="s">customize</span><span class="pi">:</span>
<span class="s">switch.ac</span><span class="pi">:</span>
<span class="s">icon</span><span class="pi">:</span> <span class="s1">'</span><span class="s">mdi:air-conditioner'</span>
</code></pre>
</div>
<h4>Breaking changes</h4>
<ul>
<li>Any existing zone icon will have to be replaced with one from <a href="https://MaterialDesignIcons.com">MaterialDesignIcons.com</a>.</li>
<li>LimitlessLED light services require colors to be specified in RGB instead of XY.</li>
</ul>
<h4>Changes</h4>
<p><img src="/images/supported_brands/honeywell.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;" height="50" /><img src="/images/supported_brands/orvibo.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;" height="50" /><img src="/images/supported_brands/pushetta.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;" height="50" /></p>
<ul>
<li>Thermostat: <a href="/components/thermostat.honeywell/">Honeywell</a> now supported (<a href="https://github.com/sander76">@sander76</a>)</li>
<li>Switch: <a href="/components/switch.orvibo/">Orvibo</a> now supported (<a href="https://github.com/happyleavesaoc">@happyleavesaoc</a>)</li>
<li>Camera: <a href="/components/camera.mjpeg/">mjpeg camera’s</a> now supported (<a href="https://github.com/ryanturner">@ryanturner</a>)</li>
<li>Notify: <a href="/components/notify.pushetta/">Pushetta</a> now supported (<a href="https://github.com/fabaff">@fabaff</a>)</li>
<li>Light: <a href="/components/light.mqtt/">MQTT</a> now supported (<a href="https://github.com/hexxter">@hexxter</a>)</li>
<li>Light: <a href="/components/zwave/">Z-Wave</a> now supported (<a href="https://github.com/leoc">@leoc</a>)</li>
<li>Switch: <a href="/components/zwave/">Z-Wave</a> now supported (<a href="https://github.com/leoc">@leoc</a>)</li>
<li>New component <a href="/components/logger/">logger</a> allows filtering logged data (<a href="https://github.com/badele">@badele</a>)</li>
<li>New component <a href="/components/updater/">updater</a> will notify users if an update for Home Assistant is available (<a href="https://github.com/rmkraus">@rmkraus</a>)</li>
<li>Notify: <a href="/components/notify.pushbullet/">PushBullet</a> now allows targeting contacts/channels/specific devices (<a href="https://github.com/tomduijf">@tomduijf</a>)</li>
<li>Light: Allow controlling color temperature (<a href="https://github.com/tomduijf">@tomduijf</a>)</li>
<li>Frontend: about page added (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Switch RGB as the color unit used in light component (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Re-install platform and component dependencies after a Home Assistant version upgrade (<a href="https://github.com/balloob">@balloob</a>)</li>
</ul>
</div>
</article>
<hr>
<div class="pagination">
<a class="btn pull-left" href="/blog/posts/14">&larr; Older</a>
<a class="btn pull-right" href="/blog/posts/12">Newer &rarr;</a>

89
blog/posts/14/index.html
View file

@ -67,6 +67,60 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2015/11/16/zwave-switches-lights-and-honeywell-thermostats-now-supported/">0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights </a>
</h1>
<div class="meta clearfix">
<time datetime="2015-11-16T21:27:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> November 16, 2015</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 1 minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Release-Notes</li>
</ul>
</span>
<a class='comments'
href="/blog/2015/11/16/zwave-switches-lights-and-honeywell-thermostats-now-supported/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><img src="/images/screenshots/custom-icons.png" style="float: right;" />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 <a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> for idea and prototype). To get started with customizing, pick any icon from <a href="https://MaterialDesignIcons.com">MaterialDesignIcons.com</a>, prefix the name with <code class="highlighter-rouge">mdi:</code> and stick it into your <code class="highlighter-rouge">customize</code> section in <code class="highlighter-rouge">configuration.yaml</code>:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">homeassistant</span><span class="pi">:</span>
<span class="s">customize</span><span class="pi">:</span>
<span class="s">switch.ac</span><span class="pi">:</span>
<span class="s">icon</span><span class="pi">:</span> <span class="s1">'</span><span class="s">mdi:air-conditioner'</span>
</code></pre>
</div>
<h4>Breaking changes</h4>
<ul>
<li>Any existing zone icon will have to be replaced with one from <a href="https://MaterialDesignIcons.com">MaterialDesignIcons.com</a>.</li>
<li>LimitlessLED light services require colors to be specified in RGB instead of XY.</li>
</ul>
<h4>Changes</h4>
<p><img src="/images/supported_brands/honeywell.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;" height="50" /><img src="/images/supported_brands/orvibo.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;" height="50" /><img src="/images/supported_brands/pushetta.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;" height="50" /></p>
<ul>
<li>Thermostat: <a href="/components/thermostat.honeywell/">Honeywell</a> now supported (<a href="https://github.com/sander76">@sander76</a>)</li>
<li>Switch: <a href="/components/switch.orvibo/">Orvibo</a> now supported (<a href="https://github.com/happyleavesaoc">@happyleavesaoc</a>)</li>
<li>Camera: <a href="/components/camera.mjpeg/">mjpeg camera’s</a> now supported (<a href="https://github.com/ryanturner">@ryanturner</a>)</li>
<li>Notify: <a href="/components/notify.pushetta/">Pushetta</a> now supported (<a href="https://github.com/fabaff">@fabaff</a>)</li>
<li>Light: <a href="/components/light.mqtt/">MQTT</a> now supported (<a href="https://github.com/hexxter">@hexxter</a>)</li>
<li>Light: <a href="/components/zwave/">Z-Wave</a> now supported (<a href="https://github.com/leoc">@leoc</a>)</li>
<li>Switch: <a href="/components/zwave/">Z-Wave</a> now supported (<a href="https://github.com/leoc">@leoc</a>)</li>
<li>New component <a href="/components/logger/">logger</a> allows filtering logged data (<a href="https://github.com/badele">@badele</a>)</li>
<li>New component <a href="/components/updater/">updater</a> will notify users if an update for Home Assistant is available (<a href="https://github.com/rmkraus">@rmkraus</a>)</li>
<li>Notify: <a href="/components/notify.pushbullet/">PushBullet</a> now allows targeting contacts/channels/specific devices (<a href="https://github.com/tomduijf">@tomduijf</a>)</li>
<li>Light: Allow controlling color temperature (<a href="https://github.com/tomduijf">@tomduijf</a>)</li>
<li>Frontend: about page added (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Switch RGB as the color unit used in light component (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Re-install platform and component dependencies after a Home Assistant version upgrade (<a href="https://github.com/balloob">@balloob</a>)</li>
</ul>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -407,41 +461,6 @@ Inspried by a <a href="https://github.com/home-assistant/home-assistant/issues/3
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/">Laundry Automation: insight and notifications</a>
</h1>
<div class="meta clearfix">
<time datetime="2015-08-26T15:12:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> August 26, 2015</time>
<span class="byline author vcard"><i class='icon-user'></i> Nolan Gilley</span>
<span><i class='icon-time'></i> five minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>User-Stories</li>
</ul>
</span>
<a class='comments'
href="/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><em>This is a guest post by Home Assistant user and contributor <a href="https://github.com/nkgilley">Nolan Gilley</a>.</em></p>
<p>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.</p>
<p>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 <a href="https://lowpowerlab.com/moteino/">Moteino</a>, 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 <a href="/components/mqtt/">MQTT component</a> to my Raspberry Pi.</p>
<p>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.</p>
<p class="img">
<a href="/images/blog/2015-08-laundry-automation/data-graph.png">
<img src="/images/blog/2015-08-laundry-automation/data-graph.png" />
</a>
Graph showing the accelerometer data
</p>
<a class="btn pull-right" href="/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<div class="pagination">
<a class="btn pull-left" href="/blog/posts/15">&larr; Older</a>
<a class="btn pull-right" href="/blog/posts/13">Newer &rarr;</a>

65
blog/posts/15/index.html
View file

@ -67,6 +67,41 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/">Laundry Automation: insight and notifications</a>
</h1>
<div class="meta clearfix">
<time datetime="2015-08-26T15:12:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> August 26, 2015</time>
<span class="byline author vcard"><i class='icon-user'></i> Nolan Gilley</span>
<span><i class='icon-time'></i> five minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>User-Stories</li>
</ul>
</span>
<a class='comments'
href="/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><em>This is a guest post by Home Assistant user and contributor <a href="https://github.com/nkgilley">Nolan Gilley</a>.</em></p>
<p>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.</p>
<p>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 <a href="https://lowpowerlab.com/moteino/">Moteino</a>, 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 <a href="/components/mqtt/">MQTT component</a> to my Raspberry Pi.</p>
<p>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.</p>
<p class="img">
<a href="/images/blog/2015-08-laundry-automation/data-graph.png">
<img src="/images/blog/2015-08-laundry-automation/data-graph.png" />
</a>
Graph showing the accelerometer data
</p>
<a class="btn pull-right" href="/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -443,36 +478,6 @@ An initial version of voice control for Home Assistant has landed. The current i
<span class="s">conversation</span><span class="pi">:</span>
</code></pre>
</div>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2015/03/08/new-logo/">New logo for Home Assistant</a>
</h1>
<div class="meta clearfix">
<time datetime="2015-03-08T22:16:10+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> March 8, 2015</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> Less than one minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Organisation</li>
</ul>
</span>
<a class='comments'
href="/blog/2015/03/08/new-logo/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>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, <a href="http://jeremygeltman.com/">Jeremy Geltman</a> has come to the rescue and contributed a brand new logo for Home Assistant.</p>
<p>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).</p>
<p class="img">
<img src="/images/blog/ha-logo-history.png" />
The old logo, the new detailed logo and the new simple logo.
</p>
</div>
</article>
<hr>

30
blog/posts/16/index.html
View file

@ -67,6 +67,36 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2015/03/08/new-logo/">New logo for Home Assistant</a>
</h1>
<div class="meta clearfix">
<time datetime="2015-03-08T22:16:10+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> March 8, 2015</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> Less than one minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Organisation</li>
</ul>
</span>
<a class='comments'
href="/blog/2015/03/08/new-logo/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>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, <a href="http://jeremygeltman.com/">Jeremy Geltman</a> has come to the rescue and contributed a brand new logo for Home Assistant.</p>
<p>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).</p>
<p class="img">
<img src="/images/blog/ha-logo-history.png" />
The old logo, the new detailed logo and the new simple logo.
</p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">

62
blog/posts/2/index.html
View file

@ -67,6 +67,41 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/10/06/deprecating-python-3.4-support/">Deprecating Python 3.4 support</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-10-06T00:36:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> October 6, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 1 minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Technology</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/10/06/deprecating-python-3.4-support/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>Starting with our next release, 0.55, we will deprecate Python 3.4 support. The current plan is to remove support for Python 3.4 at the beginning of 2018.</p>
<p>Python 3.5 was released on September 13th, 2015. It has since then become the default Python installation on the stable releases of Debian, Ubuntu, Raspbian and Hassbian. Our other own operating system, Hass.io, is more advanced and is already running the greatly improved Python 3.6.</p>
<p>The jump to Python 3.5 as a minimum version is driven by the Home Assistant core, which is based on asyncio. Starting with Python 3.5, asyncio got improved support in the language with dedicated keywords <code class="highlighter-rouge">async</code> and <code class="highlighter-rouge">await</code>. As this is the proper way of doing async in Python, we’re seeing a move by async libraries to either only support the new syntax from the beginning or dropping support for the Python 3.4 approach. Not moving along means an increased maintenance burden as we cannot use the latest releases of our libraries. Next to that it will prevent our users from being able to leverage the bug fixes and performance improvements that come with Python 3.5.</p>
<h4>Hass.io</h4>
<p>If you’re running Hass.io, you don’t have to do anything. Your system will always stay up to date.</p>
<h4>Hassbian</h4>
<p>If you’re running Hassbian it’s recommended that you make a backup of your configuration files and restore them on a fresh install. Upgrading an existing installation isn’t recommended.</p>
<h4>Windows</h4>
<p>If you’re on Windows, you’re fine as our minimum version for Windows has been 3.5 for a while now.</p>
<h4>Other Debian based systems</h4>
<p>If you’re running a Debian based system, follow <a href="https://linuxconfig.org/raspbian-gnu-linux-upgrade-from-jessie-to-raspbian-stretch-9">these instructions</a> to upgrade.</p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -544,33 +579,6 @@ Screenshot of the new customize editor.
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/08/01/hasspodcast-ep-5/">Home Assistant Podcast #5</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-08-01T00:01:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> August 1, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Phil Hawthorne</span>
<span><i class='icon-time'></i> Less than one minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Media</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/08/01/hasspodcast-ep-5/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>We cover off AppDaemon/HADashboard and all the fun stuff introduced in 0.49 and 0.50.</p>
<p>Show notes available on the <a href="https://hasspodcast.io/ha005/">Home Assistant Podcast Website</a></p>
<p><a href="https://hasspodcast.io/ha005/">Listen online</a></p>
</div>
</article>
<hr>
<div class="pagination">
<a class="btn pull-left" href="/blog/posts/3">&larr; Older</a>
<a class="btn pull-right" href="/blog/">Newer &rarr;</a>

109
blog/posts/3/index.html
View file

@ -67,6 +67,33 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/08/01/hasspodcast-ep-5/">Home Assistant Podcast #5</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-08-01T00:01:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> August 1, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Phil Hawthorne</span>
<span><i class='icon-time'></i> Less than one minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Media</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/08/01/hasspodcast-ep-5/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>We cover off AppDaemon/HADashboard and all the fun stuff introduced in 0.49 and 0.50.</p>
<p>Show notes available on the <a href="https://hasspodcast.io/ha005/">Home Assistant Podcast Website</a></p>
<p><a href="https://hasspodcast.io/ha005/">Listen online</a></p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -483,88 +510,6 @@ Screenshot of a green dashboard
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/06/17/release-47/">0.47: Python Scripts, Sesame Smart Lock, Gitter, Onvif cameras</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-06-17T01:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> June 17, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 16 minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Release-Notes</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/06/17/release-47/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><a href="/components/#version/0.47"><img src="/images/blog/2017-06-0.47/components.png" style="border: 0;box-shadow: none;" /></a></p>
<p>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 <a href="https://home-assistant.io/help/trivia/#first-commit">we’re 1369 days old</a>, which means that roughly every two days a new integration gets added!</p>
<h2><a class="title-link" name="python-scripts" href="#python-scripts"></a> Python Scripts</h2>
<p>The biggest change is a new type of script component: <a href="https://home-assistant.io/components/python_script/">Python scripts</a>. 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 <a href="https://home-assistant.io/components/python_script/">the docs</a> to see how to get started.</p>
<h2><a class="title-link" name="updater" href="#updater"></a> Updater</h2>
<p>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.</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">updater</span><span class="pi">:</span>
<span class="s">include_used_components</span><span class="pi">:</span> <span class="s">true</span>
</code></pre>
</div>
<p>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.</p>
<h2><a class="title-link" name="z-wave" href="#z-wave"></a> Z-Wave</h2>
<p>Z-Wave is also getting a big update in this release. The confusing entity_ids will be on their way out. There is a <a href="https://home-assistant.io/blog/2017/06/15/zwave-entity-ids/">zwave blog post</a> that gives more detail, but the upgrade steps will be as follows:</p>
<ol>
<li>Run Home Assistant as normal and the old IDs will still be used.</li>
<li>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.</li>
<li>Rename entities using the ui card as described in the blog post to avoid conflicts. Restart Home Assistant to observe the changes.</li>
<li>Update all places mentioning IDs (groups, automation, customization, etc.) in configuration.yaml.</li>
<li>Add <code class="highlighter-rouge">new_entity_ids: true</code> to your zwave config.</li>
<li>Restart Home Assistant to run with new IDs.</li>
<li>The old entity IDs will be available in the more info dialog to trace down any remaining errors.</li>
</ol>
<h2><a class="title-link" name="monkey-patching-python-36" href="#monkey-patching-python-36"></a> Monkey Patching Python 3.6</h2>
<p>Some people have noticed that running Home Assistant under Python 3.6 can lead to segfaults. It seems to be related to the <a href="https://github.com/home-assistant/home-assistant/issues/3453">earlier segfault issues</a> that we experienced when we released the asyncio-based core. We thought that those issues would have been fixed when <a href="https://bugs.python.org/issue26617">Python bug 26617</a> was resolved. Although we see less reports compared to the old bug, there are still users <a href="https://github.com/home-assistant/home-assistant/issues/7752">experiencing them</a> (<a href="https://github.com/home-assistant/home-assistant/issues/7752#issuecomment-305100009">gdb stacktrace points at <code class="highlighter-rouge">PyObject_GC_Del()</code></a>).</p>
<p>Since Python 3.6, the Task and Future classes have been moved to C. This gives a nice speed boost but also prevents us from monkey patching the Task class to avoid the segfault. <a href="https://github.com/bbangert">Ben Bangert</a> managed to brew up another monkey patch to stop Python 3.6 from using the C classes, falling back to the Python versions instead. This allows us to apply the original monkey patch again.</p>
<p>Both monkey patches are now active by default starting version 0.47 to avoid our users experiencing segfaults. This comes at a cost of not being able to benefit from all optimizations that were introduced in Python 3.6.</p>
<p>To run without the monkey patch, start Home Assistant with <code class="highlighter-rouge">HASS_NO_MONKEY=1 hass</code>. We will further investigate this issue and try to fix it in a future version of Python.</p>
<h2><a class="title-link" name="release-0471---june-21" href="#release-0471---june-21"></a> Release 0.47.1 - June 21</h2>
<ul>
<li>Fix Vera lights issue #8098 (<a href="https://github.com/tsvi">@tsvi</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8101">#8101</a>) (<a href="https://home-assistant.io/components/light.vera/">light.vera docs</a>)</li>
<li>Fix Dyson async_add_job (<a href="https://github.com/CharlesBlonde">@CharlesBlonde</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8113">#8113</a>) (<a href="https://home-assistant.io/components/fan.dyson/">fan.dyson docs</a>) (<a href="https://home-assistant.io/components/sensor.dyson/">sensor.dyson docs</a>)</li>
<li>Update InfluxDB to handle datetime objects and multiple decimal points (<a href="https://github.com/philhawthorne">@philhawthorne</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8080">#8080</a>) (<a href="https://home-assistant.io/components/influxdb/">influxdb docs</a>)</li>
<li>Fixed iTach command parsing with empty data (<a href="https://github.com/alanfischer">@alanfischer</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8104">#8104</a>) (<a href="https://home-assistant.io/components/remote.itach/">remote.itach docs</a>)</li>
<li>Allow iteration in python_script (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8134">#8134</a>) (<a href="https://home-assistant.io/components/python_script/">python_script docs</a>)</li>
</ul>
<h2><a class="title-link" name="new-platforms" href="#new-platforms"></a> New platforms</h2>
<ul>
<li>Added a Taps Aff binary sensor (<a href="https://github.com/bazwilliams">@bazwilliams</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7880">#7880</a>) (<a href="https://home-assistant.io/components/binary_sensor.tapsaff/">binary_sensor.tapsaff docs</a>) (new-platform)</li>
<li>lock.sesame: New lock platform for Sesame smart locks (<a href="https://github.com/trisk">@trisk</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7873">#7873</a>) (<a href="https://home-assistant.io/components/lock.sesame/">lock.sesame docs</a>) (new-platform)</li>
<li>Etherscan.io sensor (<a href="https://github.com/nkgilley">@nkgilley</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7855">#7855</a>) (<a href="https://home-assistant.io/components/sensor.etherscan/">sensor.etherscan docs</a>) (new-platform)</li>
<li>blockchain.info sensor (<a href="https://github.com/nkgilley">@nkgilley</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7856">#7856</a>) (<a href="https://home-assistant.io/components/sensor.blockchain/">sensor.blockchain docs</a>) (new-platform)</li>
<li>Add Radarr sensor (<a href="https://github.com/tboyce021">@tboyce021</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7318">#7318</a>) (<a href="https://home-assistant.io/components/sensor.radarr/">sensor.radarr docs</a>) (new-platform)</li>
<li>Added buienradar sensor and weather (<a href="https://github.com/mjj4791">@mjj4791</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7592">#7592</a>) (<a href="https://home-assistant.io/components/sensor.buienradar/">sensor.buienradar docs</a>) (<a href="https://home-assistant.io/components/weather.buienradar/">weather.buienradar docs</a>) (new-platform)</li>
<li>Add support for Vanderbilt SPC alarm panels and attached sensors (<a href="https://github.com/mbrrg">@mbrrg</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7663">#7663</a>) (<a href="https://home-assistant.io/components/spc/">spc docs</a>) (<a href="https://home-assistant.io/components/alarm_control_panel.spc/">alarm_control_panel.spc docs</a>) (<a href="https://home-assistant.io/components/binary_sensor.spc/">binary_sensor.spc docs</a>) (new-platform)</li>
<li>Add raspihats switch (<a href="https://github.com/florincosta">@florincosta</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7665">#7665</a>) (<a href="https://home-assistant.io/components/switch.raspihats/">switch.raspihats docs</a>) (new-platform)</li>
<li>Add juicenet platform (<a href="https://github.com/jesserockz">@jesserockz</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7668">#7668</a>) (<a href="https://home-assistant.io/components/juicenet/">juicenet docs</a>) (<a href="https://home-assistant.io/components/sensor.juicenet/">sensor.juicenet docs</a>) (new-platform)</li>
<li>add ripple sensor (<a href="https://github.com/nkgilley">@nkgilley</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7935">#7935</a>) (<a href="https://home-assistant.io/components/sensor.ripple/">sensor.ripple docs</a>) (new-platform)</li>
<li>New component: Python Script (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7950">#7950</a>) (<a href="https://home-assistant.io/components/python_script/">python_script docs</a>) (new-platform)</li>
<li>Nadtcp component (<a href="https://github.com/mwsluis">@mwsluis</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7955">#7955</a>) (<a href="https://home-assistant.io/components/media_player.nadtcp/">media_player.nadtcp docs</a>) (new-platform)</li>
<li>Add Gitter.im sensor (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7998">#7998</a>) (<a href="https://home-assistant.io/components/sensor.gitter/">sensor.gitter docs</a>) (new-platform)</li>
<li>Update mailgun (<a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7984">#7984</a>) (<a href="https://home-assistant.io/components/mailgun/">mailgun docs</a>) (<a href="https://home-assistant.io/components/notify.mailgun/">notify.mailgun docs</a>) (breaking change) (new-platform)</li>
<li>Add Flexit AC climate platform (<a href="https://github.com/Sabesto">@Sabesto</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7871">#7871</a>) (<a href="https://home-assistant.io/components/climate.flexit/">climate.flexit docs</a>) (new-platform)</li>
</ul>
<h2><a class="title-link" name="if-you-need-help" href="#if-you-need-help"></a> If you need help…</h2>
<p>…don’t hesitate to use our very active <a href="https://community.home-assistant.io/">forums</a> or join us for a little <a href="https://discord.gg/c5DvZ4e">chat</a>. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.</p>
<h2><a class="title-link" name="reporting-issues" href="#reporting-issues"></a> Reporting Issues</h2>
<p>Experiencing issues introduced by this release? Please report them in our <a href="https://github.com/home-assistant/home-assistant/issues">issue tracker</a>. Make sure to fill in all fields of the issue template.</p>
<a class="btn pull-right" href="/blog/2017/06/17/release-47/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<div class="pagination">
<a class="btn pull-left" href="/blog/posts/4">&larr; Older</a>
<a class="btn pull-right" href="/blog/posts/2">Newer &rarr;</a>

111
blog/posts/4/index.html
View file

@ -67,6 +67,88 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/06/17/release-47/">0.47: Python Scripts, Sesame Smart Lock, Gitter, Onvif cameras</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-06-17T01:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> June 17, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 16 minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Release-Notes</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/06/17/release-47/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><a href="/components/#version/0.47"><img src="/images/blog/2017-06-0.47/components.png" style="border: 0;box-shadow: none;" /></a></p>
<p>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 <a href="https://home-assistant.io/help/trivia/#first-commit">we’re 1369 days old</a>, which means that roughly every two days a new integration gets added!</p>
<h2><a class="title-link" name="python-scripts" href="#python-scripts"></a> Python Scripts</h2>
<p>The biggest change is a new type of script component: <a href="https://home-assistant.io/components/python_script/">Python scripts</a>. 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 <a href="https://home-assistant.io/components/python_script/">the docs</a> to see how to get started.</p>
<h2><a class="title-link" name="updater" href="#updater"></a> Updater</h2>
<p>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.</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">updater</span><span class="pi">:</span>
<span class="s">include_used_components</span><span class="pi">:</span> <span class="s">true</span>
</code></pre>
</div>
<p>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.</p>
<h2><a class="title-link" name="z-wave" href="#z-wave"></a> Z-Wave</h2>
<p>Z-Wave is also getting a big update in this release. The confusing entity_ids will be on their way out. There is a <a href="https://home-assistant.io/blog/2017/06/15/zwave-entity-ids/">zwave blog post</a> that gives more detail, but the upgrade steps will be as follows:</p>
<ol>
<li>Run Home Assistant as normal and the old IDs will still be used.</li>
<li>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.</li>
<li>Rename entities using the ui card as described in the blog post to avoid conflicts. Restart Home Assistant to observe the changes.</li>
<li>Update all places mentioning IDs (groups, automation, customization, etc.) in configuration.yaml.</li>
<li>Add <code class="highlighter-rouge">new_entity_ids: true</code> to your zwave config.</li>
<li>Restart Home Assistant to run with new IDs.</li>
<li>The old entity IDs will be available in the more info dialog to trace down any remaining errors.</li>
</ol>
<h2><a class="title-link" name="monkey-patching-python-36" href="#monkey-patching-python-36"></a> Monkey Patching Python 3.6</h2>
<p>Some people have noticed that running Home Assistant under Python 3.6 can lead to segfaults. It seems to be related to the <a href="https://github.com/home-assistant/home-assistant/issues/3453">earlier segfault issues</a> that we experienced when we released the asyncio-based core. We thought that those issues would have been fixed when <a href="https://bugs.python.org/issue26617">Python bug 26617</a> was resolved. Although we see less reports compared to the old bug, there are still users <a href="https://github.com/home-assistant/home-assistant/issues/7752">experiencing them</a> (<a href="https://github.com/home-assistant/home-assistant/issues/7752#issuecomment-305100009">gdb stacktrace points at <code class="highlighter-rouge">PyObject_GC_Del()</code></a>).</p>
<p>Since Python 3.6, the Task and Future classes have been moved to C. This gives a nice speed boost but also prevents us from monkey patching the Task class to avoid the segfault. <a href="https://github.com/bbangert">Ben Bangert</a> managed to brew up another monkey patch to stop Python 3.6 from using the C classes, falling back to the Python versions instead. This allows us to apply the original monkey patch again.</p>
<p>Both monkey patches are now active by default starting version 0.47 to avoid our users experiencing segfaults. This comes at a cost of not being able to benefit from all optimizations that were introduced in Python 3.6.</p>
<p>To run without the monkey patch, start Home Assistant with <code class="highlighter-rouge">HASS_NO_MONKEY=1 hass</code>. We will further investigate this issue and try to fix it in a future version of Python.</p>
<h2><a class="title-link" name="release-0471---june-21" href="#release-0471---june-21"></a> Release 0.47.1 - June 21</h2>
<ul>
<li>Fix Vera lights issue #8098 (<a href="https://github.com/tsvi">@tsvi</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8101">#8101</a>) (<a href="https://home-assistant.io/components/light.vera/">light.vera docs</a>)</li>
<li>Fix Dyson async_add_job (<a href="https://github.com/CharlesBlonde">@CharlesBlonde</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8113">#8113</a>) (<a href="https://home-assistant.io/components/fan.dyson/">fan.dyson docs</a>) (<a href="https://home-assistant.io/components/sensor.dyson/">sensor.dyson docs</a>)</li>
<li>Update InfluxDB to handle datetime objects and multiple decimal points (<a href="https://github.com/philhawthorne">@philhawthorne</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8080">#8080</a>) (<a href="https://home-assistant.io/components/influxdb/">influxdb docs</a>)</li>
<li>Fixed iTach command parsing with empty data (<a href="https://github.com/alanfischer">@alanfischer</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8104">#8104</a>) (<a href="https://home-assistant.io/components/remote.itach/">remote.itach docs</a>)</li>
<li>Allow iteration in python_script (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8134">#8134</a>) (<a href="https://home-assistant.io/components/python_script/">python_script docs</a>)</li>
</ul>
<h2><a class="title-link" name="new-platforms" href="#new-platforms"></a> New platforms</h2>
<ul>
<li>Added a Taps Aff binary sensor (<a href="https://github.com/bazwilliams">@bazwilliams</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7880">#7880</a>) (<a href="https://home-assistant.io/components/binary_sensor.tapsaff/">binary_sensor.tapsaff docs</a>) (new-platform)</li>
<li>lock.sesame: New lock platform for Sesame smart locks (<a href="https://github.com/trisk">@trisk</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7873">#7873</a>) (<a href="https://home-assistant.io/components/lock.sesame/">lock.sesame docs</a>) (new-platform)</li>
<li>Etherscan.io sensor (<a href="https://github.com/nkgilley">@nkgilley</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7855">#7855</a>) (<a href="https://home-assistant.io/components/sensor.etherscan/">sensor.etherscan docs</a>) (new-platform)</li>
<li>blockchain.info sensor (<a href="https://github.com/nkgilley">@nkgilley</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7856">#7856</a>) (<a href="https://home-assistant.io/components/sensor.blockchain/">sensor.blockchain docs</a>) (new-platform)</li>
<li>Add Radarr sensor (<a href="https://github.com/tboyce021">@tboyce021</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7318">#7318</a>) (<a href="https://home-assistant.io/components/sensor.radarr/">sensor.radarr docs</a>) (new-platform)</li>
<li>Added buienradar sensor and weather (<a href="https://github.com/mjj4791">@mjj4791</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7592">#7592</a>) (<a href="https://home-assistant.io/components/sensor.buienradar/">sensor.buienradar docs</a>) (<a href="https://home-assistant.io/components/weather.buienradar/">weather.buienradar docs</a>) (new-platform)</li>
<li>Add support for Vanderbilt SPC alarm panels and attached sensors (<a href="https://github.com/mbrrg">@mbrrg</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7663">#7663</a>) (<a href="https://home-assistant.io/components/spc/">spc docs</a>) (<a href="https://home-assistant.io/components/alarm_control_panel.spc/">alarm_control_panel.spc docs</a>) (<a href="https://home-assistant.io/components/binary_sensor.spc/">binary_sensor.spc docs</a>) (new-platform)</li>
<li>Add raspihats switch (<a href="https://github.com/florincosta">@florincosta</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7665">#7665</a>) (<a href="https://home-assistant.io/components/switch.raspihats/">switch.raspihats docs</a>) (new-platform)</li>
<li>Add juicenet platform (<a href="https://github.com/jesserockz">@jesserockz</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7668">#7668</a>) (<a href="https://home-assistant.io/components/juicenet/">juicenet docs</a>) (<a href="https://home-assistant.io/components/sensor.juicenet/">sensor.juicenet docs</a>) (new-platform)</li>
<li>add ripple sensor (<a href="https://github.com/nkgilley">@nkgilley</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7935">#7935</a>) (<a href="https://home-assistant.io/components/sensor.ripple/">sensor.ripple docs</a>) (new-platform)</li>
<li>New component: Python Script (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7950">#7950</a>) (<a href="https://home-assistant.io/components/python_script/">python_script docs</a>) (new-platform)</li>
<li>Nadtcp component (<a href="https://github.com/mwsluis">@mwsluis</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7955">#7955</a>) (<a href="https://home-assistant.io/components/media_player.nadtcp/">media_player.nadtcp docs</a>) (new-platform)</li>
<li>Add Gitter.im sensor (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7998">#7998</a>) (<a href="https://home-assistant.io/components/sensor.gitter/">sensor.gitter docs</a>) (new-platform)</li>
<li>Update mailgun (<a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7984">#7984</a>) (<a href="https://home-assistant.io/components/mailgun/">mailgun docs</a>) (<a href="https://home-assistant.io/components/notify.mailgun/">notify.mailgun docs</a>) (breaking change) (new-platform)</li>
<li>Add Flexit AC climate platform (<a href="https://github.com/Sabesto">@Sabesto</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7871">#7871</a>) (<a href="https://home-assistant.io/components/climate.flexit/">climate.flexit docs</a>) (new-platform)</li>
</ul>
<h2><a class="title-link" name="if-you-need-help" href="#if-you-need-help"></a> If you need help…</h2>
<p>…don’t hesitate to use our very active <a href="https://community.home-assistant.io/">forums</a> or join us for a little <a href="https://discord.gg/c5DvZ4e">chat</a>. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.</p>
<h2><a class="title-link" name="reporting-issues" href="#reporting-issues"></a> Reporting Issues</h2>
<p>Experiencing issues introduced by this release? Please report them in our <a href="https://github.com/home-assistant/home-assistant/issues">issue tracker</a>. Make sure to fill in all fields of the issue template.</p>
<a class="btn pull-right" href="/blog/2017/06/17/release-47/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -457,35 +539,6 @@ If you have a security key set in your Open Z-Wave <code class="highlighter-roug
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/05/05/podcast-init-interview/">Podcast.__init__ interview with Paulus Schoutsen</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-05-05T02:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> May 5, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> Less than one minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Media</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/05/05/podcast-init-interview/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p class="img">
<a href="https://www.podcastinit.com/"><img src="/images/blog/2017-05-podcast-init/podcast_init.png" /></a>
</p>
<p>Earlier this year I was interviewed by Tobias Macey from <a href="https://www.podcastinit.com/">Podcast.__init__</a> about Python and Home Assistant. Just realized that we never shared this on the blog, oops. Here it is, enjoy!</p>
<script class="podigee-podcast-player" src="//cdn.podigee.com/podcast-player/javascripts/podigee-podcast-player.js" data-configuration="https://www.podcastinit.com?podigee_player=205" async=""></script>
</div>
</article>
<hr>
<div class="pagination">
<a class="btn pull-left" href="/blog/posts/5">&larr; Older</a>
<a class="btn pull-right" href="/blog/posts/3">Newer &rarr;</a>

56
blog/posts/5/index.html
View file

@ -67,6 +67,35 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/05/05/podcast-init-interview/">Podcast.__init__ interview with Paulus Schoutsen</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-05-05T02:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> May 5, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> Less than one minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Media</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/05/05/podcast-init-interview/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p class="img">
<a href="https://www.podcastinit.com/"><img src="/images/blog/2017-05-podcast-init/podcast_init.png" /></a>
</p>
<p>Earlier this year I was interviewed by Tobias Macey from <a href="https://www.podcastinit.com/">Podcast.__init__</a> about Python and Home Assistant. Just realized that we never shared this on the blog, oops. Here it is, enjoy!</p>
<script class="podigee-podcast-player" src="//cdn.podigee.com/podcast-player/javascripts/podigee-podcast-player.js" data-configuration="https://www.podcastinit.com?podigee_player=205" async=""></script>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -494,33 +523,6 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/03/28/http-to-mqtt-bridge/">HTTP to MQTT bridge</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-03-28T06:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> March 28, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> petkov</span>
<span><i class='icon-time'></i> three minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/03/28/http-to-mqtt-bridge/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>The idea of creating <a href="https://github.com/petkov/http_to_mqtt">HTTP to MQTT bridge</a> appeared when I was trying to integrate Google Assistant with my Home Assistant after watching <a href="https://youtu.be/087tQ7Ly7f4?t=265">BRUH Automation</a> video. Right now there is no MQTT service available in <a href="https://ifttt.com/about">IFTTT</a>. Existing integration solution uses <a href="https://ifttt.com/maker_webhooks">Maker Webhooks</a> which requires that your Home Assistant instance is publicly accessible, which I think brings some security concerns or simply not always possible to set up.</p>
<p>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 <a href="https://expressjs.com/">Express</a> for the server part and <a href="https://www.npmjs.com/package/mqtt">MQTT.js</a> for the client.</p>
<a class="btn pull-right" href="/blog/2017/03/28/http-to-mqtt-bridge/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<div class="pagination">
<a class="btn pull-left" href="/blog/posts/6">&larr; Older</a>
<a class="btn pull-right" href="/blog/posts/4">Newer &rarr;</a>

54
blog/posts/6/index.html
View file

@ -67,6 +67,33 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/03/28/http-to-mqtt-bridge/">HTTP to MQTT bridge</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-03-28T06:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> March 28, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> petkov</span>
<span><i class='icon-time'></i> three minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/03/28/http-to-mqtt-bridge/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>The idea of creating <a href="https://github.com/petkov/http_to_mqtt">HTTP to MQTT bridge</a> appeared when I was trying to integrate Google Assistant with my Home Assistant after watching <a href="https://youtu.be/087tQ7Ly7f4?t=265">BRUH Automation</a> video. Right now there is no MQTT service available in <a href="https://ifttt.com/about">IFTTT</a>. Existing integration solution uses <a href="https://ifttt.com/maker_webhooks">Maker Webhooks</a> which requires that your Home Assistant instance is publicly accessible, which I think brings some security concerns or simply not always possible to set up.</p>
<p>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 <a href="https://expressjs.com/">Express</a> for the server part and <a href="https://www.npmjs.com/package/mqtt">MQTT.js</a> for the client.</p>
<a class="btn pull-right" href="/blog/2017/03/28/http-to-mqtt-bridge/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -658,33 +685,6 @@ On the close horizon from <a href="https://github.com/Landrash">@Landrash</a> th
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/02/03/babyphone/">Smart Baby Monitor</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-02-03T01:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> February 3, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Pascal Vizeli</span>
<span><i class='icon-time'></i> five minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/02/03/babyphone/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>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 Assistant. 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.</p>
<p>Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.</p>
<a class="btn pull-right" href="/blog/2017/02/03/babyphone/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<div class="pagination">
<a class="btn pull-left" href="/blog/posts/7">&larr; Older</a>
<a class="btn pull-right" href="/blog/posts/5">Newer &rarr;</a>

147
blog/posts/7/index.html
View file

@ -67,6 +67,33 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/02/03/babyphone/">Smart Baby Monitor</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-02-03T01:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> February 3, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Pascal Vizeli</span>
<span><i class='icon-time'></i> five minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/02/03/babyphone/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>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 Assistant. 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.</p>
<p>Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.</p>
<a class="btn pull-right" href="/blog/2017/02/03/babyphone/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -784,126 +811,6 @@ You have to note:
</ul>
<h3><a class="title-link" name="reporting-issues" href="#reporting-issues"></a> Reporting issues</h3>
<p>Experiencing issues introduced by this release? Please report them in our <a href="https://github.com/home-assistant/home-assistant/issues">issue tracker</a>. Make sure to fill in all fields of the issue template.</p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/11/05/hacktoberfest-influxdb-weather/">0.32: Hacktoberfest, InfluxDB sensor, Error reporting, and Weather</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-11-05T03:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> November 05, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter</span>
<span><i class='icon-time'></i> six minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Release-Notes</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/11/05/hacktoberfest-influxdb-weather/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>Another two weeks have passed and we are pleased to present Home Assistant 0.32.</p>
<h3><a class="title-link" name="hacktoberfest" href="#hacktoberfest"></a> Hacktoberfest</h3>
<p>The <a href="https://hacktoberfest.digitalocean.com/">Hacktoberfest</a> 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 👏 .</p>
<h3><a class="title-link" name="improved-error-reporting" href="#improved-error-reporting"></a> Improved error reporting</h3>
<p>This release has improved the reporting when a config validation error occurs. Thanks to <a href="https://github.com/kellerza">@kellerza</a> you will now get a persistent notification added to your UI when this happens.</p>
<h3><a class="title-link" name="asynchronous" href="#asynchronous"></a> Asynchronous</h3>
<p>This release contains the first asynchronous sensor and camera platforms. <a href="https://github.com/pvizeli">@pvizeli</a> and <a href="https://github.com/fabaff">@fabaff</a> ported most of the “internal” sensors to async programming. We hope that you will enjoy the new speed.</p>
<p><a href="https://github.com/balloob">@balloob</a> and <a href="https://github.com/pvizeli">@pvizeli</a> worked a lot on the improvement of the core itself.</p>
<h3><a class="title-link" name="weather-component" href="#weather-component"></a> Weather component</h3>
<p>For a long time we have had a bunch of <a href="https://home-assistant.io/components/#weather">weather sensors</a> but it’s getting better: There is now a <a href="https://home-assistant.io/components/weather/">Weather component</a>. Sorry, not much more to tell right now. The plans are to create a weather UI element and to improve the initial implementation.</p>
<h3><a class="title-link" name="all-changes" href="#all-changes"></a> All changes</h3>
<p><img src="/images/supported_brands/icloud.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/influxdb.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/emby.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/synologydsm.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/garadget_logo.jpg" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/yeelight.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/philips.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/nfandroidtv.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/currencylayer.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/influxdb.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p>
<ul>
<li>Cover: New <a href="https://home-assistant.io/components/garadget/">garadget</a> platform (<a href="https://github.com/JasonCarter80">@JasonCarter80</a>)</li>
<li>Media player: New support for <a href="https://home-assistant.io/components/media_player.emby/">Emby</a> (<a href="https://github.com/mezz64">@mezz64</a>)</li>
<li><a href="https://home-assistant.io/components/litejet/">LiteJet</a> switches and lights support (<a href="https://github.com/joncar">@joncar</a>)</li>
<li>Light: <a href="https://home-assistant.io/components/light.yeelight/">Yeelight</a> Wifi bulbs are now supported (<a href="https://github.com/HydrelioxGitHub">@HydrelioxGitHub</a>)</li>
<li>Media player: <a href="https://home-assistant.io/components/media_player.philips_js/">Philips TVs</a> with jointSPACE API re now supported (<a href="https://github.com/danielperna84">@danielperna84</a>)</li>
<li>Sensor: Support for <a href="https://home-assistant.io/components/sensor.synologydsm/">Synology DSM</a> (<a href="https://github.com/StaticCube">@StaticCube</a>)</li>
<li>Sensor: Monitoring support for <a href="https://home-assistant.io/components/sensor.dovado/">Dovado routers</a> (<a href="https://github.com/molobrakos">@molobrakos</a>)</li>
<li>Sensor: Support for monitoring <a href="https://home-assistant.io/components/sensor.cups/">printers</a> (<a href="https://github.com/fabaff">@fabaff</a>)</li>
<li>Add mochad component (<a href="https://github.com/mtreinish">@mtreinish</a>)</li>
<li>Notify: Added support for <a href="https://home-assistant.io/components/notify.nfandroidtv/">Android TV/FireTV</a> - Sensor: New finance platform <a href="https://home-assistant.io/components/sensor.currencylayer/">CurrencyLayer</a> (<a href="https://github.com/arsaboo">@arsaboo</a>)</li>
<li>Sensor: Support for <a href="https://home-assistant.io/components/sensor.influxdb/">InfluxDB sensors</a> (<a href="https://github.com/bestlibre">@bestlibre</a>)</li>
<li>Sensor: New support <a href="https://home-assistant.io/components/sensor.hddtemp/">HDDTemp sensors</a> (<a href="https://github.com/fabaff">@fabaff</a>)
(<a href="https://github.com/danielperna84">@danielperna84</a>)</li>
<li>Media player: <a href="https://home-assistant.io/components/media_player.sonos/">Sonos</a> improvements incl. timer setting functionality (<a href="https://github.com/bjarniivarsson">@bjarniivarsson</a>, <a href="https://github.com/americanwookie">@americanwookie</a>)</li>
<li>Media player: Discovery support for <a href="https://home-assistant.io/components/media_player.yamaha/">Yamaha</a> (<a href="https://github.com/sdague">@sdague</a>)</li>
<li>Config: Exclude dirs/files prefixed with . (<a href="https://github.com/lwis">@lwis</a>)</li>
<li>HTTP: Migrate WSGI to asyncio (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Configurator: Support for <code class="highlighter-rouge">entity_picture</code> (<a href="https://github.com/armills">@armills</a>)</li>
<li>Core: Configuration validation error prints line numbers (<a href="https://github.com/persandstrom">@persandstrom</a>)</li>
<li>Zoneminder: SSL/TLS support (<a href="https://github.com/Khabi">@Khabi</a>)</li>
<li>Camera: Improvements to <a href="https://home-assistant.io/components/camera.rpi_camera/">RPi camera</a> (<a href="https://github.com/postlund">@postlund</a>)</li>
<li><a href="https://home-assistant.io/components/thingspeak/">ThingSpeak</a> component (<a href="https://github.com/simonszu">@simonszu</a>)</li>
<li>Core: New property <code class="highlighter-rouge">hass.data</code> to store internal data (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Switch: Templating and configurable timeout for <a href="https://home-assistant.io/components/switch.rest/">REST</a> (<a href="https://github.com/aa755">@aa755</a>)</li>
<li>Sensor: New <a href="https://home-assistant.io/components/sensor.random/">random number</a> sensor (<a href="https://github.com/fabaff">@fabaff</a>)</li>
<li>Pilight: <code class="highlighter-rouge">send_delay</code> feature (<a href="https://github.com/janLo">@janLo</a>)</li>
<li>Config: Improvements for <code class="highlighter-rouge">known_devices</code> (<a href="https://github.com/kellerza">@kellerza</a>)</li>
<li>Device tracker: New discovered event (<a href="https://github.com/lwis">@lwis</a>)</li>
<li>Device tracker: Improvements and new features for the Volvo on Call platform (<a href="https://github.com/molobrakos">@molobrakos</a>)</li>
<li>Climate: Use unit of measurement from a Vera device (<a href="https://github.com/pavoni">@pavoni</a>)</li>
<li>Device tracker: <a href="https://home-assistant.io/components/device_tracker.icloud/">iCloud</a> improvements (<a href="https://github.com/Bart274">@Bart274</a>)</li>
<li>Minor features and bug fixes by <a href="https://github.com/fabaff">@fabaff</a>, <a href="https://github.com/kellerza">@kellerza</a>, <a href="https://github.com/robbiet480">@robbiet480</a>, <a href="https://github.com/balloob">@balloob</a>, <a href="https://github.com/DavidLP">@DavidLP</a>, <a href="https://github.com/Bart274">@Bart274</a>, <a href="https://github.com/sdague">@sdague</a>, <a href="https://github.com/mtreinish">@mtreinish</a>, <a href="https://github.com/Khabi">@Khabi</a>, <a href="https://github.com/bbesset">@bbesset</a>, <a href="https://github.com/bestlibre">@bestlibre</a>, <a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/turbokongen">@turbokongen</a>, <a href="https://github.com/devdelay">@devdelay</a>, <a href="https://github.com/molobrakos">@molobrakos</a>, <a href="https://github.com/postlund">@postlund</a>, <a href="https://github.com/wokar">@wokar</a>, <a href="https://github.com/armills">@armills</a>, <a href="https://github.com/arsaboo">@arsaboo</a>, <a href="https://github.com/hartmms">@hartmms</a>, <a href="https://github.com/nsideras">@nsideras</a>, <a href="https://github.com/tbeckha">@tbeckha</a>, and <a href="https://github.com/kirichkov">@kirichkov</a>.</li>
</ul>
<h3><a class="title-link" name="release-0321---november-6" href="#release-0321---november-6"></a> Release 0.32.1 - November 6</h3>
<p>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.</p>
<ul>
<li>Fix Sonos doing I/O inside the event loop (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
<li>Fix Radiotherm doing I/O inside the event loop (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Fix camera MJPEG streams when using HTTP 1.0 (<a href="https://github.com/balloob">@balloob</a>)</li>
</ul>
<h3><a class="title-link" name="release-0322---november-7" href="#release-0322---november-7"></a> Release 0.32.2 - November 7</h3>
<ul>
<li>Move Honeywell I/O out of the event loop (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Use sequential updates for non-async entities to prevent race conditions (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
<li>Fix setting temperature in Celsius on Radiotherm CT50 thermostats (<a href="https://github.com/andyat">@andyat</a>)</li>
<li>Fix PiLight config validation (<a href="https://github.com/DavidLP">@DavidLP</a>)</li>
</ul>
<h3><a class="title-link" name="release-0323---november-11" href="#release-0323---november-11"></a> Release 0.32.3 - November 11</h3>
<ul>
<li>Fix OpenWeather weather platform doing I/O in event loop (<a href="https://github.com/lwis">@lwis</a>)</li>
<li>Fix Alarm.com doing I/O in event loop (<a href="https://github.com/jnewland">@jnewland</a>)</li>
<li>Fix Tellstick doing I/O in event loop (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Fix KNX doing I/O in event loop (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Increase warning threshold for catching platforms that do I/O (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Change pilight systemcode validation (<a href="https://github.com/janLo">@janLo</a>)</li>
<li>Fix Yamaha discovering already configured receivers (<a href="https://github.com/sdague">@sdague</a>)</li>
<li>Fix Sonos from installing dependency each time HA was started (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
<li>Fix Synology camera SSL and error handling (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
<li>Fix Panasonic Viera doing I/O in event loop (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Improve generic camera error handling (<a href="https://github.com/kellerza">@kellerza</a>)</li>
<li>Light - Flux Led Lights: allow specifying mode if light does not support white mode (<a href="https://github.com/DanielHiversen">@DanielHiversen</a>)</li>
<li>Fix Rest switch default template (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
</ul>
<h3><a class="title-link" name="release-0324---november-15" href="#release-0324---november-15"></a> Release 0.32.4 - November 15</h3>
<ul>
<li>Fix device tracker from crashing HASS when a new device was discovered (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>HTTP: Fix X-Forwarded-For feature (<a href="https://github.com/mweinelt">@mweinelt</a>)</li>
</ul>
<h3><a class="title-link" name="misc" href="#misc"></a> Misc</h3>
<p>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.</p>
<ul>
<li><a href="https://home-assistant.io/ecosystem/ios/">iOS</a></li>
<li><a href="https://home-assistant.io/ecosystem/scenegen/">SceneGen</a></li>
</ul>
<h3><a class="title-link" name="breaking-changes" href="#breaking-changes"></a> Breaking changes</h3>
<ul>
<li>The <a href="https://home-assistant.io/components/sensor.yahoo_finance/">Yahoo Finance</a> platform supports now multiple stock. Please adjust your configuration.</li>
<li>Deprecated components <code class="highlighter-rouge">garage_door</code>, <code class="highlighter-rouge">rollershutter</code>, <code class="highlighter-rouge">thermostat</code>, and <code class="highlighter-rouge">hvac</code> have been removed.</li>
<li>The minimum Python version on Windows has been bumped to Python 3.5.</li>
<li>The Insteon Hub integration has been disabled due to a <a href="https://github.com/home-assistant/home-assistant/issues/3811">request from Insteon</a>.</li>
</ul>
<h3><a class="title-link" name="if-you-need-help" href="#if-you-need-help"></a> If you need help…</h3>
<p>…don’t hesitate to use our <a href="https://community.home-assistant.io/">Forum</a> or join us for a little <a href="https://discord.gg/c5DvZ4e">chat</a>. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.</p>
</div>
</article>
<hr>

150
blog/posts/8/index.html
View file

@ -67,6 +67,126 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/11/05/hacktoberfest-influxdb-weather/">0.32: Hacktoberfest, InfluxDB sensor, Error reporting, and Weather</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-11-05T03:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> November 05, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter</span>
<span><i class='icon-time'></i> six minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Release-Notes</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/11/05/hacktoberfest-influxdb-weather/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>Another two weeks have passed and we are pleased to present Home Assistant 0.32.</p>
<h3><a class="title-link" name="hacktoberfest" href="#hacktoberfest"></a> Hacktoberfest</h3>
<p>The <a href="https://hacktoberfest.digitalocean.com/">Hacktoberfest</a> 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 👏 .</p>
<h3><a class="title-link" name="improved-error-reporting" href="#improved-error-reporting"></a> Improved error reporting</h3>
<p>This release has improved the reporting when a config validation error occurs. Thanks to <a href="https://github.com/kellerza">@kellerza</a> you will now get a persistent notification added to your UI when this happens.</p>
<h3><a class="title-link" name="asynchronous" href="#asynchronous"></a> Asynchronous</h3>
<p>This release contains the first asynchronous sensor and camera platforms. <a href="https://github.com/pvizeli">@pvizeli</a> and <a href="https://github.com/fabaff">@fabaff</a> ported most of the “internal” sensors to async programming. We hope that you will enjoy the new speed.</p>
<p><a href="https://github.com/balloob">@balloob</a> and <a href="https://github.com/pvizeli">@pvizeli</a> worked a lot on the improvement of the core itself.</p>
<h3><a class="title-link" name="weather-component" href="#weather-component"></a> Weather component</h3>
<p>For a long time we have had a bunch of <a href="https://home-assistant.io/components/#weather">weather sensors</a> but it’s getting better: There is now a <a href="https://home-assistant.io/components/weather/">Weather component</a>. Sorry, not much more to tell right now. The plans are to create a weather UI element and to improve the initial implementation.</p>
<h3><a class="title-link" name="all-changes" href="#all-changes"></a> All changes</h3>
<p><img src="/images/supported_brands/icloud.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/influxdb.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/emby.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/synologydsm.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/garadget_logo.jpg" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/yeelight.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/philips.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/nfandroidtv.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/currencylayer.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/influxdb.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p>
<ul>
<li>Cover: New <a href="https://home-assistant.io/components/garadget/">garadget</a> platform (<a href="https://github.com/JasonCarter80">@JasonCarter80</a>)</li>
<li>Media player: New support for <a href="https://home-assistant.io/components/media_player.emby/">Emby</a> (<a href="https://github.com/mezz64">@mezz64</a>)</li>
<li><a href="https://home-assistant.io/components/litejet/">LiteJet</a> switches and lights support (<a href="https://github.com/joncar">@joncar</a>)</li>
<li>Light: <a href="https://home-assistant.io/components/light.yeelight/">Yeelight</a> Wifi bulbs are now supported (<a href="https://github.com/HydrelioxGitHub">@HydrelioxGitHub</a>)</li>
<li>Media player: <a href="https://home-assistant.io/components/media_player.philips_js/">Philips TVs</a> with jointSPACE API re now supported (<a href="https://github.com/danielperna84">@danielperna84</a>)</li>
<li>Sensor: Support for <a href="https://home-assistant.io/components/sensor.synologydsm/">Synology DSM</a> (<a href="https://github.com/StaticCube">@StaticCube</a>)</li>
<li>Sensor: Monitoring support for <a href="https://home-assistant.io/components/sensor.dovado/">Dovado routers</a> (<a href="https://github.com/molobrakos">@molobrakos</a>)</li>
<li>Sensor: Support for monitoring <a href="https://home-assistant.io/components/sensor.cups/">printers</a> (<a href="https://github.com/fabaff">@fabaff</a>)</li>
<li>Add mochad component (<a href="https://github.com/mtreinish">@mtreinish</a>)</li>
<li>Notify: Added support for <a href="https://home-assistant.io/components/notify.nfandroidtv/">Android TV/FireTV</a> - Sensor: New finance platform <a href="https://home-assistant.io/components/sensor.currencylayer/">CurrencyLayer</a> (<a href="https://github.com/arsaboo">@arsaboo</a>)</li>
<li>Sensor: Support for <a href="https://home-assistant.io/components/sensor.influxdb/">InfluxDB sensors</a> (<a href="https://github.com/bestlibre">@bestlibre</a>)</li>
<li>Sensor: New support <a href="https://home-assistant.io/components/sensor.hddtemp/">HDDTemp sensors</a> (<a href="https://github.com/fabaff">@fabaff</a>)
(<a href="https://github.com/danielperna84">@danielperna84</a>)</li>
<li>Media player: <a href="https://home-assistant.io/components/media_player.sonos/">Sonos</a> improvements incl. timer setting functionality (<a href="https://github.com/bjarniivarsson">@bjarniivarsson</a>, <a href="https://github.com/americanwookie">@americanwookie</a>)</li>
<li>Media player: Discovery support for <a href="https://home-assistant.io/components/media_player.yamaha/">Yamaha</a> (<a href="https://github.com/sdague">@sdague</a>)</li>
<li>Config: Exclude dirs/files prefixed with . (<a href="https://github.com/lwis">@lwis</a>)</li>
<li>HTTP: Migrate WSGI to asyncio (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Configurator: Support for <code class="highlighter-rouge">entity_picture</code> (<a href="https://github.com/armills">@armills</a>)</li>
<li>Core: Configuration validation error prints line numbers (<a href="https://github.com/persandstrom">@persandstrom</a>)</li>
<li>Zoneminder: SSL/TLS support (<a href="https://github.com/Khabi">@Khabi</a>)</li>
<li>Camera: Improvements to <a href="https://home-assistant.io/components/camera.rpi_camera/">RPi camera</a> (<a href="https://github.com/postlund">@postlund</a>)</li>
<li><a href="https://home-assistant.io/components/thingspeak/">ThingSpeak</a> component (<a href="https://github.com/simonszu">@simonszu</a>)</li>
<li>Core: New property <code class="highlighter-rouge">hass.data</code> to store internal data (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Switch: Templating and configurable timeout for <a href="https://home-assistant.io/components/switch.rest/">REST</a> (<a href="https://github.com/aa755">@aa755</a>)</li>
<li>Sensor: New <a href="https://home-assistant.io/components/sensor.random/">random number</a> sensor (<a href="https://github.com/fabaff">@fabaff</a>)</li>
<li>Pilight: <code class="highlighter-rouge">send_delay</code> feature (<a href="https://github.com/janLo">@janLo</a>)</li>
<li>Config: Improvements for <code class="highlighter-rouge">known_devices</code> (<a href="https://github.com/kellerza">@kellerza</a>)</li>
<li>Device tracker: New discovered event (<a href="https://github.com/lwis">@lwis</a>)</li>
<li>Device tracker: Improvements and new features for the Volvo on Call platform (<a href="https://github.com/molobrakos">@molobrakos</a>)</li>
<li>Climate: Use unit of measurement from a Vera device (<a href="https://github.com/pavoni">@pavoni</a>)</li>
<li>Device tracker: <a href="https://home-assistant.io/components/device_tracker.icloud/">iCloud</a> improvements (<a href="https://github.com/Bart274">@Bart274</a>)</li>
<li>Minor features and bug fixes by <a href="https://github.com/fabaff">@fabaff</a>, <a href="https://github.com/kellerza">@kellerza</a>, <a href="https://github.com/robbiet480">@robbiet480</a>, <a href="https://github.com/balloob">@balloob</a>, <a href="https://github.com/DavidLP">@DavidLP</a>, <a href="https://github.com/Bart274">@Bart274</a>, <a href="https://github.com/sdague">@sdague</a>, <a href="https://github.com/mtreinish">@mtreinish</a>, <a href="https://github.com/Khabi">@Khabi</a>, <a href="https://github.com/bbesset">@bbesset</a>, <a href="https://github.com/bestlibre">@bestlibre</a>, <a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/turbokongen">@turbokongen</a>, <a href="https://github.com/devdelay">@devdelay</a>, <a href="https://github.com/molobrakos">@molobrakos</a>, <a href="https://github.com/postlund">@postlund</a>, <a href="https://github.com/wokar">@wokar</a>, <a href="https://github.com/armills">@armills</a>, <a href="https://github.com/arsaboo">@arsaboo</a>, <a href="https://github.com/hartmms">@hartmms</a>, <a href="https://github.com/nsideras">@nsideras</a>, <a href="https://github.com/tbeckha">@tbeckha</a>, and <a href="https://github.com/kirichkov">@kirichkov</a>.</li>
</ul>
<h3><a class="title-link" name="release-0321---november-6" href="#release-0321---november-6"></a> Release 0.32.1 - November 6</h3>
<p>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.</p>
<ul>
<li>Fix Sonos doing I/O inside the event loop (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
<li>Fix Radiotherm doing I/O inside the event loop (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Fix camera MJPEG streams when using HTTP 1.0 (<a href="https://github.com/balloob">@balloob</a>)</li>
</ul>
<h3><a class="title-link" name="release-0322---november-7" href="#release-0322---november-7"></a> Release 0.32.2 - November 7</h3>
<ul>
<li>Move Honeywell I/O out of the event loop (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Use sequential updates for non-async entities to prevent race conditions (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
<li>Fix setting temperature in Celsius on Radiotherm CT50 thermostats (<a href="https://github.com/andyat">@andyat</a>)</li>
<li>Fix PiLight config validation (<a href="https://github.com/DavidLP">@DavidLP</a>)</li>
</ul>
<h3><a class="title-link" name="release-0323---november-11" href="#release-0323---november-11"></a> Release 0.32.3 - November 11</h3>
<ul>
<li>Fix OpenWeather weather platform doing I/O in event loop (<a href="https://github.com/lwis">@lwis</a>)</li>
<li>Fix Alarm.com doing I/O in event loop (<a href="https://github.com/jnewland">@jnewland</a>)</li>
<li>Fix Tellstick doing I/O in event loop (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Fix KNX doing I/O in event loop (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Increase warning threshold for catching platforms that do I/O (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Change pilight systemcode validation (<a href="https://github.com/janLo">@janLo</a>)</li>
<li>Fix Yamaha discovering already configured receivers (<a href="https://github.com/sdague">@sdague</a>)</li>
<li>Fix Sonos from installing dependency each time HA was started (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
<li>Fix Synology camera SSL and error handling (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
<li>Fix Panasonic Viera doing I/O in event loop (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Improve generic camera error handling (<a href="https://github.com/kellerza">@kellerza</a>)</li>
<li>Light - Flux Led Lights: allow specifying mode if light does not support white mode (<a href="https://github.com/DanielHiversen">@DanielHiversen</a>)</li>
<li>Fix Rest switch default template (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
</ul>
<h3><a class="title-link" name="release-0324---november-15" href="#release-0324---november-15"></a> Release 0.32.4 - November 15</h3>
<ul>
<li>Fix device tracker from crashing HASS when a new device was discovered (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>HTTP: Fix X-Forwarded-For feature (<a href="https://github.com/mweinelt">@mweinelt</a>)</li>
</ul>
<h3><a class="title-link" name="misc" href="#misc"></a> Misc</h3>
<p>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.</p>
<ul>
<li><a href="https://home-assistant.io/ecosystem/ios/">iOS</a></li>
<li><a href="https://home-assistant.io/ecosystem/scenegen/">SceneGen</a></li>
</ul>
<h3><a class="title-link" name="breaking-changes" href="#breaking-changes"></a> Breaking changes</h3>
<ul>
<li>The <a href="https://home-assistant.io/components/sensor.yahoo_finance/">Yahoo Finance</a> platform supports now multiple stock. Please adjust your configuration.</li>
<li>Deprecated components <code class="highlighter-rouge">garage_door</code>, <code class="highlighter-rouge">rollershutter</code>, <code class="highlighter-rouge">thermostat</code>, and <code class="highlighter-rouge">hvac</code> have been removed.</li>
<li>The minimum Python version on Windows has been bumped to Python 3.5.</li>
<li>The Insteon Hub integration has been disabled due to a <a href="https://github.com/home-assistant/home-assistant/issues/3811">request from Insteon</a>.</li>
</ul>
<h3><a class="title-link" name="if-you-need-help" href="#if-you-need-help"></a> If you need help…</h3>
<p>…don’t hesitate to use our <a href="https://community.home-assistant.io/">Forum</a> or join us for a little <a href="https://discord.gg/c5DvZ4e">chat</a>. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.</p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -1017,36 +1137,6 @@ So, part 1 of <a href="/blog/2016/07/28/esp8266-and-micropython-part1/">ESP8266
<li>Fix missing attributes on the climate and HVAC more info cards (<a href="https://github.com/home-assistant/home-assistant-polymer/commit/7e455e2be1cb7cc4f55628b063019bea548a3182">7e455e2</a>) - (<a href="https://github.com/robbiet480">@robbiet480</a>)</li>
<li>Add a default icon for the fan component (<a href="https://github.com/home-assistant/home-assistant-polymer/pull/101">#101</a>) - (<a href="https://github.com/robbiet480">@robbiet480</a>)</li>
</ul>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/08/19/github-style-calendar-heatmap-of-device-data/">Github-style calendar heatmap of device data</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-08-19T06:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> August 19, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter</span>
<span><i class='icon-time'></i> Less than one minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
<li>IoT-Data</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/08/19/github-style-calendar-heatmap-of-device-data/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>Thanks to <a href="https://github.com/kireyeu">Anton Kireyeu</a> we are able to present another awesome <a href="https://jupyter.org/">Jupyter notebook</a>. 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 <a href="https://en.wikipedia.org/wiki/Heat_map">heatmap</a>. If there are more commits, it’s getting hotter. The latest <a href="http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/DataExploration-2/DataExploration-2.ipynb">notebook</a> is capable to do the same thing for your devices. To be more precise, for the hours your devices are home.</p>
<p class="img">
<img src="/images/blog/2016-08-data-exploration/heatmap.png" />
Heatmap
</p>
</div>
</article>
<hr>

57
blog/posts/9/index.html
View file

@ -67,6 +67,36 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/08/19/github-style-calendar-heatmap-of-device-data/">Github-style calendar heatmap of device data</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-08-19T06:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> August 19, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter</span>
<span><i class='icon-time'></i> Less than one minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
<li>IoT-Data</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/08/19/github-style-calendar-heatmap-of-device-data/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>Thanks to <a href="https://github.com/kireyeu">Anton Kireyeu</a> we are able to present another awesome <a href="https://jupyter.org/">Jupyter notebook</a>. 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 <a href="https://en.wikipedia.org/wiki/Heat_map">heatmap</a>. If there are more commits, it’s getting hotter. The latest <a href="http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/DataExploration-2/DataExploration-2.ipynb">notebook</a> is capable to do the same thing for your devices. To be more precise, for the hours your devices are home.</p>
<p class="img">
<img src="/images/blog/2016-08-data-exploration/heatmap.png" />
Heatmap
</p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -487,33 +517,6 @@ One of the graphs created with this tutorial.
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/07/06/pocketchip-running-home-assistant/">PocketCHIP running Home Assistant</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-07-06T05:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> July 06, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter</span>
<span><i class='icon-time'></i> two minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/07/06/pocketchip-running-home-assistant/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><img src="/images/blog/2016-07-pocketchip/pocketchip-logo.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;" width="200" />
Over a year ago I participated in the <a href="https://www.kickstarter.com/projects/1598272670/chip-the-worlds-first-9-computer/description">kickstarter campaign</a> for “CHIP - The World’s First Nine Dollar Computer” by <a href="https://www.nextthing.co/">Next Thing Co.</a>. 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…</p>
<a class="btn pull-right" href="/blog/2016/07/06/pocketchip-running-home-assistant/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<div class="pagination">
<a class="btn pull-left" href="/blog/posts/10">&larr; Older</a>
<a class="btn pull-right" href="/blog/posts/8">Newer &rarr;</a>