* 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
* More timeout catch blocks
* Version bump
* Bump Wemo version
* 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
* Visually separated the list of control values from the example.
This will aid people who are quickly skimming the readme. There wasn't anything wrong in the doc. Everything would be clear if the reader is reading thoughtfully. But if they're skimming and looking for what to supply to the node for the first time, their eye is drawn to the JSON example. Since many nodes accept JSON input, and supplying `{"state": "off"}`, `{"state": 0}`, or `{"state": 1}` works, it might take them awhile to realize their oversight.
* Clarification
* Update README.md
* Update README.md
