Tibber binding - Reduce sub-second refresh rate to reduce log spam

Cplant · November 30, 2025, 12:03pm

I’m running openHAB 5.0.3 and the official Tibber item. Since using this binding, my openHAB log looks like this (95% of all entries are from tibber):

2025-11-30 12:59:13.853 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_LastMeterConsumption’ changed from 6944.3949 kWh to 6944.3978 kWh
2025-11-30 12:59:13.853 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedConsumption’ changed from 12.8876 kWh to 12.8905 kWh
2025-11-30 12:59:13.853 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedCost’ changed from 4.106348 EUR to 4.107312 EUR
2025-11-30 12:59:13.853 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_Power’ changed from 2763.1 W to 2602.28 W
2025-11-30 12:59:16.814 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_LastMeterConsumption’ changed from 6944.3978 kWh to 6944.3993 kWh
2025-11-30 12:59:16.815 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedConsumption’ changed from 12.8905 kWh to 12.892 kWh
2025-11-30 12:59:16.817 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedCost’ changed from 4.107312 EUR to 4.107811 EUR
2025-11-30 12:59:16.819 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_Power’ changed from 2602.28 W to 2596.47 W
2025-11-30 12:59:18.221 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Stromzaehler_Electricmeterwatts’ changed from 2541.228 to 2691.842
2025-11-30 12:59:18.315 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Stromzaehler_Electric_meter_watts_2’ changed from 167.225 to 322.548
2025-11-30 12:59:19.758 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_LastMeterConsumption’ changed from 6944.3993 kWh to 6944.4023 kWh
2025-11-30 12:59:19.759 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedConsumption’ changed from 12.892 kWh to 12.895 kWh
2025-11-30 12:59:19.761 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedCost’ changed from 4.107811 EUR to 4.108809 EUR
2025-11-30 12:59:19.761 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_Power’ changed from 2596.47 W to 2672.41 W
2025-11-30 12:59:22.491 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Flur_Bewegungsmelder_Motion’ changed from ON to OFF
2025-11-30 12:59:23.180 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_LastMeterConsumption’ changed from 6944.4023 kWh to 6944.4054 kWh
2025-11-30 12:59:23.180 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedConsumption’ changed from 12.895 kWh to 12.8981 kWh
2025-11-30 12:59:23.181 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedCost’ changed from 4.108809 EUR to 4.109839 EUR
2025-11-30 12:59:23.181 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_Power’ changed from 2672.41 W to 2712.94 W
2025-11-30 12:59:26.095 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_LastMeterConsumption’ changed from 6944.4054 kWh to 6944.4068 kWh
2025-11-30 12:59:26.095 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedConsumption’ changed from 12.8981 kWh to 12.8995 kWh
2025-11-30 12:59:26.096 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedCost’ changed from 4.109839 EUR to 4.110305 EUR
2025-11-30 12:59:26.096 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_Power’ changed from 2712.94 W to 2700.65 W
2025-11-30 12:59:29.048 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_LastMeterConsumption’ changed from 6944.4068 kWh to 6944.4098 kWh
2025-11-30 12:59:29.049 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedConsumption’ changed from 12.8995 kWh to 12.9025 kWh
2025-11-30 12:59:29.049 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedCost’ changed from 4.110305 EUR to 4.111303 EUR
2025-11-30 12:59:29.050 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_Power’ changed from 2700.65 W to 2730.64 W
2025-11-30 12:59:32.211 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Wechselrichter_Wechselrichter_Power’ changed from 19.9 W to 19.7 W
2025-11-30 12:59:32.243 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Wechselrichter_Wechselrichter_CH1_Power’ changed from 11.3 W to 11.1 W
2025-11-30 12:59:32.302 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Wechselrichter_Wechselrichter_Efficiency’ changed from 95.673 to 95.631
2025-11-30 12:59:32.482 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_LastMeterConsumption’ changed from 6944.4098 kWh to 6944.4114 kWh
2025-11-30 12:59:32.482 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedConsumption’ changed from 12.9025 kWh to 12.9041 kWh
2025-11-30 12:59:32.483 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedCost’ changed from 4.111303 EUR to 4.111835 EUR
2025-11-30 12:59:32.483 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_Power’ changed from 2730.64 W to 2741.99 W
2025-11-30 12:59:33.733 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Stromzaehler_Electricmeterwatts’ changed from 2691.842 to 2547.318
2025-11-30 12:59:33.827 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Stromzaehler_Electric_meter_watts_2’ changed from 322.548 to 166.831
2025-11-30 12:59:35.430 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_LastMeterConsumption’ changed from 6944.4114 kWh to 6944.4144 kWh
2025-11-30 12:59:35.430 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedConsumption’ changed from 12.9041 kWh to 12.9071 kWh
2025-11-30 12:59:35.431 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedCost’ changed from 4.111835 EUR to 4.112832 EUR
2025-11-30 12:59:35.431 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_Power’ changed from 2741.99 W to 2607.18 W
2025-11-30 12:59:38.387 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_LastMeterConsumption’ changed from 6944.4144 kWh to 6944.4158 kWh
2025-11-30 12:59:38.387 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedConsumption’ changed from 12.9071 kWh to 12.9085 kWh
2025-11-30 12:59:38.387 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedCost’ changed from 4.112832 EUR to 4.113298 EUR
2025-11-30 12:59:38.387 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_Power’ changed from 2607.18 W to 2601.49 W
2025-11-30 12:59:41.320 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_LastMeterConsumption’ changed from 6944.4158 kWh to 6944.4187 kWh
2025-11-30 12:59:41.321 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedConsumption’ changed from 12.9085 kWh to 12.9114 kWh
2025-11-30 12:59:41.321 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_AccumulatedCost’ changed from 4.113298 EUR to 4.114262 EUR
2025-11-30 12:59:41.321 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Tibber_Live_Power’ changed from 2601.49 W to 2610.23 W

