Description

When working as embedded network server, Milesight LoRaWAN gateways support both sending data packets to third party MQTT/HTTP/HTTPS server or receiving the downlink commands to transfer to LoRaWAN end devices.

Requirement

• Milesight LoRaWAN Gateway: UG56, UG63 V1, UG65, UG67, UG8x (Firmware version 80.0.0.64 or later)
• MQTT Server/Broker
• MQTT Client tool: take MQTT Explorer as example

Configuration

Step1. Connect gateway to MQTT broker.

Refer article How to Connect LoRaWAN Gateway to MQTT Broker？to connect gateway to MQTT broker and ensure the broker and MQTT client can receive uplinks from devices.

Step2. Send Downlink Command from Gateway

Set the gateway to send downlink commands to device directly to check if the device can receive the downlink commands and take actions.

Device EUI: the device EUI to send downlink commands

Type: downlink command type. For Milesight devices, please select hex type.

Payload: downlink command content (get from device manufacturer). For Milesight devices, please refer to downlink command contents on corresponding user guides

Port: application port of device. It is 85 by default for Milesight devices.

Confirmed: after enabled, the device will send confirmed packet back to gateway if it receives the command. If not receive, the gateway will resend the downlink command 3 times at most.

Note: for class A type devices, the gateway will add the command to queue and send it when the class A device send uplinks.

Step3. Publish Topic on MQTT Explorer to send downlink data to device. 

There is two type downlink formats:

1. Downlink Data is blank on gateway.

Publish Topic Format :

application/[applicationID]/device/[devEUI]/tx

Example :

From the gateway, we can get the application ID and device EUI about the device we want to control:

So we can publish a topic on the MQTT Explorer like below:

Topic: application/1/device/ 24e124126a148401/tx

Format: json

Content: 

send as below format and replace the data content as downlink command

{"confirmed": true, "fport": 85, "data": "CQEA/w=="}

2. Downlink Data filled in on the gateway end with“/$deveui” (Only UG65/UG67 Support)

Example: /milesight/downlink/$deveui

Publish Topic Format :

/milesight/downlink/[devEUI]

Example :

From the gateway, we can get the device EUI about the device we want to control:

So we can publish a topic on the MQTT Explorer like below:

Topic: /milesight/downlink/24e124126a148401

Format: json

Content: 

send as below format and replace the data content as downlink command

{"confirmed": true, "fport": 85, "data": "CQEA/w=="}

After click Publish, we can go to Network Server > Packets to check. If the gateway have subscribe corresponding downlink topic data successfully, there will be at least one grayed message packet record.

Milesight Device Command Examples

The MQTT downlink command format is fixed as below:

{
"confirmed": true,       //Set as true or false
"fport": 85,            //application port of device
"data": "BwAA/w=="    //base64 format downlink command
}

----END---