Sigfox Protocol (HTTP callback)

Sigfox LPWAN integration on Traccar TCP 5154 accepting HTTP JSON callbacks with deviceId, location, payload, rssi, and seqNumber.

Connect your tracker

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

Quick answers

Port?

TCP 5154 with HTTP codecs.

Who connects?

Sigfox backend → your HTTP listener.

Key JSON fields?

deviceId, location, payload, rssi, seqNumber, optional magStatus/temperature.

Direct modem TCP GPS?

Uncommon; callbacks dominate.

Commands from Traxelio?

Not a full pathway claim; positions_only.

Sigfox devices rarely open a raw GPRS GPS socket to your VPS. Positions usually arrive because the Sigfox backend posts an HTTP callback. Traccar’s SigfoxProtocol wires HTTP codecs on port 5154; SigfoxProtocolDecoder reads JSON keys such as device / deviceId, positionTime / lastSeen, nested location lat/lon, payload, magStatus, temperature, rssi, and seqNumber.

Not a Topflytech twin

If someone asks for )-terminated ASCII on 5154, they are in the wrong integration. Sigfox tickets start in the Sigfox cloud callback UI.

Stance

Catalogue positions_only. Evidence includes Traccar decoder + Sigfox platform docs.

Setup walkthrough

  1. 1

    Create a Sigfox callback toward host:5154

    HTTPS termination per your edge design.

  2. 2

    Map device ids

    Align Sigfox ids with catalogue identities.

  3. 3

    Force a downlink-era uplink test

    Confirm seqNumber increments.

  4. 4

    Validate location object shapes

    Decoder tolerates several layouts — keep a sample of yours.

  5. 5

    Monitor rssi + payload

    Explains sparse LPWAN updates.

Reference

Configuration reference

Parameter Value
Port 5154

Telemetry fields

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

Common troubleshooting

Callbacks 401/403

Edge auth mismatch — fix before blaming decode.

seqNumber stuck

Device not uplinking; check subscription/coverage.

GPRS tracker aimed at 5154

Wrong world — move to its TCP GPS port.

Explore More

Other Protocols

Dingtek

2 devices

Ais

0 devices

Obddongle

0 devices
View All Trackers

FAQ

Frequently Asked Questions

Why HTTP on a 'protocol' page?

For Sigfox, the integration surface is the callback, and Traccar models it as this protocol listener.

Manufacturer evidence?

sigfox.com plus Traccar SigfoxProtocolDecoder.

Connect Sigfox tracker
T
Trax
Online
Say hello to Trax!