Describe the bug
When I trigger bump charging, it shows the entire predicted charging slot as low rate.
Expected behaviour
I expected this to be show as high rate (as it is charged by Octopus at the "unintelligent" high rate)
Predbat version
v8.35.1
Environment details
- Inverter and battery setup: Fox Cloud
- Standard HAOS installer or Docker: Docker
Screenshots
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
Can see from the log file that the "BOOST" dispatch source is identified as low rate:
{'start': '2026-03-30T08:55:10+01:00', 'end': '2026-03-31T02:37:05+01:00', 'charge_in_kwh': -36.86620694444445, 'source': 'BOOST'}]]
...
2026-03-30 09:05:03.556027: Octopus: Intelligent slot at 03-30 08:30:00-03-31 03:00:00, assumed price 7.0, amount 36.87, kWh location , source BOOST, octopus_slot_low_rate True
I tried updating the relevant lines octopus.py file to match on the string "BOOST" as well as "bump-charge", and that seemed to make it work OK for me.
I'm not sure if "bump-charge" is even used elsewhere or if the dispatch has changed.
if octopus_slot_low_rate and source != "bump-charge" and source != "BOOST":
...
if octopus_slot_low_rate and source != "bump-charge" and source != "BOOST":
...
if octopus_slot_low_rate and source != "bump-charge" and source != "BOOST":
...
if source != "bump-charge" and source != "BOOST" and (not location or location == "AT_HOME"):
...
Describe the bug
When I trigger bump charging, it shows the entire predicted charging slot as low rate.
Expected behaviour
I expected this to be show as high rate (as it is charged by Octopus at the "unintelligent" high rate)
Predbat version
v8.35.1
Environment details
Screenshots
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
Can see from the log file that the "BOOST" dispatch source is identified as low rate:
I tried updating the relevant lines octopus.py file to match on the string "BOOST" as well as "bump-charge", and that seemed to make it work OK for me.
I'm not sure if "bump-charge" is even used elsewhere or if the dispatch has changed.