Site updated at 2017-09-26 18:37:45 UTC

2017-09-26 18:37:45 +00:00 · 2017-09-26 18:37:45 +00:00 · 6c210aca29
commit 6c210aca29
parent cd1993547e
56 changed files with 99 additions and 99 deletions
--- a/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/2016/02/12/classifying-the-internet-of-things/index.html
+++ b/blog/2016/02/12/classifying-the-internet-of-things/index.html
@ -147,7 +147,7 @@
 </ul>
 <p>Disadvantages:</p>
 <ul>
-  <li>Home automation will assume the wrong state if the the command is not received correctly or if the device is controlled in any other way outside of the home automation system.</li>
+  <li>Home automation will assume the wrong state if the command is not received correctly or if the device is controlled in any other way outside of the home automation system.</li>
 </ul>
 <h3><a class="title-link" name="polling-the-cloud" href="#polling-the-cloud"></a> Polling the cloud</h3>
 <p>These are devices that will only report their state to their own cloud backend. The cloud backend will allow reading the state but will not notify when a new state has arrived. This requires the home automation to check frequently if the state has been updated.</p>
--- a/blog/2017/02/25/config-panel-and-state-restoration/index.html
+++ b/blog/2017/02/25/config-panel-and-state-restoration/index.html
@ -118,7 +118,7 @@
 <h2>Reorganized documentation</h2>
 <p>Thanks to <a href="https://github.com/fabaff">Fabian</a> we have a great re-organized documentation. Is it perfect yet? No. But we are getting close. We put a lot of focus on making sure the Raspberry Pi is the main focus of our getting started. The other instructions are still available, just not as part of the main getting started.</p>
 <h2>State restoration</h2>
-<p>Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. <a href="https://github.com/kellerza">Johann</a> has added the foundation for state restoration to Home Assistant. For the initial release support has been added to to <code class="highlighter-rouge">input_select</code> and <code class="highlighter-rouge">input_boolean</code> components. We will be adding this to more integrations in the future.</p>
+<p>Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. <a href="https://github.com/kellerza">Johann</a> has added the foundation for state restoration to Home Assistant. For the initial release support has been added to <code class="highlighter-rouge">input_select</code> and <code class="highlighter-rouge">input_boolean</code> components. We will be adding this to more integrations in the future.</p>
 <h2>Breaking changes to customize and Z-Wave “customize”</h2>
 <p>A couple of releases ago we introduced a new way of doing <code class="highlighter-rouge">customize</code>. It became a list that allowed different ways of matching the config to the entity.</p>
 <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>
--- a/blog/categories/announcements/atom.xml
+++ b/blog/categories/announcements/atom.xml
@ -4,7 +4,7 @@
  <title><![CDATA[Category: Announcements | Home Assistant]]></title>
  <link href="https://home-assistant.io/blog/categories/announcements/atom.xml" rel="self"/>
  <link href="https://home-assistant.io/"/>
-  <updated>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/community/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/device-tracking/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/esp8266/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/how-to/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/ibeacons/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/internet-of-things/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
@ -254,7 +254,7 @@ Advantages:
 Disadvantages:
- - Home automation will assume the wrong state if the the command is not received correctly or if the device is controlled in any other way outside of the home automation system.
+ - Home automation will assume the wrong state if the command is not received correctly or if the device is controlled in any other way outside of the home automation system.
 ### <a class='title-link' name='polling-the-cloud' href='#polling-the-cloud'></a> Polling the cloud 
 These are devices that will only report their state to their own cloud backend. The cloud backend will allow reading the state but will not notify when a new state has arrived. This requires the home automation to check frequently if the state has been updated.
--- a/blog/categories/iot-data/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/media/atom.xml
+++ b/blog/categories/media/atom.xml
@ -4,7 +4,7 @@
  <title><![CDATA[Category: Media | Home Assistant]]></title>
  <link href="https://home-assistant.io/blog/categories/media/atom.xml" rel="self"/>
  <link href="https://home-assistant.io/"/>
-  <updated>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/merchandise/atom.xml
+++ b/blog/categories/merchandise/atom.xml
@ -4,7 +4,7 @@
  <title><![CDATA[Category: Merchandise | Home Assistant]]></title>
  <link href="https://home-assistant.io/blog/categories/merchandise/atom.xml" rel="self"/>
  <link href="https://home-assistant.io/"/>
-  <updated>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/micropython/atom.xml
+++ b/blog/categories/micropython/atom.xml
@ -4,7 +4,7 @@
  <title><![CDATA[Category: Micropython | Home Assistant]]></title>
  <link href="https://home-assistant.io/blog/categories/micropython/atom.xml" rel="self"/>
  <link href="https://home-assistant.io/"/>
-  <updated>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/mqtt/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/organisation/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/owntracks/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/presence-detection/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/public-service-announcement/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/release-notes/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/survey/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/talks/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/technology/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/user-stories/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/video/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/categories/website/atom.xml
+++ b/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>2017-09-26T16:07:55+00:00</updated>
+  <updated>2017-09-26T18:31:09+00:00</updated>
  <id>https://home-assistant.io/</id>
  <author>
    <name><![CDATA[Home Assistant]]></name>
