Incorrect datetime value

MI8 years ago

Hi Anton,
I have a problem with one of my devices. Can you tell me whats wrong ???
Best regards
Michael

2016-12-15 14:13:34 DEBUG: [3321AB3B: 5013 < 80.75.32.5] HEX: 2a48512c313630303036383831322c4e42522c3134313333342c3236322c30322c3235352c362c3433312c31373030332c32362c3433312c31313130312c31332c3433312c363335332c31332c3433312c32323137322c31332c3433312c31313039332c31332c3433312c36303836312c31302c3135313231362c464646464642464623
2016-12-15 14:13:34  WARN: Data truncation: Incorrect datetime value: '1970-01-01 00:00:00' for column 'fixtime' at row 1 - MysqlDataTruncation (... < QueryBuilder:443 < DataManager:293 < DefaultDataHandler:27 < ...)
2016-12-15 14:13:34  INFO: [3321AB3B] id: 1600068812, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
2016-12-15 14:13:34 DEBUG: [3321AB3B: 5013 < 80.75.32.5] HEX: 2a48512c313630303036383831322c4e42522c3134313333342c3236322c30322c3235352c362c3433312c31373030332c32362c3433312c31313130312c31332c3433312c363335332c31332c3433312c32323137322c31332c3433312c31313039332c31332c3433312c36303836312c31302c3135313231362c464646464642464623
2016-12-15 14:13:34  WARN: Data truncation: Incorrect datetime value: '1970-01-01 00:00:00' for column 'fixtime' at row 1 - MysqlDataTruncation (... < QueryBuilder:443 < DataManager:293 < DefaultDataHandler:27 < ...)
2016-12-15 14:13:34  INFO: [3321AB3B] id: 1600068812, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
2016-12-15 14:13:34 DEBUG: [3321AB3B: 5013 < 80.75.32.5] HEX: 2a48512c313630303036383831322c4e42522c3134313333352c3236322c30322c3235352c362c3433312c31373030332c32362c3433312c31313130312c31332c3433312c363335332c31332c3433312c32323137322c31332c3433312c31313039332c31332c3433312c36303836312c31302c3135313231362c464646464642464623
2016-12-15 14:13:34  WARN: Data truncation: Incorrect datetime value: '1970-01-01 00:00:00' for column 'fixtime' at row 1 - MysqlDataTruncation (... < QueryBuilder:443 < DataManager:293 < DefaultDataHandler:27 < ...)
2016-12-15 14:13:34  INFO: [3321AB3B] id: 1600068812, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
Anton Tananaev8 years ago

Your device doesn't send GPS info and time, so Traccar takes it from the last known message. If last doesn't exist, Traccar takes zero values for everything. Zero time is "1970-01-01 00:00:00":

https://en.wikipedia.org/wiki/Unix_time#Encoding_time_as_a_number

MI8 years ago

Hi Anton,
thnx for u soon reply.
Thought u have added support for LBS locations:

https://github.com/tananaev/traccar/commit/ef7247060c22c060744580f825391673773703c5

Can u confirm that version 3.9 has included LBS for H02 devices??
Best regards
Michael

Anton Tananaev8 years ago

Yes, it does support LBS data for H02, but have you enabled it in the config?

MI8 years ago

hmmmm, did u mean config of traccar?
no, if needed, what I have do do ???

Device config
no, its seems LBS is allways enabled

Michael

Anton Tananaev8 years ago

In the server config. You have to configure "location.*" parameters:

https://www.traccar.org/configuration-file/

MI8 years ago

I am really sorry for asking again....

I have two config files:

  1. traccar.xml, only some lines about database
  2. default.xml
    Here i put
    "<!-- SERVER CONFIG -->
    <entry key='location.enable'>true</entry>"

Is that correct ???
Greetings
Michael

Anton Tananaev8 years ago

First of all, you are not supposed to change default config. You should change traccar.xml. Secondly, did you notice that I said "parameters" in plural? You have to specify at least "location.enable" and "location.type". Please read the documentation.