[energidataservice] Improve handling of extended service/dataset unvailability
jlaur opened this issue · comments
This issue is created retrospectively for documenting and keeping track of issues identified during the second weekend in April 2024 where Energi Data Service experienced technical problems throughout a full weekend:
Over the weekend from Friday April 12th to Monday April 15th 2024, we experienced technical problems updating a number of datasets (including: Elspot Prices, Power System Right Now, CO2 Emission, Regulating Balance Power Data, Electricity Production and Exchange 5 min Realtime etc.).
Monday morning we were able to resume the dataload on most of the datasets and start a backfill of historical data.
Monday afternoon all datasets were updated with historical data except: [...]
The first thing I noticed when my dishwasher price calculation automation did not work, was that everything seemed normal. The Thing was still online, but prices were not available for the full requested calculation period.
Next day prices were completely missing, and some notifications regarding ended programs including price (e.g. washing macine) showed 0,00 as price for running the program. At this time, after midnight, I also noticed that next call was scheduled around 13:00 on that day, although prices were missing. Until midnight an exponential backoff strategy had been applied for a few calls during the day.
When finally there were no prices available at all even looking 24 hours back in time, the Thing went OFFLINE. This also impacted tariffs, even though they were actually available. Even before then persisting of future tariffs through time series stopped working because they relied on spot prices in the same period.
Last, when the issue was finally fixed on Monday, this now left a gap in persisted prices, since the binding's time window is 24 hours back and until next day.
All in all, this left some room for improvement. Distinct issues:
Your Environment
- Version used: 4.2 latest snapshot
This issue has been mentioned on openHAB Community. There might be relevant details there:
https://community.openhab.org/t/energi-data-service-binding-4-0-0-0-4-1-0-0/144370/50