node-red-contrib-automation-controller 1.1.4
A Node-RED automation controller
node-red-contrib-automationController
The automation controller is used to help out with home automation in mind, but has other purposes as well. The main idea is to keep multiple inputs for the same external component to be handled within this node and output a generic result.
For the easiest example: A button! Click, Double click, Hold/Release are states that the same component reports. This node enables all these states to be handled inside it and outputs a customized result. For more complex usage, the JavaScript field type can be used on multiple fields to enable more comprehensive tasks.
Argument
I was making a test with home automation where an IKEA 5 button implementation went crazy as shown here:
This node is a result of this code and resulted in this:
Fig. 1: Node appearance
Installation
In Node-RED (preferred)
- Via Manage Palette -> Search for "node-red-contrib-automation-controller"
In a shell
- go to the Node-RED installation folder, e.g.:
~/.node-red - run
npm install node-red-contrib-automation-controller
Usage
Fig. 2: Node explaination
The automation controller node is a multi-functional event/State handling node that takes an input and tries to match it against a number of different created rules. Each rule have their own setup on how it should be behave. The purpose of the node is to compress the complexity of the node schematics when having multiple behaviors for a single component, for example a button controlling a light in home automation or a server status that should trigger different gui components to be updated with states.
Fig. 3: Node appearance
The node has up to 10 different rules that can be customized to fit the purpose of the specified function. The node has by default multiple outputs (one for each rule, but can be reconfigured to have only a single output).
Node Configuration
The node configuration sets up how the sensor should react.
Fig. 4: Node properties
Name (optional)
(Optional) The name of this node. (Will change the content of the node to the name)
Input
The field to read and validate against the rule's Match mode (for events) or Activate on and Deactivate on (for states)
Behavior
Tells how the node should react when an execution occurs.
- Allow only single action, Will only allow an execution only when the node is idle.
- Allow all actions, Will freely allow executions of any rule no matter while another rule is active or not.
- Cancel ongoing actions, Will abort all ongoing rule executions when a new rule is executed.
Rule tab list
Each button/tab represents a rule. By clicking on it, the rule is presented.
To add a new rule, pres the + button (there's a maximum of 10 rules).
Item name
(Optional) Sets the name of the currently selected rule.
Match mode
Sets the mode of how this rule should function.
- Event, Will execute and then go back to idle state. (Think of it as a mouse button)
- State, Will execute and keeps active until deactivated. (Think of it as a power button or a switch)
Event
When match
The value to match the input field against. When matched, this rule will be executed.
Cooldown
The time to wait before this action can be executed again. (This will also prevent other rules to be executed if behavior is preventing multiple rules.) (Zero for disabled)
Reset event timeout
The time to wait before the rule's current value is reset to the initial. (Zero for disabled)
State
Activate on
The value to match the input field against to begin execute the rule. JS accepted: This field is designed to handle JavaScript (see JavaScript secion for more info). It will accept the return value to match against the input or, it can return a true/false statement to tell if matched the field.
Deactivate on
The value to match the input field against to halt/stop the execution of this rule. JS accepted: This field is designed to handle JavaScript (see JavaScript secion for more info). It will accept the return value to match against the input or, it can return a true/false statement to tell if matched the field.
Time out
The time to wait before this action can be executed again. (This will also prevent other rules to be executed if behavior is preventing multiple rules.) (Zero for disabled)
Trigger action on activate...
If checked, the Activate on match can occur while already active. Otherwise only Deactivate on match will be checked.
Message on repeat
The message to use for repeat messages:
- JSON, a customly specified JSON message to use.
- Original message, The message that triggered the first activation.
- Latest message, The last message that has entered the node.
Repeat
The time to wait before this action can be executed again. (This will also prevent other rules to be executed if behavior is preventing multiple rules.) (Zero for disabled)
Send on inactive
The message to send when the state becomes inactive either through Deactivate on or the Time out. JS accepted: This field is designed to handle JavaScript (see JavaScript secion for more info). It can return free of choice.
Reset to initial value...
If checked, the output mode's current value will be set to its Initial value. (The result depends on the Output mode that is used.).
Output
The field to be updated with the result of the execution. (To allow multiple rules to be executed on the same input, this field is unique per rule) JS accepted: This field is designed to handle JavaScript (see JavaScript secion for more info). It can return free of choice. Note: input value is named output.
Output engine
Tells how the output should react and work:
- Single value, Sends a simple value.
- Iterate value, Loops (or just raises) from low to high integer values.
- Bouncing value, Bouncing from low to high integer values.
- Fixed values, Uses a predefined list
Engine: Single value
Value
The value to send out to the output field. JS accepted: This field is designed to handle JavaScript (see JavaScript secion for more info). It can return free of choice.
Engine: Iterate value
Initial value
The initial value to use for first execution or when being reset (either by Reset to initial.. or by message input, msg.state='reset'). This value must resolve into an integer number. JS accepted: This field is designed to handle JavaScript (see JavaScript secion for more info). It must return a valid integer, or 0 will be used.
Min
The minimum value to use when cycling through the value. (Must resolve into an integer value less than max value)
Max
The maximum value to use. (Must resolve into an integer value greater than min and initial value) When this value is reached, the loop will either stop executing (if not to cycle) or move to the min value (if to cycle).
Steps
The number of jumps to add to the current value for each iteration/execution. (Must resolve into a positive integer value)
Cycle
If checked, the value will cycle to min value when reached the max. Otherwise, the execution of the rule will be prevented.
Ensure edges reached
If checked, the value will ensure that the max value is sent if the value reached beyond the max value (if steps is greater than 1 it might end up in max+X). And if cycle is checked, the min value will be set (instead of "curValue - (max-min)").
Engine: Bouncing value
Initial value
The initial value to use for first execution or when being reset (either by Reset to initial.. or by message input, msg.state='reset'). This value must resolve into an integer number. JS accepted: This field is designed to handle JavaScript (see JavaScript secion for more info). It must return a valid integer, or 0 will be used.
Min
The minimum value to use. (Must resolve into an integer value less than max value) When this value is reached, the iteration will turn to use the Positive steps.
Max
The maximum value to use. (Must resolve into an integer value greater than min) When this value is reached, the iteration will turn to use the Negative steps.
Positive steps
The number of jumps to add to the current value for each iteration/execution while in the positive mode. (Must resolve into a positive integer value)
Negative steps
The number of jumps to subtract from the current value for each iteration/execution while in the negative mode. (Must resolve into a positive integer value and will automatically be converted to a negative value)
Ensure edges reached
If checked, the value will ensure that the max value is sent if the value reached beyond the max value (if steps is greater than 1 it might end up in max+(X-1) or min-(X-1) and will be converted to just min/max.).
Engine: Fixed values
Initial index
The initial index to use for first execution or when being reset (either by Reset to initial.. or by message input, msg.state='reset'). This value must resolve into a positive integer number matching one of the items (First record starts on zero) JS accepted: This field is designed to handle JavaScript (see JavaScript secion for more info). It must return a valid integer, or 0 will be used.
Index
The value to send when current index maches this row. JS accepted: This field is designed to handle JavaScript (see JavaScript secion for more info). It can return free of choice.
- button
Removes the record of the related row clicked.
+ button
Adds a new record to the fixed values.
Cycle
If checked, the index will move to the first record when cycled through. Otherwise it will prevent the execution.
Engine: Linked rule
Link to rule
The rule to execute instead when this rule is executed.
Mirror effect
If checked, the engine that is executed will work in reverse. (This is convenient if to have two inputs that toggles raise/lower.) Otherwise, the rule will just be executed in normal mode.
Update target rule's last value
If checked, the target (rule linked to) will have it's latest value stored in it for usage with the JavaScript functions. Otherwise, only the current rule will have it's latest value stored.
Special inputs
The msg.state can be used to reset the state of the current output engine. The msg.engineValue can be used to override the current value (before execution, this means that the value will be altered).
JavaScript
Some fields has been JavaScript enabled. The engine works the same way in all different functions. It contains the following access features:
- input: Is available for the When match, activate on and Deactivate on fields and contains the input value.
- output: Is available for the output field and contains the output data of the rule.
- lastValue: Contains the latest executed value from all the rules.
- lastRuleValue: Contains the latest executed value from the current rule.
- lastRuleName: Contains the name of the latest executed rule.
- msg: The active message object.
- console: The console to debug with.
- context: Contains the get. set, keys, global, flow function.
- flow: Contains the get. set, keys function.
- global: Contains the get. set, keys function.
- env: Contains the get function.
- rules: Contains the index(index|name), name(index|name), value(index|name,[newValue]), isActive(index|name), length() functions.
rules object:
- index(rule.index | rule.name): will get the index of the specified rule.
- name(rule.index | rule.name): will get the name of the specified rule.
- value(rule.index | rule.name): will get the latest returned value.
- value(rule.index | rule.name, newValue): will set the current value (it's the value before next execution)
- isActive(rule.index | rule.name): will tell if the specified rule is currently active or not.
- length(): Will get the number of rules that exists in this node.
Examples
Remark: Example flows are present in the examples subdirectory. In Node-RED they can be imported via the import function and then selecting Examples in the vertical tab menu.
Example 1: Basic usage
This example shows the basic usage. The configuration simulates how a button can be clicked, double clicked or hold/release and gives you the result in three different debug nodes.
example-1.json
Fig. 5: Basic usage example
Version history
v1.0.0 Completed documentation and translations v0.1.0 Initial release
