I have used Entsoe binding to get current spot price, but from 1 Oct it stopped working!
Guess it is because Nordpol started to have 15 minute prices
The error I get is “Resolution PT60M not found in ENTSOE response”
Does anyone know how to solve this?
I just updated to 5.0.1 used 4.3 before, same result
entsoe doesn’t provide 60min tariffs any more. Just select the 15min option and they will be fetched. If you still need 60min values, you have to calculate them yourself.
Yeah, in the Thing configuration file add this line:
resolution=“PT15M”
Thank you, I did not have the resolution tag set at all
Please create a bug report, PT15M should become the default.
Also a PR on the bindings docs to mention PT15M in the first place.
… how about having the binding providing hourly prives again by averaging the 15min values per hour? That would be very handy for some of my needs.
That’s none of any binding’s business. Any such postprocessing function can also easily be misunderstood so potentially leads to all sorts of unwanted consequences.
If you want to have that for whatever reason that likely only applies to your setup, code it yourself.
Dear All,
i tried to get the entsoe Binding up and running, to it always stays offline –> see log
| 22:02:44.917[INFO] [openhab.event.ThingStatusInfoChangedEvent] - Thing ‘entsoe:day-ahead:382654dae2’ changed from OFFLINE (COMMUNICATION_ERROR): The request failed with HTTP error 400 to UNINITIALIZED |
|---|
| 22:02:44.920[INFO] [openhab.event.ThingStatusInfoChangedEvent] - Thing ‘entsoe:day-ahead:382654dae2’ changed from UNINITIALIZED to UNINITIALIZED (DISABLED) |
| 22:02:45.886[DEBUG] [org.openhab.binding.entsoe.internal.client.Client] - Sending GET request with parameters: https://web-api.tp.entsoe.eu/api?securityToken=xxxxx-xxxxx-xxxxx&documentType=A44&in_domain=10YAT-APG------L&out_domain=10YAT-APG------L&periodStart=202512142300&periodEnd=202512162300 |
| 22:02:45.887[INFO] [openhab.event.ThingStatusInfoChangedEvent] - Thing ‘entsoe:day-ahead:382654dae2’ changed from UNINITIALIZED (DISABLED) to INITIALIZING |
| 22:02:45.887[INFO] [openhab.event.ThingStatusInfoChangedEvent] - Thing ‘entsoe:day-ahead:382654dae2’ changed from INITIALIZING to UNKNOWN |
| 22:02:45.945[INFO] [openhab.event.ThingStatusInfoChangedEvent] - Thing ‘entsoe:day-ahead:382654dae2’ changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): The request failed with HTTP error 400 |
Any help would be really appreciated!
I think the Entsoe binding has a small bug in case of hourly prices. I’m using OH5.1.1 under Win11.
The error is in the price for 23h. E.g. today the hourly price at 23h is 9.678 snt/kWh here in Finland but Entsoe shows 6.28.
A few days ago I have upgraded Openhab to OH 5.1.1 from OH 5.0.2. Since then I am having a problem with electricity price updates through the ENTSOE binding. It appears to be retrieving the data OK, but the price in Openhab is not updated and stays at the same fixed level.
Platform information:
Hardware: Raspberry Pi 4
OS: Bookworm
Java Runtime Environment: openjdk 21.0.9 2025-10-21 LTS
openHAB version: 5.1.1
The binding seems to retrieve the data OK every day according to the log file:
2026-01-12 14:18:58.397 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Fetch new prices? Empty=false Hour13<=14
2026-01-12 14:18:58.398 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Fetching new prices from 2026-01-10T23:00:00Z to 2026-01-13T23:00:00Z
2026-01-12 14:18:58.399 [DEBUG] [.entsoe.internal.client.EntsoeClient] - Sending GET request with parameters: https://web-api.tp.entsoe.eu/api?securityToken=xxxxx-xxxxx-xxxxx&documentType=A44&in_domain=10YNL----------L&out_domain=10YNL----------L&periodStart=202601102300&periodEnd=202601132300
2026-01-12 14:18:58.857 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Fetched 190 price entries
2026-01-12 14:18:58.858 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Day-ahead check: false
2026-01-12 14:19:58.859 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Fetch new prices? Empty=false Hour13<=14
2026-01-12 14:19:58.860 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Fetching new prices from 2026-01-10T23:00:00Z to 2026-01-13T23:00:00Z
2026-01-12 14:19:58.860 [DEBUG] [.entsoe.internal.client.EntsoeClient] - Sending GET request with parameters: https://web-api.tp.entsoe.eu/api?securityToken=xxxxx-xxxxx-xxxxx&documentType=A44&in_domain=10YNL----------L&out_domain=10YNL----------L&periodStart=202601102300&periodEnd=202601132300
2026-01-12 14:19:58.995 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Fetched 285 price entries
2026-01-12 14:19:58.996 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Day-ahead check: true
2026-01-12 14:19:58.997 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Get TimeSeries for 285 entries and target duration PT15M
2026-01-12 14:19:58.997 [DEBUG] [internal.client.EntsoeDocumentParser] - Transforming Duration PT15M to PT15M
2026-01-12 14:19:59.200 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - TimeSeries from 2026-01-10T23:00:00Z to 2026-01-13T22:45:00Z
2026-01-12 14:19:59.208 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Day-ahead check: true
These are the settings for the Thing:
Does anyone have any idea where I am going wrong?
Your issue is likely due to persistence changes in 5.1, see the big thread on that for details.
In short: if you have an inmemory.persist remove the default strategy entry there.
@mstormi , thanks for the tip. I just checked my setup and I don’t have inmemory persistence installed, but do have JDBC persistence. I had already figured out that I needed to remove the default strategy from the JDBC persistence configuration, but I have just double checked it is actually the case. All other data is updating and logging fine. It is just the electricity prices that appear stuck at a fixed historic value.
For the EntsoE binding in 5.0+ the EnergyPrice item is a TimeSeries.
These you need to persist with inmemory (in addition to whatever default persistence you’re using).
@mstormi Thanks for that tip. I’ve added the inmemory persistence and it has correctly updated since.
hi, i tried to make relay on when item korkeinhinta is smaller than entsoe spot price:
(Dayahead_prices_Spot_Price.state as Number) > (KorkeinSahkonHinta.state as Number)
I could not get this work, openhab 5.1.1 , can not figure out whats wrong,
at label KorkeinHinta goes 0 if i set 0.09,... at items it shows correctly
and at label spot price is correctly,... both corrcetly whit units but rules
comparsion dose not work!!!!
Hi, does anyone else has issues with Entso-e not delivering day-ahead prices for DE_LU zone since last Friday? No error message, just empty response - afaict.
Thanks
Hm, no. I was one week off but looking into the data all Entso-e prices are available. Also for tomorrow the prices are avilable.
Do you have any traces for empty responses and were they answered with Http Status OK 200?
… ok. its working again. Have not touched anything. Entso-e rolled out a new software version on Friday afternoon 
which seems to have broken the updates. Data is delivered now.
still nothing in the Netherlands, no day ahead tomorrow….. The rest of EU seems fine. I switched to Nordpool.
… I came across an interesting service we might consider as an alternative. There is free but restricted API access after simple registration. It provides Entso-E data too but also some ML model predicted future data based on weather data. While the site is in German, it provides access for all bidding zones. Maybe it can be integrated as optional / fall back solution?
API documentation is here: API - Energyforecast