After upgrading to HA 2024.4.0 no prices where retreived #150

sstolk90 · 2024-04-05T07:06:57Z

I did reset my password @ Entsoe and my API key to be sure.
It shows this after reloading it all.
It has the prices of yesterday and the 3rd of April but after reloading the 5th is not showing up:

I've installed the update around 22:00

ronaldt80 · 2024-04-05T07:14:12Z

Same here on 2024.03 version so it's probably the API.

EpicCoolDude · 2024-04-05T07:15:38Z

Yes, I also think this is not an issue regarding the upgrade to 2024.4.0. Same issue over here.
Also see: #149
The Entsoe API has returned errors. If you check the prices manually at https://transparency.entsoe.eu you see that there is no information for today regarding NL.

JSamsom72 · 2024-04-05T07:38:08Z

Same issue here.

Core 2024.4.0
Supervisor 2024.03.1
Operating System 12.1
Frontend 20240403.1

richardstroobach · 2024-04-05T07:39:11Z

Same here. Not working after the update to 2024.4.0, but that might be a coincidence like @ronaldt80 mentioned he has is with 2024.3.
When I logged in to Entso-e website, I had to change my password.

Like @EpicCoolDude mentioned, the data for The Netherlands looks empty for Day Ahead :

sembeek · 2024-04-05T07:51:16Z

Same here, I've sent an email to transparency@entsoe.eu to ask if it is a known issue.

harryboer · 2024-04-05T09:08:32Z

Same here since 2024.4.0

TheBrankman · 2024-04-05T09:58:21Z

Still on HA 2024.3.0, but same problem....

TheBrankman · 2024-04-05T10:35:36Z

I have found this in the log:

chrkeijzer · 2024-04-05T10:58:08Z

I got the same, on HA 2024.3.0. Switched over to the NordPool integration for now.

sembeek · 2024-04-05T10:59:58Z

Response from ENTSO-e:

The data was published on Transparency Platform by our Data Provider.
Could you please validate and confirm if we can consider the ticket closed?

And it does indeed appear to be back online now!
Just reload the integration in home assistant and the data will appear.

sstolk90 · 2024-04-05T11:03:24Z

Not yet here. Even after a restart or reload of the integration

TheBrankman · 2024-04-05T11:05:55Z

Here also still no change after reboot or reload....

richardstroobach · 2024-04-05T11:10:38Z

Data on the Entso-e site data is working again. Still not working on HA after a restart of the integration and even after a restart of HA.

TheBrankman · 2024-04-05T11:13:05Z

But an other log entry now:

JanBoos · 2024-04-05T12:59:50Z

Bij mij werkt het weer. Een nieuwe set services aanmaken met een andere naam.

TheBrankman · 2024-04-05T13:10:53Z

Bij mij werkt het weer. Een nieuwe set services aanmaken met een andere naam.

Wat bedoel je daarmee?

Arjanmus · 2024-04-05T13:18:17Z

2 hours ago I reloaded/restarted the integration and restarted HA without luck. Just now checked the graph again with no intervention inbetween, and the prices are there. (updated around 3pm CEST)
Unclear what went wrong, but at least I have a beautiful graph for tomorrow😃👌

sstolk90 · 2024-04-05T13:33:08Z

Still this in the log:

