Helpful

CallbacksData callback

Uplink

This callback is triggered when a message has been received from a device.

You can enter a configuration to define custom variables that will be replaced by the parsed data. You can then use these variables in your callback. For more information, please refer to the Custom payload configuration section in the Custom callback creation article.

Available variable for the Uplink data callback service are:

Variable

TypeFormat

Description

time

integer

Epoch time in seconds

The event timestamp (in seconds since the Unix Epoch)

deviceTypeIdstringin hexadecimal, up to 8 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)

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 device data payload

seqNumber

integer

The sequence number of the message if available

Uplink callback example: 

  {	"deviceTypeId":"{deviceTypeId}",
"deviceId":"{deviceId}", "data": "{data}" } 

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 >