OwnTracks Protocol (_type location JSON)
OwnTracks on HTTP 5144: JSON _type location, topic or tid bind, lat/lon, HTTP 400 unknown, 200 known.
On Traxelio
What Owntracks trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Owntracks at Traxelio
-
1
Capture an OwnTracks fingerprint
Confirm an HTTP JSON body whose _type is location and whose unit key is topic or tid.
-
2
Point OwnTracks at 5144
Configure only OwnTracks HTTP to 5144. OwnTracks on 5144 is not Hoopo on 5231 or Sigfox on 5154.
-
3
Bind topic or tid
An unknown topic or tid is answered HTTP 400. Bind that key before expecting map points.
-
4
Prove one OwnTracks fix
POST one JSON body with _type location, lat, and lon on 5144 and verify a map point.
Still offline after GPS lock
Owntracks still not landing
- OwnTracks aimed at the wrong port
OwnTracks on 5144 is not Hoopo on 5231 or Sigfox on 5154.
- HTTP 200, empty map
_type must be location. A different _type is answered 200 and will not plot.
- HTTP 400 on every post
Bind the topic, or tid when topic is absent, before expecting map points.
FAQ
Owntracks leftover questions
Does OwnTracks send Concox 0x7878 frames?
No. OwnTracks posts JSON with _type location. Concox families use 0x7878 binary login.
Which _type plots an OwnTracks fix?
location. Any other _type is answered HTTP 200 and will not plot.
Does OwnTracks send an ACK?
A known unit is answered HTTP 200. An unknown topic or tid is answered HTTP 400.
Where is the OwnTracks unit key?
topic when present, otherwise tid. lat and lon sit beside tst.
Can an OwnTracks unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.