Version 4.15 - strange behaviour on gt06 protocol devices

Anton Tananaev2 years ago

If you want to investigate it, I would start with the raw data your device is reporting. Check the time there first.

Matthias Hübner2 years ago

Hello Anton,

I Isolated the communication of the device at the shown time, see marked log: https://drive.google.com/file/d/19eOt6Pq_fIM1YoQgJIe3Zg0k_sJmPKg5/view?usp=sharing

2022-03-28 16:43:31  INFO: [654e28d2: gt06 < 195.226.154.84] HEX: 78781f1216031c0e2b1dc90533bd8d00f1427a4115540106021c2c0001e100c1530c0d0a
2022-03-28 16:43:31  INFO: [654e28d2: gt06 > 195.226.154.84] HEX: 7878051200c175210d0a
2022-03-28 16:43:31  INFO: [654e28d2] id: 352887077243420, time: 2022-03-28 14:43:29, lat: 48.48719, lon: 8.78400, speed: 35.1, course: 340.0

>>
2022-03-28 16:43:47  INFO: [654e28d2: gt06 < 195.226.154.84] HEX: 78780a13440504000000c2f0860d0a
2022-03-28 16:43:47  INFO: [654e28d2: gt06 > 195.226.154.84] HEX: 7878051300c21d660d0a
2022-03-28 16:43:47  INFO: [654e28d2] id: 352887077243420, time: 2022-03-28 14:43:29, lat: 48.48719, lon: 8.78400, speed: 35.1, course: 340.0
<<

2022-03-28 16:43:52  INFO: [654e28d2: gt06 < 195.226.154.84] HEX: 78781f1216031c0e2b31c90533d1ef00f135453815480106021c2c0001e300c34ae50d0a
2022-03-28 16:43:52  INFO: [654e28d2: gt06 > 195.226.154.84] HEX: 7878051200c356330d0a
2022-03-28 16:43:52  INFO: [654e28d2] id: 352887077243420, time: 2022-03-28 14:43:49, lat: 48.49009, lon: 8.78212, speed: 30.2, course: 328.0

How to interpret?

Anton Tananaev2 years ago

Check the protocol documentation for the interpretation.

Matthias Hübner2 years ago

And I only see servertime = UTC+2 and devicetime = UTC. So where do the database entries devicetime = servertime come from?

Anton Tananaev2 years ago

Seems like you're ignoring my suggestions.

Matthias Hübner2 years ago

No, I just waited for your confirmation that status record does not have devicetime but servertime instead. Obviously, a devicetime is not transmitted as logged.

Grupo Datasoft Ltda.3 months ago

Hello Anton, looking at this post, I see that I have similar problems and I'm probably doing things wrong, I hope you can tell me what I should do:

  1. I configure my gt06 devices to report in local time GMT-5 (Colombia), is this wrong?

  2. I added in the traccar configuration this:

<entry key='time.override'>serverTime</entry>
<entry key='time.protocols'>gt06</entry>

Apparently it works but I lose the actual time the location was reported which is replaced by the server time.

Please tell me what I am doing wrong and how it should be correct in both the device time zone settings and the Traccar server settings. Thank you very much Anton

Anton Tananaev3 months ago

You should resolve the timezone problem instead of overriding the time with the server time.

Matthias Hübner2 months ago

Hello Grupo Datasoft,

I fixed this with the following steps:

  • no time zone setting on the GT06 device. Device reports UTC!
  • no time.override in server config.
    Via Server Management:
  • on Server: local timezone, here EUROPE/Paris
  • on Devices: no attribute entry for timezone.
  • on users: local timezone, here EUROPE/Paris.
  • on groups: no attribute entry for timezone.

HTH