User's Manual

Name JSON
type
Contents
“extensions” object "OTA":”<protocols>|<device type>;<supported file types>”,
"OTASTAT":”<OTA ID>,<device type>,<file type>,<state
code>,<diagnostic code>,<additional status>”
“which” array The number of this message (starting from 1),
the number of messages in the report
The OTA ID field in the OTASTAT value is initialised to 00000000 and updated when any App 107
message is received.
The OTASTAT value will be reset to “00000000,13,0,0,0,” at initialisation and for any fob ID report to
PULS where the MAC ID does not match the previous (if any) fob ID report to PULS.
An example of the JSON object is:
{“ids”:[13,1,”D05FB80DE12F”,0,”1.0a”],”extensions”:{"OTA":"1|13;0","
OTASTAT":"00000000,13,0,0,0,"},"which":[1,1]}
Note that the order within JSON arrays is fixed, but the order in JSON objects is not fixed, and so for
example the “ids” member is not necessarily the first member, and within the “extensions” object
the “OTASTAT” name/value pair may precede the “OTA” name/value pair.
The example above decodes as follows:
Structure Type Value or Name:Value Explanation
ids array 13 Device type for Bluetooth fob
1 Hardware version is the key fob app id
”D05FB80DE12F” MAC ID
0 Firmware file type
“1.0a” Firmware version
extensions object "OTA":"1|13;0" OTA attributes:
supported protocols = 1 (HTTP)
Device type = 13 (Bluetooth fob)
Supported file types = 0 (Firmware)
OTASTAT":"00000000,13,0,0,0," OTA status:
OTAID = 00000000 (timestamp)
Device type = 13 (Bluetooth fob)
File type = 0 (Firmware)
State code = 0
Diag code = 0
Additional status = “” (none)
which array 1 This is message 1
1 Number of messages in report is 1