Predbat status doesn't match plan

[brickatius]

Describe the bug
The plan is not showing the correct state for the current Predbat status.

Expected behaviour
The plan should reflect the actual Predbat status at the rime.

Predbat version

8.30.4

As well as Freeze charging it was also showing 'Charging' when Predbat status was actually Hold charging.

Predbat debug yaml file

predbat_debug.yaml

[gcoan]

can you add the logfile please Richard, and a screen shot of how predbat.status has changed (or not) aligned with the log activity

[brickatius]

predbat-2.log.txt

[springfall2008]

Fix Implemented

This issue has been fixed in PR #3115.

Root Cause

The status/plan mismatch was caused by floating point rounding differences:

• charge_limit_best[0] was rounded to 0.5 kWh (via dp2())
• reserve was 0.51 kWh (via dp3())
• Direct equality comparison 0.5 == 0.51 failed

Solution

Created is_freeze_charge() helper that compares percentages instead:

• Both 0.5 and 0.51 kWh equal 5% of 10.149 kWh battery
• Percentage comparison succeeds where kWh comparison failed

This ensures consistent freeze charge detection across status display and HTML plan generation.

Testing

Added unit test charge_freeze_rounding_issue_3107 with the exact values from your debug yaml to prevent regression.