GPS rollover fix for Traccar 6.9 fixed your problem?
The rollover fix is only the GPS week rollover issue. It does not fix any issue with coordinates or invalid location.
I know that and I said that: "The Traccar fix only changes the way Traccar interprets the date it receives"
Yes, I'm just confirming that. People definitely have some other issues with some devices.
I solved the date issue by ignoring the device date and using the server date.
By adding that setting to traccar.xml
For example, the gt06n from concox and some others in h02 now remain FIXED in the location, only when resetting them to factory settings do they update and only send a new communication on the first ping, by SMS if they are correct with time and date, obviously we know it is the fault of the equipment, I am seeing if I can isolate and see what arrives directly from the log.
is 6.9 just fix gps rolllover ini august 17?
or include all gps rollover before that?
like in 1999 and 2019 ?
thanks
It's a generic fix for all rollovers.
Out of curiosity, if the rollover took place in 2019 why only now it affected some devices?
It just depends on what date they had hardcoded in the hardware.
2025-08-29 13:52:38 INFO: [Tac3dbb40: h02 > 223.123.111.91] *HQ,9172180661,V4,V1,20250829135238#
2025-08-29 13:52:38 INFO: [Tac3dbb40: h02 > 223.123.111.91] *HQ,9172180661,V4,V1,20250829135238#
2025-08-29 13:52:38 INFO: [Tac3dbb40: h02 > 223.123.111.91] *HQ,9172180661,V4,V1,20250829135238#
2025-08-29 13:52:38 INFO: [Tac3dbb40: h02 > 223.123.111.91] *HQ,9172180661,V4,V1,20250829135238#
2025-08-29 13:52:38 INFO: [Tac3dbb40: h02 > 223.123.111.91] *HQ,9172180661,V4,V1,20250829135238#
2025-08-29 13:52:38 INFO: [Tac3dbb40: h02 > 223.123.111.91] *HQ,9172180661,V4,V1,20250829135238#
2025-08-29 13:52:38 INFO: [Tac3dbb40: h02 > 223.123.111.91] *HQ,9172180661,V4,V1,20250829135238#
2025-08-29 13:52:38 INFO: [Tac3dbb40: h02 > 223.123.111.91] *HQ,9172180661,V4,V1,20250829135238#
2025-08-29 13:52:38 INFO: [Tac3dbb40: h02 > 223.123.111.91] *HQ,9172180661,V4,V1,20250829135238#
2025-08-29 13:52:38 INFO: Event: deviceOffline, Device: 9172180661, Time: 2025-08-29 13:52:38, Notifications: 0
2025-08-29 13:52:38 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:55:22, lat: 25.42525, lon: 68.34140, course: 151.0
2025-08-29 13:52:38 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:12:21, lat: 25.23066, lon: 68.23464, speed: 9.1, course: 1.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:12:22, lat: 25.23070, lon: 68.23464, speed: 5.2, course: 18.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:12:31, lat: 25.23077, lon: 68.23467, speed: 8.3, course: 315.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:12:32, lat: 25.23080, lon: 68.23462, speed: 10.5, course: 312.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:12:35, lat: 25.23081, lon: 68.23459, speed: 4.5, course: 284.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:55:42, lat: 25.42526, lon: 68.34142, course: 225.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:12:36, lat: 25.23081, lon: 68.23459, speed: 5.8, course: 217.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:12:37, lat: 25.23081, lon: 68.23459, course: 192.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:55:50, lat: 25.42526, lon: 68.34142, course: 192.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:55:51, lat: 25.42524, lon: 68.34141, course: 187.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:55:53, lat: 25.42523, lon: 68.34141, course: 202.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:55:58, lat: 25.42522, lon: 68.34138, course: 317.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:56:02, lat: 24.74797, lon: 67.89574, course: 0.0
2025-08-29 13:52:39 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:12:38, lat: 25.23067, lon: 68.23459, course: 192.0
2025-08-29 13:52:40 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:12:40, lat: 25.23067, lon: 68.23460, course: 192.0
2025-08-29 13:52:40 INFO: [Tac3dbb40] id: 9172180661, time: 2021-01-01 02:12:42, lat: 25.23067, lon: 68.23460, speed: 5.2, course: 323.0
2025-08-29 13:52:52 INFO: [T2d167ff7: h02 < 223.123.111.91] *HQ,9172180661,V1,025721,A,2525.9104,N,06820.2280,E,027.63,329,010121,FFFF9FFF,410,04,2111,23992,5,9,136#*HQ,9172180661,V1,025722,A,2525.9172,N,06820.2247,E,027.83,342,010121,FFFF9FFF,410,04,2111,23992,5,9,138#*HQ,9172180661,V1,025724,A,2525.9172,N,06820.2247,E,029.44,330,010121,FFFF9FFF,410,04,2111,23992,5,9,136#
2025-08-29 13:52:52 INFO: [T2d167ff7: h02 > 223.123.111.91] *HQ,9172180661,V4,V1,20250829135252#
2025-08-29 13:52:52 INFO: Event: deviceOnline, Device: 9172180661, Time: 2025-08-29 13:52:52, Notifications: 0
2025-08-29 13:52:52 INFO: [T2d167ff7: h02 > 223.123.111.91] *HQ,9172180661,V4,V1,20250829135252#
2025-08-29 13:52:52 INFO: [T2d167ff7: h02 > 223.123.111.91] *HQ,9172180661,V4,V1,20250829135252#
2025-08-29 13:52:52 INFO: [T2d167ff7] id: 9172180661, time: 2021-01-01 02:57:21, lat: 25.43184, lon: 68.33713, speed: 27.6, course: 329.0
2025-08-29 13:52:52 INFO: [T2d167ff7] id: 9172180661, time: 2021-01-01 02:57:22, lat: 25.43195, lon: 68.33708, speed: 27.8, course: 342.0
2025-08-29 13:52:52 INFO: [T2d167ff7] id: 9172180661, time: 2021-01-01 02:57:24, lat: 25.43195, lon: 68.33708, speed: 29.4, course: 330.0
Time issue in 6.9.1. Any solution
This doesn't look like the same problem to me.
So what do you think, how can I fix this?
You could override the time. That's the only thing you can do on the server.
But for that I need to select a protocol. In 6.7.1, is it possible to override for a single device? When I select a protocol, the override affects reports, shows wrong locations, and disturbs the device positions sequence.
The Traccar fix only changes the way Traccar interprets the date it receives. The satellite keep sending 2006 year and the devices keep receiving it.
In the threads here I've seen reports that even with the fix, the device is sending invalid coordinates. I've seen statements from manufacturers saying erratic behavior after the rollover.
Did any of you were able to solve the issue by updating Traccar to 6.9?
Could you please share manufacturer, device model and current status of situation?