History

Ben Hardill 6c446a96f2 Add HTTP timeout handler to Wemo nodes. (#629 ) * Reduce resubscription time Halve the resubscrciption timeout to make sure event subscriptions get renewed * Big Update Includes: - New lookup node to check state of a device - Fix dimming control for lights - Fix light group control - Set the node label to match the device name - The event now includes the text description of the light capability * Fix groups properly * Fix travis error with comparitor * Bump node-ssdp version * Add extra check for empty results in discovery * Bump twitter to 280 chars fixes #371 * Bump twitter node version * Remove extra whitespace * Add catch for HTTP timeout If the device drops off line then with no catch for the timeout Node-RED will crash Should fix #616		2020-02-19 12:21:44 +00:00
..
icons	Update WeMo node to WeMo-NG (#199 )	2016-04-09 17:59:36 +01:00
lib	Add HTTP timeout handler to Wemo nodes. (#629 )	2020-02-19 12:21:44 +00:00
LICENSE	Update licenses and packages for all nodes	2016-11-06 20:26:19 +00:00
README.md	bump wemo node	2019-07-02 20:17:43 +01:00
WeMoNG.html	Big WeMo node update (#295 )	2017-04-06 11:21:33 +01:00
WeMoNG.js	Tidy up listing for some nodes. No functional changes	2017-04-12 13:32:08 +01:00
package.json	Add HTTP timeout handler to Wemo nodes. (#629 )	2020-02-19 12:21:44 +00:00

README.md

node-red-node-wemo

A set of Node-RED nodes for working with Belkin WeMo devices.

These nodes use the uPnP discovery so may not discover your devices if you have a firewall enabled

Install

Run the following command in your Node-RED user directory - typically ~/.node-red

npm install node-red-node-wemo

Output node

The output node switches a socket, a light or group of lights on or off

This should be backward compatible with the pervious version of this node but will benefit from opening the config dialog and selecting the node you want.

The node accepts the following msg.payload as input

A single value
- String : on/off
- Integer : 1/0
- Boolean : true/false
A JSON Object as below (lights only and color control is still work in the progress)

   {
     state: 1,
     dim: 255,
     color: '255,255,255',
     temperature: 25000
   }

Note: Currently any invalid value is treated as an off command.

Input Node

The new input node is now based on uPnP notifications instead of polling. This means messages will only be set when an actual change occurs in on the device. This means the node will not send regular no-change messages.

The output varies depending on the type of device but examples for sockets look like this:

   {
     "raw": "<e:propertyset xmlns:e=\"urn:schemas-upnp-org:event-1-0\">\n<e:property>\n<BinaryState>1</BinaryState>\n</e:property>\n</e:propertyset>\n\n\r",
     "state": "1",
     "sid": "uuid:e2c4586c-1dd1-11b2-8f61-b535035ae35d",
     "type": "socket",
     "name": "Bedroom Switch",
     "id": "221448K1100085"
   }

And a lightbulb can look like this:

   {
     "raw": "<e:propertyset xmlns:e=\"urn:schemas-upnp-org:event-1-0\">\n<e:property>\n<StatusChange>&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;&lt;StateEvent&gt;&lt;DeviceID\navailable=&quot;YES&quot;&gt;94103EA2B27803ED&lt;/DeviceID&gt;&lt;CapabilityId&gt;10006&lt;/CapabilityId&gt;&lt;Value&gt;1&lt;/Value&gt;&lt;/StateEvent&gt;\n</StatusChange>\n</e:property>\n</e:propertyset>\n\n\r",
     "id": "94103EA2B27803ED",
     "capability": "10006",
     "value": "1",
     "sid": "uuid:e2e5739e-1dd1-11b2-943d-c238ce2bad17",
     "type": "light",
     "name": "Bedroom"
   }

Insight

  {
    "raw": "<e:propertyset xmlns:e=\"urn:schemas-upnp-org:event-1-0\">\n<e:property>\n<BinaryState>8|1454271649|301|834|56717|1209600|8|1010|638602|12104165</BinaryState>\n</e:property>\n</e:propertyset>\n\n\r",
    "state": "8",
    "power": 1.01,
    "sid": "uuid:ea808ecc-1dd1-11b2-9579-8e5c117d479e",
    "type": "socket",
    "name": "WeMo Insight",
    "id": "221450K1200F5C"
  }