Prices are not mapped correctly because of entsoe api changes

[Roeland54]

The api response of the entsoe api has changed format and will not contain the price of a specific hour (position) if the price is the same as the previous hour. So currently it is possible that the data provided by the integration contains gaps or is not able to show the pricing at al. So based on the resolution of the dataset the empty spots should be filled with correct price.

Besides that change I have observed that the price for tomorrow in Belgium is not returned in the usual 60min resolution but in the 15min resolution instead. While the response for the Netherlands is returning everything in 60min resolution like expected.
followup for this issue in #195

[RudyDevroey]

Belgian here, since midnight the sensor is unavailable.

[XalaTheShepard]

Last update fixed it for Belgian sensors, but indeed as of midnight unavailable again.

[Roeland54]

So looking at the response of the api now. It looks like the prices for tomorrow are back to the expected 60min resolution. This could have been a one of mistake. I think this will fix itself tomorrow.

[Pluimvee]

Resolved the missing hours issue in a fork

[XalaTheShepard]

Dear all, the issue is still present and has not resolved itself as was expected. For the Belgian sensors the data is still not pushed through. If I can help you providing more information, please let me know. Kind regards, Robin

[Roeland54]

As the Belgian data issue is separate from the change of the curvetype I have create a separate issue to followup: #195

[Roeland54]

There is a beta version you can install from hacs: v0.6.3-beta1