What should you see on the Sigfox Backend

During Downlink requests, Arming and Disarming

Downlink

1. Uplink message with the current mode as the first byte and 0x81 as the second byte (Extra long press). Following bytes are FW and HW revisions: For example: 018106010A3536

MODE	EVENT	API ver.	FW ver.	FW ver.	HW	HW
01	81	06	01	0A	35	36
Press me	Extra long press	6.	1.	10	Internal	Internal

2. You should see ACKED when you click on the downlink arrow - this means that the BTS sent the downlink to the device (which does NOT mean that the device received the downlink!)

3. From FW version 6.0.228 and newer you will see a downlink confirmation uplink message. The first byte will be the new mode (if you’ve changed modes) and the second byte will be either 0x15 or 0x16 For example: 0116

MODE	EVENT
01	16
Press me	Downlink configuration confirmation

If you want to see this confirmation message in the FW version 6.0.227 or older, change the value of register 0x0F to 0x0E

Arming

1. Uplink message with the current mode as the first byte and 0x10 as the second byte (Start of arming). For example: 0210

MODE	EVENT
02	10
Guard me	Start of Arming

2. Uplink message with the current mode as the first byte and 0x11 as the second byte (Armed). For example: 0211

MODE	EVENT
02	11
Guard me	Armed/Activated

Disarming

Uplink message with the current mode as the first byte and 0x14 as the second byte (Disarmed) For example: 0214

MODE	EVENT
02	14
Guard me	Disarmed/deactivated