Time stamp empty about traccar

[tananaev]

As for time field... you are using Firefox, right? If yes, it is know issue, fixed in source code repository, but I haven't released a new traccar with this fix yet. Try to use Chrome until I release it.

Power field doesn't work with all devices, let me know what device and protocol you are using and I will confirm if it supports power or not.

Speed is in the same unit as device sends it, probably it is in knots (equal to one nautical mile (1.852 km) per hour, approximately 1.151 mph).

[jacobsr2]

Perfect! I was using Firefox. Chrome works.

The time is 2 hours out though (2 hours ahead). Where do I adjust the time? The test was 11:00 am
but Chrome displays 13:00. My time zone is GMT +2

I am using the Android client. Power not an issue. On this note, is a client for Blackberry in the pipeline?

Kind Regards
Riaan

[tananaev]

Sorry for delay in answer.

Android Client uses protocol that doesn't support power. Power is most critical for devices with no display, when you can't say how much time left till empty battery. I don't think there will Blackberry client any time soon, sorry. I am trying to concentrate my efforts on new features for main project - traccar server.

[tananaev]

For time adjustment you need to change (in traccar config)
:time
to
DATEADD('HOUR', -2, :time)

PS previous advice was wrong, it was for OpenGTS config

[jacobsr2]

Super, thanks!

Last question: How do I clean the Positions history field? It grew so large, the web interface
slowed down to a crawl.

Thanks again for a stunning platform!

Regards

[tananaev]

Yeah, that's a problem... if you have some knowledge in SQL you can connect to database with any JDBC manager and remove data from table. If you don't, probably the only way is to delete database file and start again, but you will need add all devices and IMEI numbers again.
Database file - %Program Files%\Traccar\data\database

[tananaev]

As I commented earlier time stamp problem is already fixed and version with this fix will be released soon, so I am closing this issue.

By the way possible solution for cleaning old position is described in issue #63.