--- a/blog/posts/5/index.html
+++ b/blog/posts/5/index.html
@ -208,7 +208,7 @@ Screenshot of all the different functionality the IP webcam integration offers.
 <h2>Reorganized documentation</h2>
 <p>Thanks to <a href="https://github.com/fabaff">Fabian</a> we have a great re-organized documentation. Is it perfect yet? No. But we are getting close. We put a lot of focus on making sure the Raspberry Pi is the main focus of our getting started. The other instructions are still available, just not as part of the main getting started.</p>
 <h2>State restoration</h2>
-<p>Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. <a href="https://github.com/kellerza">Johann</a> has added the foundation for state restoration to Home Assistant. For the initial release support has been added to to <code class="highlighter-rouge">input_select</code> and <code class="highlighter-rouge">input_boolean</code> components. We will be adding this to more integrations in the future.</p>
+<p>Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. <a href="https://github.com/kellerza">Johann</a> has added the foundation for state restoration to Home Assistant. For the initial release support has been added to <code class="highlighter-rouge">input_select</code> and <code class="highlighter-rouge">input_boolean</code> components. We will be adding this to more integrations in the future.</p>
 <h2>Breaking changes to customize and Z-Wave “customize”</h2>
 <p>A couple of releases ago we introduced a new way of doing <code class="highlighter-rouge">customize</code>. It became a list that allowed different ways of matching the config to the entity.</p>
 <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>
--- a/components/alarm_control_panel.egardia/index.html
+++ b/components/alarm_control_panel.egardia/index.html
@ -75,7 +75,7 @@
  </header>
  <hr class="divider">
  <p>The <code class="highlighter-rouge">egardia</code> platform enables the ability to control an <a href="http://egardia.com/">Egardia</a>/Woonveilig control panel. These alarm panels are known under different brand names across the world, including Woonveilig in the Netherlands. This was tested on a Gate01 version of the Egardia/Woonveilig platform.</p>
-<p>You will need to know the IP of your alarm panel on your local network. Test if you can login to the panel by browsing to the IP address and log in in using your Egardia/Woonveilig account.</p>
+<p>You will need to know the IP of your alarm panel on your local network. Test if you can login to the panel by browsing to the IP address and log in using your Egardia/Woonveilig account.</p>
 <p>To enable this, add the following lines to your <code class="highlighter-rouge">configuration.yaml</code>:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
 <span class="s">alarm_control_panel</span><span class="pi">:</span>
--- a/components/alexa/index.html
+++ b/components/alexa/index.html
@ -92,7 +92,7 @@
 <ol>
  <li>In your router, forward external 443 to your Home Assistant serving port (defaults to 8123)
  OR</li>
-  <li>Change your Home Assistant serving port to 443 this is done in the <a href="/components/http/"><code class="highlighter-rouge">http</code></a> section with the the <code class="highlighter-rouge">server_port</code> entry in your <code class="highlighter-rouge">configuration.yaml</code> file</li>
+  <li>Change your Home Assistant serving port to 443 this is done in the <a href="/components/http/"><code class="highlighter-rouge">http</code></a> section with the <code class="highlighter-rouge">server_port</code> entry in your <code class="highlighter-rouge">configuration.yaml</code> file</li>
 </ol>
 <p>To get started with Alexa skills:</p>
 <ul>
--- a/components/asterisk_mbox/index.html
+++ b/components/asterisk_mbox/index.html
@ -77,7 +77,7 @@
  <p>The Asterisk Voicemail integration for Home Assistant allows you to view, listen to, and delete voicemails from an Asterisk voicemail mailbox.  The component includes a panel on the frontend that provides caller-id and speech-to-text transcription (using Google’s API) of messages in addition to playback and message deletion. There is also an included sensor that indicates of the number of available messages. There is no requirement that the Asterisk PBX and Home Assistant are running on the same machine.</p>
 <p>To enable the component, a configuration is required in both Home Assistant as well as on the Asterisk server.</p>
 <p>First follow the <a href="/docs/asterisk_mbox">Asterisk PBX configuration guide</a> to setup the necessary server on the Asterisk PBX server (this is needed even if Asterisk and Home Assistant are running on the same server)</p>
-<p>Once that is complete, add the the following entry <code class="highlighter-rouge">configuration.yaml</code> file:</p>
+<p>Once that is complete, add the following entry <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">asterisk_mbox</span><span class="pi">:</span>
    <span class="s">password</span><span class="pi">:</span> <span class="s">ASTERISK_PBX_PASSWORD</span>
--- a/components/binary_sensor.arest/index.html
+++ b/components/binary_sensor.arest/index.html
@ -87,7 +87,7 @@
 <ul>
  <li><strong>resource</strong> (<em>Required</em>): IP address and schema of the device that is exposing an aREST API, e.g. http://192.168.1.10.</li>
  <li><strong>pin</strong> (<em>Required</em>): Number of the pin to monitor.</li>
-  <li><strong>name</strong> (<em>Optional</em>): Let you overwrite the the name of the device. By default <em>name</em> from the device is used.</li>
+  <li><strong>name</strong> (<em>Optional</em>): Let you overwrite the name of the device. By default <em>name</em> from the device is used.</li>
 </ul>
 <p>Accessing the URL http://IP_ADDRESS/digital/PIN_NUMBER should give you the state of the pin inside a JSON response as <code class="highlighter-rouge">return_value</code>.</p>
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>curl -X GET http://192.168.0.5/digital/9
--- a/components/binary_sensor.command_line/index.html
+++ b/components/binary_sensor.command_line/index.html
@ -85,7 +85,7 @@
 <p>Configuration variables:</p>
 <ul>
  <li><strong>command</strong> (<em>Required</em>): The action to take to get the value.</li>
