Supported Devices

Routario includes built-in native decoders for the most popular GPS tracker protocols. Each protocol has its own TCP/UDP port and handles the full device lifecycle — login, position, heartbeat, and outbound commands.

Protocol decoders are registered at startup, but listeners are opened only for protocols used by active devices. When the last active device using a protocol is removed or changed to another protocol, Routario stops that unused listener.

Cloud devices

Devices already connected to Wialon, Flespi Cloud, Traccar, 3D Tracking, GPS-Server.net, or Google Find Hub can be pulled in via cloud integrations — no direct connection needed. See Cloud Integrations.

---

Protocol Reference

Protocol	Port	Transport	Compatible Devices
Teltonika	5027	TCP + UDP	FMB001, FMB010, FMB020, FMB110, FMB120, FMB125, FMB130, FMB140, FMB204, FMB641, FMB920, FMB930, FMC, TAT, TFT series — any Codec 8 / 8E / 16 / 26 device
GT06 / Concox	5023	TCP	GT06, GT06N, GT06E, Concox GK309, JimiIoT JM-VG01U, and compatible 0x78 0x78 binary frame clones
TK103 / Coban	5001	TCP	Coban TK103, TK103A, TK103B, Xexun XT009, and compatible ASCII-framed clones
H02	5013	TCP	H02-protocol devices — common in low-cost personal and vehicle trackers (*HQ,...# frame)
Meitrack	5020	TCP	MVT100, MVT340, MVT380, T1, T3, T333, T366, T622, TC68S and other Meitrack series
Queclink	5026	TCP	GV55, GV65, GV300, GV300W, GV500, GV600, GL300, GL500, GB100 and compatible GV/GL/GB series
Flespi	5149	TCP	Any device sending Flespi's unified JSON wire format (newline-delimited)
OsmAnd	5055	TCP (HTTP)	OsmAnd Live tracking app for Android/iOS, or any device sending OsmAnd-compatible HTTP GET requests

---

Protocol Details

Teltonika

The Teltonika decoder supports Codec 8, 8E, 16, and 26 binary frames over both TCP and UDP. It decodes the full I/O element set including digital inputs, analog inputs, fuel level, battery voltage, ICCID, driver behaviour events (harsh braking, acceleration, cornering), GNSS PDOP/HDOP, and hundreds of other AVL parameters.

Supported commands: cpureset, getver, getgps, readio, getrecord, getinfo, setparam, getparam, flush, readstatus, getimei, custom (raw text or hex)

Camera support: Teltonika devices can be marked as dashcam-capable in Device Management. Routario exposes HTTP clip upload/list/playback endpoints for Teltonika DualCam and generic HTTP camera clips.

Device setup: In Teltonika Configurator, set the server IP and port to your Routario host on port 5027. Use Codec 8E for best results.

---

GT06 / Concox

Handles the binary 0x78 0x78 (short packet) and 0x79 0x79 (long packet) frame formats used by GT06 and hundreds of compatible Chinese GPS trackers.

Supported commands: reboot, get_info, set_interval, request_position, set_output (relay), custom

---

Meitrack

Full support for the $$-delimited ASCII protocol with optional XOR checksum. Decodes all standard event codes including SOS, power cut, low battery, overspeed, geofence, towing, and tampering as sensor events.

Supported commands: request_position, reboot, set_interval, set_server, set_apn, set_output, set_timezone, custom

---

Queclink

Decodes ASCII +RESP: / +ACK: / +BUFF: messages. Supports GTFRI position reports and event messages: GTIGN (ignition on), GTIGF (ignition off), GTSOS, GTSPD (overspeed), GTTOW (towing), and more.

Supported commands: reboot, get_info, set_interval, request_position, set_output, set_apn, custom — sent as AT+<CMD>=<password>,<params>$

---

H02

Decodes V1, V4 (standard position), NBR (cell-tower LBS), HTBT (heartbeat), and LINK (status) message types.

Supported commands: reboot, request_position, set_interval, set_apn, arm, disarm, set_output, custom

---

OsmAnd

Accepts OsmAnd Live tracking HTTP GET requests and converts them into normalised position records. Useful for tracking smartphones or any device that can POST OsmAnd-compatible requests.

Info

OsmAnd is a receive-only protocol — outbound commands are not supported.

---

Flespi (native)

Devices that connect directly to Routario using Flespi's unified JSON wire format (newline-delimited JSON objects). Distinct from the Flespi Cloud integration, which polls the Flespi API.

---

Adding New Protocols

See Extending Routario → Adding a Protocol Decoder.

---

Dashcam Clips

Devices with camera support can store video clips in Routario.

1. Enable This device has a dashcam for the device in Device Management.
2. Configure the camera media server/upload URL to point at /api/dashcam/upload.
3. Uploaded clips can be browsed from Device Management and shown in History when they overlap the selected time range.

Routario stores uploaded clips under web/uploads/dashcam and exposes:

• /api/dashcam/upload — clip upload endpoint.
• /api/dashcam/clips — list clips for a device and optional time range.
• /api/dashcam/clips/{clip_id}/video — stream the clip video.
• /api/dashcam/clips/{clip_id}/thumbnail — retrieve a thumbnail when available.

If a camera upload does not include coordinates, Routario links the clip to the nearest stored position for that device.