Hello --
I have one single device suddenly coming up with weird positioning info - this is the log:
2018-05-31 06:51:06 INFO: [7814C9A5] connected
2018-05-31 06:51:07 DEBUG: [7814C9A5: 5013 < 194.[redacted]] HEX: 2a48512c343130393230333439322c56312c3034333132372c562c343933352e393431382c4e2c30303630382e363138322c452c3030302e30302c3030302c3331303531382c46464646464246462c3237302c30312c302c302c3323
2018-05-31 06:51:07 INFO: [7814C9A5] id: 4109[redacted], time: 2018-05-31 06:31:27, lat: 49.[redacted], lon: 6.[redacted], speed: 0.0, course: 0.0
2018-05-31 06:51:08 DEBUG: [7814C9A5: 5013 < 194.[redacted]] HEX: 2a48512c343130393230333439322c23
2018-05-31 06:51:09 DEBUG: [7814C9A5: 5013 < 194.[redacted]] HEX: 2a48512c343130393230333439322c5631392c3034353130352c562c343933352e393431382c4e2c30303630382e363138322c452c3030302e30302c3030302c3331303531382c2c2b3335323632313237363234322c38393335323031393130333032333239353538462c464646464642464623
2018-05-31 06:51:09 INFO: [7814C9A5] id: 4109[redacted], time: 2018-05-31 06:51:05, lat: 49.[redacted], lon: 6.[redacted], speed: 0.0, course: 0.0
2018-05-31 06:51:09 DEBUG: [7814C9A5: 5013 < 194.[redacted]] HEX: 2a48512c343130393230333439322c4e42522c3034353130352c3237302c312c302c362c313031312c31353435352c33312c313031312c31353637352c32352c313031312c31333130362c32322c313031312c31353435342c32312c313031312c31333130372c31352c313031312c31353336382c31332c3331303531382c46464646464246462c3323
2018-05-31 06:51:09 INFO: [7814C9A5] id: 4109[redacted], time: 2035-07-03 09:30:39, lat: 34.65539, lon: -314.05059, speed: 343.0, course: 232.0
It seems to be sending correct positioning data (the 49/6 latitudes with the correct date) and then immediately after it sends (or Traccar receives) a bogus position with a timestamp far into the future.
When I get an SMS of the device, the position is always correct.
I've reset the device and reconfigured it, but that didn't change anything. Not touched Traccar, apart from restarting it, since this happened.
What should I be looking for?
This problem has been discussed countless number of times. If you are interested in details search forum, but what you need to do now is configure future time filtering and re-create device.
Thanks for the hint, Anton - that fixed it. Seems like my google fu was not good, I did not find this issue.
Hello --
I have one single device suddenly coming up with weird positioning info - this is the log:
It seems to be sending correct positioning data (the 49/6 latitudes with the correct date) and then immediately after it sends (or Traccar receives) a bogus position with a timestamp far into the future.
When I get an SMS of the device, the position is always correct.
I've reset the device and reconfigured it, but that didn't change anything. Not touched Traccar, apart from restarting it, since this happened.
What should I be looking for?