Skip to content

Releases: springfall2008/batpred

Reduce writes in low power mode, solar charging fix

20 Jan 08:57
1e24d6c
Compare
Choose a tag to compare

What's Changed

Improvements

Try to reduce register writes in low power mode but sticking with current charge rate if a change is not required
Minor fix related to modelling of solar charging

  • Fix related to solar charging, change to try to reduce register writes in low power mode charge by @springfall2008 in #1882

Documentation

Full Changelog: v8.11.1...v8.11.2

Optimiser fixes, tweak levelling order and fix for charging with solar

18 Jan 16:02
1747a88
Compare
Choose a tag to compare

What's Changed

Changes made to the optimiser to catch some corner cases:

  • Optimise levels from the end of the plan first
  • When charging with solar that won't provide the full rate charge account of the additional export of that solar.

Full Changelog: v8.11.0...v8.11.1

Max charge rate temperature curve

12 Jan 17:43
d19b610
Compare
Choose a tag to compare

What's Changed

Features

This feature allows you to model temperature dependant charging and discharging of the battery. You can set a charge and a discharge maximum rate scaling based on temperature and then using a temperature sensor predict future battery temperatures. Low power mode will also account for this in its calculation.

To try this feature with GivTCP (Givenergy) can you update your apps.yaml to both give battery temperature and also define charge curve. I don't know what the correct charge or discharge curves are for particular makes and models but this charge curve came from some comments made by GivEnergy.

  battery_temperature:
   - sensor.givtcp_battery_stack_1_bms_temperature
   - sensor.givtcp2_battery_stack_1_bms_temperature

  # Battery temperature charge adjustment curve
  # Specific in C which is a multiple of the battery capacity
  # e.g. 0.33 C is 33% of the battery capacity
  # values unspecified will be assumed to be 1.0 hence rate is capped by max charge rate
  battery_temperature_history: sensor.givtcp_battery_stack_1_bms_temperature
  battery_temperature_charge_curve:
    19: 0.33
    18: 0.33
    17: 0.33
    16: 0.33
    15: 0.33
    14: 0.33
    13: 0.33
    12: 0.33
    11: 0.33
    10: 0.25
    9: 0.25
    8: 0.25
    7: 0.25
    6: 0.25
    5: 0.25
    4: 0.25
    3: 0.25
    2: 0.25
    1: 0.15
    0: 0.00

Bug fixes

Full Changelog: v8.10.2...v8.11.0

Bug fixes, repeat service name, Service API for car hold

11 Jan 15:20
f9db1d8
Compare
Choose a tag to compare

What's Changed

The documented name repeat did not match the code.

The service API was not called when holding for car or iboost, this is now fixed.

Full Changelog: v8.10.1...v8.10.2

Fix optimiser bug, added service repeat option

08 Jan 20:12
683661f
Compare
Choose a tag to compare

What's Changed

Bug fixes

Sometimes the plan goes a bit crazy charging when you have 'calculate_second_pass' enabled - now fixed.

  • Inverter test cases updated, minor fix for discharge start/end time, doc update by @springfall2008 in #1851

Minor fixes to start/end time discovered from existing inverter settings, will only impact 'base' plan.

You can now set 'repeat:True' on a service call if you want that service to be repeated every run e.g. charge_start_service. Useful if your inverter stops after a while.

Full Changelog: v8.10.0...v8.10.1

Optimiser improvements, bug fixes

05 Jan 14:20
d52bfda
Compare
Choose a tag to compare

What's Changed

Features

Optimiser changes by @springfall2008 in #1838

  • Restored the selection of charge SOC % on 30 minute charge slots
  • Added new more aggressive logic to combine charge slots after optimisation, thus enabling low power mode without 'combine_charge' enabled.
  • Adjusted weighting around freeze/charge/no-charge slightly

Octopus ready time sensor change by @springfall2008 in #1839

Supported the new select. octopus ready sensor

Bug fixes

Don't enable low power in monitor mode by @springfall2008 in #1841

Previous in monitor mode Predbat was predicting low power charging, which wasn't possible.

Bug in prediction not resetting charge rate by @springfall2008 in #1845

There was a bug where if the charge rate was set to 0 the plan produced was totally messed up.

Unit testing

Extra unit tests by @springfall2008 in #1842

Test updates by @springfall2008 in #1847

Full Changelog: v8.9.3...v8.10.0

Fix charge freeze service being called for charges

02 Jan 07:47
d3bbc4b
Compare
Choose a tag to compare

What's Changed

Full Changelog: v8.9.2...v8.9.3

Fix crash with cost_car_per_kwh

01 Jan 19:45
587ac38
Compare
Choose a tag to compare

What's Changed

Full Changelog: v8.9.1...v8.9.2

Bug fix min/max selection in optimiser

01 Jan 18:56
167d2e9
Compare
Choose a tag to compare

What's Changed

In some cases the maximum SOC was not at the end of a charge slot, changed the search to include all periods in-between.

Full Changelog: v8.9.0...v8.9.1

Show XLoad per load source, Predheat hysteresis off, service API

01 Jan 11:12
de3ee9b
Compare
Choose a tag to compare

What's Changed

Improvements

The service API is called after all register changes to help with some inverters that use them.

Added a hysteresis off setting for Predheat.

In plan_debug mode you can now see each load source.

Bug fixes

Setting min_soc left around useless charge slots, now they are clipped.

Monitor mode would reset reserve/charge/discharge rates - this is now fixed.

Full Changelog: v8.8.20...v8.9.0