Rules Complete Examples - Revision history

Tbezstarosta: /* Temperature out of limit - Output1 ON */

2024-07-29T07:18:33Z

‎Temperature out of limit - Output1 ON

Tbezstarosta: /* CR17 - Digital Inputs - Connection of NETIO T1 Sensor FW 5.0.3+ */

2024-07-15T13:41:24Z

‎CR17 - Digital Inputs - Connection of NETIO T1 Sensor FW 5.0.3+

Tbezstarosta at 13:34, 15 July 2024

2024-07-15T13:34:18Z

Tbezstarosta: /* External Switch ON - All outputs ON with individual Power Up Sequence */

2024-07-08T07:52:27Z

‎External Switch ON - All outputs ON with individual Power Up Sequence

Tbezstarosta at 07:45, 8 July 2024

2024-07-08T07:45:12Z

Bbakala: /* 3. Create RULE for output ON */

2023-11-29T21:35:07Z

‎3. Create RULE for output ON

Bbakala: /* 4. Create RULE for output OFF */

2023-11-29T21:34:56Z

‎4. Create RULE for output OFF

Bbakala: /* 4. Create RULE for output OFF */

2023-11-29T21:34:33Z

‎4. Create RULE for output OFF

Bbakala: /* CR15 - Sunrise/sunset addaptive schedule with deep night off FW 4.0.1+ */

2023-11-29T21:31:50Z

‎CR15 - Sunrise/sunset addaptive schedule with deep night off FW 4.0.1+

Bbakala: /* CR15 - Sunrise/sunset addaptive schedule with deep night off FW 4.0.1+ */

2023-11-29T21:31:31Z

‎CR15 - Sunrise/sunset addaptive schedule with deep night off FW 4.0.1+

@@ Line 615: / Line 615: @@
 </nowiki>
-===  Temperature out of limit  - Output1 ON ===
+===  Temperature out of spec  - Output1 ON===
-Rule name: '''CR17_RULE'''
+Rule name: '''CR17_RULE_1'''
   <nowiki>
+{
@@ Line 624: / Line 624: @@
    "actions":{
      "OUTPUTS/1/ACTION":1
+   }
+}
 </nowiki>

@@ Line 598: / Line 598: @@
 == CR17 - Digital Inputs - Connection of NETIO T1 Sensor  <sup><code>FW 5.0.3+</code></sup>==
-Rule is used for managing outputs status in response to temperature metering connected into Digital Inputs (DI). Typical example of this solution is the temperature metering of server room. In case temperature hit specify temperature, the air-condition (AC) will turn on. As temperature come back to define temperature range, the air-condition (AC) turn off.
+Rule is used for managing outputs status in response to temperature metering connected into Digital Inputs (DI). Typical example of this solution is the temperature metering in server room. In case temperature hits specified temperature, the air-condition (AC) will turn ON.
 === Temperature measurement - condition definition temperature range (15-45)℃ ===

← Older revision		Revision as of 13:34, 15 July 2024
Line 595:		Line 595:
	}		}

		+	</nowiki>
		+
		+	== CR17 - Digital Inputs - Connection of NETIO T1 Sensor <sup><code>FW 5.0.3+</code></sup>==
		+	Rule is used for managing outputs status in response to temperature metering connected into Digital Inputs (DI). Typical example of this solution is the temperature metering of server room. In case temperature hit specify temperature, the air-condition (AC) will turn on. As temperature come back to define temperature range, the air-condition (AC) turn off.
		+
		+	=== Temperature measurement - condition definition temperature range (15-45)℃ ===
		+	NETIO T1 Sensor connected into INPUT n.2
		+
		+	Rule name: '''CR17_TEMP'''
		+
		+	<nowiki>
		+	{
		+	"source":"INPUTS/2/TEMP",
		+	"type":"RANGE",
		+	"upperBound":45,
		+	"lowerBound":15,
		+	"timeHysteresis":1
		+	}
		+	</nowiki>
		+
		+	=== Temperature out of limit - Output1 ON ===
		+	Rule name: '''CR17_RULE'''
		+	<nowiki>
		+	{
		+	"conditions":{
		+	"PAB/CR15_TEMP/IN":false
		+	},
		+	"actions":{
		+	"OUTPUTS/1/ACTION":1
		+	}
		+	}
	</nowiki>		</nowiki>

@@ Line 569: / Line 569: @@
 </nowiki>
-=== External Switch ON  - All outputs ON with individual Power Up Sequence ===
+=== External Switch ON - All outputs ON with individual Power Up Sequence ===
 Rule name: '''CR16_RULE'''

@@ Line 533: / Line 533: @@
+   }
+}
 </nowiki>

@@ Line 497: / Line 497: @@
 In this rule is definition when the output 1 should be enabled (ON). It is combination of two conditions of PAB and scheduler.
-'''This code is saying:''' When is night ( day is false = <code>"PAB/daylight/DAY": false,</code>) and in paralel schedule is not active (set to be off = <code>"SCHEDULE/christmas_off/ACTIVE": false</code>) the result is <code>true</code> and following action (set output 1 to ON <code>"OUTPUTS/1/ACTION": 1</code>)is executed.
+'''This code is saying:''' When is night ( day is false = <code>"PAB/daylight/DAY": false,</code>) and in paralel schedule is not active (set to be off = <code>"SCHEDULE/christmas_off/ACTIVE": false</code>) the result is <code>true</code> and following action (set output 1 to ON <code>"OUTPUTS/1/ACTION": 1</code>) is executed.
 RULE name: '''outON'''

@@ Line 518: / Line 518: @@
 In this rule is definition when the output 1 should be disabled (OFF). It is again combination of two conditions of PAB and scheduler.
-'''This code is saying:''' When it is day now ( day is true = <code>"PAB/daylight/DAY": true,</code>) or the schedule is active (set to be on = <code>"SCHEDULE/christmas_off/ACTIVE": true</code>) the result is <code>true</code> and following action (set output 1 to OFF <code>"OUTPUTS/1/ACTION": 0</code>)is executed.
+'''This code is saying:''' When it is day now ( day is true = <code>"PAB/daylight/DAY": true,</code>) or the schedule is active (set to be on = <code>"SCHEDULE/christmas_off/ACTIVE": true</code>) the result is <code>true</code> and following action (set output 1 to OFF <code>"OUTPUTS/1/ACTION": 0</code>) is executed.
 RULE name: '''outOFF'''

@@ Line 466: / Line 466: @@
 == CR15 - Sunrise/sunset addaptive schedule with deep night off  <sup><code>FW 4.0.1+</code></sup>==
 Control output ON/OFF based on sunrise/sunset times of set location and combine it with standard schedule using rules.
 In this example, output 1 gets turned on every day at 6:00 and switch off 30 minutes after sunrise and gets on again 30 minutes before sunset and turns off at midnight. This is an example of combination PAB output with standard schedule and mask the result of PAB with intervals defined in schedule.

@@ Line 467: / Line 467: @@
 Control output ON/OFF based on sunrise/sunset times of set location and combine it with standard schedule using rules.
 In this example, output 1 gets turned on every day at 6:00 and switch off 30 minutes after sunrise and gets on again 30 minutes before sunset and turns off at midnight. This is an example of combination PAB output with standard schedule and mask the result of PAB with intervals defined in schedule.
 === 1. Configure schedule ===
-Create a schedule with name "christmas_off" and create intervals 00:00 to 06:00 every day.
+Create a schedule with name "christmas_off" and create intervals 00:00 to 06:00 every day. No need to activate the scheduler for any output. Just define it.
 [[File:CR15 schedule christmas off.png]]
@@ Line 490: / Line 492: @@
 </nowiki>
-=== 3. Create rule for output ON ===
+=== 3. Create RULE for output ON ===
-=== PAB definition ===
+RULE name: '''outON'''
   <nowiki>
+{
-   "type": "DAYLIGHT",
+   "conditions": {
-  "longitude": "14.4129433E",
+    "operator": "AND",
-  "latitude": "50.0058144N",
+    "PAB/daylight/DAY": false,
-  "altitude": 247,
+    "SCHEDULE/christmas_off/ACTIVE": false
-   "sunriseDelay": -60,
+  },
-  "sunsetDelay": 60
+   "actions": {
+}
 </nowiki>
-=== Rule definition ===
+=== 4. Create RULE for output OFF ===
-Rule name: '''CR13_RULE'''
   <nowiki>
+{
    "conditions": {
-     "PAB/CR13_PAB/DAY": true
+    "operator": "OR",
    },
    "actions": {
-     "OUTPUTS/1/ACTION": "${COND_RESULT}"
+     "OUTPUTS/1/ACTION": 0
+   }
+}
 </nowiki>