Servertime in events Record

Salut,

in my implementation the events-record has servertime column which is UTC.

When I do reports, time in position report (route, trip) is devicetime/localtime. Time in events report is in servertime/UTC. so i cannot match in simple way trip/route report with the events report.

Is there a possibility to get the localtime in the events report?
Would be great to add a devicetime in localtime to the events-record in database.

Best regards Matthias

I believe that server returns same timezone for every report.

Salut Anton,

so i am lost. See this reports of my Lodgy:

Report type:;Events;;;;;;
;;;;;;;
Device:;Lodgy;;;;;;
Group:;Fzg Hübner;;;;;;
Period:;2018-11-15 00:00:00 - 2018-11-16 00:00:00;;;;;;
;;;;;;;
Time;Type;Geofence Name;Attributes;;;;
2018-11-15 02:01:12;deviceOnline;;;;;;
2018-11-15 02:15:12;deviceUnknown;;;;;;
2018-11-15 08:49:07;deviceOnline;;;;;;
2018-11-15 08:49:44;geofenceExit;Home;;;;;
2018-11-15 08:50:49;geofenceEnter;rue de la gare;;;;;
2018-11-15 08:58:38;geofenceExit;rue de la gare;;;;;
2018-11-15 09:00:49;geofenceEnter;Home;;;;;
2018-11-15 09:06:10;deviceOffline;;;;;;
2018-11-15 10:01:23;deviceOnline;;;;;;
2018-11-15 10:15:23;deviceUnknown;;;;;;
2018-11-15 14:57:24;deviceOnline;;;;;;
2018-11-15 14:57:46;geofenceExit;Home;;;;;
2018-11-15 14:57:46;alarm;;alarm=powerOn;;;;
2018-11-15 14:58:00;geofenceEnter;Home;;;;;
2018-11-15 14:59:03;alarm;;alarm=powerOff;;;;
2018-11-15 15:05:21;deviceOffline;;;;;;
2018-11-15 18:01:33;deviceOnline;;;;;;
2018-11-15 18:15:33;deviceUnknown;;;;;;
;;;;;;;
;;;;;;;
;;;;;;;
Report type:;Route;;;;;;
;;;;;;;
Device:;Lodgy;;;;;;
Group:;Fzg Hübner;;;;;;
Period:;2018-11-15 00:00:00 - 2018-11-16 00:00:00;;;;;;
;;;;;;;
Valid;Time;Latitude;Longitude;Altitude;Speed;Address;Attributes
WAHR;2018-11-15 11:43:59;48,834553;8,027698;0 m;5.4 km/h;48.834553°, 8.027698°;io1=0  distance=14.57  totalDistance=1.341179555E7  motion=true
WAHR;2018-11-15 11:44:13;48,834000;8,028677;0 m;24.5 km/h;48.834000°, 8.028677°;io1=0  distance=94.52  totalDistance=1.341189007E7  motion=true
WAHR;2018-11-15 11:45:18;48,828973;8,033228;0 m;42.7 km/h;48.828973°, 8.033228°;io1=0  distance=651.43  totalDistance=1.34125415E7  motion=true
WAHR;2018-11-15 11:46:48;48,826413;8,038492;0 m;8.9 km/h;48.826413°, 8.038492°;io1=0  distance=479.58  totalDistance=1.341302108E7  motion=true
WAHR;2018-11-15 11:51:53;48,826405;8,038540;0 m;6.8 km/h;48.826405°, 8.038540°;io1=0  distance=3.66  totalDistance=1.341302474E7  motion=true
WAHR;2018-11-15 11:52:43;48,829277;8,033113;0 m;42.7 km/h;48.829277°, 8.033113°;io1=0  distance=510.24  totalDistance=1.341353498E7  motion=true
WAHR;2018-11-15 11:52:54;48,830155;8,032473;0 m;17.2 km/h;48.830155°, 8.032473°;io1=0  distance=108.44  totalDistance=1.341364342E7  motion=true
WAHR;2018-11-15 11:52:56;48,830143;8,032338;0 m;22.0 km/h;48.830143°, 8.032338°;io1=0  distance=9.98  totalDistance=1.34136534E7  motion=true
WAHR;2018-11-15 11:53:07;48,829717;8,031185;0 m;31.7 km/h;48.829717°, 8.031185°;io1=0  distance=96.95  totalDistance=1.341375035E7  motion=true
WAHR;2018-11-15 11:53:24;48,830360;8,028920;0 m;32.7 km/h;48.830360°, 8.028920°;io1=0  distance=180.77  totalDistance=1.341393112E7  motion=true
WAHR;2018-11-15 11:53:32;48,830208;8,028035;0 m;28.6 km/h;48.830208°, 8.028035°;io1=0  distance=67.02  totalDistance=1.341399814E7  motion=true
WAHR;2018-11-15 11:53:34;48,830310;8,027897;0 m;29.3 km/h;48.830310°, 8.027897°;io1=0  distance=15.19  totalDistance=1.341401333E7  motion=true
WAHR;2018-11-15 11:53:46;48,830592;8,027188;0 m;26.7 km/h;48.830592°, 8.027188°;io1=0  distance=60.64  totalDistance=1.341407397E7  motion=true
WAHR;2018-11-15 11:53:48;48,830637;8,026998;0 m;26.8 km/h;48.830637°, 8.026998°;io1=0  distance=14.8  totalDistance=1.341408877E7  motion=true
WAHR;2018-11-15 11:54:05;48,831237;8,025862;0 m;17.4 km/h;48.831237°, 8.025862°;io1=0  distance=106.77  totalDistance=1.341419554E7  motion=true
WAHR;2018-11-15 11:54:46;48,833558;8,029293;0 m;12.7 km/h;48.833558°, 8.029293°;io1=0  distance=360.6  totalDistance=1.341455614E7  motion=true
WAHR;2018-11-15 11:55:18;48,834753;8,027327;0 m;7.5 km/h;48.834753°, 8.027327°;io1=0  distance=196.12  totalDistance=1.341475226E7  motion=true
WAHR;2018-11-15 17:52:15;48,834145;8,026768;0 m;2.8 km/h;48.834145°, 8.026768°;alarm=powerOn  ignition=true  io1=1  distance=79.12  totalDistance=1.341483138E7  motion=true
WAHR;2018-11-15 17:52:29;48,834367;8,027087;0 m;7.9 km/h;48.834367°, 8.027087°;io1=1  io4=146167  distance=33.96  totalDistance=1.341486534E7  motion=true
WAHR;2018-11-15 17:52:35;48,834208;8,027287;0 m;7.8 km/h;48.834208°, 8.027287°;io1=1  io4=146167  distance=22.92  totalDistance=1.341488826E7  motion=true
WAHR;2018-11-15 17:53:33;48,834417;8,027543;0 m;0.6 km/h;48.834417°, 8.027543°;alarm=powerOff  ignition=false  io1=0  distance=29.86  totalDistance=1.341491812E7  motion=true

Any suggestion?

Best regards
Matthias

I don't really understand what you want me to look for in that output.

Salut Anton,

this is one device. Upper part is events log with its time. Lower part is positions log with its time. The both times do not match.
What am I doing wrong?

1. I'm not sure what kind of reports is that.
2. Why do you expect server time (events) to match device time (positions)?

1. This is report from traccar.server.
2. you are right, this is any time i am in timezone gmt+1.

My devices give me any time?

Thank you for your help at this moment.

My devices give me any time?

Not sure what you mean exactly. Obviously devices report time.