By default, the algorithm chooses only to charge the amount of kWh needed in the "high price" hours. This are the hours current_price + min_price_diff . This can vary between 500Wh up to multiple kWh.
This is the optimal price point.
Some users like to fillup the battery to the maximum in such an "low price" event.
There should be a config option, to make batcontrol to fill up to the configured charge limit, no matter what the consumption prediction decides.
By default, the algorithm chooses only to charge the amount of kWh needed in the "high price" hours. This are the hours current_price + min_price_diff . This can vary between 500Wh up to multiple kWh.
This is the optimal price point.
Some users like to fillup the battery to the maximum in such an "low price" event.
There should be a config option, to make batcontrol to fill up to the configured charge limit, no matter what the consumption prediction decides.