Discrepancy between requested energy (0.6 kWh) and actual AC Charge Demand

[Popoboxxo]

I am currently setting up my system using evOpt with 15-minute timeslots (Tibber Pricing) and I am observing behavior regarding the charging power that I cannot fully explain. I would like to verify if my understanding of the logic is correct or if there is a bug/constraint I am missing.

My Setup: Max AC Charge: 2400 W
Interval: 15-minute Timeslots (Tibber)
Mode: evOpt

Observed Behavior: If 0.6 kWh of energy is requested for a specific 15-minute slot (see Screenshot 1), I would mathematically expect the following AC Charge Demand:

0.6 kWh * 4 = 2.4 kW (2400 W)

This corresponds to my configured Max AC Charge. However, while the full power is often predicted in the forecast and during the night, the system very rarely actually requests the full charging power during the live timeslot (see Screenshot 2). It appears that the actual demand often falls short of the forecast/calculation.

I noticed that using "EOS" (instead of evOpt/15-min logic) utilizes the maximum battery power much more effectively. However, I do not want to disable the 15-minute timeslots.

[Popoboxxo]

DEBUG
18.1.2026, 13:30:14
[BASE-CTRL] set AC charge demand for current hour 13:00 -> 591.33333 Wh - based on optimization max charge power 2400 W
INFO
18.1.2026, 13:30:14
[BASE-CTRL] AC charge demand changed to 591.33333 W
DEBUG
18.1.2026, 13:30:14
[OPTIMIZATION] Debug: current=13:30:14, next_quarter=13:45:00, quarter_start=13:44:59, time_until=885.4s
INFO
18.1.2026, 13:30:14
[OPTIMIZATION] Gap-fill run: start 13:35:14 (quarter-aligned run follows at 13:45:00)
INFO
18.1.2026, 13:30:14
[Main] Next optimization at 13:35:14 (based on average runtime of 0 seconds). Sleeping for 5 min 0 seconds
DEBUG
18.1.2026, 13:30:14
[Main] Overall state changed recently
INFO
18.1.2026, 13:30:14
[Main] Inverter mode set to MODE CHARGE FROM GRID with 1200 W (|||||)
DEBUG

In my understanding, I would expect MODE CHARGE FROM GRID with 2400 W because of the 15 min value '13:00 -> 591.33333 Wh'.

[ohAnd]

1. I've checked through the code (maybe still something wrong/ corner cases, after last refactoring in that section)

... some possibilities:

• max_charge_power_w -> you wrote 2400 W - not limited to 1200 W ?
• charging_curve_enabled -> true or false -> if true and your soc is > 50% - a % of max_charge_power_w will be used
• sensor_battery_temperature -> not set or setted -> if set and <15°C - a % of max_charge_power_w will be used
  means all 3 showing in this direction

2. point: eos/evopt - it could finally look like - I experienced not rare ... planning something for the night, but next morning not all planned slots where there - this is driven by the constantly updated output of the optimizer - e.g. load prediciton says more comsumption as it is in real later happend soc is then e.g. higher than originally expected and then "suddenly" this specific one charge is not needed anymore ... and so on

3. the log output at BASE-CTRL] AC charge demand changed to 591.33333 W - is misleading - it is Wh - will be fixed

[Popoboxxo]

Moin!

mal eben auf Deutsch :)

Wäre es möglich dass Du mir grob einen hinweis gibts, wo im Quellcode in etwa die Umrechung zwischen Opimize Energie-Anforderung und AC-Charge Demand steckt? Ich werd das Bauchgefühlt nicht los, dass die Konbinantion aus 15-Min Time-Slot, und Max AC Charge nicht ganz passt.

ev-Opt gibt die Engergie-Mengen-Empfehlung 0.6 kwh vor, was in einem optimum in 15min die Energiemnenge wäre bei einer Ladeleistung von 2400 watt. aber halt im 15min slot.
Dyn Max Charge Power mit 2400 passt top (bei EOS Backend läuft das auch super bis MaxAC). Aber die EV-Op kommt quasi nie auf 2400W, sondern nur 1200W. (Einmal war ich bei 2400W - kann aber auch ein manueller Eingriff von mir gewesen sein :D)

