MQTT/Node Red UI limitations

Hello folks,

I am running into a issue where I am using MQTT to read values and present them on Node red UI.

Has anyone found that there is a limitation to how many things you can present on the UI at once?

Has anyone found that there is a limitation to how many thing you can read topic wise at once on MQTT?

Thank you for your help.

The Dashboard is quite a complex beast but I know that many people have really complex Dashboards. The main limitation is around the use of the standard chart node where you really need to ensure that you keep the number of displayed points under control.

There have been a few discussions about this over time but the overall indication seems to be that you really can push MQTT a long way. However, it does somewhat depend on what broker you are using and what else is running on the server device. If you are using Mosquitto as your broker, it is compact and highly performant, not sure what msg rate it will run up to but it is pretty high even on a Raspberry Pi.

As always, make sure that you aren't overloading your server device. Especially with something like a Pi. Don't run Linux desktop for example if you don't absolutely have to - and if you do, expect greatly reduced performance. If you are running a desktop on the server, don't use the server to browse the Dashboard because that gives you a triple whammy.

1 Like

There shouldn't be. What problem are you seeing and what versions of node-red and the dashboard are you using?

How often are you updating the UI?
Are you using charts?

1 Like

thank you both,

version is 2.1.3 and dashboard is 3.1.2

I am basically reading around 40 mqtt topics per flow, there being 4 flows in total. Each flow is split to a seperate ui tab , but whats happening is some of the data isnt coming through mqtt when I know , say try from another device to read the mqtt same topic that its submitting data... confusing...