Skip to main content
X

Environmental Monitoring LoRaWAN Network Server Guide

Network Server and Visualization Configuration​

This section outlines the operational steps for connecting the device to the network server in both the LoRaWAN and NB-IoT application scenarios.

Figure 10694: LoRaWAN application scenario

LoRaWAN Application​

Cloud Network Server Setup​

The cloud network server deployment solution connects the gateways and devices to a third-party cloud network server. This setup integrates visualization applications to manage temperature and humidity sensor data in real-time.

This section provides instructions on creating a Datacake visualization application using the TTN v3 cloud network server.

Figure 10695: Cloud network server deployment solution
Connect Gateway to TTN​

For this example, you will use the TTNv3 cloud server and RAK7289 V2 WisGate Edge Lite 2 to demonstrate how to connect the RAK business gateway to a cloud server.

Register the Gateway
  1. Register an account and log in to the TTN v3 website. If you already have a TTN account, you can log in using your The Things ID credentials.
Figure 10696: Log in to the TTN website
  1. Once logged into the site, click on Register a gateway to begin the registration process for a new gateway.
Figure 10697: TTN home page
  1. Input the Gateway EUI and then click on Confirm to proceed.

The Gateway EUI serves as a distinct 64-bit extended identifier for the gateway. It is accessible from the Overview page of the gateway management platform or the label situated behind the gateway.

Figure 10698: Enter the Gateway EUI
  1. Choose the appropriate frequency plan used by the gateway, and click Register gateway to complete the registration process of the gateway.
Figure 10699: Configure the gateway frequency

Your gateway dashboard should look the same with Figure 7.

Figure 10700: Successfully registered the gateway
Generate a Token

TTNv3 supports TLS server authentication and client tokens, which require trust files and keys to configure the gateway and successfully connect to the network.

  1. To generate a key file, navigate to API keys from the Overview page of the registered gateway, then click Add API key.
Figure 10701: Add API keys
  1. In the Add API key page, set the Name field, tick off the checkboxes, then click Create API key.
Figure 10702: Configure the API key
  1. A new window pops up with the generated key. Copy the new API key by clicking the icon and then the I have copied the key button.
Figure 10703: Copy and save the API key
Configure the Gateway
  1. Navigate back to the gateway management platform Web UI. Click on the left navigation bar to access the LoRa > Configuration tab. Complete the following settings and save them.
  • Basics Station Server Type: LNS Server
  • Server URL: wss://eu1.cloud.thethings.network
  • Server Port: 8887
  • Authentication Mode: TLS server & Client Token Authentication
  • Trust (CA Certificate): Download the certificate.
  • Client Token: Copied API Keys
Figure 10704: Configure the gateway
  1. After saving the changes, return to the TTN gateway interface, and navigate to the Gateways tab to confirm that the gateway is now connected to TTNv3 as a Basics Station.
Figure 10705: Gateway connected successfully
Connect Sensor Hub to TTN​
  1. Return to the TTNv3 homepage and select Create an application to add a node.
Figure 10706: Select Create an application
  1. Click +Create application to initiate the creation of a node.
Figure 10707: Create a new application
  1. Enter the desired Application ID in the provided field, then click on Create application.
Figure 10708: Fill in the Application ID field
  1. Click on the +Register end device button to add a new end device to the application.
Figure 10709: Add the end device
  1. Set the parameters of the end device, as shown in Figure 17.
Figure 10710: End device parameters
  • JoinEUI, DevEUI, and AppKey can be automatically generated by clicking Generate on the TTN web page. These parameters are customizable as well.
NOTE

Ensure that the three parameters - JoinEUI, DevEUI, and AppKey - are consistent with the parameters set in the WisToolBox application.

  1. After completing the settings, return to the WisToolBox app, and click JOIN NETWORK to send the end device network join request.
Figure 10711: Sending end device network join request
  1. As shown in Figure 19, the Sensor Hub has successfully joined the TTNv3 network server.
Figure 10712: Successfully joined the TTNv3 network server
Visualize Data Through Datacake​

Datacake is a versatile IoT platform. It offers a range of features tailored for effective data visualization and management, making it a preferred choice for IoT projects requiring efficient monitoring and analysis.

Create Datacake Integration
  1. In the TTN console, navigate to Integrations on the sidebar, proceed to the Webhooks section, and then click +Add webhooks to set up an integration.
Figure 10713: Adding an integration
  1. From the list of webhook templates, select the Datacake template.
Figure 10714: Select the Datacake template
  1. Generate an API key on Datacake to enable webhook authentication. To get started, register a Datacake account, and then log in.
Figure 10715: Datacake IoT platform main page
  1. Navigate to the Datacake workspace. Select Members on the sidebar, switch to the API Users tab, then click the Add API User button.
Figure 10716: Add API User
  1. Enter the name of the API User, for instance, TTS API. Set the relevant parameters accordingly and click Save to finalize the creation process.
Figure 10717: Set Parameters
  1. Click the Copy button to copy the generated Datacake API Token.
Figure 10718: Copy the generated Datacake API Token
  1. Back on the TTN website, enter sensorhub in the Webhook ID field (as an example), and paste the Datacake API Token you previously copied into the Token field. Click the Create Datacake Webhook button to generate the Datacake Webhook.
Figure 10719: Create the Datacake Webhook
Add Sensor Hub to Datacake
  1. To add a new device, select Devices in the sidebar and click the +Add Device button.
Figure 10720: Add a device
  1. Choose LoRaWAN from the options and click Next to proceed.
Figure 10721: Select LoRaWAN
  1. As the Sensor Hub is a new device, there is no pre-existing template. Create a template by clicking New Product, enter the Product Name, and click Next to proceed.
Figure 10722: Create a New Product
  1. Choose a network server for your device. In this guide, select The Things Stack V3, then click Next to continue.
Figure 10723: Select the Things Stack V3
  1. In the STEP 3 Devices tab, enter the device DEVEUI and NAME fields, and click Next to continue.
Figure 10724: Add DEVEUI and Name
  1. In STEP 4 Plan, select the preferred subscription plan, and click Add 1 device to add the device. For this example, choose Free.
Figure 10725: Select a subscription plan
  1. The registered device can now be viewed on the Devices tab.
Figure 10726: Registered Device
Create a Payload Decoder​
  1. Click the successfully registered device and go to the Configuration tab. Scroll down to the Payload Decoder field, then copy and save the decoder code.
