| .. | ||
| .npm | ||
| 00-dashboard-example | ||
| docs/images | ||
| node_modules | ||
| .config.nodes.json | ||
| .config.nodes.json.backup | ||
| .config.projects.json | ||
| .config.runtime.json | ||
| .config.users.json | ||
| .config.users.json.backup | ||
| .flows.json.backup | ||
| .flows_cred.json.backup | ||
| flows.json | ||
| flows_cred.json | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| settings.js | ||
About
This folder will be mounted into the Node-RED runtime. So be careful.
Node-RED
If you boot up our tech stack using docker-compose you already have a Node-RED instance running on your local machine.
Node-RED is an open-source, low-code, visual programming tool based on the concept of flow-based development. The idea behind it is to make it very easy to connect APIs, hardware devices, and anything else accessible over some type of network connection.
Core Concepts
Nodes are the important part of Node-Red. They are the building blocks when working with Node-Red. Nodes are triggered by either receiving a message object from a previous node or an external event like an MQTT event. The node processes the message or event and then passes it on to the next node.
A node can:
- Inject: Starts a flow by injecting a message or a payload.
- Change: Here you can do basic transformation or modification on the message object.
- Debug: Can be used to help developing flows by sending messages to the side bar.
- Switch: Here you can add logic (like sending the message to different nodes).
- Function: Add custom JavaScript for uses cases where simple nodes do not do the trick.
Flows are an organized sequence of nodes. Let's do the "first steps" by creating a simple flow.
Plugins
The plugin folder is pushed into this Git repository and is mounted in Docker. Maybe we should use an own Docker file, instead.
Node-RED uses plugins (e.g. for InfluxDB or own Dashboard capabilites).
You can access the plugins in the right burger menu.
First steps
For debuging I already added Node-RED's own dashboard (sure, we are going to use Grafana, later).
The dashboard should be visible on the righmost menu item in Node-RED.
In Node-RED you can add a MQQT node to receive values from the power monitor. As we run in docker-composeyou don't have to use the IP address of our Eclipse Mosquitto sever, but you can simply use mosquitto as the host nome.
git a
To simply display the values in a gauge (or chart) you can hook it up to a gauge node.
In the dasboard section you have to create a tab. Inside this tab you have to create a group.
The tricky part is putting the gauges in the group. This is done in the gauge's settings (not in the dashboard's settings).
You can view the dashboard in an (also mobile) web browser.
Have a look at the flow also in this repository.
InfluxDB
Already added to this project is node-red-contrib-influxdb. You can use it's nodes to write and query data from an InfluxDB time series database. These nodes support both InfluxDB 1.x and InfluxDb 2.0 databases. At the time of this writing we are using version 2.6 of InfluxDB on port 8086.
In Node-RED we will be passing the power consumption number through MQTT.
By default this will be passed as a string, so we need to create a function to convert it into a Number before storing it in InfluxDB.
Add a function node to the page and put the following code into the node:
msg.payload = Number(msg.payload)
return msg;
You can forward this message to InfluxDB.
The URLof our InfluxDB is http://influxdb:8086. In InfluxDB you have to create a token to connect: Load Data -> API Tokens.
You can use this token to create a connection in Node-RED.
Then the measurements should be visible in Influx Data Explorer.
As the data is now stored in Influx, let's create a dashboard in Grafana.
Links
- IoT Made Easy with Node-RED and InfluxDB
- A great tutorial can be found at microcontrollerlab.com