Hello,
Our server handles different GPS devices and sends their location to traccar by emulating OsmAnd. I had to change the protocol to TK103 on port 5002 (also tried Gps103 on port 5001) to handle device on/off and SOS status and receive control messages.
The logs indicate that the data is received but it is not displayed on the UI:
For TK103
2026-03-07 18:12:20 INFO: [T2fd25a0a: tk103 < 192.168.0.175] imei:2020,tracker,260307181218,,F,3747.8744N,12226.4578W,0,36,6;
For Gps103:
2026-03-07 14:49:00 INFO: [T87aad7d4: gps103 < 192.168.0.175] 260307144858BP05000000002020260307A3747.8714N12226.4584W000.03400000000L00000000
Unfortunately the logs don't provide any information besides the one INFO line. I am using:
<entry key='logger.level'>all</entry>
<entry key='filter.enable'>false</entry>
For timestamp I tried using both the original UTC and the local time with no difference.
Do you have any suggestions what else to look for? Should those messages be handled properly by the protocol handles?
Thank you for any help.
Doesn't seem like the format is matching either of the ports.
Hello,
Our server handles different GPS devices and sends their location to traccar by emulating OsmAnd. I had to change the protocol to TK103 on port 5002 (also tried Gps103 on port 5001) to handle device on/off and SOS status and receive control messages.
The logs indicate that the data is received but it is not displayed on the UI:
For TK103
For Gps103:
Unfortunately the logs don't provide any information besides the one INFO line. I am using:
<entry key='logger.level'>all</entry> <entry key='filter.enable'>false</entry>For timestamp I tried using both the original UTC and the local time with no difference.
Do you have any suggestions what else to look for? Should those messages be handled properly by the protocol handles?
Thank you for any help.