Saving Sessions Export Price Incorrect

[thephoton]

Describe the bug
When an Octopus saving session is opted-into, PredBat is applying the export rate increase every plan recomputation (until it hits some limit, then resets).

Here, the export rate should be 56p + 15p export = 71p, but seeing 127p after 2 plans, 183p after 3 plans.

It doesn't seem to be changing the rest of the plan around the shown figure (aside from the total).

Expected behaviour
For the correct export rate to be shown.

Predbat version

8.11.4

Environment details

• Inverter and battery setup GivGateway + 2x AIOs + 2x Solax String Inverters
• Standard HAOS installer or Docker HAOS in Hyper-V
• Anything else?

Screenshots
Attached

Log file
Attached

Predbat debug yaml file
Attached

predbat debug.zip

Files starting with 2- are taken from when the first screenshot above was displaying, 3-: the second.

[gcoan]

that's super-weird, never seen anything like that. before and my own predbat doesn't experience such behaviour. Did it keep on incrementing indefinitely ?

[thephoton]

Did it keep on incrementing indefinitely ?

No, it reset at some point (highest I saw was almost 400p/slot which would've been nice!), but then carried on incrementing from 15p again.

Only adding in rate override in the apps.yaml file stopped it.

[gcoan]

well weird. Hopefully Trefor can spot something in the logfile because I've never heard of anyone else having this happen to them

[springfall2008]

What is in the octopus slot sensor attributes? I'm wondering if the saving session was there twice?

[thephoton]

Right now, not a lot...

I'll have a look next time there's a saving session scheduled (unless you can look at attributes historically?).

[gcoan]

there isn't an easy way to look at attributes historically even though they are stored in the HA database. Would need to start writing direct SQL queries to find the data and even then I don't know how it is formatted

[springfall2008]

Struggling to reproduce this, I will try to mock up the saving session data soon (I can see it in the Debug yaml but the source of the calculation isn't stored).

In the meantime I did a new release as the Octopus export URL being used creates a huge structure in memory which is likely the cause of some crashes.