Site updated at 2016-08-28 17:05:28 UTC

atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Home Assistant]]></title>
   <link href="https://home-assistant.io/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/community/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: Community | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/community/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/device-tracking/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: Device-Tracking | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/device-tracking/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/esp8266/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: ESP8266 | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/esp8266/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/how-to/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: How-To | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/how-to/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/ibeacons/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: iBeacons | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/ibeacons/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/internet-of-things/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: Internet-of-Things | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/internet-of-things/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/iot-data/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: IoT-Data | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/iot-data/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/mqtt/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: MQTT | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/mqtt/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/organisation/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: Organisation | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/organisation/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/owntracks/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: OwnTracks | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/owntracks/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/presence-detection/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: Presence-Detection | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/presence-detection/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/public-service-announcement/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: Public-Service-Announcement | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/public-service-announcement/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/release-notes/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: Release-Notes | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/release-notes/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/survey/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: Survey | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/survey/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/talks/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: Talks | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/talks/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/technology/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: Technology | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/technology/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/user-stories/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: User-Stories | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/user-stories/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/video/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: Video | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/video/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

blog/categories/website/atom.xml

@@ -4,7 +4,7 @@
   <title><![CDATA[Category: Website | Home Assistant]]></title>
   <link href="https://home-assistant.io/blog/categories/website/atom.xml" rel="self"/>
   <link href="https://home-assistant.io/"/>
-  <updated>2016-08-28T03:56:15+00:00</updated>
+  <updated>2016-08-28T17:03:21+00:00</updated>
   <id>https://home-assistant.io/</id>
   <author>
     <name><![CDATA[Home Assistant]]></name>

components/climate.nest/index.html

@@ -93,7 +93,7 @@
 
 <p>To set it up, add the following information to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
 
-<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cliamte</span><span class="pi">:</span>
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">climate</span><span class="pi">:</span>
   <span class="s">platform</span><span class="pi">:</span> <span class="s">nest</span>
 </code></pre>
 </div>

components/notify.telegram/index.html

@@ -102,17 +102,8 @@
 
 <p>The result set will include your chat ID as <code class="highlighter-rouge">id</code> in the <code class="highlighter-rouge">from</code> section:</p>
 
-<div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="w">
+<div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="nt">"ok"</span><span class="p">:</span><span class="kc">true</span><span class="p">,</span><span class="nt">"result"</span><span class="p">:[{</span><span class="nt">"update_id"</span><span class="p">:</span><span class="mi">254199982</span><span class="p">,</span><span class="w">
-   </span><span class="nt">"ok"</span><span class="p">:</span><span class="kc">true</span><span class="p">,</span><span class="w">
+</span><span class="nt">"message"</span><span class="p">:{</span><span class="nt">"message_id"</span><span class="p">:</span><span class="mi">27</span><span class="p">,</span><span class="nt">"from"</span><span class="p">:{</span><span class="nt">"id"</span><span class="p">:</span><span class="mi">123456789</span><span class="p">,</span><span class="nt">"first_name"</span><span class="p">:</span><span class="s2">"YOUR_FIRST_NAME YOUR_NICK_NAME"</span><span class="p">,</span><span class="nt">"last_name"</span><span class="p">:</span><span class="s2">"YOUR_LAST_NAME"</span><span class="p">,</span><span class="nt">"username"</span><span class="p">:</span><span class="s2">"YOUR_NICK_NAME"</span><span class="p">},</span><span class="nt">"chat"</span><span class="p">:{</span><span class="nt">"id"</span><span class="p">:</span><span class="mi">123456789</span><span class="p">,</span><span class="nt">"first_name"</span><span class="p">:</span><span class="s2">"YOUR_FIRST_NAME YOUR_NICK_NAME"</span><span class="p">,</span><span class="nt">"last_name"</span><span class="p">:</span><span class="s2">"YOUR_LAST_NAME"</span><span class="p">,</span><span class="nt">"username"</span><span class="p">:</span><span class="s2">"YOUR_NICK_NAME"</span><span class="p">,</span><span class="nt">"type"</span><span class="p">:</span><span class="s2">"private"</span><span class="p">},</span><span class="nt">"date"</span><span class="p">:</span><span class="mi">1678292650</span><span class="p">,</span><span class="nt">"text"</span><span class="p">:</span><span class="s2">"test"</span><span class="p">}}]}</span><span class="w">
-   </span><span class="nt">"result"</span><span class="p">:[</span><span class="w">
-      </span><span class="p">{</span><span class="w">
-         </span><span class="nt">"update_id"</span><span class="p">:</span><span class="mi">254199982</span><span class="p">,</span><span class="w">
-         </span><span class="nt">"message"</span><span class="p">:{</span><span class="w">
-            </span><span class="nt">"message_id"</span><span class="p">:</span><span class="mi">201</span><span class="p">,</span><span class="w">
-            </span><span class="nt">"from"</span><span class="p">:{</span><span class="w">
-               </span><span class="nt">"id"</span><span class="p">:</span><span class="mi">123456789</span><span class="p">,</span><span class="w">
-               </span><span class="nt">"first_name"</span><span class="p">:</span><span class="s2">"Your first name"</span><span class="p">,</span><span class="w">
-</span><span class="err">...</span><span class="w">
 </span></code></pre>
 </div>
 
@@ -174,6 +165,29 @@
   <li><strong>password</strong> (<em>Optional</em>): Username for an URL which require HTTP basic authentication.</li>
 </ul>
 
+<h3><a class="title-link" name="document-support" href="#document-support"></a> Document support</h3>
+
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="nn">...</span>
+<span class="s">action</span><span class="pi">:</span>
+  <span class="s">service</span><span class="pi">:</span> <span class="s">notify.NOTIFIER_NAME</span>
+  <span class="s">data</span><span class="pi">:</span>
+    <span class="s">title</span><span class="pi">:</span> <span class="s">Send a document</span>
+    <span class="s">message</span><span class="pi">:</span> <span class="s">That's a example that sends a document.</span>
+    <span class="s">data</span><span class="pi">:</span>
+      <span class="s">document</span><span class="pi">:</span>
+        <span class="s">file</span><span class="pi">:</span> <span class="s">/tmp/whatever.odf</span>
+        <span class="s">caption</span><span class="pi">:</span> <span class="s">Picture Title xy</span>
+        
+</code></pre>
+</div>
+
+<ul>
+  <li><strong>url</strong> or <strong>file</strong> (<em>Required</em>): For local or remote path to an image.</li>
+  <li><strong>caption</strong> (<em>Optional</em>): The title of the image.</li>
+  <li><strong>username</strong> (<em>Optional</em>): Username for an URL which require HTTP basic authentication.</li>
+  <li><strong>password</strong> (<em>Optional</em>): Username for an URL which require HTTP basic authentication.</li>
+</ul>
+
 <h3><a class="title-link" name="location-support" href="#location-support"></a> Location support</h3>
 
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="nn">...</span>

components/sensor.mhz19/index.html

@@ -89,7 +89,7 @@
   <hr class="divider">
   
 
-  <p>The MH-Z19 is a small nondispersive infrared sensor that can measure CO2 sensors. High CO2 levels can lead to drowsiness, poor concentration, loss of attention or increased heart rate. Outside CO2 levels are usually between 250 and 350ppm, but inside levels can reach between 1000 and 5000 ppm. High CO2 levels indicate that you should increase ventilation.</p>
+  <p>The MH-Z19 is a small nondispersive infrared sensor that can measure CO2 sensors. High CO2 levels can lead to drowsiness, poor concentration, loss of attention or increased heart rate. The CO2 level outside is around 400ppm, but inside levels can reach between 1000 and 5000 ppm. High CO2 levels indicate that you should increase ventilation.</p>
 
 <p>Check out the <a href="https://www.open-homeautomation.com/2016/08/24/monitor-co2-levels-in-your-house/">Open Home Automation web site</a> for a quick guide how to connect the sensor to your PC or Raspberry Pi.</p>
 

getting-started/configuration/index.html

@@ -120,14 +120,14 @@
 
 <p>Inside your configuration folder is the file <code class="highlighter-rouge">configuration.yaml</code>. This is the main file that contains which components will be loaded and what their configuration is. Throughout the documentation you will find snippets that you can add to your configuration file to enable that functionality.</p>
 
-<p>If you run into trouble while configuring Home Assistant, have a look at <a href="/getting-started/troubleshooting-configuration/">the configuration troubleshooting page</a> and at the <a href="/cookbook/#example-configurationyaml">configuration.yaml examples</a>.</p>
-
 <p class="note">
-  You will have to restart Home Assistant for changes to <code class="highlighter-rouge">configuration.yaml</code> take effect.
+  You will have to restart Home Assistant for changes to <code class="highlighter-rouge">configuration.yaml</code> to take effect.
 </p>
 
+<p>If you run into trouble while configuring Home Assistant, have a look at the <a href="/getting-started/troubleshooting-configuration/">configuration troubleshooting page</a> and at the <a href="/cookbook/#example-configurationyaml">configuration.yaml examples</a>.</p>
+
 <p class="note tip">
-  Install colorlog (<code class="highlighter-rouge">$ pip3 install colorlog</code>) to make the console output easier to read, hence also easier to catch errors and warnings.
+  Test any changes to your configuration files from the command line with <code class="highlighter-rouge">hass --script check_config</code>. This script allows you to test changes without the need to restart Home Assistant.
 </p>
 
 <h3><a href="/getting-started/yaml/">Next step: Get familiar with YAML »</a></h3>

getting-started/troubleshooting-configuration/index.html

@@ -99,28 +99,29 @@
 
 <p>When a component does not show up, many different things can be the case. Before you try any of these steps, make sure to look at the <code class="highlighter-rouge">home-assistant.log</code> file and see if there are any errors related to your component you are trying to set up.</p>
 
+<p>If you have incorrect entries in your configuration files you can use the <code class="highlighter-rouge">check_config</code> script to assist in identifying them: <code class="highlighter-rouge">hass --script check_config</code>.</p>
+
 <h4><a class="title-link" name="problems-with-the-configuration" href="#problems-with-the-configuration"></a> Problems with the configuration</h4>
 
 <p>One of the most common problems with Home Assistant is an invalid <code class="highlighter-rouge">configuration.yaml</code> file.</p>
 
 <ul>
-  <li>You can test your configuration using <a href="http://yaml-online-parser.appspot.com/">this online YAML parser</a> or <a href="http://www.yamllint.com/">YAML Lint</a>.</li>
+  <li>You can test your configuration using the command line with: <code class="highlighter-rouge">hass --script check_config</code></li>
+  <li>You can verify your configuration’s yaml structure using <a href="http://yaml-online-parser.appspot.com/">this online YAML parser</a> or <a href="http://www.yamllint.com/">YAML Lint</a>.</li>
   <li>To learn more about the quirks of YAML, read <a href="https://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html">YAML IDIOSYNCRASIES</a> by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well).</li>
 </ul>
 
-<p><code class="highlighter-rouge">configuration.yaml</code> does not allow multiple sections to have the same name. If you want a specific platform to be loaded twice, append a <a href="/getting-started/devices/#style-2">number or string</a> to the name or nest them using <a href="/getting-started/devices/#style-1">this style</a>.</p>
+<p><code class="highlighter-rouge">configuration.yaml</code> does not allow multiple sections to have the same name. If you want to load multiplte platforms for one component, you can append a <a href="/getting-started/devices/#style-2-list-each-device-separately">number or string</a> to the name or nest them using <a href="/getting-started/devices/#style-1-collect-every-entity-under-the-parent">this style</a>:</p>
 
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">sensor</span><span class="pi">:</span>
-  <span class="s">platform</span><span class="pi">:</span> <span class="s">forecast</span>
+  <span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">forecast</span>
     <span class="s">...</span>
-
+  <span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">bitcoin</span>
-<span class="s">sensor 2</span><span class="pi">:</span>
-  <span class="s">platform</span><span class="pi">:</span> <span class="s">bitcoin</span>
     <span class="s">...</span>
 </code></pre>
 </div>
 
-<p>Another common problem is that a required configuration setting is missing. If this is the case, the component will report this to <code class="highlighter-rouge">home-assistant.log</code>. You can have a look at <a href="/components/">the component page</a> for instructions on how to setup the components.</p>
+<p>Another common problem is that a required configuration setting is missing. If this is the case, the component will report this to <code class="highlighter-rouge">home-assistant.log</code>. You can have a look at <a href="/components/">the various component pages</a> for instructions on how to setup the components.</p>
 
 <p>If you find any errors or want to expand the documentation, please <a href="https://github.com/home-assistant/home-assistant.io/issues">let us know</a>.</p>
 

sitemap.xml

@@ -1976,62 +1976,62 @@
 </url>
 <url>
 <loc>https://home-assistant.io/demo/frontend.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/index.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-dev-event.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-dev-info.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-dev-service.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-dev-state.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-dev-template.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-history.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-iframe.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-logbook.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-map.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/googlef4f3693c209fe788.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/static/mdi-demo.html</loc>
-<lastmod>2016-08-28T03:55:29+00:00</lastmod>
+<lastmod>2016-08-28T17:02:23+00:00</lastmod>
 </url>
 </urlset>

topics/secrets/index.html

@@ -91,11 +91,11 @@
   <hr class="divider">
   
 
-  <p>The <code class="highlighter-rouge">configuration.yaml</code> file a plain-text file thus it is readable for everyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. This separation can also help you to keep easier track of your passwords and API keys (as they are all stored at one place and no longer spread across the <code class="highlighter-rouge">configuration.yaml</code> file) if you don’t want to  <a href="/topics/splitting_configuration/">split up your configuration</a>.</p>
+  <p>The <code class="highlighter-rouge">configuration.yaml</code> file is a plain-text file, thus it is readable by anyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. By using <code class="highlighter-rouge">!secrets</code> you can remove any private information from you configuration files. This separation can also help you to keep easier track of your passwords and API keys. As they are all stored at one place and no longer spread across the <code class="highlighter-rouge">configuration.yaml</code> file or even multiple yaml files if you <a href="/topics/splitting_configuration/">split up your configuration</a>.</p>
 
 <h3><a class="title-link" name="using-secretsyaml" href="#using-secretsyaml"></a> Using secrets.yaml</h3>
 
-<p>The workflow for the outsourcing in the <code class="highlighter-rouge">secrets.yaml</code> is very similar to the <a href="/topics/splitting_configuration/">splitting of the configuration</a>. Create a <code class="highlighter-rouge">secrets.yaml</code> file in your Home assistant configuration directory (The location of the folder differs between operating systems: on OS X and Linux it’s <code class="highlighter-rouge">~/.homeassistant</code> and on Windows it’s <code class="highlighter-rouge">%APPDATA%/.homeassistant</code>).</p>
+<p>The workflow for moving private information to <code class="highlighter-rouge">secrets.yaml</code> is very similar to the <a href="/topics/splitting_configuration/">splitting of the configuration</a>. Create a <code class="highlighter-rouge">secrets.yaml</code> file in your Home assistant configuration directory (The location of the folder differs between operating systems: on OS X and Linux it’s <code class="highlighter-rouge">~/.homeassistant</code> and on Windows it’s <code class="highlighter-rouge">%APPDATA%/.homeassistant</code>).</p>
 
 <p>The entries for password and API keys in the <code class="highlighter-rouge">configuration.yaml</code> file usually looks like the example below.</p>
 
@@ -113,11 +113,33 @@
 
 <p>The <code class="highlighter-rouge">secrets.yaml</code> file contains the corresponding password assigned to the identifier.</p>
 
-<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">logger</span><span class="pi">:</span> <span class="s">debug</span>
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">http_password</span><span class="pi">:</span> <span class="s">YOUR_PASSWORD</span>
-<span class="s">http_password</span><span class="pi">:</span> <span class="s">YOUR_PASSWORD</span>
 </code></pre>
 </div>
 
+<h3><a class="title-link" name="debugging-secrets" href="#debugging-secrets"></a> Debugging secrets</h3>
+
+<p>When you start splitting your configuration into multiple files, you might end up with configuration in sub folders. Secrets will be resolved in this order:</p>
+<ul>
+  <li>A <code class="highlighter-rouge">secrets.yaml</code> located in the same folder as the yaml file referencing the secret,</li>
+  <li>next, parent folders will be searched for a <code class="highlighter-rouge">secrets.yaml</code> file with the secret, stopping at the folder with the main <code class="highlighter-rouge">configuration.yaml</code>,</li>
+  <li>lastly, <code class="highlighter-rouge">keyring</code> will be queried for the secret (more info below)</li>
+</ul>
+
+<p>To see where secrets are being loaded from you can either add an option to your <code class="highlighter-rouge">secrets.yaml</code> file or use the <code class="highlighter-rouge">check_config</code> script.</p>
+
+<p><em>Option 1</em>: Print where secrets are retrieved from to the Home Assistant log by adding the following to <code class="highlighter-rouge">secrets.yaml</code>:</p>
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">logger</span><span class="pi">:</span> <span class="s">debug</span>
+</code></pre>
+</div>
+<p>This will not print the actual secret’s value to the log.</p>
+
+<p><em>Option 2</em>: View where secrets are retrieved from and the contents of all <code class="highlighter-rouge">secrets.yaml</code> files used, you can use the <code class="highlighter-rouge">check_config</code> script from the command line:</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>hass --script check_config --secrets
+</code></pre>
+</div>
+<p>This will print all your secrets</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="http://pythonhosted.org/keyring/">Keyring</a> is an alternative way to <code class="highlighter-rouge">secrets.yaml</code>. They can be managed from the command line via the keyring script.</p>
@@ -139,7 +161,7 @@
 </code></pre>
 </div>
 
-<p>If you launch home Assistant now, you will be prompted for the keyring password to unlock your keyring.</p>
+<p>If you launch Home Assistant now, you will be prompted for the keyring password to unlock your keyring.</p>
 
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>hass
 Config directory: /home/fab/.homeassistant

topics/splitting_configuration/index.html

@@ -97,7 +97,7 @@
 
 <p>As commenting code doesn’t always happen, please read on for the details.</p>
 
-<p>Now despite the logical assumption that the <code class="highlighter-rouge">configuration.yaml</code> will be replaced by this process it will in fact remain all be it in a much less cluttered form.</p>
+<p>Now despite the logical assumption that the <code class="highlighter-rouge">configuration.yaml</code> will be replaced by this process it will in fact remain, albeit in a much less cluttered form.</p>
 
 <p>In this lighter version we will still need what could be called the core snippet:</p>
 
@@ -261,17 +261,26 @@ customize.yaml
 
 <p>If you have issues checkout <code class="highlighter-rouge">home-assistant.log</code> in the configuration directory as well as your indentations. If all else fails, head over to the <a href="https://gitter.im/balloob/home-assistant">Gitter Chatroom</a> and ask away.</p>
 
+<h3><a class="title-link" name="debugging-multiple-configuration-files" href="#debugging-multiple-configuration-files"></a> Debugging multiple configuration files</h3>
+
+<p>If you have many configuration files, the <code class="highlighter-rouge">check_config</code> script allows you to see how Home Assistant interprets them:</p>
+<ul>
+  <li>Listing all loaded files: <code class="highlighter-rouge">hass --script --check_config --files</code></li>
+  <li>Viewing a component’s config: <code class="highlighter-rouge">hass --script --check_config --info light</code></li>
+  <li>Or all components’ config:  <code class="highlighter-rouge">hass --script check_config --info all</code></li>
+</ul>
+
+<p>You can get help from the command line using: <code class="highlighter-rouge">hass --script check_config --help</code></p>
+
 <h3><a class="title-link" name="advanced-usage" href="#advanced-usage"></a> Advanced Usage</h3>
 
 <p>We offer four advanced options to include whole directories at once.</p>
-
+<ul>
-<p><code class="highlighter-rouge">!include_dir_list</code> will return content of a directory as a list with each file content being an entry in the list.</p>
+  <li><code class="highlighter-rouge">!include_dir_list</code> will return the content of a directory as a list with each file content being an entry in the list.</li>
-
+  <li><code class="highlighter-rouge">!include_dir_named</code> will return the content of a directory as a dictionary which maps filename =&gt; content of file.</li>
-<p><code class="highlighter-rouge">!include_dir_named</code> will return content of a directory as a dictionary which maps filename =&gt; content of file.</p>
+  <li><code class="highlighter-rouge">!include_dir_merge_list</code> will return the content of a directory as a list by merging all files (which should contain a list) into 1 big list.</li>
-
+  <li><code class="highlighter-rouge">!include_dir_merge_named</code> will return the content of a directory as a dictionary by loading each file and merging it into 1 big dictionary.</li>
-<p><code class="highlighter-rouge">!include_dir_merge_list</code> will return content of a directory as a list by merging all files (which should contain a list) into 1 big list.</p>
+</ul>
-
-<p><code class="highlighter-rouge">!include_dir_merge_named</code> will return content of a directory as a dictionary by loading each file and merging it into 1 big dictionary.</p>
 
 <h4><a class="title-link" name="example-include_dir_list" href="#example-include_dir_list"></a> Example: <code class="highlighter-rouge">!include_dir_list</code></h4>