Site updated at 2018-01-28 22:02:31 UTC
This commit is contained in:
Travis CI
parent
57a21e9eb0
commit
01b474f87c
268 changed files with 412 additions and 412 deletions
|
|
@ -214,7 +214,7 @@
|
|||
<li>Due to massive improvements of the <a href="https://home-assistant.io/components/wink/">Wink</a> integration, the names of your binary sensors will change and new devices can show up.</li>
|
||||
<li>The <a href="https://home-assistant.io/components/mysensors/">MySensors</a> component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you.</li>
|
||||
<li>The <a href="https://home-assistant.io/components/media_player.sonos/">Sonos</a> service <code class="highlighter-rouge">sonos_group_players</code> was removed. Use now <code class="highlighter-rouge">sonos_join</code> for this function.</li>
|
||||
<li>TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. <code class="highlighter-rouge">HASH_LANG_PLATFORM.xxx</code> -> <code class="highlighter-rouge">HASH_LANG_OPTIONS_PLATFORM.xxx</code>, replace <em>OPTIONS</em> with <code class="highlighter-rouge">-</code> on exiting platforms.</li>
|
||||
<li>TTS cache have change for the last time. Files use now also an option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. <code class="highlighter-rouge">HASH_LANG_PLATFORM.xxx</code> -> <code class="highlighter-rouge">HASH_LANG_OPTIONS_PLATFORM.xxx</code>, replace <em>OPTIONS</em> with <code class="highlighter-rouge">-</code> on exiting platforms.</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 use the former communication channels. Thanks.</p>
|
||||
|
|
|
|||
|
|
@ -94,14 +94,14 @@
|
|||
<p class="note">
|
||||
We change the platform name for binary sensor in 0.38 from <code class="highlighter-rouge">ffmpeg</code> to <code class="highlighter-rouge">ffmpeg_noise</code>. Also all service going to component and was rename from <code class="highlighter-rouge">binary_sensor.ffmpeg_xy</code> to <code class="highlighter-rouge">ffmpeg.xy</code>.
|
||||
</p>
|
||||
<p>On Raspbian Jessie, you can setup <a href="/components/ffmpeg">FFmpeg</a> and install a <a href="http://icecast.org/">icecast2</a> server using:</p>
|
||||
<p>On Raspbian Jessie, you can setup <a href="/components/ffmpeg">FFmpeg</a> and install an <a href="http://icecast.org/">icecast2</a> server using:</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo <span class="nb">echo</span> <span class="s2">"deb http://ftp.debian.org/debian jessie-backports main"</span> >> /etc/apt/sources.list
|
||||
<span class="gp">$ </span>sudo apt-get update
|
||||
<span class="gp">$ </span>sudo apt-get -t jessie-backports install ffmpeg
|
||||
<span class="gp">$ </span>sudo apt-get install icecast2
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>We setup a icecast mount point for our babyphone and update <code class="highlighter-rouge">/etc/icecast2/icecast.xml</code>:</p>
|
||||
<p>We setup an icecast mount point for our babyphone and update <code class="highlighter-rouge">/etc/icecast2/icecast.xml</code>:</p>
|
||||
<div class="highlighter-rouge"><pre class="highlight"><code><mount>
|
||||
<mount-name>/babyphone.mp3</mount-name>
|
||||
<stream-name>Babyphone</stream-name>
|
||||
|
|
@ -152,7 +152,7 @@ We change the platform name for binary sensor in 0.38 from <code class="highligh
|
|||
<span class="s">entity_id</span><span class="pi">:</span> <span class="s">binary_sensor.ffmpeg_noise</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
<h3><a class="title-link" name="trigger-a-alarm" href="#trigger-a-alarm"></a> Trigger a alarm</h3>
|
||||
<h3><a class="title-link" name="trigger-an-alarm" href="#trigger-an-alarm"></a> Trigger an alarm</h3>
|
||||
<p>Now we can make a lot stuff. Here is a simple example of an automation what should be possible with Sonos speakers.</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">automation</span><span class="pi">:</span>
|
||||
<span class="pi">-</span> <span class="s">alias</span><span class="pi">:</span> <span class="s1">'</span><span class="s">Babyphone</span><span class="nv"> </span><span class="s">alarm</span><span class="nv"> </span><span class="s">on'</span>
|
||||
|
|
|
|||
|
|
@ -124,8 +124,8 @@
|
|||
<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>
|
||||
<h4>Customize has been reverted to its original config</h4>
|
||||
<p>The old customize is back. The options to match by domain or using glob have been moved to its 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>
|
||||
|
|
|
|||
|
|
@ -128,7 +128,7 @@
|
|||
<a name="read-more"></a>
|
||||
<h2><a class="title-link" name="breaking-changes" href="#breaking-changes"></a> Breaking Changes</h2>
|
||||
<ul>
|
||||
<li>history_graph component: If your component used <code class="highlighter-rouge">history.get_significant_states</code> function then you need to adjust the string <code class="highlighter-rouge">entitity_id</code> parameter has been changed to a list of strings <code class="highlighter-rouge">entity_ids</code> parameter. (<a href="https://github.com/andrey-git">@andrey-git</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9472">#9472</a>) (<a href="https://home-assistant.io/components/history_graph/">history_graph docs</a>) (breaking change)</li>
|
||||
<li>history_graph component: If your component used <code class="highlighter-rouge">history.get_significant_states</code> function then you need to adjust the string <code class="highlighter-rouge">entity_id</code> parameter has been changed to a list of strings <code class="highlighter-rouge">entity_ids</code> parameter. (<a href="https://github.com/andrey-git">@andrey-git</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9472">#9472</a>) (<a href="https://home-assistant.io/components/history_graph/">history_graph docs</a>) (breaking change)</li>
|
||||
<li>UPNP component: The <code class="highlighter-rouge">external_port</code> configuration option was removed. (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9560">#9560</a>) (<a href="https://home-assistant.io/components/upnp/">upnp docs</a>) (breaking change)</li>
|
||||
<li>New Wink services: pair new device, rename, delete and add new lock key code. All device attributes that are multi-words are now separated by “_” and no longer “ “. (<a href="https://github.com/w1ll1am23">@w1ll1am23</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9303">#9303</a>) (<a href="https://home-assistant.io/components/wink/">wink docs</a>) (<a href="https://home-assistant.io/components/binary_sensor.wink/">binary_sensor.wink docs</a>) (<a href="https://home-assistant.io/components/lock.wink/">lock.wink docs</a>) (breaking change)</li>
|
||||
<li>TP-Link Switch: Attribute names now uses underscores and unnecessary capitalization was removed. (<a href="https://github.com/djchen">@djchen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9607">#9607</a>) (<a href="https://home-assistant.io/components/switch.tplink/">switch.tplink docs</a>) (breaking change)</li>
|
||||
|
|
|
|||
|
|
@ -251,7 +251,7 @@
|
|||
state_topic: "home/ttn/garden_temp"
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add an configuration variable to <code class="highlighter-rouge">mqtt_ttn</code> sensor which allows you to select the device.</p>
|
||||
<p>This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add a configuration variable to <code class="highlighter-rouge">mqtt_ttn</code> sensor which allows you to select the device.</p>
|
||||
</article>
|
||||
<div id='post-comments'></div>
|
||||
<section id="disqus">
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@
|
|||
<p>The most amazing part? It is super easy to set up!</p>
|
||||
<a name="read-more"></a>
|
||||
<h2><a class="title-link" name="setting-up-tor" href="#setting-up-tor"></a> Setting up Tor</h2>
|
||||
<p>Our <a href="/docs/ecosystem/tor/">documentation</a> provides an detailed guide about seting up a <a href="https://www.torproject.org/docs/hidden-services.html.en">Tor’s Hidden Service</a>. The setup is straight-forward:</p>
|
||||
<p>Our <a href="/docs/ecosystem/tor/">documentation</a> provides a detailed guide about setting up a <a href="https://www.torproject.org/docs/hidden-services.html.en">Tor’s Hidden Service</a>. The setup is straight-forward:</p>
|
||||
<ol>
|
||||
<li>Install Tor. On a Debian-based system: <code class="highlighter-rouge">$ sudo apt-get install tor</code>. On Fedora: <code class="highlighter-rouge">$ sudo dnf install tor</code></li>
|
||||
<li>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue