1.Description
The node can be used by the end user to define rules that determine the execution of an action when a specific event (trigger) occurs.
An event can be triggered either by a communication object or by time/date functions.
It is possible to formulate rules in such a way that the associated action is executed each time, or just once.
Communication objects designed to serve as triggers and/or as actions can be made available to the end user by specifying Endpoint tags.
Multiple nodes can be used in the same project, for example, to allow multiple users in the building to set their own rules.
In the standard configuration, the node is found under the URL
An event can be triggered either by a communication object or by time/date functions.
It is possible to formulate rules in such a way that the associated action is executed each time, or just once.
Communication objects designed to serve as triggers and/or as actions can be made available to the end user by specifying Endpoint tags.
Multiple nodes can be used in the same project, for example, to allow multiple users in the building to set their own rules.
In the standard configuration, the node is found under the URL
HTTPS://[IP-ADR]/wenn/.1.1.Communication objects
To use communication objects with the If/Then node, they must be set up as follows: In the HS/FS expert in communication object management, one or more tags must be added under the endpoint tab:
A distinction is made between actions and triggers. Each communication object used in the project can be provided to none, one, or several If/Then nodes for use as a trigger CO, or as an action CO, or for both.
To do this, one or more Endpoint tags must be defined in the CO. The definition of additional endpoint tags is easily possible; the node only considers tags that directly affect it.
A distinction is made between actions and triggers. Each communication object used in the project can be provided to none, one, or several If/Then nodes for use as a trigger CO, or as an action CO, or for both.
To do this, one or more Endpoint tags must be defined in the CO. The definition of additional endpoint tags is easily possible; the node only considers tags that directly affect it.
1.1.1.Triggers and actions
- Triggers: To make the communication object available for this node, the same text which is transferred as fixed text to the node at Input 1 (triggers) must be entered as a tag.
- Action: To make the communication object available for this node, the same text which is transferred as fixed text to the node at Input 2 (actions) must be entered as a tag.
1.1.2.Formats
The texts displayed on a trigger or an action, as well as the format of a possible input field, can be influenced by the definition of various formats dependent on the data type of the communication object.
The abbreviation specified in the "Format" column must be specified as an additional endpoint tag in the CO.
The abbreviation specified in the "Format" column must be specified as an additional endpoint tag in the CO.
| Format | available for the data type | Explanation |
|---|---|---|
| _t_1000 | 1-bit | On/Off |
| _t_1008 | 1-bit | up/down (blinds) |
| _t_1009 | 1-bit | open/closed |
| _t_1101 | 1-bit | Scene (for collaboration with the scene nodes (19994 master and 19995 scene) |
| _t_1102 | 1-bit | Motion detector |
| _t_5001 | 8-bit (0..100%) | Dimmer |
| _t_14068 | Decimal points | Temperature in °C |
1.1.3.Confirmation objects
In an action CO, a confirmation object can be defined using the endpoint tag. This is done by entering the endpoint ID (of the confirmation object) as the tag in the action CO.
Example for an action CO and a confirmation object with Endpoint ID 101_1_1:
Example for an action CO and a confirmation object with Endpoint ID 101_1_1:
"_r_101_1_1": This additional endpoint tag on the action CO sets the confirmation object.2.Inputs
| No. | Name | Initialisation | Description |
|---|---|---|---|
| 1 | Trigger (endpoint tag) | "" | All COs that have the specified string as the endpoint tag are available to the node as a trigger. If no value is specified, no COs are available for this node as triggers. To display all COs with an endpoint ID here, a "*" must be specified. Important Only evaluated at system startup! |
| 2 | Actions (endpoint tag) | "" | All COs that have the specified string as the endpoint tag are available to the node as an action. If no value is specified, no COs are available for this node as actions. To display all COs with an endpoint ID here, a "*" must be specified. Important Only evaluated at system startup! |
| 3 | Lock-out actions (1=locked) | 0 | 1 - The node no longer carries out any actions. Default value: 0 |
| 4 | Lock-out UI (1=locked) | 0 | 1 - It is not possible to access the node. Does not affect the execution or non-execution of existing rules. Default value: 0 |
| 5 | Initial password | "" | A password must be specified! This password can only be used at the first login and for a password change. It must be changed at the first login. For all other logins only the new password can be used. Default value: "" Important Only evaluated at system startup! |
| 6 | Port | 0 | The port specified here must not be changed. Default value: 0 Warning Leave initialisation value 0 set to the default value! You must not specify a fixed value! |
| 7 | Basic path | "/If/" | The sub-path entered here (on the HS/FS) serves as the start page for the node. Default value: "/If/" Example (for the default value): HTTPS://[IP-ADR]/wenn/Important This path must start with a "/" (backslash) and end with a "/" (backslash)! This should also be noted when using the address in a browser. Only evaluated at system startup! |
3.Outputs
| No. | Name | Initialisation | SBC | Description |
|---|---|---|---|---|
| 1 | Counter | 0 | s | Specifies the number of actions performed since the last time the HS/FS was restarted by this node. |
s = send, sbc = send by change
4.Other
| Recalculation during start: | Yes |
|---|---|
| Module is retentive: | Yes |
| Internal designation: | 18160 |
| Category: | Additional modules |