Closed bscx closed 5 months ago
After waking up my vehicle the error no info on this car ID
wouldn't show up any more. However, the data in /status
is incomplete. For example:
"car_geodata": {
"geofence": "",
"latitude": 0,
"longitude": 0
},
At the same time, I'm seeing this:
2024-03-16 21:14:20.050 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/xxx/vehicle_data -> 408 (9125.258 ms)
2024-03-16 21:14:20.051 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
2024-03-16 21:14:20.052 car_id=1 [error] Error / :unknown
So, the problem is neither with mosquitto, with teslamateapi nor with my setup but with the Tesla API at this point, right?
hi @bscx, it takes some time for the data to arrive in the MQTT broker. TeslaMate talks to Tesla API and they send information to TeslaMate who feeds information into the MQTT, from where TeslaMateApi collects the information from. So there is a delay which also happens when you upgrade your TeslaMate-setup. I usually upgrade/restart when it's parked, so I don't lose "logged data", but it should not take more than 30-60 seconds usually.
After having updated eclipse-mosquitto:2, a
GET /api/v1/cars/1/status
would return:However,
GET /api/v1/cars/1
would just work fine (same for/drives
and/charges
for example).After attaching to the
teslamate-teslamateapi-1
container, I was able to observe the following. Please note, that in the first output there's this linemqtt connected
which is missing in the second.and
My mosquitto configuration has not changed:
I'm quite sure it worked before the mosquitto update but I can't put the finger on if it's now mosquitto, teslamateapi or simply my setup. I'm happy to support with more information if needed.