When sending a ZSE Get Scheduled Event command pursuant to Section 188.8.131.52 of SMETS, an HCALCS shall populate that ZCL Command according to Table 184.108.40.206.
On authenticated receipt of ZSE Get Scheduled Event command, the ESME shall send a ZSE Load Control Event command instructing the HCALCS whether it is to be open or closed, and for how long it is to be in that state.
Cluster-specific; not manufacturer specific; client-server; disable default response;
An HCALCS is not required to have a clock and therefore the HCALC is not required to know UTC time
Criticality Level Applied (UINT8)
0x01 = Voluntary
Cooling Temperature Set Point Applied (UINT16)
Heating Temperature Set Point Applied (UINT16)
Average Load Adjustment Percentage Applied (INT8)
Duty Cycle Applied (UINT8)
0x00 (0) = switched OFF; 0x64 (100) = switched ON
See ‘Meaning’ column
Event Control (BITMAP8)
Do not randomise
Signature Type (UINT8)
Table 220.127.116.11: ZSE Report Event Status command
DLMS COSEM Message Templates
Table 18.2 contains Message Templates for all Use Case with DLMS COSEM payloads. These Message Templates are derived from the Mapping Table, and shall be complied with in the construction and population of all such Messages.
Table 18.2: DLMS COSEM Message Templates
Italicised terms in this Section 18.2.1 shall have their DLMS COSEM meaning.
Compact array encoding
The Blue Book definition of attribute 2 of Profile Generic objects may be interpreted as requiring ‘entry’ to be a structure containing a single choice from the DLMS data types. The GBCS interprets it as meaning that ‘entry’ is a structure that can contain multiple choices of DLMS data types. These choices vary between instances of Profile Generic object. To identify these different structures, the naming convention ‘entry_nameOfStructure’ is used.
The GBCS uses the compact-array data type in attribute 2 of Profile Generic objects. Table 18.104.22.168 details the derivation of the contents-description element within the compact-array structure for the structures used in the Profile Generic objects required by this GBCS. These encodings are reflected in the DLMS COSEM Message Templates.