Charginghistory: ChargeEnergy to high

[AikenPandora]

Describe the bug
The added charge in kwh is summarized for all charges without unplugging the charge cable. (Field charge_energy_added)

To Reproduce
Charge multiple times without disconnecting the cable. Car can sleep or teslalogger can have a restart in between, the error still occurs.

Expected behavior
charge_energy_added should only count the charge for one charge.

Teslalogger Type
Raspberry Pi4 / Docker / Selfmade

Additional context
After looking at the log, the charge_energy_added is probably created from Telemetry through ACChargingEnergyIn, which gives the value since plugging in the charge cable.

to note
DCChargingEnergyIn seems to give the amount which the car was able to get into it‘s battery, since it still returns a value while charging with AC corresponding to the value which was added to the battery according to the native Tesla App. (Further testing needs to be done). Here is the same error, so multiple charges are counted as one. If DCChargingEnergyIn is used for Supercharging the same error would occure there to.

[Adminius]

#1444

[bassmaster187]

should be fixed

[AikenPandora]

Works perfectly now. At least no problems in the last days.
Could ACChargingEnergy not be used for a efficiency? For me and my wallbox it seems to be quite accurate at least.

[bassmaster187]

Could ACChargingEnergy not be used for a efficiency?

We will check that

[Adminius]

I'm not happy about that, because in most cases it calculates about 98% efficiency, to high IMHO

But if: only if no WallBox was defined

[AikenPandora]

Probably since this is the efficiency from everything which went into the charge port and then into the vehicle battery. So which was lost inside the car and during the conversion process to DC. The car can‘t know how much energy is lost in the cable or wallbox itself.

[AikenPandora]

Sadly it still preexists.

Car was asleep for three days, then I woke it up and after a few minutes started the charge (misclicked first).

It seems that the car did get the DCChargingEnergyIn from the first charge before starting the charge. (That the value would be the same was expected since I didn’t disconnect the car). Still the teslalogger assumed that the DCChargingEnergyIn Value started at 0 for the respective charge.
That‘s why it got a high charged kwh.

There needs to be another way to detect the DCChargingEnergyIn Value before start, since this probably happened since there was atleast one restart in between the charging sessions.

(Log is send via PM)