Site updated at 2017-09-26 07:14:23 UTC

components/alarm_control_panel.egardia/index.html

@@ -99,7 +99,7 @@
 <p>Note that this basic configuration will only enable you to read the armed/armed away/disarmed status of your alarm and will <strong>not</strong> update the status if the alarm is triggered. This is because of how Egardia built their system. The alarm triggers normally go through their servers.
 You can change this, however, using the following procedure. This is a more advanced configuration.</p>
 <ol>
-  <li>Log in into your alarm system’s control panel. You will need to access http://[ip of your control panel]. You know this already since you need it in the basic configuration from above. Log in to the control panel with your Egardia/Woonveilig username and password.</li>
+  <li>Log in into your alarm system’s control panel. You will need to access http://[IP of your control panel]. You know this already since you need it in the basic configuration from above. Log in to the control panel with your Egardia/Woonveilig username and password.</li>
   <li>Once logged in, go to <em>System Settings</em>, <em>Report</em> and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. Also, update the port number 85 or to anything you like. The provided software that you will set up in the next steps runs on port 85 by default. <strong>Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia’s / Woonveilig services.</strong> Maybe, that is just what you want. Make sure to save your settings by selecting ‘OK’.</li>
   <li>On your Home Assistant machine run <code class="highlighter-rouge">$ sudo python3 egardiaserver.py</code>. Refer to the <a href="https://github.com/jeroenterheerdt/python-egardia">python-egardia repository</a> for detailed documentation on parameters. This will receive status codes from your alarm control panel and display them. You will need the codes to include in your configuration.yaml. Make sure to change the status of your alarm to all states (disarm, arm, armhome) as well as trigger the alarm in all ways possible to get 100% coverage. <strong>Before triggering the alarm it might be good to disable the siren temporarily (can be done in Panel Settings).</strong></li>
   <li>Once you have the codes, update your <code class="highlighter-rouge">configuration.yaml</code>:

components/alert/index.html

@@ -127,7 +127,7 @@
 </code></pre>
 </div>
 <h3><a class="title-link" name="complex-alert-criteria" href="#complex-alert-criteria"></a> Complex Alert Criteria</h3>
-<p>By design, the <code class="highlighter-rouge">alert</code> component only handles very simple criteria for firing. That is, it only checks if a single entity’s state is equal to a value. At some point, it may be desireable to have an alert with a more complex criteria. Possibly, when a battery percentage falls below a threshold. Maybe you want to disable the alert on certain days. Maybe the alert firing should depend on more than one input. For all of these situations, it is best to use the alert in conjunction with a <code class="highlighter-rouge">Template Binary Sensor</code>. The following example does that.</p>
+<p>By design, the <code class="highlighter-rouge">alert</code> component only handles very simple criteria for firing. That is, it only checks if a single entity’s state is equal to a value. At some point, it may be desirable to have an alert with a more complex criteria. Possibly, when a battery percentage falls below a threshold. Maybe you want to disable the alert on certain days. Maybe the alert firing should depend on more than one input. For all of these situations, it is best to use the alert in conjunction with a <code class="highlighter-rouge">Template Binary Sensor</code>. The following example does that.</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">binary_sensor</span><span class="pi">:</span>
   <span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">template</span>
     <span class="s">sensors</span><span class="pi">:</span>
@@ -147,7 +147,7 @@
 </div>
 <p>This example will begin firing as soon as the entity <code class="highlighter-rouge">sensor.motion</code>’s <code class="highlighter-rouge">battery</code> attribute falls below 15. It will continue to fire until the battery attribute raises above 15 or the alert is acknowledged on the frontend.</p>
 <h3><a class="title-link" name="dynamic-notification-delay-times" href="#dynamic-notification-delay-times"></a> Dynamic Notification Delay Times</h3>
-<p>It may be desireable to have the delays between alert notifications dynamically change as the alert continues to fire. This can be done by setting the <code class="highlighter-rouge">repeat</code> configuration key to a list of numbers rather than a single number. Altering the first example would look like the following.</p>
+<p>It may be desirable to have the delays between alert notifications dynamically change as the alert continues to fire. This can be done by setting the <code class="highlighter-rouge">repeat</code> configuration key to a list of numbers rather than a single number. Altering the first example would look like the following.</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
 <span class="s">alert</span><span class="pi">:</span>
   <span class="s">garage_door</span><span class="pi">:</span>

components/alexa/index.html

@@ -87,7 +87,7 @@
   <iframe width="560" height="315" src="https://www.youtube.com/embed/1Ke3mtWd_cQ" frameborder="0" allowfullscreen=""></iframe>
 </div>
 <h3><a class="title-link" name="requirements" href="#requirements"></a> Requirements</h3>
-<p>Amazon requires the endpoint of a skill to be hosted via SSL. Self-signed certificates are ok because our skills will only run in development mode. Read more on <a href="https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/">our blog</a> about how to set up encryption for Home Assistant. When running Hass.io, using the <a href="/addons/lets_encrypt/">Let’s Encrypt</a> the and <a href="/addons/duckdns/">Duck DNS</a> add-ons is the easiest method. If you are unable to get HTTPS up and running, consider using <a href="https://community.home-assistant.io/t/aws-lambda-proxy-custom-alexa-skill-when-you-dont-have-https/5230">this AWS Lambda proxy for Alexa skills</a>.</p>
+<p>Amazon requires the endpoint of a skill to be hosted via SSL. Self-signed certificates are OK because our skills will only run in development mode. Read more on <a href="https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/">our blog</a> about how to set up encryption for Home Assistant. When running Hass.io, using the <a href="/addons/lets_encrypt/">Let’s Encrypt</a> the and <a href="/addons/duckdns/">Duck DNS</a> add-ons is the easiest method. If you are unable to get HTTPS up and running, consider using <a href="https://community.home-assistant.io/t/aws-lambda-proxy-custom-alexa-skill-when-you-dont-have-https/5230">this AWS Lambda proxy for Alexa skills</a>.</p>
 <p>Additionally, note that at the time of this writing, your Alexa skill endpoint <em>must</em> accept requests over port 443 (Home Assistant default to 8123). There are two ways you can handle this:</p>
 <ol>
   <li>In your router, forward external 443 to your Home Assistant serving port (defaults to 8123)
@@ -305,7 +305,7 @@ Custom slot type for script support.
           <span class="no">{% endif %}</span>
 </code></pre>
 </div>
-<p>You can add multiple items for a feed if you want. The Amazon required uid and timestamp will be randomly generated at startup and change at every restart of Home Assistant.</p>
+<p>You can add multiple items for a feed if you want. The Amazon required UID and timestamp will be randomly generated at startup and change at every restart of Home Assistant.</p>
 <p>Please refer to the <a href="https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/flash-briefing-skill-api-feed-reference">Amazon documentation</a> for more information about allowed configuration parameters and formats.</p>
 <h3><a class="title-link" name="configuring-your-flash-briefing-skill" href="#configuring-your-flash-briefing-skill"></a> Configuring your Flash Briefing skill</h3>
 <ul>

components/axis/index.html

@@ -89,6 +89,13 @@
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>ln -s /usr/lib/python3/dist-packages/gi /srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages
 </code></pre>
 </div>
+<p><a href="https://home-assistant.io/docs/installation/virtualenv/">Virtualenv</a> installation:</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>ln -s /usr/lib/python3/dist-packages/gi /srv/homeassistant/lib/python3.5/site-packages
+</code></pre>
+</div>
+<p class="note">
+  Adjust “python3.5” in command above to match your version as stored in “/srv/homeassistant/lib/pythonX.X”
+</p>
 <p>You can also manually configure your devices by adding the following lines 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">axis</span><span class="pi">:</span>

components/binary_sensor.bayesian/index.html

@@ -98,7 +98,7 @@
       <li><strong>prob_given_true</strong> (<em>Required</em>): The probability of the observation occurring, given the event is <code class="highlighter-rouge">true</code>.</li>
       <li><strong>prob_given_false</strong> (<em>Optional</em>): The probability of the observation occurring, given the event is <code class="highlighter-rouge">false</code> can be set as well.  If <code class="highlighter-rouge">prob_given_false</code> is not set, it will default to <code class="highlighter-rouge">1 - prob_given_true</code>.</li>
       <li><strong>platform</strong> (<em>Required</em>): The only supported observation platforms are <code class="highlighter-rouge">state</code> and <code class="highlighter-rouge">numeric_state</code>, which are modeled after their corresponding triggers for automations.</li>
-      <li><strong>to_state</strong> (<em>Required</em>): THe target start.</li>
+      <li><strong>to_state</strong> (<em>Required</em>): The target start.</li>
     </ul>
   </li>
   <li><strong>probability_threshold</strong> (<em>Optional</em>): The probability at which the sensor should trigger to <code class="highlighter-rouge">on</code>.</li>

components/binary_sensor.enocean/index.html

@@ -88,7 +88,7 @@
   <li><strong>name</strong> (<em>Optional</em>): An identifier for the switch in the frontend.</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>
 </ul>
-<p>EnOcean binary sensors only generate ‘button_pressed’ events. The event data has follwing four fields:</p>
+<p>EnOcean binary sensors only generate ‘button_pressed’ events. The event data has following four fields:</p>
 <ul>
   <li><strong>id</strong>: The ID of the device (see configuration).</li>
   <li><strong>pushed</strong>: <code class="highlighter-rouge">1</code> for a button press, <code class="highlighter-rouge">0</code> for a button release.</li>

components/binary_sensor.flic/index.html

@@ -113,7 +113,7 @@
 <p>Event data:</p>
 <ul>
   <li><strong>button_name</strong>: The name of the button, that triggered the event.</li>
-  <li><strong>button_address</strong>: The bluetooth address of the button, that triggered the event.</li>
+  <li><strong>button_address</strong>: The Bluetooth address of the button, that triggered the event.</li>
   <li><strong>click_type</strong>: The type of click. Possible values are <code class="highlighter-rouge">single</code>, <code class="highlighter-rouge">double</code> and <code class="highlighter-rouge">hold</code>.</li>
   <li><strong>queued_time</strong>: The amount of time this event was queued on the button, in seconds.</li>
 </ul>

components/binary_sensor.hikvision/index.html

@@ -81,7 +81,7 @@
 binary_sensor.front_port_line_crossing
 </code></pre>
 </div>
-<p>When used with a NVR device the sensors will be appeneded with the channel number they represent.  For example, if you configure an NVR with the name “Home” that supports 2 cameras with motion detection and line crossing events enabled to notify the surveillance center the following binary sensors will be added to Home Assistant:</p>
+<p>When used with a NVR device the sensors will be appended with the channel number they represent.  For example, if you configure an NVR with the name “Home” that supports 2 cameras with motion detection and line crossing events enabled to notify the surveillance center the following binary sensors will be added to Home Assistant:</p>
 <div class="highlighter-rouge"><pre class="highlight"><code>binary_sensor.home_motion_1
 binary_sensor.home_motion_2
 binary_sensor.home_line_crossing_1

components/binary_sensor.mqtt/index.html

@@ -92,7 +92,7 @@
   <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>value_template</strong> (<em>Optional</em>): Defines a <a href="/docs/configuration/templating/#processing-incoming-data">template</a> to extract a value from the payload.</li>
 </ul>
-<p>For a quick check you can use the commandline tools shipped with <code class="highlighter-rouge">mosquitto</code> to send MQTT messages. Set the state of a sensor manually:</p>
+<p>For a quick check you can use the command line tools shipped with <code class="highlighter-rouge">mosquitto</code> to send MQTT messages. Set the state of a sensor manually:</p>
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$  </span>mosquitto_pub -h 127.0.0.1 -t home-assistant/window/contact -m <span class="s2">"OFF"</span>
 </code></pre>
 </div>

components/binary_sensor.mystrom/index.html