2024-04-05 15:31:24.658 DEBUG (MainThread) [custom_components.entsoe.coordinator] Fetching ENTSO-e data
2024-04-05 15:31:24.658 DEBUG (MainThread) [custom_components.entsoe.coordinator] NL
2024-04-05 15:31:26.538 DEBUG (MainThread) [custom_components.entsoe.coordinator] Finished fetching ENTSO-e coordinator data in 1.880 seconds (success: True)
2024-04-05 15:31:26.542 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_current_electricity_market_price (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.546 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_next_hour_electricity_market_price (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.551 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_lowest_energy_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.555 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_highest_energy_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.570 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_average_electricity_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.583 WARNING (MainThread) [custom_components.entsoe.sensor] Unable to update entity due to data processing error: None and error: min() iterable argument is empty
2024-04-05 15:31:26.583 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_current_percentage_of_highest_electricity_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.596 WARNING (MainThread) [custom_components.entsoe.sensor] Unable to update entity due to data processing error: None and error: min() iterable argument is empty
2024-04-05 15:31:26.597 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_time_of_highest_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.610 WARNING (MainThread) [custom_components.entsoe.sensor] Unable to update entity due to data processing error: None and error: min() iterable argument is empty
2024-04-05 15:31:26.610 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_time_of_lowest_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues

sstolk90 · 2024-04-05T13:39:23Z

Bij mij werkt het weer. Een nieuwe set services aanmaken met een andere naam.

Wat bedoel je daarmee?

So I have created a test Enstoe (just the name with same API key) and now I see the data. So there is a difference what HA applies between versions I think

TheBrankman · 2024-04-05T14:34:57Z

Hm...I deleted the old entrance and created a new one with exact the same name. I think I got values, but the graphs are still empty.... I have to investigate further.

huub66 · 2024-04-05T15:08:00Z

Bij mij werkt het weer. Een nieuwe set services aanmaken met een andere naam.

Wat bedoel je daarmee?

So I have created a test Enstoe (just the name with same API key) and now I see the data. So there is a difference what HA applies between versions I think

Same here, only problem is that I lost the statistics on the new sensors as the naming is different and my pricing template is not working anymore so I am seeing only market prices without an uplift. Anyone facing this as well?

harryboer · 2024-04-05T16:43:23Z

Hm...I deleted the old entrance and created a new one with exact the same name. I think I got values, but the graphs are still empty.... I have to investigate further.

Try deleting old configuration and create a new one with a different name, with the same name it doens't seem to work. Only problem is that you'll have to go through all the dashboards that use it to update with new name.

harryboer · 2024-04-05T16:47:27Z

Bij mij werkt het weer. Een nieuwe set services aanmaken met een andere naam.

Wat bedoel je daarmee?

So I have created a test Enstoe (just the name with same API key) and now I see the data. So there is a difference what HA applies between versions I think

Same here, only problem is that I lost the statistics on the new sensors as the naming is different and my pricing template is not working anymore so I am seeing only market prices without an uplift. Anyone facing this as well?

It seems to only work when using a new name, but yes then need to update all the dashboards to the new entity name and you'll loose all historic data. Did you tick the box to fill in tax and template at the start when creating the configuration? I found out that when trying to apply afterwards it doesn't work (maybe it does with the new set of data tomorrow).

wimwillems7325 · 2024-04-05T19:30:50Z

I removed the entso-e integration. Reinstall with another name. The same name is not working. I changed one character and it works!!

patatman · 2024-04-06T08:35:08Z

After reading this issue, I've also deleted my integration.
But I've managed to keep my history by doing the following:

~~1) Save/remember entity name~~
~~2) Delete the existing integration~~
~~3) Restart home assistant (THIS IS THE IMPORTANT PART)~~
~~4) Reconfigure integration with Same name from step 1 (or your previous install)~~
~~5) Find your history intact!~~
~~Quitte a work-around, but it's working for now.~~

Still doesn't update to new values, you really need a new name.

RogMoe · 2024-04-06T09:12:59Z

I removed the entso-e integration. Reinstall with another name. The same name is not working. I changed one character and it works!!

...and what happened to your history? Previous time all this happened and reinstalled integration, I lost all historic data...

richardstroobach · 2024-04-08T19:01:10Z

Do we know what is causing this failure? Maybe then we can tackle this problem. I would like to keep historic data.

StreborStrebor · 2024-04-09T14:38:18Z

Still this in the log:

