Repository navigation
Conversation
Updates the requirements on [pymdown-extensions](https://github.com/facelessuser/pymdown-extensions) to permit the latest version. - [Release notes](https://github.com/facelessuser/pymdown-extensions/releases) - [Commits](facelessuser/pymdown-extensions@12.1...12.2) --- updated-dependencies: - dependency-name: pymdown-extensions dependency-version: '12.2' dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
…s-gte-12.2 deps: update pymdown-extensions requirement from >=12.1 to >=12.2
…ted fleet dispatch Dispatch fidelity: the energy-counter baseline was refreshed on every optimizer run, while the SoC baseline (and the commanded-energy window from _previous_step_hours) only moved once per price step. With the mid-period correction run at half the price interval, the counters saw only the second half of each step and fidelity read ~0.5 on packs that followed their setpoint. Both baselines now refresh together in _refresh_step_baseline. Fleet efficiency curve: aggregate_curves assumed every pack carries a rating-proportional share of the fleet power, but BatteryDispatcher concentrates a balanced fleet's setpoint on one pack and only spills the overflow onto the others. The new aggregate_curves_concentrated follows the dispatcher (expectation over which pack wins), so part-load steps are no longer modelled on the low-power end of every pack's curve. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017A9r1k4XyrexChfxhCW5oS
…ithdraw raised Venus A curve Dispatcher: a balanced fleet still concentrates, but now also evaluates the proportional split from each pack's own curve and takes it when it loses less (near rated power two packs at half load beat one at full), with a 0.5 % hysteresis. aggregate_curves_concentrated takes the better of the two per point so the DP plans with what the dispatcher does. Calibration: commanded energy is integrated over every setpoint dispatched during the step (full runs, mid-period run, real-time ticks), so a power change inside a step is planned segment by segment, and steps that ran both ways are skipped as plan_not_executed. The same integral is the denominator of dispatch_fidelity. Docs: the "production-measured" Venus A curve (community x1.0492) is withdrawn — it rested on clamped charge corrections and inverted discharge samples; the analysis page now explains reading the product of the two corrections. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017A9r1k4XyrexChfxhCW5oS
The charge/discharge correction ratio has three indistinguishable causes (capacity, curve asymmetry, BMS SoC drift); recommend a full-discharge test instead of a derived capacity. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017A9r1k4XyrexChfxhCW5oS
feat: efficiency-aware multi-battery dispatch, fleet curve that matches it, and correct dispatch fidelity
- manifest.json: add categories (energy.solar_batteries, energy.energy_prices); the HACS action now warns when they are missing - hacs.json: set minimum Home Assistant version (2026.2.0, the oldest version CI tests) and drop render_readme, which the Marketplace ignores - README, docs and release notes: describe installing through Settings -> Marketplace, keep HACS steps for 2026.10 and older Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W6MpP97a1Yy1D9ENVHFKJy
The Marketplace renders the README on the project page next to its own install button. Wrap install instructions and badges in ha-marketplace:exclude markers so they only show on GitHub. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W6MpP97a1Yy1D9ENVHFKJy
chore: prepare for the Home Assistant 2026.11 Marketplace
github-actions
Bot
added
documentation
This branch was previously deployed
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
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.
Description
Brings
devintomain. Besides the Marketplace preparation from #208,devalready carried these commits that were not onmainyet:categories,hacs.jsonminimum HA version, Marketplace install docs, README exclude markers707f074docs: do not infer pack capacity from the calibration splitf2fb447feat: split for efficiency, score calibration per setpoint segment, withdraw raised Venus A curve4ccf686fix: measure dispatch fidelity over the full step and model concentrated fleet dispatch086b6eedeps: update pymdown-extensions requirement from >=12.1 to >=12.2Type of change
fix:Bug fix (patch version bump)feat:New feature (minor version bump)feat!:/BREAKING CHANGE:Breaking change (major version bump)chore:/docs:/ci:Maintenance or documentation (no version bump)Checklist
devtomainGenerated by Claude Code