Leihenhafte Erklärung -> Entweder muss ich auf DC-Charge Demant schauen oder die Umrechnung von Demand aus EV-Opt auf den 15-Min TimeFrame bzg. Ladeleistung in W passt nicht.

(Den "Treppenstufen-Teil" bitte nicht beachten, da habe ich wohl ein Abnpassungfehler in meinem Mapping auf den Zendure-Manager)

[Popoboxxo]

Anbei nochmal das Verhalten. Angofordert 0.6kwh -> mit 0.6kw in 15 min nicht zu schaffen :) daher hätte ich 2,4 kw erwartet.

[Popoboxxo]

@ohAnd danke für das verbesserte Logging!

2026-02-28 13:51:07 INFO [CHARGE_DEMAND] Power capped by battery max: calculated=1783.00 W, capped=1200.00 W, bat_max=1200.00 W

Wird irgendwo die Config nicht durchpropagiert, oder hab ich och irgendwo im Cache etwas hängen?

2026-02-28 13:51:05 INFO [OPTIMIZATION] Quarter-hour aligned run: start 13:59:59, finish at 14:00:00 2026-02-28 13:51:05 INFO [Main] Next optimization at 13:59:59 (based on average runtime of 0 seconds). Sleeping for 8 min 54 seconds 2026-02-28 13:51:06 INFO [CHARGE_DEMAND] Energy→Power conversion: 264.00 Wh / 534.00s (0.1483h) = 1780.00 W 2026-02-28 13:51:06 INFO [CHARGE_DEMAND] Power capped by battery max: calculated=1780.00 W, capped=0.00 W, bat_max=0.00 W 2026-02-28 13:51:06 INFO [CHARGE_DEMAND] Final AC charge power returned: 0.00 W 2026-02-28 13:51:06 INFO [CHARGE_DEMAND] MQTT publish: control/eos_ac_charge_demand = 0.00 W 2026-02-28 13:51:06 INFO [CHARGE_DEMAND] Energy→Power conversion: 264.00 Wh / 534.00s (0.1483h) = 1780.00 W 2026-02-28 13:51:06 INFO [CHARGE_DEMAND] Power capped by battery max: calculated=1780.00 W, capped=0.00 W, bat_max=0.00 W 2026-02-28 13:51:06 INFO [CHARGE_DEMAND] Final AC charge power returned: 0.00 W 2026-02-28 13:51:06 DEBUG [BASE-CTRL] set current battery charge max to 1200 2026-02-28 13:51:06 INFO [BASE-CTRL] Battery charge max (W) changed to 1200.00 2026-02-28 13:51:06 DEBUG [Main] Overall state changed recently 2026-02-28 13:51:06 INFO [Main] Inverter mode set to MODE CHARGE FROM GRID with 0 W (_____|||||_____) 2026-02-28 13:51:07 INFO [CHARGE_DEMAND] Energy→Power conversion: 264.00 Wh / 533.00s (0.1481h) = 1783.00 W 2026-02-28 13:51:07 INFO [CHARGE_DEMAND] Power capped by battery max: calculated=1783.00 W, capped=1200.00 W, bat_max=1200.00 W 2026-02-28 13:51:07 INFO [CHARGE_DEMAND] Final AC charge power returned: 1200.00 W 2026-02-28 13:51:07 INFO [CHARGE_DEMAND] MQTT publish: control/eos_ac_charge_demand = 1200.00 W 2026-02-28 13:51:07 INFO [CHARGE_DEMAND] Energy→Power conversion: 264.00 Wh / 533.00s (0.1481h) = 1783.00 W 2026-02-28 13:51:07 INFO [CHARGE_DEMAND] Power capped by battery max: calculated=1783.00 W, capped=1200.00 W, bat_max=1200.00 W 2026-02-28 13:51:07 INFO [CHARGE_DEMAND] Final AC charge power returned: 1200.00 W