Time setting tk103b

Adam7 years ago

I have a problem with time on the tk103b device.
I've set the UTC +2 time zone
SMS gives good time.
However, the difference is in time at traccar.

How to solve the problem?

https://ibb.co/bsKa5S

2018-04-01 10:22:22  INFO: [C1C830A9] id: 865205031866501, time: 2018-04-01 12:22:21, lat: 50.03936, lon: 18.67932, speed: 0.0, course: 0.0
2018-04-01 10:22:31 DEBUG: [C1C830A9: 5013 < 94.254.131.236] HEX: 2a48512c3836353230353033313836363530312c56312c3130323233312c412c353030322e33363137392c4e2c30313834302e37353930322c452c302e30302c302c3031303431382c4546453746424646230d0a
2018-04-01 10:22:31  INFO: Position filtered by Distance filters from device: 865205031866501 with id: 2
URLEY REY7 years ago

Debes revisar la configuración del horario de tu servidor traccar siempre usa la hora de este. Ajustala con el mismo horario del gps.

Saludos...

Adam7 years ago

I do not understand your hints.

Ubuntu server time is good.

vps518626:~$ date
Sun  1 Apr 22:32:47 CEST 2018
Anton Tananaev7 years ago

Traccar expects UTC time from devices, not local time.

URLEY REY7 years ago

Para resolver el error debes dejar la hora del servidor local y el gps con el mismo formato gmt +2

Adam7 years ago

@Anton

I have a faulty device?

As I have a UTC 0 time in traccar I have a good one. However, the hour in sms is bad.

Can I make a filter at traccar?

Example UTC 0

Database:
serwertime:11:41 (Good time)
devicetime: 11:41 (Good time)
fixtime:11:41 (Good time)

SMS device
Time: 9:41 (Bad time)
Date: 18:04:02

Example UTC +2

serwertime: 13:41 (Bad time)
devicetime: 13:41 (Bad time)
fixtime: 13:41 (Bad time)

SMS device
Time: 11:41 (Good time)
Date: 18:04:02

Anton Tananaev7 years ago

Unless your device supports reporting UTC to the server and local over SMS, you won't be able to do anything about it.