By the end of this activity, you will learn how to view sensor data generated by the Welcome LoRaWAN® and ThingPark Cookbook directly in a web browser, eliminating the need for a mobile app. ThingPark Community is an IoT platform designed for creating and managing LoRaWAN® devices and their associated data flows. In this activity, you’ll leverage both the connectivity services of the ThingPark Community platform and the application data processing capabilities of Qubitro.
This following diagram gives an overview of the data flow.
At a high level, the LoRaWAN® gateway(s) are used for wireless transmission of the data between the network and the end-device. Gateways are connected to the Network Server (ThinkPark Community), which acts as a conduit to the application platform (Qubitro).
When you complete this activity, you will be able to use the web browser to view the sensor data.
Previously…
The environment depicted below was created by following the instructions provided by the “Hello LoRaWAN® and ThingPark®” cookbook. The webhook website was used to display the data that was gathered. However, It does not allow you to do further processing with the data collected by the sensor.
Now..
As you follow this cookbook, you will expand your ability to build a device dashboard, which presents sensor data, and access that dashboard by using a browser.
Solution flow…
The picture depicts the flow of the data that was collected from the sensors. The flow’s first three stages were previously explained at Welcome LoRaWAN® and ThingPark cookbook. Only three additional flow stages between 4 and 6 are introduced in this new activity.
The sensor data is collected as described in the Hello LoRaWAN® and ThingPark® Cookbook.
As an application platform, we will make use of Qubitro so that you can view the collected data.
On the Qubitro website, you will find information regarding their application platform service.
During this activity, you are going to perform two different kinds of tasks. The first category is to implement the solution, and the second category is to maintain oversight on how data moves between various functional elements (TPC, TPX, Qubitro, web browser). To help with debugging, it is necessary to get familiar with “how to follow the footprints of the data.”
