Wrong time?

dennis 5 years ago

Hi!

I'm using traccar on a few devices like the ST-901.
Since today i have a ST-901M but the time is wrong.

This is correct:

2021-05-03 20:40:16  INFO: [e755568e: h02 < 18.197.xx.xx] HEX: 2a48512c39xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2021-05-03 20:40:16  INFO: [e755568e: h02 > 18.197.xx.xx] HEX: 2a48512c39xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2021-05-03 20:40:16  INFO: [e755568e] id: 917xxxxxx, time: 2021-05-03 20:40:13, lat: 53.xxxxx, lon: 5.xxxxx, course: 20.0

But on the web interface the time is +2 hours. The device has a setting of TIME ZONE:00 so thats correct. All my devices are like that without any problems.
I have tried to change the time zone to W02 to put it back -02 UTC but still its wrong.
Then i see in the logs:

2021-05-03 20:30:49  INFO: [e755568e] id: 917xx, time: 2021-05-03 22:30:47

But still the time is exactly the same on the web interface.

The biggest problem of this is that the location on the map isnt beeing updated. In the log i do so the new coordinates. What to do?

dennis 5 years ago

Sometimes i see this

2021-05-03 19:38:41  INFO: [b31bb5c5] connected
2021-05-03 19:38:41  INFO: [b31bb5c5] id: 917xxxxxx, time: 2021-05-03 21:38:40, lat: 53.xxxxx, lon: 5.xxxxx, course: 0.0
2021-05-03 19:39:41  INFO: [b31bb5c5] id: 917xxxxxx, time: 2021-05-03 19:39:39, lat: 53.xxxxx, lon: 5.xxxxx, course: 340.0

When its connecting it first starts with wrong time but not always

dennis 5 years ago

Ok... i think i have the sollution.
I have changed a old device to this new ID because i replaced the ST901 with this ST901M.

But when i now created a new device in traccar with this ID everything is going alright.
How is this possible? Its the same protocol and almost same device. How can i do this the good way because i want to keep the history
The old device im changing ID has no attributes to this cant be it.

Edit: oh... this worked for a few minutes... :/

Anton Tananaev 5 years ago

If you think something is not decoded correctly, we'll need to see a sample with expected and actual values.

dennis 5 years ago

What do you want me to provide.

2021-05-03 20:40:16  INFO: [e755568e] id: 917xxxxxx, time: 2021-05-03 20:40:13, lat: 53.xxxxx, lon: 5.xxxxx, course: 20.0

This is in the traccar log

on the web gui i see 22:40:13 and its not updating any GPS location in the web gui, in the log i see it changing

Anton Tananaev 5 years ago
  1. Clearly you masked some data. We won't be able to check like this.
  2. We need some evidence that it's not a device issue.
dennis 5 years ago

Isnt publishing the HEX exposing my location?

Anton Tananaev 5 years ago

Yes. But without it we won't be able to verify your sample.

dennis 5 years ago

I have send a email. It happend when i changed the Traccar Device that was using a watch protcol (TK905) to the new ID from a ST-901M thats using H05.
Now everything is messed up somehow. Even when i turn it back to the old situation.

dennis 5 years ago

Made a typo. H05 Should be h02 sorry

Anton Tananaev 5 years ago

If your last location is already in the future, fixing time won't immediately solve it. Traccar always shows you latest location by time.

dennis 5 years ago

For example:
Its now 21:00, In the log i see 21:00 in the device log and in the web gui the time is presented at the device as 21:17
That cant be right? Also the location isnt being updated in this scenario but in the log i see the GPS coordinates chancing.

It shouldn't be a problem to reuse a traccar device that was before lets say using the protocol watch and then it had a ID change to a h02 device?

Anton Tananaev 5 years ago

There is no problem with reusing devices. It should work just fine.

dennis 5 years ago

Thats strange, i really think thats part of my problem. The device still shows as a h02 protocol device in the web gui but it is for over an hour a Watch device and also using the correct ports.

Anton Tananaev 5 years ago

It sounds like your problem is that previous device reported time in the future.