Hello everyone! I apologize for the Google Translate. I have a question about what is happening in a request. When I do a fetch for /api/positions?deviceId=32&from=2025-03-29T03%3A00%3A00.000Z&to=2025-03-30T02%3A59%3A59.999Z (trying to get the entire route of the day) the result of the last known position is different from the last known position of the same device when I do it in /api/positions.
Is this behavior normal? Shouldn't the last position in /api/positions?deviceId=32&from=2025-03-29T03%3A00%3A00.000Z&to=2025-03-30T02%3A59%3A59.999Z be the same as the one that appears in /api/positions?
/api/positions always appears with a more up-to-date position relative to the other endpoint
What fix time value do you get when you call /api/positions?
This simple question opened my mind. I performed several tests and indeed both were receiving the same known position at the same time. The problem was a filter that had been created and therefore hid the route from the map, leaving it separate from the device. Thank you very much for your attention!
Hello everyone! I apologize for the Google Translate. I have a question about what is happening in a request. When I do a fetch for
/api/positions?deviceId=32&from=2025-03-29T03%3A00%3A00.000Z&to=2025-03-30T02%3A59%3A59.999Z(trying to get the entire route of the day) the result of the last known position is different from the last known position of the same device when I do it in/api/positions.Is this behavior normal? Shouldn't the last position in
/api/positions?deviceId=32&from=2025-03-29T03%3A00%3A00.000Z&to=2025-03-30T02%3A59%3A59.999Zbe the same as the one that appears in/api/positions?/api/positionsalways appears with a more up-to-date position relative to the other endpoint