<p>First off, in case you haven’t seen it yet: <ahref="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>
<pclass="img">
<imgsrc="/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 <codeclass="highlighter-rouge">configuration.yaml</code>:</p>
<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 <codeclass="highlighter-rouge">groups.yaml</code> and <codeclass="highlighter-rouge">zwave_device_config.yaml</code> in your config dir and add the following entries to your config:</p>
<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 <ahref="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. <ahref="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 to <codeclass="highlighter-rouge">input_select</code> and <codeclass="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 <codeclass="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>
<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>
<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>
<p>And a final shout out to <ahref="https://github.com/pvizeli">Pascal</a>. He keeps improving the performance of components and platforms all over Home Assistant.</p>
<li>Added <ahref="https://home-assistant.io/components/media_player.openhome/">Openhome</a> support (<ahref="https://github.com/bazwilliams">@bazwilliams</a>)</li>
<li><ahref="https://home-assistant.io/components/media_player.gstreamer/">Gstreamer</a> media player (<ahref="https://github.com/happyleavesaoc">@happyleavesaoc</a>)</li>
<li>Support for the <ahref="https://home-assistant.io/components/climate.oem/">Open Energy Monitor Thermostat</a> (<ahref="https://github.com/Cadair">@Cadair</a>)</li>
<li>Add platform for <ahref="https://home-assistant.io/components/light.yeelight-sunflower">Yeelight Sunflower lights</a> (<ahref="https://github.com/lindsaymarkward">@lindsaymarkward</a>)</li>
<li>Support for <ahref="https://home-assistant.io/components/sensor.pocketcasts/">Pocket Casts</a> (<ahref="https://github.com/molobrakos">@molobrakos</a>)</li>
<li><ahref="https://home-assistant.io/components/volvooncall/">VolvoOnCall</a> component with support for sensors, heater and lock (<ahref="https://github.com/molobrakos">@molobrakos</a>)</li>
<li>Add <ahref="https://home-assistant.io/components/notify.pushsafer/">pushsafer.com</a> notification service (<ahref="https://github.com/appzer">@appzer</a>)</li>
<li><ahref="https://home-assistant.io/components/media_player.kodi/">Websocket push</a> notifications for Kodi (<ahref="https://github.com/armills">@armills</a>)</li>
<li>New component ‘insteon_plm’ and related platforms (<ahref="https://github.com/nugget">@nugget</a>)</li>
<li>Tellduslive: Don’t thow exception if connection to server is lost (<ahref="https://github.com/molobrakos">@molobrakos</a>)</li>
<li>Core: Convert config.components to a set (<ahref="https://github.com/balloob">@balloob</a>)</li>
<li>Media Player - Apple TV: Handle connection errors when connecting to Apple TVs, re-use aiohttp session , add fake support for turn on/off (<ahref="https://github.com/postlund">@postlund</a>)</li>
<li>Zoneminder: Refactoring and JSON decode error handling (<ahref="https://github.com/pschmitt">@pschmitt</a>)</li>
<li>Recorder: Add tests for full schema migration, limit to session scope (<ahref="https://github.com/armills">@armills</a>)</li>
<li>Device tracker - Tado: Add support for multiple devices to Tado device tracker (<ahref="https://github.com/markoudev">@markoudev</a>)</li>
<li>Z-Wave: Fix zwave helper getter not to fail on some None results. (<ahref="https://github.com/andrey-git">@andrey-git</a>)</li>
<li>Core: <codeclass="highlighter-rouge">sensor_class</code> migrate to <codeclass="highlighter-rouge">device_class</code> (<ahref="https://github.com/armills">@armills</a>)</li>
<li>Sensor - Amcrest: Avoid traceback for Amcrest cameras/firmware that does not have the software_information API call (<ahref="https://github.com/tchellomello">@tchellomello</a>)</li>
<li>Media Player - MPD: Adds play URL support to mpd (<ahref="https://github.com/jjmontesl">@jjmontesl</a>)</li>
<li>Logbook: Component set add using OR (<ahref="https://github.com/kellerza">@kellerza</a>)</li>
<li>Config: Add config component and hassbian example panel (<ahref="https://github.com/balloob">@balloob</a>)</li>
<li>Proximity: Fixed proximity zone incorrectly using name instead of zone setting (<ahref="https://github.com/jjmontesl">@jjmontesl</a>)</li>
<li>Z-Wave: Add device_class support to cover component (<ahref="https://github.com/armills">@armills</a>)</li>
<li>Config: Add check_config API (<ahref="https://github.com/balloob">@balloob</a>)</li>
<li>Media player: Add media_image to media_player component (<ahref="https://github.com/postlund">@postlund</a>)</li>
<li>Sensor- Vasttrafik.py: vasttrafik: update token on read error (<ahref="https://github.com/persandstrom">@persandstrom</a>)</li>
<li>History: Allow printing the number of states returned by history and time it took to extract and add day (<ahref="https://github.com/andrey-git">@andrey-git</a>)</li>
<li>MQTT: Enable sensor for discovery (<ahref="https://github.com/fabaff">@fabaff</a>)</li>
<li>Light - Limitlessled: Added limitlessled support for bridge v6 and RGBWW bulbs. (<ahref="https://github.com/soldag">@soldag</a>)</li>
<li>Config - Hassbian: Update hassbian component with real output (<ahref="https://github.com/balloob">@balloob</a>)</li>
<li>Media Player -Sonos: Bugfix sonos favorite_source after lost connection (<ahref="https://github.com/pvizeli">@pvizeli</a>)</li>
<li>Sensor - SenseHAT: Add flag to declare if SenseHAT is attached (<ahref="https://github.com/nodinosaur">@nodinosaur</a>)</li>
<p>…don’t hesitate to use our very active <ahref="https://community.home-assistant.io/">forums</a> or join us for a little <ahref="https://gitter.im/home-assistant/home-assistant">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 <ahref="https://github.com/home-assistant/home-assistant/issues">issue tracker</a>. Make sure to fill in all fields of the issue template.</p>
</article>
<sectionid="disqus">
<h3class="indent title">Comments</h3>
<divid="disqus_thread"aria-live="polite"><noscript>Please enable JavaScript to view the <ahref="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript></div>
Contact us at <ahref='mailto:hello@home-assistant.io'>hello@home-assistant.io</a>.<br>
Website powered by <ahref='http://jekyllrb.com/'>Jekyll</a> and the <ahref='https://github.com/coogie/oscailte'>Oscalite theme</a>.<br/>
Hosted by <ahref='https://pages.github.com/'>GitHub</a> and served by <ahref='https://cloudflare.com'>CloudFlare</a>.
</div>
<arel="license"href="http://creativecommons.org/licenses/by-nc-sa/4.0/"><imgalt="Creative Commons License"style="border-width:0"src="https://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png"/></a><br/><spanxmlns:dct="http://purl.org/dc/terms/"property="dct:title">home-assistant.io</span> is licensed under a <arel="license"href="http://creativecommons.org/licenses/by-nc-sa/4.0/">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License</a>.
</div>
</div>
</div>
</div>
</footer>
<script>
var _gaq=[['_setAccount','UA-57927901-1'],['_trackPageview']];