Site updated at 2017-07-29 22:06:40 UTC

docs/automation/trigger/index.html

@@ -144,9 +144,6 @@
 <p class="note warning">
   Use quotes around your values for <code class="highlighter-rouge">from</code> and <code class="highlighter-rouge">to</code> to avoid the YAML parser interpreting values as booleans.
 </p>
-<p class="note warning">
-  Using <code class="highlighter-rouge">state</code> as an alias for <code class="highlighter-rouge">to</code> is deprecated.
-</p>
 <h3><a class="title-link" name="sun-trigger" href="#sun-trigger"></a> Sun trigger</h3>
 <p>Trigger when the sun is setting or rising. An optional time offset can be given to have it trigger for example 45 minutes before sunset, when dusk is setting in.</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">automation</span><span class="pi">:</span>

docs/configuration/secrets/index.html

@@ -133,6 +133,21 @@ Please enter password <span class="k">for </span>encrypted keyring:
 <p class="note warning">
   If you are using the Python Keyring, <a href="/getting-started/autostart/">autostarting</a> of Home Assistant will no longer work.
 </p>
+<h3><a class="title-link" name="storing-passwords-in-a-keyring-managed-by-your-os" href="#storing-passwords-in-a-keyring-managed-by-your-os"></a> Storing passwords in a keyring managed by your OS</h3>
+<p>Using <a href="https://github.com/fugue/credstash">Credstash</a> is an alternative way to <code class="highlighter-rouge">secrets.yaml</code>. They can be managed from the command line via the credstash script.</p>
+<p>Before using credstash, you need to set up AWS credentials either via the <code class="highlighter-rouge">aws</code> command line tool, or using environment variables as explained in the <a href="http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html">AWS CLI docs</a> as well as creating a KMS key named ‘credstash’ as explained in the <a href="https://github.com/fugue/credstash#setting-up-kms">credstash readme</a>. After that is complete, you can use the provided script to add secrets to your Home Assistant secret store in credstash</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>hass --script credstash --help
+</code></pre>
+</div>
+<p>To store a password in credstash, replace your password or API key with <code class="highlighter-rouge">!secret</code> and an identifier in <code class="highlighter-rouge">configuration.yaml</code> file.</p>
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">http</span><span class="pi">:</span>
+  <span class="s">api_password</span><span class="pi">:</span> <span class="kt">!secret</span> <span class="s">http_password</span>
+</code></pre>
+</div>
+<p>Create an entry in your credstash store.</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>hass --script credstash <span class="nb">set </span>http_password
+</code></pre>
+</div>
 </article>
         </div>
         <aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">

docs/configuration/yaml/index.html

@@ -116,6 +116,18 @@ The other properties (like name) are specified using mappings. Note that the sec
     <span class="s">state_topic</span><span class="pi">:</span> <span class="s">sensor2/topic</span>
 </code></pre>
 </div>
+<h3><a class="title-link" name="using-environment-variables" href="#using-environment-variables"></a> Using Environment Variables</h3>
+<p>You can include values from your system’s environment variables with <code class="highlighter-rouge">!env_var</code>.</p>
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">http</span><span class="pi">:</span>
+  <span class="s">api_password</span><span class="pi">:</span> <span class="kt">!env_var</span> <span class="s">PASSWORD</span>
+</code></pre>
+</div>
+<h4>Default Value</h4>
+<p>If an environment variable is not set, you can fallback to a default value.</p>
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">http</span><span class="pi">:</span>
+  <span class="s">api_password</span><span class="pi">:</span> <span class="kt">!env_var</span> <span class="s">PASSWORD default_password</span>
+</code></pre>
+</div>
 </article>
         </div>
         <aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">

docs/z-wave/index.html

@@ -136,6 +136,9 @@ Depending on what’s plugged into your USB ports, the name found above may chan
 </p>
 <h3><a class="title-link" name="adding-devices" href="#adding-devices"></a> Adding Devices</h3>
 <p>To add a Z-Wave device to your system, go to the Services menu and select the <code class="highlighter-rouge">zwave</code> domain, and select the <code class="highlighter-rouge">add-node</code> service. Then find your device’s add button and press that as well.</p>
+<p class="note">
+Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devices to the network using their own contol buttons. This method should be avoided as it is prone to errors. Devices added to the Z-Wave network using this method may not function well.
+</p>
 <h3><a class="title-link" name="adding-security-devices" href="#adding-security-devices"></a> Adding Security Devices</h3>
 <p>Security Z-Wave devices require a network key before being added to the network using the <code class="highlighter-rouge">zwave.add_node_secure</code> service. You must set the <em>network_key</em> configuration variable to use a network key before adding these devices.</p>
 <p>An easy script to generate a random key:</p>