Open mhilbush opened 1 year ago
Could be a resource not properly released when the thing handler is disposed.
Thanks. That was one of my first thoughts, too. But doing a single binding restart didn't cause a problem.
However, when I did several restarts quickly, I was able to create a similar situation with multiple ping jobs running (and open websocket connections), but it wasn't exactly the same behavior as what I showed above.
I occasionally see this in my openhab log file.
It seems to coincide with a condition where the bridge and sprinkler things go OFFLINE, then come back ONLINE. This OFFLINE/ONLINE condition occurs pretty regularly (multiple times a day) when the binding detects that the cloud service closes the websocket connection. However, the above condition occurs much more rarely than that.
When it happens, I also see this behavior in the binding DEBUG log.
This suggests to me that there are 2 websocket connections open to the OrbigBhyve cloud service. However, it's still unclear the condition(s) under which a 2nd connection is orphaned. If I can pinpoint the cause, I'l submit a fix.