Atmel ATSAM3S-EK2 Hoja De Datos
Atmel AVR2055
21
8348D-AVR-06/12
On receipt of a Read Attributes Response command from the ESP, the internal
Display time will be adjusted, and the following message is sent to UART:
+Read Time response: t = <new time>
4.8 Thermostat
The Thermostat reference application makes use of the following clusters:
Table 4-8. Thermostat application in/out clusters.
Table 4-8. Thermostat application in/out clusters.
In clusters (server clusters)
Out clusters (client clusters)
Basic
Demand response and load control
Time
OTAU (when enabled)
Key establishment (when enabled)
Time
OTAU (when enabled)
Key establishment (when enabled)
each of the clusters it registered.
Table 4-9. Thermostat application cluster interactions.
Cluster
Request/response and indication callbacks
Remarks
Demand response and load control
loadControlEventInd()
cancelLoadControlEventInd()
cancelAllLoadControlEventsInd()
cancelLoadControlEventInd()
cancelAllLoadControlEventsInd()
ZCL_CommandReq() ->
reportEventStatusResponse()
ZCL_CommandReq() confirms load
control event and repots event
status (start and end); also, invokes
Get Schedule Events command
Time
ZCL_AttributeReq() ->
ZCL_ReadAttributeResp()
Gets time attribute
After initialization of stack parameters, the application attempts to join the network.
Every 15 seconds, when
thermostatReadTimeTimer
fires, the application invokes
ZCL_AttributeReq()
to read the current value of the Time attribute stored in the
Time cluster on the ESP device (see Section
). When this happens, the application
outputs:
->Time: read attribute
On receipt of a Read Attributes Response command from the ESP, the internal
Thermostat time will be adjusted, and the following message is sent to UART:
+Read Time response: t = <new time>
On receipt of a Load Control Event command from the EPS,
loadControlEventInd()
callback is invoked, and the application replies with a
Report Event Status command with status value Command Received. When a Load
Control Event command is received, the following information is sent to the UART:
<-Load control Event:
Event id = <id>,
Device class = <class>,
criticality level = <level>,
Event id = <id>,
Device class = <class>,
criticality level = <level>,