FW 12.0.43
I’m writing a little tool in NodeJS at the moment and while just watching what’s going on, I noticed that my T-Beam (f244e3c4) seems to send different times in the location packages. I had a Lora32 V2 connected to the USB port and that’s the output:
2021-09-01T05:11:04.000Z from f244e3c4 to ffffffff Userinfo: !f244e3c4 Wolfman Wlf 4
2021-09-01T05:11:34.000Z from f244e3c4 to ffffffff Location: 612552981 240564764 124 2021-09-01T05:11:34.000Z
2021-09-01T05:11:43.000Z from 91990330 to ffffffff Userinfo: !91990330 Maiju Mai 1
2021-09-01T05:12:14.000Z from 91990330 to ffffffff Location: 612551322 240563480 123 ????-??-??T??:??:??.???Z
2021-09-01T05:15:45.000Z from f244e3c4 to ffffffff Location: 612551521 240563413 124 2021-09-01T12:08:17.000Z
2021-09-01T05:16:05.000Z from f244e3c4 to ffffffff Userinfo: !f244e3c4 Wolfman Wlf 4
2021-09-01T05:16:36.000Z from f244e3c4 to ffffffff Location: 612551521 240563413 124 2021-09-01T05:16:36.000Z
2021-09-01T05:17:58.000Z from 91990330 to ffffffff Userinfo: !91990330 Maiju Mai 1
2021-09-01T05:18:29.000Z from 91990330 to ffffffff Location: 612551322 240563480 123 ????-??-??T??:??:??.???Z
The correct time would be 12:08:17.000Z in this case. I suspect, the location package with the wrong time was initiated by the device firmware and the location package with the right time was initiated by the app on the paired phone. I have disabled the GPS on the T-Beam in question because the antenna is broken and I’m waiting for a new one. I assumed it would use the phone position then.
It appears that the T-Beam does remember the position from a phone-initiated transmit but for some reason not the time.