Visually separated the list of control values from the example. (#552)

* 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
This commit is contained in:
Robert Leach 2019-07-02 15:08:12 -04:00 committed by Dave Conway-Jones
parent 8cf3c8b990
commit d9ea55d3b2
1 changed files with 11 additions and 5 deletions

View File

@ -19,12 +19,18 @@ 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 accecpts the following inputs
The node accepts the following `msg.payload` inputs
* Strings on/off
* integers 1/0
* boolean true/false
* an Object like this (lights only & color control is still work in the progress)
* A single value
* Accepted values:
* Strings `on`/`off`
* Integers `1`/`0`
* Boolean `true`/`false`
* Example:
```
off
```
* A JSON Object like this (lights only & color control is still work in the progress)
```
{
state: 1,