bassmaster187
End-SOC not correct after charging
Append Logfile Posted it privat.
Describe the bug Charged till 64%. In the last 3 minutes there was only one SOC with 63% (without any decimals). No other charging states. Charged ended with 63%, just 3 minutes after the end of charging, the car a new transmitted SOC with 63,9994% corresponding to the right charge at the ending of the charging.
This is a telemtry Error which is replicable in e.g. TeslaFi, but they chose in this special instance a latter SOC as the ending SOC.
To Reproduce Normal charge, right now, I have no idea how to reproduce this error. Maybe it was a one time error from Telemetry.
Expected behavior Correct SOC at the end of charge. Either with taking a later SOC or making a issue with Tesla.
Screenshots
Teslalogger Type Raspberry Pi4, Docker, Selfmade
I haven‘t had this issue anymore.
Sometimes there is a new charging a bit later, but this is mostly relevant for DC charging, where the charge only ends after unpluging the car. And so waiting a few seconds usually leads to a correct SOC.
I would close this issue, if nobody has it anymore. Maybe fixed via Tesla.
The 100% charging bug is/was something else though, there TeslaLogger deletes the rest of the correct recognized charging (according to the log) and shortens it after finishing for more then 20 minutes
Today I run in this issue again, completing a charge (ac 8 ampere, 3 phases) with 60,7 instead of 62,2%. (As directly reported after the charge)
After observing the last charges closely:
It seems to be a problem with fleet api since SOC is sometimes reported after end of charge. But it also seems like the SOC itself doesn‘t lead to a charging entry, at least not when the SOC is reported just before the end of charging.
At least that SOC changes trigger a charging entry would alleviate the problem for SOC. But it would still continue in cases of SOC change after end of charging.