Sigfox Protocol (HTTP JSON callback)
Sigfox on HTTP 5154: JSON device or deviceId, location lat/lng or hex data/payload; HTTP 400 unknown, 200 known.
On Traxelio
What Sigfox trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Sigfox at Traxelio
-
1
Capture a Sigfox fingerprint
Confirm an HTTP JSON body whose unit key is device or deviceId.
-
2
Point Sigfox at 5154
Configure only the Sigfox callback to HTTP 5154. Sigfox on 5154 is not Hoopo on 5231 or Polte on 5214.
-
3
Bind the unit key
An unknown device or deviceId is answered HTTP 400. Bind that key before expecting map points.
-
4
Prove one Sigfox fix
POST one JSON body with location lat/lng or hex data that unpacks coordinates on 5154 and verify a map point.
Still offline after GPS lock
Sigfox still not landing
- Sigfox aimed at the wrong destination
Sigfox on 5154 is not Hoopo on 5231 or Polte on 5214.
- HTTP 400 on every Sigfox POST
The device or deviceId is unknown. Bind that key before debugging GPS.
- HTTP 200, empty map
A known unit with no location and no unpackable hex data stores no new fix. A 0,0 pair reuses the last point.
FAQ
Sigfox leftover questions
Does Sigfox send Concox 0x7878 frames?
No. Sigfox posts a JSON object. The unit key is device or deviceId. A fix sits in location, lat/lng, or hex data.
What does a Sigfox unit send as its unit key?
JSON field device, or deviceId when device is absent. An unknown key is answered HTTP 400 and stores no fix.
Why does a Sigfox POST return 200 without a map fix?
A known unit with no location and no unpackable hex data or payload stores nothing new. A 0,0 pair reuses the last point.
What sits inside Sigfox hex data versus location JSON?
location or lat/lng are decimals. Hex data unpacks packed coordinates. Hex payload is a tagged list; event 0x22 or 0x62 is SOS.
Can a Sigfox unit run SMS setup or a controlled-action flow?
This dialect is positions only. Optional moving, magStatus, temperature, rssi, and seqNumber are extras. There is no SMS family on this row.