This MiOS plugin interfaces with devices in the [http://www.belkin.com/us/wemo Belkin WeMo] range.

[[Image(Screenshot.png)]]

= Supported devices =

* [http://www.belkin.com/us/wemo-switch WeMo Switch]: an appliance switch.
* [http://www.belkin.com/us/wemo-motion/p/P-F7C028-APL WeMo Motion]: a motion sensor.

Supported devices are recognized by the plugin and are presented in the dashboard as a child device.

= Unsupported devices =

* [http://www.belkin.com/us/wemo-baby WeMo Baby]: a remote microphone.

Unsupported devices will not be recognized by the plugin.

= Prerequisite setup =

You will need the official Belkin [https://itunes.apple.com/au/app/wemo/id511376996?mt=8 WeMo app for iOS] to set up new !WeMo devices and add them to your Wi-Fi network.  You will also need the app to upgrade !WeMo firmware.  For day-to-day use you do not need the iOS app at all.

Set up all your !WeMo devices with the iOS app before installing the MiOS plugin.  It is recommended that you assign a fixed IP address to each !WeMo device using your router's DHCP Reservation feature; this will help the MiOS plugin to re-establish connections to the devices more quickly and reliably when it starts.

If you want to interface with If This Then That [https://ifttt.com/ IFTTT], register an account with IFTTT and set up your rules.

= Installing the plugin =

Install the plugin from [http://apps.mios.com/plugin.php?id=3726 apps.mios.com].  If you have !WeMo Motion sensors, or want to receive instant status updates in the dashboard when a switch is changed through the iPhone app or [https://ifttt.com/ IFTTT], also install the [http://apps.mios.com/plugin.php?id=3716 UPnP Event Proxy] plugin.  (Note that the UPnP Event Proxy has [http://code.mios.com/trac/mios_upnp-event-proxy extra uninstallation steps].)

= Discovering !WeMo devices =

On the plugin's main device, click the spanner/wrench and go to the '''Configure''' tab.  Ensure that the '''Enable scan for !WeMo devices on LAN''' option is turned on.

[[Image(Discovery.png)]]

The '''Configure''' page lists all of the !WeMo switch and sensor devices that were found on your LAN.  (Note that sometimes a device will not respond to discovery.  Reload the Luup engine and the plugin will attempt discovery again.  Devices on different subnets will not be discovered.)

For each device that you want Vera to know about, press one of the '''Add''' buttons.  Press '''Add Static''' if you allocated that !WeMo device a fixed IP address through your router; press '''Add Dynamic''' otherwise.

Once you have added all devices, close the device dialog and press '''SAVE'''.

On restarting the Luup engine, child devices will appear for each WeMo device.  You can rename these and place them in rooms.

= Removing devices =

To remove a !WeMo device, go to the '''Configure''' page and press '''Remove''' for the devices that you want to remove.  Close the device dialog and press '''SAVE'''.

[[Image(Removal.png)]]

= Controlling devices =

Child devices follow the same conventions as other MiOS switches and sensors.

== !WeMo switches ==

Switches show their on/off status in the dashboard.  Clicking '''On''' or '''Off''' will change the state.

Service variables:
||= Namespace =||= Variable name =||= Meaning =||
|| urn:upnp-org:serviceId:SwitchPower1 || Status || '''0''' if switch is off; '''1''' if switch is on ||

Actions:
||= Namespace =||= Action name =||= Parameters =||= Meaning =||
|| urn:upnp-org:serviceId:SwitchPower1 || !SetTarget || newTargetValue: '''0''' to turn switch off; '''1''' to turn switch on || Set the switch to the specified state ||

Events:
||= Name =||= Meaning =||
|| A device is turned on or off || The switch status has changed from on to off, or from off to on ||

== !WeMo sensors ==

Sensors show their tripped status in the dashboard.  Clicking '''Arm''' or '''Bypass''' affects only the Vera internal state; it has no effect on the !WeMo sensor and will not affect whether !WeMo rules fire.

Service variables:
||= Namespace =||= Variable name =||= Meaning =||
|| urn:micasaverde-com:serviceId:SecuritySensor1 || Tripped || '''0''' if no motion detected; '''1''' if motion was detected in the last 2 seconds ||
|| urn:micasaverde-com:serviceId:SecuritySensor1 || Armed || '''0''' the sensor is bypassed; '''1''' if the sensor is armed ||

Actions:
||= Namespace =||= Action name =||= Parameters =||= Meaning =||
|| urn:micasaverde-com:serviceId:SecuritySensor1 || !SetArmed || newArmedValue: '''0''' to bypass the sensor; '''1''' to arm the sensor || Set the sensor's arm/bypass state ||

Events:
||= Name =||= Meaning =||
|| A sensor (door/window/motion/etc.) is tripped || Fires when motion is detected ||
|| An armed sensor is tripped || Fires when motion is detected and the sensor is armed ||