feat(devices): add battery profiles

A battery profile describes a battery model: the charge and discharge limit
maps over temperature and SoC, the charge and discharge efficiency curves
over C-rate, the technical SoC bounds, the hard temperature cutoffs and,
for a model, its nominal capacity and power limits. EOS packages the
generic profile generic-lfp; users add their own profiles.

A battery or electric vehicle selects its profile by battery_profile and
describes how the installation differs from it in profile_adjustment
(capacity, power limits of the installation, periodic full charge). The
effective values are resolved from both at the measured operating point
(temperature, SoC, power) and shown as effective_* fields.

The GENETIC simulation uses the limits and efficiencies of the profile over
SoC, with precomputed tables as a fast path; GENETIC0 gets the values at the
operating point. Optimization parameters are always valid: a battery whose
profile is missing, unreadable or invalid uses the packaged generic-lfp
profile, and the former defaults only if that is not usable either; each is
logged as error, and an optimization run is never cancelled because of a
battery.

Additional changes
- Add a generic device profile store: user and packaged profiles, atomic
  saves, compiled profiles cached per file and checked again at most once a
  second, plain file names as profile names ('schema' is reserved). On
  Windows, a save or read that collides with the other is retried briefly.
- Add the REST API /v1/profile to list the profile kinds and to list, read
  (document and JSON schema), save and delete profiles.
- Check the hard temperature cutoffs on the exact temperature.
- Resolve inhibited charging or discharging to a power of 0, e.g. for a cold
  battery; give GENETIC0 its own discharge limit for that.
- Limit generic profiles without own power limits to the former 5000 W.
- Accept only the implemented units; current limits need the nominal
  voltage.
- Migrate legacy battery settings into the profile adjustment, keep the
  former charge power limit as discharge limit (also for a Home Assistant
  entity on it) and report dropped efficiencies as errors.
- Limit GENETIC battery discharge by the discharge power.
- Allow battery profile lookups while the configuration is created.
- Resolve a battery once per configuration dump.
- Package the bundled profiles, document battery profiles and regenerate
  the configuration and OpenAPI documentation.
- Ignore the report PDFs written by the visualization tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Assisted-by: Claude Code (claude-opus-5-5)
This commit is contained in:
Bobby Noelte
2026-11-11 22:08:18 +01:00
co-authored by Claude Opus 5.5
parent dd41e5d57c
commit e255f987bf
56 changed files with 11381 additions and 619 deletions
@@ -0,0 +1,88 @@
{
"schema_version": "1.0",
"battery_model": "Generic LFP home battery",
"chemistry": "LFP",
"nominal_voltage_v": null,
"technical_min_soc_percent": 0.0,
"technical_max_soc_percent": 100.0,
"units": {
"temperature": "degC",
"soc": "percent",
"limit": "C-rate"
},
"interpolation": "bilinear",
"out_of_range_behavior": "clamp_to_nearest",
"axes": {
"temperature_degC": [
-10.0, -7.5, -5.0, -2.5,
0.0, 2.5, 5.0, 7.5, 10.0, 12.5, 15.0,
20.0, 25.0, 35.0, 48.0, 55.0, 60.0
],
"soc_percent": [0, 40, 80, 100]
},
"charge_limit_crate": {
"description": "Max charge C-rate; rows = temperature, cols = SOC. Rows below 0 degC are zero because the datasheet curve ends at 0 degC with C-rate 0 and the charge hard cutoff is at 0 degC. Above 80 % SOC the limit tapers linearly to the value of the 100 % SOC column.",
"values": [
[0.0, 0.0, 0.0, 0.0],
[0.0, 0.0, 0.0, 0.0],
[0.0, 0.0, 0.0, 0.0],
[0.0, 0.0, 0.0, 0.0],
[0.0, 0.0, 0.0, 0.0],
[0.1, 0.1, 0.1, 0.1],
[0.1, 0.1, 0.1, 0.1],
[0.38, 0.38, 0.38, 0.38],
[0.38, 0.38, 0.38, 0.38],
[0.5, 0.5, 0.5, 0.5],
[0.5, 0.5, 0.5, 0.5],
[1.0, 1.0, 1.0, 0.75],
[1.0, 1.0, 1.0, 0.8],
[1.0, 1.0, 1.0, 0.8],
[0.8, 0.8, 0.8, 0.8],
[0.27, 0.27, 0.27, 0.27],
[0.0, 0.0, 0.0, 0.0]
]
},
"discharge_limit_crate": {
"description": "Generic continuous discharge C-rate for an LFP home battery. 0.5C in the normal range, derated near the low and high temperature ends. Peak discharge (typically around 1C) is deliberately not represented; only the continuous rating is stored, which is the safe value for controller-side power limiting.",
"values": [
[0.0, 0.0, 0.0, 0.0],
[0.1, 0.1, 0.1, 0.1],
[0.2, 0.2, 0.2, 0.2],
[0.3, 0.3, 0.3, 0.3],
[0.3, 0.3, 0.3, 0.3],
[0.3, 0.3, 0.3, 0.3],
[0.3, 0.3, 0.3, 0.3],
[0.5, 0.5, 0.5, 0.5],
[0.5, 0.5, 0.5, 0.5],
[0.5, 0.5, 0.5, 0.5],
[0.5, 0.5, 0.5, 0.5],
[0.5, 0.5, 0.5, 0.5],
[0.5, 0.5, 0.5, 0.5],
[0.5, 0.5, 0.5, 0.5],
[0.3, 0.3, 0.3, 0.3],
[0.2, 0.2, 0.2, 0.2],
[0.0, 0.0, 0.0, 0.0]
]
},
"charge_efficiency": {
"description": "Generic one-way DC charge efficiency of an LFP battery pack (cells and BMS) versus absolute C-rate. Losses grow with current (I^2 R), so efficiency falls slowly with C-rate. AC/DC conversion losses are not included; they belong to the inverter settings (ac_to_dc_efficiency).",
"c_rate": [0.05, 0.1, 0.25, 0.5, 0.75, 1.0],
"efficiency": [0.975, 0.975, 0.97, 0.96, 0.95, 0.94],
"interpolation": "linear",
"out_of_range_behavior": "clamp_to_nearest"
},
"discharge_efficiency": {
"description": "Generic one-way DC discharge efficiency of an LFP battery pack (cells and BMS) versus absolute C-rate. The curve ends at the 0.5C continuous discharge rating of this profile; higher C-rates are clamped to the last point. DC/AC conversion losses are not included; they belong to the inverter settings (dc_to_ac_efficiency).",
"c_rate": [0.05, 0.1, 0.25, 0.5],
"efficiency": [0.975, 0.975, 0.97, 0.96],
"interpolation": "linear",
"out_of_range_behavior": "clamp_to_nearest"
},
"hard_cutoffs": {
"charge_allowed_below_degC": 0.0,
"charge_allowed_above_degC": 60.0,
"discharge_allowed_below_degC": -10.0,
"discharge_allowed_above_degC": 60.0,
"description": "Charge is inhibited strictly below 0 degC and strictly above 60 degC. At exactly 0 degC and exactly 60 degC the charge map returns 0.0, so charging is effectively disabled there too. Discharge is inhibited strictly below -10 degC and strictly above 60 degC; the discharge map already reaches 0.0 at both ends, so the hard cutoff only governs whether the accessor returns None or 0.0."
}
}