7 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
4 people	8224c64654	feat: integrate device and runtime configuration foundation on main (#1328) ... * feat: adapt configuration for multi optimization algorithms Decouple configuration from optimization algorithm parameters. Add to_[algorithm]_param() methods to the configuration that derive optimization algorithm specific parameters from the configuration. Add x-scope tags to the configuration options that describe for which specific algorithms the configuration option is for. The whole device settings are restructured. There are now general settings for the device classes with the afore mentioned to_[algorithm]_param() methods. The general device settings got their own directory `devices/settings`. By this the parameter class also does not have to be a pydantic model which can be used for future optimization/ simulations speed up. Also the parameter class for a device is now part of the device module. This better decouples and also is the natural place for parameters of a device. Besides this feature there are also fixes and improvements: * feat: extend home appliance time window settings and simulation Home appliance can now be configured for multiple runs with per-cycle allowed time windows. The number of remaining cycles to plan is determined at runtime by reading the ``cycles_completed_measurement_key`` from the measurement store. * feat: specialiced CycleTimeWindowSequence for time window sequences Sequence of time windows associated to cycles. This model specializes ``ValueTimeWindowSequence`` so that the ``value`` field of each ``ValueTimeWindow`` encodes the **cycle index** (0-based integer) the window belongs to. Typical use: an appliance that must run ``n`` times per day, each run constrained to a distinct time window. Assign ``value=0`` to windows for the first cycle, ``value=1`` for the second, and so on. Multiple windows may share the same cycle index (their allowed regions are unioned). Windows with ``value=None`` are silently ignored by all cycle-aware methods. * fix: Make test_configmigrate also regard the _ANY_SENTENIEL in key values * chore: Make devices configurations a map instead of a list This makes config paths stable regardless of declaration order and lets each device settings class build its own config path from ``self.device_id`` without needing an external index. Tests are adapted likewise. Devices configurations are automatically migrated from lists to maps. * chore: rename levelized_cost_of_storage_kwh to levelized_cost_of_storage_amt kwh This better fits in the naming scheme and also makes clear the costs are money. Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com> * fix: runtime config update ignored by config file Runtime settings were handed back to pydantic-settings as init settings, which rank below the config file and the environment. Any key already present in EOS.config.json or in the environment silently discarded the update, so a bulk PUT /v1/config returned 200 without applying anything, while the granular PUT /v1/config/{path} endpoint kept working. Add a dedicated runtime settings source ranked directly below the command line arguments and record granular updates there as well, so both endpoints share one store that survives re-evaluation of the settings sources. Environment variables keep precedence over the config file for all keys that were not set at runtime. Also repairs revert_settings() and update(), which passed their data through the same init settings. Closes #1303 * fix: env vars ignored on first config build ConfigEOS.__init__ passed self as first positional argument to _setup, which forwards it to pydantic_settings.BaseSettings.__init__. Its first positional parameter is _case_sensitive, so the environment source matched the upper case variable names against the lower case field names and returned nothing. Environment settings only took effect after the next configuration setup. * docs: changelog for config priority fixes * fix(config): preserve device identities and storage costs during migration * fix(devices): preserve charge-rate typing and public import compatibility * ruff format fix * fix(config): satisfy typed device conversion and migration contracts * docs(config): refresh validated configuration prerequisite schemas --------- Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com> Co-authored-by: Bobby Noelte <b0661n0e17e@gmail.com> Co-authored-by: r0b2g1t <r0b2g1t@users.noreply.github.com>	2026-09-17 17:51:40 +02:00
Bobby NoelteandGitHub	6093d8d348	chore: improve error msg on home assistant add-on port config (#1186) ... When running as a Home Assistant add-on the ports shall not be changed as this would break config.yaml that is used by Home Assistant. Prevent the change and return an error message. Extra fixes: * fix: EOS configuration initialisation by cli under EOSdash. Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>	2026-07-23 15:11:18 +02:00
Bobby NoelteandGitHub	3bb0e02aed	fix: provider settings in top level field of configuration (#1161) ... Configuration for some providers was given in the sub-field `provider_settings` combining the settings of several providers. Pydantic does not understand this very well and the configuration became cumbersome, especially in EOSdash. All provider settings from the `provider-settings` sub-field are now lifted to the top level field of the configuration. The changes are automatically migrated in the configuration. Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>	2026-07-20 14:37:03 +02:00
Bobby NoelteandGitHub	cf477d91a3	feat: add fixed electricity prediction with time window support (#930) ... Add a fixed electricity prediction that supports prices per time window. The time windows may flexible be defined by day or date. The prediction documentation is updated to also cover the ElecPriceFixed provider. The feature includes several changes that are not directly related to the electricity price prediction implementation but are necessary to keep EOS running properly and to test and document the changes. * feat: add value time windows Add time windows with an associated float value. * feat: harden eos measurements endpoints error detection and reporting Cover more errors that may be raised during endpoint access. Report the errors including trace information to ease debugging. * feat: extend server configuration to cover all arguments Make the argument controlled options also available in server configuration. * fix: eos config configuration by cli arguments Move the command line argument handling to config eos so that it is excuted whenever eos config is rebuild or reset. * chore: extend measurement endpoint system test * chore: refactor time windows Move time windows to configabc as they are only used in configurations. Also move all tests to test_configabc. * chore: provide config update errors in eosdash with summarized error text If there is an update error provide the error text as a summary. On click provide the full error text. * chore: force eosdash ip address and port in makefile dev run Ensure eosdash ip address and port are correctly set for development runs. Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>	2026-03-11 17:18:45 +01:00
Bobby NoelteandGitHub	997e7646e9	fix: prevent exception when load prediction data is missing (#925) ... Validate solution prediction data before processing. If required prediction data is missing, the prediction is skipped instead of raising an exception. Introduce a new configuration file saving policy to improve loading robustness: - Exclude computed fields - Exclude fields set to their default values - Exclude fields with value None - Use field aliases - Recursively remove empty dictionaries and lists - Ensure general.version is always present and correctly set When loading older configuration files, computed fields are now stripped before migration. This further improves backward compatibility and loading robustness. Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>	2026-03-07 14:46:30 +01:00