Site updated at 2018-01-17 12:29:18 UTC

components/calendar.todoist/index.html

@@ -178,7 +178,7 @@
   </li>
 </ul>
 <h3><a class="title-link" name="services" href="#services"></a> Services</h3>
-<p>Todoist also comes with access to a service, <code class="highlighter-rouge">todoist.new_task</code>. This service can be used to create a new Todoist task. You can specify labels and a project, or you can leave them blank, and the task will go to your “Inbox” project.</p>
+<p>Todoist also comes with access to a service, <code class="highlighter-rouge">calendar.todoist_new_task</code>. This service can be used to create a new Todoist task. You can specify labels and a project, or you can leave them blank, and the task will go to your “Inbox” project.</p>
 <p>Here’s an example JSON payload:</p>
 <div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="w">
     </span><span class="nt">"content"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Pick up the mail"</span><span class="p">,</span><span class="w">

components/history/index.html

@@ -141,6 +141,18 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D
      <span class="pi">-</span> <span class="s">sensor.date</span>
 </code></pre>
 </div>
+<p>If you’d like the order of display of the sensors to follow the way
+they are listed in the included entity list, you can set the flag
+<code class="highlighter-rouge">use_include_order</code> to True.</p>
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry using specified entity display order</span>
+<span class="s">history</span><span class="pi">:</span>
+  <span class="s">use_include_order</span><span class="pi">:</span> <span class="s">True</span>
+  <span class="s">include</span><span class="pi">:</span>
+    <span class="s">entities</span><span class="pi">:</span>
+      <span class="pi">-</span> <span class="s">sun.sun</span>
+      <span class="pi">-</span> <span class="s">light.front_porch</span>
+</code></pre>
+</div>
 <h4><a class="title-link" name="implementation-details" href="#implementation-details"></a> Implementation details</h4>
 <p>The history is stored in a SQLite database <code class="highlighter-rouge">home-assistant_v2.db</code> within your configuration directory if the <code class="highlighter-rouge">recorder</code> component is not set up differently.</p>
 <ul>

components/sensor.mopar/index.html

@@ -95,7 +95,7 @@
   <li><strong>pin</strong> (<em>Required</em>): Your uConnect pin.</li>
 </ul>
 <h2><a class="title-link" name="service" href="#service"></a> Service</h2>
-<p>Call the <code class="highlighter-rouge">mopar.remote_command</code> service to perform a remote command on your vehicle.</p>
+<p>Call the <code class="highlighter-rouge">sensor.mopar_remote_command</code> service to perform a remote command on your vehicle.</p>
 <ul>
   <li><strong>vehicle_index</strong> (<em>Required</em>): <code class="highlighter-rouge">vehicle_index</code> attribute found on sensor.</li>
   <li><strong>command</strong> (<em>Required</em>): One of <code class="highlighter-rouge">lock/unlock/engineon/engineoff/horn</code>.</li>

components/switch.broadlink/index.html

@@ -112,7 +112,7 @@
 </ul>
 <p>Information about how to install on Windows can be found <a href="https://home-assistant.io/components/sensor.broadlink/#microsoft-windows-installation">here</a></p>
 <h3><a class="title-link" name="how-to-obtain-irrf-packets" href="#how-to-obtain-irrf-packets"></a> How to obtain IR/RF packets?</h3>
-<p>Choose Call Service from the Developer Tools. Choose the service broadlink/learn_command from the list of <strong>Available services:</strong> and hit <strong>CALL SERVICE</strong>. Press the button on your remote with in 20 seconds. The packet will be printed as a persistent notification in the States page of the web interface.</p>
+<p>Choose Call Service from the Developer Tools. Choose the service <code class="highlighter-rouge">switch.broadlink_learn_command</code> from the list of <strong>Available services:</strong> and hit <strong>CALL SERVICE</strong>. Press the button on your remote with in 20 seconds. The packet will be printed as a persistent notification in the States page of the web interface.</p>
 <p>Example config for <code class="highlighter-rouge">rm</code>, <code class="highlighter-rouge">rm2</code>, <code class="highlighter-rouge">rm_mini</code>, <code class="highlighter-rouge">rm_pro_phicomm</code>, <code class="highlighter-rouge">rm2_home_plus</code>, <code class="highlighter-rouge">rm2_home_plus_gdt</code>, <code class="highlighter-rouge">rm2_pro_plus</code>, <code class="highlighter-rouge">rm2_pro_plus2</code>, <code class="highlighter-rouge">rm2_pro_plus_bl</code> and <code class="highlighter-rouge">rm_mini_shate</code> devices:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">switch</span><span class="pi">:</span>
   <span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">broadlink</span>
@@ -183,8 +183,8 @@
       <span class="s">slot_4</span><span class="pi">:</span> <span class="s1">'</span><span class="s">Speaker</span><span class="nv"> </span><span class="s">slot'</span>
 </code></pre>
 </div>
-<h3><a class="title-link" name="service-send_packet" href="#service-send_packet"></a> Service <code class="highlighter-rouge">send_packet</code></h3>
-<p>You can use the service broadlink/send_packet to directly send IR packets without the need to assign a switch entity for each command.</p>
+<h3><a class="title-link" name="service-broadlink_send_packet" href="#service-broadlink_send_packet"></a> Service <code class="highlighter-rouge">broadlink_send_packet</code></h3>
+<p>You can use the service <code class="highlighter-rouge">switch.broadlink_send_packet</code> to directly send IR packets without the need to assign a switch entity for each command.</p>
 <table>
   <thead>
     <tr>
@@ -205,7 +205,7 @@
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">script</span><span class="pi">:</span>
   <span class="s">tv_select_source</span><span class="pi">:</span>
     <span class="s">sequence</span><span class="pi">:</span>
-      <span class="pi">-</span> <span class="s">service</span><span class="pi">:</span> <span class="s">broadlink.send_packet_192_168_0_107</span>
+      <span class="pi">-</span> <span class="s">service</span><span class="pi">:</span> <span class="s">switch.broadlink_send_packet_192_168_0_107</span>
         <span class="s">data</span><span class="pi">:</span>
           <span class="s">packet</span><span class="pi">:</span> 
             <span class="pi">-</span> <span class="s2">"</span><span class="s">JgCMAJSSFDYUNhQ2FBEUERQRFBEUERQ2FDYUNhQRFBEUERQRFBEUERQRFDYUERQRFBEUERQRFDYUNhQRFDYUNhQ2FDYUNhQABfWUkhQ2FDYUNhQRFBEUERQRFBEUNhQ2FDYUERQRFBEUERQRFBEUERQ2FBEUERQRFBEUERQ2FDYUERQ2FDYUNhQ2FDYUAA0FAAAAAAAAAAAAAAAA"</span>

components/timer/index.html

@@ -82,7 +82,7 @@ With the current implementation timers don’t persist over restarts. After a re
 <p>To add a timer to your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
 <span class="s">timer</span><span class="pi">:</span>
-  <span class="s">timer</span><span class="pi">:</span>
+  <span class="s">laundry</span><span class="pi">:</span>
     <span class="s">duration</span><span class="pi">:</span> <span class="s1">'</span><span class="s">00:01:00'</span>
 </code></pre>
 </div>