Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 170.1
edited by Dilisi S
on 2025/03/19 21:00
Change comment: There is no comment for this version
To version 91.1
edited by Dilisi S
on 2025/03/08 03:54
Change comment: Uploaded new attachment "add-downlink-data-converter.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -17,153 +17,76 @@
17 17  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**.
18 18  
19 19  
20 -= 2. Prerequisites =
20 += 2. Add New Device =
21 21  
22 -To complete this tutorial, you need to have the following:
23 23  
24 -* ThingsBoard cloud account
25 -* MQTT Broker (public or private) such as,
26 -** **[[HiveMQ Cloud>>https://www.hivemq.com]] - You can create a free account to try it or subscribe for a paid account. - We use HiveMQ Cloud as the MQTT broker to build example in this tutorial.**
27 -** [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] - The public MQTT server is only used for MOTT learning and testing, and should not be used in the production environment.
28 -** [[lns1.thingseye.io>>http://lns1.thingseye.io/]] - This is Dragino's MQTT broker, which requires a CA certificate to use.
23 +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.
29 29  
30 -== 2.1 ThingsBoard Cloud ==
25 +In the left navigation, click **Entities** and then click **Devices**.
31 31  
27 +[[image:device-list-empty.png]]
32 32  
33 -Go to [[https:~~/~~/thingsboard.io/>>https://thingsboard.io/]]
34 34  
35 -Click on the **Try it now**.
30 +On the **Devices **page, click on the ‘**+**’ button, and then click on the **Add new device **from the dropdown menu.
36 36  
32 +[[image:ThingsBoard-add-new-device.png||height="279" width="500"]]
37 37  
38 -[[image:thingsboard-1.png]]
39 39  
35 +The **Add new device** window appears. Name the device, for example '**Virtual NB/CB device**'.
40 40  
41 -Select either the **North America** or **Europe** region. Here, we use the Europe region.
37 +Click on the **Next: Credentials** button.
42 42  
43 -[[image:thingsboard-2.png]]
39 +[[image:new-device-device-details.png||height="529" width="500"]]
44 44  
45 45  
46 -You can sign up with your **Google**, **GitHub**, **Facebook**, or **Apple** account. If not you can create an account with providing your **name**, **email address** and a **password**.
42 +Click the **Access token** button if it is not selected by default.
47 47  
48 -Click on the **Sign up** button.
44 +Copy the **Access token** to a text editor, as you will need it in the section **'Sending data from an MQTT client'**.
49 49  
50 -[[image:thingsboard-3.png||height="651" width="500"]]
46 +Click on the **Add** button.
51 51  
48 +[[image:new-device-access-token.png||height="528" width="500"]]
52 52  
53 -You will be navigated to the following page.
54 54  
55 -[[image:thingsboard-5.png||height="109" width="500"]]
51 +Click on the **MQTT** button.
56 56  
53 +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.
57 57  
58 -simultaneously, you will receive an email to confirm your email address. Click on the **Activate Your Account** button.
55 +Copy the MQTT pub command in the '**Execute the following command**' section.
59 59  
57 +{{code language="none"}}
58 +mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/me/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:25}"
59 +{{/code}}
60 60  
61 -[[image:thingsboard-4.png||height="249" width="500"]]
61 +Note that the **State** is still shown as **'Inactive'** in the **Latest telemetry** section.
62 62  
63 +[[image:new-device-check-connectivity.png||height="522" width="500"]]
63 63  
64 -Now losing to the account using your credentials:
65 65  
66 +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 66  
67 -[[image:thingsboard-6.png||height="244" width="500"]]
68 68  
69 +[[image:mqtt-command-1.png||height="228" width="700"]]
69 69  
70 -== 2.2 HiveMQ Cloud ==
71 71  
72 -=== 2.2.1 HiveMQ Cloud ===
72 +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.
73 73  
74 74  
75 -Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
75 +[[image:new-device-telemetry-test.png||height="520" width="500"]]
76 76  
77 -Click on the **Start Free** button.
78 78  
79 -[[image:hivwmq-1.png]]
78 +Send the same command again, only changing the **temperature** value, to see how the **Latest telemetry** section updates its data.
80 80  
80 +Once you are done experimenting with this, close the window by clicking the **Close** button.
81 81  
82 -Click on the **Sign Up FREE Now** button in the **HIVEMQ CLOUD** section.
83 83  
84 -[[image:hivemq-2.png]]
83 +[[image:mqtt-command-2.png||height="227" width="700"]]
85 85  
86 86  
87 -Click on the **Sign Up** button.
88 88  
89 -You can sign up with HiveMQ using your **GitHub**, **Google**, or **LinkedIn** account.
87 +[[image:virtual-device-active.png]]
90 90  
91 -If not, provide your **email address** and a **password** to create an account by clicking on the **Sign Up** button.
92 92  
93 -
94 -[[image:hivemq-3.png]]
95 -
96 -
97 -You will receive an email to verify your email address. Click on the **Confirm my account** button.
98 -
99 -
100 -[[image:hivemq-4.jpg||height="889" width="400"]]
101 -
102 -
103 -You will be redirected to a page asking you to complete your profile. Once done, click the **Continue** button.
104 -
105 -
106 -[[image:hivemq-5.png||height="655" width="700"]]
107 -
108 -
109 -Select the CloudMQ Cloud plan you need. For testing purposes, select the **Serverless FREE** plan by clicking on the **Create Serverless Cluster** button.
110 -
111 -
112 -[[image:hivemq-6.png]]
113 -
114 -
115 -You will be navigated to the **Your Clusters** page. Click on the **Manage Cluster** button.
116 -
117 -[[image:hivemq-7.png]]
118 -
119 -
120 -In your cluster page, you can find some useful parameters you need to create a MQTT connection.
121 -
122 -**URL**: This is the host name. Click on the copy button to copy it.
123 -
124 -**Port**: 8883
125 -
126 -
127 -Click on the **Getting Started** tab to setup the username and the password as the connection credentials.
128 -
129 -
130 -[[image:hivemq-8.png]]
131 -
132 -
133 -In the '**Create Connection Credentials**' section, provide a **username** and **password**, then click the **Add** button.
134 -
135 -
136 -[[image:hivemq-9.png]]
137 -
138 -
139 -
140 -If everything is successful, you will see the following message.
141 -
142 -
143 -[[image:hivemq-10.png||height="206" width="500"]]
144 -
145 -
146 -You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
147 -
148 -
149 -=== 2.2.2 emqx ===
150 -
151 -
152 -The [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] public MQTT server is only used for MOTT learning and testing, and should not be used in the production environment.
153 -
154 -
155 -[[image:emqx.png||height="420" width="500"]]
156 -
157 -
158 -=== 2.2.3 Ins1.thingseye.io ===
159 -
160 -[[lns1.thingseye.io>>http://lns1.thingseye.io/]] is the Dragino's MQTT broker, which requires a CA certificate file, Certificate file, and the Private key file to use.
161 -
162 -If customers need to use this MQTT connection with ThingsBoard, they need to contact the TE team to obtain three license files.
163 -
164 -[[image:ins1.png||height="310" width="500"]]
165 -
166 -
167 167  = 3. Data Converters =
168 168  
169 169  
... ... @@ -175,24 +175,18 @@
175 175  
176 176  In the left navigation, click **Integrations center**, and then click **Data converters**.
177 177  
101 +[[image:data-converter-list-page.png]]
178 178  
179 -[[image:data-converters-list-empty.png]]
180 180  
104 +On the **Data converters** page, click on the ‘+’ button, and then click on the **Create new converter** from the dropdown menu.
181 181  
182 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
106 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
183 183  
184 184  
185 -
186 -[[image:create-new-converter-menu.png||height="259" width="500"]]
187 -
188 -
189 189  The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
190 190  
191 -Click on the **JavaScript** button.
111 +Click on the **JavaScript** button. Now copy and paste the following JavaScript to the **Decoder function** section. This decoder function is valid for both NB and CB series devices.
192 192  
193 -Delete the default decoder function in the code editor. Now copy and paste the following decoder function written in **JavaScript** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
194 -
195 -
196 196  {{code language="JavaScript"}}
197 197  //Version: 0.1
198 198  // decode payload to string
... ... @@ -313,38 +313,83 @@
313 313  }
314 314  
315 315  return result;
233 +
316 316  {{/code}}
317 317  
318 318  
319 319  Click on the **Add** button.
320 320  
239 +[[image:uplink-data-converter.png||height="529" width="500"]]
321 321  
322 -[[image:mqtt-uplink.png||width="500"]]
323 323  
242 +You should see that the newly added **uplink data converter** is listed on the **Data Converters** page.
324 324  
244 +[[image:data-converter-list-showing-uplink-dc.png]]
325 325  
326 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
327 327  
247 +== 3.2 Downlink ==
328 328  
329 -[[image:data-converter-list-showing-uplink-dc.png]]
330 330  
250 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
331 331  
252 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
332 332  
333 333  
255 +The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
334 334  
257 +Click on the **JavaScript** button. Now copy and paste the following JavaScript to the **Encoder function **section. This encoder function is valid for both NB and CB series devices.
335 335  
336 -= 4. Add Integration =
337 337  
260 +{{code language="JavaScript"}}
261 +function hexToBase64(hexString) {
262 + // 将16进制字符串两个字符转换为一个字节
263 + var bytes = hexString.match(/.{2}/g);
264 + // 对每个字节进行解析，并转换为对应的字符
265 + var binaryString = bytes.map(function(byte) {
266 + return String.fromCharCode(parseInt(byte, 16));
267 + }).join('');
268 +
269 + // 使用btoa进行base64编码
270 + return btoa(binaryString);
271 +}
338 338  
339 -In the left navigation, click **Integrations center**, and then click **Integrations**.
273 +// Result object with encoded downlink payload
274 +var result = {
275 + // downlink data content type: JSON, TEXT or BINARY (base64 format)
276 + contentType: "BINARY",
340 340  
278 + // downlink data
279 + data:hexToBase64(metadata.shared_value)
341 341  
342 -[[image:integrations-list-empty.png]]
281 + // Optional metadata object presented in key/value format
282 + //metadata: {}
343 343  
284 +};
344 344  
286 +return result;
287 +{{/code}}
288 +
289 +
290 +Click on the **Add** button.
291 +
292 +[[image:downlink-data-converter.png||height="530" width="500"]]
293 +
294 +
295 +You should see that the newly added **downlink data converter** is listed on the **Data Converters** page.
296 +
297 +[[image:data-converter-list.png]]
298 +
299 +
300 += 4. Add Integration =
301 +
302 +
303 +In the left navigation, click **Integrations center**, and then click **Integrations**.
304 +
345 345  On the **Integrations** page, click on the '**+**' button.
346 346  
307 +[[image:data-converter-list-page.png]]
347 347  
309 +
348 348  The **Add integration** window appears.
349 349  
350 350  In the **Add integration** window, configure the following settings:
... ... @@ -354,12 +354,9 @@
354 354  
355 355  * **Integration type**: MQTT
356 356  * **Name**: MQTT integration NB/CB
357 -* **Enable integration**: YES
358 -* **Allows create devices or assets**: YES
359 359  
360 360  Click **Next** button.
361 361  
362 -
363 363  [[image:add-integration-basic-settings.png||height="511" width="500"]]
364 364  
365 365  
... ... @@ -370,10 +370,9 @@
370 370  
371 371  Click **Next** button.
372 372  
332 +[[image:add-integration-uplink-data-converter.png||width="500"]]
373 373  
374 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
375 375  
376 -
377 377  **Downlink data converter:**
378 378  
379 379  * Click on the **Select existing** button.
... ... @@ -381,242 +381,47 @@
381 381  
382 382  Click **Next** button.
383 383  
342 +[[image:add-integration-downlink-data-converter.png||height="510" width="500"]]
384 384  
385 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
386 386  
387 -
388 388  **Connection:**
389 389  
390 -* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
391 -* **Port**: 8883
347 +* **Host**: mqtt.eu.thingsboard.cloud (This is the host name you copied from the device - See section xxxxx for more information)
348 +* **Port**: 1883 (This is the port number you copied from the device - See section xxxxx for more information)
392 392  * **Credentials**: Basic
393 -* **Enable SSL**: YES
394 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
395 -* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
396 -* **Topic: v1/devices/+/telemetry** (the + replaces any 'device name' will create a device in the Entities -> Devices)
397 -* **QoS:** 0-At most once
350 +* **Username**: Access token (This is the access token you copied from the device)
351 +* **Password** - Leave it as blank
352 +* **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')
353 +* **QoS** - 0-At most once
398 398  
399 -[[image:add-integration-connection.png||height="511" width="500"]]
400 -
401 -
402 -Click on the **Advanced settings** button.
403 -
404 -* **Clean session:** YES
405 -* **Retained**: YES
406 -
407 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
408 -
409 -
410 410  Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
411 411  
357 +[[image:add-integration-connection.png||width="500"]]
412 412  
413 -[[image:check-connection.png||height="83" width="300"]]
414 414  
360 +If the connection is successful, you will see the **Connected** message.
415 415  
416 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
362 +Click on the **Add** button.
417 417  
364 +[[image:add-connection-success.png||height="511" width="500"]]
418 418  
419 -[[image:connection-success.png||height="511" width="500"]]
420 420  
421 -
422 -Click on the **Add** button.
423 -
424 424  You should see that the newly added integration is listed on the **Integrations** page.
425 425  
426 426  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
427 427  
371 +[[image:integrations-list-added-pending.png]]
428 428  
429 429  
430 -[[image:new-integration-pending.png]]
374 += 5. Verifying the receipt of data from the device =
431 431  
432 432  
433 -= 5. Verifying the receipt of data from virtual devices =
377 +On the terminal, issue the following MQTT command which simulates the device S31B-NB.
434 434  
435 -
436 -== 5.1 How does it work? ==
437 -
438 -
439 -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.
440 -
441 -The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
442 -
443 -(% 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.
444 -
445 445  {{code language="none"}}
446 -{"IMEI": "S31B-NB", "temperature": 27, ......}
380 +mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}"
447 447  {{/code}}
448 448  
449 -Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
383 +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.
450 450  
451 -
452 -== 5.2 Sending messages ==
453 -
454 -
455 -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.
456 -
457 -{{code language="none"}}
458 -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}'
459 -{{/code}}
460 -
461 -If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
462 -
463 -
464 -[[image:integration-active.png]]
465 -
466 -
467 -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**.
468 -
469 -
470 -[[image:new-device.png]]
471 -
472 -
473 -== 5.3 Viewing messages ==
474 -
475 -
476 -Go back to the **Integrations** page.
477 -
478 -Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
479 -
480 -Click on the **Edit** button (//**pen icon**//).
481 -
482 -Click on the **Disabled** button in the upper-right corner.
483 -
484 -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.
485 -
486 -Click on the **Apply** button.
487 -
488 -Then click on the **Apply changes** (//**tick icon**//) button.
489 -
490 -
491 -[[image:Screenshot 2025-03-18 at 09.23.10.png]]
492 -
493 -
494 -Now go to the **Events** tab.
495 -
496 -Select the Event type as **Debug** from the dropdown list.
497 -
498 -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.
499 -
500 -
501 -[[image:Screenshot 2025-03-16 at 18.38.59.png]]
502 -
503 -
504 -Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
505 -
506 -
507 -[[image:Screenshot 2025-03-16 at 18.39.12.png]]
508 -
509 -
510 -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.
511 -
512 -
513 -= 6. Creating a Dashboard =
514 -
515 -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.
516 -
517 -
518 -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.
519 -
520 -
521 -First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
522 -
523 -{{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}}
524 524  
525 -
526 -In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
527 -
528 -
529 -[[image:dashboard-1.png]]
530 -
531 -
532 -In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
533 -
534 -Click on the **Add** button.
535 -
536 -
537 -[[image:dashboard-2.png||height="526" width="500"]]
538 -
539 -
540 -Click on the **Add widget / Add new widget** button.
541 -
542 -
543 -[[image:dashboard-3.png]]
544 -
545 -
546 -In the **Select widgets bundle** window, click **Charts**.
547 -
548 -
549 -[[image:dashboard-4.png||height="537" width="700"]]
550 -
551 -
552 -
553 -In the **Charts: select widget** window, click **Time series chart**.
554 -
555 -
556 -[[image:dashboard-5.png||height="525" width="700"]]
557 -
558 -
559 -Configure the **Time series chart** widget as follows:
560 -
561 -* **Datasource** - select S31B-NB device you provisioned.
562 -* **Series**:
563 -** **temperature** - you can see this key by default.
564 -** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
565 -* Click on the **Add** button.
566 -
567 -[[image:timeseries-1.png||height="491" width="700"]]
568 -
569 -
570 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
571 -
572 -Click the **Save** button to add the widget to the dashboard.
573 -
574 -
575 -[[image:timeseries-3.png||height="347" width="700"]]
576 -
577 -
578 -Now send the following MQTT messages from the terminal to simulate the data.
579 -
580 -
581 -{{code language="none"}}
582 -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}'
583 -
584 -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}'
585 -
586 -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}'
587 -
588 -{{/code}}
589 -
590 -The chart will update with the values in realtime, as shown in the below image.
591 -
592 -
593 -[[image:timeseries-4.png||height="316" width="700"]]
594 -
595 -
596 -= 7. Configure NB-IoT Sensor =
597 -
598 -
599 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
600 -
601 -First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
602 -
603 -
604 -**AT Commands**
605 -
606 -* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
607 -* **AT+SUBTOPIC=<MQTT subscribe topic> **
608 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
609 -* **AT+CLIENT=null**
610 -* **AT+UNAME=<MQTT Username>**
611 -* **AT+PWD=<MQTT Password>**
612 -* **AT+SERVADDR=<Broker address, Port>**
613 -
614 -Test your uplink by pressing the ACT button for 1 second.
615 -
616 -
617 -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**.
618 -
619 -[[image:image-4.png]]
620 -
621 -
622 -
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 -277.0 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
add-integration-basic-settings.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -122.5 KB
Content
add-integration-connection-advanced-settings.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -155.2 KB
Content
add-integration-connection.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -153.2 KB
Content
add-integration-downlink-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -123.0 KB
Content
add-integration-uplink-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -120.7 KB
Content
check-connection.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -14.7 KB
Content
connection-success.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -90.0 KB
Content
dashboard-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -271.1 KB
Content
dashboard-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -112.2 KB
Content
dashboard-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -141.3 KB
Content
dashboard-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -803.7 KB
Content
dashboard-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -476.1 KB
Content
data-converter-list-showing-uplink-dc.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -194.9 KB
Content
data-converters-list.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -212.2 KB
Content
device-provision-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -265.7 KB
Content
device-provision-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -213.9 KB
Content
emqx.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -39.1 KB
Content
hivemq-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -82.7 KB
Content
hivemq-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -300.7 KB
Content
hivemq-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -535.2 KB
Content
hivemq-4.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -309.8 KB
Content
hivemq-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -115.0 KB
Content
hivemq-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -321.0 KB
Content
hivemq-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -203.5 KB
Content
hivemq-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -268.7 KB
Content
hivemq-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -303.7 KB
Content
hivwmq-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -380.3 KB
Content
image-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -96.0 KB
Content
ins1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -28.8 KB
Content
integration-active.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -64.2 KB
Content
integrations-list-empty.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -264.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
new-integration-pending.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -199.7 KB
Content
telemetry-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -191.9 KB
Content
telemetry-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -185.1 KB
Content
thingsboard-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -1.9 MB
Content
thingsboard-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -901.1 KB
Content
thingsboard-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -146.3 KB
Content
thingsboard-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -122.1 KB
Content
thingsboard-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -106.7 KB
Content
thingsboard-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -119.3 KB
Content
timeseries-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -179.1 KB
Content
timeseries-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -174.2 KB
Content
timeseries-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -159.0 KB
Content