Incorrect Average price

[MsEDok]

Version of the custom_component

0.0.17

Homeassistant version

2025.10.2

Configuration

sensor:
  - platform: nordpool
    region: "SE3"
    currency: "SEK"
    VAT: False
    precision: 6
    low_price_cutoff: 0
    price_in_cents: false
    price_type: kWh
    additional_costs: "{{0.0|float}}"

Describe the bug

i setup 2 ha instance and i have one runnign this config for awhile
i check the average price for first instance that have been running for awhile 0,591214 SEK/kWh
i check the average price for second instance that have just added the component 0.5904775 SEK/kWh

i check nordpool Average: 590,48 which is 0.59047 SEK/kWh

so somehow the first instance get the incorrect data. if i were to remove the first instance then readd it i get the correct aerage

[Tazzios]

The avg, min and max attributes are calculated on the current day. So they do not take in account the prices of tomorrow.
avg, min and max are spot on today here.

As improvement, the naming maybe could changed in:
today_avg
today_min
today_max

And additional maybe:
tomorrow_avg
tomorrow_min
tomorrow_max

For knowing if I should charge my battery overall future attributes would be nice. This future should disregard all the prices/hours that already have past today and also takes tomorrow prices if they are known.
Future_avg
Future_min
Future_max

[martin3000]

And the mean price is in fact the median.

[Hellowlol]

Hi,

Yeah, there is a bug in in the calculation after the switch from hourly to quartly prices.

Relevant code this here:
https://github.com/custom-components/nordpool/blob/master/custom_components/nordpool/sensor.py#L317-L320

[Asse3]

Hi,

Yeah, there is a bug in in the calculation after the switch from hourly to quartly prices.

Relevant code this here: https://github.com/custom-components/nordpool/blob/master/custom_components/nordpool/sensor.py#L317-L320

I'm a total newbie at programming but it seems that code just look at the posts [0:8] in the price-list and not at the actual time/hour. I tried to multiply all number with 4 (for quaters sin e there are 96 posts in the list now instead of 24), seems I'll get a bit more accurate values now, but as mentioned I dont now anything about programming, just a great copy-paster