4 devices 3 brands

Dragino Protocol (LoRaWAN HTTP uplink JSON)

Dragino HTTP on Traccar TCP 5253: end_device_ids + uplink_message.decoded_payload Lat/Lon/Hum/BatV/Tem.

Connect your tracker

Enter the tracker IMEI first, then verify your email and continue setup.

Browse 4 supported devices

Quick answers

Stock Traccar port?

TCP 5253 (HTTP).

JSON path for coords?

uplink_message.decoded_payload.Latitude/Longitude.

Device id key?

end_device_ids.device_id.

Dragino on Traccar TCP 5253 is an HTTP decoder aimed at LoRaWAN uplink JSON (often from a network-server webhook). DraginoProtocolDecoder (BaseHttpProtocolDecoder) reads end_device_ids.device_id, then uplink_message.received_at and decoded_payload fields Latitude, Longitude, Hum, BatV, Tem, plus optional ALARM_status → SOS.

LoRa/HTTP IoT, not cellular tracker CSV

Distinct from dmthttp’s IMEI/Records/FType on 5139 and from FleetGuide’s compressed UDP on 5254 (adjacent port). Dragino’s identity is LoRaWAN uplink JSON on 5253.

Catalogue stance

Stock Traccar reference. positions_only.

Setup walkthrough

  1. 1

    Point LoRaWAN webhook at HTTP 5253

    Network-server HTTP integration host + port 5253 — not a raw TCP tracker port.

  2. 2

    Ensure decoded_payload present

    Payload must already be decoded to Lat/Lon/Hum/BatV/Tem keys.

  3. 3

    Register end_device_ids.device_id

    Bind the LoRa device_id string before expecting positions.

  4. 4

    Optional ALARM_status

    Boolean/string true maps to SOS alarm in the open decoder.

Setup

Public setup commands

Use these rows only after confirming the tracker password and SIM settings. Command families can differ between brands even when they use the same protocol.

Setup guidance

Connection supported

gps.traxelio.com:5253 4 example models
LBT1 LGT92 TrackerD TrackerD-LS

Traxelio can receive this model, but public SMS setup depends on SIM or model settings.

Reference

Configuration reference

Parameter Value
Port 5253

Telemetry fields

GPS Location Speed Altitude Heading / Direction Street Address GPS Accuracy Ignition Status Odometer / Mileage Battery Level

All Models

All Dragino Devices (4)

Start with the strongest matches, then use pagination or brand pages for the full compatibility list.

LBT1

LBT1

LGT92

LGT92

TrackerD

TrackerD

TrackerD-LS

TrackerD

Compatible Brands

Brands Using Dragino Protocol

TrackerD

2 devices

LBT1

1 device

LGT92

1 device

Common troubleshooting

Raw LoRa bytes without decoded_payload

Decoder needs decoded Lat/Lon keys — configure NS payload codec first.

Posted to dmthttp 5139

DMT JSON schema differs; use Dragino 5253 for end_device_ids uplinks.

Confused with FleetGuide 5254

5254 is UDP binary signature 0x53 — not HTTP LoRa JSON.

Explore More

Other Protocols

Dmthttp

2 devices

Fleetguide

1 device

Envotech

14 devices
View All Trackers

FAQ

Frequently Asked Questions

Is Dragino cellular?

Stock decoder expects LoRaWAN-style HTTP uplink JSON, not a classic GPRS CSV tracker frame.

Support tier?

positions_only.

Humidity/temp claimed as product features?

Open decoder maps Hum/Tem/BatV when present; Traxelio tier remains positions_only.

Connect Dragino tracker
T
Trax
Online
Say hello to Trax!