difference in time
Status time is the server time and position time is device time, so it seems like your device is reporting wrong time.
seems the time was 8 hours earlier, is there a setting that I can set the timezone for GT06?
If you don't know how to configure it on the device, you can also adjust it on the server.
can you provide a link to the doc that shows how to adjust?
i have two types of devices, namely h02 and gt06
h02 is sending in a correct local time:
2024-02-03 23:05:55 INFO: [Tfa44046f] id: 9170910955, time: 2024-02-03 23:05:34, lat: 10.35470, lon: 123.93352, course: 0.0gt06 is sending the data in the UTC time
2024-02-03 22:55:20 INFO: [Tebff68fd] id: 860501044914667, time: 2024-02-03 14:35:14, lat: 10.32714, lon: 123.91489, speed: 10.3, course: 60.0how to configure the server to use the gt06 in local time?
thanks
I don't think your device is sending UTC time. UTC is what's usually expected on the server side.
during the replay for gt06, I have to use 'custom' option and subtract 8 hours to show the correct data, I don't have to do this on the other h2 devices. also if using the seller's platform, replay shows up without doing a subtraction, seller confirms device sending UTC and platform adjust it.
Let's see the proof. Where is the raw data from the logs?
gt06:
2024-02-04 07:25:39 INFO: [T0623b5f4: gt06 < 110.54.186.240] 78780a13440603000200779bb90d0a
2024-02-04 07:25:39 INFO: [T0623b5f4] id: 860501044914667, time: 2024-02-03 23:20:31, lat: 11.32988, lon: 123.91814, course: 0.0
2024-02-04 07:25:39 INFO: [T0623b5f4: gt06 > 110.54.186.240] 787805130077ff400d0ah02:
2024-02-04 07:25:08 INFO: [T2fce34a7] id: 9175570030, time: 2024-02-04 07:25:05, lat: 11.32963, lon: 123.91827, course: 286.0The sample you provided doesn't have any GPS or timestamp. Make sure you check the samples against the protocol documentation first.
this is from another device, maybe 15 hours ago while the car is moving:
2024-02-03 18:49:48 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:49:43, lat: 10.31916, lon: 123.90882, speed: 11.9, course: 48.0
2024-02-03 18:49:58 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:49:53, lat: 10.31942, lon: 123.90911, speed: 2.7, course: 48.0
2024-02-03 18:50:08 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:50:03, lat: 10.31973, lon: 123.90954, speed: 17.3, course: 57.0
2024-02-03 18:50:18 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:50:13, lat: 10.32013, lon: 123.91020, speed: 12.4, course: 56.0
2024-02-03 18:50:28 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:50:23, lat: 10.32035, lon: 123.91051, speed: 2.2, course: 61.0
2024-02-03 18:50:38 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:50:33, lat: 10.32038, lon: 123.91055, course: 61.0
2024-02-03 18:53:07 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:53:02, lat: 10.32053, lon: 123.91075, speed: 5.9, course: 35.0
2024-02-03 18:53:13 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:53:06, lat: 10.32065, lon: 123.91079, speed: 7.0, course: 180.0
2024-02-03 18:53:14 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:53:08, lat: 10.32072, lon: 123.91078, speed: 6.5, course: 340.0
2024-02-03 18:53:18 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:53:14, lat: 10.32082, lon: 123.91073, speed: 5.4, course: 331.0
2024-02-03 18:53:29 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:53:24, lat: 10.32109, lon: 123.91059, speed: 7.0, course: 328.0
2024-02-03 18:53:39 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:53:34, lat: 10.32128, lon: 123.91047, speed: 1.6, course: 329.0
2024-02-03 18:53:59 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:53:54, lat: 10.32141, lon: 123.91038, speed: 4.9, course: 328.0
2024-02-03 18:54:09 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:54:04, lat: 10.32154, lon: 123.91030, course: 328.02024-02-03 18:54:38 INFO: [T56d21b7f: gt06 < 110.54.184.189] 787826121802030a3622cf011b7de50d4b4bf20515490203145aa400c4e4000000000039d60146548c0d0a
2024-02-03 18:54:38 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:54:34, lat: 10.32162, lon: 123.91025, speed: 2.7, course: 329.0
2024-02-03 18:54:38 INFO: [T56d21b7f: gt06 > 110.54.184.189] 7878051201469c4e0d0a
2024-02-03 18:54:39 INFO: [T251a7c97] connected
2024-02-03 18:54:49 INFO: [T56d21b7f: gt06 < 110.54.184.189] 787826121802030a362ccf011b7f190d4b4b350515460203145aa400c4e4000000000039ed014729220d0a
2024-02-03 18:54:49 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:54:44, lat: 10.32179, lon: 123.91015, speed: 2.7, course: 326.0
2024-02-03 18:54:49 INFO: [T56d21b7f: gt06 > 110.54.184.189] 7878051201478dc70d0a
2024-02-03 18:54:59 INFO: [T56d21b7f: gt06 < 110.54.184.189] 787826121802030a3636cf011b7f430d4b4b1f0015430203145aa400c4e4000000000039ef0148f6650d0a
2024-02-03 18:54:59 INFO: [T56d21b7f] id: 860501044912117, time: 2024-02-03 10:54:54, lat: 10.32182, lon: 123.91013, course: 323.0
2024-02-03 18:54:59 INFO: [T56d21b7f: gt06 > 110.54.184.189] 78780512014875300d0a
2024-02-03 18:55:09 INFO: [T5de27d65] disconnected
Hi,
Got a GT06 device, here is a log:
when it reports online, time is correct: 2024-02-02 21:20:31 but when it reports position, it was wrong: 2024-02-02 11:08:17
what's wrong here and how to correct it? thanks.