I notice the WiFi signal strength isn't exactly 100%.
No, not the cause, but it won't be helping.
Oh, something else:
Can you check the load on the tablet? How hard the processor is working.
If the flow has a bit of bad stuff in it causing a high load, that can contribute to this happening too.
At least 2 charts I can see are configured for 24 hours. And there is 4 and 5 datasets per chart. It really depends what is the rate of input for chart but you can calculate the count of data-points you r charts needs to be handle. At some point there is limit. And that limit is what you see - The connection lost.
It is discussed here in forum many times and there is many advises given how to handle this situation.
Do search in forum in therms of slow/unresponsive dashboard with charts.
Basically what you'll need to do is to reduce data-points for charts. Many ways to do it. And it depends what is the meaningful readout you are expecting.
There is no direct answer to that question. It is combination of device capabilities, browser, other things the device/browser needs to do at same time, the page set up and many many more things.
But if you'll do the calculations based on the device you are seeing the connection lost, then that is definitely max for that device in current conditions.
Yes, that helps to get your main page responsive and not to fall into that trouble, but will the page/tab with charts be better? Probably not.
The charts in node-red are plain charts. Unlike for example grafana where a lot of optimizations is done under the hood by default, you have no need to even think about such problems. Well, you can kill the browser with them too, but that's another story. But for raw chart libraries the data optimization is left for user to figure out.
You are just overloading the device with too much data to handle in the charts. As has been suggested, reduce the update rate to the charts so that the total number of samples across the chart is not much more than the number of pixels.
