Entsoe prices assigned to wrong day

[rwegnerGermany]

Describe the bug

When using entsoe for BZN|DE-LU, todays prices are assigned to tomorrow. Please see these examples:

The problem seems to occur only in the afternoon when the response comprises 48h of price data. Pleas find attached a entsoe response from 15:00 local time. Energy_Prices_202410091400-202410101400.txt

Now in the evening after evcc restart no current prices are shown and data seems to be one day off because Thursday 20:00, for example should be 31.8 ct instead of > 33 ct:

Please also see discussions: https://github.com/evcc-io/evcc/issues/16519 https://github.com/evcc-io/evcc/discussions/16539

(Sorry for not testing any nightly build, but I think v0.130.13 is up to date in this regard.)

Steps to reproduce

1. Configure Entsoe template as grid tariff with BZN|DE-LU
2. start evcc
3. wait until afternoon when tomorrows prices are published ...

Configuration details

tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    type: template
    template: entsoe
    domain: BZN|DE-LU
    securitytoken: xxx # api token
    charges: 0.16672 #0.1984 minus 19% # optional, additional charges per kWh
    tax: 0.19 # optional, additional tax (0.1 for 10%)

Log details

[entsoe] TRACE 2024/10/09 20:44:58 GET https://web-api.tp.entsoe.eu/api?DocumentType=A44&In_Domain=10Y1001A1001A82H&Out_Domain=10Y1001A1001A82H&PeriodEnd=202410102000&PeriodStart=202410092000&securityToken=***

...the response is truncated in my log, but please see attached file as an example.
No further log items to find regarding this topic.

What type of operating system are you running?

Docker container

Nightly build

• [X] I have verified that the issue is reproducible with the latest nightly build

Version

0.130.13

[andig]

Screenshots are useless without the log data.

[rwegnerGermany]

here is the trace log, but the entsoe response is truncated evcc-20241009-222649-trace.log

especially the log doesn't show the fact, that there are 2 Period sections within the single Timeseries section in the response. Please refer to the intro post for a the full entsoe response for the given query.