2 devices 2 brands

DMT HTTP Protocol (JSON Records / Edge)

DMT HTTP on Traccar TCP 5139: JSON IMEI+Records+FType or device-edge objects; HTTP 200/400 replies.

Connect your tracker

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

Quick answers

Stock Traccar port?

TCP 5139 (HTTP listener).

JSON shapes?

Traditional IMEI+Records+FType, or edge device object.

vs binary dmt?

HTTP JSON here; binary HELLO/DATA on 5137.

dmthttp on Traccar TCP 5139 is the HTTP/JSON sibling of binary dmt. DmtHttpProtocol installs HttpRequestDecoder / aggregator; DmtHttpProtocolDecoder (extends BaseHttpProtocolDecoder) branches: traditional root keys IMEI, Records (each with SeqNo, Reason, DateUTC, Fields / FType GPS/IO/analogue) versus edge roots with device. Successful decode answers HTTP 200, failures 400.

HTTP twin of dmt 5137

Binary 0x02 0x55 units on 5137 will never speak this JSON contract — keep the twins on separate ports.

Catalogue stance

Stock Traccar reference. positions_only.

Setup walkthrough

  1. 1

    POST JSON, do not open raw TCP binary

    Content must be JSON with IMEI/Records or device — not 0x02 0x55 frames.

  2. 2

    Target HTTP port 5139

    Configure the device’s HTTP endpoint host and port 5139.

  3. 3

    Include FType 0 GPS fields

    Lat/Long/GpsUTC live under Fields entries with FType 0.

  4. 4

    Expect HTTP status answers

    200 means accepted; 400 means bind/parse failure — check IMEI registration.

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:5139 2 example models

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

Reference

Configuration reference

Parameter Value
Port 5139

Telemetry fields

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

All Models

All Dmthttp Devices (2)

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

Compatible Brands

Brands Using Dmthttp Protocol

Common troubleshooting

Binary frames on 5139

Move binary firmware to dmt 5137; HTTP decoder rejects non-JSON bodies.

400 on every post

Unknown IMEI or malformed Records/Fields — fix catalogue bind before GPS debug.

Confused with Dragino HTTP 5253

Dragino expects LoRaWAN uplink_message JSON, not DMT Records/FType.

FAQ

Frequently Asked Questions

Does dmthttp share dmt’s 0x02 0x55 header?

No. dmthttp is HTTP JSON only; binary header belongs to dmt 5137.

Support tier?

positions_only.

T
Trax
Online
Say hello to Trax!