Skip to content

Chart ui-chart

Provides configuration options to create the following chart types:

Properties

PropDynamicDescription
GroupDefines which group of the UI Dashboard this widget will render in.
SizeControls the width of the button with respect to the parent group. Maximum value is the width of the group.
LabelThe text shown within the button.
ClassThe text shown within the button.
Chart TypeLine | Bar | Scatter
Show LegendDefines whether or not a legend is shown between the title and the chart. Each label is driven by msg.topic.
ActionControls how new data is added to a chart. It will either "append", keeping existing data, or "replace", removing existing data, before adding any newly provided data points.
Point ShapeDefine the shape of the point shown in Scatter & Line charts.
Point RadiusDefine the radius (in pixels) of each point rendered onto a Scatter or Line chart.
X-Axis TypeTimescale | Linear | Categorical
X-Axis LimitAny data that is before the specific time limit (for time charts) or where there are more data points than the limit specified will be removed from the chart.
PropertiesSeries: Controls how you want to set the Series of data stream into this widget. The default is msg.topic, where separate topics will render to a new line/bar in their respective plots.
X: Only available for Line & Scatter Charts. This defines the key (which can be nested) of the value that should be plotted onto the x-axis. If left blank, the x-value will be calculated as the current timestamp.
Y: Defines the key (which can be nested, e.g. 'nested.value') of the value that should be plotted onto the x-axis. This value is ignored if injecting single numerical values into the chart.

Dynamic Properties

Dynamic properties are those that can be overriden at runtime by sending a particular msg to the node.

Where appropriate, the underlying values set within Node-RED will be overriden by the values set in the received messages.

PropPayloadStructures
Classmsg.classString

Controls

Removing Data

"Append" or "Replace" Added In: v0.11.3

The "Action" property on the chart allows you to control whether you:

  • Append: Any new data provided will be added to the existing data on the chart
  • Replace: Any existing data will first be removed, then new data will be added.

If you ever want to override the property on a message-by-message basis, you can also do this by including a msg.action property, which will override the default behaviour. For example:

js
msg = {
    "action": "append",
    "payload": 1
}

Would append this data point to the chart, leaving existing data, even if the underlying chart has been configured to always "Replace".

Clear All Data

Alternatively, you can remove all data from a chart at any time by sending a msg.payload of [] to the node. Most commonly, this is done by wiring a ui-button to the ui-chart node and configuring the button to send a JSON payload with a value of [].

Working with Data

ui-chart allows you to define which "keys" from your data you would like to render on the chart.

Example keymapping config for UI ChartExample keymapping config for UI Chart

In this example, each received datapoint would plot to a fixed "Temperature" series, and UI Chart would read the .time value to plot on the x-axis, and the .temp value to plot on the y-axis.

Series

The Series property allows you to define how you want to control which line/bar (series) data belongs to when streamed into this widget. The default is msg.topic, where separate topics will render to a new line/bar in their respective plots.

If you want to label a single line on your chart, you can set this to a static string value, e.g. Temperature, which saves you have to assign msg.topic to every data point.

Multiple Lines

If you would like to plot multiple lines on the same chart, you can do so by defining the Series property, which defaults to msg.topic.

With this defined, you can assign different data to different datasets that will be plotted:

js
msg = {
    "topic": "line-1",
    "payload": 1
}
js
msg = {
    "topic": "line-2",
    "payload": 2
}

This use case is great if you have multiple sensors feeding data into the same chart. You can assign msg.topic accordignly for each sensor.

This behaviour is mimicked here with three sliders, each with a different msg.topic:

Example Line Chart rendering data from different "sensors" using msg.topicExample Line Chart rendering data from different "sensors" using msg.topic

Alternatively, you can set the series property to type JSON, and then provide an array of keys (e.g. ["key1", "key2"]), which will plot a data point for each key provided, from a single data point. For example:

