Helpful

CallbacksData callback

Bidir

This callback will trigger when a message has been received from a device including a downlink payload request.

This service required the Downlink mode set to “Callback” in device type settings. For more details refer to Downlink Callback article.

Variables

TypeFormat

Description

time

integerEpoch time in seconds

The event timestamp (in seconds since the Unix Epoch)

deviceTypeIdstringin hexadecimal, up to 24 charactersDevice Type identifier (in hexadecimal – up to 8 characters <=> 4 bytes)

device

stringin hexadecimal, up to 8 characters

Device identifier (in hexadecimal – up to 8 characters <=> 4 bytes)

snr

floattwo maximum fraction digits

The signal to noise ratio (in dB – Float value with two maximum fraction digits)

Condition: for devices with contract option NETWORK METADATA

rssi

floattwo maximum fraction digits

The RSSI (in dBm – Float value with two maximum fraction digits). If there is no data to be returned, then the value is null.

Condition: for devices with contract option NETWORK METADATA

station

stringin hexadecimal, 4 characters

The base station identifier (in hexadecimal – 4 characters <=> 2 bytes)

Condition: for devices with contract option NETWORK METADATA

data

stringhexadecimal

The user data (in hexadecimal)

seqNumber

integer

The sequence number of the message if available

longPollingbool
True if device support long poling mechanism for downlink (required compatible device)

ack

bool

True if this message needs to be acknowledged, false else.

You can decide not to send any answer to the device. There are 2 ways to do so :

  • respond to the callback with the HTTP NO_CONTENT code (204)
  • respond with a JSON data containing the noData field ex :
   {    "0CB3":{
        "noData":true
    }
}

Can't find what you're looking for ?

Have questions? Our worldwide Community of expert fans can answer them.
Have answers? Join the Community and help!

slack logo

Ask the community >