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@11.0.2...12.1) --- updated-dependencies: - dependency-name: pymdown-extensions dependency-version: '12.1' dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
_planned_first_step_was_executed compared the optimizer's planned power against the committed power (after the commitment filter). When the commitment filter locked a different power level within a price period, the difference exceeded the 10% tolerance and every discharge step was classified as plan_not_executed, preventing any calibration samples. The power check is redundant at the fleet level: the direction check already filters out mode-resolution overrides (hybrid → zero_grid, manual), and the per-battery planned_delta already uses the committed setpoint from _last_battery_setpoints — so a power difference caused by the commitment filter does not invalidate the measurement. Remove the power comparison; only the direction (effective_mode) check is needed at the fleet level.
…p duration _previous_step_hours() was reading step_durations[0] from the last published optimizer run. When a mid-period correction run (e.g. at t=7.5 min into a 15-min price step) overwrites self.data, its first step covers only the remaining ~7.5 minutes. Calibration at the period boundary then computes planned_delta against 7.5 min instead of the full 15 min, pushing it below the step_too_small_to_measure threshold even though the SoC snapshot covers the complete price step. Fix: when the SoC snapshot age exceeds the data-derived step duration, use the snapshot age as the measurement window. The snapshot is refreshed once per price step, so its age equals the full step the measurement covers. The snapshot age is only preferred when larger than data_hours, so tests and first-startup cases without a snapshot timestamp are unaffected.
- Type schemas against probatio (HA 2026.10 replaced voluptuous); keep the voluptuous import at runtime for older releases. - Allow implicit re-export from homeassistant.components.binary_sensor so BinarySensorDeviceClass can still be imported from the package. - Device migration: on the single config entry device model move a device still under the main entry into its subentry instead of removing the main-entry link, which would delete the device. - Point .python-version at the Python 3.14 environment.
…s-gte-12.1 deps: update pymdown-extensions requirement from >=11.0.2 to >=12.1
github-actions
Bot
added
documentation
This branch was successfully 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
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.
No description provided.