binderth
(Thomas Binder)
September 27, 2024, 12:52pm
292
i just filed a feature request/improvement on github:
https://github.com/openhab/openhab-addons/issues/17476
to add more context:
this was the origin, that I got too many events.log entries:
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…
and then I changed the “refresh interval” to 25 minutes, which led to the behaviour, that all non-live channels refreshed “randomly”, but not “on the hour”:
I think, there’s a opportunity for improved behaviour on the tibber binding side.
following this thread:
I set the change to 25mins. My thinking was to eliminate the change every minute, which was logged excessively!
This led to the binding “rotating” also the hourly price every 25mins. So it was randomly ok for a time, but could be as much off as 25mins. I’ll try to file an improvement issue for it on github.
for the time being, I changed it to 60mins exactly on the hour, so until a…
So my suggestion is to change all the hour-related channels “on the hour” as described in the github-issue.