incorrect lowest price time of day

[Mariusthvdb]

with the fixed PR in the timestamp for these sensors, this is revealed (today is dec 20th)

while it should really be like

note the timestamp is indeed 1 day off:

instead of

the correct timestamp is ,made by the custom intergration by @klaasnicolaas for the EnergyZero data

see:

[sfstar]

In what mode of calculation are you running with the integration? And to double check: the timestamp format is now ok?

[Mariusthvdb]

dont think I understand what you are asking about the mode of calculation.

(timestamp seems to be ok, that is, it is showing in the frontend correctly. only a day off ;-)

see this:

it just doesnt check todays prices and seems to go back a full day.

which is remarkable, because when I select 48 hours, these are not ready yet, and only todays prices are available:

[sfstar]

@Mariusthvdb you can find the selected calculation method in the options menu that you can access via the configure button on the entsoe integration. Should look like this:

Based on your selected method this could be related to #77 and #98

[JaccoR]

I am in publish and i am having the same problem. Would choosing another calculation method fix this? The calculation method introduced some difficulties. I think #99 also has something to do with it.

[klaasnicolaas]

The hourprices list you get in the _filter_calculated_hourprices function, does it consist of data from multiple days?

[JaccoR]

Highest price is also incorrect and therefore the percentage is also incorrect.

[lfdmn]

The hourprices list you get in the _filter_calculated_hourprices function, does it consist of data from multiple days?

If I understand the code correctly, if self.calculation_mode == CALCULATION_MODE["publish"] it'll return data for 72h or 48h which makes these guys incorrect if you expect the values to be for the current day?

            "min_price": self.get_min_price(filtered_hourprices),
            "max_price": self.get_max_price(filtered_hourprices),
            "avg_price": self.get_avg_price(filtered_hourprices),
            "time_min": self.get_min_time(filtered_hourprices),
            "time_max": self.get_max_time(filtered_hourprices),

Or is this on purpose?

[martin3000]

I'm in publish mode and the "sensor.entsoe_highest_energy_price_today" is showing a price for tomorrow. Also, sensor.entsoe_time_of_highest_price_today is for tomorrow.