Traccar (3.7) odd position/time issue
Again an issue but only with a date in the future this time. Maybe there should be a threshold to not store the information if the date is X hours ahead of server time. It could probably be in the filters section.
2016-12-19 20:59:52 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2a48512c343230393931343239372c4e42522c3139353934392c3
230362c312c302c372c323031342c32383832302c35302c323031342c32383832322c34312c323031342c32383830322c34302c323031342c3238
3832312c33362c323031342c32383832352c32362c323031342c34313131382c32302c323031342c32383732332c31392c3139313231362c46464
646464246462c3523
2016-12-19 20:59:52 INFO: Position filtered by Duplicate filters from device: 4209914297 with id: 4
2016-12-19 21:00:03 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2442099142971959571908245048893005004160870c000000fff
ffbffff001f000000254000ce0100000000ae
2016-12-19 21:00:03 INFO: [D3EE1A4D] id: 4209914297, time: 2024-08-19 21:59:57, lat: 50.81488, lon: 4.26812, speed: 0.0, course: 0.0
2OK, I just noticed there is already such a filter.. :)
But not documented
Please provide HEX messages for the whole TCP session.
Here they are (well, till the problem)
2016-12-19 20:58:19 INFO: [D3EE1A4D] connected
2016-12-19 20:58:19 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2a48512c343230393931343239372c56312c3139353831382c562c353034382e383933312c4e2c30303431362e303837382c452c3030302e30302c3030302c3139313231362c46464646464246462c3230362c30312c302c302c3523
2016-12-19 20:58:19 INFO: [D3EE1A4D] id: 4209914297, time: 2016-12-19 20:58:18, lat: 50.81489, lon: 4.26813, speed: 0.0, course: 0.0
2016-12-19 20:58:19 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2a48512c343230393931343239372c5631392c3139353831372c562c353034382e383933312c4e2c30303431362e303837382c452c3030302e30302c3030302c3139313231362c2c303033323437353837343134312c383934343533383533303030303534333430333f2c464646464642464623
2016-12-19 20:58:19 INFO: [D3EE1A4D] id: 4209914297, time: 2016-12-19 20:58:17, lat: 50.81489, lon: 4.26813, speed: 0.0, course: 0.0
2016-12-19 20:58:24 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2a48512c343230393931343239372c4e42522c3139353832332c3230362c312c302c372c323031342c32383832302c36332c323031342c32383832322c36332c323031342c32383832352c35362c323031342c32383830322c34342c323031342c32383832312c33342c323031342c34313131382c32362c323031342c35353333342c32352c3139313231362c46464646464246462c3523
2016-12-19 20:58:35 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2442099142971958321912165048893005004160870c000000fffffbffff001f000000254000ce0100000000aa
2016-12-19 20:58:35 INFO: [D3EE1A4D] id: 4209914297, time: 2016-12-19 20:58:32, lat: 50.81488, lon: 4.26812, speed: 0.0, course: 0.0
2016-12-19 20:58:46 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2a48512c343230393931343239372c4e42522c3139353834332c3230362c312c302c372c323031342c32383832302c36322c323031342c32383832322c35312c323031342c32383830322c34342c323031342c32383832352c34322c323031342c32383832312c32362c323031342c34313131382c32322c323031342c32383732332c31392c3139313231362c46464646464246462c3523
2016-12-19 20:58:57 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2442099142971958541912165048893005004160870c000000fffffbffff001f000000254000ce0100000000ab
2016-12-19 20:58:57 INFO: [D3EE1A4D] id: 4209914297, time: 2016-12-19 20:58:54, lat: 50.81488, lon: 4.26812, speed: 0.0, course: 0.0
2016-12-19 20:59:08 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2a48512c343230393931343239372c4e42522c3139353930352c3230362c312c302c372c323031342c32383832302c35332c323031342c32383832322c34362c323031342c32383832352c33362c323031342c32383830322c33352c323031342c32383832312c32392c323031342c34313131382c31362c323031342c32383732332c31362c3139313231362c46464646464246462c3523
2016-12-19 20:59:19 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2442099142971959181912165048893005004160870c000000fffffbffff001c000000254000ce0100000000ac
2016-12-19 20:59:19 INFO: [D3EE1A4D] id: 4209914297, time: 2016-12-19 20:59:18, lat: 50.81488, lon: 4.26812, speed: 0.0, course: 0.0
2016-12-19 20:59:30 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2a48512c343230393931343239372c4e42522c3139353932372c3230362c312c302c372c323031342c32383832302c35362c323031342c32383830322c34332c323031342c32383832322c34322c323031342c32383832312c33382c323031342c32383832352c33372c323031342c35353333342c32362c323031342c34313131382c32362c3139313231362c46464646464246462c3523
2016-12-19 20:59:41 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2442099142971959381912165048893005004160870c000000fffffbffff001d000000254000ce0100000000ad
2016-12-19 20:59:41 INFO: [D3EE1A4D] id: 4209914297, time: 2016-12-19 20:59:38, lat: 50.81488, lon: 4.26812, speed: 0.0, course: 0.0
2016-12-19 20:59:52 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2a48512c343230393931343239372c4e42522c3139353934392c3230362c312c302c372c323031342c32383832302c35302c323031342c32383832322c34312c323031342c32383830322c34302c323031342c32383832312c33362c323031342c32383832352c32362c323031342c34313131382c32302c323031342c32383732332c31392c3139313231362c46464646464246462c3523
2016-12-19 21:00:03 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2442099142971959571908245048893005004160870c000000fffffbffff001f000000254000ce0100000000ae
2016-12-19 21:00:03 INFO: [D3EE1A4D] id: 4209914297, time: 2024-08-19 21:59:57, lat: 50.81488, lon: 4.26812, speed: 0.0, course: 0.0
2016-12-19 21:00:14 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2a48512c343230393931343239372c4e42522c3230303031322c3230362c312c302c372c323031342c32383832302c35392c323031342c32383832312c36302c323031342c32383830322c35342c323031342c32383832322c35302c323031342c34313131382c32372c323031342c32383732332c32332c323031342c32383832352c32332c3139303832342c46464646464246462c3523
2016-12-19 21:00:25 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2442099142972000221912165048893005004160870c000000fffffbffff001d000000254000ce0100000000af
2016-12-19 21:00:25 INFO: [D3EE1A4D] id: 4209914297, time: 2016-12-19 21:00:22, lat: 50.81488, lon: 4.26812, speed: 0.0, course: 0.0
2016-12-19 21:00:36 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2a48512c343230393931343239372c4e42522c3230303033332c3230362c312c302c372c323031342c32383832302c35362c323031342c32383832312c35372c323031342c32383832322c35322c323031342c32383830322c35312c323031342c34313131382c33372c323031342c32383832352c33342c323031342c32383732332c33312c3139313231362c46464646464246462c3523
2016-12-19 21:00:47 DEBUG: [D3EE1A4D: 5013 < 213.137.13.4] HEX: 2442099142972000441912165048893005004160870c000000fffffbffff001a000000254000ce0100000000b0
2016-12-19 21:00:47 INFO: [D3EE1A4D] id: 4209914297, time: 2016-12-19 21:00:44, lat: 50.81488, lon: 4.26812, speed: 0.0, course: 0.0
This looks like completely different issue from the original one discussed in this thread. Device reported invalid date. Looks like a device malfunction. You can use future filter, but ideally vendor should fix it with a firmware update.
It could be an interesting challenge to make a chinese provider of cheap tracking device update its firmware for devices he already sold.
Speaking of the future filter, shouldn't FILTER_FUTURE_LIMIT be configurable instead of fixed at 5 minutes?
Yes, ideally it should be configurable. At the moment, it's not.
Hi @AlphaTek and @renaud
I am facing the same problem in my GPS tracker. It is sending LBS location info by default with the GPS location. And when i try to find the GPS device in the traccar server it show the location in the middle of the Ocean which is Atlantic Ocean.
Please can you tell me how do u have resolve this issue.
Here is the log
HEX:
2a68712c3335363332373038313031363035342c56312c3031303330302c562c303030302e303030302c4e2c30303030302e303030302c452c3030302e30302c302c3031303131352c46464646464646462c34332c332c3437302c3030322c39322c333536352c302c39322c313235382c35362c39322c313230392c343423Decoded HEX :
*hq,356327081016054,V1,010300,V,0000.0000,N,00000.0000,E,000.00,0,010115,FFFFFFFF,43,3,470,002,92,3565,0,92,1258,56,92,1209,44#
Yes, it should fix the issue.