thanks, this looks great! I installed the .jar file and setup the binding. Its pulling the data and populating the time series - both on the DayAhead and Forecast Prices.
The issue is this offset is not applied on the DayAhead Price. It is applied on the Forecast Price. The typo is in the description text, the value needs to be entered with a dot, not a comma.
… and I have a feature request: please add a channel for hourly price - calculated based on the average of the 15min prices of a given hour of the day. That would be very helpful for some of the action I’m triggering based on the prices. And it’s a bit of a pain to do that in a rule dealing with time series.
Many thanks for this nice binding. It seems that Fraunhofer doesn’t provide yet the prices and forecasts for Finland but hopefully these will be available in the future. I’m somewhat annoyed about the electricity prices because they vary a lot here in Finland, thanks to wind energy. We have had somewhat stupid problem with the wind turbines due to freezing of blades.
Ok, maybe i18n issue.My Regional Settings is Country Germany but Langauge is English so I can share screenshots in the forum. DOT isn’t accepted in these settings so I’ve to put COMMA.
Do you have other settings?
Yes, I read about this issue. Would be ineresting to know if this is a common issue or happening only a few times.
My PV is also covered in snow now but it’s only happening here and there so it’s acceptable.
In fact they do (Pic 1)! But there’s a legal disclaimer which zones are licensed and which not (Pic 2). I hate these questions because I’m not a lawyer!
Let’s see - I removed now the restrictions to the options and you can enter FI into the Bidding zone configuration to receive prices for Finland.
Nevertheless I want to highlight entsoe binding which is already providing energy prices for Finland (Pic 3).
@ weymann, many thanks for the info. I’m just wondering why the forecast data is not available in Finland. This would be very interesting feature. I’m already using entsoe binding but if the forecast data will become available in Finland then I’ll change to this new binding.
EnergyForecast provides a commercial service, payment is needed for 96h forecast.
Creative Commons allows usage in commercial services. Seems only countries listed under CC4.0 are supported with a forecast.
thanks for the update of the .jar file. My Regional Settings is Country Deutschland and Language is Deutsch. Still, the Thing settings are in English so it accepts the dot only. I’m running OH 5.1.2 in Docker container. No idea where this is coming from
In the updated .jar I see you introduced an option for the Price Resolution. While this is great, I asked for a separate Pricing Channel so that I can have both. For overall energy cost calculations I’d like to use the 15min resolution prices while for some rules and actions triggered I’d like to use the 60min resolution prices.
Thanks!
EDIT: … ah, nerver mind - I realized the API provides both, hourly and 15min resolution. So I can get both by having 2 Things with its channels. Great!
OK, thanks. I just wonder how to get Finland into the list in your Pic 2 above. It would be really interesting to get the forecast data because the electricity prices in Finland depend mainly on wind.
Yeah, I mean the area of 60 minutes resolution pricing is now over. The native resolution for Europe is now 15 minutes, the rest is averaging.
I understand users have some legacy code which depends on this 60 min but sooner or later this should be corrected.
My proposal: Simply ask the author Moritz Mair for some background.
I placed also some questions before publishing this binding ang got an instant response.
I’ll just add that at least in Denmark I have not yet heard of any private customers being moved to contracts with 15-minute prices (I don’t even know yet if my meter already supports this, or will need a firmware upgrade). So even though you are right, averaging is still needed in order to do calculations etc. considering the actual prices being paid.
For the dayAhead data I’m receiving 96 (15min) or 24 (hourly) values only, for the current day. Shouldn’t there be values for the next day too? That’s what the API description says - 48hours, no? The time series run out at the end of the current day. For my applications I need to know next days data. The Forecast time series have more data.
@ weymann , I sent a message to Moritz and I got almost immediate response from him. His model doesn’t have the weather data yet for Finland but he is planning to add new data points some time in the future. Many thanks for your help.
I agree. Implementing different services in the same binding seems arbitrary, and could evolve into a mess as the services evolve (in different directions). It would also be hard to define the scope for such a monolithic approach.
