1.Description
The "Scene" environment requires (per project) the following nodes:
- At least one 19994 master node
- At least one 19995 Scene node (this node) per Master node
The environment settings are made in the master. The scenes are managed by scene nodes.
The use of these nodes creates an accessible endpoint (a URL) on the HomeServer/FacilityServer through which scenes can be created, learned and retrieved. The communication objects used for this purpose must have special entries (Tags) so that they can be used in the scene environment.
Several scenes can be created per scene node. Furthermore, several scene nodes can be used, e.g. to group scenes.
For each node, the communication objects it can manage can be determined.
Each scene can be learned and called up individually.
The use of these nodes creates an accessible endpoint (a URL) on the HomeServer/FacilityServer through which scenes can be created, learned and retrieved. The communication objects used for this purpose must have special entries (Tags) so that they can be used in the scene environment.
Several scenes can be created per scene node. Furthermore, several scene nodes can be used, e.g. to group scenes.
For each node, the communication objects it can manage can be determined.
Each scene can be learned and called up individually.
1.1.Communication objects
To use communication objects with the scene nodes, they must be set up as follows: In the HS/FS Expert in communication object management, the following tags must be added under the Endpoint tab:
- [Mandatory]: The tag that allows the scene node to use this communication object (see Input 4).
This tag can be applied several times per communication object! (For example, to make it available to multiple scene nodes) - [Optional]: A tag that tells the scene node which communication object to use when learning a scene.
Must be specified only if not the communication object itself, but another communication object is to be used when learning a scene!
The tag to be entered has the following format:"_r_x_y_z", where x_y_z is the value specified under Endpoint ID.
Note the following: Although a "foreign" communication object specified here must have an Endpoint ID, it does not need any endpoint tags!
This tag may be applied only once per communication object! - [Optional]: A tag that represents a KNX data point format.
Format: "_t_" + Number.
Depending on the specification, different texts appear in the web interface when using this communication object. The current standard formats are described in the following chapter.
Example for the tag field of a communication object with GrpAdr 100/1/2
heating, _t_14068, 2nd_floor| Heating: | Indicator entered in scene node A in Input 4 |
| _t_14068: | Data point formats. Sets the format as a temperature. |
| 2nd_floor: | Indicator entered in scene node B in Input 4. |
Example for the tag field of a communication object with GrpAdr 100/1/3 that uses a foreign CO (105/1/27) for learning in a scene.
_t_5001, _r_105_1_27, Light5, 1st_floor, dimmer| _t_5001: | Data point formats. Sets the format as a percentage. |
| _r_105_1_27: | When learning a scene, the communication object with Endpoint ID CO @ 105_1_27 is used. |
| Light5: | Any indicator that (in this example) has nothing to do with scenes. |
| 2nd_floor: | Indicator entered in scene node B in Input 4. |
| Dimmer: | Indicator entered in scene node C in Input 4. |
1.2.Standard data point formats
The data point formats described here can be specified in the Endpoint tag of a communication object in order to obtain a specially-formatted input and output in the scene node's web interface.
Currently the following formats can be used: The format can only be used for communication objects with the data type specified in square brackets:
Currently the following formats can be used: The format can only be used for communication objects with the data type specified in square brackets:
- "_t_1000" [0..1/DPT 1.xxx]: Switching on/off - (CO * is switched on/CO * is switched off)
- "_t_1008" [0..1/DPT 1.xxx]: Startup/shutdown - (CO * starts up/CO * shuts down)
- "_t_5001" [0..100%/DPT 5.001]: Percent (CO * is set to x%)
- "_t_14068" [16-bit/DPT 9.xxx]: Temperature (CO* is set to x.y°C)
- Not specified: [All]**: (CO * is set to x)
Only one "_t_*" tag may be assigned per communication object!
* = designation of the communication object.
** = communication objects with data types of the HS data type keys 0, 1, and 3-10.
* = designation of the communication object.
** = communication objects with data types of the HS data type keys 0, 1, and 3-10.
2.Inputs
| No. | Name | Initialisation | Description |
|---|---|---|---|
| 1 | Module ID | 0 | Must be connected to the output of a scene master (19994) with the same name. |
| 2 | Call up | 0 | To call up a scene, the scene number is sent to this input. The scenes of a node are consecutively numbered from 1 to n (n = number, which is indicated at Input 5). The number is also displayed in the web interface. |
| 3 | Learn | 0 | To learn a scene, the scene number is sent to this input. The scenes of a node are consecutively numbered from 1 to n (n = number, which is indicated at Input 5). The number is also displayed in the web interface. |
| 4 | Endpoint tag | "" | Enter a text here that serves as a filter for the visible and usable communication objects in this node. All communication objects that have this tag can be used in this node. If no value is specified, no COs are available for this node! To display all COs with an endpoint ID here, a "*" must be specified. Note A communication object can have multiple tags. Important Must be entered as a fixed value in the input! |
| 5 | Max. number of scenes | 255 | Number of maximum usable scenes in this node. In the web interface, exactly this number of scenes is always displayed! Maximum value: 255 Warning Must be entered as a fixed value in the input! |
| 6 | Name | "" | The text specified here serves as a heading for this node in the web interface. Important Must be entered as a fixed value in the input! |
3.Outputs
| No. | Name | Initialisation | SBC | Description |
|---|---|---|---|---|
| 1 | Status | 0 | s | Sends status messages. |
s = send, sbc = send by change
4.Other
| Recalculation during start: | Yes |
|---|---|
| Module is retentive: | Yes |
| Internal designation: | 19995 |
| Category: | Additional modules\Scenes |