I have just upgraded from a earlier version or Traccar (local instance on my own server), and re-registered my devices, and while they were working correctly before and correctly reporting their positions, speeds, directions, etc with Version 6.4 (Windows) the same devices are still sending the same protocol strings, but it seems that v6.4 is not able to correctly interpret these, so they appear at 0,0 in the middle of the Ocean
The string being sent / processed in the log previously was ;
2024-12-14 23:59:09 INFO: [988c334e: gt06 < 1.152.111.97] HEX: 78780a1305060400020300dee60d0a
2024-12-14 23:59:09 INFO: [988c334e: gt06 > 1.152.111.97] HEX: 787805130300d2100d0a
2024-12-14 23:59:09 INFO: [988c334e] id: 860121060088534, time: 2024-12-14 11:28:58, lat: -37.88107, lon: 145.05971, course: 355.0
However when looking at the details now (it is still sending the same format string), I can see the following, so it is online and communicating, but it seems that it is unable to process the string successfully;
Attribute Name Value
id Identifier 137
deviceId 2
protocol Protocol gt06
serverTime Server Time 12/13/2024, 11:47:35 AM
deviceTime Device Time 12/13/2024, 11:47:35 AM
fixTime Fix Time 01/06/1980, 11:00:19 AM
outdated No
valid Valid No
latitude Latitude 0.000000°
longitude Longitude 0.000000°
altitude Altitude 0.00 m
speed Speed 0.00 km/h
course Course ↑
Any suggestions as to cause, is there a config issue that I have missed ?
and a very happy user of this great software for years.
Probably your devices have not reported any locations yet. In your log I only see the status update that doesn't include a location.
@nton is correct. I have SeeWorld S5L on GT06 Protocol too and the firmware often hangs and coordinates jumps to 0:0 each time it happens every hour or so which makes the tracker unusable.
I added this into traccar.xml and the problem stopped!
<entry key='coordinates.filter'>true</entry>
<entry key='coordinates.minError'>10</entry>
<entry key='coordinates.maxError'>10000</entry>
I hope this custom attributes trick help you too.
Good Luck!
Cheers.
Rodney
And these filters could be helpfull
<entry key='filter.invalid'>true</entry>
<entry key='filter.zero'>true</entry>
I have tried this filter for 0:0 coordinates issues but often it does not work!
<entry key='filter.invalid'>true</entry>
<entry key='filter.zero'>true</entry>
Only this below filter works! As suggested by @nton.
<entry key='coordinates.filter'>true</entry>
<entry key='coordinates.minError'>10</entry>
<entry key='coordinates.maxError'>10000</entry>
I have just upgraded from a earlier version or Traccar (local instance on my own server), and re-registered my devices, and while they were working correctly before and correctly reporting their positions, speeds, directions, etc with Version 6.4 (Windows) the same devices are still sending the same protocol strings, but it seems that v6.4 is not able to correctly interpret these, so they appear at 0,0 in the middle of the Ocean
The string being sent / processed in the log previously was ;
However when looking at the details now (it is still sending the same format string), I can see the following, so it is online and communicating, but it seems that it is unable to process the string successfully;
Any suggestions as to cause, is there a config issue that I have missed ?
and a very happy user of this great software for years.