Traccar Feature Suggestion – Device-wise time.override

I would like to suggest an improvement for the time.override functionality.

Currently, applying time.override at the protocol level affects all devices using that protocol, which can create issues when the problem is not common across all devices.

In our case, the time-related issue is device-specific, not protocol-specific. Therefore, it would be much more flexible and practical to implement time.override on a device-wise basis instead of only protocol-wise.

Suggested Improvement:
Add support for time.override as a device attribute
Keep protocol-level configuration as fallback (optional default)
Device-level setting should take priority over protocol-level setting
Benefit:
Prevents unintended impact on all devices under the same protocol
Allows fine-tuned control for problematic devices only
Improves flexibility in multi-device, multi-protocol environments
Reduces risk of breaking working devices when fixing one

This change would make troubleshooting time synchronization issues much safer and more scalable.

You could also simply copy the protocol and use the time.overide and use a new port for that same protocol and point all the devices that have the same issue to that new port (when you compile and run your own server instance).

Done:

https://github.com/traccar/traccar/commit/93d14fe5e6f76a9ff185131dbdaf8b5a51b3bbf7