Datasheet

The first byte is the Message Type (0x10), which identifies this as a command message.
The second and third bytes are 0x1234 (34 12 in little-endian notation), which is the
unique command ID. This value will be compared against the command lookup table
and redirected to an appropriate command handler function if a matching entry was
found.
The fourth byte indicates that we have a message payload of 1 byte
The fifth byte is the 1 byte payload: 0xFF
Response Messages
Response messages (Message Type = 0x20) are generated in response to an incoming
command, and have the following structure:
By including the Command ID that this response message is related to, the recipient can
more easily correlate responses and commands. This is useful in situations where multiple
commands are sent, and some commands may take a longer period of time to execute than
subsequent commands with a different command ID.
Response messages can only be generate in response to a command message, so the
10 34 12 01 FF
0: Message Type (U8)
1+2: Command ID (U16)
3: Payload Len (U8)
4: Payload (...)
0x10
0x34 0x12
0x01
0xFF
Name
Message Type
Command ID
Payload Length
Payload
Type
U8
U16
U8
Meaning
Always '0x20'
Command ID this message is a response to
[7] More data
[6-5] Reserved
[4-0] Payload length (0..16)
Optional response payload (parameters, etc.)
© Adafruit Industries https://learn.adafruit.com/adafruit-feather-m0-bluefruit-le Page 201 of 238