Massimo bc37f40b60 Fixed persistent state deletion upon node update/delete | 5 anni fa | |
---|---|---|
boolean-logic-ultimate | 5 anni fa | |
.gitattributes | 5 anni fa | |
.gitignore | 5 anni fa | |
CHANGELOG.md | 5 anni fa | |
LICENSE | 5 anni fa | |
README.md | 5 anni fa | |
package-lock.json | 5 anni fa | |
package.json | 5 anni fa |
The node performs Boolean logic on the incoming payloads.
The node performs 3 checks (AND,OR,XOR) on the incoming boolean payloads and outputs the result at the same time, as follow:
The node can have a persistent input: the input values are retained after a node-red reboot. That means, that if you reboot your node-red, you don’t need to wait all inputs to arrive and initialize the node, before the node can output a payload.
The node expects a fixed number of topics (configured in the settings) on which it will operate. It will only output a value
when it has seen the expected number of topics. If it ever sees more than the configured number of topics it will log a message then reset its state and start over.
Changing the topic is usually only needed when chaining multiple boolean nodes after each other becuse the topics will then all be the same when delivered to the nodes further down the chain.
Filter output result