Site updated at 2017-01-17 07:50:15 UTC

components/emulated_hue/index.html

@@ -121,6 +121,7 @@ The virtual bridge has the ability to turn entities on or off, or change the bri
   <li><strong>type</strong> (<em>Optional</em>): The type of assistant who we are emulated for. Either <code class="highlighter-rouge">alexa</code> or <code class="highlighter-rouge">google_home</code>.</li>
   <li><strong>host_ip</strong> (<em>Optional</em>): The IP address that your Home Assistant installation is running on. If you do not specify this option, the component will attempt to determine the IP address on its own.</li>
   <li><strong>listen_port</strong> (<em>Optional</em>): The port the Hue bridge API web server will run on. If not specified, this defaults to 8300. This can be any free port on your system.</li>
+  <li><strong>upnp_bind_multicast</strong> (<em>Optional</em>): Whether or not to bind the UPNP (SSDP) listener to the multicast address (239.255.255.250) or instead to the (unicast) host_ip address specified above (or automatically determined). The default is true, which will work for most situations.  In special circumstances, like running in a FreeBSD or FreeNAS jail, you may need to disable this.</li>
   <li>
     <p><strong>off_maps_to_on_domains</strong> (<em>Optional</em>): The domains that maps an “off” command to an “on” command.</p>
 

components/tts/index.html

@@ -156,7 +156,7 @@ If you are running Home Assistant over SSL or from within a container, you will
   <span class="s">message</span><span class="pi">:</span> <span class="s1">'</span><span class="s">May</span><span class="nv"> </span><span class="s">the</span><span class="nv"> </span><span class="s">Force</span><span class="nv"> </span><span class="s">be</span><span class="nv"> </span><span class="s">with</span><span class="nv"> </span><span class="s">you.'</span>
 </code></pre>
 </div>
-<p>Say to the <code class="highlighter-rouge">media_player.floor</code> device entitie:</p>
+<p>Say to the <code class="highlighter-rouge">media_player.floor</code> device entity:</p>
 
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">service</span><span class="pi">:</span> <span class="s">tts.google_say</span>
 <span class="s">entity_id</span><span class="pi">:</span> <span class="s">media_player.floor</span>
@@ -165,7 +165,7 @@ If you are running Home Assistant over SSL or from within a container, you will
 </code></pre>
 </div>
 
-<p>Say to the <code class="highlighter-rouge">media_player.floor</code> device entitie in french:</p>
+<p>Say to the <code class="highlighter-rouge">media_player.floor</code> device entity in French:</p>
 
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">service</span><span class="pi">:</span> <span class="s">tts.google_say</span>
 <span class="s">entity_id</span><span class="pi">:</span> <span class="s">media_player.floor</span>
@@ -186,7 +186,7 @@ If you are running Home Assistant over SSL or from within a container, you will
 
 <h2><a class="title-link" name="cache" href="#cache"></a> Cache</h2>
 
-<p>The component have two caches. Both caches can be controlled with the <code class="highlighter-rouge">cache</code> option in the  platform configuration or the service call <code class="highlighter-rouge">say</code>. A long time cache will be located on the file system. The in-memory cache for fast responses to media players will be auto-cleaned after a short period.</p>
+<p>The component has two caches. Both caches can be controlled with the <code class="highlighter-rouge">cache</code> option in the platform configuration or the service call <code class="highlighter-rouge">say</code>. A long time cache will be located on the file system. The in-memory cache for fast responses to media players will be auto-cleaned after a short period.</p>
 
 
 </article>