Send network acknowledgment confirming the downlink message emission from the network whatever the Downlink mode (DIRECT or a CALLBACK Downlink).
Variable | Type | Format | Description |
time | integer | Epoch time in seconds | The GMT timestamp corresponding to the reception date |
device | string | in 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. |
