GUI Coordinates differs from log
How can that be. The GUI takes the record from the DB
I recommend you to look at the date and time in the GUI. Because it's in future it doesn't get overridden with your other data.
Now, in database servertime, devicetime and fixtime are the same
116465 castel 72 2018-01-10 18:52:20 2018-01-10 18:52:15 2018-01-10 18:52:15 0 4.733066666666667 -74.04367 0 0 0 {"sat":0,"status":0,"battery":255,"odometer":0,"distance":9454266.46,"totalDistance":1.890916799E7,"motion":false} 0 {"radioType":"gsm","considerIp":false,"cellTowers":[{"cellId":30126,"locationAreaCode":12290,"mobileCountryCode":0,"mobileNetworkCode":0}]}
116466 castel 72 2018-01-10 18:53:02 2018-01-10 18:52:15 2018-01-10 18:52:15 0 4.733066666666667 -74.04367 0 0 0 {"sat":0,"status":0,"battery":255,"odometer":0,"distance":9454266.46,"totalDistance":1.890916799E7,"motion":false} 0 {"radioType":"gsm","considerIp":false,"cellTowers":[{"cellId":30126,"locationAreaCode":12290,"mobileCountryCode":0,"mobileNetworkCode":0}]}
116467 castel 72 2018-01-10 18:53:24 2018-01-10 18:53:16 2018-01-10 18:53:16 0 4.733066666666667 -74.04367 0 0 0 {"sat":0,"status":0,"battery":255,"odometer":0,"distance":9454266.46,"totalDistance":1.890916799E7,"motion":false} 0 {"radioType":"gsm","considerIp":false,"cellTowers":[{"cellId":30126,"locationAreaCode":12290,"mobileCountryCode":0,"mobileNetworkCode":0}]}But why in database is this future date if in logs is correct
2018-01-10 17:17:46 INFO: [91E0EB08] id: 611150007810, time: 2018-01-10 17:17:42, lat: 4.73307, lon: -74.04367, speed: 0.0, course: 0.0
2018-01-10 17:18:48 INFO: [91E0EB08] id: 611150007810, time: 2018-01-10 17:18:43, lat: 4.73307, lon: -74.04367, speed: 0.0, course: 0.0So I think there is nothing to do on the device becouse i assume that if logs are ok, device is reporting ok. But how can avoid this? is there anything wrong with this protocol?
I have several devices (same model) with same behaviour.
If I delete the device with GUI and add it again with different name, they work fine buy anytime they start to fail as reported.
Any hint to avoid this? because with this behaviour thiese devidec are not trustie and I will be forced to discard them.
Thanks in advance for your support
I think you misunderstood the issue. Sometime in the past your device reported invalid data with time in the future. Now Traccar considers it to be the latest by time, so it doesn't update it in the GUI.
Ok, I think I understand now, so if I delete the "future records" in positions table problem should be solved?
You would also need to fix the reference from devices table.
I have no idea how to work with databases so my fix was to delete and re-add the device when I had this same issue.
Then I found the config to stop future time stamps and this fixed the problem for ever.
https://www.traccar.org/configuration-file/
<entry key='filter.enable'>true</entry>
<entry key='filter.zero'>true</entry>
<entry key='filter.duplicate'>true</entry>
<entry key='filter.maxSpeed'>2500</entry>
<entry key='filter.future'>86400</entry>Thank you all!
Hello,
At first, I thought that a device was misinforming the location but after checking the logs I found that the location on logs was ok but in GUI is different.
This are the log records:
and in the GUI Latitud: -0.000004 Longitud: 10.868053 Speed: 1081.6 KM date: 2048-12-08 06:50:07 (even date is wrong)
The device is a Sinocastel PT-690 configured on port 5086.
Any clue of what can be happening?