Overview

This guide provides instructions for configuring your LoRa Network Server (such as ChirpStack, The Things Network, or similar) to forward device data to the IoT Pro Software Platform.

Prerequisites

• LoRa Network Server installed and operational with at least one LoRa Gateway connected

• Administrative access to your network server console

Device Profile Configuration

Before registering devices to a new application, create a Device Profile with the following settings:

Application Setup

Organization Strategy

Create a separate application for each IoT Pro application to:

• Maintain logical separation of device groups

• Enable application-specific integration endpoints

• Simplify device management and troubleshooting

• Support independent configuration and monitoring

Integration Configuration

Configure HTTP integration for each application:

• Integration Type: HTTP

• Method: POST

• URL: http://57.129.34.12:8900/iotpro/lora/chirpstack?device_param_application_id={application_id}

  • Replace {application_id} with the id for that application. See Applications.

• Headers: Content-Type: application/json

• Payload Format: The uplink payload forwarded to IoT Pro Platform must contain:

{
  "deviceInfo": {
    "devEui": "0101010101010101"
  },
  "data": "qg=="
}

Field Descriptions:

• devEui: Device EUI in hexadecimal format (16 characters)

• data: Base64-encoded payload from the LoRa device

Downlink Management

Queue Handling

Critical: Always flush the device's downlink queue before queuing new commands to prevent stale commands from executing. Most network servers provide this functionality through their web interface or API.

Downlink Configuration

• FPort: All downlinks to IoT Pro devices must use FPort 1

• Encoding: Ensure downlink payloads are properly formatted according to IoT Pro Protocol Overview

• Confirmation: Use confirmed downlinks when command acknowledgment is required