The provider settings (weather, PV forecast, load, electricity price, feed-in
tariff, electricity fee) validate their provider id against the providers of
the prediction instance. While the configuration is created, that instance
does not exist yet, and the validation falls back to fixed lists. These were
incomplete: weather knew only 'WeatherImport', load lacked
'LoadAkkudoktorAdjusted'. A configuration file with e.g. weather provider
'OpenMeteo' then fails to load:
Provider 'OpenMeteo' is not a valid weather provider: ['WeatherImport']
This is hidden today because ConfigEOS.documentation_mode() is always true
(_force_documentation_mode is a pydantic private attribute, whose class
attribute is a truthy descriptor), and get_prediction() then creates the
prediction instance on access. Once documentation mode is enabled only
explicitly, the configuration does not load.
Derive the provider ids from the provider classes instead
(prediction_provider_ids). They no longer depend on whether the prediction
instance exists, so the validation is the same before and after
initialization.
Additional changes
- Add the test fixture uncreated_config, which lets get_config(init=True)
create a new configuration from the config file and restores the old one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bobby NoelteandClaude Opus 5.5
a0e57a18b7