2024-04-05 15:31:24.658 DEBUG (MainThread) [custom_components.entsoe.coordinator] Fetching ENTSO-e data
2024-04-05 15:31:24.658 DEBUG (MainThread) [custom_components.entsoe.coordinator] NL
2024-04-05 15:31:26.538 DEBUG (MainThread) [custom_components.entsoe.coordinator] Finished fetching ENTSO-e coordinator data in 1.880 seconds (success: True)
2024-04-05 15:31:26.542 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_current_electricity_market_price (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.546 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_next_hour_electricity_market_price (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.551 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_lowest_energy_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.555 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_highest_energy_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.570 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_average_electricity_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.583 WARNING (MainThread) [custom_components.entsoe.sensor] Unable to update entity due to data processing error: None and error: min() iterable argument is empty
2024-04-05 15:31:26.583 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_current_percentage_of_highest_electricity_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.596 WARNING (MainThread) [custom_components.entsoe.sensor] Unable to update entity due to data processing error: None and error: min() iterable argument is empty
2024-04-05 15:31:26.597 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_time_of_highest_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-05 15:31:26.610 WARNING (MainThread) [custom_components.entsoe.sensor] Unable to update entity due to data processing error: None and error: min() iterable argument is empty
2024-04-05 15:31:26.610 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.energieprijzen_time_of_lowest_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues

I have the exact same logs. It seems the Entities have changed classes (for example from Measurement to Monetary or Measurement to Timestamp).

Maybe deleting / reinstalling the integration configures it all correctly. But that would kill historic data.
Better would be to for the integration to fix the already configured entities, that no longer work.

abroeders · 2024-04-13T10:02:49Z

I guess if recreating the plugin instance with another name is solving this problem that it is a bug in this plugin. I'll wait until this bug is fixed.

RogMoe · 2024-04-13T10:13:30Z

Second time it happened to me. I switched to Nordpool. Sorry -------- Oorspronkelijk bericht --------Van: Arno Broeders ***@***.***> Datum: 13-04-2024 12:04 (GMT+01:00) Aan: JaccoR/hass-entso-e ***@***.***> Cc: RogMoe ***@***.***>, Comment ***@***.***> Onderwerp: Re: [JaccoR/hass-entso-e] After upgrading to HA 2024.4.0 no prices where retreived (Issue #150) I guess if recreating the plugin instance with another name is solving this problem that it is a bug in this plugin. I'll wait until this bug is fixed. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

martin3000 · 2024-04-14T21:01:14Z

You have to delete the ensoe entries from .storage/core.restore_state

martin3000 · 2024-04-15T14:05:12Z

The problem is that sometimes there are wrong stored sensor values. And the function "async_get_last_sensor_data" in sensor.py always overwrites the good values. At the end, there is no way out.
If "async_get_last_sensor_data" always returns None, the integration is working again.

PvaI · 2024-04-17T09:54:19Z

You have to delete the ensoe entries from .storage/core.restore_state

How do you proceed after deleting them?

I've deleted all entso entries and reloaded HA, but old data is retained,
I've changed the last seen value to None / a date in the past and reload HA, but no change.
I've deleted the specific entry with hourly values and kept the file open, reloaded the integration and it still gets the wrong values from somewhere, these values are not in the core.restore_state file, it's only updated with the old values once I close the file.

I've queried my database, but entso data isn't stored there. I'll try to add the data to recorder and try to delete it there.

martin3000 · 2024-04-17T10:42:04Z

I stopped HA, deleted the stored values and started HA. But that fixed only the "today" values, "tomorrow" was still wrong. So I fixed sth. in the code. If you have access to the custom_components/entsoe files, I can give you my fix.

PvaI · 2024-04-17T11:22:17Z

I have access, looking at your hass-entso-e repo now, do you have the change documented? or in comments in the affceted file? So I can re-apply / understand the fix :)

martin3000 · 2024-04-17T11:48:29Z

The main change is func async_get_last_sensor_data in sensor.py. It always returns "None" now.
I also changed coordinator.py, but I'm not sure if you need that.
Maybe the mean, max or min values will stop work. I did not check that.

PvaI · 2024-04-17T11:52:38Z

I'll check it out, I'm moving from the provided min/avg/max values; today the avg provided by Entso-E is below the min value :/
I'm checking out TheFes's work to get the optimal hours - https://github.com/TheFes/cheapest-energy-hours

martin3000 · 2024-04-17T12:28:18Z

I'm checking out TheFes's work to get the optimal hours

This looks pretty complex. I did not know that there is sth. like custom templates!

PvaI · 2024-04-17T17:45:47Z

You can import it through hacs, if you enable experimental features in HACS (Integrations -> Hacs - > Configure), you then still need to move the cheapest_energy_hours.jinja file from the www/community/cheapest-energy-hours folder to the custom_templates folder (which you may need to create at the same level as the www & custom_components folders.
Hmm, I suppose I should symlink it and not lose the benefits of HACS ;)

I then used the following in the template editor to get some results, later I'll create some sensors or automations with them.
There's some more stuff you can do with weighted hours, still figuring this out myself ;)

{%- set sensor = 'sensor.entso_average_electricity_price_today' -%}
{% from 'cheapest_energy_hours.jinja' import cheapest_energy_hours %}
Cheapest 3 hour period tonight: 
{{ cheapest_energy_hours(sensor=sensor, attr_today='prices_today', attr_tomorrow='prices_tomorrow', time_key='time', value_key='price', hours=all, start='21:00', end=today_at('09:00') + timedelta(days=1), look_ahead=true) }}
Cheapest 3 hour period tomorrow:
{{ cheapest_energy_hours(sensor=sensor, attr_today='prices_today', attr_tomorrow='prices_tomorrow', time_key='time', value_key='price', hours=all, start='09:00', end=today_at('21:00') + timedelta(days=1), look_ahead=true) }}

JaySea77 · 2024-06-08T15:50:37Z

Happened to me again in the last couple days. Have to remove and add the integration with a new name again...

richardstroobach · 2024-06-08T15:54:33Z

And again, after updating to the latest Home Assistant release, I have no data. Tried reinstalling with another name, but no luck this time. Can't this be solved permanently somehow?

JaySea77 · 2024-06-08T15:57:24Z

And again, after updating to the latest Home Assistant release, I have no data. Tried reinstalling with another name, but no luck this time. Can't this be solved permanently somehow?

Haven't tried to do the trick again, and updated my ha today, so might be broken since today.

wilfredktlr · 2024-06-08T16:38:06Z

This happened again today (for the second time). You can either create a new integration with a different name (this sucks because you also have to change the name in the automations and you lose the history) or use this fix (which worked for me).

I'm not sure what the underlying cause is. Maybe this issue has something to do with it.

PvaI · 2024-06-10T18:40:41Z

I didn't upgrade and I had implemented Martin's fix, still broke. Trying to clear config/.storage/core.restore_state entries now...

Update: Clearing the entries from core.restore_state worked.

StreborStrebor · 2024-06-13T09:26:53Z

I didn't upgrade and I had implemented Martin's fix, still broke. Trying to clear config/.storage/core.restore_state entries now...

Update: Clearing the entries from core.restore_state worked.

I only needed to clear this object (including all the nested today and tomorrow prices that seemed to be stuck since 6 days ago): sensor.[your entso-e config name]_average_electricity_price_today

Prices and graphs filled almost immediately after starting hass again.

JaySea77 · 2024-06-13T14:14:59Z

I didn't upgrade and I had implemented Martin's fix, still broke. Trying to clear config/.storage/core.restore_state entries now...

Update: Clearing the entries from core.restore_state worked.

I only needed to clear this object (including all the nested today and tomorrow prices that seemed to be stuck since 6 days ago): sensor.[your entso-e config name]_average_electricity_price_today

Prices and graphs filled almost immediately after starting hass again.

Can you say how to clear the object including the nested today and tomorrow prices?

StreborStrebor · 2024-06-14T07:19:38Z

I only needed to clear this object (including all the nested today and tomorrow prices that seemed to be stuck since 6 days ago): sensor.[your entso-e config name]_average_electricity_price_today
Prices and graphs filled almost immediately after starting hass again.

Can you say how to clear the object including the nested today and tomorrow prices?

Sure,

SSH into your HASS
Shut down HASS with ha core stop
Make a backup of the state config file cp config/.storage/core.restore_state config/.storage/core.restore_state.bak
Edit it: nano config/.storage/core.restore_state

Remove this segment starting with the {

      "state": {"entity_id":"sensor.[your entso-e config name]_average_electricity_price_today","state":"0.26295","attributes":{"state_class":"measurement","prices_today":[{"time":"2024-06-14 00:00:00+02:00","price":0.25825},{"time":">
      "extra_data": {
        "native_value": 0.26295,
        "native_unit_of_measurement": null,
        "_attr_extra_state_attributes": {
          "prices_today": [
            {
              "time": "2024-06-14 00:00:00+02:00",
              "price": 0.25825
            },
            {
              "time": "2024-06-14 01:00:00+02:00",
              "price": 0.24494
            },

...cut to keep this readably short...

            {
              "time": "2024-06-14 23:00:00+02:00",
              "price": 0.3043
            }
          ],
          "prices_tomorrow": [],
          "prices": [
            {
              "time": "2024-06-13 00:00:00+02:00",
              "price": 0.29839
            },

...cut to keep this readably short...

            {
              "time": "2024-06-14 22:00:00+02:00",
              "price": 0.30842
            },
            {
              "time": "2024-06-14 23:00:00+02:00",
              "price": 0.3043
            }
          ]
        }
      },
      "last_seen": "2024-06-14T07:15:22.322960+00:00"
    },

Restart HASS with ha core start

TheLion · 2024-06-14T07:27:03Z

I didn't upgrade and I had implemented Martin's fix, still broke. Trying to clear config/.storage/core.restore_state entries now...
Update: Clearing the entries from core.restore_state worked.

I only needed to clear this object (including all the nested today and tomorrow prices that seemed to be stuck since 6 days ago): sensor.[your entso-e config name]_average_electricity_price_today

Prices and graphs filled almost immediately after starting hass again.

Clearing this one object solved the issue for me.

Hopefully there will be a fix soon, that fixes it permanently ;-)

DannyOosterveer · 2024-06-14T21:48:08Z

This is a quite persistent and annoying error. I've been using the integration for over two years. Everytime the ENTSO-e API had some error, and there is no data available for some time, the integration seems to corrupt the data in sensors. Even after the data in the API is correct again, you can't use the previous sensors anymore. You'll have to delete the integration, add it again and change all our automations etc. Probably some better error handling is necessary when receiving empty or wrong data from the API...

JaySea77 · 2024-06-15T17:32:00Z

Sure,

SSH into your HASS Shut down HASS with ha core stop Make a backup of the state config file cp config/.storage/core.restore_state config/.storage/core.restore_state.bak Edit it: nano config/.storage/core.restore_state

Remove this segment starting with the {

where should the config dir be? I managed to get the ha core to stop, but I cannot find the file you are refering to.

Found it on mnt/data/supervisor/homeassistant/.storage/core.restore_state
I removed the entire block starting with the line after prices_today since I didn't know which { you were referring to.

Edit2: the data filled up a few minutes after the removing the data from core.restore_state. Thanks for pointing this out.

Roeland54 · 2024-08-31T11:18:04Z

v0.4.0 is released this version contains fixes that solve a lot of warnings and known issues. This issue is probably also solved.
Please update to the latest version.
Closing this issue for now. If you still have issue please feel free to open a new issue.

ronaldt80 · 2024-09-02T17:48:51Z

Dont think its resolved.. my prices tomorrow attribute is empty; prices today contains today's prices and prices attribute contains prices of yesterday and tomorrow.

richardstroobach · 2024-09-02T18:39:44Z

Here the same as @ronaldt80.

Roeland54 · 2024-09-02T20:45:33Z

The entso-e platform does not respond with the prices of tomorrow a.t.m. So the issue you currently experiencing is not related to the integration.

JaySea77 · 2024-09-03T18:18:05Z

It happened again today so the 0.4.0 update didn't fix the issue.

Roeland54 · 2024-09-03T18:39:24Z

The entso-e platform did not return prices for today until it was almost noon. Currently the integration does not handle this properly. We are working on this.: Follow-up on this in issue #171. But entso-e being 20 hours late with prices is something we can't solve.

V0.4.0 should have automatically recovered this afternoon without user intervention. If this is not the case feel free to open a new issue with detailed information about your config.

JaySea77 · 2024-09-03T18:41:34Z

I noticed the current today prices are the prices of 2 days ago. How can I force the data to update?

Edit:
I think the issue you mentioned is what is happening here. Though it still says 1th and 2nd of September for me.

Edit2:
Suddenly the data updated in the last 2 minutes. It shows 3rd and 4th of September now.

Roeland54 · 2024-09-03T18:58:45Z

Follow-up in issue #171.

Roeland54 closed this as completed Aug 31, 2024

Repository owner locked and limited conversation to collaborators Sep 3, 2024

After upgrading to HA 2024.4.0 no prices where retreived #150

After upgrading to HA 2024.4.0 no prices where retreived #150

Comments

sstolk90 commented Apr 5, 2024

ronaldt80 commented Apr 5, 2024

EpicCoolDude commented Apr 5, 2024 • edited Loading

JSamsom72 commented Apr 5, 2024

richardstroobach commented Apr 5, 2024 • edited Loading

sembeek commented Apr 5, 2024

harryboer commented Apr 5, 2024

TheBrankman commented Apr 5, 2024

TheBrankman commented Apr 5, 2024

chrkeijzer commented Apr 5, 2024

sembeek commented Apr 5, 2024 • edited Loading

sstolk90 commented Apr 5, 2024

TheBrankman commented Apr 5, 2024

richardstroobach commented Apr 5, 2024 • edited Loading

TheBrankman commented Apr 5, 2024

JanBoos commented Apr 5, 2024 • edited Loading

TheBrankman commented Apr 5, 2024

Arjanmus commented Apr 5, 2024

sstolk90 commented Apr 5, 2024 • edited Loading

sstolk90 commented Apr 5, 2024 • edited Loading

TheBrankman commented Apr 5, 2024

huub66 commented Apr 5, 2024

harryboer commented Apr 5, 2024

harryboer commented Apr 5, 2024

wimwillems7325 commented Apr 5, 2024

patatman commented Apr 6, 2024 • edited Loading

RogMoe commented Apr 6, 2024

richardstroobach commented Apr 8, 2024

StreborStrebor commented Apr 9, 2024

abroeders commented Apr 13, 2024

RogMoe commented Apr 13, 2024 via email • edited Loading

martin3000 commented Apr 14, 2024

martin3000 commented Apr 15, 2024 • edited Loading

PvaI commented Apr 17, 2024

martin3000 commented Apr 17, 2024

PvaI commented Apr 17, 2024

martin3000 commented Apr 17, 2024

PvaI commented Apr 17, 2024

martin3000 commented Apr 17, 2024

PvaI commented Apr 17, 2024 • edited Loading

JaySea77 commented Jun 8, 2024

richardstroobach commented Jun 8, 2024 • edited Loading

JaySea77 commented Jun 8, 2024

wilfredktlr commented Jun 8, 2024

PvaI commented Jun 10, 2024 • edited Loading

StreborStrebor commented Jun 13, 2024

JaySea77 commented Jun 13, 2024

StreborStrebor commented Jun 14, 2024 • edited Loading

TheLion commented Jun 14, 2024

DannyOosterveer commented Jun 14, 2024

JaySea77 commented Jun 15, 2024 • edited Loading

Roeland54 commented Aug 31, 2024

ronaldt80 commented Sep 2, 2024

richardstroobach commented Sep 2, 2024 • edited Loading

Roeland54 commented Sep 2, 2024

JaySea77 commented Sep 3, 2024

Roeland54 commented Sep 3, 2024 • edited Loading

JaySea77 commented Sep 3, 2024 • edited Loading

Roeland54 commented Sep 3, 2024

EpicCoolDude commented Apr 5, 2024 •

edited

Loading

richardstroobach commented Apr 5, 2024 •

edited

Loading

sembeek commented Apr 5, 2024 •

edited

Loading

richardstroobach commented Apr 5, 2024 •

edited

Loading

JanBoos commented Apr 5, 2024 •

edited

Loading

sstolk90 commented Apr 5, 2024 •

edited

Loading

sstolk90 commented Apr 5, 2024 •

edited

Loading

patatman commented Apr 6, 2024 •

edited

Loading

RogMoe commented Apr 13, 2024 via email •

edited

Loading

martin3000 commented Apr 15, 2024 •

edited

Loading

PvaI commented Apr 17, 2024 •

edited

Loading

richardstroobach commented Jun 8, 2024 •

edited

Loading

PvaI commented Jun 10, 2024 •

edited

Loading

StreborStrebor commented Jun 14, 2024 •

edited

Loading

JaySea77 commented Jun 15, 2024 •

edited

Loading

richardstroobach commented Sep 2, 2024 •

edited

Loading

Roeland54 commented Sep 3, 2024 •

edited

Loading

JaySea77 commented Sep 3, 2024 •

edited

Loading