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

Site updated at 2017-12-17 16:27:07 UTC

Browse source
This commit is contained in:
Travis CI 2017-12-17 16:27:07 +00:00
parent 4e546d5869
commit db3021af91
919 changed files with 15842 additions and 3639 deletions
Download patch file Download diff file Expand all files Collapse all files

263
blog/posts/6/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/04/24/hardware-contest-2017/">Hardware Contest 2017</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-04-24T06:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> April 24, 2017</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>Community</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/04/24/hardware-contest-2017/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>We have four submissions for our <a href="https://home-assistant.io/blog/2017/04/01/thomas-krenn-award/">Hardware Contest 2017</a>.</p>
<ul>
<li><a href="https://community.home-assistant.io/t/entry-for-hardware-contest-part-of-iot-course/14827">Part of IoT-course</a></li>
<li><a href="https://community.home-assistant.io/t/entry-automating-a-nursing-home/14872">Automating a nursing home!</a></li>
<li><a href="https://community.home-assistant.io/t/entry-dedicated-hardware-for-coding-testing-building-and-contributing-to-home-assistant/15515">Dedicated hardware for coding, testing, building, and contributing to Home Assistant</a></li>
<li><a href="https://community.home-assistant.io/t/entry-hassio-home-assistant-hub-for-dummies/16037">HassIO - Home Assistant hub for dummies</a></li>
</ul>
<p>The voting is now open. To keep things simple are we using the voting feature of the <a href="https://community.home-assistant.io/c/contest-2017">forum</a>. Vote for your choices.</p>
<p>End of the voting period: April, 30 2017 - 23.59 UTC</p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/04/22/ikea-tradfri-spotify/">Home Assistant 0.43: IKEA Trådfri, Spotify and our iOS app is live</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-04-22T01:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> April 22, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 14 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/04/22/ikea-tradfri-spotify/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><a href="/components/#added_in_current_version"><img src="/images/blog/2017-04-0.43/components.png" style="border: 0;box-shadow: none;" /></a></p>
<p>Oooh yeah. It’s time for 0.43 and this is going to be a killer release. For the people that have been following on social media, you might have noticed that <a href="/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/">we got pretty excited about the new IKEA Trådfri line up</a>. And so we are very happy to announce that thanks to the work by <a href="https://github.com/ggravlingen">@ggravlingen</a>, <a href="https://github.com/MartinHjelmare">@MartinHjelmare</a> and myself that this will be the first release to support the IKEA light bulbs. Home Assistant will automatically detect the gateway on your network and after following the instructions, allow you to control your lights.</p>
<p class="img">
<img src="/images/blog/2017-04-tradfri/discovery.png" />
After automatic discovery, Home Assistant will ask the user to finish pairing with the gateway.
</p>
<p>And in case you have missed the other big news: <a href="https://github.com/robbiet480">@robbiet480</a> released the <a href="/blog/2017/04/15/ios/">first version of our iOS app</a>! It took a little over a year but it offers some great ways to make your iDevice work with Home Assistant. Big congrats to Robbie for shipping! As with our other parts, the app is open-sourced under APACHE 2 and contributors are welcome. <a href="https://github.com/home-assistant/home-assistant-ios">Check it out.</a></p>
<p>A big shout out this release to <a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> for his constant stream of great contributions to Home Assistant. The first contribution was back in October 2015 and since then <a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> has been responsible for many platforms and bug fixes including the Spotify platform this release. Thanks <a href="https://github.com/happyleavesaoc">@happyleavesaoc</a>, you’re a great example of what makes our community awesome.</p>
<p>The new Spotify integration is based on the new Spotify Connect Playback API. It supports playback, album art and switching which Spotify device you’re controlling.</p>
<p>Also note that you have till the end of the weekend to <a href="https://community.home-assistant.io/c/contest-2017">submit an application</a> to our giveaway of low energy servers which we got when <a href="/blog/2017/04/01/thomas-krenn-award/">we won the Thomas Krenn award 2017</a>. <a href="https://community.home-assistant.io/c/contest-2017">Go apply!</a></p>
<h2><a class="title-link" name="new-platforms" href="#new-platforms"></a> New Platforms</h2>
<ul>
<li>MaryTTS platform (<a href="https://github.com/johanpalmqvist">@johanpalmqvist</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6988">#6988</a>) (<a href="/components/tts.marytts/">tts.marytts docs</a>) (new-platform)</li>
<li>Telegram bot component (incl. webhook and polling platform) (<a href="https://github.com/sander76">@sander76</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6913">#6913</a>) (<a href="https://home-assistant.io/components/telegram_bot/">telegram_bot docs</a>) (<a href="https://home-assistant.io/components/telegram_bot.polling/">telegram_bot.polling docs</a>) (<a href="https://home-assistant.io/components/telegram_bot.webhooks/">telegram_bot.webhooks docs</a>) (breaking change) (new-platform)</li>
<li>Support fo map data from Neato (<a href="https://github.com/turbokongen">@turbokongen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6939">#6939</a>) (<a href="/components/neato/">neato docs</a>) (<a href="/components/camera.neato/">camera.neato docs</a>) (<a href="/components/sensor.neato/">sensor.neato docs</a>) (new-platform)</li>
<li>Support for IKEA Trådfri (<a href="https://github.com/ggravlingen">@ggravlingen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7074">#7074</a>) (<a href="/components/light.tradfri/">light.tradfri docs</a>) (new-platform)</li>
<li>MQTT camera (<a href="https://github.com/MrMep">@MrMep</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7092">#7092</a>) (<a href="/components/camera.mqtt/">camera.mqtt docs</a>) (new-platform)</li>
<li>LIFX Cloud scene support (<a href="https://github.com/amelchio">@amelchio</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7124">#7124</a>) (<a href="/components/scene.lifx_cloud/">scene.lifx_cloud docs</a>) (new-platform)</li>
<li>Spotify media player (<a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6980">#6980</a>) (<a href="/components/media_player.spotify/">media_player.spotify docs</a>) (new-platform)</li>
<li>JSON MQTT Device tracker (<a href="https://github.com/MrMep">@MrMep</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7055">#7055</a>) (new-platform)</li>
<li>Opensky sensor (<a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7061">#7061</a>) (<a href="/components/sensor.opensky/">sensor.opensky docs</a>) (new-platform)</li>
<li>Ping binary sensor (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7052">#7052</a>) (<a href="/components/binary_sensor.ping/">binary_sensor.ping docs</a>) (new-platform)</li>
<li>myStrom Wifi Bulbs (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7161">#7161</a>) (<a href="/components/light.mystrom/">light.mystrom docs</a>) (new-platform)</li>
</ul>
<a class="btn pull-right" href="/blog/2017/04/22/ikea-tradfri-spotify/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -365,187 +447,6 @@
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/03/11/repurpose-any-android-phone-as-ip-camera/">Home Assistant 0.40: Turn any Android phone into an IP Webcam</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-03-11T08:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> March 11, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 10 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/03/11/repurpose-any-android-phone-as-ip-camera/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><a href="/components/#added_in_current_version"><img src="/images/blog/2017-03-0.40/social.png" style="border: 0;box-shadow: none;" /></a></p>
<p>It’s time for version 0.40 already! For this version, the main focus was on performance and bug fixes. Big thanks to <a href="https://github.com/pvizeli">@pvizeli</a> for driving this effort. Startup is now super fast. We have also continued with adding warnings for components and platforms that are slowing down Home Assistant.</p>
<p>Some people have interpreted our recent added warnings as if 0.39 introduced the issues that caused the warning. This is not the case, the platforms and components have been misbehaving for a while but now we are adding warnings so we are able to track down the culprits.</p>
<p>Before we continue talking about all the improvements in this release I want to take a moment to thank a few people from the Home Assistant community that are fundamental to the success of Home Assistant. Big thanks to <a href="https://github.com/dale3h">@dale3h</a>, <a href="https://github.com/CCOSTAN">@CCOSTAN</a>, <a href="https://github.com/skalavala">@skalavala</a>, <a href="https://github.com/rrubin0">@rrubin0</a>, <a href="https://github.com/brahmafear">@brahmafear</a>, <a href="https://github.com/bassclarinetl2">@bassclarinetl2</a>, and <a href="https://github.com/torn8o">@torn8o</a>! These are all people that hang out in our <a href="https://discord.gg/c5DvZ4e">main chat channel</a> and help new users get started and help existing users when running into trouble. Home Assistant would not be there without all the effort you put in! 🙇</p>
<p>And that our community kicks ass is also shown in the numbers. We have already raised together over $700 for the <a href="https://www.eff.org">EFF</a> via the sale of <a href="https://home-assistant.io/blog/2017/02/22/home-assistant-tshirts-have-arrived/">our t-shirts</a>! All of you rock! Another number worth mentioning is that this release brings us passed 600 integrations for Home Assistant. All of you rock, again!</p>
<h2>Z-Wave is now threadsafe</h2>
<p><a href="https://github.com/andrey-git">@andrey-git</a> has spend a lot of time to make Z-Wave perform better. It should no longer cause Home Assistant to run slower or raise warnings about the timer getting out of sync.</p>
<h2>Update on the MQTT Out of Memory errors in 0.39</h2>
<p>MQTT started causing “Out of Memory” errors for some people on a Raspberry Pi. We have been able to track this down to Raspberry Pis that are using an older firmware. If you are experiencing this issue, please <a href="https://github.com/Hexxeh/rpi-update#installing">upgrade your firmware using <code class="highlighter-rouge">rpi-update</code></a>.</p>
<h2>Turn any Android phone into an IP Camera</h2>
<p>With the new support for <a href="/components/android_ip_webcam/">IP Webcam</a> added by <a href="https://github.com/robbiet480">@robbiet480</a> and <a href="https://github.com/pvizeli">@pvizeli</a> you are now able to re-purpose any Android phone to become a multifunctional IP webcam. Some of the cool things that you can do:</p>
<ul>
<li>Integrate the Android device camera</li>
<li>Binary sensor when motion is detected</li>
<li>Sensors to expose the device sensors, including pressure, sound, battery, light</li>
<li>Control device features like the GPS, night vision and camera flash</li>
</ul>
<p class="img">
<img src="/images/blog/2017-03-0.40/ipwebcam.png" />
Screenshot of all the different functionality the IP webcam integration offers.
</p>
<h2>Other Highlights</h2>
<ul>
<li>Support added for Austrian weather using Zamg weather data (<a href="https://github.com/Zac-HD">@Zac-HD</a>)</li>
<li>Ring.com video doorbell integration added (<a href="https://github.com/tchellomello">@tchellomello</a>)</li>
<li>Blink Home Security Camera support added (<a href="https://github.com/fronzbot">@fronzbot</a>)</li>
<li>AppleTV has been converted to push data to Home Assistant instead of us having to poll (<a href="https://github.com/postlund">@postlund</a>)</li>
</ul>
<h2>Breaking changes</h2>
<ul>
<li>Vera entity ids have changed. This is a one time change to migrate to a model that will prevent future conflicts.</li>
<li>The Twilio notify platforms now have to be configured via the twilio component.</li>
</ul>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">twilio</span><span class="pi">:</span>
<span class="s">account_sid</span><span class="pi">:</span> <span class="s2">"</span><span class="s">abc"</span>
<span class="s">auth_token</span><span class="pi">:</span> <span class="s2">"</span><span class="s">xyz"</span>
</code></pre>
</div>
<ul>
<li>If you are using async custom components, the passed in <code class="highlighter-rouge">async_add_devices</code> method is now a callback instead of a coroutine function.</li>
</ul>
<h3>If you need help…</h3>
<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>
<h3>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>
<h3><a class="title-link" name="release-0401---march-16" href="#release-0401---march-16"></a> Release 0.40.1 - March 16</h3>
<ul>
<li>Fix wake_on_lan ping with None as host (<a href="https://github.com/iamtpage">@iamtpage</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6532">#6532</a>)</li>
<li>Don’t start the push updater if the Apple TV is ‘off’ (<a href="https://github.com/jnewland">@jnewland</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6552">#6552</a>)</li>
<li>Fix for the case of zwave value used in several devices. (<a href="https://github.com/andrey-git">@andrey-git</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6577">#6577</a>)</li>
<li>Fix hydroquebec (<a href="https://github.com/titilambert">@titilambert</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6574">#6574</a>)</li>
<li>Update pyecobee version to 0.0.7 (<a href="https://github.com/dale3h">@dale3h</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6593">#6593</a>)</li>
<li>Update SMA solar sensor to work with the new add_devices callback (<a href="https://github.com/kellerza">@kellerza</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6602">#6602</a>)</li>
<li>since knx_2_float can’t handle 0, bypass converting 0 value from knx to float (<a href="https://github.com/goofz">@goofz</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6626">#6626</a>)</li>
<li>Fix Osram Lightify colors (<a href="https://github.com/deisi">@deisi</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6598">#6598</a>)</li>
<li>Bugfix RFLINK remove group (<a href="https://github.com/pvizeli">@pvizeli</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6580">#6580</a>)</li>
</ul>
<h3><a class="title-link" name="release-0402---march-22" href="#release-0402---march-22"></a> Release 0.40.2 - March 22</h3>
<p>Hot fix release to fix dependency issues. More detailed information about the issue in <a href="/blog/2017/03/22/broken-dependencies/">this blog post</a>.</p>
<ul>
<li>Prevent dependencies that are installed on demand from installing different versions of core dependencies (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6738">#6738</a>)</li>
<li>Upgrade PyChromecast to silent some benign errors (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6702">#6702</a>)</li>
</ul>
<a class="btn pull-right" href="/blog/2017/03/11/repurpose-any-android-phone-as-ip-camera/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/02/25/config-panel-and-state-restoration/">0.39: Configuration panel, state restoration and improved docs</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-02-25T08:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> February 25, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> nine 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/02/25/config-panel-and-state-restoration/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>It’s time for 0.39 and this release has some amazing new features!</p>
<p><a href="/components/#added_in_current_version"><img src="/images/blog/2017-02-0.39/social.png" style="border: 0;box-shadow: none;" /></a></p>
<h2>T-Shirts</h2>
<p>First off, in case you haven’t seen it yet: <a href="https://home-assistant.io/blog/2017/02/22/home-assistant-tshirts-have-arrived/">we have t-shirts</a> now and they are beautiful. All proceeds from the shirts will be donated to the Electronic Frontier Foundation. The first three days all of you have already raised $400! Still waiting for Teespring to get back to me so stay tuned for the EU store.</p>
<h2>Configuration panel</h2>
<p>Yep, you read that right. We have a configuration panel. It’s just the first of many small steps. Putting in a foundation is important and gives us something to iterate on.</p>
<p>To start, we have three simple configuration panels:</p>
<ul>
<li>Core: allows you to validate config, reload core/group/automation config and restart/stop Home Assistant</li>
<li>Group: allows you to rename groups, change type between group/view and reorder entities.</li>
<li>Z-Wave: allows you to set device specific configuration settings</li>
</ul>
<p class="img">
<img src="/images/blog/2017-02-0.39/config.png" />
Screenshot of our new configuration panel.
</p>
<p>As a security measure, the configuration panel will need to be activated in the config file to be activated. This can be done by adding the following to your <code class="highlighter-rouge">configuration.yaml</code>:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">config</span><span class="pi">:</span>
</code></pre>
</div>
<p>Using our configuration panels will require you to structure your groups and Z-Wave device config according to how the configuration panel expects it. This is on purpose as it we will not be aiming to build a system that supports both our extended set of configuration extend hooks and our configuration panels. It’s one or the other.</p>
<p>To activate them in your config, create empty files <code class="highlighter-rouge">groups.yaml</code> and <code class="highlighter-rouge">zwave_device_config.yaml</code> in your config dir and add the following entries to your config:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">group</span><span class="pi">:</span> <span class="kt">!include</span> <span class="s">groups.yaml</span>
<span class="s">zwave</span><span class="pi">:</span>
<span class="s">device_config</span><span class="pi">:</span> <span class="kt">!include</span> <span class="s">zwave_device_config.yaml</span>
</code></pre>
</div>
<p><em>Note that this is the first release. Things will be missing, things might be broken.</em></p>
<h2>Reorganized documentation</h2>
<p>Thanks to <a href="https://github.com/fabaff">Fabian</a> we have a great re-organized documentation. Is it perfect yet? No. But we are getting close. We put a lot of focus on making sure the Raspberry Pi is the main focus of our getting started. The other instructions are still available, just not as part of the main getting started.</p>
<h2>State restoration</h2>
<p>Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. <a href="https://github.com/kellerza">Johann</a> has added the foundation for state restoration to Home Assistant. For the initial release support has been added to <code class="highlighter-rouge">input_select</code> and <code class="highlighter-rouge">input_boolean</code> components. We will be adding this to more integrations in the future.</p>
<h2>Breaking changes to customize and Z-Wave “customize”</h2>
<p>A couple of releases ago we introduced a new way of doing <code class="highlighter-rouge">customize</code>. It became a list that allowed different ways of matching the config to the entity.</p>
<p>We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn’t like config panels?</p>
<p>So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.</p>
<p><a href="https://jsfiddle.net/balloob/d2e56q6f/74/"><strong>Update: the online tool can be found here.</strong></a></p>
<h4>Customize has been reverted to it’s original config</h4>
<p>The old customize is back. The options to match by domain or using glob have been moved to it’s own options. It will now look like this:</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">light.kitchen</span><span class="pi">:</span>
<span class="s">hidden</span><span class="pi">:</span> <span class="s">true</span>
<span class="s">customize_domain</span><span class="pi">:</span>
<span class="s">light</span><span class="pi">:</span>
<span class="s">icon</span><span class="pi">:</span> <span class="s">mdi:home</span>
<span class="s">customize_glob</span><span class="pi">:</span>
<span class="s2">"</span><span class="s">light.kitchen_*"</span><span class="pi">:</span>
<span class="s">icon</span><span class="pi">:</span> <span class="s">mid:description</span>
</code></pre>
</div>
<h4>Z-Wave customize is now device config</h4>
<p>Ever wondered why the Z-Wave customize was called customize? Yeah, so did we. So when migrating this to the new config format, we decided to upgrade the name too:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">zwave</span><span class="pi">:</span>
<span class="s">device_config</span><span class="pi">:</span>
<span class="s">light.kitchen</span><span class="pi">:</span>
<span class="s">ignored</span><span class="pi">:</span> <span class="s">true</span>
<span class="s">device_config_domain</span><span class="pi">:</span>
<span class="s">light</span><span class="pi">:</span>
<span class="s">polling_intensity</span><span class="pi">:</span> <span class="s">2</span>
<span class="s">device_config_glob</span><span class="pi">:</span>
<span class="s2">"</span><span class="s">light.kitchen_*"</span><span class="pi">:</span>
<span class="s">polling_intensity</span><span class="pi">:</span> <span class="s">0</span>
</code></pre>
</div>
<h2>Speed improvements</h2>
<p>And a final shout out to <a href="https://github.com/pvizeli">Pascal</a>. He keeps improving the performance of components and platforms all over Home Assistant.</p>
<a class="btn pull-right" href="/blog/2017/02/25/config-panel-and-state-restoration/#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>