Comma Connect is Providing incorrect data from API

[jacobwaller]

Describe the bug

I'm trying to figure out how to fix some crummy data i'm getting from the Comma API. Connect shows my device in Montana, and it is definitely not in Montana. I think it has to do with the API and not the software i'm running (Although, that underlying data may have been broken by software I ran in the past)

https://api.comma.ai/v1/devices/38b065e31c0a9ed7/location
gives:

{
"dongle_id": "38b065e31c0a9ed7",
"lat": 44.5921,
"lng": -110.386,
"time": 39951532852000
}

That time field would indicate January 6, 3236 12:00:52 AM.

I've reached out to support, but they told me they can't help with software issues.

Provide a route where the issue occurs

38b065e31c0a9ed7

openpilot version

N/A

Additional info

[adeebshihadeh]

Your "latest" route has start_time 3236-01-05 15:58:50, which is causing this. Looking into how this happened, then I'll fix that row in the table.

[jacobwaller]

Hey thanks for looking into this. Not sure if it's important, but I DID go to Yellowstone in August (Approximately where this location is) and cell service is extremely spotty there.

Is there some case where the device having a spotty LTE connection could cause a weird time-sync glitch?

Thanks!