OH4.2 Tibber Binding: "shall process timeseries" multiple logentries

Add-ons Bindings
,
1

Using openHAB 4.2.0 release on openHABian.

Since upgrading to 4.2 everytime the “Current total price” of tibber gets updated I receive a lenghty entry in the logs:

2024-07-19 09:24:35.118 [INFO ] [openhab.event.ItemTimeSeriesEvent   ] - Item 'TIB_Current_Total_Price' shall process timeseries [Entry[timestamp=2024-07-18T22:00:00Z, state=0.2934], Entry[timestamp=2024-07-18T23:00:00Z, state=0.2819], Entry[timestamp=2024-07-19T00:00:00Z, state=0.2812], Entry[timestamp=2024-07-19T01:00:00Z, state=0.2805], Entry[timestamp=2024-07-19T02:00:00Z, state=0.2854], Entry[timestamp=2024-07-19T03:00:00Z, state=0.2949], Entry[timestamp=2024-07-19T04:00:00Z, state=0.3237], Entry[timestamp=2024-07-19T05:00:00Z, state=0.3179], Entry[timestamp=2024-07-19T06:00:00Z, state=0.3032], Entry[timestamp=2024-07-19T07:00:00Z, state=0.283], Entry[timestamp=2024-07-19T08:00:00Z, state=0.2694], Entry[timestamp=2024-07-19T09:00:00Z, state=0.256], Entry[timestamp=2024-07-19T10:00:00Z, state=0.2389], Entry[timestamp=2024-07-19T11:00:00Z, state=0.2296], Entry[timestamp=2024-07-19T12:00:00Z, state=0.2292], Entry[timestamp=2024-07-19T13:00:00Z, state=0.2368], Entry[timestamp=2024-07-19T14:00:00Z, state=0.262], Entry[timestamp=2024-07-19T15:00:00Z, state=0.2782], Entry[timestamp=2024-07-19T16:00:00Z, state=0.2951], Entry[timestamp=2024-07-19T17:00:00Z, state=0.3301], Entry[timestamp=2024-07-19T18:00:00Z, state=0.4128], Entry[timestamp=2024-07-19T19:00:00Z, state=0.3289], Entry[timestamp=2024-07-19T20:00:00Z, state=0.3133], Entry[timestamp=2024-07-19T21:00:00Z, state=0.2951]]
2024-07-19 09:24:35.127 [INFO ] [hab.event.ItemTimeSeriesUpdatedEvent] - Item 'TIB_Current_Total_Price' updated timeseries [Entry[timestamp=2024-07-18T22:00:00Z, state=0.2934], Entry[timestamp=2024-07-18T23:00:00Z, state=0.2819], Entry[timestamp=2024-07-19T00:00:00Z, state=0.2812], Entry[timestamp=2024-07-19T01:00:00Z, state=0.2805], Entry[timestamp=2024-07-19T02:00:00Z, state=0.2854], Entry[timestamp=2024-07-19T03:00:00Z, state=0.2949], Entry[timestamp=2024-07-19T04:00:00Z, state=0.3237], Entry[timestamp=2024-07-19T05:00:00Z, state=0.3179], Entry[timestamp=2024-07-19T06:00:00Z, state=0.3032], Entry[timestamp=2024-07-19T07:00:00Z, state=0.283], Entry[timestamp=2024-07-19T08:00:00Z, state=0.2694], Entry[timestamp=2024-07-19T09:00:00Z, state=0.256], Entry[timestamp=2024-07-19T10:00:00Z, state=0.2389], Entry[timestamp=2024-07-19T11:00:00Z, state=0.2296], Entry[timestamp=2024-07-19T12:00:00Z, state=0.2292], Entry[timestamp=2024-07-19T13:00:00Z, state=0.2368], Entry[timestamp=2024-07-19T14:00:00Z, state=0.262], Entry[timestamp=2024-07-19T15:00:00Z, state=0.2782], Entry[timestamp=2024-07-19T16:00:00Z, state=0.2951], Entry[timestamp=2024-07-19T17:00:00Z, state=0.3301], Entry[timestamp=2024-07-19T18:00:00Z, state=0.4128], Entry[timestamp=2024-07-19T19:00:00Z, state=0.3289], Entry[timestamp=2024-07-19T20:00:00Z, state=0.3133], Entry[timestamp=2024-07-19T21:00:00Z, state=0.2951]]

This happens every minute and since the value doesn’t change for a whole day this blows up my logging now. Is there something I can do to reduce the logging for that?

it’s “standard”-integration:

thing:
UID: tibber:tibberapi:pl12
label: Tibber API
thingTypeUID: tibber:tibberapi
configuration:
  refresh: 1
  homeid: xxx
  token: yyyy
channels:
  - id: current_total
    channelTypeUID: tibber:price
    label: Current Total Price
    description: "Total Price: Energy + Tax"
    configuration: {}
...

item:
label: Strompreis
type: Number:Dimensionless
category: ""
groupNames:
  - TibberAPI
tags:
  - Point

thanks!

2

If you don’t need the time series events at all you can turn them off. Set openhab.event.ItemTimeSeriesEvent and openhab.event.ItemTimeSeriesUpdateEvent to ERROR level logging and those events will be suppressed in events.log. There are already a lot of events which are not logged there so turning these off shouldn’t be a big deal.

Since there is an ItemTimeSeriesUpdatedEvent, there might also be an ItemTimeSeriesChangedEvent. So watch out for that too.

1 Like
3

ok, just to be on board: if an item is capable of TimeSeries (as my pricing information for future prices is), there’ll always be that info shall process and updated timeseries?

I only need a change of the item (which in my case is every 24h), and that one will be logged regardless, I think?

4

IMO the binding should only send a new TimeSeries if something changed. Since this will probbaly persisted, it creates unnecessary load to update with the same value.

5

So, this can (and should) be managed within the binding, that only chances lead to those entries? Then I’ll post it in the thread of the tibber binding…

1 Like
6

Yes. Those are events that are put on the event bus and if you don’t explicitely suppress them by changing the logging level you will see those entries every time the event occurs for every Item.

The only way to change events.log on a per Item basis would be to set up filtering (Log filtering in OH 3). events.log is the logger for the event bus itself.

I completely agree.

1 Like