Abnormal situation of geographic position reported by the server

I am concerned about the very strange situation of some devices within the server.

Several days ago a Chinese device, with H02 protocol, on the platform maintained a fixed geographical position for several days, everything was in order, device online, the correct time, and it is reported to the server every 30 seconds, with a valid position, however the GPS device was NOT geographically located in the position that traccar reports, at that time, I restarted the GPS device, reconfigured with the appropriate data, with the same result in the traccar platform. I checked in the registry what information was received from that device and I see that it receives the coordinates reported by the server, so I assumed that the device was damaged, it was replaced and everything was ok. However, this damaged GPS device, I added it again as a new device on the platform with the surprise that now it reports the correct geographic position, very strange.

Now I have another device, this time an OBDii coban GPS103 protocol, which has the same situation, it is online, reports every 30 seconds with a valid position, and is in the same geographical position for several days, I have the device in my hands, and it is at a distance of approximately 20 km from the position reported on the traccar platform, the strangest thing is that when I ask the device for its position by SMS, it reports its CORRECT position by SMS, which I repeat differs by more than 20 km due to the reported for traccar.

Obviously there is a problem that causes great confusion with the position reported by the system and the position reported by the GPS device itself.

I wanted to know if anyone has any ideas so I can review and find the problem, before I just delete the device and add it back in the traccar platform

Have you checked the logs? Have you checked the timestamps? The location won't update if your device is reporting time older than the "latest" position.

the last valid records from table tc_positions the servertime its ok, devicetime its ok, fixedtime its FIXED untill now with coordinates FIXED too. Hay have the query if you need

You have to compare those records, not just look at the last one.

actually reviewing the tc_positions table, I found several inconsistencies with the device time, however at present it was reporting the correct time, I have deleted from the tc_positions table all the records of the device before it remains in the same position until now. And it keeps showing the same wrong position on the platform

If you still need some help, please start providing evidence and details of the investigation, with screenshots.

Meaby you have filters enabled?

If you state that the device location in traccar is 20 km from the real postion reported by your device then check in the traccar log if the position is actually reported as valid (im not sure if your protocol states if the position is valid or not. I only use watch protocol). If the device reports the position as not valid then it might be an Lbs geo location which would explain the 20 km difference.. ?

Most logic is to show details, logs etc..

It is important to highlight:

• the device has been working correctly for several years
• I am using version 5.6
• It is the 3rd time that this has happened to me with different devices, with different protocols, and with different versions of traccar

(I am writing in two parts because when I try to reply in the forum I get a "Forbidden" message)

Here are screenshots of a backup of the database (remember that I deleted several wrong positions from the tc_positions table)

start the problem

Inconsistency of the time reported by the GPS Device

After deleting from the tc_positions table several days before the failure

now in the present

What is recorded in the log file, (the server has time zone UTC-4):

2023-02-24 21:44:28  INFO: [Tb277fdd4: gps103 < 181.114.123.99] 696d65693a3836343138303033363031333335322c747261636b65722c3233303232353031343430362c2c462c3031343430322e3030302c412c313732322e303531332c532c30363630392e363336382c572c302e30302c302c2c302c2c302e3030252c2c3b
2023-02-24 21:44:28  INFO: [Tb277fdd4] id: 864180036013352, time: 2023-02-24 21:44:02, lat: -17.66230, lon: -66.99789, course: 0.0

And what the GPS device reports by SMS:

lat:-17.367522 lon:-66.160613
speed:0.00
T:23/02/25 01:44
bat:100%
Pwr: ON ACC: OFF

Seeing what is recorded in the log file, it is easy to think that the GPS device is damaged and reporting an invalid position, however I have configured the GPS device to report to the server: demo2.traccar.org and there the correct geographical position is reflected

Now I'm more worried

What do you have in the config files? Have you changed anything comparing to the defaults?

this is the partial content of traccar.xml

<entry key='filter.enable'>true</entry>
<!--
    <entry key='filter.zero'>true</entry>
    <entry key='filter.static'>true</entry>
    <entry key='filter.distance'>100</entry>
