Node-RED With IoT Long Range Vibration and Temperature Sensor

Introducing NCD’s long-range wireless temperature humidity sensor, boasting up to a 28 Mile range using a wireless mesh networking architecture. Incorporating the Honeywell HIH9130 temperature humidity sensor transmits highly accurate temperature and humidity samples at user-defined intervals.

Hardware:

NCD Long Range Vibration and Temperature Sensor

NCD Long Range Wireless Mesh Modem with USB Interface

Software:

Node-Red

Now that you have sensors running, we need a way to do something useful with that data.

• First of all, you'll have to install Node-Red.
• Once that’s done, you’ll need to enter your command line, or Power Shell for Windows users, navigate to the directory Node-RED is installed in.
• Now type “npm i ncd-red-wireless node-red-dashboard“. This will install the nodes required to receive data from your wireless sensors and you can start Node-RED once this is done.
• To start node server write node-red in the command prompt or terminal and press enter.

At this point you’ll be viewing a large blank flow with a long list of nodes on the left-hand side, this sidebar is called the palette.

ncd-red-wireless Provides the nodes that manage the serial connection, parse incoming sensor data, filter it by specific parameters, and allow you to configure the wireless sensors.

When you’ve delivered the node you’ll be able to view the info tab, which contains records about the node’s capability, this tab is well-populated for maximum node-red packages and consists of treasured statistics, often you will now not want to view any other documentation outdoor of the info tab, so hold it in thoughts even as you're building your flows when you have a question approximately how a node works. The next element we want to do is configure the node, when you first add it you’ll note that there is a small triangle at the top right corner next to a blue dot, the triangle indicates that the node wishes extra configuration, the blue dot indicates that the node has no longer but been deployed as part of the flow.

• Double click on the node to open up the configuration options.
• Click on the pencil icon next to the Serial Device field to configure your USB router, this will open a second configuration panel that only has a few options.

Now out of your wireless sensors data is gathered and it is output to the “debug” tab, this "debug tab" is placed within the right sidebar subsequent to the information tab. To see the information is available to hit the reset button. In node-red records is surpassed among nodes in a json packet. When the msg object comes into the debug tab you may make bigger it to view the overall list of information that comes with it. This is extraordinarily useful in case you need to quickly see which sensors are checking in. The other issue this node gives is an easy way to interchange your router to the network identity that devices in configuration mode document on, simply hit the button on the left of the node and the tool will switch to the configuration network, hit it once more to return it to listening mode. Once we get the wi-fi tool nodes set up, they may be set to routinely configure a sensor whilst it enters configuration mode, so it’s always available to maintain such gateway nodes present at the flow for speedy configuring a device.

We need to separate wireless sensor records domestically in order that we are able to display it, we could use a switch node to split out the messages from the gateway based totally on the mac address with or sensor type, but as I referred to, the wireless nodes truly incorporate extra functionality for configuring the sensors, so we’ll start with them to give you an extra entire image of how those structures can work. In case you haven’t already seen packets coming in from both of your sensors, cross in advance and hit the reset button on the only that hasn’t started. While a sensor assessment in through any serial device configuration node, the mac address and kind of sensor is cached in a pool so we are able to quickly find it for the duration of this next step.

• Grab a Wireless Node from the palette and drag it onto the flow, double click on it to get it configured.

You’ll notice this automatically sets the sensor type for you, you can also give it a name to make it easier to identify. As noted in the info tab, the Serial Device for Config field is optional, and we won’t worry about it right now. The node you have just added effectively works as a filter on incoming sensor data, only passing through data for the mac address, or sensor type if no mac address is present.

These nodes for the wireless sensors output a msg object with all of the same information as the Wireless Gateway node, just in a slightly different format, the Sensor Data itself is sent in the msg.payload, which is what most nodes use to interact with the msg itself.

• Grab a “split” node from the palette, and place it to the right of the Vib/Temp node.

• Click on the “==” and select “matches regex”, in the field next to it type “rms_.”, this means “match a string that contains rms_ followed by any character (.) as many characters as are available ().

• Follow the last step, replacing “rms” with “max”, and then one more time with “min” and atlast one more row for temperature type “temperature” next to the “==”. This will split our incoming payloads into 4 sections to be routed to ui, each containing the appropriate values for all 3 axes and temperature.

• set the Group to "[Current]Vibration" and set the Label to RMS as shown in the picture.

• set the Group to "[Current]Vibration" and set the Label to MAX as shown in the picture.

• set the Group to "[Current]Vibration" and set the Label to MIN as shown in the picture.

• set the Label to “Temperature”, and the Value format to “{{value | number:2}}”, and the Units to “Celsius” you can alter the range to the minimum and maximum expected temperature, I’m using 0 and 50.

Provides the ability to create a UI using the flow builder, provides charts, graphs, and a number of other visual elements we can use to display data, along with nodes to trigger a flow using user input. We will use some of these nodes to display the telemetry from your wireless sensors.

• let’s check it out! There is a tab on the top right that says “Dashboard”

It is likely that the gauges aren’t displaying any information, because no sensor data has been reported since you deployed the flow, click the reset button on your temperature/humidity sensor to force it to check in and your gauges should jump up. You should now have real time data displaying!

Now as the value of vibration and temperature increases and decreases new data available inside the various variable.

• RMS/MAX/MIN Output