springfall2008
Plan is showing incorrect Octopus Agile rates (Predbat Octopus Direct)
Describe the bug Switched from Octopus Flux to Agile Import/Outgoing Octopus a few days ago. Every day since, the Predbat plan is showing an incorrect Octopus Agile import rate of 0.00 for the 23:00 & 23:30 slots. This is causing the plan to implement a one hour charge slot at these times thereby possibly skewing what might have happened earlier in the day. Obviously, as a result of this the cost figures are inaccurate too.
Expected behaviour The plan should show the correct rate for these time slots.
Predbat version
8.27.4 using the direct connection to Octopus
Environment details
- LuxPower
- Standard HAOS installer Core 2025.11.0
- OS 16.3
Log file Nothing in the log file Predbat debug yaml file
The incorrect 0:00 rates as shown in the plan.
Some rates however are shown in the Compare feature (although they are not what they should be according to the Octopus Agile website, even though the rest of the day is correct). Running 'compare now' then shows 0:00 rates for the 23:00 and 23:30 time slots.
Reverting to an earlier version (8.26.4) fixes the issue of the 0:00 slots but the figures shown are again not what they should be.
Interesting note: It is now just past 4PM, the Octopus rates for tomorrow have been released and the 0:00 rate 23:00 and 23:30 slots have now been filled with the correct rates.
This last image shows a plan generated post 4PM with all of the rates shown and in accord with the Octopus Agile website.
it might be worth seeing if you get the same problem with the Octopus integration? I suspect you won't and its a bug with Predbat Octopus direct, but would be useful to confirm
I can confirm that the bug is only with the direct connection. I swapped over to the Octopus integration and all the rates are consistent with the Agile website for my region. (The 23:00 & 23:30 slots were at 0:00 again this morning, having been correct after 4PM yesterday. I’m sorry but I’ve no idea what time they went wrong again. Presumably some time after midnight.)
I don't know if this is relevant. I see that any rates after the 22:30 slot today are followed by a ? (obviously because the real rates haven't been released yet) and these ? rates are the same as the equivalent slot 24 hours earlier. Could the issue be somehow related to the data that is used for the Compare feature, given that that runs for 24 hours from midnight?
I don't know if this is relevant. I see that any rates after the 22:30 slot today are followed by a ? (obviously because the real rates haven't been released yet) and these ? rates are the same as the equivalent slot 24 hours earlier. Could the issue be somehow related to the data that is used for the Compare feature, given that that runs for 24 hours from midnight?
No that's not relevant, its normal predbat behaviour.
If any rates that the plan needs are not available then predbat repeats the prior day rates and adds a question mark
You can get a more accurate prediction of what the future rates from 10pm will be by using the norddata prediction that's available from about 10am. Setup details in the apps.yaml documentation