Octopus IOG Planned Slots not showing in Plan

[steve7171]

Need some help to check understanding and if my understanding is correct, how to debug this...

I've got the following line in my app.yaml which I understood would take the planned IOG charging slots from HA and include them in the Predbat Plan but these cheap rate slots never show up in the plan until charging actually starts. Is this how it should be?
octopus_intelligent_slot: 're:(binary_sensor.octopus_energy([0-9a-z_]+|)_intelligent_dispatching)'
This regex should match my HA sensor:
binary_sensor.octopus_energy_00000000_000X_X000_XXXX_0000000XXXXX_intelligent_dispatching
(XXX are hex characters which I've removed as I'm not sure if they're security sensitive)

This lack of advanced notice of the cheap slots causes Predbat to not export when it could if it knew a cheap slot was coming.

Have I misunderstood how this is supposed to work?
If my understanding is correct, how should I debug this?

[gcoan]

I don't have an EV so my feedback is based on my understanding of how Predbat now handles IOG slots ...

In essence since Octopus can and does change IOG slots (during the day), Predbat will now treat these as "unconfirmed" until the slot starts AND the EV starts charging. Then once the EV is charging it will plan them in and start charging the battery etc

Maybe this needs to be made clearer in the documentation but this is the correct behaviour you are seeing.

Problem with the old approach which sounds like you were expecting to happen:

• Octopus plugs an IOG bonus slot
• Predbat treats the future slot as being confirmed cheap rate charging, discharging the battery etc to take advantage of it
• Octopus then withdraws/reschedules the slot before it starts

End result battery depleted unnecessarily

Or if the slot starts and the EV doesn't start charging then Octopus will charge you full rate for the slot. Again this isn't desireable