Uplink
This callback will trigger 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. To get more information about the format of the configuration. For more information, please refer to the Custom payload configuration section in the Custom callback creation article.
This callback type defines the reception of a user message from a device. Common variables available for Uplink data callback service are:
Variables | Type | Format | Description |
|---|---|---|---|
time | integer | Epoch time in seconds | The event timestamp (in seconds since the Unix Epoch) |
| deviceTypeId | string | in hexadecimal, up to 8 characters | Device Type identifier (in hexadecimal – up to 8 characters <=> 4 bytes) |
deviceId | string | in hexadecimal, up to 8 characters | Device identifier (in hexadecimal – up to 8 characters <=> 4 bytes) |
snr | float | two maximum fraction digits | The signal to noise ratio (in dB – Float value with two maximum fraction digits) Condition: for devicez with contract option NETWORK METADATA |
rssi | float | two 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 | string | in hexadecimal, 4 characters | The base station identifier (in hexadecimal – 4 characters <=> 2 bytes) Condition: for devices with contract option NETWORK METADATA |
data | string | hexadecimal | The user data (in hexadecimal) |
seqNumber | integer | The sequence number of the message if available |
Uplink callback example:
|
