API: logbook/most_recent_positions API endpoint reports stale data

[alexanv]

Subject of the issue

As of a week and a half ago the logbook/most_recent_positions/ API endpoint appears to report stale data:

e.g.
curl -X GET "https://api.autopi.io/logbook/most_recent_positions/" -H "accept: application/json" -H "Authorization: APIToken <redacted>"

[
  {
    "positions": [
      {
        "utc": "18:01:20",
        "course_over_ground": 129.43,
        "speed_over_ground": 0,
        "altitude": 58.1,
        "ts": "2021-12-30T18:01:21.098840Z",
        "nsat": 7,
        "location": {
          "lat": <redacted>,
          "lon": <redacted>
        }
      }
    ],
    "unit_id": "1ec61816-5df9-adeb-21cf-60dae2159003",
    "ts": "2021-12-30T18:01:21.098840Z"
  },
  {
    "positions": [
      {
        "utc": "17:42:38",
        "course_over_ground": 353,
        "speed_over_ground": 0,
        "altitude": 105.5,
        "ts": "2021-12-30T17:42:38.570356Z",
        "nsat": 6,
        "location": {
          "lat": <redacted>,
          "lon": <redacted>
        }
      }
    ],
    "unit_id": "62776ad1-2236-f19c-f6f2-9d27975c6b6f",
    "ts": "2021-12-30T17:42:38.570356Z"
  }
]

The timestamp above for both of my units is 12-30-2021 despite both vehicles having more recent position data that can be retrieved via most_recent_position endpoint with the device_id

Is this the expected behavior?
I see that there are “v2” endpoints (/logbook/v2/most_recent_position/ and /logbook/v2/most_recent_positions/). Should these be used instead and the v1 endpoints are now deprecated?

[Eriks]

Hi @alexanv,

Yes, you should be using the V2 endpoints from now on. And doing a request to V2 will also return the correct position data.