-  <li><strong>name</strong> (<em>Optional</em>): Let you overwrite the the name of the device. By default <em>name</em> from the device is used.</li>
+  <li><strong>name</strong> (<em>Optional</em>): Let you overwrite the name of the device. By default <em>name</em> from the device is used.</li>
  <li><strong>device_class</strong> (<em>Optional</em>): The <a href="/components/binary_sensor/">type/class</a> of the sensor to set the icon in the frontend.</li>
  <li><strong>payload_on</strong> (<em>Optional</em>): The payload that represents enabled state. Default is “ON”.</li>
  <li><strong>payload_off</strong> (<em>Optional</em>): The payload that represents disabled state. Default is “OFF”.</li>
--- a/components/climate.eq3btsmart/index.html
+++ b/components/climate.eq3btsmart/index.html
@ -79,7 +79,7 @@
 As the device doesn’t contain a temperature sensor (<a href="https://forum.fhem.de/index.php/topic,39308.15.html">read more</a>),
 we report target temperature also as current one.</p>
 <h3>Testing the connectivity</h3>
-<p>Before configuring Home Assistant you should check that connectivity with the thermostat is working, which can can be done with the eq3cli tool:</p>
+<p>Before configuring Home Assistant you should check that connectivity with the thermostat is working, which can be done with the eq3cli tool:</p>
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code>eq3cli --mac 00:11:22:33:44:55
 <span class="o">[</span>00:1A:22:XX:XX:XX] Target 17.0 <span class="o">(</span>mode: auto dst, away: no<span class="o">)</span>
--- a/components/device_tracker.snmp/index.html
+++ b/components/device_tracker.snmp/index.html
@ -163,7 +163,7 @@ This device tracker needs SNMP to be enabled on the router. It could be that you
 <p>Configuration variables:</p>
 <ul>
  <li><strong>host</strong> (<em>Required</em>): The IP address of the router, eg. 192.168.1.1.</li>
-  <li><strong>community</strong> (<em>Required</em>): The SNMP community which is set for the device. Most devices have a default community set to to <code class="highlighter-rouge">public</code> with read-only permission (which is sufficient).</li>
+  <li><strong>community</strong> (<em>Required</em>): The SNMP community which is set for the device. Most devices have a default community set to <code class="highlighter-rouge">public</code> with read-only permission (which is sufficient).</li>
  <li><strong>baseoid</strong> (<em>Required</em>): The OID prefix where wireless client registrations can be found, usually vendor specific. It’s advised to use the numerical notation. To find this base OID, check vendor documentation or check the MIB file for your device.</li>
  <li><strong>authkey</strong> (<em>Inclusive</em>): Authentication key for SNMPv3. Variable privkey must also be set.</li>
  <li><strong>privkey</strong> (<em>Inclusive</em>): Privacy key SNMPv3. Variable authkey must also be set.</li>
--- a/components/downloader/index.html
+++ b/components/downloader/index.html
@ -86,7 +86,7 @@
  <li><strong>download_dir</strong> (<em>Required</em>): If the path is not absolute, it’s assumed to be relative to the Home Assistant configuration directory (eg. <code class="highlighter-rouge">.homeassistant/downloads</code>).</li>
 </ul>
 <h3><a class="title-link" name="use-the-service" href="#use-the-service"></a> Use the service</h3>
-<p>Go the the “Developer Tools”, then to “Call Service”, and choose <code class="highlighter-rouge">downloader/download_file</code> from the list of available services. Fill the “Service Data” field as shown in the example below and hit “CALL SERVICE”.</p>
+<p>Go to the “Developer Tools”, then to “Call Service”, and choose <code class="highlighter-rouge">downloader/download_file</code> from the list of available services. Fill the “Service Data” field as shown in the example below and hit “CALL SERVICE”.</p>
 <div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="nt">"url"</span><span class="p">:</span><span class="s2">"http://domain.tld/path/to/file"</span><span class="p">}</span><span class="w">
 </span></code></pre>
 </div>
--- a/components/joaoapps_join/index.html
+++ b/components/joaoapps_join/index.html
@ -74,7 +74,7 @@
    </h1>
  </header>
  <hr class="divider">
-  <p>The Join platform exposes services from <a href="http://joaoapps.com/join">Join</a>. In Home Assistant, the Join features are divided up in two locations, the Join component, and the Join notify platform. The notify platform allows us to send messages to Join devices, the the component allows us to access the other special features that Join offers.</p>
+  <p>The Join platform exposes services from <a href="http://joaoapps.com/join">Join</a>. In Home Assistant, the Join features are divided up in two locations, the Join component, and the Join notify platform. The notify platform allows us to send messages to Join devices, the component allows us to access the other special features that Join offers.</p>
 <p>In the <code class="highlighter-rouge">configuration.yaml</code> file you need to provide the api key and device id or name of the target device.  You can find your device id and api key <a href="https://joinjoaomgcd.appspot.com/">here</a>.</p>
 <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">notify</span><span class="pi">:</span>
--- a/components/lock/index.html
+++ b/components/lock/index.html
@ -80,7 +80,7 @@
  <li>Registers services <code class="highlighter-rouge">lock/lock</code> and <code class="highlighter-rouge">lock/unlock</code> to control locks.</li>
 </ul>
 <h3><a class="title-link" name="use-the-services" href="#use-the-services"></a> Use the services</h3>
