Busy times caused a larger delay and me not being able to provide the binding in time for release of 4.2, sorry about that, but I’m happy to say that I have a release candidate now. Would be nice to get some feedback on it.
This is my repo, I will make a pull request to openHAB repo as soon as it is tested some more and I’ve finished up on the readme and translations.
I tried adding the jar and I’ve got both freecurrency:info and entsoe:dayAhead Things showing green ONLINE status, but the Spot Price item shows UNDEF. What might I have missed? (I also only have a single prices channel which don’t seem to match above.)
Did you add a exchange-rate channel to freecurrency from EUR to your base currency? And also did you specify freecurrency as the default currency provider in system settings of openhab? Which area are you trying to read data from?
Thanks, nope sorry, missed a few of those.
Only set Base Currency in the first place I saw it, in Freecurrency binding. (SEK)
Now I’ve also set Settings > Unit Settings > Currency Provider to Freecurrency API
and Settings > Unit Settings > Fixed Base Currency to SEK
and created Exchange Rate channel item(s) (SEK->EUR and EUR->SEK).
But item still shows UNDEF.
Do I need to trigger a re-read/re-calc somehow?
I’m using area 10Y1001A1001A46L.
After changing/adding those I believe you will need to make the binding try to read data from entsoe again. It doesnt monitor for those changes. So either disable the entsoe-thing and enable it again so it initializes over again, or restart openhab. Did that help?
I restarted OpenHAB and Spot Price showed as NULL.
Checking Things, entsoe said “Could not get exchange rate. Have you configured a currency binding to fetch currency rates and set your base currency?”
Settings > Unit Settings are still ok.
The exchange rate channels show correct values.
Did disable and enable on entsoe Thing and it now shows ONLINE.
Spot price still NULL though.
Changed the logging level on my side and it looks promising.
There are exchange rates and converted values but first value is “Datetime: 2024-08-19T22:00:00Z, base value: 0.00422 EUR/kWh, converted value: 0.0485494237 SEK/kWh” which would be midnight tonight. So things will work from midnight, possibly?
Ok, so probably an issue with which data that is downloaded, I will adjust that… Yeah, will probably work from midnight… Thanks for looking into it and providing logs!
Thank you for all your effort in updating this binding and making it an official addon
Really, really appreciate your work.
I am using the binding now for ~1 week and i noticed that it is not auto-updating the prices. They remain old and i need to restart the binding. Is this somehow known? Sadly the logs remain silent at around 14:00 when the update is expected to happen. Nothing is happening.
When i do manually stop and start the binding all values are updated and processed and no errors are logged.
All fine. Thx for the update! What i immediately noticed, is that the reported prices for the current hour are not correct. Do i now need to set somewhere my current timezone? Seems that now UTC is used?
Ah damn i now realize what is happening. The binding had before some settings to apply VAT and to apply the base price that i need to pay in addition to the hourly price. Those settings now seem to be gone. @jmelhus: Can you confirm that? Is that intentionally? That was actually a great feature.
Is there some docu how this should now be done?
It will by default update the prices at 13:00 CET/CEST time (central european time, day light saving taken into account). If you set another time within the binding, you should specify this value in CET/CEST time. Also check what Markus Storm is mentioning, if your java is running the correct timezone…
I added a review comment. IMHO the code is wrong and delivers the wrong prices for the current time. This is also what i am noticing.
For VAT and SUM i still need to figure out how this is supposed to work since i directly store the value in Influx so that i can visualize it in Grafana. Sadly way more complicated than before.
You are right about SUM, but not about VAT, in terms of being “way more complicated” than before.
For VAT you just need to install the VAT profile and select it for your item, and your item will be persisted with VAT exactly as before.
For SUM, you need to create a group with your items as child items, which in itself is more complicated than just adding a fixed amount in the configuration. However, it is also more flexible and allows you to add dynamic tariffs and other price components (even from other bindings) as well. You can still persist your group item and it will work as before, but unfortunately time series are not supported, so you cannot visualize future total prices out-of-the-box:
