Hi @patrick
Please bear with me on this but I have noticed the odd strange thing going on since the last dashboard update.
I couple of times my hub has gone unresponsive and a reboot clears the issue.
Today I noticed that my under-stairs cupboard light did not come on.
My first thought is to go to the dashboard on my phone and check to make sure the contact sensor is opening and closing on the dashboard and rule this out.
When I opened the dashboard on my phone it had been left open in a room. Not the cupboard.
When I opened the dashboard the motion sensors in the room then registered all the movements that had happened since the last time the dashboard was opened on the phone. (I assume).
i.e. Both motion sensors in the dashboard went active/inactive/active/inactive etc. etc. quite a number of times before stopping at the current state of the sensors.
I then opened/closed the cupboard door a number of times and the light turned on/off as it should.
This gets me to thinking that the commands were stacked up and had caused my hub to go unresponsive.
Just a thought and wonder what your thoughts are on this and whether there could be an issue here causing problems.
Like I say, just some thoughts and I know too well, a little knowledge is a dangerous thing. 
Anything is possible. But I don't think dashboard itself can cause what you are describing. It just sounds like the websocket reconnected and processed the info.
If a browser is open in background on the local network, it should eventually disconnect / timeout and on refocus should reconnect.
@patrick
Thanks for the reply Patrick.
The events happened as described and I put 2 and 2 together, came up with 25 and thought I'd ask the question.
I've never seen the, I'm going to describe it as, downloading the history when re-opening the dashboard before, so thought I'd ask the question.
It's a "normal" browser behavior to cache backgrounded UI tasks and then render them on focus. Since this data was already transmitted in real time via the websocket, There really wasn't any interaction with the Hub at the moment you opened back up the browser.
