Merge branch 'wemo_leds' of https://github.com/jaharkes/home-assistant.io into jaharkes-wemo_leds

This commit is contained in:
Fabian Affolter 2016-02-22 15:51:34 +01:00
commit 84dadb0fc4
3 changed files with 43 additions and 29 deletions

View File

@ -1,24 +1,21 @@
---
layout: page
title: "Belkin WeMo Light"
description: "Instructions how to integrate Belkin WeMo lights into Home Assistant."
date: 2016-02-22 07:00
title: "Belkin WeMo Lights"
description: "Instructions how to integrate Belkin WeMo LED lights into Home Assistant."
date: 2016-02-20 00:45
sidebar: true
comments: false
sharing: true
footer: true
logo: belkin_wemo.png
ha_category: Light
ha_iot_class: "Local Polling"
---
The `wemo` light platform allows you to control your [Belkin WeMo](http://www.belkin.com) lights from within Home Assistant.
The `wemo` platform allows you to control your [Belkin WeMo](http://www.belkin.com/us/p/P-F5Z0489/) LED lights from within Home Assistant.
They will be automatically discovered if the discovery component is enabled.
```yaml
# Example configuration.yaml entry
light:
platform: wemo
```
For more configuration information see the [WeMo component](/components/wemo/) documentation.

View File

@ -2,13 +2,14 @@
layout: page
title: "Belkin WeMo Switch"
description: "Instructions how to integrate Belkin WeMo switches into Home Assistant."
date: 2015-03-23 19:59
date: 2016-02-20 00:47
sidebar: true
comments: false
sharing: true
footer: true
logo: belkin_wemo.png
ha_category: Switch
ha_iot_class: "Local Push"
---
@ -16,22 +17,4 @@ The `wemo` platform allows you to control your [Belkin WeMo](http://www.belkin.c
They will be automatically discovered if the discovery component is enabled.
```yaml
# Example configuration.yaml entry
switch:
platform: wemo
```
Alternately, wemos 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:
```yaml
switch:
platform: wemo
static:
- 192.168.1.23
- 192.168.52.172
```
Any WeMo devices that are not statically configured but reachable via discovery will still be added automatically.
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.
For more configuration information see the [WeMo component](/components/wemo/) documentation.

View File

@ -0,0 +1,34 @@
---
layout: page
title: "Belkin WeMo devices"
description: "Instructions how to integrate Belkin WeMo devices into Home Assistant."
date: 2016-02-20 00:41
sidebar: true
comments: false
sharing: true
footer: true
logo: belkin_wemo.png
ha_category: Hub
---
The `wemo` component is the main component to integrate various [Belkin WeMo](http://www.belkin.com/us/Products/home-automation/c/wemo-home-automation/) devices with Home Assistant.
Supported devices will be automatically discovered if the discovery component is enabled. If you are not using the discovery component, loading the `wemo` component will scan for WeMo devices on the local network.
```yaml
# Example configuration.yaml entry
wemo:
```
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:
```yaml
wemo:
static:
- 192.168.1.23
- 192.168.52.172
```
Any WeMo devices that are not statically configured but reachable via discovery will still be added automatically.
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.