-<p>Go the the <strong>Developer Tools</strong>, then to <strong>Call Service</strong> in the frontend, and choose <code class="highlighter-rouge">lock/lock</code> or <code class="highlighter-rouge">lock/unlock</code> from the list of available services (<strong>Available services:</strong> on the left). Enter something like the sample below into the <strong>Service Data</strong> field and hit <strong>CALL SERVICE</strong>.</p>
+<p>Go to the <strong>Developer Tools</strong>, then to <strong>Call Service</strong> in the frontend, and choose <code class="highlighter-rouge">lock/lock</code> or <code class="highlighter-rouge">lock/unlock</code> from the list of available services (<strong>Available services:</strong> on the left). Enter something like the sample below into the <strong>Service Data</strong> field and hit <strong>CALL SERVICE</strong>.</p>
 <div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="nt">"entity_id"</span><span class="p">:</span><span class="s2">"lock.front_door"</span><span class="p">}</span><span class="w">
 </span></code></pre>
 </div>
--- a/components/media_player.anthemav/index.html
+++ b/components/media_player.anthemav/index.html
@ -74,7 +74,7 @@
    </h1>
  </header>
  <hr class="divider">
-  <p>Both <a href="http://www.anthemav.com/">Anthem</a>’s current and last generation of A/V Receivers and and Processors support IP-based, network control. This Home Assistant platform adds proper “local push” support for any of these receivers on your network.</p>
+  <p>Both <a href="http://www.anthemav.com/">Anthem</a>’s current and last generation of A/V Receivers and Processors support IP-based, network control. This Home Assistant platform adds proper “local push” support for any of these receivers on your network.</p>
 <h2><a class="title-link" name="supported-models" href="#supported-models"></a> Supported Models</h2>
 <ul>
  <li>MRX 520, MRX 720, MRX 1120, and AVM 60</li>
--- a/components/media_player.directv/index.html
+++ b/components/media_player.directv/index.html
@ -74,7 +74,7 @@
    </h1>
  </header>
  <hr class="divider">
-  <p>Master <a href="http://www.directv.com/">DirecTV</a> receivers (ie: those that have tuners) will be automatically discovered if you enable the <a href="/components/discovery/">discovery component</a> and the the receiver is powered-on. Slave/RVU client/Genie boxes will also be discovered, but only if they are also online at the time of discovery.</p>
+  <p>Master <a href="http://www.directv.com/">DirecTV</a> receivers (ie: those that have tuners) will be automatically discovered if you enable the <a href="/components/discovery/">discovery component</a> and the receiver is powered-on. Slave/RVU client/Genie boxes will also be discovered, but only if they are also online at the time of discovery.</p>
 <p>To ensure that your DirecTV boxes are always found and configured, they should be added into your <code class="highlighter-rouge">configuration.yaml</code>.</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
 <span class="s">media_player</span><span class="pi">:</span>
--- a/components/plant/index.html
+++ b/components/plant/index.html
@ -117,7 +117,7 @@
 <h3>Using plain MQTT sensor to get the data</h3>
 <p>This is a practical example that uses a multiple of <code class="highlighter-rouge">MQTT sensors</code> to supply the readings used by the <code class="highlighter-rouge">plant</code> sensor.
 Another good source of this data would be the <a href="https://home-assistant.io/components/sensor.miflora/">Mi Flora</a> component.</p>
-<p>If the sensor data within the the min/max values the status will be <code class="highlighter-rouge">ok</code>, if not the status will be <code class="highlighter-rouge">problem</code>. You can use this to trigger a notification, if there is a problem with your plant. Of course you can only monitor attributes of your plant, where the sensor is configured and is providing the data.</p>
+<p>If the sensor data is within the min/max values the status will be <code class="highlighter-rouge">ok</code>, if not the status will be <code class="highlighter-rouge">problem</code>. You can use this to trigger a notification, if there is a problem with your plant. Of course you can only monitor attributes of your plant, where the sensor is configured and is providing the data.</p>
 <h2>Data Source</h2>
 <p>The main sources of the data will usually be a <a href="sensor.miflora">MiFlora sensor</a> or a <a href="sensor.mqtt">MQTT sensor</a> receiving the data from a <a href="https://github.com/ChristianKuehnel/plantgateway">PlantGateway</a>.</p>
 <p>If you want to get the date via a PlantGateway, this is a typical configuration for the MQTT sensors:</p>
--- a/components/remote/index.html
+++ b/components/remote/index.html
@ -80,7 +80,7 @@
  <li>Registers services <code class="highlighter-rouge">remote/turn_on</code>, <code class="highlighter-rouge">remote/turn_off</code>, <code class="highlighter-rouge">remote/toggle</code>, <code class="highlighter-rouge">remote/sync</code>, and <code class="highlighter-rouge">remote/send_command</code> to control remotes.</li>
 </ul>
 <h3><a class="title-link" name="use-the-services" href="#use-the-services"></a> Use the services</h3>
-<p>Go the the <strong>Developer Tools</strong>, then to <strong>Call Service</strong> in the frontend, and choose <code class="highlighter-rouge">remote/turn_on</code>, <code class="highlighter-rouge">remote/turn_off</code>, or <code class="highlighter-rouge">remote/toggle</code> from the list of available services (<strong>Available services:</strong> on the left). Enter something like the sample below into the <strong>Service Data</strong> field and hit <strong>Call Service</strong>.</p>
+<p>Go to the <strong>Developer Tools</strong>, then to <strong>Call Service</strong> in the frontend, and choose <code class="highlighter-rouge">remote/turn_on</code>, <code class="highlighter-rouge">remote/turn_off</code>, or <code class="highlighter-rouge">remote/toggle</code> from the list of available services (<strong>Available services:</strong> on the left). Enter something like the sample below into the <strong>Service Data</strong> field and hit <strong>Call Service</strong>.</p>
 <div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="nt">"entity_id"</span><span class="p">:</span><span class="s2">"remote.family_room"</span><span class="p">}</span><span class="w">
 </span></code></pre>
 </div>
--- a/components/sensor.arest/index.html
+++ b/components/sensor.arest/index.html
@ -91,7 +91,7 @@
 <p>Configuration variables:</p>
 <ul>
  <li><strong>resource</strong> (<em>Required</em>): IP address and schema of the device that is exposing an aREST API, e.g. http://192.168.1.10.</li>
-  <li><strong>name</strong> (<em>Optional</em>): Let you overwrite the the name of the device. By default <em>name</em> from the device is used.</li>
+  <li><strong>name</strong> (<em>Optional</em>): Let you overwrite the name of the device. By default <em>name</em> from the device is used.</li>
  <li><strong>monitored_variables</strong> array (<em>Optional</em>): List of exposed variables.
    <ul>
      <li><strong>[variable]</strong> (<em>Required</em>): Name of the variable to monitor.
--- a/components/sensor.citybikes/index.html
+++ b/components/sensor.citybikes/index.html
@ -86,8 +86,8 @@
 <ul>
  <li><strong>name</strong> (<em>Optional</em>): The base name of this group of monitored stations. The entity ID of every monitored station in this group will be prefixed with this base name, in addition to the network ID.</li>
  <li><strong>network</strong> (<em>Optional</em>):  The name of the bike sharing system to poll. Defaults to the system that operates in the monitored location.</li>
-  <li><strong>latitude</strong> (<em>Optional</em>):  Latitude of the location, around which bike stations are monitored. Defaults to the latitude in your your <code class="highlighter-rouge">configuration.yaml</code> file.</li>
+  <li><strong>latitude</strong> (<em>Optional</em>):  Latitude of the location, around which bike stations are monitored. Defaults to the latitude in your <code class="highlighter-rouge">configuration.yaml</code> file.</li>
-  <li><strong>longitude</strong> (<em>Optional</em>):  Longitude of the location, around which bike stations are monitored. Defaults to the longitude in your your <code class="highlighter-rouge">configuration.yaml</code> file.</li>
+  <li><strong>longitude</strong> (<em>Optional</em>):  Longitude of the location, around which bike stations are monitored. Defaults to the longitude in your <code class="highlighter-rouge">configuration.yaml</code> file.</li>
  <li><strong>radius</strong> (<em>Optional</em>):  The radius (in meters or feet, depending on the Home Assistant configuration) around the monitored location. Only stations closer than this distance will be monitored.</li>
  <li><strong>stations</strong> array (<em>Optional</em>): A list of specific stations to monitor. The list should contain station <code class="highlighter-rouge">ID</code>s or <code class="highlighter-rouge">UID</code>s, which can be obtained from the CityBikes API.</li>
 </ul>
--- a/components/sensor.dweet/index.html
+++ b/components/sensor.dweet/index.html
@ -87,7 +87,7 @@
 <ul>
  <li><strong>device</strong> (<em>Required</em>): Identification of the device (also known as <code class="highlighter-rouge">thing</code>).</li>
  <li><strong>value_template</strong> (<em>Required</em>): The variable to extract a value from the content.</li>
-  <li><strong>name</strong> (<em>Optional</em>): Let you overwrite the the name of the device in the frontend.</li>
+  <li><strong>name</strong> (<em>Optional</em>): Let you overwrite the name of the device in the frontend.</li>
  <li><strong>unit_of_measurement</strong> (<em>Optional</em>): Defines the unit of measurement of the sensor, if any.</li>
 </ul>
 <h3><a class="title-link" name="full-configuration-sample" href="#full-configuration-sample"></a> Full configuration sample</h3>
--- a/components/sensor.loop_energy/index.html
+++ b/components/sensor.loop_energy/index.html
@ -74,9 +74,9 @@
    </h1>
  </header>
  <hr class="divider">
-  <p>Integrate your <a href="https://www.your-loop.com/">Loop Energy</a> meter information into Home Assistant. To use this sensor you need the the client serial number and secret keys for your devices.</p>
+  <p>Integrate your <a href="https://www.your-loop.com/">Loop Energy</a> meter information into Home Assistant. To use this sensor you need the client serial number and secret keys for your devices.</p>
 <p>The library used to get the data isn’t officially supported and the only way to get the keys is to log into loop energy’s website and type a command into your browser console.</p>
