Helpful

CallbacksService callback

Acknowledge

Send network acknowledgment confirming the downlink message emission from the network whatever the Downlink mode (DIRECT or a CALLBACK Downlink).

When a message needs to be acknowledged, the selected callback for downlink must contain data. It must contain 8 bytes of data that will be sent to the device asking for acknowledgment. The data is JSON formatted, and must be structured as follows:

{    "device_id":{
        "downlinkData":"deadbeefcafebabe"
     }
}

   

With device_id being replaced by the corresponding device id, in hexadecimal format.

With batch callbacks, multiple devices may need an acknowledgment. The response must contain the data for all these devices.

{   "device1_id":{
        "downlinkData":"deadbeefcafebabe"
    },
    "device2_id":{
        "downlinkData":"bebebabab0b0b1b1"
    }
}   

   

If the JSON body contains other data or data related to devices not asking for acknowledgment, it will be ignored.

Variable

TypeFormat

Description

time

integerEpoch time in seconds

The GMT timestamp corresponding to the reception date

device 

stringin hexadecimal, up to 8 characters

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

infoCode

Integer
  • 0 (ACKED) 
    the station emitted the answer
  • 1 (NO_ANSWER)
    the customer did not give any answer
  • 2 (INVALID_PAYLOAD)
    the data to send to the device is invalid,
  • 3 (OVERRUN_ERROR)
    the device exceeded its daily downlink quota,
    so it was blocked because of a lower priority
    than transmissions for devices that did not exceed
    their quota,
  • 4 (NETWORK_ERROR) 
    it was not possible to transmit the answer,
  • 5 (PENDING) 
    not technically a code that is sent in the callback because
    it is a transient state before the answer is sent,
  • 6 (NO_DOWNLINK_CONTRACT) 
    the device asked for an answer but its BSS order
    does not allow downlink,
  • 7 (TOO_MANY_REQUESTS) 
    the device asked for an answer before the expiration
    of the listening time,
  • 8 (INVALID_CONFIGURATION) 
    the device type is configured to get data by callback,
    but no BIDIR

This is the status code of the downlink

infoMessage

string

A message associated with the code.

downlinkAck

boolean

True if the station acknowledged the transmission, false else.

downlinkOverusage

boolean

True if the device exceeded its daily quota, false else.

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 >