I experience some issues with the tibber binding in OH 3.0.1:
I can read e.g. current price and current consumption perfectly for a while, but suddenly consumption is lost, while I still get the current price:
The log says
2021-03-02 21:48:39.373 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'tibber.items'
2021-03-03 00:09:59.664 [WARN ] [ibber.internal.handler.TibberHandler] - Websocket Client Stop Exception: null
2021-03-03 02:48:01.400 [WARN ] [ibber.internal.handler.TibberHandler] - IO Exception: java.util.concurrent.TimeoutException: Total timeout 20000 ms elapsed
2021-03-03 08:00:24.500 [WARN ] [ibber.internal.handler.TibberHandler] - IO Exception: java.util.concurrent.TimeoutException: Total timeout 20000 ms elapsed
2021-03-03 09:54:33.406 [WARN ] [ibber.internal.handler.TibberHandler] - Websocket Client Stop Exception: null
2021-03-03 23:51:38.186 [WARN ] [ibber.internal.handler.TibberHandler] - Websocket Client Stop Exception: null
2021-03-04 07:00:36.024 [WARN ] [ibber.internal.handler.TibberHandler] - IO Exception: java.util.concurrent.TimeoutException: Total timeout 20000 ms elapsed
2021-03-04 08:00:24.739 [WARN ] [ibber.internal.handler.TibberHandler] - IO Exception: java.util.concurrent.TimeoutException: Total timeout 20000 ms elapsed
2021-03-04 10:00:49.833 [WARN ] [ibber.internal.handler.TibberHandler] - IO Exception: java.util.concurrent.TimeoutException: Total timeout 20000 ms elapsed
2021-03-04 12:00:21.355 [WARN ] [ibber.internal.handler.TibberHandler] - IO Exception: java.util.concurrent.TimeoutException: Total timeout 20000 ms elapsed
2021-03-04 13:01:12.760 [WARN ] [ibber.internal.handler.TibberHandler] - IO Exception: java.util.concurrent.TimeoutException: Total timeout 20000 ms elapsed
2021-03-05 01:00:33.719 [WARN ] [ibber.internal.handler.TibberHandler] - IO Exception: java.util.concurrent.TimeoutException: Total timeout 20000 ms elapsed
So it looks like sometimes the binding manages to reconnect, but later it only times out.
In the tibber app, however, I still see current consumption, so nothing seems to be wrong with the Pulse.
Did anybody find out how to fix this?
I think it is similar to what @Thorbjorn_Skistad mentions in this post.