Closed fysmd closed 3 months ago
It seems like your charge was not terminated by TelsaMAte correctly, please follow (due to Tesla API down/rate limit): https://docs.teslamate.org/docs/maintenance/manually_fixing_data#terminate-a-drive-or-charge
Beside of that: If you charge, stop, charge, these are technically independent charges for Tesla and therefore for TeslaMate. If you charge, stop, then TeslaMate will give your car time to going to sleep state. So you need to either keep it from doing by manual press in webpage, http request or whatever.
Looks like Tesla API was not responsive, perhaps that caused teslamate to not notice the charge?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
Is there an existing issue for this?
What happened?
I use Inteligetnt octopus charging at home and this will sometimes start and stop AC charging as it sees fit. Yesterday I connected and the charge scedule was split into two parts but teslamate detected the first hour and then did not start the 2nd charge period on time. Data in Grafana shows the complete data (see screenie of the whole period) is there but it is not captured in a charge record,
Expected Behavior
I would expect each part of a charge session to be captured and reported as a seperate chargw
Steps To Reproduce
No response
Relevant log output
Screenshots
Additional data
00charges.csv
but unfortunately: ~/data$ psql teslamate -U teslamate -c "COPY (select from charging_processes where date > '2024-04-19') TO STDOUT WITH CSV HEADER" > 00charging_processes.csv ERROR: column "date" does not exist LINE 1: COPY (select from charging_processes where date > '2024-04... ^
Type of installation
Docker
Version
v1.28.5