2 Commits

Include renames

Author	SHA1	Message	Date
Bobby NoelteandClaude Opus 5.5	faf37abfe7	feat(devices): add inverter profiles ... An inverter profile describes the technical data of an inverter model: its nominal AC power, the DC→AC and AC→DC efficiency curves over the load fraction (AC power relative to the nominal power), the AC charge power limit of the model, whether that limit also limits PV charging, and an optional power derating over the ambient temperature. Curves are read linearly and clamped at their ends, so every lookup yields a value. The packaged profile generic-hybrid has typical hybrid inverter efficiencies, no nominal power (the inverter device has to provide it) and full power up to 45 degC. Inverter settings name their profile (inverter_profile, default generic-hybrid) and hold the differences of the unit in profile_adjustment: nominal_power_w (replaces the profile value, required for a generic profile), max_power_w and max_ac_charge_power_w (installation limits that can only lower; an AC charge limit of 0 disables AC charging). The effective parameters are resolved at the ambient temperature of the inverter, given by the new measurement key <device_id>-temperature-degc (45 degC without a fresh value); the power derating lowers the maximum power and the AC charge limit. Optimization parameters are always valid: the GENETIC and GENETIC0 parameter preparation resolve the inverter with resolve_current_operating_parameters_or_defaults, which never raises. An unusable profile gives the generic-hybrid profile, a missing nominal power the fallback of 10000 W, an inverter derated to zero power the parameters at 45 degC, and no usable profile at all the profile adjustment with constant efficiency; each is logged as error. The GENETIC inverter takes the AC→DC efficiency curve of the profile, solved exactly on each linear piece of the curve (about 2 % longer runs); GENETIC0 keeps constant efficiencies and no longer replaces the configured inverters with the demo inverter; a battery, electric vehicle or inverter that cannot be prepared is left out of the GENETIC0 run, never replaced by a demo device. Configurations migrate: max_power_w becomes profile_adjustment.nominal_power_w, max_ac_charge_power_w moves into the adjustment, an ac_to_dc_efficiency of 0 keeps AC charging disabled, and the efficiency fields are dropped with an error log, as for batteries, so the profile efficiencies apply. Home Assistant config paths follow. Additional changes - Move the curve algorithms of the battery profile into profilecurve, so battery and inverter profiles share them; the battery profile keeps its document format and classes. - Move ProfileBaseModel, the strict base of profile documents, into profilestore. - Serve inverter profiles through the profile REST API. Refuse to delete a profile that a configured device uses and that has no packaged profile to revert to (409). - Share the measurement access of the device settings in devicemeasurement. - Rename check_battery_profiles to check_device_profiles; the device profile check at configuration setup covers inverters, too. - Document inverter profiles, their configuration, defaults and sharing; regenerate the configuration and OpenAPI documentation. 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
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