-
Notifications
You must be signed in to change notification settings - Fork 105
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
0.0.15.b1 tomorrows prices gone after restart #404
Comments
yes, for me also tomorrow prices is gone |
Same issue here. This commit probably explains it, since the feature was deleted: 46e66ba |
Update: |
for me also tomorrow prices is gone |
The problem with missing "tomorrow" isn't just that you don't see the next day, it's that once the day changes to the tomorrow, there's no information, because the "today" becomes "yesterday" and there's no "tomorrow" to show for the ongoing day until it updates the data from the nordcloud api again either forced by a restart or perhaps afternoon next day. This also coincides with the highest peak hour prices in a long while. |
Same issues here also. |
Same issue here. |
I have two sensors, one with VAT and the other without. Strangely the one without is missing tomorrow prices, the other sensor with VAT gets them. Could it be something related to VAT change in Finland? 🤔 |
@odelma that is really weird. Can you provide logs? Anyway if you are having issues please downgrade |
Yes, weird. And now I noticed that the sensor that shows tomorrow’s prices still gets sort of stuck after midnight with last price from yesterday. For example it showed 0,46 after midnight until morning and only got new prices after reloading the integration. I will try to downgrade and see what happens… |
Downgrading did not help for me.. (2 days ago) |
To which version did you downgrade? I remember the last time I tried to upgrade (0.15xx 🤔) it did not load the integration at all at startup and going back to 0.14 did not help either. Once I downgraded to 0.13 it started working again…🤷♂️ |
Downgraded to 0.14 |
Or, if you are on 0.0.15b1, never restart HA, after tomorrow's values are available works for me. |
I see this too. Downgraded to 0.0.14 again. Errors in logs is preferred over not working. |
@Hellowlol I'm a newbie here, so is there anything else I can do to help resolve this issue? |
The latest commit needs to be reverted. A part for that I’m not sure. Need to have time to debug it. Seems strange |
I'm on 0.0.14 and same situation, tomorrows prices are totally gone after HA restart today 2024-09-22 at 20:10 EEST (so UTC+03:00) and 'Tomorrow valid' i set to false. Restarting Nordpool doesn't help until the day has changed. So is restart only fetching 'todays' values and logic fails for 'tomorrow' until new values are published? Attributes
|
Then it fails after midnight because there are no values for current day Logger: homeassistant.util.logging Exception in handle_new_day when dispatching 'nordpool_update_day': () Traceback (most recent call last): File "/config/custom_components/nordpool/sensor.py", line 473, in handle_new_day await self.handle_new_hr() File "/config/custom_components/nordpool/sensor.py", line 478, in handle_new_hr today = await self._api.today(self._area, self._currency) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/nordpool/init.py", line 123, in today return await self._someday(area, currency, "today") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/nordpool/init.py", line 119, in _someday return self._data.get(currency, {}).get(day, {}).get(area) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get' |
A reload of nordpool integration now after midnight fetches the values for 2023-09-23 that were missing yesterday after HA restart. Tomorrow is not published yet, that will happen in the afternoon. Average 0.08
|
Just to confirm that I've been running the past three weeks without issues by omitting this commit, where the try/catch exists for the exact scenario of no tomorrow when the time switches to the "old tomorrow" as the "current day" between midnight and availabality of a "new tomorrow" dataset the next afternoon: 46e66ba |
Version of the custom_component
0.0.15.b1
Homeassistant version
HA 2024.8.3
Configuration
Describe the bug
After restarting HA, tomorrows values are gone. Even after reloading the integration at 14:50.
Debug log
The text was updated successfully, but these errors were encountered: