-
-
Notifications
You must be signed in to change notification settings - Fork 179
Description
Append Logfile
29.06.2025 14:45:41 : #1[.NET TP Worker:26]: *** FT: { "data": [ { "key": "DetailedChargeState", "value": { "detailedChargeStateValue": "DetailedChargeStateComplete" } }, { "key": "ChargeState", "value": { "stringValue": "Idle" } }, { "key": "TimeToFullCharge", "value": { "invalid": true } }, { "key": "ACChargingPower", "value": { "doubleValue": 0 } }, { "key": "IdealBatteryRange", "value": { "doubleValue": 177.09803525723663 } }, { "key": "PackCurrent", "value": { "doubleValue": -0.4000000059604645 } }, { "key": "Soc", "value": { "doubleValue": 61.96487376509331 } } ], "createdAt": "2025-06-29T12:45:41.774594562Z", "vin": "LRW3E7EL3NC520044" }
29.06.2025 14:45:41 : #1[.NET TP Worker:26]: *** FT: Key: DetailedChargeState
29.06.2025 14:45:41 : #1[.NET TP Worker:26]: *** FT: ChargeState Idle
29.06.2025 14:45:41 : #1[.NET TP Worker:26]: *** FT: Stop AC Charging ***
29.06.2025 14:45:41 : #1[.NET TP Worker:26]: *** FT: ACCharging = False
29.06.2025 14:45:41 : #1[.NET TP Worker:26]: *** FT: Insert Location
29.06.2025 14:45:41 : #1[.NET TP Worker:26]: *** FT: DetailedChargeState: DetailedChargeStateComplete
29.06.2025 14:45:42 : #1[Car_1:20]: change TeslaLogger state: Charge -> Start
Describe the bug
SOC is mostly (right now only ever tenth charge is somewhat under 1% tolerance the rest 1-2%) old at the end of charging, even though Telemetry is sending the correct SOC at the end of charging.
This leads to differences of up to 2%
(In this case 1,3% difference, but the charge before was also 62%)
This is also reproducible for DC charging. Comparing the charges with the invoices TeslaLogger reports 2-4kwh less charge, which is an error of 10-20% in my last charges. The correct amount was reported by the API, but the TeslaLogger doesn‘t save it, since the trigger for saving another hasn‘t been met.
To Reproduce
Charge AC or DC.
Expected behavior
In this case TeslaLogger should take the last SOC and create a new entry for it before closing the charge. Maybe in the future it could wait another minute for new, but since 2025.14 the SOC is transmitted quite reliable at the end of charging.
Teslalogger Type
PI5 with 1.63.6.8 and net8
