Time Different in Report Route and Disabling Record

Martin Küchler6 years ago

First Question: I am using Crome as Browser. The time in the Report has one hour different to the effictive time, although I have set the time Zone in the Server and on the user and on the device as well. As clinet I am using the Android App. What did I do wrong?
Secound Question: Is it possibble to set a data record invalid i a route Report, if the postion data are inaccurate?

Thanks for your answer in advance.
Regards Martin

Anton Tananaev6 years ago

Have you checked logs?

Martin Küchler6 years ago

I have a lot of such entries in the log:

2018-05-24 11:42:44 DEBUG: [52723C58: 5055 < 178.197.225.252] HEX: 504f5354202f3f69643d303739373037363131322674696d657374616d703d31353237313531333731266c61743d34372e3135343930363636363636363636266c6f6e3d382e3331363736352673706565643d322e373735343937303437353132353331332662656172696e673d31332e38323939393939323337303630353526616c7469747564653d3532322e342661636375726163793d302e3026626174743d39332e3020485454502f312e310d0a436f6e74656e742d547970653a206170706c69636174696f6e2f782d7777772d666f726d2d75726c656e636f6465640d0a557365722d4167656e743a2044616c76696b2f322e312e3020284c696e75783b20553b20416e64726f696420372e303b20533431204275696c642f4e524439304d290d0a486f73743a20617273352e63683a353035350d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2018-05-24 11:42:44 DEBUG: [52723C58: 5055 > 178.197.225.252] HEX: 485454502f312e3120323030204f4b0d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2018-05-24 11:42:44  INFO: [52723C58] id: 0797076112, time: 2018-05-24 10:42:51, lat: 47.15491, lon: 8.31677, speed: 2.8, course: 13.8
2018-05-24 11:42:46 DEBUG: [52723C58: 5055 < 178.197.225.252] HEX: 504f5354202f3f69643d303739373037363131322674696d657374616d703d31353237313531333733266c61743d34372e313534393235303030303030303036266c6f6e3d382e3331363738353030303030303030312673706565643d322e343639333332303631323033393536372662656172696e673d36312e363539393939383437343132313126616c7469747564653d3532332e392661636375726163793d302e3026626174743d39332e3020485454502f312e310d0a436f6e74656e742d547970653a206170706c69636174696f6e2f782d7777772d666f726d2d75726c656e636f6465640d0a557365722d4167656e743a2044616c76696b2f322e312e3020284c696e75783b20553b20416e64726f696420372e303b20533431204275696c642f4e524439304d290d0a486f73743a20617273352e63683a353035350d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2018-05-24 11:42:46 DEBUG: [52723C58: 5055 > 178.197.225.252] HEX: 485454502f312e3120323030204f4b0d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2018-05-24 11:42:46  WARN: Geocoding failed - Empty address - GeocoderException (JsonGeocoder:69 < *:34 < *:96 < ...)
2018-05-24 11:42:46  INFO: [52723C58] id: 0797076112, time: 2018-05-24 10:42:53, lat: 47.15493, lon: 8.31679, speed: 2.5, course: 61.7
2018-05-24 11:42:46  WARN: Empty address
Veerendra6 years ago

@martink If I am not wrong It looks server time and reported time by device have one hour difference. It seems that server time is not following UTC time.