The recommended way to send a downlink is to use the RadioBridge Console API which uses a simple POST request.
Contact Sensor Downlink Example:
Downlink message formats for RadioBridge sensors are documented in the user guides for each product.
If you were looking for configuration information for the Contact Sensor
, you would refer to section 6.3 of the Contact Sensor User Guide
An entire downlink message should always be 8 bytes long (zero padded at the end).
The first byte is always the device identifier. In this example 0x07 would define the type of downlink for a contact sensor.
The second byte defines which types of events are disabled.
The next two pairs of bytes define how long an event must be held before sending an event message.
The Contact Sensor Downlink can be diagrammed as follows:
07 Device Identifier (07 = Contact Sensor)
03 Disable Events Config (00 = none disabled, 01 = closed events, 02 = open events, 03 = both)
FFFF Closed Hold Time before message sent - can be 0 (disabled) to 65535 x 250ms (i.e. 0004 = 1 sec, FFFF = max 4.5 hours)
FFFF Open Hold Time before message sent - can be 0 (disabled) to 65535 x 250ms (i.e. 0004 = 1 sec, FFFF = max 4.5 hours)
0000 Zero padding to make a total of eight bytes for the entire downlink message.
0700 0004 003C 0000
no events disabled
contact must be closed for 1 second to trigger an event
contact must be open for 15 seconds to trigger an event
0702 0E10 0000 0000
open events disabled
contact must be closed for 15 minutes to trigger an event