fixTime in positions query

code_af2 years ago

Hi,
I checked the forum there are some discussion exists on this topic, I came across an issue too:

The device reported a position at 2023-01-19 00:00:00 then it only sent heartbeat every 5 minutes up to 2023-01-23 00:00:00. I know that if everytime heartbeat is reported, the last position is copied ahead, and the fixTime in this new copied position is same as previous (2023-01-19 00:00:00) because there isn't any fixTime included in hearbeat data.

Now I want to check the device positions between 2023-01-20 00:00:00 - 2023-01-21 00:00:00, I expected to get all those duplicated positions which was copied with heartbeat, but the result set is empty.

If, I want to check the device positions between 2023-01-18 23:59:00 - 2023-01-19 00:01:00, I expect to get all those positions which are reported in this mentioned date interval, but I get all those positions also which are duplicated one day later by heartbeat (during 2023-01-20 and 2023-01-21).

So, anyone knows, is it the intentional expected behaviour?

Anton Tananaev2 years ago

That's because we use GPS fix time for reports.

code_af2 years ago

Okay, then how if we set fixTime's value manually sometimes, to avoid this problem?
For example, specifically for watch protocol here, if we set the current time as fixTime when it reported a LK with batteryLevel?

Anton Tananaev2 years ago

I guess you could.