Figure 10727: Configuration tab
Figure 10728: Decoder code
Click to view the code 
function lppDecode (bytes) {
var sensor_types = {
	0: { 'size': 1, 'name': ' digital_in ', 'signed': false, 'divisor': 1 },
	1: { 'size': 1, 'name': ' digital_out ', 'signed': false, 'divisor': 1 },
	2: { 'size': 2, 'name': ' analog_in ', 'signed': true, 'divisor': 100 },
	3: { 'size': 2, 'name': ' analog_out ', 'signed': true, 'divisor': 100 },
	100: { 'size': 4, 'name': 'generic', 'signed': false, 'divisor': 1 },
	101: { 'size': 2, 'name': 'illuminance', 'signed': false, 'divisor': 1 },
	102: { 'size': 1, 'name': 'presence', 'signed': false, 'divisor': 1 },
	103: { 'size': 2, 'name': 'temperature', 'signed': true, 'divisor': 10 },
	104: { 'size': 1, 'name': 'humidity', 'signed': false, 'divisor': 1 },
	112: { 'size': 2, 'name': ' humidity_prec ', 'signed': true, 'divisor': 10 },
	113: { 'size': 6, 'name': 'accelerometer', 'signed': true, 'divisor': 1000 },
	115: { 'size': 2, 'name': 'barometer', 'signed': false, 'divisor': 10 },
	116: { 'size': 2, 'name': 'voltage', 'signed': false, 'divisor': 100 },
	117: { 'size': 2, 'name': 'current', 'signed': false, 'divisor': 1000 },
	118: { 'size': 4, 'name': 'frequency', 'signed': false, 'divisor': 1 },
	120: { 'size': 1, 'name': 'percentage', 'signed': false, 'divisor': 1 },
	121: { 'size': 2, 'name': 'altitude', 'signed': true, 'divisor': 1 },
	125: { 'size': 2, 'name': 'concentration', 'signed': false, 'divisor': 1 },
	128: { 'size': 2, 'name': 'power', 'signed': false, 'divisor': 1 },
	130: { 'size': 4, 'name': 'distance', 'signed': false, 'divisor': 1000 },
	131: { 'size': 4, 'name': 'energy', 'signed': false, 'divisor': 1000 },
	132: { 'size': 2, 'name': 'direction', 'signed': false, 'divisor': 1 },
	133: { 'size': 4, 'name': 'time', 'signed': false, 'divisor': 1 },
	134: { 'size': 6, 'name': ' gyrometer ', 'signed': true, 'divisor': 100 },
	135: { 'size': 3, 'name': ' colour ', 'signed': false, 'divisor': 1 },
	136: { 'size': 9, 'name': ' gps ', 'signed': true, 'divisor': [10000, 10000, 100] },
	137: { 'size': 11, 'name': ' gps ', 'signed': true, 'divisor': [1000000, 1000000, 100] },
	138: { 'size': 2, 'name': ' voc ', 'signed': false, 'divisor': 1 },
	142: { 'size': 1, 'name': 'switch', 'signed': false, 'divisor': 1 },
	188: { 'size': 2, 'name': ' soil_moist ', 'signed': false, 'divisor': 10 },
	190: { 'size': 2, 'name': ' wind_speed ', 'signed': false, 'divisor': 100 },
	191: { 'size': 2, 'name': ' wind_direction ', 'signed': false, 'divisor': 1 },
	192: { 'size': 2, 'name': ' soil_ec ', 'signed': false, 'divisor': 1000 },
	193: { 'size': 2, 'name': ' soil_ph_h ', 'signed': false, 'divisor': 100 },
	194: { 'size': 2, 'name': ' soil_ph_l ', 'signed': false, 'divisor': 10 },
	195: { 'size': 2, 'name': 'pyranometer', 'signed': false, 'divisor': 1 },
	203: { 'size': 1, 'name': 'light', 'signed': false, 'divisor': 1 },
};


function arrayToDecimal (stream, is_signed , divisor) {


	var value = 0;
	for (var i = 0; i < stream.length ; i ++) {
		if (stream[ i ] > 0xFF)
			throw 'Byte value overflow!';
		value = (value << 8) | stream[ i ];
	}


	if ( is_signed ) {
		var edge = 1 << ( stream.length ) * 8; // 0x1000..
		var max = (edge - 1) >> 1; // 0x0FFF.. >> 1
		value = (value > max) ? value - edge : value;
	}


	value /= divisor;


	return value;


}


var sensors = [];
var i = 0;
while ( i < bytes.length ) {


	var s_no = bytes[ i ++];
	var s_type = bytes[ i ++];
	if ( typeof sensor_types [ s_type ] == 'undefined') {
		throw 'Sensor type error!: ' + s_type ;
	}


	var s_value = 0;
	var type = sensor_types [ s_type ];
	switch ( s_type ) {


		case 113: //Accelerometer
		case 134: // Gyrometer
			s_value = {
				'x': arrayToDecimal ( bytes.slice ( i + 0, i + 2), type.signed , type.divisor ),
				'y': arrayToDecimal ( bytes.slice ( i + 2, i + 4), type.signed , type.divisor ),
				'z': arrayToDecimal ( bytes.slice ( i + 4, i + 6), type.signed , type.divisor )
			};
			break;
		case 136: // GPS Location
			s_value = {
				'latitude': arrayToDecimal ( bytes.slice ( i + 0, i + 3), type.signed , type.divisor [0]),
				'longitude': arrayToDecimal ( bytes.slice ( i + 3, i + 6), type.signed , type.divisor [1]),
				'altitude': arrayToDecimal ( bytes.slice ( i + 6, i + 9), type.signed , type.divisor [2])
			};
			break;
		case 137: // Precise GPS Location
			s_value = {
				'latitude': arrayToDecimal ( bytes.slice ( i + 0, i + 4), type.signed , type.divisor [0]),
				'longitude': arrayToDecimal ( bytes.slice ( i + 4, i + 8), type.signed , type.divisor [1]),
				'altitude': arrayToDecimal ( bytes.slice ( i + 8, i + 11), type.signed , type.divisor [2])
			};
			sensors.push ({
				'channel': s_no ,
				'type': s_type ,
				'name': 'location',
				'value': "(" + s_value.latitude + "," + s_value.longitude + ")"
			});
			sensors.push ({
				'channel': s_no ,
				'type': s_type ,
				'name': 'altitude',
				'value': s_value.altitude
			});
			break;
		case 135: // Color
			s_value = {
				'r': arrayToDecimal ( bytes.slice ( i + 0, i + 1), type.signed , type.divisor ),
				'g': arrayToDecimal ( bytes.slice ( i + 1, i + 2), type.signed , type.divisor ),
				'b': arrayToDecimal ( bytes.slice ( i + 2, i + 3), type.signed , type.divisor )
			};
			break;


		default: // All the rest
			s_value = arrayToDecimal ( bytes.slice ( i , i + type.size ), type.signed , type.divisor );
			break;
	}


	sensors.push ({
		'channel': s_no ,
		'type': s_type ,
		'name': type.name,
		'value': s_value
	});


	i += type.size ;


}


return sensors;
}


