Sending-Data-of-IOT-Wireless-Temperature-and-Humidity-Sensor-to-MySQL

Introducing NCD’s Long Range IoT Temperature and Humidity Sensor. Boasting up to a 28-mile range, and a wireless mesh networking architecture, this sensor transmits humidity (±1.7%) and temperature (±0.3°C) data at user-defined intervals, sleeping in between to maximize battery life.

Powered by just 2 AA batteries and an operational lifetime of 500,000 wireless transmissions, 10-year battery life can be achieved with proper calibration. Optionally, this sensor may be externally powered.

An open communication protocol allows easy integration with just about any control system or gateway. Data can be transmitted to a PC, Raspberry Pi, or even an Arduino, and sent on to Microsoft Azure®, AWS or Google Cloud Platform. Wireless transmission settings can be changed using the open communication protocol providing maximum configurability depending on the intended application. The long-range, price, accuracy, battery life and security features of our Wireless Temperature and Humidity Sensor make it an ideal choice to start, or expand, your own wireless sensor network using a device which exceeds the requirements for most of the industrial as well as consumer market applications.

Hardware:

• NCD Long Range Temperature and Humidity Sensor
• NCD Long Range Wireless Mesh Modem with USB Interface

Software:

• Node-Red
• XAMPP

XAMPP is most prevailing, free an open-source cross-platform which is one solution to run your web services. XAMPP is developed by ApacheFriends which released in May 2002. XAMPP Stands for Cross-Platform(X), Apache(A), MySQL(M) also Sometimes (M) refers to MariaDB, PHP(P) and Pearl(P).

XAMPP allows you to work on a local server and test local copies of websites using PHP code and MySQL databases. Once XAMPP is active, you can access your local copy with a browser using an URL like http://localhost/ or http://localhost/

Downloading and Installing XAMPP

Go to XAMPP web site and download the installer based on your operating system. Installation should be similar to a normal software installation you do in your operating system. When installing, there would be an option to select whether you want to run Apache and MySQL as services. If you chose it, Apache and MySQL will start at system boot-up which may not need if your computer is tight with memory resources or if you are not doing PHP development frequently. You can change these settings after installation.

Go to the location where you installed XAMPP (usually C:\Program Files\xampp) and double click on XAMPP Control Panel (xampp-control.exe). This will bring you the following screen. Click on Start buttons next to Apache and MySQL for starting them.

Name = temperature, Type = DECIMAL, Length/Values = 10,2(i.e up to 2 decimal points) and similarly for humidity and in the last column you can show created time and click on the save button as shown in the picture below.

That's all with the setting up of XAMPP.

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.

The function node is used to run JavaScript code against the msg object. The function node accepts a msg object as input and can return 0 or more message objects as output. This message object must have a payload property (msg.payload), and usually has other properties depending on the proceeding nodes.

• Now grab a “function” node from the palette, and place it to the right of the Temp/Hum node.

Here you have to write little javascript code to create a condition, so at particular temperature value, an email alert will be sent to the respective email id.

Once its done, you'll see "mysql" node is present in the palette.

Here you can visualize the data coming in.