js
msg.payload = [
    {
        "x_value": 12,
        "value": 17,
        "nested": {
            "value": 24
        }
    },
    {
        "x_value": 17,
        "value": 36,
        "nested": {
            "value": 10
        }
    },
    {
        "x_value": 23,
        "value": 19,
        "nested": {
            "value": 75
        }
    },
    {
        "x_value": 34,
        "value": 12,
        "nested": {
            "value": 23
        }
    }
]

with a chart config of:

Example config of a Line Chart to render multiple lines of data from a single data point

Would result in:

Example of a Line Chart rendering multiple data points per injecting payload

Nested Data

It is a common use case that you would have data structured as JSON, and want to plot some of it e.g:

js
msg = {
    "topic": "Sensor A" 
    "payload": {
        "id": "Dataset 1",
        "value": 3,
        "nested": {
            "value": 1
        }
    }
}

Here, we can utilise the "Properties" series, x and y to define which values we want to plot on the chart.

Some combinations to consider:

seriesxydescription
str:line1valuenested.valueThis would plot (3, 1), on a line labelled "line1".
property:idvaluenested.valueThis would plot (3, 1), on a line labelled "Dataset 1".
property:idvalueLine Chart: This would plot (Date.now(), 3), labelled "Dataset 1".

Bar Chart: this would plot a single bar, labelled "Dataset 1", with a height of 3.
msg.topicnested.valueOn a bar chart, this would plot a single bar, labelled "Sensor A", with a height of 1.

Live Data

If you're producing "live" data (from sensors for example), you do not need to define how the x property should be plotted. Instead, you can leave this blank and the chart will automatically calculate the current date/time.

This works equally well if you use Object formatted data, e.g.

js
msg = {
    "topic": "Sensor A" 
    "payload": {
        "value": 3
    }
}

Where you could set the y property to property:value, as well as if you're providing raw numerical data, e.g.

js
msg = {
    "topic": "Sensor A" 
    "payload": 3
}

Where the y property is ignored, as it detects that is stored as a raw number.

Chart Types

Line Chart

Example of a Line ChartExample of a rendered line chart with a "time" x-axis.

Payloads

Line Charts accept a variety of payload formats. The following are all valid:

  • msg.payload = <value>
    • In this case, the value received by the chart will be used as a y value, and the x value will be automatically added as the current date/time.
  • msg.payload = { y: <value> }
    • In this case, the y value will be used as defined, and the x value will be calculated as the current date/time.
  • msg.payload = { x: <value>, y: <value> }
    • In this case, the x and y values will be used as the x and y values of the data point.
  • msg.payload = [{ x: <value>, y: <value> }, { x: <value>, y: <value> }]
    • In this case, multiple points will be plotted into a single line.
  • msg.payload = [{ x: <value>, y: <value>, line: <value> }, { x: <value>, y: <value>, line: <value> }]
    • In this case, multiple points will be plotted, and if the series property is set to property:line then the line property will be used to determine which line each data point should be plotted on.

Multiple Lines

If you would like to plot multiple lines on the same chart, you can do so by including a msg.topic alongside the relevant msg.payload, e.g:

js
msg = {
    "topic": "line-1",
    "payload": 1
}
js
msg = {
    "topic": "line-2",
    "payload": 2
}

Whilst msg.topic is the default value for the series property on a ui-chart, this can be changed. You could also set it to key:<series> to differentiate each point to a separate line, in that case your data would like like:

js
msg.payload = {
    "value": 2,
    "series": "my-series"
}

Multiple Data Points (Injecting an Array of Data)

If you would like to pass in multiple data points at the same time into a chart, you can do so by passing an Array in msg.payload.

js
msg = {
    "topic": "line-1",
    "payload": [{
        "x": 30,
        "y": 43
    }, {
        "x": 40,
        "y": 56
    }, {
        "x": 50,
        "y": 74
    }]
}

Note how we can still define the msg.topic value (or whatever we have defined for series) such that these data points all appear on the same line.

If we wanted each point in a different series, we could set series to key:series, so that each data point is condsidered individually:

js
msg = {
    "payload": [{
        "series": "Line 1",
        "x": 30,
        "y": 43
    }, {
        "series": "Line 2",
        "x": 40,
        "y": 56
    }, {
        "series": "Line 1",
        "x": 50,
        "y": 74
    }]
}

Scatter Plot

Example of a Scatter PlotExample of a rendered scatter plot with a "time" x-axis.

Payloads

Scatter Plots accept a variety of payload formats. The following are all valid:

  • msg.payload = <value>
    • In this case, the value received by the chart will be used as a y value, and the x value will be automatically added as the current date/time.
  • msg.payload = { y: <value> }
    • In this case, the y value will be used as defined, and the x value will be calculated as the current date/time.
  • msg.payload = { x: <value>, y: <value> }
    • In this case, the x and y values will be used as the x and y values of the data point.
  • msg.payload = [{ x: <value>, y: <value> }, { x: <value>, y: <value> }]
    • In this case, multiple points will be plotted into a single series.
  • msg.payload = [{ x: <value>, y: <value>, series: <value> }, { x: <value>, y: <value>, series: <value> }]
    • In this case, multiple points will be plotted, and if the series property is set to property:series then the series property will be used to determine which data series each data point should be plotted on.

Bar Graph

Example of a Bar GraphExample of a rendered bar graph.

Bar charts can only be configured with a "Categorical" x-axis type, the series that each data point will group into is then defined by the "Series" property, with the "y" property defining the value of each bar.

Configuration

  • X Axis Type: Categorical
  • Series: Define how to separate your data into individual bars
    • msg.<variable>: Each message sent to the chart will assign to the category depending on msg.<variable>. In Dashboard 1.0 this was the default behaviour, where msg.topic would control the series of the data, and this is still supported in Dashboard 2.0.
    • string: Each message received will always bind to the same bar, this restricts the chart to only being able to show a single column/category of data.
    • key:<key>: Each message, or object within an array payload, will be assigned the category based on it's value <key>. If you have raw numerical data, and not an object, leave this blank.
    • JSON:: This combines the "Series" and "y" options, where you can provide an Array of strings, pointing to the property/value that you want to render. The category label is then defined by the property itself.
  • Y: Describe how to retrieve the value you want to plot on the y-axis. Leave blank if you're sending raw numerical data, otherwise, provide the key (which can be nested) of the value that should be plotted onto the x-axis, e.g. {"nested": {"value": 34}} would plot 34 on the y-axis if you set this to nested.value.

Examples

The payload will heavily depend on the "Series" value used, as such, we provide examples of each as follows:

Series: msg.<property>

Each message send to the chart will assign to the category depending on msg.<property>. In Dashboard 1.0 this was the default behaviour, where msg.topic would control the series of the data, and this is still supported in Dashboard 2.0.

js
const msg = {
    "topic": "bar-1",
    "payload": 1
}

would set the value of the bar-1 series to 1.

Series: string

Each message received will always bind to the same bar, this restricts the chart to only being able to show a single column/category of data.

js
const msg = {
    "payload": 12
}

would set the value of the single series to 12.

Series: key:<key>

Each message received will bind to the category defined by the value of <key> in the message payload. So, if we set the "Series" value to be key:category, then the following message:

js
const msg = {
    "payload": {
        "category": "bar-1",
        "value": 34
    }
}

Would set the value of the bar-1 series to 34.

Additionally, with this option it's then easy to control multiple bars from a single msg:

js
const msg = {
    "payload": [
        {
            "category": "bar-1",
            "value": 34
        },
        {
            "category": "bar-2",
            "value": 12
        },
        {
            "category": "bar-3",
            "value": 23
        },
        {
            "category": "bar-1",
            "value": 17
        }
    ]
}
Series: JSON:

This combines the "Series" and "y" options, where you can provide an Array of strings, pointing to the property/value that you want to render. The category label is then defined by the property itself.

So in an example where we set "Series" to ["value", "nested.value"]

js
const msg = {
    "payload": {
        "value": 34,
        "nested": {
            "value": 12
        }
    }
}

This would render two bars, one labelled value with a value of 34, and one labelled nested.value with a value of 12.