Lost connection to car --> solved with 4.0.1

[wiredguydk]

Hi,

I've been running Teslamate in Docker for a couple of years without issue. Car is now upgraded to 2026.17.5 (FSD version 14.2.2.6) and teslamate is 4.0.0 (update from 2.0.0 went without issue). I've tried logging out in Teslamate and logging in again, but it seems there is no connection to the car anymore. It shows "Health check failed" and "Status: unavailable" currently. Would appreciate any help :-)

[dgooijer]

Same here. Seems the owner API is not accepting the connection.

[ktsenvolt]

Same issue.

[wdywdy6688]

the problem started yesterday afternoon (6/12), this morning, I tried docker pull and restarted the service, it seemed to be working, but now, same issue again

[wdywdy6688]

changed my image path to "ghcr.io/teslamate-org/teslamate:pr-5406" in docker-compose.yml file, it's working now

[pauste]

Same here. The owner API is not accepting the connection. Do I need to change to the fleet-api ?
I tried to go back to v3.1.0 but still get the "healthcheck failed" and "Status: unavailable"

[Disincentivato]

Same for me, Status: Not available.
and: healthcheck failed.

[svewag]

Teslamate: 4.0.0
Tesla: 2026.20

2026-06-14 07:08:09.150 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/9298474XXXXXXXX -> 403 (68.316 ms)
2026-06-14 07:08:09.150 [warning] TeslaApi.Error / %{"error" => "forbidden, see https://developer.tesla.com/docs/fleet-api", "error_description" => "", "response" => nil}
2026-06-14 07:08:09.150 car_id=1 [error] Error / :unknown

[SNP-MajorK]

Is for me the same. I have no Data since 12.06.2026.

Teslamate Version 4.0.0
Tesla: 2026.20

2026-06-14 07:54:16.274 [warning] TeslaApi.Error / %{"error" => "forbidden, see https://developer.tesla.com/docs/fleet-api", "error_description" => "", "response" => nil}
2026-06-14 07:54:16.274 [warning] Could not get vehicles: :unknown
2026-06-14 07:54:16.283 [warning] Using fallback vehicles:

2026-06-14 07:58:16.729 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/*************** -> 403 (40.313 ms)
2026-06-14 07:58:16.729 [warning] TeslaApi.Error / %{"error" => "forbidden, see https://developer.tesla.com/docs/fleet-api", "error_description" => "", "response" => nil}
2026-06-14 07:58:16.729 car_id=1 [error] Error / :unknown

[yantove95]

Is for me the same. I have no Data since 12.06.2026.

Teslamate Version 4.0.0
Tesla: 2026.20

Will we have to switch to the Tesla Fleet API, because it's really not great at all?

I've been using QNAP Container for six years now and I found it simple and easy to set up.
However, I'm wondering how to transition to a Fleet API given what's required on Tesla's page.
I hope it doesn't come to that.

[iBrobdingnagian]

Moring Guys. Same here.

vehicle_config: nil,
vehicle_state: nil
}
]
026-06-14 11:18:45.387 car_id=1 [error] Error / :unknown
2026-06-14 11:19:10.780 [notice] :alarm_handler: {:set, {TeslaMate.Vehicles.Vehicle_1_api_error, :fuse_blown}}
2026-06-14 11:19:15.428 [info] GET https://owner-api.teslamotors.com/api/1/vehicles//xxxxxxxxxxxx -> 403 (39.722 ms)
2026-06-14 11:19:15.428 [warning] TeslaApi.Error / %{"error" => "forbidden, see https://developer.tesla.com/docs/fleet-api", "error_description" => "", "response" => nil}

[tpd-opitz]

See here: #5399 and here: #5406

[iBrobdingnagian]

Thanks mate.

[wdywdy6688]

Thanks, #5406 worked for me.

[iHorstD]

Updated to 4.0.0 and logged off and on - still same error as mentioned above

[tpd-opitz]

Updated to 4.0.0 and logged off and on - still same error as mentioned above

Have you seen #5399 and #5406?

[iHorstD]

Thanks, I didn’t got that I have to pul a CI build. Thought that with the PR that was fixed and I just can repull. But this is only now with the release of 4.0.1 the case. For now I struggle with the update as portainer update somehow still gets 4.0.0 for me… need to try again and see why this is so wired now. I‘m sure the API issue is solved once I get this done. Thanks

[iHorstD]

ok, not it works again - thanks all for support

[pauste]

See here: #5399 and here: #5406

5406 fixed it for me

[wiredguydk]

Updated to 4.0.1 and it now works again from here - thanks :-)