I am using Sinotrack ST901 devices with the h02 protocol and encountering a week rollover issue. This happens because the GPS week counter is 10-bit, which resets every 1024 weeks (~19.7 years).
Problem:
After ~19 years from the GPS epoch, the device shows an incorrect date (e.g., 2006 instead of 2025).
The time (hours, minutes, seconds) is still correct.
Historical data and replay in Traccar display wrong timestamps later 19 years
Is there an official solution from Traccar to handle the 1024-week rollover for Sinotrack ST901 devices?
If not, what is the recommended workaround on the Traccar server side or in the protocol decoder?
Some sources suggest applying a 1024-week offset (~19.7 years) to the timestamp or modifying the H02 decoder.
I want to know if Traccar provides a built-in fix or an official method to correct this issue.
Thank you in advance for any guidance!
What version of Traccar are you using?
I'm using
Traccar Server Version: 6.8.1
You should upgrade to the latest version.
I am using Sinotrack ST901 devices with the h02 protocol and encountering a week rollover issue. This happens because the GPS week counter is 10-bit, which resets every 1024 weeks (~19.7 years).
Problem:
After ~19 years from the GPS epoch, the device shows an incorrect date (e.g., 2006 instead of 2025).
The time (hours, minutes, seconds) is still correct.
Historical data and replay in Traccar display wrong timestamps later 19 years
Is there an official solution from Traccar to handle the 1024-week rollover for Sinotrack ST901 devices?
If not, what is the recommended workaround on the Traccar server side or in the protocol decoder?
Some sources suggest applying a 1024-week offset (~19.7 years) to the timestamp or modifying the H02 decoder.
I want to know if Traccar provides a built-in fix or an official method to correct this issue.
Thank you in advance for any guidance!