ENTSO-E Binding: Went offline

Add-ons Bindings
,
1

I’ve been having problems with the ENTSO-E connection for a few days now. My system is openHAB 5.1.3. At first, I didn’t notice that it had gone offline. I only noticed that the day-ahead price wasn’t being updated. Today, I saw that the binding had gone offline again.

In the thing definition, I saw the following message.

COMMUNICATION_ERROR
java.util.concurrent.TimeoutException: Total timeout 30000 ms elapsed

Before it went offline I switched the debug mode to DEBUG but there is nothing in. I switched the binding on again and switch the mode to TRACE see what we will get with this. Perhaps this is related to Energy Forecast Binding - #24 by fregger65 ?

2026-03-01 13:00:00.537 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Fetch new prices? Empty=false Hour13<=13

2026-03-01 13:00:00.537 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Fetching new prices from 2026-02-25T23:00:00Z to 2026-03-02T23:00:00Z

2026-03-01 13:00:00.537 [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=10Y1001A1001A82H&out_domain=10Y1001A1001A82H&periodStart=202602252300&periodEnd=202603022300

2026-03-01 13:00:30.538 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Day-ahead check: true

2026-03-01 13:00:30.539 [DEBUG] [ntsoe.internal.handler.EntsoeHandler] - Get TimeSeries for 476 entries and target duration PT15M
2

I don’t think so. These are simple REST API requests towards different urls.

This is a pitch perfect query at 13:00 (your update hour) to get day-ahead prices

  • EntsoeHandler] - Fetching new prices => query 500 ms after 13:00
  • EntsoeHandler] - Day-ahead check: true => immediately day-ahead prices are received

After this normally entsoe binding sleeps till 2nd March 13:00 to check again.
Is your communication error due to a reboot? Or disabled thing?
Do you have inmemory configured and the previous values got lost?

Nevertheless you should see the above traces again and again due to retries but with different results, right?

3

@weymann Thanks for the feedback and, of course, the binding!

You’re probably right.

To be honest, I didn’t look at it, so I don’t know if it worked after the last restart/deactivation, sorry.

I save the item in infulxdb, strategy forecast.

I’ll see what happens today at 13:00 (with debug mode TRACE), thank you.

4

Everything went well today. I’ll keep an eye on it.

2026-03-02 13:00:00.248 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Fetch new prices? Empty=false Hour13<=13
2026-03-02 13:00:00.248 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Fetching new prices from 2026-02-26T23:00:00Z to 2026-03-03T23:00:00Z
2026-03-02 13:00:00.249 \[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=10Y1001A1001A82H&out_domain=10Y1001A1001A82H&periodStart=202602262300&periodEnd=202603032300
2026-03-02 13:00:30.250 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Day-ahead check: false
2026-03-02 13:01:30.250 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Fetch new prices? Empty=false Hour13<=13
2026-03-02 13:01:30.250 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Fetching new prices from 2026-02-26T23:00:00Z to 2026-03-03T23:00:00Z
2026-03-02 13:01:30.250 \[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=10Y1001A1001A82H&out_domain=10Y1001A1001A82H&periodStart=202602262300&periodEnd=202603032300
2026-03-02 13:02:00.252 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Day-ahead check: false
2026-03-02 13:03:00.252 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Fetch new prices? Empty=false Hour13<=13
2026-03-02 13:03:00.252 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Fetching new prices from 2026-02-26T23:00:00Z to 2026-03-03T23:00:00Z
2026-03-02 13:03:00.252 \[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=10Y1001A1001A82H&out_domain=10Y1001A1001A82H&periodStart=202602262300&periodEnd=202603032300
2026-03-02 13:03:06.608 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Day-ahead check: false
2026-03-02 13:04:06.608 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Fetch new prices? Empty=false Hour13<=13
2026-03-02 13:04:06.609 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Fetching new prices from 2026-02-26T23:00:00Z to 2026-03-03T23:00:00Z
2026-03-02 13:04:06.609 \[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=10Y1001A1001A82H&out_domain=10Y1001A1001A82H&periodStart=202602262300&periodEnd=202603032300
2026-03-02 13:04:09.009 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Fetched 476 price entries
2026-03-02 13:04:09.009 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Day-ahead check: true
2026-03-02 13:04:09.009 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Get TimeSeries for 476 entries and target duration PT15M
2026-03-02 13:04:09.009 \[DEBUG\] \[internal.client.EntsoeDocumentParser\] - Transforming Duration PT15M to PT15M
2026-03-02 13:04:09.054 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - TimeSeries from 2026-02-26T23:00:00Z to 2026-03-03T22:45:00Z
2026-03-02 13:04:09.123 \[DEBUG\] \[ntsoe.internal.handler.EntsoeHandler\] - Day-ahead check: true