Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 64.2
edited by Xiaoling
on 2025/03/07 11:46
Change comment: There is no comment for this version
To version 57.1
edited by Dilisi S
on 2025/03/06 04:08
Change comment: Uploaded new attachment "mqtt-command-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.pradeeka
Content
... ... @@ -6,24 +6,21 @@
6 6  Draft Document
7 7  {{/warning}}
8 8  
9 -= 1. Introduction =
9 += Introduction =
10 10  
11 -
12 12  This document guides you on integrating Dragino **-NB** and **-CB** series devices data with ThingsBoard. For this guide, we use ThingsBoard Cloud, which is one of the ThingsBoard versions that allows you to try it for free.
13 13  
14 14  The **NB series** devices end with the suffix **-NB**, and the **CB series** devices end with the suffix **-CB**. For example, **S31B-NB** is an **NB device**, and **S31-CB** is a **CB device**.
15 15  
16 16  
17 -= 2. Add New Device =
16 += Add New Device =
18 18  
19 -
20 -First, we will add a device to simulate data using MQTT. This device does not represent a real physical device but serves as a common virtual device for all Dragino NB/CB devices.
21 -
22 22  In the left navigation, click **Entities** and then click **Devices**.
23 23  
24 -[[image:device-list-empty.png]]
25 25  
21 +[[image:ThingsBoard-Device.png]]
26 26  
23 +
27 27  On the **Devices **page, click on the ‘**+**’ button, and then click on the **Add new device **from the dropdown menu.
28 28  
29 29  
... ... @@ -30,78 +30,23 @@
30 30  [[image:ThingsBoard-add-new-device.png||height="279" width="500"]]
31 31  
32 32  
33 -The **Add new device** window appears. Name the device, for example '**Virtual NB/CB device**'.
34 34  
35 -Click on the **Next: Credentials** button.
31 += Data Converters =
36 36  
37 -
38 -[[image:new-device-device-details.png||height="529" width="500"]]
39 -
40 -
41 -Click the **Access token** button if it is not selected by default.
42 -
43 -Copy the **Access token** to a text editor, as you will need it in the section **'Sending data from an MQTT client'**.
44 -
45 -Click on the **Add** button.
46 -
47 -[[image:new-device-access-token.png||height="528" width="500"]]
48 -
49 -
50 -Click on the **MQTT** button.
51 -
52 -Then, select the operating system you are going to use with the **Mosquitto MQTT Broker**. This example shows sending a command from a computer running **MacOS**. First, install the necessary client tools on your computer.
53 -
54 -Copy the MQTT pub command in the '**Execute the following command**' section.
55 -
56 -{{code language="none"}}
57 -mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/me/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:25}"
58 -{{/code}}
59 -
60 -Note that the **State** is still shown as **'Inactive'** in the **Latest telemetry** section.
61 -
62 -[[image:new-device-check-connectivity.png||height="522" width="500"]]
63 -
64 -
65 -On the terminal, enter the command you copied. This command sends the MQTT payload **{temperature:25}** as telemetry data from a virtual device named **'me'**. Of course, you can replace **'me'** with a device name or use the wildcard character **'+'** to match any device name.
66 -
67 -
68 -[[image:mqtt-command-1.png||height="228" width="700"]]
69 -
70 -
71 -If the command is successful, you can see the telemetry data you sent under the **Latest telemetry** section. Note that the **State** is now **'Active'** in the **Latest telemetry** section.
72 -
73 -
74 -[[image:new-device-telemetry-test.png||height="520" width="500"]]
75 -
76 -
77 -Send the same command again, only changing the **temperature** value, to see how the **Latest telemetry** section updates its data.
78 -
79 -Once you are done experimenting with this, close the window by clicking the **Close** button.
80 -
81 -
82 -[[image:mqtt-command-2.png||height="227" width="700"]]
83 -
84 -
85 -
86 -[[image:virtual-device-active.png]]
87 -
88 -
89 -= 3. Data Converters =
90 -
91 -
92 92  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.
93 93  
94 94  
95 -== 3.1 Uplink ==
36 +== Uplink ==
96 96  
97 -
98 98  In the left navigation, click **Integrations center**, and then click **Data converters**.
99 99  
40 +
100 100  [[image:data-converter-list-page.png]]
101 101  
102 102  
103 103  On the **Data converters** page, click on the ‘+’ button, and then click on the **Create new converter** from the dropdown menu.
104 104  
46 +
105 105  [[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
106 106  
107 107  
... ... @@ -232,22 +232,24 @@
232 232  
233 233  {{/code}}
234 234  
235 -
236 236  Click on the **Add** button.
237 237  
179 +
238 238  [[image:uplink-data-converter.png||height="529" width="500"]]
239 239  
240 240  
183 +
241 241  You should see that the newly added **uplink data converter** is listed on the **Data Converters** page.
242 242  
186 +
243 243  [[image:data-converter-list-showing-uplink-dc.png]]
244 244  
245 245  
246 -== 3.2 Downlink ==
190 +== Downlink ==
247 247  
248 -
249 249  On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
250 250  
194 +
251 251  [[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
252 252  
253 253  
... ... @@ -288,21 +288,24 @@
288 288  
289 289  Click on the **Add** button.
290 290  
235 +
291 291  [[image:downlink-data-converter.png||height="530" width="500"]]
292 292  
293 293  
239 +
294 294  You should see that the newly added **downlink data converter** is listed on the **Data Converters** page.
295 295  
242 +
296 296  [[image:data-converter-list.png]]
297 297  
298 298  
299 -= 4. Add Integration =
246 += Add Integration =
300 300  
301 -
302 302  In the left navigation, click **Integrations center**, and then click **Integrations**.
303 303  
304 304  On the **Integrations** page, click on the '**+**' button.
305 305  
252 +
306 306  [[image:data-converter-list-page.png]]
307 307  
308 308  
... ... @@ -318,9 +318,11 @@
318 318  
319 319  Click **Next** button.
320 320  
268 +
321 321  [[image:add-integration-basic-settings.png||height="511" width="500"]]
322 322  
323 323  
272 +
324 324  **Uplink data converter:**
325 325  
326 326  * Click on the **Select existing** button.
... ... @@ -328,9 +328,11 @@
328 328  
329 329  Click **Next** button.
330 330  
280 +
331 331  [[image:add-integration-uplink-data-converter.png||width="500"]]
332 332  
333 333  
284 +
334 334  **Downlink data converter:**
335 335  
336 336  * Click on the **Select existing** button.
... ... @@ -338,9 +338,11 @@
338 338  
339 339  Click **Next** button.
340 340  
292 +
341 341  [[image:add-integration-downlink-data-converter.png||height="510" width="500"]]
342 342  
343 343  
296 +
344 344  **Connection:**
345 345  
346 346  * **Host**: mqtt.eu.thingsboard.cloud (This is the host name you copied from the device - See section xxxxx for more information)
... ... @@ -348,11 +348,12 @@
348 348  * **Credentials**: Basic
349 349  * **Username**: Access token (This is the access token you copied from the device)
350 350  * **Password** - Leave it as blank
351 -* **Topic** - v1/devices/+/telemetry (sightly modify the topic 'v1/devices/me/telemetry' you copied from the device to enable receiving data from any 'device name')
304 +* **Topic** - v1/devices/+/telemetry (sightly modify the topic 'v1/devices/me/telemetry' you copied for the device to enable receiving data from any 'device name')
352 352  * **QoS** - 0-At most once
353 353  
354 354  Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
355 355  
309 +
356 356  [[image:add-integration-connection.png||width="500"]]
357 357  
358 358  
... ... @@ -360,25 +360,22 @@
360 360  
361 361  Click on the **Add** button.
362 362  
317 +
363 363  [[image:add-connection-success.png||height="511" width="500"]]
364 364  
365 365  
366 -You should see that the newly added integration is listed on the **Integrations** page.
367 367  
368 -Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
369 369  
370 -[[image:integrations-list-added-pending.png]]
371 371  
372 372  
373 -= 5. Verifying the receipt of data from the device =
374 374  
326 +You should see that the newly added integration is listed on the **Integrations** page.
375 375  
376 -On the terminal, issue the following MQTT command which simulates the device S31B-NB.
328 +Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
377 377  
378 -{{code language="none"}}
379 -mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}"
380 -{{/code}}
330 +[[image:Integrations-list.png]]
381 381  
382 -If the integration was performed without errors, after the transmission of the first telemetry, a new device with the name “S31B-NB” will appear in the Devices → All. Also, you can verify the input and output data, respectively, before and after conversion in Data converters → UDP Uplink Converter NB/CB → Events.
383 383  
384 -
333 += Verifying the receipt of data from the device =
334 +
335 +Connect **S31B-NB** to transfer information. If the integration was performed without errors, after the transmission of the first telemetry, a new device with the name “xxxxx” will appear in the Devices → All. Also, you can verify the input and output data, respectively, before and after conversion in Data converters → UDP Uplink Converter NB/CB → Events.
mqtt-command-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -202.8 KB
Content
new-device-telemetry-test.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -202.8 KB
Content
virtual-device-active.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -202.8 KB
Content