LOCUS Integration with Third-Party Network Servers

This guide explains how to configure uplink and downlink communication between LOCUS and any third-party Network Server (NS).

Use the settings below to configure uplink data delivery from the LoRaWAN Network Server of your choice to the LOCUS application.
LOCUS Application URL https://locus-pc.tektelic.com/v2/integration

Required Payload Format - JSON

The external NS must decode the uplink payload and send the result to LOCUS in a valid JSON structure.

{
  "recvTime": 1412429658,
  "deviceEui": "647FDA0000000000",
  "fPort": 10,
  "bytes": [
    0,
    103,
    0,
    100
  ],
  "gatewayRxInfo": [
    {
      "gwEui": "647FDAFFFE001111",
      "rssi": -112,
      "snr": 2.5
    }
  ]
}

• {recvTime} - The time the message was received, represented as GPS time in seconds (number of seconds since January 6, 1980);
• {deviceEui} - The unique identifier (EUI-64 format) of the device that sent the message;
• {fPort} - The FPort number used to classify the application or service associated with the message (user-defined application port);
• {bytes} - The plaintext payload sent by the device, represented as an array of unsigned integers (raw data before any decoding);
• {gatewayRxInfo} (optional) - An array containing information about the gateway(s) that received the message. This array is optional but must be provided if you want to update RSSI and SNR data;
• {gatewayRxInfo[].gwEui} - The unique identifier (EUI-64 format) of the gateway that received the message;
• {gatewayRxInfo[].rssi} - The Received Signal Strength Indicator (RSSI) measured by the gateway, expressed as a negative integer in dBm (decibel-milliwatts);
• {gatewayRxInfo[].snr} - The Signal-to-Noise Ratio (SNR) measured by the gateway, expressed as a floating-point number in dB (decibels);

Decoder setup is mandatory on the Network Server.

1. Go to Settings → Uplink Delivery in LOCUS.

2. Copy the value shown in the field LOCUS Application URL.

3. Paste this URL in your Network Server uplink integration settings.

4. This URL is the endpoint where your NS must send uplinks.

   
   

This section defines how downlink commands are delivered from the LOCUS platform to the end devices through the Network Server.

To enable downlink delivery, LOCUS must know the endpoint on your Network Server where downlink requests should be sent.

Example of what LOCUS sends to the Network Server:

{
  "deviceEui": "647FDA0000001111",
  "confirmed": false,
  "msgId": "1",
  "data": {
    "bytes": [-14, -70]
  },
  "fPort": 100
}

The encoder on the NS side must convert this into the correct downlink payload format required by your NS/device.

LOCUS does not modify or transform the payload.

To configure where LOCUS should send downlinks:

Send POST request to the https://locus-api.tektelic.com/api/ns-credentials API endpoint

Request Payload

{
  "tekNsDlUrl": "{your-network-server-endpoint}",
  "region": ""
}

**cURL example**

curl -X 'POST' \
  'https://locus-api.tektelic.com/api/ns-credentials' \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer {Token}' \
  -H 'Content-Type: application/json' \
  -d '{
  "tekNsDlUrl": "{your-network-server-endpoint}",
  "region": ""
}'

LOCUS will NOT transform downlink payloads.
Encoder setup on the NS side is required.

Uplink and downlink integrations require:

• Correct endpoint URLs
• Decoder (Uplink)
• Encoder (Downlink)

If you need assistance retrieving the correct endpoint URL for your NS, please contact support.