This sounds like a really good idea! With energy field it should also be possible to identify negative energy prices despite the total price is positive.
So at the end it’ll end up into:
price#total - price to pay to Tibber
price#spot - pure energy market price
price#tax - tax and extra costs like described in Tibber API
since upgrading to openHAB 5.0 my tibber integration won’t work correct. I’ve recreated all items - but the spot-price channel only has value null.
So i’ve just installed the oh5 version from marketplaces. All values (including total price, tax and price level) are working fine, but spot-prices and average price are only showing null.
Nothing inside the log files (i don’t even have the possibility to change the log level for tibber binding within the settings, is this correct?). All items from the price-group are configured within persistence configuration to store forecast values.
Do you see something in /var/log/openhab/events.log like 2025-08-29 13:00:32.208 [INFO ] [hab.event.ItemTimeSeriesUpdatedEvent] - Item 'Tibber_API_Spot_Price' updated timeseries with 48 values.
If yes the data is there. Which persistence do you use to store forecast data and can you show your config?
Hi @weymann
just a heads up, I experienced the exact same thing as Sönke. What I did this morning was:
in short:
unlink all items from the binding
remove the thing
remove the (core) Tibber binding
install the (core) Tibber binding
linked all (existing) items again
This resulted at first in the same thing happening: all live-items got updated, but spot-price, level and average24h stayed the same value, even though there were the “shall process timeseries” entries in the events.log (see the hidden details in my above post).
After a while and after 13:00h it reverted to normal and all three TimeSeries items got updated as expected. Nothing really in the logs (even though I set the binding to TRACE).
Oh. I just found out, that it already did change at 12:00h, sorry wasn’t aware of that. that happens to be the next full hour after I did those remove und re-install things.
2025-08-29 12:00:00.034 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'TIB_Current_Total_Price' changed from 0.1711 EUR/kWh to 0.2433 EUR/kWh
2025-08-29 12:00:00.035 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ForecastSolar_Energy_Forecast' changed from 5.6259999999999994 kWh to 7.968999999999999 kWh
2025-08-29 12:00:00.036 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ForecastSolar_Power_Forecast' changed from 2226 W to 2428 W
2025-08-29 12:00:00.037 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'TIB_SpotPrices' changed from 0.1711 EUR/kWh to 0.2433 EUR/kWh
2025-08-29 12:00:00.038 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'TIB_SpotPrices' changed from 0.1711 EUR/kWh to 0.2433 EUR/kWh
I do have both “TIB_Current_Total_Price” and “TIB_SpotPrices” linked to the #spotPrice channel. But “TIB_SpotPrices” changed value two times within a millisecond. Perhaps that’s a hint?
But then again, I just also found out, that’s happening with the ForecastSolar binding (also the core 5.0.1 and not your Marketplace one! ) also:
2025-08-29 14:00:00.094 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ForecastSolar_Power_Forecast' changed from 2469 W to 3148 W
2025-08-29 14:00:00.095 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ForecastSolar_Power_Forecast' changed from 2469 W to 3148 W
2025-08-29 14:00:00.095 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'TIB_Current_Total_Price' changed from 0.2272 EUR/kWh to 0.234 EUR/kWh
2025-08-29 14:00:00.095 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'TIB_Average24h' changed from 0.28890243055555553 EUR/kWh to 0.28870833333333334 EUR/kWh
2025-08-29 14:00:00.095 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'TIB_Current_Total_Price' changed from 0.2272 EUR/kWh to 0.234 EUR/kWh
I’m quite sensitive regarding TimeSeries because I see many problems during setup, but if it runs, it runs!
I cannot state a root cause yet but I assume the use case and it gets into technical details
Tibber thing (or other thing providing forecast) is created
Itens are attached e.g. add equipment to model and stay nullbut binding sends forecast to channel (not item) for 100%, I’m sure!
Mostly during 1st setup the items are not connected to the right persistence forecast strategy in beforehand.
Just my guess, I know I’ve done that plenty of times!
So after guidance items are attached to the correct persistence strategy
now the persistence is correct but items still stay null. Of couse: the new attached persistence hasn’t received any data yet!
the binding itsself, which is just updating channels, notitems isn’t aware of any item persistence changes
due to the fact TIbber is updating TimeSeriesonce per dayyou’ll stay a long time with null items
@jlaur We discussed several times regarding update strategy. Do you think the above analysis is correct?
There are 2 channels spot-price and spot-prices
During the official review openHAB maintainers and I discussed a lot about channel naming. In OH5 current release binding contains spot-price which delivers the total price and this is misleading as stated in community post.
Finally we agreed to stay compatible and introduce new channels.
Long story short:
Please delete thing
uninstall tibber binding
install version from Marketplace again - it contains now the final version which will be released with OH5.1
Quick question: My tibber binding sometimes stops working and only starts working again (for a couple of days) when I deactivate and then activate the tibber API-thing:
Thanks for your response. Will do / just activated trace.
What’s odd: The connection appears to be coming back, even if I don’t de-/reactivate the Thing (as seen in the most recent gap in the data: I did not de-/reactivate the Thing).
I have stopped my Tibber contract back in February and was still receiving live data without any problem. at some point in summer, my Tibber binding was stopping to receive the live data.
I reinstalled the binding, generated another token, tried the Tibber oh 5 binding and all of these without success.
from what ai helped me so far it seems that the binding fails due to some contract/subscription check. but so I am wondering that it was working for quite a long time without the contract/subscription and suddenly not any longer.
I am able to get the live data via tibbers API page and also another app (EHW+) is getting the data without any problems.
I still got my contract with Tibber, so I can’t test. But I think, the token for using the Tibber API has to be renewed once in a while. The OH-token obviously expired and the one for your other App ist still valid (but should also expire soon).
My advice would be to use a “offline” solution and replace the Tibber Pulse with an IR-reader. There’s a bunch of ootb IR-Reader available for digital meters.
have a look at the SmartMeter Binding:
not sure, if you’re german or can read german, but I did have this one before I had to replace it with the Tibber Pulse: hardware:controllers:ir-schreib-lesekopf [wiki.volkszaehler.org]. It’s much cheaper and works perfectly fine with standard eHZ or the likes.