fix(config): raise car charging rate/threshold max to 24kW for 3-phase chargers

[chalfontchubby]

Summary

Users with 3-phase home EV chargers have been reporting (Facebook group) that they can no longer set a car charging rate above 8.5kW / 11kW in Predbat.

car_charging_rate (and _1/_2/_3) and car_charging_threshold are input_number CONFIG_ITEMS with a declared max. That max was originally 8.5, then raised to 11 in #4312 to cover single-phase EU chargers (the Netherlands' single-phase max is 11kW) - but it's still too low for a 3-phase charger, which commonly runs up to ~22kW on a domestic supply (32A × 3 phases × 230V).

The reason this now actually bites people (rather than just being a slider limit they could type past): #4273 added enforcement in load_user_config() that clamps input_number config items to their declared min/max even when the value comes from an apps.yaml override, not just the GUI slider - closing a real garbage-in gap for other config items, but as a side effect it also silently clamps a legitimate high car_charging_rate set via apps.yaml down to the old max, capping the actual planned charge rate below what the hardware can really do.

Change

Raised max from 11 to 24 for:

• car_charging_rate, car_charging_rate_1, car_charging_rate_2, car_charging_rate_3
• car_charging_threshold (same power domain, subject to the identical clamp, raised for consistency)

24kW gives headroom above the common ~22kW 3-phase domestic ceiling.

Test plan

• unit_test.py --test integer_config (covers the clamp/type-consistency schema checks from fix(config): clamp input_number config items to their declared min/max #4273) - passes
• unit_test.py --quick - full suite passes
• pre-commit (ruff, black, cspell) clean
• Checked no test hardcodes the old max value, and the step=0.10 (float) / max=24 (int) pairing is exempt from the integer step/min/max type-consistency self-check (that check only applies when step is integer-valued)

🤖 Generated with Claude Code