After an agile charging period predbat is not clearing the charging time from the givtcp charge slots, notably slot 1. Hence if the charge times are different next day, as they often are on agile, you get another charge at a time not in the plan and in addition to that days plan.. You essentially get the previous days charging slot for as many days until predbat happens to overwrite it with a new time in a later plan. I spotted this after getting 6am charges unexpectedly when no such was in the predbat plan. But such a slot had occured a couple of days earlier.
Expected behaviour
After an agile charge period predbat should clear the charge slot times as it can't rely on over writes the following day.
Predbat version
8.40.5
Environment details
- Givenergy gen 3
- Standard HAOS install
- Anything else?
Log file
Can you capture a log file from the time of the issue, debug mode is not normally required.
You can download the logfile from the WebUI on the Dash tab select predbat.log
Predbat debug yaml file
This is important for any plan related issues.
Once you have captured the issue go to the Web UI, in the Dash tab click on predbat_debug.yaml and wait 30 seconds for it to download. Select 'keep' if your Web Browser thinks the file is dangerous.
Rename the download file to predbat_debug.yaml.txt and upload it to GitHub. This will allow your plan to be reproduced and also stores all your settings for review.
After an agile charging period predbat is not clearing the charging time from the givtcp charge slots, notably slot 1. Hence if the charge times are different next day, as they often are on agile, you get another charge at a time not in the plan and in addition to that days plan.. You essentially get the previous days charging slot for as many days until predbat happens to overwrite it with a new time in a later plan. I spotted this after getting 6am charges unexpectedly when no such was in the predbat plan. But such a slot had occured a couple of days earlier.
Expected behaviour
After an agile charge period predbat should clear the charge slot times as it can't rely on over writes the following day.
Predbat version
8.40.5
Environment details
Log file
Can you capture a log file from the time of the issue, debug mode is not normally required.
You can download the logfile from the WebUI on the Dash tab select predbat.log
Predbat debug yaml file
This is important for any plan related issues.
Once you have captured the issue go to the Web UI, in the Dash tab click on predbat_debug.yaml and wait 30 seconds for it to download. Select 'keep' if your Web Browser thinks the file is dangerous.
Rename the download file to predbat_debug.yaml.txt and upload it to GitHub. This will allow your plan to be reproduced and also stores all your settings for review.