problem with the time zone with the gt06 protocol in gps concox vl03

Kind regards, I write to request support regarding gt06 devices, I know there were several threads about it but the solutions but they are from years ago, someone may correct me if I do something wrong.

in the FIXTIME reports of the gps devices it sends me a time totally superior to the time of the server and the configured time zone but in the text messages I configure and the time zone is correct, only on the platform, looking for solutions I found a lot of threads where they recommended Adjust the following scripts but none managed to solve the problem and the position reports of these gt06 protocol gps the time difference is abysmal. I will append the lines that I had used and added in the traccar.xml

<!– Configuration the protocol GT06 –>
<string key='gt06.enable'>true</string>
<string key='gt06.port'>5023</string>
<string key='gt06.timezone'>-18000< /string>

time zone is -5 in seconds is -18000

I am attentive to any suggestion I have reviewed many threads on the subject but I can not give a solution, totally grateful if a colleague corrects me.

After placing the script in traccar.xml, I restart the server and even clear the cache, but I did not mention it in case they ask.

Can you share:

1. Log fragment for a connection session for one device, starting from "connected" message.
2. Server timezone configuration (time in logs).
3. Device timezone configuration.

To go deeper into the subject, doing a live monitoring, I see that the time is wrong only when the engine is on, while the engine is off, it sends the time ok (GMT-5) but once the engine is turned on and starts to walk, the log shows an incorrect time (5 hours ahead), look at the log: (the correct current hour is 2022-10-26 04:04:19

    Linea 28297: 2022-10-25 16:06:22  INFO: [T06709d97] id: 862476051294139, time: 2022-10-26 04:04:19, lat: 6.17029, lon: -75.43596, speed: 32.4, course: 347.0
    Linea 28986: 2022-10-25 16:06:24  INFO: [T06709d97] id: 862476051294139, time: 2022-10-25 21:06:09, lat: 6.18006, lon: -75.43496, speed: 13.5, course: 14.0
    Linea 28988: 2022-10-25 16:06:24  INFO: [T06709d97] id: 862476051294139, time: 2022-10-25 21:06:19, lat: 6.18076, lon: -75.43476, speed: 16.7, course: 16.0
    Linea 30785: 2022-10-25 16:06:30  INFO: [T06709d97] id: 862476051294139, time: 2022-10-25 21:06:29, lat: 6.18155, lon: -75.43455, speed: 18.4, course: 16.0
    Linea 34808: 2022-10-25 16:06:41  INFO: [T06709d97] id: 862476051294139, time: 2022-10-25 21:06:39, lat: 6.18244, lon: -75.43430, speed: 22.1, course: 16.0
    Linea 36960: 2022-10-25 16:06:50  INFO: [T06709d97] id: 862476051294139, time: 2022-10-25 21:06:49, lat: 6.18345, lon: -75.43402, speed: 22.1, course: 16.0
    Linea 38992: 2022-10-25 16:07:01  INFO: [T06709d97] id: 862476051294139, time: 2022-10-25 21:06:59, lat: 6.18452, lon: -75.43372, speed: 25.4, course: 14.0
    Linea 41497: 2022-10-25 16:07:11  INFO: [T06709d97] id: 862476051294139, time: 2022-10-25 21:07:09, lat: 6.18569, lon: -75.43356, speed: 26.5, course: 359.0
    Linea 52968: 2022-10-25 16:07:59  INFO: [T1ce82b13: gt06 < 190.130.109.159] 78781101086247605129413980391f49000251ac0d0a
    Linea 53697: 2022-10-25 16:08:01  INFO: [T1ce82b13] id: 862476051294139, time: 2022-10-26 04:04:19, lat: 6.17029, lon: -75.43596, speed: 32.4, course: 347.0
    Linea 54353: 2022-10-25 16:08:03  INFO: [T1ce82b13: gt06 < 190.130.109.159] 79790020940a086247605129413907321016413964538957101602307214430400049b090d0a
    Linea 54355: 2022-10-25 16:08:03  INFO: [T1ce82b13] id: 862476051294139, time: 2022-10-26 04:04:19, lat: 6.17029, lon: -75.43596, speed: 32.4, course: 347.0
    Linea 55201: 2022-10-25 16:08:05  INFO: [T1ce82b13] id: 862476051294139, time: 2022-10-25 21:07:41, lat: 6.18964, lon: -75.43369, speed: 26.5, course: 358.0
    Linea 55202: 2022-10-25 16:08:05  INFO: [T1ce82b13] id: 862476051294139, time: 2022-10-25 21:07:51, lat: 6.19084, lon: -75.43372, speed: 27.5, course: 358.0
    Linea 55205: 2022-10-25 16:08:05  INFO: [T1ce82b13] id: 862476051294139, time: 2022-10-25 21:08:01, lat: 6.19229, lon: -75.43380, speed: 34.0, course: 359.0
    Linea 57603: 2022-10-25 16:08:13  INFO: [T1ce82b13] id: 862476051294139, time: 2022-10-25 21:08:11, lat: 6.19389, lon: -75.43380, speed: 31.9, course: 357.0
    Linea 60804: 2022-10-25 16:08:23  INFO: [T1ce82b13] id: 862476051294139, time: 2022-10-25 21:08:21, lat: 6.19533, lon: -75.43406, speed: 31.3, course: 340.0
    Linea 63076: 2022-10-25 16:08:33  INFO: [T1ce82b13] id: 862476051294139, time: 2022-10-25 21:08:31, lat: 6.19674, lon: -75.43459, speed: 32.9, course: 339.0
    Linea 64818: 2022-10-25 16:08:43  INFO: [T1ce82b13] id: 862476051294139, time: 2022-10-25 21:08:41, lat: 6.19819, lon: -75.43513, speed: 32.4, course: 340.0
    Linea 66790: 2022-10-25 16:08:53  INFO: [T1ce82b13] id: 862476051294139, time: 2022-10-25 21:08:51, lat: 6.19960, lon: -75.43564, speed: 31.3, course: 339.0
    Linea 69479: 2022-10-25 16:09:02  INFO: [T1ce82b13] id: 862476051294139, time: 2022-10-25 21:09:01, lat: 6.20100, lon: -75.43616, speed: 32.9, course: 339.0

Are you posting from 2 different accounts?

No, we are just 2 colleagues who are trying to understand the error and find a solution

OK, so you need to either wait or recreate your device.

Excuse me Anton, I did not understand, wait? create the device?

Well, your device reported a position in the future (or you didn't configure timezone correctly originally). Now Traccar will use that as the most recent position and reuse it for all the data that doesn't include location. That's probably why you see it for some messages. So you will have that until the actual time is passes that timestamp in the future. Alternative - recreate device, which would clear all the data.

Thanks Anton, I'll keep exploring... in case the data is of any use: this does not happen in Traccar 4.4, with the update to Traccar 5.0 it started to happen

Hello Anton and Control Taken, good news, I already solved it thanks to a post from 4 years ago in which you gave a solution with the approach of replacing fixtime with servertime:

https://www.traccar.org/forums/topic/can-i-use-servertime-instead-of-fixtime/

This script was the solution:

 <string key='time.override'>serverTime</string>
 <string key='time.protocols'>osmand,gt06</string>

Thank you both for the help! As always Anton, my admiration and respect for the Traccar project

That's the worst solution, but I guess if it works for you...

Anton, I understand that solution that the colleague mentioned when the device is offline and reconnect all the previous positions will arrive with a delay, what is the optimal solution that you suggest to be able to solve satisfactorily without any damage when loading information from positions where there was no signal, Totally grateful for your input.

I already explained the situation above.

That's right... what this solution did was affect, from one moment to another, all the positions (tc_positions) began to report servertime, devicetime and fiztime 7 hours later...