Using the Node Red Status Node

status-nodeIn Node red any node can report status information in the visual editor.

The screen shot below shows the MQTT node.


It shows a green circle to indicate that it is connected and the text connected underneath the node.

The UI visual status is enabled by default but can be disabled in the menu>settings.


Although useful as a visual indicator it is even more  useful to have this status information available in the flow, and to be able to take action based on the node status.

status-node-locationTo do this you need to add the status node to your flow.

You will find the status node under the input nodes.

If you add this node to the flow and open the flow you can select the node/nodes you want to receive status information for as shown below:


In the above I have selected the MQTT node. The screen shot below shows my example flow.status-node-example-flow

The status node sends a msg whenever the status of the monitored node/nodes changes.

This message consists of two objects.

  • status object – used to get status information
  • source object- Identifies source of message using the node id. Every node has a unique node id as shown in the screen shot below:

You can view the id of a node by clicking it and then clicking on the information pane in the far right.


To access these properties in a function or other node use:

msg.status.text and

In my simple flow the function node receives the status information from the status node and simply passes it on to the debug node.

Th screen shot below shows the status text changing as the MQTT node connects.


You can take action based on the connection text in a function node using an if statement e.g.

if (msg.status.text=="node-red:common.status.connected")
DO Something

Because the status information is only sent when the status changes it is usually necessary to place the information in a global or flow object.

To do this pass the status msg into a function node that has the following code.

var mqtt_status=msg.status;

The Status information can then be used anywhere in the flow.


Here is a video that covers the above and also demonstrates using the status information to control when  messages are published over MQTT.

Flow used in video


 Using the Status Node for Flow Control

In this video we use the status node to switch publishing from one broker to a standby broker.

Flow used in video

Displaying Status Information from Function Nodes

You can display stays information from your own function nodes in the admin UI.

To do that use the following:


The object you pass can have three key value pairs:

  • fill – This is the fill colour can be: red, green, yellow, blue or grey
  • shape- Ring or Dot
  • Text – descriptive text

The screen shot below shows an example function configured to display status information using the following:



Related tutorials and Resources:

Click to rate this post!
[Total: 1 Average: 5]


    1. I think it is a browser setting as they display for me. I seem to remember that I had that problem a few years ago but I can’t remember what I did to solve it.

    1. You only get a status message when something changes but each node can generate a status message.
      Does that help?

  1. Steve, another very good and well explain guide to the status node. I would like to see a follow up video on further using the information gathered as in ‘Do something’. Perhaps displaying something on the dashboard. If, for example the MQTT was disconnected, then, unless using a second broker, one could not send an error message via MQTT. Depending upon which type of device the broker was running on, a Raspi for example, it could activate an output or serial message. Just my thoughts!!

Leave a Reply

Your email address will not be published. Required fields are marked *