// For TTN, Helium and Datacake
function Decoder(bytes, fport ) {
// bytes = input.bytes ;
// fPort = input.fPort ;


// flat output (like original decoder):
var response = {};
lppDecode (bytes, 1). forEach (function (field) {
	response[field['name'] + '_' + field['channel']] = field['value'];
});


// Enable only for Datacake
response['LORA_RSSI'] = (!! normalizedPayload.gateways && !! normalizedPayload.gateways [0] && normalizedPayload.gateways [0]. rssi ) || 0;
response['LORA_SNR'] = (!! normalizedPayload.gateways && !! normalizedPayload.gateways [0] && normalizedPayload.gateways [0].snr) || 0;
response['LORA_DATARATE'] = normalizedPayload.data_rate ;


return response;
}
  1. Scroll down until you find the Fields section at the bottom part of the page, then click the +Add Field button
Figure 10729: Add Field
  1. Fill out the fields, as shown in Figure 37, to configure the stored data in the device.
Figure 10730: Configuration fields
NOTE
  • Enter an appropriate name in the Name field.
  • The Identifier field will be automatically filled in based on the name.
  • When an uplink is received, refresh the page and the CURRENT VALUE field will be updated.
  • Leave everything else as default, and click Add Field to complete the setup.
  1. When completed, it will look the same, as shown in Figure 38.
Figure 10731: Successfully added fields
Create a Dashboard
  1. To create a dashboard, click the edit mode switch on the Dashboard tab of the device on Datacake.
Figure 10732: Turn on the edit mode switch
  1. Click +Add Widget to add a visualization widget.
Figure 10733: Add visualization widget
  1. Select Value from the menu to create a new dashboard.
Figure 10734: Select Value to create a new dashboard
NOTE

You can select different types of widgets to accommodate various data formats.

  1. In the Title field under the Basics tab, name the widget as Temperature.
Figure 10735: Name the widget
  1. Under the Data tab, click the Field tab dropdown arrow, select Temperature, and set the unit to °C.
Figure 10736: Set the unit
  1. Under the Gauge tab, select the gauge type and color, set the range of values for the widget, and then click Save.
Figure 10737: Set the widget type
  1. To add another widget, ensure the edit mode switch is ON, then click the +Add Widget button again.
Figure 10738: Added Widget
  1. After adding the widgets, turn off the edit mode switch to save the edits.
Figure 10739: Save the edits

Built-In Network Server Setup​

The RAK gateway comes with a built-in NS, which eliminates the need to deploy NS in the cloud or locally. This gateway is suitable for small-sized industrial application scenarios and offers various advantages such as cost savings, reduced R&D investment, high execution efficiency, and shorter delays.

The built-in network server of the RAK gateway provides MQTT and HTTP integration that allows for post-processing data and implementing solutions based on the needs.

This section will use the public MQTT broker integration as an example to demonstrate how to use the built-in network server to create a visualization application on ThingsBoard.

Figure 10740: Gateway Built-In NS application scenario
Configure the ThingsBoard​
  1. Log in to ThingsBoard. If you don't have an account yet, create one before proceeding.
Figure 10741: ThingsBoard authentication page
  1. After successfully logging in, you will be directed to the ThingsBoard homepage.
Figure 10742: ThingsBoard homepage
  1. Navigate to the Integration center > Data converters in the left navigation tree to create a data converter for the uplink.
Figure 10743: Create a data converter
  1. Click the Add Data Converter icon and choose the Create new converter option.
Figure 10744: Create a data converter
  1. Enter the name of the decoder in the Name field (for example, Uplink decoder), leave the Type field as Uplink, and select the JavaScript option.
Figure 10745: Add the decoder code
  1. Edit the decoder code by copying the following code into the edit box. Click Add to include the uplink decoder.
Click to view the code 
/** Decoder **/
//decode payload to string
var payloadStr = decodeToString (payload);
var data = JSON.parse ( payloadStr ).data;
var bytes = atob (data).split('').map(function (c) {
return c.charCodeAt (0);
});


var values = {};
let i = 0;
while ( i < bytes.length ) {
var channelId = (bytes[ i ] << 8) | bytes[ i + 1];
var value;
switch ( channelId ) {
case 0x0167:
value = (bytes[ i + 2] << 8) | bytes[ i + 3];
      values.temperature = value / 10.0;
      i += 4;
break;
case 0x0268:
value = bytes[ i + 2];
      values.humidity = value;
      i += 3;
break;
default:
break;
}
}


var integrationName = 'MQTT Integration';
var deviceName = ' rak1901 ';
var result = {
  deviceName : deviceName ,
attributes: {
    integrationName : metadata[' integrationName '],
temperature: values.temperature ,
humidity: values.humidity ,
},
};


/** Helper functions **/


function decodeToString (payload) {
return String.fromCharCode.apply (String, payload);
}


return result;
  1. Navigate to the Integration Center > Integrations menu and click the Add Integration icon to add the MQTT integration.
Figure 10746: Add the MQTT integration
  1. Enter the name of the integration (for example, MQTT Integration) in the Name field and select MQTT in the Type drop-down menu. Click Next to continue.
Figure 10747: Fill in the integration name
  1. In the Uplink data converter options, click Select existing to choose the previously created decoder (Uplink Decoder), then click Next.
Figure 10748: Select the created decoder

  1. In the Downlink data converter interface, no configuration is necessary and just click Skip to bypass this setup.

  2. Configure connection options. Host is the MQTT broker address used for messages. The Host of the external MQTT broker used in this example is broker.hivemq.com. You can choose to use other brokers with a different Host.

  3. Enter the address broker.hivemq.com in the Host field, with the port number 1883. Click the Add topic filter button to configure the subscription topic.

Figure 10749: Configure the connection options
Configure the subscription topic 
application/{{application_name}}/device/{{device_EUI}}/join
application/{{application_name}}/device/{{device_EUI}}/rx
application/{{application_name}}/device/{{device_EUI}}/tx
application/{{application_name}}/device/{{device_EUI}}/ack
application/{{application_name}}/device/{{device_EUI}}/status
  • application_name: The application ID created in the gateway.
  • device_EUI: The device EUI of the end device.
  1. Modify the parameter values corresponding to the topics based on the actual application created and the device used. After configuring the details, click the Add button to save and complete the settings.
NOTE

The values in the subscription topic must be all lowercase. For example, application/1/device/0123456789abcdef/join.

Figure 10750: Configure and add the subscription topics
Configure the Gateway​

This section will use the RAK7268 V2 WisGate Edge Lite 2 as an example.

  1. To access the gateway web management platform, refer to the WisGateOS V2 user manual for details.
Figure 10751: WisGate OS Web Management Platform
  1. After successfully logging in, navigate to the LoRa® menu in the left navigation tree and set the Work mode of the gateway to the Built-in network server.
Figure 10752: Set the Work mode of the gateway
  1. Once done with the setting, click the Applications tab, then the Add application button. You can also click add one now text link to add a new application.
Figure 10753: Applications tab
  1. Configure the following information: Application name, Application description, and Application Type.
Figure 10754: Configure the Application

  • Unified Application key: Choose this option if all devices will use the same application key. Once selected, a field for the application key appears, where you can manually type in an application key or click the Autogenerate button to generate one.

  • After enabling the Auto Add Device option, configure the Application EUI option. The value needs to be consistent with the node value. Once you have verified the application EUI and key, the device will be added automatically to the application.

Figure 10755: Auto Add Device
NOTE

You can obtain the values by either querying the end device or generating it automatically and modifying the corresponding value of the device synchronously.

  1. Once you've completed the configuration, click on Save Application to add the new application.

  2. In the application list, locate the newly created application and navigate to the End devices tab. If you've enabled the Auto Add Device function, the device will be automatically registered upon the addition request.

Figure 10756: End devices tab
  1. Click the Add end device button. In the End device information interface, fill in the following information:
  • Activation Mode: Select the activation mode of the device: OTAA or ABP.
    • Choosing ABP mode creates two additional fields: Application Session Key and Network Session Key.
    • In this example, use OTAA activation mode.
  • End device (group) name: Enter the name of the end device or the group it belongs to.
  • End device description (optional): Optionally provide a description for the end device.
  • Class: Select Class A for device's operating mode.
  • Frame Counter Width: Keep the default value.
  • LoRaWAN MAC Version: The protocol version (v1.0.3) of the end device.
  1. After completing, click Add end devices to proceed to the next step.
Figure 10757: Add new end devices
  1. In the Adding end devices interface, enter the device EUI in the End Device EUI (Main) field and select the Add to End Devices list button. Then click Add end devices to complete adding the end device.
NOTE
  • The device EUI configured here must match the end device. You can either obtain it by querying the end device or entering one (1) EUI and synchronously updating the corresponding value of the end device.
  • If the EUI is correct, the device will be displayed in the End devices list.
  • If the EUI is incorrect, the device will be displayed in the End devices with an error section.
Figure 10758: Add the device to the device list
  1. Click the Add button to confirm adding the device.
Figure 10759: Confirm to add the end device
  1. When finished, enter the End devices interface, where you can see the created end device.
Figure 10760: End Device Created
Connect Sensor Hub to the Built-In Network Server​

For specific configuration on how to connect Sensor Hub to the server, refer to SensorHub Network Configuration > LoRaWAN Application Scenario.

Once completed, the device will join the network. As shown in Figure 68, the end device SensorHub has successfully connected to the gateway's built-in server.

Figure 10761: End device SensorHub has been connected
Configure the MQTT Integration​
  1. Navigate to the LoRa® > Configuration > Integration Interface Parameters section.
  2. Toggle the Enable Integration Interface option and select Generic MQTT as the Integration mode.
Figure 10762: Set up MQTT integration

  1. In the MQTT Broker Address option, enter broker.hivemq.com, then click Save changes.

  2. After the device has joined and has been sending uplink data, check the uplink data in ThingsBoard > Integrations > Your Integration > Events.

Figure 10763: View the gateway uplink data
Visualize Data Through ThingsBoard​
  1. After creating the data converter, integrating, and obtaining some data in the Event tab, check the automatically created devices based on the decoder in the Entities > Devices > Groups tab.
Figure 10764: Check the device
  1. Click the group named All in the Device groups menu to automatically create a decoder device.
Figure 10765: Automatically created decoder device
  1. Click the device, navigate to the Attributes tab to view the node data.
Figure 10766: Node data
  1. To visualize the data, simply select the values you wish to display, then click the Show on widget button.
Figure 10767: Data visualization
  1. On the next page, select the desired widget for the data from the Current bundle drop-down menu. In this example, choose Analogue gauges as it has the humidity widget, then click Add to dashboard.
Figure 10768: Choose an appropriate visualization chart
Figure 10769: Selecting a widget
  1. By default, there is no dashboard in the profile, so you need to select Create new dashboard and enter a name for the dashboard in the new dashboard title field.
  • In this guide, name the dashboard SensorHub_Environmental.
Figure 10770: Enter the dashboard name
  1. After setting the dashboard name, click the Add button to add more widgets. Alternatively, check the Open dashboard option to automatically open the created dashboard after adding the widget.
NOTE

If the Open dashboard option is not selected, you can still easily view the added widgets via Dashboard groups > All > [Group Name].

Figure 10771: Dashboard created
  1. You can visualize other data from the device following the same steps as above. The only difference is that when adding the widget, instead of Create a new dashboard, click Select existing dashboard.
Figure 10772: Adding widgets

NB-IoT/LTE CAT-M1 Application​

Connect Sensor Hub to MQTT Server​

In the Network Server and Visualization Configuration section, the server has been set as a public MQTT broker: broker.hivemq.com. You can also choose other brokers or servers, such as AWS IoT Core (optional), according to the actual usage scenario.

Figure 10773: NB-IoT/LTE CAT-M1 Application Scenario

Visualize Data Through Datacake​

In this example, you will use Datacake as the visualization platform. Datacake is a versatile IoT platform designed to visualize data from nodes in a user-friendly manner.

To get started, create an account on the official website and log in.

Add Sensor Hub to Datacake​
  1. After logging in to your account, navigate to the Devices tab and click +Add Device to proceed with adding the Sensor Hub end device.
Figure 10774: Add the end device, SensorHub
  1. Select the API option and click Next to proceed.
Figure 10775: Select API
  1. As the device is new and there's no ready-made template, choose New Product from the Datacake Product options. Enter the device name in the Product Name field, then click Next to proceed.
Figure 10776: Select New Product
  1. The SERIAL NUMBER field can be left blank. Datacake will randomly generate a serial number for the device, then click Next.
Figure 10777: Add devices
  1. Select the preferred subscription plan, then click Add 1 device. For this example, choose Free.
Figure 10778: Select a subscription plan
  1. The registered device can now be viewed on the Devices tab.
Figure 10779: Registered device
MQTT Configuration​
  1. Click the name of the device you just created in the list to enter the interface, then select the Configuration tab.
Figure 10780: Configuration tab
  1. Scroll down to the API Configuration option and copy the Serial number. Save it locally for later use.
Figure 10781: Copy the serial number

  1. Continue scrolling down to the MQTT Configuration option and configure the external MQTT Broker.

  2. Click +Add new MQTT server and configure the relevant parameters.

Figure 10782: Configure the external MQTT Broker
  1. Fill in the relevant information based on the actual server used, then click Test Connection to verify whether Datacake can successfully connect to the MQTT Broker.
Figure 10783: Configure the relevant parameters
NOTE

If SSL/TLS encryption and authentication are set for more secure communication, ensure to configure them accordingly in this section. However, for this example, you can skip this option.

  1. If the connection is successful, you will see the message Connection successful. Click Add MQTT Server to complete the addition of the MQTT server.
Figure 10784: Configure the relevant parameters
  1. After successfully adding the MQTT server, click on +Add Uplink Decoder to add a decoder.
Figure 10785: Add MQTT Server
  1. A new window will appear, and fill in the fields according to your project.
Figure 10786: Add Uplink Decoder
  • Subscribe to topics: Configure the subscription topics, that is, the value of the Publish Topic configured in the Network Server and Visualization Configuration section.
  • Decoder function: Copy the following decoding code and paste it into the Decoder function space.
function Decoder(topic, payload) {
var decoded = [];
    var data = JSON.parse(payload.replace(/\s*/g,""));
    for (var key in data) {
        decoded.push(
            {
                device: "7d9afdfb-97ea-4de1-ab15-36d7e69629e6",
                field: key,
                value: data[key]
            }
        )
    }
    return decoded;
}
NOTE

In the above code, make sure that the parameter serial_number (device: 7d9afdfb-97ea-4de1-ab15-36d7e69629e6) matches the serial number saved locally earlier.

  1. Once completed, click Add uplink decoder.
  2. In the Fields option, click +Add Field to show the monitoring values of the devices. Each device can create a certain number of fields, also known as a data point.
Figure 10787: Add Field
  1. Set the necessary parameters of the Field. For Fields with multiple data points, add them one by one. Once done, click Add Field.
Figure 10788: Set the related parameters of the field
NOTE

The Identifier field will be automatically filled based on the name.

  1. Once the uplink data is received, the Current value column in the Fields list will display the current monitoring value from the sensor.
Figure 10789: Added sensor monitoring values
  1. Follow Steps 10-11 to add other monitoring parameters.
Figure 10790: Add other monitoring parameters individually
Create a Dashboard to Visualize Data​

Dashboards can be customized depending on the specific needs and preferences of a project. Follow the steps below to add widgets and visualize the data.

  1. On the device details page, navigate to the Dashboard tab, then toggle on the edit mode switch.
  2. Click on the +Add Widget button to add a widget for visualizing data.
Figure 10791: Open the edit mode
  1. Choose what type of widgets you want to display. For this example, select Value to visualize temperature monitoring values.
Figure 10792: Select and add widgets for visualizing data
  1. Go to the Data tab and choose the data you want to visualize from the available Field options. For this example, select Temperature and set the unit of the field to °C.
Figure 10793: Select the visualization data field
  1. After configuring the widget, click Save. You should now see the successfully created temperature widget on the dashboard interface.
Figure 10794: Successfully created temperature widget

  1. To add more parameter widgets, click the +Add Widget button again with the edit mode toggle switch ON, then repeat Steps 2-5.

  2. Once done with the dashboard configuration, turn off the edit mode switch to save the settings.

Figure 10795: Environmental Monitoring data visualization