Support 15-minute MTU

[jpulakka]

https://www.nordpoolgroup.com/en/trading/transition-to-15-minute-market-time-unit-mtu/

Spot prices are calculated on 15 minute intervals starting from 11.6.2025.

How to handle this on nordpool_diff depends on how exactly https://github.com/JaccoR/hass-entso-e and https://github.com/custom-components/nordpool shall handle this.

[xoferz]

Is there a status update on this?
We are switching to 15 minute resolution tomorrow. Official Nordpool integration says that they support it.

[jpulakka]

Is there a status update on this?
We are switching to 15 minute resolution tomorrow. Official Nordpool integration says that they support it.

I will look into this during this week, when we see how exactly Nordpool and Entsoe output the 15 min readings.

[ahammas]

Seem to be working.

[jyrkij]

Seem to be working.

Is this the nordpool integration? AFAIK Entso-e is still missing 15min support.

[ahammas]

Yes this is nordpool integration. Thought that was what was discussed.

[victorwm7]

Is there a status update on this?
We are switching to 15 minute resolution tomorrow. Official Nordpool integration says that they support it.

I will look into this during this week, when we see how exactly Nordpool and Entsoe output the 15 min readings.

I made a fix for the 15min thingy. Seems to work.
branch to sensor.py https://github.com/victorwm7/nordpool_diff/
pull request #35

[jpulakka]

Is there a status update on this?
We are switching to 15 minute resolution tomorrow. Official Nordpool integration says that they support it.

I will look into this during this week, when we see how exactly Nordpool and Entsoe output the 15 min readings.

I made a fix for the 15min thingy. Seems to work. branch to sensor.py https://github.com/victorwm7/nordpool_diff/ pull request #35

Thank you @victorwm7 !

#35 looks good, and you say it seems to work, so it's now merged, hope it helps someone!

