Conversation
Bumps [github/issue-labeler](https://github.com/github/issue-labeler) from 3.4 to 3.5. - [Release notes](https://github.com/github/issue-labeler/releases) - [Commits](github/issue-labeler@v3.4...v3.5) --- updated-dependencies: - dependency-name: github/issue-labeler dependency-version: '3.5' dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…/issue-labeler-3.5 ci: bump github/issue-labeler from 3.4 to 3.5
Add a production-measured efficiency curve for the Marstek Venus A derived from HA recorder data on two units (Sept 2026): SoC-based calibration showed efficiency_factor > 1.0 on both batteries, calibration correction factor capped at 1.0492. Community curve scaled by ×1.0492 gives one-way efficiency of 0.954 at the 500–800 W plateau (RTE 91 %) vs 0.909 (RTE 83 %) in the community curve. Also add docs/efficiency-analysis-from-db.md explaining the two-pronged methodology: hourly SQL queries against the statistics table for dispatch fidelity, and Python parsing of .storage calibration files for the SoC-based efficiency factor — so the analysis can be repeated in future.
docs: Venus A production-measured efficiency curve + DB analysis methodology
…ion moves When the efficiency correction is at CALIBRATION_APPLY_MAX (1.05) every new sample is added to the rolling window but record() returns moved=False, so async_save() is never called. The file on disk then keeps the old raw_ratio schema indefinitely and is re-migrated on every HA restart, resetting to correction=1.05 each time. The sensor appears permanently stuck. Fix: save after every successful sample (CALIBRATION_SAMPLED), not only when the correction shifts by more than CALIBRATION_SIGNIFICANT_CHANGE. This keeps the file in the current efficiency_factor schema and the sample count current, so a reset is not needed to unblock the sensor.
fix: always persist calibration after sampling, not only when correction moves
github-actions
Bot
added
the
documentation
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.
Description
Type 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
feat:,fix:,chore:, etc.)devbranch (notmain, unless this is a hotfix)Screenshots / Logs (optional)