Intermittent charges incorrectly recorded about teslamate HOT 9 OPEN

Can you post the rest of the log from 28th Jan? I think the part you posted doesn't show the time when charging should have started again (I assume your time is currently UTC+11 and the time in the log is UTC).

from teslamate.

Hi,

Yes the logs timestamps are in UTC while Teslamate is set as UTC+11.

Please find attached the logs starting on the 27th 1pm UTC up until 28th 1pm UTC which should encapsulate both charges

teslamate.log

from teslamate.

While yesterday charge lined up well between the charger data and Teslamate, today's charge is missing 20+ minutes at the start in Teslamate and is thus under reported: 

teslamate_30.log

The Tesla app is correctly reporting 9kWh similar to the charger.

Any idea what's causing the erratic behavior as the charge reporting cannot be trusted as it stands ?
This time the charge once started was continuous unlike the prior examples.

from teslamate.

Intermitted charging and driving logging is possibly related to a change in the API endpoint, see #3629. However, your charging durations are longer as "typical" for this issue, see #3635.

A fix for the API endpoint change in the works, #3630.

from teslamate.

It looks like communication errors between the car and Tesla:

2024-01-30 00:39:50.107 [warning] GET https://owner-api.teslamotors.com/api/1/vehicles/.../vehicle_data -> 540 (2975.551 ms)
2024-01-30 00:39:50.107 [warning] TeslaApi.Error / vehicle error: it is online but not responsive
2024-01-30 00:39:50.107 car_id=1 [error] Error / :unknown
2024-01-30 00:40:10.617 car_id=1 [info] Suspending logging
2024-01-30 00:40:32.921 [warning] Too many disconnects from streaming API

I think the vehicle error: it is online but not responsive comes from the Tesla server.

Maybe a weak WiFi signal where the car is parked?

from teslamate.

from teslamate.

While they aren't related to the car, are the large number of MQTT timeouts expected?

from teslamate.

from teslamate.

TeslaMate wait for the car to fall asleep when the charge has stopped, and thus can be still in the state of waiting for sleep when you start charging again. This can only be prevented when forcing the car to be awake, or resume TeslaMate logging before start the charge again.

from teslamate.