mirror of
https://github.com/Akkudoktor-EOS/EOS.git
synced 2026-11-13 09:13:30 +01:00
Bobby NoelteandClaude Opus 5.5
faf37abfe7
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)
43 lines
1.6 KiB
Python
43 lines
1.6 KiB
Python
"""Reading device measurements for the device settings.
|
|
|
|
Measurement access is asynchronous (``DataSequence.key_to_value``), so it is
|
|
kept out of the device settings models and out of the parameter resolution.
|
|
``get_measured_value`` is the only place where device settings talk to the
|
|
measurement subsystem; the device specific modules (e.g. ``batterymeasurement``,
|
|
``invertermeasurement``) turn the measured values into operating points.
|
|
"""
|
|
|
|
from typing import Optional
|
|
|
|
from loguru import logger
|
|
|
|
from akkudoktoreos.utils.datetimeutil import DateTime, to_duration
|
|
|
|
# Maximum age of a measurement that is still taken as "current".
|
|
DEVICE_MEASUREMENT_MAX_AGE: str = "1 hour"
|
|
|
|
|
|
async def get_measured_value(key: str, target_datetime: DateTime) -> Optional[float]:
|
|
"""Return the measured value for a measurement key nearest to a datetime.
|
|
|
|
Args:
|
|
key: Measurement key.
|
|
target_datetime: Datetime the value is looked up for.
|
|
|
|
Returns:
|
|
The value nearest to target_datetime within DEVICE_MEASUREMENT_MAX_AGE,
|
|
or None if there is no such value or the measurement cannot be queried.
|
|
"""
|
|
try:
|
|
from akkudoktoreos.core.coreabc import get_measurement
|
|
|
|
value = await get_measurement().key_to_value(
|
|
key=key,
|
|
target_datetime=target_datetime,
|
|
time_window=to_duration(DEVICE_MEASUREMENT_MAX_AGE),
|
|
)
|
|
return None if value is None else float(value)
|
|
except Exception as exc: # a missing measurement falls back to the defaults
|
|
logger.warning(f"Device measurement '{key}' not available: {exc}")
|
|
return None
|