batpred icon indicating copy to clipboard operation
batpred copied to clipboard

timed_charge_current updates at odd times/spikes to max

Open chris-y opened this issue 1 year ago • 2 comments

Describe the bug I'm using:

  timed_charge_current:
    - input_number.solis_battery_charge_rate_predbat

The input_number.solis_battery_charge_rate_predbat is updating only during a charge. I have charge_control_immediate: False and switch.predbat_set_charge_low_power: true set so expect the next charging session to be set with appropriate current.

Additionally, the charge appears to be updating to a large value before the charge ends, which is causing the battery SOC to suddenly increase much higher than predbat planned for.

Expected behavior I expect the set current to update when the plan updates, to either the required current for the in-progress charge, or the predicted required current for the next upcoming charge if there isn't a charge in progress.

Predbat version

8.3.7

Environment details

See #1375

Screenshots This shows the massive increase at the end of a charge: image

It is then stuck at that level even though the next planned charge only needs to increase 40% (which by my calculations should be about 15A): image

The calibration chart shows a jump to that level wasn't as expected: image

The night before it behaved, as the current decided to drop down to 0 before the end.

Log file Nothing relevant in the log.

chris-y avatar Aug 27 '24 09:08 chris-y

More context.

Tonight the plan was to charge to a SOC which was lower than it was currently at:

Screenshot_20240831-003702~2.png

When I looked at about 00:40, the charge current was still set to 72A where it had been since this afternoon's free charge, and it was charging at 72A despite needing a reduction in charge.

Screenshot_20240831-003745-169.png

chris-y avatar Aug 30 '24 23:08 chris-y

Extreme example of it spiking up to max. Seems to do it before reducing to 0:

Screenshot_20240911-135737-047.png

chris-y avatar Sep 11 '24 12:09 chris-y

As this ticket is old I'm going to close it, please re-open if the issue is there on latest.

springfall2008 avatar Jan 01 '25 19:01 springfall2008