Charges not ending if vehicle lost connection

[bodosom]

Discussed in #4483

^{Originally posted by bodosom January 8, 2025}

In the last few weeks, I've had a couple of charges that didn't terminate when charging stopped. Other non-Teslamate systems work and a MyTeslaMate instance is working. Log snip below starting abount when charging stopped.

teslamate-1  | 2025-01-21 06:40:07.905 [info] GET https://owner-api.teslamotors.com/api/1/vehicles//vehicle_data -> 408 (156.024 ms)
teslamate-1  | 2025-01-21 06:40:08.055 car_id=1 [warning] Vehicle went offline while charging
teslamate-1  | 2025-01-21 06:40:18.202 [info] GET https://owner-api.teslamotors.com/api/1/vehicles//vehicle_data -> 408 (145.368 ms)
teslamate-1  | 2025-01-21 06:40:18.419 car_id=1 [warning] Vehicle went offline while charging
...
teslamate-1  | 2025-01-21 14:45:42.492 [info] GET https://owner-api.teslamotors.com/api/1
/vehicles//vehicle_data -> 408 (150.943 ms)
teslamate-1  | 2025-01-21 14:45:42.669 car_id=1 [warning] Vehicle went offline while char
ging
teslamate-1  | 2025-01-21 14:45:53.073 car_id=1 [info] Derived efficiency factor: 149.130
00000000002 Wh/km (77x confirmed)
teslamate-1  | 2025-01-21 14:45:53.073 car_id=1 [info] Charging / Complete / 2.46 kWh – 5
36 min
teslamate-1  | 2025-01-21 14:45:53.078 car_id=1 [info] Start / :online
teslamate-1  | 2025-01-21 14:45:53.112 car_id=1 [info] Connecting ...

[JakobLichterfeld]

Vehicle went offline while charging

check your internet connection.

But this does not result in not ended charges, we do cover this with our automated tests as well.

[bodosom]

check your internet connection.

If this was a network issue shouldn't all systems be failing? It could be foolishness on my part but I assume the MyTeslaMate code is similar to the public image and it reported the expect end of charging.

[JakobLichterfeld]

If this was a network issue shouldn't all systems be failing?

I assume you are running TeslaMate on your end and

Other non-Teslamate systems

are server based. So a network error on your end will in fact result in your described behavior, as the connection is lost

[bodosom]

If this was a network issue shouldn't all systems be failing?

I assume you are running TeslaMate on your end

I was unclear, I run two stand-alone legacy API instances. One is residential, the other is at Cloudflare (Linode). Both of my instances show this issue. I also have a hosted MyTeslaMate instance using the Fleet API which also has this issue but not in lockstep with the other two. All three Teslamates are version 1.32.0 but MyTeslaMate may have local mods to the monitoring code.