Owntracks: Configuration for DeviceID and UserID

[radh21301]

Owntrack IOS app has the ability to configure the DeviceID and the UserID - like in the screenshot below

Why do I need this:
I use the owntrack app with another server application 'traccar' and not the owntrack server. https://www.traccar.org/
I find traccar to be much better in terms on UI. So, I already have a lot of information logged there which is associated with a certain DeviceID and UserID. And I want Overland-IOS to basically add data to the same device. I presume there could be other applications where these configurations might be useful as well.

[aaronpk]

I think it will work right now if you enter goku/iphone in the Overland device ID setting.

[radh21301]

Hello. I apologize for the significantly delayed response.

I tried your suggestion, but that does not seem to work with Overland-ios (it works when I use the owntracks app, though). Just so you know, I do not have an owntracks server to test this. The server side is the app called Traccar. My mobile clients are overland-ios and the owntracks app.

I looked at the server side logs when I used the owntracks app and the overland app. It looked like gibberish, but then learned that it was in HEX. Not sure if this is helpful, but I used ChatGPT to decode the messages and give me the differences between 2 logs (Log 1 is Owntracks app. Log 2 is the overland app).

Hopefully this is helpful. Let me know if I can do something else to help figure this out.

---

Differences in Format/Structure

Headers:
    Both messages share common HTTP headers like POST / HTTP/1.1, Host, Content-Type, Connection, Accept, Accept-Encoding, and Accept-Language.
    The first message includes additional headers: X-Limit-D, X-Limit-U, User-Agent: OwnTracks/17.3.1 CFNetwork/1496.0.7 Darwin/23.5.0, and Authorization: Basic aXBob2xvZ3k=.
    The second message includes a different User-Agent: Overland/1.3 (iPhone; iOS 17.5.1; Scale/3.00) and a Content-Length of 468, compared to 282 in the first message.

JSON Payload:
    First Message:
        The payload is a JSON object with fields like batt, lon, acc, bs, p, vel, BSSID, SSID, vac, lat, topic, t, conn, m, tst, alt, _type, and tid.
    Second Message:
        The payload follows the GeoJSON Feature format, containing type, geometry (with type and coordinates), and properties (with speed, battery_state, motion, timestamp, horizontal_accuracy, speed_accuracy, vertical_accuracy, battery_level, wifi, course, device_id, altitude, and course_accuracy).

Summary

The main differences in format/structure between the two log messages are:

Headers:
    The first message has additional headers related to OwnTracks specifics (X-Limit-D, X-Limit-U, Authorization), while the second has a simpler set of standard headers.
    The User-Agent strings are different, indicating possibly different versions or configurations of the tracking application.

JSON Payload Structure:
    The first message's JSON is a flat object with many specific fields related to tracking information.
    The second message's JSON uses a more structured GeoJSON Feature format, with geometry and properties nested within the main object.

These differences suggest that the two messages may come from different versions or configurations of the OwnTracks application or related applications, possibly indicating different levels of detail or different methods of reporting location and device status.