-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time offset for each device #3572
Comments
Any Update regarding this ? |
Not as far as I know. |
@tananaev thanks |
I'm thinking of this feature, we already have experience with users/server We have already implemented functions to lookup attribute device->group->server or device->group->config. If we use first one server timezone may not fit to devices, if we use second one we get unneeded lookup |
I agree with the second option to fallback to config. As for the value, how about we throw exception if it's in old format? It will force people to update their configs to start server. And in one of future releases (in a year or so) we can drop it completely. |
Is it OK if we do not have per protocol timezone in future? |
I think it's even better if we can implement a more universal solution. |
Hm...I also thought, we will get server attribute |
I don't think so. We just need to use some clear key. For example |
Hm, looks like GT06 basic devices report their timezone in login message https://github.com/tananaev/traccar/blob/master/src/org/traccar/protocol/Gt06ProtocolDecoder.java#L401 As I understand it should be applied to all other messages from this device, what do you think about extending |
I don't see any problem with it. |
Please implement configurable time offset for each device. There are plenty of cheap Chinese GPS trackers with poor documentation where correct time zone is impossible to setup. Even when using multiple GT06 devices, it is not possible to configure this "globally" as each device sends different timezone timestamp.
So I think the best is to add device attribute with Time Offset, so I can specify different offset for particular device.
The text was updated successfully, but these errors were encountered: