Do you happen to know on “what side of the fence” this problem is? Is this a problem on this client side (the UI implementation), meaning that another UI using the Rest API would not have this problem, or is it on the server side meaning that any UI implementation would be hit by the problem?
Its on the server side and has to do with the use of the Atmosphere Framework. That framework has been replaced in OH 2 I’ve been told. I think any UI that depends on websockets would see this problem.