Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Make getting prices more robust #115

Closed
ArdJonker opened this issue Oct 5, 2024 · 0 comments · Fixed by #116
Closed

Feature Request: Make getting prices more robust #115

ArdJonker opened this issue Oct 5, 2024 · 0 comments · Fixed by #116

Comments

@ArdJonker
Copy link
Contributor

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.

ArdJonker added a commit that referenced this issue Oct 14, 2024
 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.
ArdJonker added a commit that referenced this issue Oct 14, 2024
 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.
@ArdJonker ArdJonker linked a pull request Oct 14, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant