Skip to content

Updated documentation to clarify battery curve calculation in read only mode behaviour (#5547) #5555

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
springfall2008 merged 4 commits into from
Oct 16, 2026
Merged

Updated documentation to clarify battery curve calculation in read only mode behaviour (#5547) #5555

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5285e95
Update FAQ with note on Read Only mode for Battery Curves
ahdinko Oct 15, 2026
0eda7c4
Clarify battery curve calculation limitations
ahdinko Oct 15, 2026
182653d
Correct typo in battery charge curve note
ahdinko Oct 15, 2026
b2ba941
Fix capitalization in apps-yaml.md documentation
ahdinko Oct 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/apps-yaml.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2577,7 +2577,7 @@ Note that the charge/discharge curves *only* affect the accuracy of the charging
Predbat will still instruct the inverter to charge/discharge at full rate regardless of the charging curve so not having these curves only has an impact on plan accuracy.

If you know the battery charge or discharge curves (e.g. manufacturer info or your own testing) then you can manually configure this in `apps.yaml`,
or Predbat can calculate the curves based on historical inverter charging/discharging data in Home Assistant.
or Predbat can calculate the curves based on historical inverter charging/discharging data in Home Assistant. Note the battery curves cannot be calculated if Predbat is in Read Only mode.

If the battery has not recently been fully charged or fully discharged *at a charge/discharge rate that is at least 95% of your maximum charge/discharge rate* then Predbat will not be able to calculate the curves and you'll get a warning in the logfile.
For some inverters you may not be able to practically charge/discharge at full rates so you'll keep getting the curve warning every time Predbat starts. Simply create dummy curves to stop this warning, e.g:
Expand Down
2 changes: 2 additions & 0 deletions docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -375,6 +375,8 @@ It's recommended that you don't include the Solcast forecast within your GivEner
If you get the message "Info: Cannot find battery charge curve, one of the required settings for soc_kw, battery_power and charge_rate are missing from apps.yaml" in the logfile
then Predbat is trying to create a battery charge curve but does not have access to the required history information in Home Assistant.

**Note:** The battery charge curve cannot be calculated if Predbat is in Read Only mode. Even though required history may be available, the log message will continue to appear until Predbat is out of read only mode and has calculated the curve.

[Creating the battery charge curve](apps-yaml.md#battery-chargedischarge-curves) is described in the `apps.yaml` document.

One cause of the above message appearing in the logfile is that you are controlling a GivEnergy inverter in REST mode
Expand Down
Loading