Changes for page ThingsBoard

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

From 155.1 to 154.1 From 188.1 to 187.1

From version 187.1

edited by Dilisi S
on 2025/03/27 22:51

Change comment: Uploaded new attachment "add-integartion-connetcion.png", version {1}

To version 155.1

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

Change comment: Mar 16 edits - part 1

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (2 modified, 0 added, 14 removed)

Details

Page properties

Content

@@ -67,6 +67,7 @@
  [[image:thingsboard-6.png||height="244" width="500"]]
++(% class="wikigeneratedid" %)
  == 2.2 HiveMQ Cloud ==
  === 2.2.1 HiveMQ Cloud ===
@@ -164,138 +164,147 @@
  [[image:ins1.png||height="310" width="500"]]
--= 3. Creating Devices =
++= 3. Data Converters =
--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 **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.
--In the left navigation, click Entities -> Devices.
++== 3.1 Uplink ==
--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**.
++In the left navigation, click **Integrations center**, and then click **Data converters**.
--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.
++[[image:data-converters-list-empty.png]]
--= 4. Data Converters =
++On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
--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.
++[[image:create-new-converter-menu.png||height="259" width="500"]]
--== 4.1 Uplink ==
++The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
--In the left navigation, click **Integrations center**, and then click **Data converters**.
++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.
++{{code language="JavaScript"}}
++/** Decoder **/
--[[image:data-converters-list-empty.png]]
++// 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';
--On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
++// Result object with device attributes/telemetry data
++var result = {
++    deviceName: deviceName,
++    deviceType: deviceType,
++    attributes: {
++        integrationName: metadata['integrationName'],
++    },
++    telemetry: {
++        temperature: data.temperature,
++        humidity: data.humidity,
++    }
++};
++/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
++return result;
++{{/code}}
--[[image:create-new-converter-menu.png||height="259" width="500"]]
++Click on the **Add** button.
--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 it has not been selected by default.
--Modify the default TBEL function to match with your device as described below:
++[[image:add-uplink-data-converter.png||height="529" width="500"]]
--* Uncomment** line 11**:
++You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
--//var data = decodeToJson(payload)//
++[[image:data-converter-list-showing-uplink-dc.png]]
--* **Line 13**: Assign your device name to the **deviceName** field. - We used **Device A** as it is to match with our device, **Device A **in the Devices section.
--* From **line 38**: Modify the telemetry section to allow parsed data to be assigned to the fields.
--//telemetry: {
--       temperature: data.temperature,
--       humidity: data.humidity,
--       rawData: payloadStr
--   }//
++== 3.2 Downlink ==
--The modified uplink decoder function to match with **Device A** is shown below.
++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"}}
--// Decode an uplink message from a buffer
--// payload - array of bytes
--// metadata - key/value object
++// Encode downlink data from incoming Rule Engine message
--/** Decoder **/
++// 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
--// decode payload to string
--var payloadStr = decodeToString(payload);
++/** Encoder **/
--// decode payload to JSON
--var data = decodeToJson(payload);
++var 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';
++// Process data from incoming message and metadata
--// Result object with device/asset attributes/telemetry data
++data.tempFreq = msg.temperatureUploadFrequency;
++data.humFreq = msg.humidityUploadFrequency;
++
++data.devSerialNumber = metadata['ss_serialNumber'];
++
++// Result object with encoded downlink payload
  var result = {
--// 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: data.temperature,
--       humidity: data.humidity,
--       rawData: payloadStr
--   }
--};
--/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
++    // 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;
  {{/code}}
--Once you modify the decoder function, click on the **Add** button.
++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 Uplink converter **NB/CB is listed on the **Data Converters** page.
++You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
--[[image:data-converter-list-showing-uplink-dc.png]]
++[[image:data-converters-list.png]]
--= 5. Add Integration =
++= 4. Add Integration =
++
  In the left navigation, click **Integrations center**, and then click **Integrations**.
@@ -320,6 +320,7 @@
  Click **Next** button.
++
  [[image:add-integration-basic-settings.png||height="511" width="500"]]
@@ -331,31 +331,31 @@
  Click **Next** button.
++
  [[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
  **Downlink data converter:**
--Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
++* Click on the **Select existing** button.
++* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
--* Click on the **Skip **button in the Downlink data converter section.
++Click **Next** button.
--Click **Skip** button.
--[[image:integration-dl-skip.png||height="511" width="500"]]
++[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
--
  **Connection:**
--* **Host**: Host URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
++* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
  * **Port**: 8883
--* **Credentials type**: Basic
++* **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)
--* **Enable SSL**: YES
--* **Topic: device/a** (The topic can be anything; you can even use just the device name.)
++* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
  * **QoS:** 0-At most once
  [[image:add-integration-connection.png||height="511" width="500"]]
@@ -388,91 +388,93 @@
  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
++
  [[image:new-integration-pending.png]]
--= 6. Verifying the receipt of data from virtual devices =
++= 5. Verifying the receipt of data from virtual devices =
--== 6.1 How does it work? ==
++== 5.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 (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
++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.
--(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
++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.
--{{code language="none"}}
--{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
--{{/code}}
--Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
++**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.**
--== 5.2 Sending messages ==
++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
--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.
++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"}}
--mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":30, "humidity":80, "pressure":1005}'
++{"temperature":10.4, "humidity":85}
  {{/code}}
--If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
++== 5.2 Sending messages ==
--[[image:integration-active.png]]
++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.
++{{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}'
++{{/code}}
++If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
--== 6.3 Viewing messages ==
++[[image:integration-active.png]]
--Go back to the **Integrations** page.
--Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
++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**.
--Click on the **Edit** button (//**pen icon**//).
--Click on the **Disabled** button in the upper-right corner.
++[[image:device-provision-1.png]]
--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.
++Click on the device S31B-NB on the devices list to see its details.
--Then click on the **Apply changes** (//**tick icon**//) button.
++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.
--[[image:Screenshot 2025-03-18 at 09.23.10.png]]
++[[image:telemetry-1.png]]
--Now go to the **Events** tab.
--Select the Event type as **Debug** from the dropdown list.
++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//.
--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:telemetry-2.png]]
--[[image:Screenshot 2025-03-26 at 19.49.31.png]]
++Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
++{{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}}
--Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
++Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
--[[image:Screenshot 2025-03-26 at 19.47.52.png]]
++[[image:device-provision-2.png]]
++= 6. Creating a Dashboard =
--
--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.
@@ -479,11 +479,6 @@
  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.
@@ -540,11 +540,11 @@
  {{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":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":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": 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":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": 19, "humidity":80}'
++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}'
  {{/code}}
@@ -554,10 +554,10 @@
  [[image:timeseries-4.png||height="316" width="700"]]
--= 8. Configure NB-IoT Sensor =
++= 7. 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 **TS01-NB**.
++Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-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.
@@ -565,8 +565,8 @@
  **AT Commands**
  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
--* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
--* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
++* **AT+SUBTOPIC=<MQTT topic>**
++* **AT+PUBTOPIC=<MQTT topic>**
  * **AT+CLIENT=null**
  * **AT+UNAME=<MQTT Username>**
  * **AT+PWD=<MQTT Password>**
@@ -573,16 +573,3 @@
  * **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]]
--
--
--

Screenshot 2025-03-16 at 18.38.59.png

Author

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

Size

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

Content

Screenshot 2025-03-16 at 18.39.12.png

Author

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

Size

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

Content

Screenshot 2025-03-18 at 09.23.10.png

Author

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

Size

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

Content

Screenshot 2025-03-26 at 18.15.08.png

Author

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

Size

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

Content

Screenshot 2025-03-26 at 19.47.52.png

Author

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

Size

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

Content

Screenshot 2025-03-26 at 19.49.31.png

Author

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

Size

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

Content

add-integartion-connetcion.png

Author

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

Size

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

Content

add-integration-basic-settings.png

Size

@@ -1,1 +1,1 @@
--123.8 KB
++122.5 KB

Content

add-integration-connection.png

Size

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

Content

add-integration-ul-data-converter.png

Author

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

Size

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

Content

image-4.png

Author

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

Size

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

Content

integration-dl-skip.png

Author

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

Size

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

Content

mqtt-uplink.png

Author

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

Size

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

Content

new-device.png

Author

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

Size

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

Content

ul-data-converter-added.png

Author

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

Size

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

Content

ul-data-converter-device-a.png

Author

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

Size

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

Content

Changes for page ThingsBoard

Summary

Details

Applications

Navigation