Warning

This message will be generated if NS experienced some problems during message processing, but still successfully finished processing steps.

Here is an example of the situation when no AS responded to NS downlink_request.

• Device send confirmed uplink message
• NS process confirmed uplink message, prepare downlink_request and send it to the AS
• AS do not answer and do not send downlink_response back to the ns NS
• NS do not get downlink_reseponse from AS, create warning message and send it to AS

Params

Example

{
    "meta": {
        "network": "75697b95",
        "packet_hash": "79f664df2c2073af798fa87497305d8d",
        "application": "70b3d54b17db0106",
        "device_addr": "36c365b4",
        "time": 1504806731.754539,
        "device": "faa73111a2aead2c",
        "packet_id": "fdbb09021c4523d9f28bb815ca872c70",
        "gateway": "7c95bd79864622a4"
    },
    "type": "warning",
    "params": {
        "message": "Requesting downlink message failed: application request timeout. Please check application availability."
    }
}

List of Warnings

• Downlink message with empty payload sent to device <dev_eui>

• Downlink disabled for this device

• Requesting downlink message failed: application request timeout. Please check application availability

• Received packet is outside device band

• Device tried to send join request, but uplinks are blocked on this device

• Device tried to send message, but uplinks are blocked on this device

• Uplink message with repeated counter received