Difference between revisions of "Wiring Editor"
(→Inputs) |
|||
| Line 1: | Line 1: | ||
The Wiring Editor is a tool to create logical connections (wirings) between HSYCO's inputs and outputs. It can be used, for instance, to quickly and easily make a button turn on/off a light or control a dimmer or an automation or, again, activate a scenario. It provides for a set of functionalities which are often implemented in home automation installation without having to resort to complex programming. | The Wiring Editor is a tool to create logical connections (wirings) between HSYCO's inputs and outputs. It can be used, for instance, to quickly and easily make a button turn on/off a light or control a dimmer or an automation or, again, activate a scenario. It provides for a set of functionalities which are often implemented in home automation installation without having to resort to complex programming. | ||
| − | + | ||
An input is something that triggers an event. It can be: a readable I/O Server's datapoint, a User event (e.g. an event triggered by a User button), a scheduler event or a group of inputs. | An input is something that triggers an event. It can be: a readable I/O Server's datapoint, a User event (e.g. an event triggered by a User button), a scheduler event or a group of inputs. | ||
| + | |||
| + | Inputs are divided into 2 categories: those whose value is binary (has value "0" or "1", generally used to activate/deactivate an output or a scenario) and those whose value correspond to a general numeric value (used, for instance, to set an output to a specific value). | ||
Revision as of 16:37, 25 February 2014
The Wiring Editor is a tool to create logical connections (wirings) between HSYCO's inputs and outputs. It can be used, for instance, to quickly and easily make a button turn on/off a light or control a dimmer or an automation or, again, activate a scenario. It provides for a set of functionalities which are often implemented in home automation installation without having to resort to complex programming.
An input is something that triggers an event. It can be: a readable I/O Server's datapoint, a User event (e.g. an event triggered by a User button), a scheduler event or a group of inputs.
Inputs are divided into 2 categories: those whose value is binary (has value "0" or "1", generally used to activate/deactivate an output or a scenario) and those whose value correspond to a general numeric value (used, for instance, to set an output to a specific value).
