Closed Philhews closed 14 hours ago
I think this is due to having "metric_min_improvement(-0.4 p)" meaning you will charge now even if it costs 0.4p extra.
Can you try setting it back to 0?
Don't think that's helped.
Log file from it too appdaemon.log
Having forced an idle and used some battery it seems it's happy to leave it on idle when below 100
Can you try changing 'metric_battery_value_scaling' to 1.0?
Also I have a new release coming that might help with this too..
Please try this one: https://github.com/springfall2008/batpred/releases/tag/v7.16.8
Battery value scaling at 1, metric min improvement set to 0 and updated to .8 seems to look more sensible as an ahead plan, will leave it and keep an eye on what it does during the day.
Having pulled in nord pool rates it went back to hold charge on an expensive slot. (10.10 plan). Changing metric min improvement to -0.2 removed the charges except on the current slot which is over 16p import. appdaemon.log
Initially the hold charge went away at 4pm,but at 5 past it calculated and put it back in. This results in anything over solar pulling at 26p which can't be the best plan? appdaemon.log
Closing this old ticket, please open a new one if you have an up to date question
Describe the bug After charging to 100 the current slot is always set to hold charge 100 even when the grid cost is higher than the export of excess solar (even to the point of the first expensive agile slot)
Expected behavior When grid import cost goes above export price the system should be idle to allow battery use and refill rather than forcing grid use at expensive rates.
Predbat version
7.16.7
Environment details
Screenshots
Log file appdaemon.log