Atmel ATSAM3S-EK2 Hoja De Datos
Atmel AVR2055
23
8348D-AVR-06/12
After initialization of stack parameters, the application attempts to start the network.
The ESP device is the network coordinator, so its presence is required for at least
one other device to join successfully.
Once every second, when
Once every second, when
clockTimer
fires, the application updates the
ZCL TIME
CLUSTER SERVER TIME ATTRIBUTE
parameter of its Time cluster.
4.9.1 Pricing interactions
On receipt of a Get Current Price command, the application’s
getCurrentPriceInd()
callback is invoked, outputting to the UART:
<-Get Current Price
and a Publish Price command is sent back, outputting:
->Publish Price:
Event ID: <id>
Event ID: <id>
When
publishPriceResponse()
is invoked, the status of the Publish Price command
is sent to the UART:
+Publish Price Response status (<status>)
4.9.2 Load Control Events
On receipt of a Get Scheduled Events command, the following message will be sent
to the UART:
<-Get Scheduled Events
Start Time: <time>
Number of Events: <number>
Start Time: <time>
Number of Events: <number>
The Thermostat device (see Section
) will periodically send a Report Event
Status command to the ESP. If the event status is Completed, the following message
is output to the UART:
<-Report Event Status Command Completed
EventId: <id>
EventId: <id>
If the event status is Started, the following message is output:
<-Report Event Status Command Started
EventId: <id>
EventId: <id>
If the event status is Received, the following message is output:
<-Report Event Status Command Received
EventId: <id>
EventId: <id>
Every
REQUEST_SENDING_PERIOD
seconds (by default 15), the ESP application sends
a Load Control Event command to Thermostat, but only if the previous event has
been Completed. When this happens, the application outputs:
->Load Control event:
Event ID: <id>
Event ID: <id>