OsmAnd device not recognized

Hello Anton,

we have implemented a device that uses the OsmAnd protocol but for some reason it is not properly handled by the server. When the server is restarted it indicates that the device is online on the first packet it receives but it does not indicate the location or any subsequent packets until the server is restarted. (running v4.0).

We also have a smartphone that uses the Traccar client and successfully reports into the system, so we tried copying the same POST headers with no luck.

Here is the log information:

2018-09-19 00:17:44  INFO: [9fa007a8] connected
2018-09-19 00:17:44 DEBUG: [9fa007a8: 5055 < 192.168.0.166] HEX: 504f5354202f3f69643d37352674696d657374616d703d323031382d30392d313925323030373a31373a3433266c61743d33372e373937393731266c6f6e3d2d3132322e3434303934362673706565643d312662656172696e673d343226616c7469747564653d3026626174743d31303026646576636f64653d363134373220485454502f312e310d0a557365722d4167656e743a207465737420676174657761790d0a4163636570743a202a2f2a0d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a486f73743a203139322e3136382e302e3232323a353035350d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2018-09-19 00:17:44 DEBUG: [9fa007a8: 5055 > 192.168.0.166] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2018-09-19 00:17:44  INFO: [9fa007a8] disconnected

When the phone sends data via the client, we do see an extra INFO line after the DEBUG line with the 200 OK that shows the successfully decoded data.

Any thoughts?

You either need to use GET, or send data in the body with POST. Sending data in query parameters with POST is incorrect.

Hi Anton,

thank you. I changed it to a GET call and it sort of worked.... it worked sending data to a Win10 PC running Traccar 3.15, but did not work with a CentOS VM running Traccar 4.0.

Here's the log:

18-09-19 20:57:38  INFO: [1215c199] connected
2018-09-19 20:57:38 DEBUG: [1215c199: 5055 < 192.168.0.1] HEX: 474554202f3f69643d37352674696d657374616d703d323031382d30392d323025323030333a35373a3335266c61743d33372e373937393436266c6f6e3d2d3132322e3434303936342673706565643d312662656172696e673d31393426616c7469747564653d3026626174743d31303026646576636f64653d363134373220485454502f312e310d0a4163636570743a20746578742f68746d6c2c6170706c69636174696f6e2f7868746d6c2b786d6c2c6170706c69636174696f6e2f786d6c3b713d302e392c2a2f2a3b713d302e380d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a557365722d4167656e743a204d6f7a696c6c612f352e30202857696e646f7773204e5420362e333b20574f5736343b2072763a34392e3029204765636b6f2f32303130303130312046697265666f782f34392e300d0a4163636570742d4c616e67756167653a20656e2d75732c656e3b713d302e350d0a4163636570742d456e636f64696e673a20677a69700d0a486f73743a20736970322e7461626c65746d656469612e636f6d3a353035350d0a0d0a
2018-09-19 20:57:38 DEBUG: [1215c199: 5055 > 192.168.0.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2018-09-19 20:57:38  INFO: [1215c199] disconnected

BTW: the problem seems to be related to the geocoder: if I disable it the data is recognized ok. Oddly enough the geocoder works fine when the iOS client sends data.