Skip to content

feat: per-battery charge/discharge efficiency#99

Open
andig wants to merge 1 commit into
mainfrom
feat/per-battery-efficiency
Open

feat: per-battery charge/discharge efficiency#99
andig wants to merge 1 commit into
mainfrom
feat/per-battery-efficiency

Conversation

@andig

@andig andig commented Jul 22, 2026

Copy link
Copy Markdown
Member

Batteries can now carry their own eta_c/eta_d. The top-level eta_c/eta_d become defaults applied to batteries that omit them, so existing payloads behave identically.

  • BatteryConfig gains eta_c/eta_d (default 0.95)
  • Optimizer no longer takes global eta_c/eta_d; SOC constraints read them per battery
  • app.py resolves each battery's efficiency from its own value, falling back to the request-level default
  • OpenAPI schema + generated Go client updated

Refs evcc-io/evcc#32038

🤖 Generated with Claude Code

Batteries can now carry their own eta_c/eta_d, overriding the top-level
values which become defaults for batteries that omit them. The optimizer
reads efficiency from BatteryConfig instead of a single global pair.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant