Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23

From 155.1 to 156.1 From 177.1 to 178.1

From version 156.1

edited by Dilisi S
on 2025/03/17 00:34

Change comment: Uploaded new attachment "mqtt-uplink.png", version {1}

To version 177.1

edited by Dilisi S
on 2025/03/26 21:03

Change comment: Mar 26 edits - part 2

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (1 modified, 6 added, 0 removed)

Details

Page properties

Content

@@ -67,7 +67,6 @@
  [[image:thingsboard-6.png||height="244" width="500"]]
--(% class="wikigeneratedid" %)
  == 2.2 HiveMQ Cloud ==
  === 2.2.1 HiveMQ Cloud ===
@@ -165,19 +165,37 @@
  [[image:ins1.png||height="310" width="500"]]
--= 3. Data Converters =
++= 3. Creating Devices =
++First, you need to create devices in ThingsBoard to represent your physical devices. For example, you can name it **Device A**, and the second device could be **Device B** or any name you prefer. The device name should be unique within the **Devices** space.
++
++
++In the left navigation, click Entities -> Devices.
++
++Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
++
++In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
++
++Click the **Add** button.
++
++Skip the **connectivity testing** by clicking the **Close** button.
++
++The device is created and listed on the **Devices** page. Note that its initial state is **Inactive** because it has not received any data yet.
++
++
++= 4. Data Converters =
++
++
  In **ThingsBoard**, **Data Converters** are components used to transform incoming or outgoing data between different formats, typically to convert raw telemetry data from devices into a structured format that ThingsBoard can understand, or vice versa.
--== 3.1 Uplink ==
++== 4.1 Uplink ==
  In the left navigation, click **Integrations center**, and then click **Data converters**.
--
  [[image:data-converters-list-empty.png]]
@@ -190,30 +190,54 @@
  The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
--Click on the **TBEL** button if not selected it by default. Delete the existing decoder function in the code editor. Now copy and paste the following decoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
++Click on the **TBEL** button if it has not been selected by default.
++The default TBEL function is shown below.
++
++
  {{code language="JavaScript"}}
++// Decode an uplink message from a buffer
++// payload - array of bytes
++// metadata - key/value object
++
  /** Decoder **/
  // decode payload to string
  var payloadStr = decodeToString(payload);
--var data = JSON.parse(payloadStr);
--var deviceName =  metadata.topic.split("/")[3];
  // decode payload to JSON
--var deviceType = 'sensor';
++// var data = decodeToJson(payload);
--// Result object with device attributes/telemetry data
++var deviceName = 'Device A';
++var deviceType = 'thermostat';
++var customerName = 'Customer C';
++var groupName = 'thermostat devices';
++var manufacturer = 'Example corporation';
++// use assetName and assetType instead of deviceName and deviceType
++// to automatically create assets instead of devices.
++// var assetName = 'Asset A';
++// var assetType = 'building';
++
++// Result object with device/asset attributes/telemetry data
  var result = {
--    deviceName: deviceName,
--    deviceType: deviceType,
--    attributes: {
--        integrationName: metadata['integrationName'],
--    },
--    telemetry: {
--        temperature: data.temperature,
--        humidity: data.humidity,
--    }
++// Use deviceName and deviceType or assetName and assetType, but not both.
++   deviceName: deviceName,
++   deviceType: deviceType,
++// assetName: assetName,
++// assetType: assetType,
++// customerName: customerName,
++   groupName: groupName,
++   attributes: {
++       model: 'Model A',
++       serialNumber: 'SN111',
++       integrationName: metadata['integrationName'],
++       manufacturer: manufacturer
++   },
++   telemetry: {
++       temperature: 42,
++       humidity: 80,
++       rawData: payloadStr
++   }
  };
  /** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
@@ -221,91 +221,36 @@
  return result;
  {{/code}}
++We use the same decoder function for all our devices. However, you need to modify a few things for each device. Among these, **deviceName** is a **mandatory** field. You should assign a device name to the **deviceName** field that matches the name of your device in the **Devices** section.
--Click on the **Add** button.
++For example, if your device name is **Device B**, you can change **Device A** to **Device B**.
--
--[[image:add-uplink-data-converter.png||height="529" width="500"]]
--
--
--You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
--
--[[image:data-converter-list-showing-uplink-dc.png]]
--
--
--
--== 3.2 Downlink ==
--
--
--On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
--
--
--[[image:create-new-converter-menu.png||width="500"]]
--
--
--
--The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
--
--Click on the **TBEL** button if not selected it by default. Now copy and paste the following encoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This encoder function is compatible for both NB and CB series devices.
--
--
  {{code language="JavaScript"}}
--// Encode downlink data from incoming Rule Engine message
--
--// msg - JSON message payload downlink message json
--// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
--// metadata - list of key-value pairs with additional data about the message
--// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
--
--/** Encoder **/
--
--var data = {};
--
--// Process data from incoming message and metadata
--
--data.tempFreq = msg.temperatureUploadFrequency;
--data.humFreq = msg.humidityUploadFrequency;
--
--data.devSerialNumber = metadata['ss_serialNumber'];
--
--// Result object with encoded downlink payload
--var result = {
--
--    // downlink data content type: JSON, TEXT or BINARY (base64 format)
--    contentType: "JSON",
--
--    // downlink data
--    data: JSON.stringify(data),
--
--    // Optional metadata object presented in key/value format
--    metadata: {
--            topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
--    }
--
--};
--
--return result;
++var deviceName = 'Device A';
++var deviceType = 'thermostat';
++var customerName = 'Customer C';
++var groupName = 'thermostat devices';
++var manufacturer = 'Example corporation';
  {{/code}}
--Click on the **Add** button.
++Once you modify the decoder function, click on the **Add** button.
++[[image:mqtt-uplink.png||width="500"]]
--[[image:add-downlink-data-converter.png||height="529" width="500"]]
--You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
++You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
--[[image:data-converters-list.png]]
++[[image:data-converter-list-showing-uplink-dc.png]]
++= 5. Add Integration =
--= 4. Add Integration =
--
  In the left navigation, click **Integrations center**, and then click **Integrations**.
@@ -330,7 +330,6 @@
  Click **Next** button.
--
  [[image:add-integration-basic-settings.png||height="511" width="500"]]
@@ -342,31 +342,31 @@
  Click **Next** button.
--
  [[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
  **Downlink data converter:**
--* Click on the **Select existing** button.
--* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
++Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
--Click **Next** button.
++* Click on the **Skip **button in the Downlink data converter section.
++Click **Skip** button.
--[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
++[[image:integration-dl-skip.png||height="511" width="500"]]
++
  **Connection:**
--* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
++* **Host**: Cluster URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
  * **Port**: 8883
  * **Credentials**: Basic
  * **Enable SSL**: YES
  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
--* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
++* **Topic: v1/devices/me/telemetry** (The topic can be anything; you can even use just the device name. For example, you can use your device name here, such as devices/a/telemetry.)
  * **QoS:** 0-At most once
  [[image:add-integration-connection.png||height="511" width="500"]]
@@ -399,48 +399,35 @@
  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
--
  [[image:new-integration-pending.png]]
--= 5. Verifying the receipt of data from virtual devices =
++= 6. Verifying the receipt of data from virtual devices =
--== 5.1 How does it work? ==
++== 6.1 How does it work? ==
  We use the Mosquitto MQTT client to simulate MQTT messages, acting as a virtual device. First, install the Mosquitto client on your computer from [[this link>>url:https://mosquitto.org/download/]]. The Mosquitto client publishes messages to the MQTT broker (HiveMQ) on a specified MQTT topic. ThingsBoard subscribes to these messages using the same topic.
--The Mosquitto client publishes messages on the topic v1/devices/[device_name]/telemetry. The [device_name]placeholder can be replaced with any device name, for example, 'S31B-NB'. Then, the MQTT topic would be v1/devices/S31B-NB/telemetry.
++The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
--On the ThingsBoard side, we configure the MQTT topic subscription as v1/devices/+/telemetry. The + wildcard represents any device name and allows ThingsBoard to automatically create (provision) a device with that name, such as S31B-NB, for example.
++(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows, which is common for all **~-~-NB** and **~-~-CB** series devices. The **IMEI** field is mandatory and is used to provision a new device with the name assigned to it in ThingsBoard.
--
--**The new device is created the first time the MQTT topic is received. For subsequent MQTT topics with the same device name, no duplicate devices will be created.**
--
--
--For example, if you send two MQTT messages with different device names in the topic:
--
--1. v1/devices/**S31B-NB**/telemetry
--1. v1/devices/**LDS25-NB**/telemetry
--
--ThingsBoard will create two devices named **S31B-NB** and **LDS25-NB** in the **//Devices//** section.
--
--
--The MQTT payload format is as follows, which is common for all ~-~-NB and ~-~-CB series devices:
--
  {{code language="none"}}
--{"temperature":10.4, "humidity":85}
++{"IMEI": "S31B-NB", "temperature": 27, ......}
  {{/code}}
++Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
++
  == 5.2 Sending messages ==
--On the terminal, issue the following MQTT command which simulates the device S31B-NB. The message payload contains the fields temperature and humidity, which hold the values 10.4 and 85, respectively. This payload is also (technically) known as telemetry.
++On the terminal, issue the following MQTT command which simulates the device S31B-NB. The message payload contains the fields temperature and humidity, which hold the values S31B-NB and 27, respectively. This payload is also (technically) known as telemetry.
  {{code language="none"}}
--mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":10.4, "humidity":85}'
++mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 27}'
  {{/code}}
  If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
@@ -452,40 +452,51 @@
  Also, a new device named **S31B-NB** will appear under **//Entities -> Devices -> All//**. This means the first MQTT message triggers ThingsBoard to provision a device named **S31B-NB**.
--[[image:device-provision-1.png]]
++[[image:new-device.png]]
--Click on the device S31B-NB on the devices list to see its details.
++== 6.3 Viewing messages ==
--Then go to the **Latest telemetry** tab.
--You can see the fields temperature and humidity with the values you previously sent using the MQTT message.
++Go back to the **Integrations** page.
++Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
--[[image:telemetry-1.png]]
++Click on the **Edit** button (//**pen icon**//).
++Click on the **Disabled** button in the upper-right corner.
--Now, change the values of the fields and send the MQTT message again. For example, set temperature to 20 and humidity to 70. Observe how the values update in //Latest Telemetry//.
++Turn on the **All messages (15 min)** option. This will enable displaying all messages in the **Events** tab. This setting will expire in 15 minutes, and you will need to repeat the same steps if you want to view the messages in the Events tab later.
++Click on the **Apply** button.
--[[image:telemetry-2.png]]
++Then click on the **Apply changes** (//**tick icon**//) button.
--Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
++[[image:Screenshot 2025-03-18 at 09.23.10.png]]
--{{code language="none"}}
--mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/LDS25-NB/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":11, "humidity":87}'
--{{/code}}
++Now go to the **Events** tab.
--Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
++Select the Event type as **Debug** from the dropdown list.
++Now you can see all the Uplink messages you are simulating through the MQTT broker. The status should be OK if there is no errors in your integration.
--[[image:device-provision-2.png]]
++[[image:Screenshot 2025-03-16 at 18.38.59.png]]
--= 6. Creating a Dashboard =
++Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
++
++
++[[image:Screenshot 2025-03-16 at 18.39.12.png]]
++
++
++Now, you have successfully tested your integration with a simulated uplink payload and verified that it is received by ThingsBoard, and the device is provisioned.
++
++
++= 7. Creating a Dashboard =
++
  ThingsBoard **Dashboards** provide a powerful way to visualize and monitor real-time and historical data from connected devices. They allow users to create interactive, customizable panels displaying telemetry data, device status, and other key metrics. With a variety of widgets, including charts, maps, and tables, dashboards help users gain insights, track trends, and manage IoT deployments efficiently.
@@ -492,6 +492,11 @@
  This section guides you on how to create a dashboard to display temperature and humidity data from the device on a time-series chart. You may also use other widgets in ThingsBoard to display data according to your requirements.
++First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
++
++{{code language="none"}}mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 22, "humidity":80}'{{/code}}
++
++
  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
@@ -548,11 +548,11 @@
  {{code language="none"}}
--mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":20, "humidity":70}'
++mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 22, "humidity":70}'
--mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":22, "humidity":71}'
++mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 27, "humidity":72}'
--mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":18, "humidity":79}'
++mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 19, "humidity":80}'
  {{/code}}
@@ -562,10 +562,10 @@
  [[image:timeseries-4.png||height="316" width="700"]]
--= 7. Configure NB-IoT Sensor =
++= 8. Configure NB-IoT Sensor =
--Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
++Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
@@ -573,8 +573,8 @@
  **AT Commands**
  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
--* **AT+SUBTOPIC=<MQTT topic>**
--* **AT+PUBTOPIC=<MQTT topic>**
++* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
++* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
  * **AT+CLIENT=null**
  * **AT+UNAME=<MQTT Username>**
  * **AT+PWD=<MQTT Password>**
@@ -581,3 +581,16 @@
  * **AT+SERVADDR=<Broker address, Port>**
  Test your uplink by pressing the ACT button for 1 second.
++
++
++
++The following image shows the uplink payload of a real Dragino device. The publish topic is **TS01-NB**, and the device name is **861275077962896**, which is represented by the **IMEI**.
++
++{{info}}
++The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
++{{/info}}
++
++[[image:image-4.png]]
++
++
++

add-integration-connection.png

Size

@@ -1,1 +1,1 @@
--124.4 KB
++158.1 KB

Content

Screenshot 2025-03-16 at 18.38.59.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+221.2 KB

Content

Screenshot 2025-03-16 at 18.39.12.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+211.9 KB

Content

Screenshot 2025-03-18 at 09.23.10.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+78.7 KB

Content

image-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+96.0 KB

Content

integration-dl-skip.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+105.5 KB

Content

new-device.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+143.3 KB

Content

Changes for page ThingsBoard

Summary

Details

Applications

Navigation