Sometimes the connection sessions are getting mapped to wrong devices in v5.12, seems like.
Here is the relevant log:
2024-02-21 07:46:14 INFO: [T127cc1b8: teltonika < 54.169.57.95] 000000000000004e08010000018dc972f5f80034171a430d4f658e002900e10f0000001007ef00f0015005150445010100b30007b5000ab60006420000180000430f2144000009008302c7000000001002b50dde000100007f58
2024-02-21 07:46:14 INFO: [T127cc1b8] id: 867440060759420, time: 2024-02-21 07:46:11, lat: 22.33072, lon: 87.39293, course: 225.0
The connection session T127cc1b8 was indeed created for a Teltonika device. However, this particular location data was assigned to a Concox device for some bug in the between session-to-device mapping part. The actual Teltonika device and the wrong Concox device were running on two very different locations. As a result, the Concox device showed a jump in its trip report.
Not sure if this is an issue with gt06 protocol decoder, teltonika protocol decoder or any generic part of the traccar server.
Sometimes the connection sessions are getting mapped to wrong devices in v5.12, seems like.
Here is the relevant log:
The connection session T127cc1b8 was indeed created for a Teltonika device. However, this particular location data was assigned to a Concox device for some bug in the between session-to-device mapping part. The actual Teltonika device and the wrong Concox device were running on two very different locations. As a result, the Concox device showed a jump in its trip report.
Not sure if this is an issue with gt06 protocol decoder, teltonika protocol decoder or any generic part of the traccar server.