Device configuration through downlink message

This article is only used for integrators customer.

In order to set up the collection frequency, and the sensorset index, a configuration downlink message must be sent to the device.

Within Sigfox and Lora network the downlink radio message is triggered on reception of an uplink message. The backend will only be able to transfer the downlink message when the uplink will include a ack flag corresponding to a downlink request. (For deeper understanding of LPWAN DL mecanism).

The HummBox device send specific uplink messages to request configuration from downlinks. Some are triggered by button action, others are sent on a regular basis :

Uplinks Message Name	Message code (byte 0)	Occurancy
Startup	0x00	sent on device reboot
Monitoring	0x01	twice a day
Configuration request	0x40	on user request (push buton)
Manual Calibration request	0x42	on user request (push buton)

The server must filter these messages by checking their content to send the relevant downlink.

Description of each uplink message content:

Configuration request message

	Byte 0	Byte 1	Byte 2	Byte 3	Byte 4	Byte 5	Byte 6
Value	Message Code	firmware release 1	Sensorset Index	module type	CF	Reserved	firmware release 2
Hexa	0x{40}	0x{2a}	0x{0f}	0x{02}	0x{90}	0x{00}	0x{01}

Startup message

	Byte 0	Byte 1	Byte 2	Byte 3	Byte 4	Byte 5	Byte 6
Value	Message Code	temperature	voltage	firmware release 1	module type	reboot cause	firmware release 2
Hexa	0x{00}	0x{13}	0x{a0}	0x{2a}	0x{01}	0x{00}	0x{01}

Monitoring message

	Byte 0	Byte 1	Byte 2	Byte 3	Byte 4	Byte 5	Byte 6
Value	Message Code	firmware no	Sensorset Index	module type	CF	Reserved	FW Ext
Hexa	0x{01}	0x{2a}	0x{0f}	0x{02}	0x{90}	0x{00}	0x{01}

Manual calibration request

	Byte 0	Byte 1	Byte 2	Byte 3	Byte 4	Byte 5	Byte 6
Value	Message Code	firmware no	Sensorset Index	module type	CF	Reserved	FW Ext
Hexa	0x{42}	0x{2a}	0x{0f}	0x{02}	0x{90}	0x{00}	0x{01}

Downlink message structure

Configuration downlink can be used to set up the collection frequency, and the sensorset index.

Sensorset list

Sensor Reference	Sensor set index
Level 7052 resolution 1cm	16
Level 7360, 7369 resolution 1mm	46
Level V3 (2020)	75
Level V3 (2021)	99
Catnip Soil	19
Waterscout Soil	50
Waterscout Soil, rain collector	58
Air Outdoor THr	41
Air Outdoor THr, Rain collector	41
Air Outdoor THr, Wind Speed Vortex	49
Air Outdoor Leaf Wetness	54
Air Outdoor Leaf Wetness, rain collector	60
Air Outdoor Leaf Wetness, wind speed Vortex	61
Air Indoor THr	5
Air Indoor THr, CO2	31
Air Indoor THr, Lumen, PIR, CO2	56
Pressure V1	70
Pressure V2	76
Anemometer	64

Configuration downlink message structure

	Byte 0	Byte 1	Byte 2	Byte 3	Byte 4	Byte 5	Byte 6	Byte 7
Value	Message Code	data	data	data	Collected frequency	Power management value	Device role	sensor set index
Hexa	0x{00}	0x{01}	0x{01}	0x{00}	0x{18}	0x{0e}	0x{00}	0x{10}
Decimal	0	1	1	0	24	14	0	16
Unit	-	-	-	-	Number of transmissions per day	dB	-	-

Authorized values for byte4 (collected frequency) are

Frequency	Value Décimal	Value Hexa
once a day	1	0x01
twice a day	2	0x02
every 6 hours	4	0x04
every 3 hours	8	0x08
every 2 hours	12	0x0C
every hour	24	0x18
every 30 min	48	0x30
every 15 min	96	0x60
every 10 min	144	0x90

In this example the hexadecimal downlink message to be sent is:

{00 01 01 00 18 0e 00 10} 

Downlink : reboot

The downlink message to ask the device to reboot is : 

{05 00 00 00 00 00 00 00} 

Downlink : Wake Up / Hibernation

It is possile to hibernate the devices throught downlink.

The payload to send to the device to hibernate it is : 

{06 00 00 00 00 00 00 00} 

In hibernation mode the device will do a sanity reboot every 2 days. If a downlink is sent to the device, it will wake up. (Any downlinks will wake the device up)