Eseal exists for padlocks and container seals that must prove a door moved or a shock hit the box. Traccar listens on TCP 5169 with a line-based ASCII decoder (EsealProtocolDecoder) that pulls customer id, firmware, message type, index, date/time, interval, fix flag, lat/lon, course, speed, door state, acceleration, NFC, battery, and RSSI from one CRLF sentence.
Seal events that matter
Decoded labels include Event-Door, Event-Shock, Event-Drop, Event-Lock, Event-RC-Unlock, plus lifecycle markers Startup, Normal, Button-Normal, and Termination. A map pin without those labels is not a seal audit trail.
Arm / disarm note
The Traccar protocol class advertises custom, alarm-arm, and alarm-disarm data commands. Traxelio still catalogues Eseal as positions_only until a given seal SKU’s command path is reviewed — vendor NFC/SMS unlock tools often finish the field job.
Server aim
Aim the seal firmware at your hostname and TCP 5169. Prove a Startup or Normal line before chasing missing door events. Do not park seals on Motor’s 5202 listener: same “line TCP” idea, different grammar.