You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The price data is not always exactly in timedue to several reasons (not part of this issue).
To make getting the energy (and emission data) more robust, try get prices every 15 minutes after 13:00 instead of 2 tries per day. Alert the user if it has not received data at 17:00 as then the schedules might get influenced by this missing data.
The text was updated successfully, but these errors were encountered:
Now, if the getting the prices fails or is not up to date yet, we check every hour until the following noon.
There is one check at 18:30 to see if prices are up to date, if not the user is notified.
The notification is removed if prices are up to date again.
The code is consolidated where possible.
The test version of get_fm_data.py is added to a tests folder.
Now, if the getting the prices fails or is not up to date yet, we check every hour until the following noon.
There is one check at 18:30 to see if prices are up to date, if not the user is notified.
The notification is removed if prices are up to date again.
The code is consolidated where possible.
The test version of get_fm_data.py is added to a tests folder.
The price data is not always exactly in timedue to several reasons (not part of this issue).
To make getting the energy (and emission data) more robust, try get prices every 15 minutes after 13:00 instead of 2 tries per day. Alert the user if it has not received data at 17:00 as then the schedules might get influenced by this missing data.
The text was updated successfully, but these errors were encountered: