Optimizer Automatik-Modus: Sicherheits-Gate, Profile, Anzeige (wartet auf evcc PR 32881) - #3
Open
SolarPower2024 wants to merge 4 commits into
Open
SolarPower2024 wants to merge 4 commits into
SolarPower2024 wants to merge 4 commits into
Conversation
In automatic mode the optimizer sets the battery mode. The fork keeps its safety limits at execution, as the one hook after upstream decided the mode: - a charge request passes the same gate as the fork's own grid charging (running peak, circuit headroom, charge power setpoint) and becomes hold when refused; so the charge power entity no longer gets 0 W while the optimizer charges - hold gives way to normal while a peak has to be covered, and peak shaving then only discharges for the peak instead of the free value - with a missing or stale optimizer result the fork's grid charging applies as without the optimizer The soc-based grid charging does not switch the battery itself while the optimizer is in control, it is an optimizer input instead. The gate is extracted from the grid charge request unchanged. Without automatic mode nothing changes (contract test). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 75f9f3b)
A profile's discharge control is refused while the optimizer decides it; it is skipped with a debug note instead of failing the whole profile. The stored upstream value applies again once automatic mode is off. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 7bc1bdd)
- the load management overview marks loads the optimizer controls, and shows the battery as grid charging while an optimizer charge request passed the gate - battery page: with automatic mode the soc grid charging card says the optimizer plans the charging (start soc as floor, stop soc at the cheapest time) - profile editor: discharge control is skipped in automatic mode - advanced settings: "Netzlade-Ziel erreichen in" (grid charge window, 1-24 h, default 3) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 67c2481)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SolarPower2024
force-pushed
the
preview/optimizer-auto
branch
from
September 26, 2026 21:49
cfff56b to
1f02031
Compare
SolarPower2024
force-pushed
the
feature/optimizer
branch
from
September 26, 2026 21:49
090c8ba to
61745e0
Compare
SolarPower2024
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wartet auf evcc PR 32881 (Automatik-Modus des Optimizers, upstream noch offen). Basis ist
preview/optimizer-auto=load-peak-features+ evcc PR 32881 als ein Commit.Die Eingaben an den Optimizer und das einmalige Netzladen sind schon in
load-peak-features(v0.316.0-lm2). Hier steht nur noch der Automatik-Teil. Plan und Entscheidungen: Plan-Seite „Optimizer-Anbindung“.Was noch offen ist
Sicherheits-Gate im Automatik-Modus (ein Anschluss nach der evcc-Entscheidung):
Profile: Die Entladesteuerung wird im Automatik-Modus übersprungen, statt das ganze Profil scheitern zu lassen.
Oberfläche: „Optimizer“-Kennzeichen in der Lastmanagement-Übersicht, Hinweise auf der Batterieseite und im Profil-Dialog.
Unverändert: Ohne Automatik-Modus folgt die Batterie evcc (Vertragstest).
Getestet
Go und Frontend grün, Tests für das Gate (laden erlaubt/abgelehnt, halten bei Spitze, veraltetes Ergebnis, ohne Automatik unverändert). Nicht lokal testbar: Automatik-Modus mit echtem Sponsor-Token, das folgt bei der Abnahme auf deiner custom-Instanz.
Wenn evcc PR 32881 in einem Release ist
Release in
load-peak-featuresübernehmen, diesen Zweig darauf umsetzen, mergen, bauen.🤖 Generated with Claude Code