Hello
I Have a Dog GPS tracker YG119 running on the Huabao protocol, and everything works ok Except for the time.
i have confirmed when i SMS the unit for a location it comes up in 0 GMT time, and both my server and web client are +11
But when i look at the logs i get the following from this Unit
2025-11-18 20:59:43 INFO: [T3ed7a42d] id: 088076427003, time: 2025-11-18 12:59:38, lat: -37.90028, lon: 144.63213, course: 144.0
2025-11-18 20:59:45 INFO: [T3ed7a42d] id: 088076427003, time: 2025-11-18 12:59:40, lat: -37.90028, lon: 144.63213, course: 144.0
the time that is showing up is not GMT Time (12:59) above, it appears that the unit for some reason it appears to be sending +2 GMT time. unfortunately there is no much documentation on this, and as when i send a sms for a location the time is correct, im not sure why its doing this
is there any way to be able in Traccar to Offset the device to apply a fix time two hours earlier? i have tried ignoreFixTime but found out it does not work with this protocol
Thanks in advance
sorry it appears to be sending +3 GMT my mistake
You can configure timezone using decoder.timezone config parameter. It can also be configure per device.
Hello
I Have a Dog GPS tracker YG119 running on the Huabao protocol, and everything works ok Except for the time.
i have confirmed when i SMS the unit for a location it comes up in 0 GMT time, and both my server and web client are +11
But when i look at the logs i get the following from this Unit
the time that is showing up is not GMT Time (12:59) above, it appears that the unit for some reason it appears to be sending +2 GMT time. unfortunately there is no much documentation on this, and as when i send a sms for a location the time is correct, im not sure why its doing this
is there any way to be able in Traccar to Offset the device to apply a fix time two hours earlier? i have tried ignoreFixTime but found out it does not work with this protocol
Thanks in advance