@@ -95,7 +95,7 @@
 </div>
 <h3><a class="title-link" name="setup-of-the-mystrom-buttons" href="#setup-of-the-mystrom-buttons"></a> Setup of the myStrom Buttons</h3>
 <p>You need to configure every button to make it work with Home Assistant. First connect the Wifi Buttons to your wireless network. Keep in mind that they only support WPS (Wi-FI Protected Setup). Once a button is connected you have three minutes to set the actions for the push patterns. The fastest way is to use <code class="highlighter-rouge">curl</code>. Check the <a href="https://mystrom.ch/wp-content/uploads/REST_API_WBP.txt">documentation</a> of the WiFi Button for further details about the implementation (<code class="highlighter-rouge">http://</code> is replaced by <code class="highlighter-rouge">get://</code> or <code class="highlighter-rouge">post://</code>). <code class="highlighter-rouge">action</code> is the name of the corresponding push pattern (see above).</p>
-<p>The endpoint that is recieving the data is <code class="highlighter-rouge">[IP address Home Assistant]:8123/api/mystrom</code>.</p>
+<p>The endpoint that is receiving the data is <code class="highlighter-rouge">[IP address Home Assistant]:8123/api/mystrom</code>.</p>
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>curl -d <span class="s2">"[action]=get://[IP address Home Assistant]:8123/api/mystrom?[action]%3D[ID of the button]"</span> http://[IP address of the button]/api/v1/device/[MAC address of the button]
 <span class="o">{</span>
   <span class="s2">"[MAC address of the button]"</span>: <span class="o">{</span>

components/binary_sensor.pilight/index.html

@@ -74,7 +74,7 @@
     </h1>
   </header>
   <hr class="divider">
-  <p>The <code class="highlighter-rouge">pilight</code> binary sensor platform implement the <a href="/components/pilight/">pilight hub</a> binary sensor functionality. Two type of Pilight binary sensor configuration available. A normal sensor which send the on and off state cyclical and a trigger sensor which send only a trigger when an event happend (for example lots of cheap PIR motion detector).</p>
+  <p>The <code class="highlighter-rouge">pilight</code> binary sensor platform implement the <a href="/components/pilight/">pilight hub</a> binary sensor functionality. Two type of Pilight binary sensor configuration available. A normal sensor which send the on and off state cyclical and a trigger sensor which send only a trigger when an event happened (for example lots of cheap PIR motion detector).</p>
 <p>To enable a Pilight binary sensor 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.yml entry</span>
 <span class="s">binary_sensor</span><span class="pi">:</span>

components/binary_sensor.rfxtrx/index.html

@@ -84,7 +84,7 @@
   <span class="s">automatic_add</span><span class="pi">:</span> <span class="s">True</span>
 </code></pre>
 </div>
-<p>Open your local home-assistant web UI and go to the “states” page. Then make sure to trigger your sensor. You should see a new entity appear in the <em>Current entites</em> list, starting with “binary_sensor.” and some hexadecimal digits. Those hexadecimal digits are your device id.</p>
+<p>Open your local home-assistant web UI and go to the “states” page. Then make sure to trigger your sensor. You should see a new entity appear in the <em>Current entities</em> list, starting with “binary_sensor.” and some hexadecimal digits. Those hexadecimal digits are your device id.</p>
 <p>For example: “binary_sensor.0913000022670e013b70”. Here your device id is <code class="highlighter-rouge">0913000022670e013b70</code>. Then you should update your configuration to:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
 <span class="s">binary_sensor</span><span class="pi">:</span>
@@ -120,7 +120,7 @@
 </code></pre>
 </div>
 <h2>Options for PT-2262 devices under the Lighting4 protocol</h2>
-<p>When a data packet is transmitted by a PT-2262 device using the Lighting4 protocol, there is no way to automatically extract the device identifier and the command from the packet. Each device has its own id/command length combination and the fields lengths are not included in the data. One device that sends 2 different commands will be seen as 2 devices on Home Assistant. For sur cases, the following options are available in order to circumvent the problem:</p>
+<p>When a data packet is transmitted by a PT-2262 device using the Lighting4 protocol, there is no way to automatically extract the device identifier and the command from the packet. Each device has its own id/command length combination and the fields lengths are not included in the data. One device that sends 2 different commands will be seen as 2 devices on Home Assistant. For such cases, the following options are available in order to circumvent the problem:</p>
 <ul>
   <li><strong>data_bits</strong> (<em>Optional</em>): Defines how many bits are used for commands inside the data packets sent by the device.</li>
   <li><strong>command_on</strong> (<em>Optional</em>): Defines the data bits value that is sent by the device upon an ‘On’ command.</li>

components/binary_sensor.ring/index.html

@@ -89,7 +89,7 @@
   <li><strong>monitored_conditions</strong> array (<em>Required</em>): Conditions to display in the frontend. The following conditions can be monitored.
     <ul>
       <li><strong>ding</strong>: Return a boolean value when the doorbell button was pressed.</li>
-      <li><strong>motion</strong>: Return a boolean value when a moviment was detected by the Ring doorbell.</li>
+      <li><strong>motion</strong>: Return a boolean value when a movement was detected by the Ring doorbell.</li>
     </ul>
   </li>
 </ul>

components/binary_sensor.template/index.html

@@ -115,11 +115,11 @@ your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
         <dd>
           <p class="desc"><span class="type">(<span class="template"><a href="/docs/configuration/templating/">template</a></span>)</span><span class="required">(Required)</span><span class="description">Defines a template to set the state of the sensor.</span></p>
         </dd>
-        <dt><a class="title-link" name="on_delay" href="#on_delay"></a> on_delay</dt>
+        <dt><a class="title-link" name="delay_on" href="#delay_on"></a> delay_on</dt>
         <dd>
           <p class="desc"><span class="type">(<span class="time">time</span>)</span><span class="required">(Optional)</span><span class="description">The amount of time the template state must be <strong><em>met</em></strong> before this sensor will switch to <code class="highlighter-rouge">on</code>.</span></p>
         </dd>
-        <dt><a class="title-link" name="off_delay" href="#off_delay"></a> off_delay</dt>
+        <dt><a class="title-link" name="delay_off" href="#delay_off"></a> delay_off</dt>
         <dd>
           <p class="desc"><span class="type">(<span class="time">time</span>)</span><span class="required">(Optional)</span><span class="description">The amount of time the template state must be <strong><em>not met</em></strong> before this sensor will switch to <code class="highlighter-rouge">off</code>.</span></p>
         </dd>
@@ -202,7 +202,7 @@ there has been no washer activity for 5 minutes.</p>
     <span class="s">sensors</span><span class="pi">:</span>
       <span class="s">washing_machine</span><span class="pi">:</span>
         <span class="s">friendly_name</span><span class="pi">:</span> <span class="s2">"</span><span class="s">Washing</span><span class="nv"> </span><span class="s">Machine"</span>
-        <span class="s">off_delay</span><span class="pi">:</span>
+        <span class="s">delay_off</span><span class="pi">:</span>
           <span class="s">minutes</span><span class="pi">:</span> <span class="s">5</span>
         <span class="s">value_template</span><span class="pi">:</span> <span class="pi">&gt;-</span>
           <span class="no">{{ states('sensor.washing_machine_power')|float &gt; 0 }}</span>

components/binary_sensor.velbus/index.html

@@ -97,7 +97,7 @@
       <li><strong>name</strong> (<em>Required</em>): Name of the binary sensor.</li>
       <li><strong>module</strong> (<em>Required</em>): The hexadecimal module address</li>
       <li><strong>channel</strong> (<em>Required</em>): The channel number in the module.</li>
-      <li><strong>is_pushbutton</strong> (<em>Optional</em>): Booelan to indicate if a wall switch is a push button or not (default: false)</li>
+      <li><strong>is_pushbutton</strong> (<em>Optional</em>): Boolean to indicate if a wall switch is a push button or not (default: false)</li>
     </ul>
   </li>
 </ul>

components/binary_sensor.wink/index.html

@@ -91,7 +91,7 @@
   <li>Dropcam sensors</li>
 </ul>
 <p class="note">
-The above devices are confimed to work, but others may work as well.
+The above devices are confirmed to work, but others may work as well.
 </p>
 </article>
         </div>

components/binary_sensor.workday/index.html

@@ -76,7 +76,7 @@
   <hr class="divider">
   <p>The <code class="highlighter-rouge">workday</code> binary sensor indicates, whether the current day is a workday or not. It allows specifying, which days of the week counts as workdays and also uses the python module <a href="https://pypi.python.org/pypi/holidays">holidays</a> to incorporate information about region-specific public holidays.</p>
 <p>To enable the <code class="highlighter-rouge">workday</code> sensor 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 configuation.yaml entry</span>
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
 <span class="s">binary_sensor</span><span class="pi">:</span>
   <span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">workday</span>
     <span class="s">country</span><span class="pi">:</span> <span class="s">DE</span>

components/camera.generic/index.html

@@ -90,7 +90,7 @@
   <li><strong>username</strong> (<em>Optional</em>): The username for accessing your camera.</li>
   <li><strong>password</strong> (<em>Optional</em>): The password for accessing your camera.</li>
   <li><strong>authentication</strong> (<em>Optional</em>): Type for authenticating the requests <code class="highlighter-rouge">basic</code> (default) or <code class="highlighter-rouge">digest</code>.</li>
-  <li><strong>limit_refetch_to_url_change</strong> (<em>Optional</em>): True/false value (default: false). Limits refetching of the remote image to when the URL changes. Only relevant if using a template to fetch the remote image.</li>
+  <li><strong>limit_refetch_to_url_change</strong> (<em>Optional</em>): True/false value (default: false). Limits re-fetching of the remote image to when the URL changes. Only relevant if using a template to fetch the remote image.</li>
   <li><strong>content_type</strong> (<em>Optional</em>): Set the content type for the IP camera if it is not a jpg file (default: <code class="highlighter-rouge">image/jpeg</code>). Use <code class="highlighter-rouge">image/svg+xml</code> to add a dynamic svg file.</li>
 </ul>
 <p class="img">

components/camera.mjpeg/index.html

@@ -85,7 +85,7 @@
 <p>Configuration variables:</p>
 <ul>
   <li><strong>mjpeg_url</strong> (<em>Required</em>): The URL your camera serves the video on, eg. http://192.168.1.21:2112/</li>
-  <li><strong>still_image_url</strong> (<em>Optional</em>): The URL for thumbmail picture if camera support that.</li>
+  <li><strong>still_image_url</strong> (<em>Optional</em>): The URL for thumbnail picture if camera support that.</li>
   <li><strong>name</strong> (<em>Optional</em>): This parameter allows you to override the name of your camera.</li>
   <li><strong>username</strong> (<em>Optional</em>): The username for accessing your camera.</li>
   <li><strong>password</strong> (<em>Optional</em>): The password for accessing your camera.</li>

components/camera.mqtt/index.html

@@ -74,7 +74,7 @@
     </h1>
   </header>
   <hr class="divider">
-  <p>The <code class="highlighter-rouge">mqtt</code> camera platform allows you to integrate the content of an image file sent through MQTT into Home Assistant as a camera. Everytime a message under the <code class="highlighter-rouge">topic</code> in the configuration is received, the image displayed in Home Assistant will also be updated.</p>
+  <p>The <code class="highlighter-rouge">mqtt</code> camera platform allows you to integrate the content of an image file sent through MQTT into Home Assistant as a camera. Every time a message under the <code class="highlighter-rouge">topic</code> in the configuration is received, the image displayed in Home Assistant will also be updated.</p>
 <p>This can be used with an application or a service capable of sending images through MQTT, for example <a href="https://play.google.com/store/apps/details?id=it.barbaro.zanzito">Zanzito</a>.</p>
 <p>To enable this camera 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>

components/camera.synology/index.html

@@ -8,7 +8,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
     <title>Synology Camera - Home Assistant</title>
     <meta name="author" content="Home Assistant">
-    <meta name="description" content="Instructions how to integrate Synolog Surveillance Station cameras within Home Assistant.">
+    <meta name="description" content="Instructions how to integrate Synology Surveillance Station cameras within Home Assistant.">
     <meta name="viewport" content="width=device-width">
     <link rel="canonical" href="https://home-assistant.io/components/camera.synology/">
     <meta property="fb:app_id" content="338291289691179">
@@ -16,12 +16,12 @@
     <meta property="og:site_name" content="Home Assistant">
     <meta property="og:url" content="https://home-assistant.io/components/camera.synology/">
     <meta property="og:type" content="article">
-    <meta property="og:description" content="Instructions how to integrate Synolog Surveillance Station cameras within Home Assistant.">
+    <meta property="og:description" content="Instructions how to integrate Synology Surveillance Station cameras within Home Assistant.">
     <meta property="og:image" content="https://home-assistant.io/images/default-social.png">
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:site" content="@home_assistant">
     <meta name="twitter:title" content="Synology Camera">
-    <meta name="twitter:description" content="Instructions how to integrate Synolog Surveillance Station cameras within Home Assistant.">
+    <meta name="twitter:description" content="Instructions how to integrate Synology Surveillance Station cameras within Home Assistant.">
     <meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
     <link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
     <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">

components/climate.ecobee/index.html

@@ -158,7 +158,7 @@ The attributes <code class="highlighter-rouge">min_temp</code> and <code class="
   <tbody>
     <tr>
       <td>Integer</td>
-      <td>Currenly measured temperature</td>
+      <td>Currently measured temperature</td>
     </tr>
   </tbody>
 </table>
@@ -313,7 +313,7 @@ auto operation mode.</p>
 <p>Returns the climate currently active on the thermostat. The mode
 is returned as the user-visible name (rather than the internally used name).</p>
 <h3><a class="title-link" name="attribute-fan_min_on_time" href="#attribute-fan_min_on_time"></a> Attribute <code class="highlighter-rouge">fan_min_on_time</code></h3>
-<p>Returns the current fan mimimum on time.</p>
+<p>Returns the current fan minimum on time.</p>
 <table>
   <thead>
     <tr>
@@ -413,7 +413,7 @@ are not implemented for this thermostat.</p>
 </table>
 <h3><a class="title-link" name="service-set_hold_mode" href="#service-set_hold_mode"></a> Service <code class="highlighter-rouge">set_hold_mode</code></h3>
 <p>Puts the thermostat into the given hold mode. For ‘home’, ‘away’, ‘sleep’,
-and ony other hold based on a reference climate, the
+and any other hold based on a reference climate, the
 target temperature is taken from the reference climate.
 For ‘temp’, the current temperature is taken as the target temperature.
 When None is provided as parameter, the hold_mode is turned off.

components/climate.knx/index.html

@@ -8,7 +8,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
     <title>KNX Climate - Home Assistant</title>
     <meta name="author" content="Home Assistant">
-    <meta name="description" content="Instructions on how to integrate KXN thermostats with Home Assistant.">
+    <meta name="description" content="Instructions on how to integrate KNX thermostats with Home Assistant.">
     <meta name="viewport" content="width=device-width">
     <link rel="canonical" href="https://home-assistant.io/components/climate.knx/">
     <meta property="fb:app_id" content="338291289691179">
@@ -16,12 +16,12 @@
     <meta property="og:site_name" content="Home Assistant">
     <meta property="og:url" content="https://home-assistant.io/components/climate.knx/">
     <meta property="og:type" content="article">
-    <meta property="og:description" content="Instructions on how to integrate KXN thermostats with Home Assistant.">
+    <meta property="og:description" content="Instructions on how to integrate KNX thermostats with Home Assistant.">
     <meta property="og:image" content="https://home-assistant.io/images/default-social.png">
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:site" content="@home_assistant">
     <meta name="twitter:title" content="KNX Climate">
-    <meta name="twitter:description" content="Instructions on how to integrate KXN thermostats with Home Assistant.">
+    <meta name="twitter:description" content="Instructions on how to integrate KNX thermostats with Home Assistant.">
     <meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
     <link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
     <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
@@ -112,7 +112,7 @@
     <p><strong>controller_status_state_address</strong> (<em>Optional</em>) Explicit KNX address for reading HVAC controller status</p>
   </li>
   <li><strong>operation_mode_frost_protection_address</strong> (<em>Optional</em>) KNX address for switching on/off frost/heat protection mode.</li>
-  <li><strong>operation_mode_night_address</strong> (<em>Optional</em>) KNX address for switching on/off night nmode.</li>
+  <li><strong>operation_mode_night_address</strong> (<em>Optional</em>) KNX address for switching on/off night mode.</li>
   <li><strong>operation_mode_comfort_address</strong> (<em>Optional</em>) KNX address for switching on/off comfort mode.</li>
 </ul>
 <p><code class="highlighter-rouge">operation_mode_frost_protection_address</code> / <code class="highlighter-rouge">operation_mode_night_address</code> / <code class="highlighter-rouge">operation_mode_comfort_address</code> are not necessary if <code class="highlighter-rouge">operation_mode_address</code> was specified.</p>

components/climate.proliphix/index.html

@@ -93,7 +93,7 @@
   <li><strong>username</strong> (<em>Required</em>): Username for the thermostat.</li>
   <li><strong>password</strong> (<em>Required</em>): Password for the thermostat.</li>
 </ul>
-<p>The Proliphix NT Thermostat series are ethernet connected thermostats. They have a local HTTP interface that is based on get/set
+<p>The Proliphix NT Thermostat series are Ethernet connected thermostats. They have a local HTTP interface that is based on get/set
 of OID values. A complete collection of the API is available in this <a href="https://github.com/sdague/thermostat.rb/blob/master/docs/PDP_API_R1_11.pdf">API documentation</a>.</p>
 </article>
         </div>

components/climate.sensibo/index.html

@@ -85,7 +85,7 @@
 <p>Configuration variables:</p>
 <ul>
   <li><strong>api_key</strong> (<em>Required</em>): Your API key.</li>
-  <li><strong>id</strong> (<em>Optional</em>): A unit ID or a list of IDs. If none specified then all units acessible by the <code class="highlighter-rouge">api_key</code> will be used.</li>
+  <li><strong>id</strong> (<em>Optional</em>): A unit ID or a list of IDs. If none specified then all units accessible by the <code class="highlighter-rouge">api_key</code> will be used.</li>
 </ul>
 <p>To get your API key visit <a href="https://home.sensibo.com/me/api">https://home.sensibo.com/me/api</a></p>
 <p class="note">

components/climate.wink/index.html

@@ -87,7 +87,7 @@
   <li>Quirky Aros window AC unit</li>
 </ul>
 <p class="note">
-The above devices are confimed to work, but others may work as well.
+The above devices are confirmed to work, but others may work as well.
 </p>
 </article>
         </div>

components/cover.knx/index.html

@@ -8,7 +8,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
     <title>KNX Cover - Home Assistant</title>
     <meta name="author" content="Home Assistant">
-    <meta name="description" content="Instructions on how to integrate KXN covers with Home Assistant.">
+    <meta name="description" content="Instructions on how to integrate KNX covers with Home Assistant.">
     <meta name="viewport" content="width=device-width">
     <link rel="canonical" href="https://home-assistant.io/components/cover.knx/">
     <meta property="fb:app_id" content="338291289691179">
@@ -16,12 +16,12 @@
     <meta property="og:site_name" content="Home Assistant">
     <meta property="og:url" content="https://home-assistant.io/components/cover.knx/">
     <meta property="og:type" content="article">
-    <meta property="og:description" content="Instructions on how to integrate KXN covers with Home Assistant.">
+    <meta property="og:description" content="Instructions on how to integrate KNX covers with Home Assistant.">
     <meta property="og:image" content="https://home-assistant.io/images/default-social.png">
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:site" content="@home_assistant">
     <meta name="twitter:title" content="KNX Cover">
-    <meta name="twitter:description" content="Instructions on how to integrate KXN covers with Home Assistant.">
+    <meta name="twitter:description" content="Instructions on how to integrate KNX covers with Home Assistant.">
     <meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
     <link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
     <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">

components/cover.mqtt/index.html

@@ -110,7 +110,7 @@ state from <code class="highlighter-rouge">state_topic</code>. If these messages
   <li><strong>tilt_max</strong> (<em>Optional</em>): The maximum tilt value. Default is <code class="highlighter-rouge">100</code></li>
   <li><strong>tilt_closed_value</strong> (<em>Optional</em>): The value that will be sent on a <code class="highlighter-rouge">close_cover_tilt</code> command. Default is <code class="highlighter-rouge">0</code></li>
   <li><strong>tilt_opened_value</strong> (<em>Optional</em>): The value that will be sent on an <code class="highlighter-rouge">open_cover_tilt</code> command. Default is <code class="highlighter-rouge">100</code></li>
-  <li><strong>tilt_status_optimistic</strong> (<em>Optional</em>): Flag that determines if tilt works in optimistic mode. Default is <code class="highlighter-rouge">true</code> if <code class="highlighter-rouge">tilt_status_topic</code> is not deinfed, else <code class="highlighter-rouge">false</code></li>
+  <li><strong>tilt_status_optimistic</strong> (<em>Optional</em>): Flag that determines if tilt works in optimistic mode. Default is <code class="highlighter-rouge">true</code> if <code class="highlighter-rouge">tilt_status_topic</code> is not defined, else <code class="highlighter-rouge">false</code></li>
   <li><strong>tilt_invert_state</strong> (<em>Optional</em>): Flag that determines if open/close are flipped; higher values toward closed and lower values toward open. Default is <code class="highlighter-rouge">False</code></li>
 </ul>
 <h2><a class="title-link" name="examples" href="#examples"></a> Examples</h2>

components/cover.wink/index.html

@@ -89,7 +89,7 @@
   <li>Chamberlain (Limited functionality) (No Wink hub required)</li>
 </ul>
 <p class="note">
-The above devices are confimed to work, but others may work as well.
+The above devices are confirmed to work, but others may work as well.
 </p>
 </article>
         </div>

components/device_tracker.bluetooth_le_tracker/index.html

@@ -77,7 +77,7 @@
   <p class="note warning">
 We have received <a href="https://github.com/home-assistant/home-assistant/issues/4442">numerous reports</a> that this integration will have a big impact on the performance of the server.
 </p>
-<p>This tracker discovers new devices on boot and in regular intervals and tracks bluetooth low-energy devices periodically based on interval_seconds value. It is not required to pair the devices with each other.</p>
+<p>This tracker discovers new devices on boot and in regular intervals and tracks Bluetooth low-energy devices periodically based on interval_seconds value. It is not required to pair the devices with each other.</p>
 <p>Devices discovered are stored with ‘BLE_’ as the prefix for device mac addresses in <code class="highlighter-rouge">known_devices.yaml</code>.</p>
 <p>This platform requires pybluez to be installed. On Debian based installs, run</p>
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo apt install bluetooth libbluetooth-dev pkg-config libboost-python-dev libboost-thread-dev libglib2.0-dev python-dev
@@ -96,11 +96,11 @@ We have received <a href="https://github.com/home-assistant/home-assistant/issue
 </div>
 <p>Configuration variables:</p>
 <ul>
-  <li><strong>device_id</strong> (<em>Optional</em>): The device ID for the bluetooth device to be used for tracking. Defaults to <code class="highlighter-rouge">hci0</code>.</li>
+  <li><strong>device_id</strong> (<em>Optional</em>): The device ID for the Bluetooth device to be used for tracking. Defaults to <code class="highlighter-rouge">hci0</code>.</li>
 </ul>
 <p>As some BT LE devices change their MAC address regularly, a new device is only discovered when it has been seen 5 times.
 Some BTLE devices (e.g. fitness trackers) are only visible to the devices that they are paired with. In this case, the BTLE tracker won’t see this device.</p>
-<p>For running Home Assistant as non root user we can give python3 the missing capabilities to access the bluetooth stack. Quite like setting the setuid bit (see <a href="http://unix.stackexchange.com/questions/96106/bluetooth-le-scan-as-non-root">Stack Exchange</a> for more information).</p>
+<p>For running Home Assistant as non root user we can give python3 the missing capabilities to access the Bluetooth stack. Quite like setting the setuid bit (see <a href="http://unix.stackexchange.com/questions/96106/bluetooth-le-scan-as-non-root">Stack Exchange</a> for more information).</p>
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo apt-get install libcap2-bin
 <span class="gp">$ </span>sudo setcap <span class="s1">'cap_net_raw,cap_net_admin+eip'</span> <span class="sb">`</span>readlink -f <span class="se">\`</span>which python3<span class="se">\`</span><span class="sb">`</span>
 </code></pre>

components/device_tracker.bluetooth_tracker/index.html

@@ -8,7 +8,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
     <title>Bluetooth Tracker - Home Assistant</title>
     <meta name="author" content="Home Assistant">
-    <meta name="description" content="Instructions for integrating bluetooth tracking within Home Assistant.">
+    <meta name="description" content="Instructions for integrating Bluetooth tracking within Home Assistant.">
     <meta name="viewport" content="width=device-width">
     <link rel="canonical" href="https://home-assistant.io/components/device_tracker.bluetooth_tracker/">
     <meta property="fb:app_id" content="338291289691179">
@@ -16,12 +16,12 @@
     <meta property="og:site_name" content="Home Assistant">
     <meta property="og:url" content="https://home-assistant.io/components/device_tracker.bluetooth_tracker/">
     <meta property="og:type" content="article">
-    <meta property="og:description" content="Instructions for integrating bluetooth tracking within Home Assistant.">
+    <meta property="og:description" content="Instructions for integrating Bluetooth tracking within Home Assistant.">
     <meta property="og:image" content="https://home-assistant.io/images/default-social.png">
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:site" content="@home_assistant">
     <meta name="twitter:title" content="Bluetooth Tracker">
-    <meta name="twitter:description" content="Instructions for integrating bluetooth tracking within Home Assistant.">
+    <meta name="twitter:description" content="Instructions for integrating Bluetooth tracking within Home Assistant.">
     <meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
     <link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
     <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
@@ -76,7 +76,7 @@
   <hr class="divider">
   <p>This tracker discovers new devices on boot and tracks Bluetooth devices periodically based on <code class="highlighter-rouge">interval_seconds</code> value. It is not required to pair the devices with each other! Devices discovered are stored with ‘bt_’ as the prefix for device MAC addresses in <code class="highlighter-rouge">known_devices.yaml</code>.</p>
 <p class="note">
-<a href="/hassio/">Hass.io</a> only supports bluetooth on Raspberry Pi 3 via the Bluetooth BCM43xx (/addons/bluetooth_bcm43xx/) addon. <a href="/hassio/">Hass.io</a> doesn’t support external Bluetooth dongles.
+<a href="/hassio/">Hass.io</a> only supports Bluetooth on Raspberry Pi 3 via the Bluetooth BCM43xx (/addons/bluetooth_bcm43xx/) addon. <a href="/hassio/">Hass.io</a> doesn’t support external Bluetooth dongles.
 </p>
 <p>To use the Bluetooth tracker 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>

components/device_tracker.mysensors/index.html

@@ -111,7 +111,7 @@
 <span class="cp">#define SN "GPS Sensor"
 #define SV "1.0"
 </span>
-<span class="c1">// GPS position send interval (in millisectonds)
+<span class="c1">// GPS position send interval (in milliseconds)
 </span><span class="cp">#define GPS_SEND_INTERVAL 30000
 </span><span class="c1">// The child id used for the gps sensor
 </span><span class="cp">#define CHILD_ID_GPS 1

components/device_tracker.nmap_tracker/index.html

@@ -77,7 +77,7 @@
   <p>As an alternative to the router-based device tracking, it is possible to directly scan the network for devices by using Nmap. The IP addresses to scan can be specified in any format that Nmap understands, including the network-prefix notation (<code class="highlighter-rouge">192.168.1.1/24</code>) and the range notation (<code class="highlighter-rouge">192.168.1.1-255</code>).</p>
 <p>If you’re on Debian or Ubuntu, you might have to install the packages for <code class="highlighter-rouge">arp</code> and <code class="highlighter-rouge">nmap</code>. Do so by running <code class="highlighter-rouge">$ sudo apt-get install net-tools nmap</code>. On a Fedora host run <code class="highlighter-rouge">$ sudo dnf -y install nmap</code>.</p>
 <p class="note">
-If you are using <a href="/hassio/">Hass.io</a> then just move forward to the configuration as all requirements are already fullfilled.
+If you are using <a href="/hassio/">Hass.io</a> then just move forward to the configuration as all requirements are already fulfilled.
 </p>
 <p>Host detection is done via Nmap’s “fast scan” (<code class="highlighter-rouge">-F</code>) of the most frequently used 100 ports, with a host timeout of 5 seconds.</p>
 <p>To use this device tracker in your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>

components/device_tracker.owntracks/index.html

@@ -87,7 +87,7 @@
   <li><strong>max_gps_accuracy</strong> (<em>Optional</em>): Sometimes Owntracks can report GPS location with a very low accuracy (few kilometers). That can trigger false zoning in your Home Assistant installation. With the parameter, you can filter these GPS reports. The number has to be in meter. For example, if you put 200 only GPS report with an accuracy under 200 will be take in account.</li>
   <li><strong>waypoints</strong> (<em>Optional</em>): Owntracks users can define <a href="http://owntracks.org/booklet/features/waypoints/">waypoints</a> (a.k.a regions) which are similar in spirit to Home Assistant zones. If this configuration variable is <code class="highlighter-rouge">True</code>, the Owntracks users who are in <code class="highlighter-rouge">waypoint_whitelist</code> can export waypoints from the device and Home Assistant will import them as zone definitions. Defaults to <code class="highlighter-rouge">True</code>.</li>
   <li><strong>waypoint_whitelist</strong> (<em>Optional</em>): A list of user names (as defined for <a href="/components/device_tracker.owntracks/">Owntracks</a>) who can export their waypoints from Owntracks to Home Assistant. Defaults to all users who are connected to Home Assistant via Owntracks.</li>
-  <li><strong>secret</strong> (<em>Optional</em>): <a href="http://owntracks.org/booklet/features/encrypt/">Payload encryption key</a>. This is usable when communicating with a third-party untrusted server or a public server (where anybody can subscribe to any topic). By default the payload is assumed to be unecrypted (although the comunication between Home Assistant and the server might still be encrypted). This feature requires the <code class="highlighter-rouge">libsodium</code> library to be present.</li>
+  <li><strong>secret</strong> (<em>Optional</em>): <a href="http://owntracks.org/booklet/features/encrypt/">Payload encryption key</a>. This is usable when communicating with a third-party untrusted server or a public server (where anybody can subscribe to any topic). By default the payload is assumed to be unencrypted (although the communication between Home Assistant and the server might still be encrypted). This feature requires the <code class="highlighter-rouge">libsodium</code> library to be present.</li>
 </ul>
 <p>A full sample configuration for the <code class="highlighter-rouge">owntracks</code> platform is shown below:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
@@ -118,10 +118,10 @@
 <p>When you exit a zone, Home Assistant will start using location updates to track you again. To make sure that Home Assistant correctly exits a zone (which it calculates based on your GPS coordinates), you may want to set your Zone radius in HA to be slightly smaller that the Owntracks region radius.</p>
 <h3><a class="title-link" name="using-owntracks-regions---forcing-owntracks-to-update-using" href="#using-owntracks-regions---forcing-owntracks-to-update-using"></a> Using Owntracks regions - forcing Owntracks to update using  iBeacons</h3>
 <p>When run in the usual <em>significant changes mode</em> (which is kind to your phone battery), Owntracks sometimes doesn’t update your location as quickly as you’d like when you arrive at a zone. This can be annoying if you want to trigger an automation when you get home. You can improve the situation using iBeacons.</p>
-<p>iBeacons are simple bluetooth devices that send out an “I’m here” message. They are supported by IOS and some Android devices. Owntracks explain more <a href="http://owntracks.org/booklet/guide/beacons/">here</a>.</p>
+<p>iBeacons are simple Bluetooth devices that send out an “I’m here” message. They are supported by IOS and some Android devices. Owntracks explain more <a href="http://owntracks.org/booklet/guide/beacons/">here</a>.</p>
 <p>When you enter an iBeacon region, Owntracks will send a <code class="highlighter-rouge">region enter</code> message to HA as described above. So if you want to have an event triggered when you arrive home, you can put an iBeacon outside your front door. If you set up an OwnTracks iBeacon region called <code class="highlighter-rouge">home</code> then getting close to the beacon will trigger an update to HA that will set your zone to be <code class="highlighter-rouge">home</code>.</p>
 <p>When you exit an iBeacon region HA will switch back to using GPS to determine your location. Depending on the size of your zone, and the accuracy of your GPS location this may change your HA zone.</p>
-<p>Sometimes Owntracks will lose connection with an iBeacon for a few seconds. If you name your beacon starting with <code class="highlighter-rouge">-</code> Owntracks will wait longer before deciding it has exited the beacon zone. HA will ignore the <code class="highlighter-rouge">-</code> when it matches the Owntracks region with Zones. So if you call your Owntracks region <code class="highlighter-rouge">-home</code> then HA will recognise it as <code class="highlighter-rouge">home</code>, but you will have a more stable iBeacon connection.</p>
+<p>Sometimes Owntracks will lose connection with an iBeacon for a few seconds. If you name your beacon starting with <code class="highlighter-rouge">-</code> Owntracks will wait longer before deciding it has exited the beacon zone. HA will ignore the <code class="highlighter-rouge">-</code> when it matches the Owntracks region with Zones. So if you call your Owntracks region <code class="highlighter-rouge">-home</code> then HA will recognize it as <code class="highlighter-rouge">home</code>, but you will have a more stable iBeacon connection.</p>
 <h3><a class="title-link" name="using-owntracks-ibeacons-to-track-devices" href="#using-owntracks-ibeacons-to-track-devices"></a> Using Owntracks iBeacons to track devices</h3>
 <p>iBeacons don’t need to be stationary. You could put one on your key ring, or in your car.</p>
 <p>When your phone sees a mobile iBeacon that it knows about, it will tell HA the location of that iBeacon. If your phone moves while you are connected to the iBeacon, HA will update the location of the iBeacon. But when your phone loses the connection, HA will stop updating the iBeacon location.</p>

components/device_tracker.snmp/index.html

@@ -74,7 +74,7 @@
     </h1>
   </header>
   <hr class="divider">
-  <p>A lot WiFi access points and WiFi routers support the Simple Network Management Protocol (SNMP). This is a standardized method for monitoring/manageing network connected devices. SNMP uses a tree-like hierarchy where each node is an object. Many of these objects contain (live) lists of insances and metrics, like network interfaces, disks, and wifi registrations.</p>
+  <p>A lot WiFi access points and WiFi routers support the Simple Network Management Protocol (SNMP). This is a standardized method for monitoring/manageing network connected devices. SNMP uses a tree-like hierarchy where each node is an object. Many of these objects contain (live) lists of instances and metrics, like network interfaces, disks, and WiFi registrations.</p>
 <p class="note warning">
 This device tracker needs SNMP to be enabled on the router. It could be that you need to install the SNMP support manually.
 </p>

components/device_tracker.trackr/index.html

@@ -75,7 +75,7 @@
   </header>
   <hr class="divider">
   <p>The <code class="highlighter-rouge">trackr</code> platform allows you to detect presence using <a href="https://www.thetrackr.com/">TrackR</a> devices.</p>
-<p>The offical TrackR mobile app handles the tracking of the TrackR devices using your phones bluetooth and GPS.</p>
+<p>The official TrackR mobile app handles the tracking of the TrackR devices using your phones Bluetooth and GPS.</p>
 <p>To integrate TrackR in Home Assistant, add the following section 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">device_tracker</span><span class="pi">:</span>

components/ecobee/index.html

@@ -98,7 +98,7 @@
 <ul>
   <li>If you do not have an ecobee card, you may be using groups with <code class="highlighter-rouge">default_view</code> that don’t show the card. To get around this you can temporarily comment out the <code class="highlighter-rouge">default_view</code> section or add the <code class="highlighter-rouge">configurator.ecobee</code> component to your <code class="highlighter-rouge">default_view</code> and restart Home Assistant.</li>
 </ul>
-<p>Once you enter the PIN on the ecobee site, wait approximately 5 minutes and then click on the <strong>I have authorized the app</strong> link at the bottom of the ecobee popup window. If everything worked correctly, you should now be able to restart Home Assistant again to see the full ecobee card with all of the sensors populated or see the list of sensors in the developer tools. Now you can re-enable your <code class="highlighter-rouge">default_view</code> (if you had to disable it) and add the ecobee sensors to a group and/or view.</p>
+<p>Once you enter the PIN on the ecobee site, wait approximately 5 minutes and then click on the <strong>I have authorized the app</strong> link at the bottom of the ecobee pop-up window. If everything worked correctly, you should now be able to restart Home Assistant again to see the full ecobee card with all of the sensors populated or see the list of sensors in the developer tools. Now you can re-enable your <code class="highlighter-rouge">default_view</code> (if you had to disable it) and add the ecobee sensors to a group and/or view.</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="c1"># Example configuration.yaml entry</span>
 <span class="s">ecobee</span><span class="pi">:</span>

components/foursquare/index.html

@@ -98,7 +98,7 @@ You will receive an OAuth request landing page, asking you if you want to connec
 After that, you will get redirected to your <code class="highlighter-rouge">REDIRECT_URL</code> with the <code class="highlighter-rouge">access_token</code> as a HTTP GET variable. Copy everything after the = and paste it in your configuration.yaml as the <code class="highlighter-rouge">access_token</code>.</p>
 <h3><a class="title-link" name="real-time-api" href="#real-time-api"></a> Real-Time API</h3>
 <p>The component accepts pushes from Foursquare at <code class="highlighter-rouge">/api/foursquare</code>. The route does not require authentication.</p>
-<p>Foursquare checkin events can be used out of the box to trigger automation actions, e.g.:</p>
+<p>Foursquare check-in events can be used out of the box to trigger automation actions, e.g.:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">automation</span><span class="pi">:</span>
   <span class="pi">-</span> <span class="s">alias</span><span class="pi">:</span> <span class="s">Trigger action when you check into a venue.</span>
     <span class="s">trigger</span><span class="pi">:</span>
@@ -117,7 +117,7 @@ After that, you will get redirected to your <code class="highlighter-rouge">REDI
   <li><strong>eventId</strong> (<em>Optional</em>): The event the user is checking in to.</li>
   <li><strong>shout</strong> (<em>Optional</em>): A message about your check-in. The maximum length of this field is 140 characters.</li>
   <li><strong>mentions</strong> (<em>Optional</em>): Mentions in your check-in. This parameter is a semicolon-delimited list of mentions. A single mention is of the form “start,end,userid”, where start is the index of the first character in the shout representing the mention, end is the index of the first character in the shout after the mention, and userid is the userid of the user being mentioned. If userid is prefixed with “fbu-“, this indicates a Facebook userid that is being mention. Character indices in shouts are 0-based.</li>
-  <li><strong>broadcast</strong> (<em>Optional</em>): “Who to broadcast this check-in to. Accepts a comma-delimited list of values: private (off the grid) or public (share with friends), facebook share on facebook, twitter share on twitter, followers share with followers (celebrity mode users only), If no valid value is found, the default is public.”</li>
+  <li><strong>broadcast</strong> (<em>Optional</em>): “Who to broadcast this check-in to. Accepts a comma-delimited list of values: private (off the grid) or public (share with friends), Facebook share on Facebook, twitter share on twitter, followers share with followers (celebrity mode users only), If no valid value is found, the default is public.”</li>
   <li><strong>ll</strong> (<em>Optional</em>): Latitude and longitude of the user’s location. Only specify this field if you have a GPS or other device reported location for the user at the time of check-in.</li>
   <li><strong>llAcc</strong> (<em>Optional</em>): Accuracy of the user’s latitude and longitude, in meters.</li>
   <li><strong>alt</strong> (<em>Optional</em>): Altitude of the user’s location, in meters.</li>

components/hdmi_cec/index.html

@@ -74,14 +74,14 @@
     </h1>
   </header>
   <hr class="divider">
-  <p>The <code class="highlighter-rouge">hdmi_cec</code> component provides services that allow selecting the active device, powering on all devices, setting all devices to standby and creates switch entites for HDMI devices. Devices are defined in the configuration file by associating HDMI port number and a device name. Connected devices that provide further HDMI ports, such as Soundbars and AVRs are also supported. Devices are listed from the perspective of the CEC-enabled Home Assistant device. Any connected device can be listed, regardless of whether it supports CEC. Ideally the HDMI port number on your device will map correctly the CEC physical address. If it does not, use <code class="highlighter-rouge">cec-client</code> (part of the <code class="highlighter-rouge">libcec</code> package) to listen to traffic on the CEC bus and discover the correct numbers.</p>
+  <p>The <code class="highlighter-rouge">hdmi_cec</code> component provides services that allow selecting the active device, powering on all devices, setting all devices to standby and creates switch entities for HDMI devices. Devices are defined in the configuration file by associating HDMI port number and a device name. Connected devices that provide further HDMI ports, such as sound-bars and AVRs are also supported. Devices are listed from the perspective of the CEC-enabled Home Assistant device. Any connected device can be listed, regardless of whether it supports CEC. Ideally the HDMI port number on your device will map correctly the CEC physical address. If it does not, use <code class="highlighter-rouge">cec-client</code> (part of the <code class="highlighter-rouge">libcec</code> package) to listen to traffic on the CEC bus and discover the correct numbers.</p>
 <h2><a class="title-link" name="cec-setup" href="#cec-setup"></a> CEC Setup</h2>
 <h3><a class="title-link" name="adapter" href="#adapter"></a> Adapter</h3>
 <p>The computer running Home Assistant must support CEC, and of course be connected via HDMI to a device also supporting CEC. You can purchase a <a href="https://www.pulse-eight.com/p/104/usb-hdmi-cec-adapter">USB CEC adapter</a> to add support if necessary. Note that all Raspberry Pi models support CEC natively.</p>
 <h3><a class="title-link" name="libcec" href="#libcec"></a> libcec</h3>
 <p><a href="https://github.com/Pulse-Eight/libcec">libcec</a> must be installed for this component to work. Follow the installation instructions for your environment, provided at the link. <code class="highlighter-rouge">libcec</code> installs Python 3 bindings by default as a system Python module. If you are running Home Assistant in a <a href="/getting-started/installation-virtualenv/">Python virtual environment</a>, make sure it can access the system module, by either symlinking it or using the <code class="highlighter-rouge">--system-site-packages</code> flag.</p>
 <p class="note">
-If you are using <a href="/hassio/">Hass.io</a> then just move forward to the configuration as all requirements are already fullfilled.
+If you are using <a href="/hassio/">Hass.io</a> then just move forward to the configuration as all requirements are already fulfilled.
 </p>
 <h4><a class="title-link" name="symlinking-into-virtual-environment" href="#symlinking-into-virtual-environment"></a> Symlinking into virtual environment</h4>
 <p>Create a symlink to the <code class="highlighter-rouge">cec</code> installation. Keep in mind different installation methods will result in different locations of cec.</p>

components/homematic/index.html

@@ -89,7 +89,7 @@ You can manually rename the created entities by using Home Assistants <a href="h
 <p>Configuration variables (global):</p>
 <ul>
   <li><strong>hosts</strong> (<em>Required</em>): Configuration for each host to integrate into Home Assistant.</li>
-  <li><strong>local_ip</strong> (<em>Optional</em>): IP of device running Home Assistant. Override autodetected value for exotic network setups.</li>
+  <li><strong>local_ip</strong> (<em>Optional</em>): IP of device running Home Assistant. Override auto-detected value for exotic network setups.</li>
   <li><strong>local_port</strong> (<em>Optional</em>): Port for connection with Home Assistant. By default it is randomly assigned.</li>
 </ul>
 <p>Configuration variables (host):</p>
@@ -136,7 +136,7 @@ You can manually rename the created entities by using Home Assistants <a href="h
 <h3><a class="title-link" name="multiple-hosts" href="#multiple-hosts"></a> Multiple hosts</h3>
 <p>In order to allow communication with multiple hosts or different protocols in parallel (wireless, wired and ip), multiple connections will be established, each to the configured destination. The name you choose for the host has to be unique and limited to ASCII letters.
 Using multiple hosts has the drawback, that the services (explained below) may not work as expected. Only one connection can be used for services, which limits the devices/variables a service can use to the scope/protocol of the host.
-This does <em>not</em> affect the entites in Home Assistant. They all use their own connection and work as expected.</p>
+This does <em>not</em> affect the entities in Home Assistant. They all use their own connection and work as expected.</p>
 <h3><a class="title-link" name="reading-attributes-of-entities" href="#reading-attributes-of-entities"></a> Reading attributes of entities</h3>
 <p>Most devices have, besides their state, additional attributes like their battery state or valve position. These can be accessed using templates in automations, or even as their own entities using the <a href="https://home-assistant.io/components/sensor.template/">template sensor</a> component. Here’s an example of a template sensor that exposes the valve state of a thermostat.</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">sensor</span><span class="pi">:</span>

components/http/index.html

@@ -86,7 +86,7 @@ It’s HIGHLY recommended that you set the <code class="highlighter-rouge">api_p
 <p>Configuration variables:</p>
 <ul>
   <li><strong>api_password</strong> (<em>Optional</em>): Protect Home Assistant with a password.</li>
-  <li><strong>server_host</strong> (<em>Optional</em>): Only listen to incoming requests on specific ip/host (default: accept all)</li>
+  <li><strong>server_host</strong> (<em>Optional</em>): Only listen to incoming requests on specific IP/host (default: accept all)</li>
   <li><strong>server_port</strong> (<em>Optional</em>): Let you set a port to use. Defaults to 8123.</li>
   <li><strong>base_url</strong> (<em>Optional</em>): The URL that Home Assistant is available on the internet. For example: <code class="highlighter-rouge">hass-example.duckdns.org:8123</code>. Defaults to local IP address. The IOS app finds local installations, if you have an outside URL use this so that you can auto fill when discovered in the app.</li>
   <li><strong>development</strong> (<em>Optional</em>): Disable caching and load unvulcanized assets. Useful for Frontend development.</li>
@@ -96,7 +96,7 @@ It’s HIGHLY recommended that you set the <code class="highlighter-rouge">api_p
   <li><strong>use_x_forwarded_for</strong> (<em>Optional</em>): Enable parsing of the <code class="highlighter-rouge">X-Forwarded-For</code> header, passing on the client’s correct IP address in proxied setups. You should only enable this in a trustworthy network environment, as clients passing that header could easily spoof their source IP address. Defaults to False.</li>
   <li><strong>trusted_networks</strong> (<em>Optional</em>): List of trusted networks, consisting of IP addresses or networks, that are allowed to bypass password protection when accessing Home Assistant. It should be noted that if you use a reverse proxy, all requests to home assistant, regardless of source, will arrive from the reverse proxy IP address. Therefore in a reverse proxy scenario this option should be used with extreme care.</li>
   <li><strong>ip_ban_enabled</strong> (<em>Optional</em>): Flag indicating whether additional IP filtering is enabled. Defaults to False.</li>
-  <li><strong>login_attempts_threshold</strong> (<em>Optional</em>): Number of failed login attemt from single IP after which it will be automatically banned if <code class="highlighter-rouge">ip_ban_enabled</code> is True. Defaults to -1, meaning that no new automatic bans will be added.</li>
+  <li><strong>login_attempts_threshold</strong> (<em>Optional</em>): Number of failed login attempt from single IP after which it will be automatically banned if <code class="highlighter-rouge">ip_ban_enabled</code> is True. Defaults to -1, meaning that no new automatic bans will be added.</li>
 </ul>
 <p>The sample below shows a configuration entry with possible values:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
@@ -125,7 +125,7 @@ It’s HIGHLY recommended that you set the <code class="highlighter-rouge">api_p
 <p>To use those kind of <a href="/components/sensor.http/">sensors</a> or <a href="components/binary_sensor.http/">binary sensors</a> in your installation no configuration in Home Assistant is needed. All configuration is done on the devices themselves. This means that you must be able to edit the target URL or endpoint and the payload. The entity will be created after the first message has arrived.</p>
 <p>All <a href="/developers/rest_api/#post-apistatesltentity_id">requests</a> need to be sent to the endpoint of the device and must be <strong>POST</strong>.</p>
 <p>If you want to use Home Assistant to host or serve static files then create a directory called <code class="highlighter-rouge">www</code> under the <code class="highlighter-rouge">.homeassistant</code> configuration path. The static files in <code class="highlighter-rouge">.homeassistant/www/</code> can be accessed by the following URL <code class="highlighter-rouge">http://your.domain:8123/local/</code>.</p>
-<p>If you want to apply additional IP filtering, and automatically ban bruteforce attempts, set <code class="highlighter-rouge">ip_ban_enabled</code> to <code class="highlighter-rouge">True</code> and select number of attempts. After first ban file <code class="highlighter-rouge">ip_bans.yaml</code> will be created in the root configuration folder. It will have IP address and time in UTC when it was added:</p>
+<p>If you want to apply additional IP filtering, and automatically ban brute force attempts, set <code class="highlighter-rouge">ip_ban_enabled</code> to <code class="highlighter-rouge">True</code> and select number of attempts. After first ban file <code class="highlighter-rouge">ip_bans.yaml</code> will be created in the root configuration folder. It will have IP address and time in UTC when it was added:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">127.0.0.1</span><span class="pi">:</span>
   <span class="s">banned_at</span><span class="pi">:</span> <span class="s1">'</span><span class="s">2016-11-16T19:20:03'</span>
 </code></pre>

components/ifttt.manything/index.html

@@ -74,7 +74,7 @@
     </h1>
   </header>
   <hr class="divider">
-  <p><a href="https://manything.com">Manything</a> is a smart app that turns your Android device, iPhone, iPod, or iPad into a wifi camera for monitoring your home, your pets, anything! Comes with live streaming, motion activated alerts, cloud video recording, and more.</p>
+  <p><a href="https://manything.com">Manything</a> is a smart app that turns your Android device, iPhone, iPod, or iPad into a WiFi camera for monitoring your home, your pets, anything! Comes with live streaming, motion activated alerts, cloud video recording, and more.</p>
 <p>To get manything support, HA will use IFTTT’s <a href="https://ifttt.com/maker">Maker Channel</a> and the <a href="https://ifttt.com/manything">ManyThing Channel</a>. Use the <a href="/components/ifttt/">IFTTT Setup instructions</a> to activate the IFTTT Platform.</p>
 <p>After setting up IFTTT, Maker Channel and ManyThing Channel, you can use the following examples to configure Home Assistant.</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>

components/image_processing.openalpr_local/index.html

@@ -78,7 +78,7 @@
 <p>For using inside automation look on <a href="/components/image_processing">component</a> page.</p>
 <h3><a class="title-link" name="local-installation" href="#local-installation"></a> Local installation</h3>
 <p>If you want process all data locally, you need version 2.3.1 or higher of the <code class="highlighter-rouge">alpr</code> commandline tool.</p>
-<p>If you don’t find binaries for your distribution you can compile from source. Documention of how to build OpenALPR is found <a href="https://github.com/openalpr/openalpr/wiki">here</a>.</p>
+<p>If you don’t find binaries for your distribution you can compile from source. Documentation of how to build OpenALPR is found <a href="https://github.com/openalpr/openalpr/wiki">here</a>.</p>
 <p>On a Debian system you can use this <code class="highlighter-rouge">cmake</code> command to build only the command line tool:</p>
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>cmake -DWITH_TEST<span class="o">=</span>FALSE -DWITH_BINDING_JAVA<span class="o">=</span>FALSE --DWITH_BINDING_PYTHON<span class="o">=</span>FALSE <span class="se">\</span>
   --DWITH_BINDING_GO<span class="o">=</span>FALSE -DWITH_DAEMON<span class="o">=</span>FALSE -DCMAKE_INSTALL_PREFIX:PATH<span class="o">=</span>/usr ..

components/image_processing.seven_segments/index.html

@@ -8,7 +8,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
     <title>Seven segments display - Home Assistant</title>
     <meta name="author" content="Home Assistant">
-    <meta name="description" content="Instructions how to use OCR for seven segemnts displays into Home Assistant.">
+    <meta name="description" content="Instructions how to use OCR for seven segments displays into Home Assistant.">
     <meta name="viewport" content="width=device-width">
     <link rel="canonical" href="https://home-assistant.io/components/image_processing.seven_segments/">
     <meta property="fb:app_id" content="338291289691179">
@@ -16,12 +16,12 @@
     <meta property="og:site_name" content="Home Assistant">
     <meta property="og:url" content="https://home-assistant.io/components/image_processing.seven_segments/">
     <meta property="og:type" content="article">
-    <meta property="og:description" content="Instructions how to use OCR for seven segemnts displays into Home Assistant.">
+    <meta property="og:description" content="Instructions how to use OCR for seven segments displays into Home Assistant.">
     <meta property="og:image" content="https://home-assistant.io/images/screenshots/ssocr.png">
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:site" content="@home_assistant">
     <meta name="twitter:title" content="Seven segments display">
-    <meta name="twitter:description" content="Instructions how to use OCR for seven segemnts displays into Home Assistant.">
+    <meta name="twitter:description" content="Instructions how to use OCR for seven segments displays into Home Assistant.">
     <meta name="twitter:image" content="https://home-assistant.io/images/screenshots/ssocr.png">
     <link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
     <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
@@ -76,7 +76,7 @@
   <hr class="divider">
   <p>The <code class="highlighter-rouge">seven_segments</code> image processing platform allows you to read physical seven segments displays through Home Assistant. <a href="https://www.unix-ag.uni-kl.de/~auerswal/ssocr/"><code class="highlighter-rouge">ssocr</code></a> is used to extract the value shown on the display which is observed by a <a href="/components/camera/">camera</a>.</p>
 <p class="note">
-If you are using <a href="/hassio/">Hass.io</a> then just move forward to the configuration as all requirements are already fullfilled.
+If you are using <a href="/hassio/">Hass.io</a> then just move forward to the configuration as all requirements are already fulfilled.
 </p>
 <p><code class="highlighter-rouge">ssocr</code> needs to be available on your system. Check the installation instruction below:</p>
 <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo dnf -y install imlib2-devel <span class="c"># Fedora</span>
@@ -89,7 +89,7 @@ If you are using <a href="/hassio/">Hass.io</a> then just move forward to the co
 <span class="gp">$ </span>make deb <span class="c"># (Optional) This allows you to make a deb so that you apt is aware of ssocr</span>
 </code></pre>
 </div>
-<p>To enable the OCR of a seven segement display in your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
+<p>To enable the OCR of a seven segment display 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>
 <span class="s">image_processing</span><span class="pi">:</span>
   <span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">seven_segments</span>

components/index.html

@@ -107,8 +107,7 @@ Support for these components is provided by the Home Assistant community.
     <a href='#lock' class="btn">Lock (12)</a>
     <a href='#mailbox' class="btn">Mailbox (1)</a>
     <a href='#media-player' class="btn">Media Player (50)</a>
-    <a href='#notifications' class="btn">Notifications (49)</a>
-    <a href='#notify' class="btn">Notify (1)</a>
+    <a href='#notifications' class="btn">Notifications (50)</a>
     <a href='#organization' class="btn">Organization (3)</a>
     <a href='#presence-detection' class="btn">Presence Detection (43)</a>
     <a href='#remote' class="btn">Remote (4)</a>
@@ -274,7 +273,7 @@ var allComponents = [
 {url:"/components/device_tracker.ddwrt/", title:"DD-WRT", cat:"presence-detection", featured: false, v: "0.7", logo: "ddwrt.png"},
 {url:"/components/sensor.dht/", title:"DHT Sensor", cat:"diy", featured: false, v: "0.7", logo: "dht.png"},
 {url:"/components/sensor.dnsip/", title:"DNS IP", cat:"sensor", featured: false, v: "0.40", logo: "home-assistant.png"},
-{url:"/components/sensor.dsmr/", title:"DSMR/Slimme meter", cat:"energy", featured: false, v: "0.34", logo: "netbeheernederland.jpg"},
+{url:"/components/sensor.dsmr/", title:"DSMR or Slimme meter", cat:"energy", featured: false, v: "0.34", logo: "netbeheernederland.jpg"},
 {url:"/components/sensor.dte_energy_bridge/", title:"DTE Energy Bridge", cat:"energy", featured: false, v: "0.21", logo: "dte_energy.png"},
 {url:"/components/sensor.dwd_weather_warnings/", title:"DWD Weather warnings", cat:"weather", featured: false, v: "0.51", logo: ""},
 {url:"/components/sensor.darksky/", title:"Dark Sky", cat:"weather", featured: true, v: "0.3", logo: "dark_sky.png"},
@@ -457,7 +456,7 @@ var allComponents = [
 {url:"/components/climate.knx/", title:"KNX Climate", cat:"climate", featured: false, v: "0.25", logo: "knx.png"},
 {url:"/components/cover.knx/", title:"KNX Cover", cat:"cover", featured: false, v: "0.48", logo: "knx.png"},
 {url:"/components/light.knx/", title:"KNX Light", cat:"light", featured: false, v: "0.44", logo: "knx.png"},
-{url:"/components/notify.knx/", title:"KNX Notify", cat:"notify", featured: false, v: "0.53", logo: "knx.png"},
+{url:"/components/notify.knx/", title:"KNX Notify", cat:"notifications", featured: false, v: "0.53", logo: "knx.png"},
 {url:"/components/sensor.knx/", title:"KNX Sensor", cat:"sensor", featured: false, v: "0.29", logo: "knx.png"},
 {url:"/components/switch.knx/", title:"KNX Switch", cat:"switch", featured: false, v: "0.24", logo: "knx.png"},
 {url:"/components/sensor.kwb/", title:"KWB Easyfire Sensor", cat:"sensor", featured: false, v: "0.4", logo: "kwb.png"},
@@ -1224,7 +1223,7 @@ allComponents.pop(); // remove placeholder element at the end
       <li><a href='/components/device_tracker.ddwrt/'>DD-WRT</a></li>
       <li><a href='/components/sensor.dht/'>DHT Sensor</a></li>
       <li><a href='/components/sensor.dnsip/'>DNS IP</a></li>
-      <li><a href='/components/sensor.dsmr/'>DSMR/Slimme meter</a></li>
+      <li><a href='/components/sensor.dsmr/'>DSMR or Slimme meter</a></li>
       <li><a href='/components/sensor.dte_energy_bridge/'>DTE Energy Bridge</a></li>
       <li><a href='/components/sensor.dwd_weather_warnings/'>DWD Weather warnings</a></li>
       <li><a href='/components/sensor.darksky/'>Dark Sky</a></li>

components/influxdb/index.html

@@ -169,9 +169,9 @@ optional arguments:
 <h2><a class="title-link" name="data-import-script" href="#data-import-script"></a> Data import script</h2>
 <p>If you want to import all the recorded data from your recorder database you can use the data import script.
 It will read all your state_change events from the database and add them as data-points to the InfluxDB.
-You can specify the source database either by pointing the <code class="highlighter-rouge">--config</code> option to the config directory which includes the default sqlite database or by giving a sqlalchemy connection URI with <code class="highlighter-rouge">--uri</code>.
+You can specify the source database either by pointing the <code class="highlighter-rouge">--config</code> option to the config directory which includes the default SQLite database or by giving a sqlalchemy connection URI with <code class="highlighter-rouge">--uri</code>.
 The writing to InfluxDB is done in batches that can be changed with <code class="highlighter-rouge">--step</code>.</p>
-<p>You can control, which data is imported by using the commandline options <code class="highlighter-rouge">--exclude_entities</code> and <code class="highlighter-rouge">--exclude_domains</code>.
+<p>You can control, which data is imported by using the command line options <code class="highlighter-rouge">--exclude_entities</code> and <code class="highlighter-rouge">--exclude_domains</code>.
 Both get a comma separated list of either entity-ids or domain names that are excluded from the import.</p>
 <p>To test what gets imported you can use the <code class="highlighter-rouge">--simulate</code> option, which disables the actual write to the InfluxDB instance.
 This only writes the statistics how much points would be imported from which entity.</p>

components/insteon_plm/index.html

@@ -111,7 +111,7 @@ unambiguous, but sometimes the component will not be able to guess the actual
 usage of the device.  For example, there might be a table lamp plugged into an
 INSTEON appliance relay module.  By default, this will show as a ‘switch’
 device in Home Assistant, but it really should be a ‘light’ device.  For
-exceptions like this, the component supports a device plaform override.  You
+exceptions like this, the component supports a device platform override.  You
 can set any device (by address) to explicitly use a specific platform if the
 default is not correct.</p>
 <h3><a class="title-link" name="example-configuration-with-options" href="#example-configuration-with-options"></a> Example Configuration with Options</h3>

components/keyboard_remote/index.html

@@ -117,7 +117,7 @@ In case of presence of multiple devices of the same model, <code class="highligh
 </code></pre>
 </div>
 <h2><a class="title-link" name="disconnections" href="#disconnections"></a> Disconnections</h2>
-<p>This component manages disconnections and re-connections of the keyboard, for example in the case of a bluetooth device that turns off automatically to preserve battery.</p>
+<p>This component manages disconnections and re-connections of the keyboard, for example in the case of a Bluetooth device that turns off automatically to preserve battery.</p>
 <p>If the keyboard disconnects, the component will fire an event <code class="highlighter-rouge">keyboard_remote_disconnected</code>.
 When the keyboard reconnects, an event <code class="highlighter-rouge">keyboard_remote_connected</code> will be fired.</p>
 <p>Here’s an automation example that plays a sound through a media player whenever the keyboard connects/disconnects:</p>

components/knx/index.html

@@ -8,7 +8,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
     <title>KNX - Home Assistant</title>
     <meta name="author" content="Home Assistant">
-    <meta name="description" content="Instructions on how to integrate KXN components with Home Assistant.">
+    <meta name="description" content="Instructions on how to integrate KNX components with Home Assistant.">
     <meta name="viewport" content="width=device-width">
     <link rel="canonical" href="https://home-assistant.io/components/knx/">
     <meta property="fb:app_id" content="338291289691179">
@@ -16,12 +16,12 @@
     <meta property="og:site_name" content="Home Assistant">
     <meta property="og:url" content="https://home-assistant.io/components/knx/">
     <meta property="og:type" content="article">
-    <meta property="og:description" content="Instructions on how to integrate KXN components with Home Assistant.">
+    <meta property="og:description" content="Instructions on how to integrate KNX components with Home Assistant.">
     <meta property="og:image" content="https://home-assistant.io/images/default-social.png">
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:site" content="@home_assistant">
     <meta name="twitter:title" content="KNX">
-    <meta name="twitter:description" content="Instructions on how to integrate KXN components with Home Assistant.">
+    <meta name="twitter:description" content="Instructions on how to integrate KNX components with Home Assistant.">
     <meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
     <link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
     <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">

components/lametric/index.html

@@ -79,7 +79,7 @@
 <ul>
   <li><a href="/components/notify.lametric">Notify</a></li>
 </ul>
-<p>The LaMetric Time can only be accessed by authorized applications. Therefore, each application that wants to access the LaMetric time needs to be registered at the LaMetric Developer webpage. Sign Up and login to the developer webpage. Click the Create button in the upper right corner, then select Notification App and click Create again. Enter an app name, a description and a redirect URL. Finally, click Save to create the application. For the newly created app you will obtain a client id and a client secret that is required in the following configuration.</p>
+<p>The LaMetric Time can only be accessed by authorized applications. Therefore, each application that wants to access the LaMetric time needs to be registered at the LaMetric Developer web page. Sign Up and login to the developer web page. Click the Create button in the upper right corner, then select Notification App and click Create again. Enter an app name, a description and a redirect URL. Finally, click Save to create the application. For the newly created app you will obtain a client id and a client secret that is required in the following configuration.</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># configuration.yaml example</span>
 <span class="s">lametric</span><span class="pi">:</span>
   <span class="s">client_id</span><span class="pi">:</span> <span class="s">xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx</span>

components/light.avion/index.html

@@ -87,13 +87,13 @@
 <ul>
   <li><strong>username</strong> (<em>Optional</em>): The username used in the Avion app. If username and password are both provided, any associated switches will automatically be added to your configuration.</li>
   <li><strong>password</strong> (<em>Optional</em>): The password used in the Avion app.</li>
-  <li><strong>devices</strong> (<em>Optional</em>): An optional list of devices with their bluetooth address, a custom name to use in the frontend and the API key. The API key can be obtained by executing the following command:
+  <li><strong>devices</strong> (<em>Optional</em>): An optional list of devices with their Bluetooth address, a custom name to use in the frontend and the API key. The API key can be obtained by executing the following command:
     <div class="highlighter-rouge"><pre class="highlight"><code>curl -X POST -H "Content-Type: application/json" -d '{"email": "fakename@example.com", "password": "password"}' https://admin.avi-on.com/api/sessions | jq
 </code></pre>
     </div>
   </li>
 </ul>
-<p>with the email and password fields replaced with those used when registering the device via the mobile app. The passphrase field of the output should be used as the API key in the configuration.</p>
+<p>with the email and password fields replaced with those used when registering the device via the mobile app. The pass phrase field of the output should be used as the API key in the configuration.</p>
 <p>If username and password are not supplied, devices must be configured manually like so:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Manual device configuration.yaml entry</span>
 <span class="s">light</span><span class="pi">:</span>

components/light.hue/index.html

@@ -107,8 +107,8 @@
 </code></pre>
 </div>
 <h3><a class="title-link" name="using-hue-groups-in-home-assistant" href="#using-hue-groups-in-home-assistant"></a> Using Hue Groups in Home Assistant</h3>
-<p>The Hue API allows you to group lights. Home Assistant also supports grouping of entities natively, but sometimes it can be usefull to use Hue Groups to group light bulbs. By doing so, Home Assistant only needs to send one API call to change the state of all the bulbs in those groups instead of one call for every light in the group. This causes all the bulbs to change state simultaniously.</p>
-<p>These Hue Groups can be a <code class="highlighter-rouge">Luminaire</code>, <code class="highlighter-rouge">Lightsource</code>, <code class="highlighter-rouge">LightGroup</code> or <code class="highlighter-rouge">Room</code>. The <code class="highlighter-rouge">Luminaire</code> and <code class="highlighter-rouge">Lightsource</code> can’t be created manually since the Hue bridge manages these automatically based on the discovered bulbs. The <code class="highlighter-rouge">Room</code> and <code class="highlighter-rouge">LightGroup</code> can be created manually through the API, or the mobile app. A bulb can only exist in one <code class="highlighter-rouge">Room</code>, but can exist in multiple <code class="highlighter-rouge">LightGroup</code>. The <code class="highlighter-rouge">LightGroup</code> can be usefull to link certain bulbs together since.</p>
+<p>The Hue API allows you to group lights. Home Assistant also supports grouping of entities natively, but sometimes it can be useful to use Hue Groups to group light bulbs. By doing so, Home Assistant only needs to send one API call to change the state of all the bulbs in those groups instead of one call for every light in the group. This causes all the bulbs to change state simultaneously.</p>
+<p>These Hue Groups can be a <code class="highlighter-rouge">Luminaire</code>, <code class="highlighter-rouge">Lightsource</code>, <code class="highlighter-rouge">LightGroup</code> or <code class="highlighter-rouge">Room</code>. The <code class="highlighter-rouge">Luminaire</code> and <code class="highlighter-rouge">Lightsource</code> can’t be created manually since the Hue bridge manages these automatically based on the discovered bulbs. The <code class="highlighter-rouge">Room</code> and <code class="highlighter-rouge">LightGroup</code> can be created manually through the API, or the mobile app. A bulb can only exist in one <code class="highlighter-rouge">Room</code>, but can exist in multiple <code class="highlighter-rouge">LightGroup</code>. The <code class="highlighter-rouge">LightGroup</code> can be useful to link certain bulbs together since.</p>
 <p>The 2nd generation Hue app only allows to create a <code class="highlighter-rouge">Room</code>. You need to use the first generation app or the API to create a <code class="highlighter-rouge">LightGroup</code>.</p>
 <p>Example:</p>
 <p>To create a <code class="highlighter-rouge">LightGroup</code> named <code class="highlighter-rouge">Ceiling lights</code> that contains the lights 1, 2 and 3, execute the following command:</p>
@@ -168,7 +168,7 @@ This will have all the bulbs transitioned at once, instead of one at a time usin
 <p><em>** Caveats **</em></p>
 <p>The Hue API doesn’t activate scenes directly, only on a Hue Group (typically rooms, especially if using the 2nd gen app). But Hue Scenes don’t actually reference their group. So heuristic matching is used.</p>
 <p>Neither group names or scene names are guaranteed unique in Hue. If you are getting non deterministic behavior, adjust your Hue scenes via the App to be more identifying.</p>
-<p>The Hue hub has limitted spaces for scenes, and will delete scenes if new ones get created that would overflow that space. The API docs say this is based on “Least Recently Used”.</p>
+<p>The Hue hub has limited spaces for scenes, and will delete scenes if new ones get created that would overflow that space. The API docs say this is based on “Least Recently Used”.</p>
 </article>
         </div>
         <aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">

components/light.knx/index.html

@@ -8,7 +8,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
     <title>KNX Light - Home Assistant</title>
     <meta name="author" content="Home Assistant">
-    <meta name="description" content="Instructions on how to integrate KXN lights with Home Assistant.">
+    <meta name="description" content="Instructions on how to integrate KNX lights with Home Assistant.">
     <meta name="viewport" content="width=device-width">
     <link rel="canonical" href="https://home-assistant.io/components/light.knx/">
     <meta property="fb:app_id" content="338291289691179">
@@ -16,12 +16,12 @@
     <meta property="og:site_name" content="Home Assistant">
     <meta property="og:url" content="https://home-assistant.io/components/light.knx/">
     <meta property="og:type" content="article">
-    <meta property="og:description" content="Instructions on how to integrate KXN lights with Home Assistant.">
+    <meta property="og:description" content="Instructions on how to integrate KNX lights with Home Assistant.">
     <meta property="og:image" content="https://home-assistant.io/images/default-social.png">
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:site" content="@home_assistant">
     <meta name="twitter:title" content="KNX Light">
-    <meta name="twitter:description" content="Instructions on how to integrate KXN lights with Home Assistant.">
+    <meta name="twitter:description" content="Instructions on how to integrate KNX lights with Home Assistant.">
     <meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
     <link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
     <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
@@ -96,7 +96,7 @@
   <li><strong>state_address</strong>: (<em>Optional</em>) separate KNX group address for retrieving the switch state of the light.</li>
   <li><strong>brightness_state_address</strong>: (<em>Optional</em>) separate KNX group address for retrieving the dimmed state of the light.</li>
 </ul>
-<p>Some KNX devices can change their state internally without any messages on the KXN bus, e.g., if you configure a timer on a channel. The optional <code class="highlighter-rouge">state_address</code> can be used to inform Home Assistant about these state changes. If a KNX message is seen on the bus addressed to the given state address, this will overwrite the state of the switch object.
+<p>Some KNX devices can change their state internally without any messages on the KNX bus, e.g., if you configure a timer on a channel. The optional <code class="highlighter-rouge">state_address</code> can be used to inform Home Assistant about these state changes. If a KNX message is seen on the bus addressed to the given state address, this will overwrite the state of the switch object.
 For switching/light actuators that are only controlled by a single group address and can’t change their state internally, you don’t have to configure the state address.</p>
 </article>
         </div>

components/light.limitlessled/index.html

@@ -76,7 +76,7 @@
   <hr class="divider">
   <p><code class="highlighter-rouge">limitlessled</code> can control your <a href="http://www.limitlessled.com/">LimitlessLED</a> lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, MiLight, LEDme, dekolight, or iLight.</p>
 <h3><a class="title-link" name="setup" href="#setup"></a> Setup</h3>
-<p>Before configuring Home Assistant, make sure you can control your bulbs or LEDs with the MiLight mobile application. Discover your bridge(s) IP address. You can do this via your router or a mobile application like Fing (<a href="https://play.google.com/store/apps/details?id=com.overlook.android.fing&amp;hl=en">android</a> or <a href="https://itunes.apple.com/us/app/fing-network-scanner/id430921107?mt=8">itunes</a>). Keep in mind that LimitlessLED bulbs are controlled via groups. You can not control an individual bulb via the bridge, unless it is in a group by itself. Note that you can assign an <code class="highlighter-rouge">rgbw</code>, <code class="highlighter-rouge">rgbww</code> and <code class="highlighter-rouge">white</code> group to the same group number, effectively allowing 12 groups (4 <code class="highlighter-rouge">rgbww</code>, 4 <code class="highlighter-rouge">rgbw</code> and 4 <code class="highlighter-rouge">white</code>) per bridge.</p>
+<p>Before configuring Home Assistant, make sure you can control your bulbs or LEDs with the MiLight mobile application. Discover your bridge(s) IP address. You can do this via your router or a mobile application like Fing (<a href="https://play.google.com/store/apps/details?id=com.overlook.android.fing&amp;hl=en">android</a> or <a href="https://itunes.apple.com/us/app/fing-network-scanner/id430921107?mt=8">iTunes</a>). Keep in mind that LimitlessLED bulbs are controlled via groups. You can not control an individual bulb via the bridge, unless it is in a group by itself. Note that you can assign an <code class="highlighter-rouge">rgbw</code>, <code class="highlighter-rouge">rgbww</code> and <code class="highlighter-rouge">white</code> group to the same group number, effectively allowing 12 groups (4 <code class="highlighter-rouge">rgbww</code>, 4 <code class="highlighter-rouge">rgbw</code> and 4 <code class="highlighter-rouge">white</code>) per bridge.</p>
 <p>To add <code class="highlighter-rouge">limitlessled</code> 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">light</span><span class="pi">:</span>
@@ -138,7 +138,7 @@
   </li>
   <li><strong>White</strong>
     <ul>
-      <li>When using a legacy wifi bridge (before v6), you can observe on the MiLight mobile application, you can not select a specific brightness or temperature - you can only step each property up or down. There is no indication of which step you are on. This restriction, combined with the unreliable nature of LimitlessLED transmissions, means that setting white bulb properties is done on a best-effort basis. The only very reliable settings are the minimum and maximum of each property.</li>
+      <li>When using a legacy WiFi bridge (before v6), you can observe on the MiLight mobile application, you can not select a specific brightness or temperature - you can only step each property up or down. There is no indication of which step you are on. This restriction, combined with the unreliable nature of LimitlessLED transmissions, means that setting white bulb properties is done on a best-effort basis. The only very reliable settings are the minimum and maximum of each property.</li>
       <li><em>Temperature</em>: Wifi bridge v6 supports 101 temperature steps; older versions only 10.</li>
       <li><em>Brightness</em>: Wifi bridge v6 supports 101 brightness steps; older versions only 10.</li>
     </ul>

components/light.rflink/index.html

@@ -133,7 +133,7 @@
         <span class="s">name</span><span class="pi">:</span> <span class="s">Bedroom Lamp</span>
 </code></pre>
 </div>
-<p>Any on/off command from any allias ID updates the current state of the light. However when sending a command through the frontend only the primary ID is used.</p>
+<p>Any on/off command from any alias ID updates the current state of the light. However when sending a command through the frontend only the primary ID is used.</p>
 <h3><a class="title-link" name="light-types" href="#light-types"></a> Light types</h3>
 <p>Light devices can come in different forms. Some only switch on and off, other support dimming. Dimmable devices might not always respond nicely to repeated <code class="highlighter-rouge">on</code> command as they turn into a pulsating state until <code class="highlighter-rouge">on</code> is pressed again (for example KlikAanKlikUit). The RFLink component support three types of lights to make things work in every situation:</p>
 <ul>

components/light.wink/index.html

@@ -85,7 +85,7 @@
   <li>Wink light groups (User created groups of lights)</li>
 </ul>
 <p class="note">
-The above devices are confimed to work, but others may work as well.
+The above devices are confirmed to work, but others may work as well.
 </p>
 </article>
         </div>

components/light.x10/index.html

@@ -88,7 +88,7 @@
 </div>
 <p>Configuration variables:</p>
 <ul>
-  <li><strong>id</strong> (<em>Required</em>): Device identifier. Composed of house code und unit id.</li>
+  <li><strong>id</strong> (<em>Required</em>): Device identifier. Composed of house code and unit id.</li>
   <li><strong>name</strong> (<em>Optional</em>): A friendly name for the device. By default <em>id</em> from the device is used.</li>
 </ul>
 </article>

components/light.yeelight/index.html

@@ -104,7 +104,7 @@
 <p class="note">
 Before trying to control your light through Home Assistant, you have to setup your bulb using Yeelight app. ( <a href="https://play.google.com/store/apps/details?id=com.yeelight.cherry&amp;hl=fr">Android</a>, <a href="https://itunes.apple.com/us/app/yeelight/id977125608?mt=8">IOS</a> ).
 In the bulb property, you have to enable “Developer Mode”  Developer mode may only be available with the latest firmware installed on your bulb.  Firmware can be updated in the application after connecting the bulb.
-Determine your bulb ip (using router, software, ping …)
+Determine your bulb IP (using router, software, ping …)
 </p>
 <p class="note warning">
 This component is tested to work with the following models. If you have a different model and it is working please let us know.

components/mailgun/index.html

@@ -164,6 +164,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/media_player.firetv/index.html

@@ -8,7 +8,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
     <title>FireTV - Home Assistant</title>
     <meta name="author" content="Home Assistant">
-    <meta name="description" content="Instructions how to integrate FIre-TV into Home Assistant.">
+    <meta name="description" content="Instructions how to integrate Fire-TV into Home Assistant.">
     <meta name="viewport" content="width=device-width">
     <link rel="canonical" href="https://home-assistant.io/components/media_player.firetv/">
     <meta property="fb:app_id" content="338291289691179">
@@ -16,12 +16,12 @@
     <meta property="og:site_name" content="Home Assistant">
     <meta property="og:url" content="https://home-assistant.io/components/media_player.firetv/">
     <meta property="og:type" content="article">
-    <meta property="og:description" content="Instructions how to integrate FIre-TV into Home Assistant.">
+    <meta property="og:description" content="Instructions how to integrate Fire-TV into Home Assistant.">
     <meta property="og:image" content="https://home-assistant.io/images/default-social.png">
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:site" content="@home_assistant">
     <meta name="twitter:title" content="FireTV">
-    <meta name="twitter:description" content="Instructions how to integrate FIre-TV into Home Assistant.">
+    <meta name="twitter:description" content="Instructions how to integrate Fire-TV into Home Assistant.">
     <meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
     <link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
     <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">

components/media_player.kodi/index.html

@@ -251,7 +251,7 @@
         <span class="s">method</span><span class="pi">:</span> <span class="s">System.Shutdown</span>
 </code></pre>
 </div>
-<h4>Turn on and off the TV with the Kodi JSON-CEC Addon</h4>
+<h4>Turn on and off the TV with the Kodi JSON-CEC Add-on</h4>
 <p>For Kodi devices running 24/7 attached to a CEC capable TV (OSMC / OpenElec and systems alike running in Rasperry Pi’s, for example), this configuration enables the optimal way to turn on/off the attached TV from Home Assistant while Kodi is always active and ready:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">media_player</span><span class="pi">:</span>
   <span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">kodi</span>

components/media_player.spotify/index.html

@@ -118,7 +118,7 @@ Controlling the Spotify component (pause, play, next, etc) requires a Premium ac
 <h2><a class="title-link" name="setup" href="#setup"></a> Setup</h2>
 <p>After the prerequisites and configuration are complete, restart Home Assistant. A <strong>Spotify</strong> configurator element will be available. Follow the instructions to authorize Home Assistant to access your Spotify account. A Spotify media player will then appear. If Spotify prompts you to download a file after completing authorization, discard the download. It is not needed.</p>
 <h2><a class="title-link" name="sources" href="#sources"></a> Sources</h2>
-<p>The sources are based on if you have streamed to these devices before in Spotify. If you don’t have any sources, then simply stream from your phone to another device in your house, bluetooth, echo, etc. Once you do the sources will show up in the developer console as a device to cast/stream to. Also know that the devices won’t show up in the dev-console as sources unless they are powered on as well.</p>
+<p>The sources are based on if you have streamed to these devices before in Spotify. If you don’t have any sources, then simply stream from your phone to another device in your house, Bluetooth, echo, etc. Once you do the sources will show up in the developer console as a device to cast/stream to. Also know that the devices won’t show up in the dev-console as sources unless they are powered on as well.</p>
 <h2><a class="title-link" name="uri-links-for-playlistsetc" href="#uri-links-for-playlistsetc"></a> URI Links For Playlists/Etc</h2>
 <p>You can send playlists to spotify via the “media_content_type”: “playlist” and “media_content_id”: “spotify:user:spotify:playlist:37i9dQZF1DWSkkUxEhrBdF” which are a part of the media_player.play_media service, you can test this from the services control panel in the Home Assistant frontend.</p>
 <p>In this example this is a URI link to the Reggae Infusions playlist, the link below from Spotify explains how to get this URI value to use for playlists in the Spotify component.</p>

components/media_player.universal/index.html

@@ -115,7 +115,7 @@
 <p>The universal media player will primarily imitate one of its <em>children</em>. The first child in the list that is active (not idle/off) will be controlled the universal media player. The universal media player will also inherit its state from the first active child. Entities in the <em>children</em> list must be media players.</p>
 <p>It is recommended that the command <em>turn_on</em>, the command <em>turn_off</em>, and the attribute <em>state</em> all be provided together. The <em>state</em> attribute indicates if the Media Player is on or off. If <em>state</em> indicates the media player is off, this status will take precedent over the states of the children. If all the children are idle/off and <em>state</em> is on, the universal media player’s state will be on.</p>
 <p>It is also recommended that the command <em>volume_up</em>, the command <em>volume_down</em>, the command <em>volume_mute</em>, and the attribute <em>is_volume_muted</em> all be provided together. The attribute <em>is_volume_muted</em> should return either True or the on state when the volume is muted. The <em>volume_mute</em> service should toggle the mute setting.</p>
-<p>When providing <em>select_source</em> as a command, it is recomended to also provide the attributes <em>source</em>, and <em>source_list</em>. The <em>source</em> attribute is the currently select source, while the <em>source_list</em> attribute is a list of all available sources.</p>
+<p>When providing <em>select_source</em> as a command, it is recommended to also provide the attributes <em>source</em>, and <em>source_list</em>. The <em>source</em> attribute is the currently select source, while the <em>source_list</em> attribute is a list of all available sources.</p>
 <p>Below is an example configuration.</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">media_player</span><span class="pi">:</span>
   <span class="s">platform</span><span class="pi">:</span> <span class="s">universal</span>

components/media_player.yamaha/index.html

@@ -101,7 +101,7 @@
 <ul>
   <li>Not specifying the host variable will result in automatically searching your network for Yamaha Receivers. It will add a media player device for each one.</li>
   <li>For receivers that support more than one zone, Home Assistant will add one media player per zone supported by the player, named “$name Zone 2” and “$name Zone 3”.</li>
-  <li>In some cases, autodiscovery fails due to a known bug in the receiver’s firmware. It is possible to manually specify the receiver’s IP address or via it’s hostname (if it is discoverably by your DNS) then.</li>
+  <li>In some cases, auto-discovery fails due to a known bug in the receiver’s firmware. It is possible to manually specify the receiver’s IP address or via it’s hostname (if it is discoverable by your DNS) then.</li>
   <li>Please note: If adding the IP address or hostname manually, you <strong>must</strong> enable network standby on your receiver, or else startup of Home Assistant will hang if you have your receiver switched off.</li>
   <li>Currently, this component supports powering on/off, mute, volume control and source selection. Playback controls, for instance play and stop are available for sources that supports it.</li>
 </ul>

components/mysensors/index.html

@@ -106,9 +106,9 @@
 </div>
 <p>Configuration variables:</p>
 <ul>
-  <li><strong>device</strong> (<em>Required</em>): The path to the serial gateway where it is connected to your Home Assistant host, or the address of the tcp ethernet gateway, or <code class="highlighter-rouge">mqtt</code> to setup the MQTT gateway. Resolving DNS addresses is theoretically supported but not tested.</li>
+  <li><strong>device</strong> (<em>Required</em>): The path to the serial gateway where it is connected to your Home Assistant host, or the address of the TCP Ethernet gateway, or <code class="highlighter-rouge">mqtt</code> to setup the MQTT gateway. Resolving DNS addresses is theoretically supported but not tested.</li>
   <li><strong>baud_rate</strong> (<em>Optional</em>): Specifies the baud rate of the connected serial gateway. Default is 115200.</li>
-  <li><strong>tcp_port</strong> (<em>Optional</em>): Specifies the port of the connected tcp ethernet gateway. Default is 5003.</li>
+  <li><strong>tcp_port</strong> (<em>Optional</em>): Specifies the port of the connected TCP Ethernet gateway. Default is 5003.</li>
   <li><strong>topic_in_prefix</strong> (<em>Optional</em>): Set the prefix of the MQTT topic for messages coming from the MySensors gateway in to Home Assistant. Default is an empty string.</li>
   <li><strong>topic_out_prefix</strong> (<em>Optional</em>): Set the prefix of the MQTT topic for messages going from Home Assistant out to the MySensors gateway. Default is an empty string.</li>
   <li><strong>debug</strong> (<em>DEPRECATED</em>): This option has been deprecated. Please remove this from your config is you have it included. Use the logger component to filter log messages on log level.</li>
@@ -141,7 +141,7 @@ The MQTT gateway requires MySensors version 2.0 and only the MQTT client gateway
 <h3><a class="title-link" name="presentation" href="#presentation"></a> Presentation</h3>
 <p>Present a MySensors sensor or actuator, by following these steps:</p>
 <ol>
-  <li>Connect the serial gateway to your computer or the ethernet or MQTT gateway to your network.</li>
+  <li>Connect the serial gateway to your computer or the Ethernet or MQTT gateway to your network.</li>
   <li>Configure the MySensors component in <code class="highlighter-rouge">configuration.yaml</code>.</li>
   <li>Start hass.</li>
   <li>Write and upload your MySensors sketch to the sensor. Make sure you:

components/nest/index.html

@@ -89,7 +89,7 @@
   <li>Fill in details:
     <ul>
       <li>Product name must be unique. We recommend [email] - Home Assistant.</li>
-      <li>The description, users, urls can all be anything you want.</li>
+      <li>The description, users, URLs can all be anything you want.</li>
       <li>Leave the “Redirect URI” Field blank</li>
     </ul>
   </li>

components/netatmo/index.html

@@ -107,7 +107,7 @@ Click on ‘Create an App’ at the top of the page.</p>
 <img src="/images/screenshots/netatmo_api.png" />
 </p>
 <p class="note">
-The Home Assistant Netatmo platform has only be tested with the classic indoor, outdoor module and rainmeter. There is no support for the windmeter module at this time because developers does not own these modules.
+The Home Assistant Netatmo platform has only be tested with the classic indoor, outdoor module and rain meter. There is no support for the wind meter module at this time because developers does not own these modules.
 </p>
 </article>
         </div>

components/notify.apns/index.html

@@ -183,6 +183,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.aws_lambda/index.html

@@ -196,6 +196,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.aws_sns/index.html

@@ -186,6 +186,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.aws_sqs/index.html

@@ -176,6 +176,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.ciscospark/index.html

@@ -76,7 +76,7 @@
   <hr class="divider">
   <p>The <code class="highlighter-rouge">ciscospark</code> notification platform allows you to deliver notifications from Home Assistant to <a href="https://ciscospark.com/">Cisco Spark</a>.</p>
 <p>To use this notification platform you need to get a developer token. To obtain a token visit <a href="https://developer.ciscospark.com/index.html">Spark for Developers</a></p>
-<p>At this time you also need to specify the <code class="highlighter-rouge">Cisco Spark</code> <code class="highlighter-rouge">roomid</code>. The <code class="highlighter-rouge">roomid</code> can also be found at <a href="https://developer.ciscospark.com/index.html">Spark for Developers</a>. Just look in the Doumentation under Rooms.</p>
+<p>At this time you also need to specify the <code class="highlighter-rouge">Cisco Spark</code> <code class="highlighter-rouge">roomid</code>. The <code class="highlighter-rouge">roomid</code> can also be found at <a href="https://developer.ciscospark.com/index.html">Spark for Developers</a>. Just look in the Documentation under Rooms.</p>
 <p>To enable the Cisco Spark notification 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>
 <span class="s">notify</span><span class="pi">:</span>
@@ -163,6 +163,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.clicksend/index.html

@@ -165,6 +165,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.command_line/index.html

@@ -176,6 +176,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.discord/index.html

@@ -190,6 +190,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.ecobee/index.html

@@ -174,6 +174,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.facebook/index.html

@@ -197,6 +197,9 @@ The phone number used in <strong>target</strong> should be registered with Faceb
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.file/index.html

@@ -168,6 +168,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.free_mobile/index.html

@@ -167,6 +167,9 @@ If you disable and re-enable the SMS API option, please be sure to update your t
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.gntp/index.html

@@ -163,6 +163,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.group/index.html

@@ -175,6 +175,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.hipchat/index.html

@@ -199,6 +199,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.html5/index.html

@@ -363,6 +363,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.instapush/index.html

@@ -189,6 +189,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.joaoapps_join/index.html

@@ -153,6 +153,9 @@
         <li>
             Join Notify
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.knx/index.html

@@ -133,11 +133,158 @@
     </ul>
     </div>
     <div class='section'>
-    <h1 class="title delta">Category Notify</h1>
+    <h1 class="title delta">Category Notifications</h1>
     <ul class='divided'>
+        <li>
+            <a href='/components/notify.apns/'>APNS</a>
+        </li>
+        <li>
+            <a href='/components/notify.aws_lambda/'>AWS Lambda</a>
+        </li>
+        <li>
+            <a href='/components/notify.aws_sns/'>AWS SNS</a>
+        </li>
+        <li>
+            <a href='/components/notify.aws_sqs/'>AWS SQS</a>
+        </li>
+        <li>
+            <a href='/components/notify.ciscospark/'>Cisco Spark</a>
+        </li>
+        <li>
+            <a href='/components/notify.clicksend/'>ClickSend SMS</a>
+        </li>
+        <li>
+            <a href='/components/notify.command_line/'>Command line Notify</a>
+        </li>
+        <li>
+            <a href='/components/notify.discord/'>Discord</a>
+        </li>
+        <li>
+            <a href='/components/notify.ecobee/'>Ecobee Notify</a>
+        </li>
+        <li>
+            <a href='/components/notify.facebook/'>Facebook Messenger</a>
+        </li>
+        <li>
+            <a href='/components/notify.file/'>File</a>
+        </li>
+        <li>
+            <a href='/components/notify.free_mobile/'>Free Mobile</a>
+        </li>
+        <li>
+            <a href='/components/notify.gntp/'>GNTP (Growl)</a>
+        </li>
+        <li>
+            <a href='/components/notify.hipchat/'>HipChat</a>
+        </li>
+        <li>
+            <a href='/components/notify.instapush/'>Instapush</a>
+        </li>
+        <li>
+            <a href='/components/notify.xmpp/'>Jabber (XMPP)</a>
+        </li>
+        <li>
+            <a href='/components/notify.joaoapps_join/'>Join Notify</a>
+        </li>
         <li>
             KNX Notify
         </li>
+        <li>
+            <a href='/components/notify.kodi/'>Kodi</a>
+        </li>
+        <li>
+            <a href='/components/notify.webostv/'>LG WebOS TV notifications</a>
+        </li>
+        <li>
+            <a href='/components/notify.lametric/'>LaMetric Notify</a>
+        </li>
+        <li>
+            <a href='/components/notify.lannouncer/'>Lannouncer</a>
+        </li>
+        <li>
+            <a href='/components/notify.llamalab_automate/'>LlamaLab Automate</a>
+        </li>
+        <li>
+            <a href='/components/notify.mqtt/'>MQTT Notifications</a>
+        </li>
+        <li>
+            <a href='/components/mailgun/'>Mailgun</a>
+        </li>
+        <li>
+            <a href='/components/notify.mailgun/'>Mailgun Notify</a>
+        </li>
+        <li>
+            <a href='/components/notify.matrix/'>Matrix</a>
+        </li>
+        <li>
+            <a href='/components/notify.message_bird/'>MessageBird</a>
+        </li>
+        <li>
+            <a href='/components/notify.mysensors/'>MySensors Notify</a>
+        </li>
+        <li>
+            <a href='/components/notify.mycroft/'>Mycroft AI</a>
+        </li>
+        <li>
+            <a href='/components/notify.nfandroidtv/'>Notifications for Android TV / FireTV</a>
+        </li>
+        <li>
+            <a href='/components/notify.group/'>Notify Group</a>
+        </li>
+        <li>
+            <a href='/components/notify.nma/'>Notify My Android</a>
+        </li>
+        <li>
+            <a href='/components/notify.prowl/'>Prowl</a>
+        </li>
+        <li>
+            <a href='/components/notify.html5/'>Push Notifications</a>
+        </li>
+        <li>
+            <a href='/components/notify.pushbullet/'>Pushbullet</a>
+        </li>
+        <li>
+            <a href='/components/notify.pushetta/'>Pushetta</a>
+        </li>
+        <li>
+            <a href='/components/notify.pushover/'>Pushover</a>
+        </li>
+        <li>
+            <a href='/components/notify.pushsafer/'>Pushsafer</a>
+        </li>
+        <li>
+            <a href='/components/notify.rest/'>REST</a>
+        </li>
+        <li>
+            <a href='/components/notify.smtp/'>SMTP</a>
+        </li>
+        <li>
+            <a href='/components/notify.sendgrid/'>SendGrid</a>
+        </li>
+        <li>
+            <a href='/components/notify.simplepush/'>Simplepush</a>
+        </li>
+        <li>
+            <a href='/components/notify.slack/'>Slack</a>
+        </li>
+        <li>
+            <a href='/components/notify.syslog/'>Syslog</a>
+        </li>
+        <li>
+            <a href='/components/notify.telegram/'>Telegram</a>
+        </li>
+        <li>
+            <a href='/components/notify.telstra/'>Telstra</a>
+        </li>
+        <li>
+            <a href='/components/notify.twilio_call/'>Twilio Call</a>
+        </li>
+        <li>
+            <a href='/components/notify.twilio_sms/'>Twilio SMS</a>
+        </li>
+        <li>
+            <a href='/components/notify.twitter/'>Twitter</a>
+        </li>
     </ul>
     </div>
 </section>

components/notify.kodi/index.html

@@ -272,6 +272,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             Kodi
         </li>

components/notify.lametric/index.html

@@ -166,6 +166,9 @@ Note that icons always begin with “i” while animations begin with “a”. T
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.lannouncer/index.html

@@ -193,6 +193,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.llamalab_automate/index.html

@@ -175,6 +175,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.mailgun/index.html

@@ -192,6 +192,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.matrix/index.html

@@ -167,6 +167,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.message_bird/index.html

@@ -168,6 +168,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.mqtt/index.html

@@ -200,6 +200,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.mycroft/index.html

@@ -153,6 +153,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.mysensors/index.html

@@ -260,6 +260,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.nfandroidtv/index.html

@@ -183,6 +183,9 @@ This is a fully customized JSON you can use to test how the final notification w
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.nma/index.html

@@ -161,6 +161,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.prowl/index.html

@@ -178,6 +178,9 @@
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>

components/notify.pushbullet/index.html

@@ -250,6 +250,9 @@ Don’t forget to <a href="/docs/configuration/basic/">whitelist external direct
         <li>
             <a href='/components/notify.joaoapps_join/'>Join Notify</a>
         </li>
+        <li>
+            <a href='/components/notify.knx/'>KNX Notify</a>
+        </li>
         <li>
             <a href='/components/notify.kodi/'>Kodi</a>
         </li>