Node-RED Nodes that output combinations of consecutive incoming messages
These nodes aim to solve typical use cases where multi-input nodes (something that doesn't exist in Node-RED's concept)
would be convenient. Incoming messages are stored internally by the nodes so combinations of multiple messages can be
provided. Distinction of these messages is based on their topic
property.
node-red-contrib-combine requires Node.js version 7.0.0 or higher.
Forwards messages to the first output when previously received a truthy payload on "Condition Topic", otherwise messages will be routed to the second output.
Logic combination of incoming messages (And, Or, Xor, Nand, Nor, Xnor).
Simple subtraction of the values received on two configured topics.
Bang-bang (2 step / on-off) Controller. Emits true
when the the payload value exceeds the upper bound, emits
false
when the payload goes below the lower bound. You could e.g. use this as a simple thermostat for a
climate control, feed in the actual temperature and use the output to control a cooling device. For a heating
device you would have to use the "invert" option, so you receive false
when exceeding the upper bound and
true
when going below the lower bound.
Calculate statistic samples like e.g. min, max, mean, median, ... from incoming payloads. Message distinction can be
configured to msg.topic
or msg._id
. A timeout can be configured that removes messages from the internal cache.
The statistics are re-composed when a message times out.
Compose a table of consecutive incoming topics and payloads. Output as array, csv, html table or html list. Columns and
sort order can be configured. Message distinction can be configured to msg.topic
or msg._id
. A timeout can be
configured that removes messages from the internal cache. The tables are re-composed when a message times out.
Defer a message with truthy payload for given time. If another message arrives with falsy payload the timer is cancelled. Keeps track on each topics state, only one message per topic will be sent until reset by a falsy payload.
MIT (c) Sebastian Raff