fix: azimuth setting of pvforecastakkudoktor provider (#567)

EOS now enforces the general azimuth definition as e.g. defined in ISO 19111:
north=0, east=90, south=180, west=270. This is the convention that is and was
in the EOS documentation.

As the PV forecast of akkudoktor.net follows a different convention
(north=+-180, east=-90, south=0, west=90) the values from EOS are now converted
before the request is sent to akkudoktor.net.

BREAKING CHANGE: Azimuth configurations that followed the PVForecastAkkudoktor convention
(north=+-180, east=-90, south=0, west=90) must be converted to the general azimuth definition:
north=0, east=90, south=180, west=270.

Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>
This commit is contained in:
Bobby Noelte
2025-05-28 20:42:43 +02:00
committed by GitHub
parent 46e078fce1
commit 3ec36e0932
8 changed files with 50 additions and 37 deletions

View File

@@ -95,7 +95,7 @@ class TestEOSdashConfig:
PVForecastPlaneSetting(), values, values_prefix=["pvforecast", "planes", "0"]
)
assert any(
item["name"] == "pvforecast.planes.0.surface_azimuth" and item["value"] == "-10"
item["name"] == "pvforecast.planes.0.surface_azimuth" and item["value"] == "170"
for item in config
)
assert any(