You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Charging plans are often selecting more expensive slots to charge when later cheaper slots are available including where negative slots are available and then selecting a slot where the cost is postive
Expected behaviour
Cheapest slots for charging are selected
Predbat version
v8.7.2
Environment details
GivEnergy Gen1 Inverter and 9.5k battery
NuC Home Assistant - all up to date (core, supervisor etc)
Octopus HACS latest
Screenshots
As can be seen from the screenshot at 21:35 the plan chose to charge, SoC in screen shot 1 was 53%
Screen shot 2 shows it charging SoC 60%
In both cases it can be seen that there are later cheaper slots, 00:00 (14:11p) and 02:30 (14:49p)
setting images
If applicable, add screenshots to help explain your problem. The most useful ones can be your battery chart, the Predbat HTML plan and your current settings in HA.
Describe the bug
Charging plans are often selecting more expensive slots to charge when later cheaper slots are available including where negative slots are available and then selecting a slot where the cost is postive
Expected behaviour
Cheapest slots for charging are selected
Predbat version
v8.7.2
Environment details
GivEnergy Gen1 Inverter and 9.5k battery
NuC Home Assistant - all up to date (core, supervisor etc)
Octopus HACS latest
Screenshots
As can be seen from the screenshot at 21:35 the plan chose to charge, SoC in screen shot 1 was 53%
Screen shot 2 shows it charging SoC 60%
In both cases it can be seen that there are later cheaper slots, 00:00 (14:11p) and 02:30 (14:49p)
setting images
If applicable, add screenshots to help explain your problem. The most useful ones can be your battery chart, the Predbat HTML plan and your current settings in HA.
Log file
predbat.log
predbatlog1.txt
The text was updated successfully, but these errors were encountered: