Outsafe on HTTP 5200: JSON device, lat, lon, altitude, heading, rssi, origin; receive-time stamp.
On Traxelio
Point this protocol at Traxelio
Confirm HTTP JSON with a string device field and top-level lat/lon. Reject ueToken or $GPRMC captures as the wrong neighbor.
Configure only Outsafe to HTTP 5200. Outsafe on 5200 is not Polte on 5214 or OpenGTS on 5159.
The JSON field device is the key. HTTP 400 means that string is unknown.
Post one JSON body with latitude and longitude on 5200 and verify a map point.
Still offline after GPS lock
Outsafe on 5200 is not Polte ueToken on 5214 or OpenGTS $GPRMC on 5159.
The JSON device string is unknown. Bind that value before debugging GPS.
Outsafe stamps receive time. There is no device timestamp field on this body.
FAQ
No. Outsafe posts a JSON body with a string device field, latitude, longitude, altitude, heading, rssi, and origin.
A known unit gets HTTP 200. An unknown unit gets HTTP 400 and is not plotted.
Outsafe stamps receive time. The body has no device clock field.
Each key is stored as a number, a string, or a boolean. Those extras do not replace latitude and longitude.
This dialect is positions only. The listed unit is Outsafe. There is no SMS family on this row.