I started looking into this by updating my very old version of nordpool to a recent version (by clicking the button in https://www.home-assistant.io/integrations/nordpool/ instead of copying stuff from github to custom_components), and now my HASS is in a state where neither NordPool nor ENTSO-E works, either at all, or with nordpool_diff X-) Entso-e was reportedly fixed in JaccoR/hass-entso-e#244, but things there seem to be in a somewhat volatile state, so I won't stress about fixing this immediately. Overall, this issue #33 is a bit complex and needs some thinking, for many reasons:

• Some internal details of the official nordpool integration apparently changed at some point in time, and I'm not sure if it's compatible with nordpool_diff now. I'm tired of breaking changes, and thinking to build just getting the damn prices into nordpool_diff itself, so that it would work without any dependencies. It should be fairly easy, https://gist.github.com/jpulakka/f866e37dcedeede31e96a34e9f06ed7a
• filter_length defines how many hours to consider. But should we now change that to define how many quarter hours to consider (goodbye backward compatibility), or keep the adjustment granularity 1 hour (but multiply by 4 under the hood and ensure that calculations are performed with 15-minute resolution!)?
• Even though market pricing moved to 15 minutes now, some customers are still charged by 1 hour granularity, due to old meters. Optimizing consumption for one doesn't optimize for the other. Perhaps we should have configurable 15/60-minute pricing?

[xoferz]

• Even though market pricing moved to 15 minutes now, some customers are still charged by 1 hour granularity, due to old meters. Optimizing consumption for one doesn't optimize for the other. Perhaps we should have configurable 15/60-minute pricing?

I would say that is highly preferable. Even if I do have 15 minute pricing, I would highly appreciate an opportunity to configure some sensors at 15 minute resolution and some at 1 hour resolution. Perhaps introduce a filter_resolution parameter?

Use case:

• I would use a sensor with 15 minute resolution for devices that react instantly, e.g. relay
• I would use a sensor with 1 hour resolution for slow devices, e.g. ground heat pump. There is absolutely no point in controlling the heat pump with 15 minute precision as it takes 10-20 minutes to spin up or down.

[Heronimonimo]

Is there a status update on this?
We are switching to 15 minute resolution tomorrow. Official Nordpool integration says that they support it.

I will look into this during this week, when we see how exactly Nordpool and Entsoe output the 15 min readings.

I made a fix for the 15min thingy. Seems to work. branch to sensor.py https://github.com/victorwm7/nordpool_diff/ pull request #35

Thank you @victorwm7 !

#35 looks good, and you say it seems to work, so it's now merged, hope it helps someone!

I started looking into this by updating my very old version of nordpool to a recent version (by clicking the button in https://www.home-assistant.io/integrations/nordpool/ instead of copying stuff from github to custom_components), and now my HASS is in a state where neither NordPool nor ENTSO-E works, either at all, or with nordpool_diff X-) Entso-e was reportedly fixed in JaccoR/hass-entso-e#244, but things there seem to be in a somewhat volatile state, so I won't stress about fixing this immediately. Overall, this issue #33 is a bit complex and needs some thinking, for many reasons:

• Some internal details of the official nordpool integration apparently changed at some point in time, and I'm not sure if it's compatible with nordpool_diff now. I'm tired of breaking changes, and thinking to build just getting the damn prices into nordpool_diff itself, so that it would work without any dependencies. It should be fairly easy, https://gist.github.com/jpulakka/f866e37dcedeede31e96a34e9f06ed7a
• filter_length defines how many hours to consider. But should we now change that to define how many quarter hours to consider (goodbye backward compatibility), or keep the adjustment granularity 1 hour (but multiply by 4 under the hood and ensure that calculations are performed with 15-minute resolution!)?
• Even though market pricing moved to 15 minutes now, some customers are still charged by 1 hour granularity, due to old meters. Optimizing consumption for one doesn't optimize for the other. Perhaps we should have configurable 15/60-minute pricing?

Great work!

Would it be possible to make a release including this fix such that we can easily update the integration via HACS? And is Nordpool the default sensor when both Nordpool and ENTSO-E are configured?

[jpulakka]

Would it be possible to make a release including this fix such that we can easily update the integration via HACS?

Now there's https://github.com/jpulakka/nordpool_diff/releases/tag/v0.3.0-beta.1

Please let me know how it works and how it doesn't.

And is Nordpool the default sensor when both Nordpool and ENTSO-E are configured?

It's a bit complicated, documented in https://github.com/jpulakka/nordpool_diff?tab=readme-ov-file#entso-e-vs-nord-pool

If you want to ensure that only one of them is used, you need to remove the other.

[jpulakka]

Ok, I realized now that there exist (at least) two flavors of HASS NordPool integrations, also discussed in custom-components/nordpool#451:

1. https://github.com/custom-components/nordpool, seems to work with nordpool_diff v0.3.0-beta.1
2. The official https://www.home-assistant.io/integrations/nordpool, does not work with nordpool_diff. Its "Current price" sensor doesn't provide the required "Today" and "Tomorrow" attributes. Apparently, there would be a way to get these by creating a trigger sensor using a trigger template or whatever. Feel free to try, but I'm not going to spend effort on this when options, that work without customizations, exist.

https://github.com/JaccoR/hass-entso-e has not released a working version yet, keeping eye on JaccoR/hass-entso-e#244 before proceeding to make changes to nordpool_diff.

[xoferz]

1. https://github.com/custom-components/nordpool, seems to work with nordpool_diff v0.3.0-beta.1

I am not sure the custom nordpool integration is maintained any more. Last update half a year ago and issues piling up.

[jpulakka]

1. https://github.com/custom-components/nordpool, seems to work with nordpool_diff v0.3.0-beta.1

I am not sure the custom nordpool integration is maintained any more. Last update half a year ago and issues piling up.

The irony is that the custom nordpool intergration is the only one of the three that currently both 1) works and 2) provides not only the current price but also the future prices out of the box :D

"Issues piling up" is also a signal that people actually use it.

[xoferz]

The irony is that the custom nordpool intergration is the only one of the three that currently both 1) works and 2) provides not only the current price but also the future prices :D

I totally see your reasoning.

The trouble is, it does not actually work. I mean, it may work as a source for nodrpool_diff, but there are issues elsewhere. Its current price sensor updates only hourly. And it is not even an average of the four 15 minute intervals, just the price of the first interval.

Last release in 12/24, last merge 05/25. I mean, even Estonian VAT from 22 to 24 patch is not even merged. I moved to to official Nordpool integration and can query tomorrow's prices, but unfortunately had to ditch nordpool_diff in the process :-(

YMMV of course.