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

Site updated at 2018-01-21 05:37:59 UTC

Browse source
This commit is contained in:
Travis CI 2018-01-21 05:37:59 +00:00
parent 67c9b83494
commit 6d15a94899
242 changed files with 2651 additions and 1490 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -67,6 +67,84 @@
<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/07/29/release-50/">0.50: Voice control, History improvements, and Xiaomi</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-07-29T00:11:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> July 29, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 13 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/07/29/release-50/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><a href="/components/#version/0.50"><img src="/images/blog/2017-07-0.50/components.png" style="border: 0;box-shadow: none;" /></a></p>
<p>Last Wednesday we released <a href="https://home-assistant.io/hassio/">Hass.io</a>, an operating system to take care of all the updating hassles that come with running home automation at home and so much more. This is a major milestone for Home Assistant as it is our first step to offering a fully integrated solution using a bring your own hardware approach.</p>
<p>The launch has been crazy successful. The <a href="https://www.youtube.com/watch?v=XWPluWcYRMI&amp;feature=youtu.be">20 minute introduction video</a> by BRUHAutomation already has 12.5k views in just 4 days with no less than 150 comments.</p>
<p>Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.</p>
<h3><a class="title-link" name="adding-the-power-of-voice-to-integrations" href="#adding-the-power-of-voice-to-integrations"></a> Adding the power of voice to integrations</h3>
<p>But enough about Hass.io, let’s not forget about Home Assistant. This release has completely revamped the way how we deal with voice integrations. We turned Home Assistant into a platform to write voice apps, no matter where the processing of the voice happens. This can be done by Alexa, Google Assistant or in the Home Assistant user interface.</p>
<p>We are super excited about the new functionality and hope that it will trigger a new type of applications and systems to be built on top of Home Assistant. This release includes a shopping list to show the new functionality. As a user you can add any item to the shopping list with your voice and also ask what is on your shopping list.</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
<span class="s">shopping_list</span><span class="pi">:</span>
</code></pre>
</div>
<p>To make testing these applications easier, we’ve updated the conversation component. The component will now allow sentences to be configured that hook directly into the new voice functionality. Combined with the new interface it will allow for some great interactions! Check out the <a href="https://home-assistant.io/developers/intent/">developer docs</a> for more information.</p>
<div class="videoWrapper">
<iframe width="560" height="315" src="https://www.youtube.com/embed/Ij0zDF3qwmE" frameborder="0" allowfullscreen=""></iframe>
</div>
<h3><a class="title-link" name="history-improvements" href="#history-improvements"></a> History improvements</h3>
<p><a href="https://github.com/OverloadUT">@OverloadUT</a> has been recently spending a lot of time on optimizing the history database queries. This release includes PR <a href="https://github.com/home-assistant/home-assistant/pull/8632">#8632</a>, the first in a list of improvements that he is working on. This PR greatly improves requests for single entities by using an optimized query for this use case.</p>
<p>The performance change in some of his tests shows this change to be about 300x faster (30 seconds to 0.1 seconds!) (There is no theoretical upper limit due to the issue with multi-entity queries getting worse the longer the current recorder run has been going.)</p>
<h3><a class="title-link" name="xiaomi-integration" href="#xiaomi-integration"></a> Xiaomi integration</h3>
<p>Yes, it has happened! After being in beta for a while, the Xiaomi support is now available to all. <a href="https://github.com/danielhiversen">@danielhiversen</a> did an amazing job and we now support sensors, switches, lights and covers.</p>
<h3><a class="title-link" name="velbus-integration" href="#velbus-integration"></a> Velbus integration</h3>
<p>Another awesome integration is that of the Velbus home automation system which has been contributed by <a href="https://github.com/thomasdelaet">@thomasdelaet</a>. It integrates their sensors, covers, fans, lights and switches.</p>
<h3><a class="title-link" name="manual-alarm-with-mqtt-control" href="#manual-alarm-with-mqtt-control"></a> Manual alarm with MQTT control</h3>
<p>A new version of the manual alarm component is now available with full MQTT control thanks to <a href="https://github.com/colinodell">@colinodell</a>. Using this you can build your own control panel to remotely arm/disarm the alarm. For example, using a <a href="https://www.hackster.io/colinodell/diy-alarm-control-panel-for-home-assistant-ac1813">Raspberry Pi to create an alarm</a>.</p>
<h2><a class="title-link" name="new-platforms" href="#new-platforms"></a> New Platforms</h2>
<ul>
<li>Initial support for Google Wifi/OnHub (<a href="https://github.com/fronzbot">@fronzbot</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8485">#8485</a>) (<a href="https://home-assistant.io/components/sensor.google_wifi/">sensor.google_wifi docs</a>) (new-platform)</li>
<li>Xiaomi gw support (<a href="https://github.com/danielhiversen">@danielhiversen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8555">#8555</a>) (<a href="https://home-assistant.io/components/xiaomi/">xiaomi docs</a>) (<a href="https://home-assistant.io/components/binary_sensor.xiaomi/">binary_sensor.xiaomi docs</a>) (<a href="https://home-assistant.io/components/cover.xiaomi/">cover.xiaomi docs</a>) (<a href="https://home-assistant.io/components/light.xiaomi/">light.xiaomi docs</a>) (<a href="https://home-assistant.io/components/sensor.xiaomi/">sensor.xiaomi docs</a>) (<a href="https://home-assistant.io/components/switch.xiaomi/">switch.xiaomi docs</a>) (new-platform)</li>
<li>Add Intent component (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8434">#8434</a>) (<a href="https://home-assistant.io/components/alexa/">alexa docs</a>) (<a href="https://home-assistant.io/components/intent_script/">intent_script docs</a>) (<a href="https://home-assistant.io/components/shopping_list/">shopping_list docs</a>) (<a href="https://home-assistant.io/components/snips/">snips docs</a>) (breaking change) (new-platform)</li>
<li>Manual alarm with MQTT control (<a href="https://github.com/colinodell">@colinodell</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8257">#8257</a>) (<a href="https://home-assistant.io/components/alarm_control_panel.manual_mqtt/">alarm_control_panel.manual_mqtt docs</a>) (new-platform)</li>
<li>Add component Light TPLink (<a href="https://github.com/gollo">@gollo</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8643">#8643</a>) (<a href="https://home-assistant.io/components/light.tplink/">light.tplink docs</a>) (new-platform)</li>
<li>Velbus (<a href="https://github.com/thomasdelaet">@thomasdelaet</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8076">#8076</a>) (<a href="https://home-assistant.io/components/velbus/">velbus docs</a>) (<a href="https://home-assistant.io/components/binary_sensor.velbus/">binary_sensor.velbus docs</a>) (<a href="https://home-assistant.io/components/light.velbus/">light.velbus docs</a>) (new-platform)</li>
<li>Add uk_transport component. (<a href="https://github.com/robmarkcole">@robmarkcole</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8600">#8600</a>) (<a href="https://home-assistant.io/components/sensor.uk_transport/">sensor.uk_transport docs</a>) (new-platform)</li>
</ul>
<h2><a class="title-link" name="release-0502---july-31" href="#release-0502---july-31"></a> Release 0.50.2 - July 31</h2>
<p>Straight to 0.50.2. We released 0.50 as 0.50.1 due to an upload error to PyPi.</p>
<ul>
<li>Fix TP-Link light brightness issue #8744. (<a href="https://github.com/gollo">@gollo</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8755">#8755</a>)</li>
<li>Fix typo in script error (<a href="https://github.com/n8henrie">@n8henrie</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8754">#8754</a>)</li>
<li>Fix tradfri error spam (<a href="https://github.com/MartinHjelmare">@MartinHjelmare</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8738">#8738</a>) (<a href="https://home-assistant.io/components/light.tradfri/">light.tradfri docs</a>)</li>
<li>Media Player - Pioneer: Suppress exception if host is not available (fixes #8684) (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8732">#8732</a>) (<a href="https://home-assistant.io/components/media_player.pioneer/">media_player.pioneer docs</a>)</li>
<li>Telegram Bot: Retry set_webhook up to three times, reduce timeout to 5s again (<a href="https://github.com/azogue">@azogue</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8716">#8716</a>) (<a href="https://home-assistant.io/components/telegram_bot.webhooks/">telegram_bot.webhooks docs</a>)</li>
<li>Fixed sensor issue with Google Wifi routers in bridge mode (<a href="https://github.com/fronzbot">@fronzbot</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8710">#8710</a>) (<a href="https://home-assistant.io/components/sensor.google_wifi/">sensor.google_wifi docs</a>)</li>
<li>Fix alexa cards (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8708">#8708</a>) (<a href="https://home-assistant.io/components/alexa/">alexa docs</a>)</li>
<li>Fix Kodi reconnection after websocket disconnect (<a href="https://github.com/armills">@armills</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8704">#8704</a>) (<a href="https://home-assistant.io/components/media_player.kodi/">media_player.kodi docs</a>)</li>
<li>Move I/O outside of properties for light/tplink platform (<a href="https://github.com/gollo">@gollo</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8699">#8699</a>) (<a href="https://home-assistant.io/components/light.tplink/">light.tplink docs</a>) (new-platform)</li>
<li>Correctly discover GE Fan Controllers (<a href="https://github.com/armills">@armills</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8682">#8682</a>) (<a href="https://home-assistant.io/components/zwave/">zwave docs</a>)</li>
<li>Fix Z-Wave barrier discovery for new API (<a href="https://github.com/armills">@armills</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8706">#8706</a>) (<a href="https://home-assistant.io/components/zwave/">zwave docs</a>) (<a href="https://home-assistant.io/components/cover.zwave/">cover.zwave docs</a>)</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/07/29/release-50/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -487,35 +565,6 @@ Screenshot of a green dashboard
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/06/15/zwave-entity-ids/">ZWave Entity IDs</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-06-15T12:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> June 15, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Adam Mills</span>
<span><i class='icon-time'></i> two minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Technology</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/06/15/zwave-entity-ids/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>ZWave entity_ids have long been a source of frustration in Home Assistant. The first problem we faced was that depending on the order of node discovery, entity_ids could be discovered with different names on each run. To solve this we added the node id as a suffix to the entity_id. This ensured that entity_ids were generated deterministically on each run, but additional suffixes had to be added to handle edge cases where there would otherwise be a conflict. The resulting entity_ids worked, but have been difficult to work with and makes ZWave a strange exception among other Home Assistant components.</p>
<p>Thanks to the awesome work of <a href="https://github.com/turbokongen">@turbokongen</a>, a growing number of ZWave configuration options are now available from the new ZWave panel in the Home Assistant frontend. Among these new features is support for renaming of ZWave nodes and their underlying values. (These renames are persisted in zwcfg_*.xml) This is important, because these items are combined to form the Home Assistant entity name, which is used to generate the entity_id. Now that these options are available, ZWave users can rename nodes and values, influencing the entity_ids that are generated by Home Assistant.</p>
<p>Now that users are able to control these names, we will be making changes to how the entity_ids are generated for ZWave entities. The ZWave entity_ids are going to switch back to using the standard entity_id generation from Home Assistant core, based on the entity names. Moving forward, if there is a conflict when generating entity_ids, a suffix will be added, and it will be the responsibility of the user to rename their nodes and values to avoid the conflict. This is the same as any other platform in Home Assistant where two devices are discovered with the same name.</p>
<p>With the release of 0.47, this feature will be opt-in. Setting <code class="highlighter-rouge">new_entity_ids: true</code> under <code class="highlighter-rouge">zwave:</code> in your configuration.yaml will enable the new generation. After 0.48 this feature will become opt-out. From 0.48 onward, unless you’ve declared <code class="highlighter-rouge">new_entity_ids: false</code> you will switch to the new entity_id generation. At an undecided point in the future, the old entity_id generation will be removed completely.</p>
<p>I’m sure all ZWave users understand that the current entity_ids aren’t easy to use. They’re annoying to type in configuration.yaml, and break if a node needs to be re-included to the network. We know that breaking changes are painful, and so we’re doing what we can to roll this change out as smoothly as possible. The end result should be a dramatic simplification of most ZWave configurations. We hope that this change will ultimately make ZWave much easier to work with, and bring ZWave configuration just a little closer to the rest of the Home Assistant platforms.</p>
</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>
@ -541,6 +590,7 @@ Screenshot of a green dashboard
<section class="aside-module grid__item one-whole lap-one-half">
<h1 class="title delta">Categories</h1>
<ul class="divided">
<li><a href="/blog/categories/announcement/">Announcement</a></li>
<li><a href="/blog/categories/announcements/">Announcements</a></li>
<li><a href="/blog/categories/community/">Community</a></li>
<li><a href="/blog/categories/device-tracking/">Device Tracking</a></li>
@ -555,8 +605,10 @@ Screenshot of a green dashboard
<li><a href="/blog/categories/organisation/">Organisation</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public/">Public</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>
<li><a href="/blog/categories/release-notes/">Release Notes</a></li>
<li><a href="/blog/categories/service/">Service</a></li>
<li><a href="/blog/categories/survey/">Survey</a></li>
<li><a href="/blog/categories/talks/">Talks</a></li>
<li><a href="/blog/categories/technology/">Technology</a></li>