Warn: Cannot find battery discharge curve

[MarkDarwin]

I have recently setup predbat and come across this error in the logs every few minutes:

2026-04-06 20:05:53.147264: Warn: Cannot find battery discharge curve (no full rate discharge curve found for battery to empty), one of the required settings for soc_kwh, discharge_rate, battery_power and predbat.status do not have history, check apps.yaml

2026-04-06 20:14:51.945912: Warn: Cannot find battery charge curve (no full rate charge curve found for battery to full), one of the required settings for soc_kwh, charge_rate, battery_power and predbat.status do not have history, check apps.yaml

I have gone through apps.yaml and found the entry related to the above entities then cross referenced with home assistant in the dev tools, and each one has a value, predbat.status being "Demand"

Edit in case it's relevant, I also see this error:

2026-04-06 20:20:01.272346: Warn: Found 1 periods of zero load with power data, filling using power integration

The inverter is a GivEnergy so I have configured the geserial then commented out geserial2 and the second line of each configuration pointing to the second inverter as I only have one.

Lastly, at 0200 this morning the battery was at 4% and by 0900 back to 100%, so I have performed a full empty/charge cycle.

Can someone help point out what I am missing please?

[gcoan]

Sorry for the delay in replying, I have been away and then taking a sabbatical away from github

The charge/discharge curves are explained in the documentation https://springfall2008.github.io/batpred/apps-yaml/#battery-chargedischarge-curves

It is most likely that predbat is giving this error because (as it explains in the documentation) predbat cannot find a full-rate or near full rate charge or discharge to full/empty in your entity history. The key thing is that the charge/discharge must be at near full rate. The inverter being in Eco mode and trickle charging off solar is not enough for predbat to be able to determine the curves

Not having the curves is not a major issue, it just improves the plan accuracy

[MarkDarwin]

No need to apologies at all. There was no expectation you'd be the one replying - hope you had a good break!

I like to optimise everything as much as possible so will endeavour to keep going. My last attempt was to add this but it didn't stop the logs:

   battery_charge_power_curve:
    91 : 0.91
    92 : 0.81
    93 : 0.71
    94 : 0.62
    95 : 0.52
    96 : 0.43
    97 : 0.33
    98 : 0.24
    99 : 0.24
    100 : 0.24
  #battery_discharge_power_curve:
    4 : 1.0

Like you mentioned, I'll try taking it out of eco mode and forcing a faster power cycle.
Thanks very much for releasing the app too. It gives me something new to tinker with :)

[gcoan]

It was great. Away for 2 weeks and then not touching github for a while afterwards has been very refreshing. 150 notifications though to work through ....

Looks like you have your curve not quite formatted right in the above apps.yaml, should be:

  battery_charge_power_curve:
    91 : 0.91
    92 : 0.81
    93 : 0.71
    94 : 0.62
    95 : 0.52
    96 : 0.43
    97 : 0.33
    98 : 0.24
    99 : 0.24
    100 : 0.24
  battery_discharge_power_curve:
    4 : 1.0

You need two spaces before the 'battery...: line (and not have one commented out, and then 4 spaces before the subsequent lines

[MarkDarwin]

Commenting the fix for anyone in the future:
Formatting was a github paste problem. Removing the comment fixed it

Thanks again for the help