[Shelly] Binding & OH 2.5.6: Error after upgrade from 2.5.3 to 2.5.6

Add-ons Bindings
1

Hello *,

I am running OH v2.5.6 as docker container (x86_64, debian) in my NAS.
After upgrading from 2.5.3 I see some minutes after startup the warning shown below three times in a row in the logs and then no more.

Do I need to be concerned about that?

14:13:30.026 [WARN ] [ommon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception: 
java.lang.IllegalStateException: Stopwatch has not been started
	at org.apache.commons.lang.time.StopWatch.getStartTime(StopWatch.java:306) ~[?:?]
	at org.openhab.binding.shelly.internal.handler.ShellyBaseHandler.refreshStatus(ShellyBaseHandler.java:396) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_252]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) ~[?:1.8.0_252]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) ~[?:1.8.0_252]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) ~[?:1.8.0_252]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_252]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_252]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
2

If the binding works as expected then I wouldn’t worry much about the warning. If you only see it after a restart of OH then it’s likely their is something else in OH that has not yet started hence the warning.