Time Override Only for Specific Protocol / Device (Huboo)
Sorry, by mistake I wrote protocol name wrong. The correct protocol name is: Huabao.
You can use time.protocols to specify which protocol(s) to apply time override to.
Couldn't the protocol be adjusted to handle GPS Week Number Rollover?
It could be.
ok! As a partial fix, I did this for this protocol.
<!-- Uses the server time instead of the device's fixTime. -->
<entry key='time.override'>serverTime</entry>
<!-- Apply only to the EasyTrack protocol (so as not to affect other devices). -->
<entry key='time.protocols'>easytrack</entry>
Same problem with a gt06 protocol devices. This is definitely a traccar update that has created problems.
This is definitely NOT Traccar update that created this problem.
Hi Anton, how can we contribute to this fix? I see several issues being closed dealing with this topic. What do you suggest and what files do you recommend so that nothing is too simple or exaggerated?
It's already fixed.
Hello,
I have a problem with someone of my devices (protocol: huboo) reporting the wrong date and month. Example:
Device Time: 01/02/2006
Fix Time: 01/02/2006
Server Time: 08/18/2025
The data (ignition, distance, location etc.) is correct, but the timestamps are wrong.
I know Traccar has the time.override option, but when I enable it globally the device stops updating locations. Also, I don’t want this override for all devices, only for:
Specific protocol (huboo)
Or specific device(s)
My questions:
Is it possible to apply time.override only for a specific protocol (like huboo)?
If not, is there a way to apply it only for one device (via attributes, config, or database)?
Basically, I want to save data with Server Time only for certain devices where the Device/Fix Time is always wrong, without affecting others.
Any suggestions or solution?
Thanks!