Battery charge planning for grid charging

[Elektron30]

Is your feature request related to a problem? Please describe.

evcc already supports grid charging for home batteries via the "Grid charging" feature, including a configurable price limit.

This is already very useful with dynamic electricity tariffs. However, the current logic is mainly price-threshold based. What is currently missing is a simple charge planning function for home batteries, similar to the existing charge planning for vehicles.

A typical use case would be:

• charge the home battery during cheap hours at night
• reach a defined target SoC by a defined time in the morning
• avoid charging the battery unnecessarily full, so there is still capacity left for PV surplus during the day

Describe the solution you'd like

I would like to see the existing home battery "Grid charging" feature extended with a simple battery charge plan.

Possible parameters:

• target SoC, e.g. 70%
• target time, e.g. 18:00
• optional maximum SoC for grid charging, e.g. 80%
• use the cheapest available time slots
• optionally respect an existing price limit
• optionally consider PV forecast / expected surplus

Example:

"Charge the home battery from the grid so that it reaches at least 70% by 18:00, using the cheapest available hours, but do not charge above 80%."

Describe alternatives you've considered

The current alternative is to use a fixed price limit for grid charging.

This works, but it does not guarantee that the battery reaches a desired SoC by a specific time. It can also lead to charging too early or too much, depending on the price curve and PV forecast.

External automation via Home Assistant or scripts would be possible, but since evcc already has grid charging and vehicle charge planning, it would be very useful to have this logic directly inside evcc.

Additional context

I know that not every battery or inverter supports active battery control. This feature would only apply to systems where evcc can already trigger grid charging today.

This request is therefore not about introducing full battery control for all systems, but about extending the existing "Grid charging" functionality with planning logic.

This could be especially useful for users with dynamic electricity tariffs and future time-variable grid fees.

[github-actions]

Thanks for the detailed proposal. I checked the current implementation: home battery grid charging (site.batteryGridChargeLimit in core/site.go / core/site_api.go, exposed via GetBatteryGridChargeLimit/SetBatteryGridChargeLimit in core/site/api.go) is indeed a simple price-threshold check (site.batteryGridChargeActive) with no concept of a target SoC, target time, or cheapest-slot planning — unlike vehicle charging, which already has a full plan-based planner (core/planner).

This matches what you describe: it's a genuine feature gap, not a bug. Implementing "reach X% SoC by time T using cheapest slots for the battery" would require adapting/reusing the vehicle planner logic for the home battery (including battery capacity/current SoC awareness, and optionally PV forecast), which is a non-trivial design and implementation effort touching the planner, site battery-control logic, and UI/config. I'll leave this open for maintainer/community discussion on scope and design rather than attempting an implementation here.

🤖 Generated with Claude Code

[werschi]

#24351

[Schimi1983]

erfüllt der Optimizer nicht die anforderungen?

[sfriesdorf]

erfüllt der Optimizer nicht die anforderungen?

Die automatische Berechnung ja, aber das ist bisher ja auch rein informativ und steuert die Batterie nicht aktiv. (btw: wann kommt das eigentlich - ich finde den Optimizer-Ergebnisse plausibler als die Victron VRM DESS Optimierung).

Hier wird darüber hinaus aber auch noch die manuelle Vorgabe von SoC Ständen zu bestimmten Uhrzeiten angefordert. Das könnte dennoch dann Input für den Optimizer sein, der dann die Steuerung auch übernimmt.

[Schimi1983]

erfüllt der Optimizer nicht die anforderungen?

Die automatische Berechnung ja, aber das ist bisher ja auch rein informativ und steuert die Batterie nicht aktiv. (btw: wann kommt das eigentlich - ich finde den Optimizer-Ergebnisse plausibler als die Victron VRM DESS Optimierung).

Hier wird darüber hinaus aber auch noch die manuelle Vorgabe von SoC Ständen zu bestimmten Uhrzeiten angefordert. Das könnte dennoch dann Input für den Optimizer sein, der dann die Steuerung auch übernimmt.

Ich habe für den iobroker (und einen Zendure Solarflow 2400 AC) ein Skript geschrieben (einfach googlen, sollte leicht zu finden sein), das sollte sich von der KI sehr gut auf andere systeme umbiegen lassen (viel wert auf vernünftige kommentierung gelegt).

vielleicht ist das eine idee?