Files
EOS/tests/testdata/eos_config_andreas_now.json
T
Bobby NoelteandClaude Opus 5.5 e255f987bf 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)
2026-11-11 22:08:18 +01:00

87 lines
2.0 KiB
JSON

{
"general": {
"version": "__ANY__",
"data_output_subpath": "output",
"latitude": 52.5,
"longitude": 13.4
},
"cache": {
"subpath": "cache"
},
"logging": {
"console_level": "INFO"
},
"devices": {
"batteries": {
"pv_akku": {
"device_id": "pv_akku",
"profile_adjustment": {
"nominal_capacity_wh": 30000
}
}
},
"electric_vehicles": {
"ev0": {
"device_id": "ev0",
"charge_rates": [
0.0,
0.375,
0.5,
0.625,
0.75,
0.875,
1.0
]
}
}
},
"measurement": {
"load_emr_keys": [
"Household"
]
},
"optimization": {
"genetic0": {
"horizon_hours": 48
}
},
"elecprice": {
"provider": "ElecPriceAkkudoktor"
},
"load": {
"loadakkudoktor": {
"loadakkudoktor_year_energy_kwh": 13000.0
}
},
"pvforecast": {
"provider": "PVForecastAkkudoktor",
"planes": [
{
"surface_tilt": 87.907,
"surface_azimuth": 175.0,
"userhorizon": [
28.0,
34.0,
32.0,
60.0
],
"peakpower": 13.11,
"loss": 18.6,
"trackingtype": 0,
"albedo": 0.25,
"inverter_paco": 15000,
"modules_per_string": 20,
"strings_per_inverter": 2
}
]
},
"weather": {
"provider": "WeatherImport"
},
"server": {
"host": "0.0.0.0",
"verbose": true,
"eosdash_host": "0.0.0.0"
}
}