jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Site updated at 2017-08-24 06:43:59 UTC

Browse source
This commit is contained in:
Travis CI 2017-08-24 06:43:59 +00:00
parent 337e2f0247
commit 270647e144
43 changed files with 94 additions and 94 deletions
Download patch file Download diff file Expand all files Collapse all files

8
components/wemo/index.html
View file

@ -75,12 +75,12 @@
</header>
<hr class="divider">
<p>The <code class="highlighter-rouge">wemo</code> component is the main component to integrate various <a href="http://www.belkin.com/us/Products/home-automation/c/wemo-home-automation/">Belkin WeMo</a> devices with Home Assistant.</p>
<p>Supported devices will be automatically discovered if the discovery component is enabled. If you are not using the discovery component, loading the <code class="highlighter-rouge">wemo</code> component will scan for WeMo devices on the local network.</p>
<p>Supported devices will be automatically discovered if the discovery component is enabled. Loading the <code class="highlighter-rouge">wemo</code> component will scan the local network for WeMo devices, even if you are not using the discovery component</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
<span class="s">wemo</span><span class="pi">:</span>
</code></pre>
</div>
<p>Alternately, WeMo devices that are not discoverable can be statically configured. If you have WeMo devices on subnets other than where Home Assistant is running, and/or devices in a remote location reachable over a VPN, you will need to manually configure them. This is also useful if you wish to disable discovery for some wemos, even if they are local. Example static configuration:</p>
<p>Alternately, WeMo devices that are not discoverable can be statically configured. If you have WeMo devices on subnets other than where Home Assistant is running, or devices in a remote location reachable over a VPN, you will need to configure them manually. This is also useful if you wish to disable discovery for some WeMo’s, even if they are local. Example static configuration:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">wemo</span><span class="pi">:</span>
<span class="s">static</span><span class="pi">:</span>
<span class="pi">-</span> <span class="s">192.168.1.23</span>
@ -88,8 +88,8 @@
</code></pre>
</div>
<p>Any WeMo devices that are not statically configured but reachable via discovery will still be added automatically.</p>
<p>Note that if you use this, you may want to configure your router (or whatever runs your DHCP server) to force your WeMo devices to use a static IP address. Check the DHCP section of your router configuration for this ability.</p>
<p>If the device doesn’t seem to work and all you see is the state “unavailable” on your dashboard, check that your firewall doesn’t block incoming request on port 8989 since this is the address to which the WeMo devices sends their update.</p>
<p>Note that if you use this, you may want to set up your router (or whatever runs your DHCP server) to force your WeMo devices to use a static IP address. Check the DHCP section of your router configuration for this ability.</p>
<p>If the device doesn’t seem to work and all you see is the state “unavailable” on your dashboard, check that your firewall doesn’t block incoming request on port 8989 since this is the address to which the WeMo devices send their update.</p>
</article>
</div>
<aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">