Does the coordinator need to have its sleep mode enabled to send queued packets to sleepy endpoints?
No and you typically don’t want to put the coordinator into sleep mode.
When the queue packet command is used the coordinator will check to see
if the endpoint is sleepy, and if it is not then it will send the
message immediately. In other words, the packet is only queued if the
endpoint is sleepy.
If I only used AT sleep mode command without SLEEP_RQ, coordinator still receives STA 0001, is this behavior right?
The sleep mode command ATSM will enable or disable sleep mode, but does not put the device to sleep. If an endpoint has sleep mode enabled but it is not sleeping then the coordinator should not receive the STA 0001 (sleepy endpoint) status message.
What is the relation between SLEEP_RQ pin and sleep mode AT code, do I need both to enter sleep mode?
Yes, you need to first enable sleep mode on the endpoint using the command: ATSM1 and then pull the SLEEP_RQ pin high to enter sleep. Pull the pin low to exit sleep mode.
If I put a packet in the queue, but then send out enough regular packets (SP) that the governor kicks in, what happens to my queued packet?
Queued packets are not saved if the governor is engaged. When the governor has hit the limit, any new send requests through SP or QP will be rejected with an error indicating that the governor is on.
What is the difference between a coordinator and an endpoint?
The SubGig standard defines a very simple star topology where one coordinator device speaks to multiple endpoints. The coordinator is generally controlled by a host processor, typically on a gateway connected to the cloud. A device acting as a ...
Does the coordinator know which endpoints are sleepy ones, and can it give me a list of which ones are/aren’t?
In the next firmware release v1.02 we will have the command ES which will report endpoint status including the sleep mode of the endpoint.