I have my coordinator CE set to 1 (Coordinator enable)
I have my coordinator's ST set to 5ms (remote is 10ms)
I have my coordinator's SP set to 30 seconds (remote is 28 seconds - and have tested with 2 seconds on the remote)
I am in API mode.
I am using 64 bit addressing in my transmit packet.
I have mac mode (MM) set to 2 (no MaxStream header, but 802.15.4 acks enabled) - my remote does not support MaxStrem (it could if it were documented somewhere).
I have a packet sniffer - and am able to see traffic both ways.
It starts out fine, requests a beacon, gets one, requests coordination (indicates battery powered, no short address) - gets accepted, sends a "hello" message (custom protocol), followed by a few data requests, the software sends an appropriate response via API, it's transmitted (within 2ms of the last data request) and the remote goes into a sleep mode. Later (about 2 seconds) I send an API transmit request for a message to the remote, and the coordinator simply sends it (and repeats 3 more times since the remote is asleep and doesn't ack).
How do I get the coordinator module to queue this as an indirect message rather than send immediately as a direct message?
The poll request comes 26 seconds later - get's ack'd, but no data (since it was already sent).