Skip to content

Optimise performance with new calculate_max_windows limiting charge/discharge windows to the best N
Compare
Choose a tag to compare
@springfall2008 springfall2008 released this 12 Oct 13:57
· 1025 commits to main since this release
v7.8.2
36565dc
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's Changed

In order to optimise performance a new setting calculate_max_windows has been added to HA which replaces the old max_windows setting in apps.yaml. The new default is set to 32, in this case the best 32 windows for charge and discharge will be picked, helping to reduce runtime. Users of slower machines can reduce this further to say 24 or 16 depending on the tariff.

  • The rate_high_threshold and rate_low_threshold can now both be set to 0 to disable the threshold and just let the best rates be picked based on the number set in calculate_max_windows. This is recommended for Agile but not recommended for tariffs such as Flux where you can set the threshold once manually.

  • Changed rate selection to pick the best N windows based on calculate_max_windows by @springfall2008 in #168

  • Fix bug in rate_low/high calculation and issue with calculate discharge on charge slots by @springfall2008 in #171

Full Changelog: v7.8.1...v7.8.2

Contributors

springfall2008
Assets 2
Loading