-
Notifications
You must be signed in to change notification settings - Fork 108
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
Version 0.0.14 does not load tomorrow’s prices #326
Comments
Version 0.0.13 has same issue. It started yesterday. No updates performed since 2 weeks ago, so it have to be Noorpool api issue.. |
Double check entity/device name. Mine changed for some reason. |
It did not load yesterday prices for today. Today it failed to load tomorrow prices as well. |
I'm having the same problem. |
Same isse for me. Only a HA restart loads tomorrow prices. |
Or to reload integration manually. |
Once per hour in home-assistant.log --
|
I have a few additional exceptions Here, inn case they are useful
|
There is some issue with the data from nordpool, your error msg indicates that some data is missing (NoneType). And it started 00:00 today. |
I had to manually change the sensor.py to get it to work:
|
Just do a restart |
This issue is likely because the prices on the spot market weren't established at the regular time today and yesterday (and once before, a few weeks ago). The nordpool integration appears to only try to fetch the prices once, randomly between 13:00 and 14:00 hours. Today, the prices for tomorrow were delayed by 3 hours for NL (see https://www.epexspot.com/en/market-data) :
I suppose the best solution would be to add a periodic check every hour starting at 13: (the current logic) and repeating until valid date has been received. |
How do you reload a Hacs integration? Tried redownloading and restart HA without success, still no prices for today |
I do have the same problem since updating HA from 2023.4 to 2023.5 😕 |
Same problem with core 2023.5.4, looks like today's prices didn't load. |
How to reload integration when it is defined in configuration.yaml? Only restart? |
I will investigate and attempt to fix it today. Please provide debug logs. |
Same problem with 2023.4.6 - tomorrow's prices n/a. Maybe related to negative prices? |
Not the negative prices per se, but a delay in the markets (from how I'm interpreting it, because a balance could not be found at the first attempt, so repeat auctions were required) combined with just a single attempt from the sensor to fetch the prices. |
Same issue here. Only restart of HA will solve the issue. |
Until a fix is in. Just auto restart the integration right after midnight (or whatever works for you) |
Yeah, I was using the config. I added it as an integration instead and that solved it. But the problem is not solved by reloading the integration, only by restarting HA |
Interestingly enough, even when I've restarted HA multiple times (using YAML config), still no prices for today show up. Yesterday this fixed the issue. I'll see if I can retrieve debug logging. |
@ThePatricide check if the sensor got a new name. Some of the settings are using in the entity id name. In the lastest release i merged a pr that changed back to the default vat thus changing the entity id for Finland |
|
Do not know the cause, but after 3 days of misbehavior today tomorrow's prices automagically showed up :-) So it seems that the problem was on NPS side :-/ ? |
Same happened in finland, tomorrow's prices didn't show up until i restarted HA |
@Hellowlol sorry, no logs for now. turned on debug and restarted HA, will collect logs next time. |
This happens if the first auction is unsuccessful. Implemented by verifying that the data is valid (in join_result_for_correct_time()) and raising an exception (which triggers retry) if it isn't. This fixes issue custom-components#326.
This fixes the root cause of issue custom-components#326
And this should fix the other side of issue custom-components#326 (the lack of retries if data is not available at the usual polling time).
This fixes the root cause of issue custom-components#326
And this should fix the other side of issue custom-components#326 (the lack of retries if data is not available at the usual polling time).
This fixes the root cause of issue custom-components#326
And this should fix the other side of issue custom-components#326 (the lack of retries if data is not available at the usual polling time).
This fixes the root cause of issue custom-components#326
And this should fix the other side of issue custom-components#326 (the lack of retries if data is not available at the usual polling time).
And this should fix the other side of issue custom-components#326 (the lack of retries if data is not available at the usual polling time).
This fixes the root cause of issue custom-components#326
And this should fix the other side of issue custom-components#326 (the lack of retries if data is not available at the usual polling time).
This fixes the root cause of issue custom-components#326
And this should fix the other side of issue custom-components#326 (the lack of retries if data is not available at the usual polling time).
the prices for tomorrow were not updated today and there were the following log messages:
|
This happens if the first auction is unsuccessful. Implemented by verifying that the data is valid (in join_result_for_correct_time()) and raising an exception if it isn't. This partially fixes issue custom-components#326.
Sorry for commenting on a closed thread, but two times this week I had to reload the integration because prices were not automatically fetched for next day. Even after the new day started no data was visible, and around 02 in the night I reloaded the integration and prices appeared. Seems like this issue is not solved, or maybe it is not published yet? |
I noticed the same. Had to reload Saturday and today (Wednesday) |
Same here, checked Nordpool and Tibber, they did not update until around 15.00 (UTC+1). |
Nordpool did not publish the prices on time, unfortunately.
- - -
Mvh / BR
*Jahn Thomas Fidje*+47 915 88 028
…On Wed, 1 Nov 2023 at 21:57, agrauballe ***@***.***> wrote:
Sorry for commenting on a closed thread, but two times this week I had to
reload the integration because prices were not automatically fetched for
next day. Even after the new day started no data was visible, and around 02
in the night I reloaded the integration and prices appeared.
Seems like this issue is not solved, or maybe it is not published yet?
I noticed the same. Had to reload Saturday and today (Wednesday)
—
Reply to this email directly, view it on GitHub
<#326 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADUBG22B4Q4TOXGLJV4X6ULYCKZSBAVCNFSM6AAAAAAYRGPCAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBZGY3TGMRUGQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Add these automations to your configurations. One automatically reloads the Nordpool integration after midnight if the (Note: replace the sensor name in
|
Thank you for this! I will test it later when I get time for it. Thanks for sharing |
Doesn’t seem to be an issue that’s hard to handle properly in the addon is it? It’s a situation (=prices not available at a certain time) that obviously happens from time to time. So a re-check every random minutes until the prices have been received properly. |
Ditto :-) |
@Hellowlol Maybe it's time to do a release with this fix so it gets out to the masses? |
@Hellowlol, still alive? :-) |
Version of the custom_component
0.0.14
Homeassistant version
2023.5.3 and 2023.5.4
Configuration
UI config
Describe the bug
After updating to the latest version, the integration no longer loads tomorrow’s prices. I have to reload the integration to get next day’s prices.
Debug log
Nothing in the normal logs. I have activate debug logging now, will follow up in a comment if something pops up.
The text was updated successfully, but these errors were encountered: