Interesting and very strange. Normally it enters this piece of code only if the state actually changes - I’m wondering if there could maybe be multiple concurrent EventSources at some point.
You seem to have network issues in the errors screenshot, so you can’t receive updates while it’s in this state, not much we can do. However, it should recover nicely and start listening to updates again.
I have a few optimizations in mind already for this part.
The warnings should be unimportant, but the 2147483647 ms delay here is quite alaming This has to be wrong…
Handling of ‘touchmove’ input event was delayed for 2147483647 ms
Thanks for the PDF as well, not much to see at first sight apart from what’s in the screenshots but there is Atmosphere-related stuff which is normally for OH 1.8 only!
I’ll have more next week.