node-red-contrib-boolean-logic-ultimate 1.0.62 → 1.1.0

package/CHANGELOG.md

@@ -3,6 +3,14 @@
 
 # CHANGELOG
 
+<p>
+<b>Version 1.1.0</b> September 2023<br/>
+- NEW: Translator config node. Each boolean logic node can now translate the input payload to a boolean value. For example, you can add "done:true" to the translation table, to convert the input payload "done", to a boolean <i>TRUE</> value.</br>
+</p>
+<p>
+<b>Version 1.0.63</b> September 2023<br/>
+- NEW: Comparator node. Compare the values from 2 input messages.</br>
+</p>
 <p>
 <b>Version 1.0.62</b> August 2023<br/>
 - Math node: added "subtract option".</br>

package/README.md

@@ -38,6 +38,7 @@ Other than true/false, all nodes accepts these strings and convert it to true/fa
 | "home" | true |
 | "not_home" | false |
 
+You can add your own translation command, thanks to the translator-config node.
 
 <br/>
 <br/>
@@ -84,7 +85,7 @@ The node can convert arbitrary input values to true/false. It supports Homeassis
 |Property|Description|
 |--|--|
 | Inputs count | Set the number of different topics to be evaluated. The node will output a message to the flow, after this number of *different* topics arrives. *Remember: each input topic must be different. For example, if you set this field to 3, the node expects 3 different topics.* |
-| Evaluate | Set the property where the input payload is. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
+| Evaluate | It's the msg property to be evaluated. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
 | Filter output | **Output both 'true' and 'false'** results: Standard behaviour, the node will output <b>true</b> and <b>false</b> whenever it receives an input and calculate the boolean logics as output. **Output only 'true'** results: whenever the node receives an input, it outputs a payload <b>true</b> only if the result of the logic is true. <b>False</b> results are filtered out. |
 | Trigger mode | **All topics**: standard behaviour, the node will evaluate each input topic and ouputs the values. At each input change, it will output a msg on the flow. **Single topic + eval other inputs**: the node evaluates all the input topics, but only whenever it receives a msg input with the **specified topic**, it  outputs a msg to the flow.|
 | If input states are undefined | Every time you create a node or modify the node, all inputs are set to undefined. This means that the node will wait the arrive of all topics (for example 3 topics, if you've selected 3 topics in the option), before it can output a payload. This can be a problem if your logic must be operative as soon as you deploy the flow. To overcome this problem, you can "initialize" all the undefined inputs with True or False. **Leave undefined**: Standard behaviour, the node will wait all the "undefined" topics to arrive, then starts a flow with the result. **True or False**: The node is immediately operative, by force the initialization of the "undefined" inputs with "true" or "false".|
@@ -118,7 +119,7 @@ The interrupt flows is able to stop the input messages to exiting the node.
 |Property|Description|
 |--|--|
 | Trigger by topic | Whenever the node receives a payload = false from this topic,it stops output messages to the flow. As soon it receives payload = true from this topic, the output messages start to flow out again. The node will output the current stored message plus an added property "isReplay = true", as soon as it receives a ***msg.play = true*** from this topic. The node will clear the current stored message, as soon as it receives a ***msg.reset = true*** from this topic. |
-| With Input | Set the property where the input payload is. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
+| With Input | It's the msg property to be evaluated. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
 | Then | This property, allow you to auto toggle the selected start state (pass or block) after a timer has elapsed. You can choose from some pre-defined delays. If you have, for example, an Homekit-Bridged nodeset with a thermostat node or security system node in your flow, once node-red restarts, these homekit nodes output a default message to the flow. Just put an InterruptFlow node with a "block at start" behaviour and a toggle delay enabled behind homekit nodes, to temporary stop the chained nodes to receive the unwanted startup message.|
 
 
@@ -190,7 +191,7 @@ The input message is preserved and passed to the output, changing only the topic
 
 |Property|Description|
 |--|--|
-| Input | Set the property where the input payload is. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
+| Input | It's the msg property to be evaluated. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
 
 <br/>
 
@@ -212,7 +213,7 @@ The input message is preserved and passed to the output, changing only the topic
 
 |Property|Description|
 |--|--|
-| Input | Set the property where the input payload is. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
+| Input | It's the msg property to be evaluated. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
 
 <br/>
 
@@ -234,7 +235,7 @@ output2 : outputs the inverted value false/true<br/>
 
 |Property|Description|
 |--|--|
-| Input | Set the property where the input payload is. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
+| Input | It's the msg property to be evaluated. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
 
 <br/>
 
@@ -270,7 +271,7 @@ This is useful if you need to simply send a true or false payload.
 
 |Property|Description|
 |--|--|
-| Input | Set the property where the input payload is. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
+| Input | It's the msg property to be evaluated. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
 
 <br/>
 
@@ -344,7 +345,7 @@ The pourpose of this node is to send a sequence of pulsed commands to for exampl
 
 |Property|Description|
 |--|--|
-| Input | Set the property where the input payload is. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
+| Input | It's the msg property to be evaluated. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
 
 <br/>
 
@@ -389,7 +390,7 @@ The pourpose of this node is to do maths on the incoming values. Each incoming m
 
 |Property|Description|
 |--|--|
-| Input | Set the property where the input payload is. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
+| Input | It's the msg property to be evaluated. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
 
 <br/>
 
@@ -427,7 +428,7 @@ The pourpose of this node is to toggle between true/false, everytime an inboud m
 
 |Property|Description|
 |--|--|
-| Input | Set the property where the input payload is. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
+| Input | It's the msg property to be evaluated. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
 
 <br/>
 
@@ -452,7 +453,7 @@ The railway switcher, switches the input msg flow to one ot the two outputs (upp
 |Property|Description|
 |--|--|
 | Switcher topic | Whenever the node receives a payload from this **topic**, it switches the input messages to an output. |
-| With Input | Set the property where the input payload is. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
+| With Input | It's the msg property to be evaluated. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
 | Then | This property, allow you to auto toggle the selected start state after some time. |
 
 <br/>

package/boolean-logic-ultimate/BlinkerUltimate.html

@@ -86,7 +86,7 @@
 
 |Property|Description|
 |--|--|
-| Input | Set the property where the input payload is. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
+| Input | It's the msg property to be evaluated. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
 
 <br/>
 

package/boolean-logic-ultimate/BooleanLogicUltimate.html

@@ -35,7 +35,8 @@
 					}
 			},
 			restrictinputevaluation: { value: false },
-			delayEvaluation: { value: 0 }
+			delayEvaluation: { value: 0 },
+			translatorConfig: { type: "translator-config", required: false }
 		},
 		inputs: 1,
 		outputs: 3,
@@ -201,6 +202,15 @@
 					(ms)</label>
 				<input style="width:150px" type="text" id="node-input-delayEvaluation" placeholder="Set 0 for no delay">
 			</div>
+			<div class="form-row">
+				<br />
+				<b>Translator</b>
+				<br />
+				<label for="node-input-translatorConfig">
+					<font color="green" size="4px"><i class="fa fa-sign-in" aria-hidden="true"></i></font> Input
+				</label>
+				<input type="text" id="node-input-translatorConfig" />
+			</div>
 		</p>
 	</div>
 	
@@ -218,7 +228,7 @@
 |Property|Description|
 |--|--|
 | Inputs count | Set the number of different topics to be evaluated. The node will output a message to the flow, after this number of *different* topics arrives. *Remember: each input topic must be different. For example, if you set this field to 3, the node expects 3 different topics.* |
-| Evaluate | Set the property where the input payload is. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
+| Evaluate | It's the msg property to be evaluated. *By default, it is "payload", but you can also specify other properties, for example "payload.value"* |
 
 <br/>
 
@@ -232,6 +242,7 @@
 | Remember latest input values after reboot | If checked, 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. Every time you modify the node's config, <b>the retained values are cleared</b>.|
 | Reject non boolean (true/false) input values | If checked, the node will accept only boolean true/false values. Otherwise, it will try to convert the payload value to a logic true/false boolean. |
 | Delay evaluation (ms) | Delays the evaluation until this time (in milliseconds) is elapsed. Each time a message or "topic trigger message" (see **Trigger mode**) arrives, the delay is restarted. This option is useful for debouncing pourposes or simply for adding some delay. For example, you can turn on a light if the room is occupied for a long time, allowing people to fast transit repeatedly, without the need of turning the light on. Another example, if you have many sensors changing state rapidly, you can wait until these sensor reach a quiet state, then evaluate the inputs.|
+| Translator Input | Translates the incoming <code>payload</code> value, to true/false. This allows the compatibility with, for example, **HomeAssistant** nodes. |
 
 <br/>