-<p>To do this log into <a href="https://www.your-loop.com/">Loop Energy</a>. Once you’re logged in you should be able see see your live readings on the web page.</p>
+<p>To do this log into <a href="https://www.your-loop.com/">Loop Energy</a>. Once you’re logged in you should be able see your live readings on the web page.</p>
 <p>You can then open your browser’s console window, how you do this varies by browser but in Chrome you click on `More Tools / Developer Tools’ and click on the console window. You then type:</p>
 <p><code class="highlighter-rouge">Drupal.settings.navetas_realtime.</code></p>
 <p>This should show something like</p>
--- a/components/sensor.snmp/index.html
+++ b/components/sensor.snmp/index.html
@ -88,7 +88,7 @@
  <li><strong>host</strong> (<em>Required</em>): The IP address of your host, eg. <code class="highlighter-rouge">192.168.1.32</code>.</li>
  <li><strong>baseoid</strong> (<em>Required</em>): The OID where the information is located. It’s advised to use the numerical notation.</li>
  <li><strong>port</strong> (<em>Option</em>): The SNMP port of your host. Defaults to <code class="highlighter-rouge">161</code>.</li>
-  <li><strong>community</strong> (<em>Optional</em>): The SNMP community which is set for the device. Most devices have a default community set to to <code class="highlighter-rouge">public</code> with read-only permission (which is sufficient).</li>
+  <li><strong>community</strong> (<em>Optional</em>): The SNMP community which is set for the device. Most devices have a default community set to <code class="highlighter-rouge">public</code> with read-only permission (which is sufficient).</li>
  <li><strong>version</strong> (<em>Optional</em>) version of SNMP protocol, <code class="highlighter-rouge">1</code> or <code class="highlighter-rouge">2c</code>. Defaults to <code class="highlighter-rouge">1</code>. Version <code class="highlighter-rouge">2c</code> is needed to read data from 64-bit counters.</li>
  <li><strong>name</strong> (<em>Optional</em>): Name of the SNMP sensor.</li>
  <li><strong>unit_of_measurement</strong> (<em>Optional</em>): Defines the unit of measurement of the sensor, if any.</li>
--- a/components/sensor.uber/index.html
+++ b/components/sensor.uber/index.html
@ -86,7 +86,7 @@
 <p>Configuration variables:</p>
 <ul>
  <li><strong>server_token</strong> (<em>Required</em>): A server token obtained from <a href="https://developer.uber.com">developer.uber.com</a> after <a href="https://developer.uber.com/dashboard/create">creating an app</a>.</li>
-  <li><strong>start_latitude</strong> (<em>Optional</em>): The starting latitude for a trip. Defaults to the latitude in your your <code class="highlighter-rouge">configuration.yaml</code> file.</li>
+  <li><strong>start_latitude</strong> (<em>Optional</em>): The starting latitude for a trip. Defaults to the latitude in your <code class="highlighter-rouge">configuration.yaml</code> file.</li>
  <li><strong>start_longitude</strong> (<em>Optional</em>): The starting longitude for a trip. Defaults to the longitude in your <code class="highlighter-rouge">configuration.yaml</code> file.</li>
  <li><strong>end_latitude</strong> (<em>Optional</em>): The ending latitude for a trip. While <code class="highlighter-rouge">end_latitude</code> is optional, it is strongly recommended to provide an <code class="highlighter-rouge">end_latitude</code>/<code class="highlighter-rouge">end_longitude</code> when possible as you will get more accurate price and time estimates.</li>
  <li><strong>end_longitude</strong> (<em>Optional</em>): The ending longitude for a trip. While <code class="highlighter-rouge">end_longitude</code> is optional, it is strongly recommended to provide an <code class="highlighter-rouge">end_latitude</code>/<code class="highlighter-rouge">end_longitude</code> when possible as you will get more accurate price and time estimates.</li>
--- a/components/switch.arest/index.html
+++ b/components/switch.arest/index.html
@ -99,7 +99,7 @@
 <p>Configuration variables:</p>
 <ul>
  <li><strong>resource</strong> (<em>Required</em>): IP address and schema of the device that is exposing an aREST API, eg. http://192.168.1.10 (no-trailing slash)</li>
-  <li><strong>name</strong> (<em>Optional</em>): Let you overwrite the the name of the device. By default <em>name</em> from the device is used.</li>
+  <li><strong>name</strong> (<em>Optional</em>): Let you overwrite the name of the device. By default <em>name</em> from the device is used.</li>
  <li><strong>pins</strong> array (<em>Optional</em>): An array with all used pins.
    <ul>
      <li><strong>name</strong> (<em>Required</em>): The name of the pin to use in the frontend.</li>
--- a/components/switch.flux/index.html
+++ b/components/switch.flux/index.html
@ -75,8 +75,8 @@
  </header>
  <hr class="divider">
  <p>The <code class="highlighter-rouge">flux</code> switch platform will change the temperature of your lights similar to the way flux works on your computer, using circadian rhythm. They will be bright during the day, and gradually fade to a red/orange at night.</p>
-<p>The component will update your lights based on the the time of day. It will only affect lights that are turned on and listed in the flux configuration.</p>
+<p>The component will update your lights based on the time of day. It will only affect lights that are turned on and listed in the flux configuration.</p>
-<p>During the day (in between <code class="highlighter-rouge">start time</code> and <code class="highlighter-rouge">sunset time</code>), it will fade the lights from the <code class="highlighter-rouge">start_colortemp</code> to the <code class="highlighter-rouge">sunset_colortemp</code>.  After sunset (between <code class="highlighter-rouge">sunset_time</code> and <code class="highlighter-rouge">stop_time</code>), the lights will fade from the the <code class="highlighter-rouge">sunset_colortemp</code> to the <code class="highlighter-rouge">stop_colortemp</code>. If the lights are still on after the <code class="highlighter-rouge">stop_time</code> it will continue to change the light to the <code class="highlighter-rouge">stop_colortemp</code> until the light is turned off. The fade effect is created by updating the lights every 30 seconds with a 30 second transition time.</p>
+<p>During the day (in between <code class="highlighter-rouge">start time</code> and <code class="highlighter-rouge">sunset time</code>), it will fade the lights from the <code class="highlighter-rouge">start_colortemp</code> to the <code class="highlighter-rouge">sunset_colortemp</code>.  After sunset (between <code class="highlighter-rouge">sunset_time</code> and <code class="highlighter-rouge">stop_time</code>), the lights will fade from the <code class="highlighter-rouge">sunset_colortemp</code> to the <code class="highlighter-rouge">stop_colortemp</code>. If the lights are still on after the <code class="highlighter-rouge">stop_time</code> it will continue to change the light to the <code class="highlighter-rouge">stop_colortemp</code> until the light is turned off. The fade effect is created by updating the lights every 30 seconds with a 30 second transition time.</p>
 <p>If you don’t wish to have flux update on 30 second intervals, you can leave the switch turned off and use automation rules that call the service <code class="highlighter-rouge">switch.&lt;name&gt;_update</code> whenever you want the lights updated, where <code class="highlighter-rouge">&lt;name&gt;</code> equals the <code class="highlighter-rouge">name:</code> property in the switch configuration.</p>
 <p>To use the Flux switch in 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>
--- a/components/switch/index.html
+++ b/components/switch/index.html
@ -80,7 +80,7 @@
  <li>Registers services <code class="highlighter-rouge">switch/turn_on</code>, <code class="highlighter-rouge">switch/turn_off</code>, and <code class="highlighter-rouge">switch/toggle</code> to control switches.</li>
 </ul>
 <h3><a class="title-link" name="use-the-services" href="#use-the-services"></a> Use the services</h3>
-<p>Go the the <strong>Developer Tools</strong>, then to <strong>Call Service</strong> in the frontend, and choose <code class="highlighter-rouge">switch/turn_on</code> or <code class="highlighter-rouge">switch/turn_off</code> from the list of available services (<strong>Available services:</strong> on the left). Enter something like the sample below into the <strong>Service Data</strong> field and hit <strong>CALL SERVICE</strong>.</p>
+<p>Go the <strong>Developer Tools</strong>, then to <strong>Call Service</strong> in the frontend, and choose <code class="highlighter-rouge">switch/turn_on</code> or <code class="highlighter-rouge">switch/turn_off</code> from the list of available services (<strong>Available services:</strong> on the left). Enter something like the sample below into the <strong>Service Data</strong> field and hit <strong>CALL SERVICE</strong>.</p>
 <div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="nt">"entity_id"</span><span class="p">:</span><span class="s2">"livingroom_pin2"</span><span class="p">}</span><span class="w">
 </span></code></pre>
 </div>
--- a/components/telegram_bot.webhooks/index.html
+++ b/components/telegram_bot.webhooks/index.html
@ -101,7 +101,7 @@
  <li><strong>proxy_params</strong> (<em>Optional</em>): Proxy configuration parameters, as dict, if working behind a proxy (<code class="highlighter-rouge">username</code>, <code class="highlighter-rouge">password</code>, etc.)</li>
  <li><strong>url</strong> (<em>Optional</em>): Allow to overwrite the <code class="highlighter-rouge">base_url</code> from the <a href="/components/http/"><code class="highlighter-rouge">http</code></a> component for different configurations (<code class="highlighter-rouge">https://&lt;public_url&gt;:&lt;port&gt;</code>).</li>
 </ul>
-<p>To get your <code class="highlighter-rouge">chat_id</code> and <code class="highlighter-rouge">api_key</code> follow the instructions <a href="/components/notify.telegram">here</a>. As well as authorizing the chat, if you have added your bot to a group you will also need to authorize any user that will be interacting with the webhook. When an unauthorized user tries to interact with the webhook Home Assistant will raise an error (“Incoming message is not allowed”), you can easily obtain the the users id by looking in the “from” section of this error message.</p>
+<p>To get your <code class="highlighter-rouge">chat_id</code> and <code class="highlighter-rouge">api_key</code> follow the instructions <a href="/components/notify.telegram">here</a>. As well as authorizing the chat, if you have added your bot to a group you will also need to authorize any user that will be interacting with the webhook. When an unauthorized user tries to interact with the webhook Home Assistant will raise an error (“Incoming message is not allowed”), you can easily obtain the users id by looking in the “from” section of this error message.</p>
 <p>Full configuration sample:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
 <span class="s">http</span><span class="pi">:</span>
--- a/developers/development_environment/index.html
+++ b/developers/development_environment/index.html
@ -88,7 +88,7 @@
 <p class="note">
 Different distributions have different package installation mechanisms and sometimes packages names as well. For example Centos would use: <code class="highlighter-rouge">sudo yum install epel-release &amp;&amp; sudo yum install python34 python34-devel mysql-devel</code>
 </p>
-<p>Additional dependencies exist if you you plan to perform Frontend Development, please read the <a href="https://home-assistant.io/developers/frontend/">Frontend</a> section to learn more.</p>
+<p>Additional dependencies exist if you plan to perform Frontend Development, please read the <a href="https://home-assistant.io/developers/frontend/">Frontend</a> section to learn more.</p>
 <h4><a class="title-link" name="developing-on-windows" href="#developing-on-windows"></a> Developing on Windows</h4>
 <p>If you are using Windows as a development platform, make sure that you have the correct Microsoft Visual C++ build tools installed. Check the <a href="https://wiki.python.org/moin/WindowsCompilers">Windows Compilers</a> section on the <a href="https://www.python.org/">Python website</a> for details. Validation using <code class="highlighter-rouge">tox</code> will fail if this is not done correctly.</p>
 <p>Also, make sure to install or upgrade the <code class="highlighter-rouge">setuptools</code> Python package. It contains compatibility improvements and adds automatic use of compilers:</p>
--- a/docs/installation/hassbian/common-tasks/index.html
+++ b/docs/installation/hassbian/common-tasks/index.html
@ -85,7 +85,7 @@ Linux and Mac OS users execute the following command in a terminal.</p>
 <p>Windows users start <a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Putty</a>, enter the IP address of the Raspberry Pi in the <em>Host name</em> field and port 22 in the <em>Port</em> field. Then click <em>Open</em> and a terminal window will open. Enter the credentials. Default user name is <code class="highlighter-rouge">pi</code> and password is <code class="highlighter-rouge">raspberry</code>.</p>
 <p>Optionally, starting with Windows 10 anniversary update, you can use the built-in ‘<a href="https://msdn.microsoft.com/en-us/commandline/wsl/about">Bash on Windows</a>’ to use SSH if you have enabled Developer mode and have installed the “Windows Subsystem for Linux (beta)” feature.</p>
 <h3><a class="title-link" name="startstoprestart-home-assistant" href="#startstoprestart-home-assistant"></a> Start/Stop/Restart Home Assistant</h3>
-<p>Log in as the <code class="highlighter-rouge">pi</code> account account and execute the following commands:</p>
+<p>Log in as the <code class="highlighter-rouge">pi</code> account and execute the following commands:</p>
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo systemctl stop home-assistant@homeassistant.service 
 </code></pre>
 </div>
--- a/docs/installation/synology/index.html
+++ b/docs/installation/synology/index.html
@ -237,7 +237,7 @@ esac
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c"># chmod 777 /volume1/homeassistant/hass-daemon</span>
 </code></pre>
 </div>
-<p>Update your firewall (if it is turned on on the Synology device):</p>
+<p>Update your firewall (if it is turned on the Synology device):</p>
 <ul>
  <li>Go to your Synology control panel</li>
  <li>Go to security</li>
--- a/docs/tools/scripts/index.html
+++ b/docs/tools/scripts/index.html
@ -75,7 +75,7 @@
    </h1>
  </header>
  <hr class="divider">
-  <p>The command-line and the frontend which simplify common tasks, are helping with migrations, and ensure that Home Assistant runs properly. Please do not confuse those with with Home Assistant’s <a href="/docs/scripts/">script</a> feature.</p>
+  <p>The command-line and the frontend which simplify common tasks, are helping with migrations, and ensure that Home Assistant runs properly. Please do not confuse those with Home Assistant’s <a href="/docs/scripts/">script</a> feature.</p>
 <h3><a class="title-link" name="configuration-check" href="#configuration-check"></a> Configuration check</h3>
 <p>Test any changes to your <code class="highlighter-rouge">configuration.yaml</code> file before launching Home Assistant. This script allows you to test changes without the need to restart Home Assistant.</p>
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>hass --script check_config
--- a/sitemap.xml
+++ b/sitemap.xml
@ -3374,7 +3374,7 @@
 </url>
 <url>
 <loc>https://home-assistant.io/components/switch.hook/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/cookbook/automation_for_rainy_days/</loc>
@ -4006,99 +4006,99 @@
 </url>
 <url>
 <loc>https://home-assistant.io/docs/autostart/init.d/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/appdaemon/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/appdaemon/api/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/appdaemon/configuration/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/appdaemon/example_apps/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/appdaemon/installation/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/appdaemon/operation/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/appdaemon/reboot/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/appdaemon/running/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/appdaemon/tutorial/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/appdaemon/updating/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/appdaemon/windows/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/certificates/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/hadashboard/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/hass-configurator/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/ios/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/nginx/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/notebooks/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/scenegen/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/ecosystem/synology/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/tools/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/tools/dev-tools/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/tools/hass/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/docs/tools/scripts/</loc>
-<lastmod>2017-09-26T16:07:55+00:00</lastmod>
+<lastmod>2017-09-26T18:31:09+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/faq/after-upgrading/</loc>
@ -5110,62 +5110,62 @@
 </url>
 <url>
 <loc>https://home-assistant.io/demo/frontend.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:34+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/index.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:34+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-dev-event.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:34+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-dev-info.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:34+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-dev-service.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:34+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-dev-state.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:34+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-dev-template.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:34+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-history.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:34+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-iframe.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:34+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-logbook.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:34+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/demo/panels/ha-panel-map.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:34+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/googlef4f3693c209fe788.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:34+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:35+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:35+00:00</lastmod>
 </url>
 <url>
 <loc>https://home-assistant.io/static/mdi-demo.html</loc>
-<lastmod>2017-09-26T16:06:57+00:00</lastmod>
+<lastmod>2017-09-26T18:30:35+00:00</lastmod>
 </url>
 </urlset>