-->

    <entry key='filter.duplicate'>true</entry>
    <entry key='filter.maxSpeed'>25000</entry>
    <entry key='filter.invalid'>true</entry>
    <entry key='filter.accuracy'>50</entry>
    <entry key='filter.minPeriod'>20</entry>
    <entry key='filter.skipLimit'>180</entry>
    <entry key='filter.skipAttributes.enable'>true</entry>
    <entry key='filter.skipAttributes'>alarm,ignition,result,status</entry>

    <entry key='processing.computedAttributes.deviceAttributes'>true</entry>
    <entry key='processing.copyAttributes.enable'>true</entry>
    <entry key='processing.copyAttributes'>alarm</entry>

    <entry key='h02.timeout'>700</entry>
    <entry key='tcp.timeout'>40</entry>

    <entry key='status.ignoreOffline'>h02</entry>
    <entry key='status.timeout'>600</entry>

    <entry key='coordinates.filter'>true</entry>
    <entry key='coordinates.minError'>100</entry>
    <entry key='coordinates.maxError'>30000</entry>

    <entry key='event.overspeed.notRepeat'>true</entry>
    <entry key='event.overspeed.minimalDuration'>10</entry>
    <entry key='event.motion.processInvalidPositions'>false</entry>
    <entry key='event.motion.speedThreshold'>1</entry>

Filter zero, static and distance was disabled after the problem.
The file ReportMailer.java was modified only the mail content in v5.6, ReportResource.java file in previous version.
The default.xml file no touched.

More information

same device reconfigured back to server

the log file

2023-02-25 08:00:24  INFO: [T088266b1] connected
2023-02-25 08:00:24  INFO: [T088266b1: gps103 < 181.114.124.198] 23232c696d65693a3836343138303033363031333335322c413b
2023-02-25 08:00:24  INFO: [T088266b1: gps103 > 181.114.124.198] 4c4f4144
2023-02-25 08:01:06  INFO: [T088266b1: gps103 < 181.114.124.198] 696d65693a3836343138303033363031333335322c747261636b65722c2c2c4c2c2c2c366234352c2c333733662c2c2c2c2c302c2c302e3030252c2c3b
2023-02-25 08:01:06  INFO: [T088266b1] id: 864180036013352, time: 2023-02-24 22:56:05, lat: -17.66230, lon: -66.99789, course: 0.0
2023-02-25 08:01:07  INFO: [T088266b1: gps103 < 181.114.124.198] 696d65693a3836343138303033363031333335322c4f42442c2c2c302e30302c2c302c302c30252c302c30252c302c302e30302c2c2c2c3b
2023-02-25 08:01:17  INFO: [T088266b1: gps103 < 181.114.124.198] 696d65693a3836343138303033363031333335322c73656e736f7220616c61726d2c2c2c4c2c2c2c366234352c2c333733662c2c2c2c2c302c2c302e3030252c2c3b
2023-02-25 08:01:17  INFO: [T088266b1] id: 864180036013352, time: 2023-02-24 22:56:05, lat: -17.66230, lon: -66.99789, course: 0.0
2023-02-25 08:01:24  INFO: [T088266b1: gps103 < 181.114.124.198] 3836343138303033363031333335323b
2023-02-25 08:01:24  INFO: [T088266b1: gps103 > 181.114.124.198] 4f4e
2023-02-25 08:02:07  INFO: [T088266b1: gps103 < 181.114.124.198] 696d65693a3836343138303033363031333335322c747261636b65722c2c2c462c3132303230342e3030302c412c313732312e333335312c532c30363630392e343732322c572c32312e34312c362e38342c2c302c2c302e3030252c2c3b
2023-02-25 08:02:07  INFO: [T088266b1] id: 864180036013352, time: 1999-11-29 08:02:04, lat: -17.66230, lon: -66.99789, speed: 21.4, course: 6.8
2023-02-25 08:02:08  INFO: [T088266b1: gps103 < 181.114.124.198] 696d65693a3836343138303033363031333335322c4f42442c3233303232353132303230352c2c302e30302c2c302c302c30252c302c30252c302c302e30302c2c2c2c3b
2023-02-25 08:02:08  INFO: [T088266b1] id: 864180036013352, time: 2023-02-24 22:56:05, lat: -17.66230, lon: -66.99789, course: 0.0

The coordinates.filter is probably messing with your location. Try without it.

that is it! set to false, restart service and show the right position. Have to read more about coordinates.filter.
Thanks to help solve this headache