You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Charging to 100% are not correctly recognized.
It seems the last bit of the charge is deleted and the charge all stop at 99% percent.
There is data from 1-30 minutes missing, corresponding the data in the tables chargingstate and charge are not existend for this time.
In the logs the charge is correctly recognized and the ending of the charge too, but teslalogger then seems to delete the charge at some point just before the end. Maybe because of the slow charge in the last few minutes.
Tested with a NMC battery, should be worse for LFP if the assumption of the slow charge at the end as culprit is correct. So probably the balancing isn’t correctly reported for these cars.
To Reproduce
Charge to 100%
Expected behavior
Charge correctly ending at the time where they stopped as reported by detailedchargingstate btw as correctly recognized in the logs.
No additional shortening of these charges later on.
Teslalogger Type
Raspberry PI 5 with Docker
1.62.14.0
The text was updated successfully, but these errors were encountered:
Describe the bug
Charging to 100% are not correctly recognized.
It seems the last bit of the charge is deleted and the charge all stop at 99% percent.
There is data from 1-30 minutes missing, corresponding the data in the tables chargingstate and charge are not existend for this time.
In the logs the charge is correctly recognized and the ending of the charge too, but teslalogger then seems to delete the charge at some point just before the end. Maybe because of the slow charge in the last few minutes.
Tested with a NMC battery, should be worse for LFP if the assumption of the slow charge at the end as culprit is correct. So probably the balancing isn’t correctly reported for these cars.
To Reproduce
Charge to 100%
Expected behavior
Charge correctly ending at the time where they stopped as reported by detailedchargingstate btw as correctly recognized in the logs.
No additional shortening of these charges later on.
Teslalogger Type
Raspberry PI 5 with Docker
1.62.14.0
The text was updated successfully, but these errors were encountered: