58: Message Box
Read or subscribe to the device's cached down-synced message box on supported firmware. Build 2644 GET responses and subscription updates use field 1 for the stored message-box CRC and field 129 for its content. An empty payload is omitted. Unsupported products return Not Supported (response code 7). Field 129 uses a two-byte little-endian length prefix, even for payloads shorter than 256 bytes. Older firmware used chunk fields 10..14 with one-byte lengths; do not parse field 129 with that legacy layout. The message-frame CRC is separate from field 1. In tracking-session uploads, field 129 can instead carry pending Transmit Now upload data. In that context field 1 still describes the down-synced message box, so it must not be treated as the checksum of the upload payload.
Header
| Field | Name | Description | Type |
|---|---|---|---|
| 5 | Method | Request a service to be perform an action Possible values:
| uint8 |
Payload
| Field | Name | Description | Type | Unit |
|---|---|---|---|---|
| 1 | CRC | Stored checksum of the down-synced message box, separate from the outer message-frame CRC. Integer encoding may omit a high zero byte. | uint16 | |
| 129 | Full Payload | Down-synced message-box bytes in GET responses and subscription updates (up to 1024 bytes in build 2644). Uses a uint16 little-endian length prefix. Tracking-session uploads may use this field for independent Transmit Now data instead. | bytes |
Examples
Synthetic GET request (not a hardware capture)
Code
For convenience, the following constants can be used to reference this message type.