And this second URL should display exactly the same content as the first dashboard, like a real-time mirror, without needing to duplicate all nodes, groups, or pages.
Basically:
Is there any built-in method or configuration in Dashboard 1.0 or Dashboard 2.0 that allows creating a duplicate/mirrored dashboard endpoint?
Or do I need to use another approach (reverse proxy, iframe, virtual screen, etc.)?
Any advice or examples would be greatly appreciated!
The reason I’m trying to create a second dashboard (a mirrored one) is mainly for performance and data-loading optimization.
In my setup, the dashboard is collecting and displaying real-time data coming from multiple devices. When I open the main dashboard on one screen, everything works fine — but I’d like to display the same dashboard simultaneously on another screenwithout doubling the load on the main URL.
What do you mean by dashboard? The dashboard runs in the browser, normally it is the node red server that collects the data. The dashboard only displays it.
Thanks Colin.
To clarify:
Node-RED does the data collection and logic, yes — the dashboard is only the GUI.
All I want is to duplicate the same GUI, so I can view the exact same dashboard on a second screen, but with a different URL, like:
X.X.X.X:1880/ui
X.X.X.X:1880/ui/2
Both should display the same interface, without recreating all the UI nodes.
The reason I want a different URL is that I’m having display issues when I open the same dashboard on a second screen.
Some data doesn’t load or doesn’t update correctly when two browser windows open the same /ui endpoint.
This causes delays or missing values on the second screen.
So my idea was to create a mirror page that shows the exact same GUI, but without triggering the same loading/rendering issues as when I open /ui twice.
I’m not trying to change how the data is collected — just solve this display problem by having two separate access points that show the same dashboard.
And yes, I’m using multiple charts on the dashboard (Dashboard 1.0).
When I open a second window, some charts don’t load correctly or take a long time to refresh.
That’s why I was looking for a way to create a mirror page — not to duplicate the logic, but to avoid these display issues when /ui is opened twice.
I suspect that you would still have the same problem. Do you still see it if you open the second window from a different PC or your phone? If not then you are overloading the browser.
How many samples have you got in charts? For example, on a chart with a time range of 1 hour, and points added every 5 seconds, with 5 lines, that would be 720*5 points. If you find that you have tens of thousands of points in charts then that is the problem. The server and the browser have to move all those points down every time there is a new sample. If you have got a very large number of points then reduce the sample interval (or the time range of the charts).
Yes, that explains it — my dashboard is overloaded with data.
Some charts update every 1 second, and others display weeks of historical data with thousands of points.
This mix creates a heavy load, and that’s why opening a second window causes display issues.
That’s the main reason I was trying to create a “mirror” page — to show the same dashboard on two screens without reloading all the heavy charts twice.
It probably wouldn't make any difference. It is likely that it is the browser that is overloaded. Check in the system monitor to see what is using the CPU.
To check, as I suggested, open the second window on a different PC to see if it is ok then.
You can add some Delay nodes in Rate Limit mode to cut down the update rate to the charts.
