Probably you need to configure the timezone on the device or the server.
Appear that does not update your device the time....
My happens to me too but it is a problem of the platform protocol, because with the manufacturer it does not have the fault.
Hi, I am facing same problem.
Fixtime is 5:30 behind in GT06 protocol.
How you solved this problem?
Please send me a photo to see the fault.
Server Time 2024-07-05 00:10:09
Device Time 2024-07-05 00:10:09
Fix Time 2024-07-04 17:35:04
This is the data i cann in the traccar. fix time is always 5:30 behind than actual time. servicetime and devicetime is actual times.
It seems to be a fault of your device that is not updating the time in the last position entrusted, verify that it has an active GPS signal.... Because there what you show you don't see flaws in tracing.
Send them the following SMS command: GMT,E,0,0#. let me know how it goes.
just now i have used
<entry key='time.override'>deviceTime</entry>
<entry key='time.protocols'>gt06</entry>
I think it will remove fixtime out of the game.
After updating this FixTime issue is gone ( I did not tested all the features i.e. notifications etc )
i will test it for 1 more day than i can say something about this.
Overriding time is usually a really bad idea.
Yes it was a bad idea, I have removed time.override code from server configuration.
any more solutions please :)
I have fixed the issue by sending GMT,E,0,0# command to device.
Problem was: Chinese EV02 device showing time +00:00 but in real it was reporting in +5:30 time zone.
Hence by above command device started sending data in +00:00 which solved the problem as server is expecting timeZone in UTC.
I had given you the solution in several comments ago... But that is our excension to resist in order to learn....
Good day
I have a concox GT06 device, and I want to know how to correct the FIX TIME