This has two downsides:

My logs are flooded (it’s hard to see other things anymore)
It consumes more DB-space in my persistence (influxDB 1.8) than needed. Sub-minute updates appear like a waste.

From what I could see, I could at least reduce the logging spam via log:set WARN openhab.event.ItemStateChangedEvent.Tibber_Live, but that does not solve the DB-space-problem.

Does anyone have an idea?

mstormi · November 30, 2025, 12:11pm

As WARN once has been the default setting anyway, why don’t you just go back there?

Database, you don’t have to persist all items let alone on any change. You can switch to everyMinute strategy. Or to a different database. This would not be an issue if you still were with the default rrd4j. You can even define which DB to use per-item if you insist on having both.

rlkoshak · December 1, 2025, 3:22pm

I don’t think that would work. But please do try it and report back if it does.

This log isn’t coming from the binding. It’s coming from the event bus.

Also, I see three Items changing once every two to three seconds or so, not subsecond. Every 2-3 seconds is not unreasonable.

Assuming this cannot be configured from the binding itself, given these changes are very small, and apparently you don’t actually care about changes that are this small, one approach you can do is to use one of the Debounce, Round, or State Filter profiles to reduce the number of changes that make it to the Item. These will either limit how often the Item is changed based on time or based on the size of the delta between the new state and the old state.

Or you can use a REGEX filter on the logger itself to just exclude events from these Items from events.log.

For the database, in addition to what @mstormi suggested, you can apply filters (e.g. a threshold or time based filter) to reduce the data being written to the database.

But it seems to me that the log statements in events.log, the events that trigger your rules, and the data stored in persistence should match. So I would recommend in order of preference:

configure the binding to produce less data
use a profile to limit the number of changes that make it to the Items in the first place
configure your persistence so it doesn’t matter if there are lots of changes (e.g. use rrd4j, or don’t save these Items)

weymann · December 2, 2025, 6:55pm

Took me some time to think this through but I think you have a good point here!

Step-by-step

Refresh rate
The binding is opening a connection to Tibber and they push the live values. There’s nothing to configure like slower refresh rate.
Persistence config
Like @mstormi and @rlkoshak mentioned. Do you really need items like Tibber_Live_AccumulatedCost in your long time Storage?
I personally hand-pick selective items which shall be stored in influxdb, like all my inverter values, plugs with power measurement, temperatures, …
Use profiles
Mentioned by @rlkoshak I think this is the best choice.

The values like Tibber_Live_AccumulatedCost can be limited with the present Debounce Time Profile - this is working.

For items like Tibber_Live_Power I would like to have an average of the delivered values in a configurable time frame.

Let me evaluate this with new transformation time-weigthed-average.