Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 176.1
edited by Dilisi S
on 2025/03/26 20:27
Change comment: Mar 26 edits - part 1
To version 20.1
edited by Dilisi S
on 2025/03/04 04:18
Change comment: Uploaded new attachment "Data-converter-list-uplink-only.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -6,216 +6,49 @@
6 6  Draft Document
7 7  {{/warning}}
8 8  
9 += Introduction =
9 9  
11 +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.
10 10  
13 +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.
11 11  
12 -= 1. Introduction =
13 13  
16 += Add New Device =
14 14  
15 -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.
18 +In the left navigation, click **Entities** and then click **Devices**.
16 16  
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  
21 +[[image:ThingsBoard-Device.png]]
19 19  
20 -= 2. Prerequisites =
21 21  
22 -To complete this tutorial, you need to have the following:
24 +On the ‘**Devices**’ page, click on the ‘**+**’ button, and then click on the ‘**Add new device**’ from the dropdown menu.
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.
29 29  
30 -== 2.1 ThingsBoard Cloud ==
27 +[[image:ThingsBoard-add-new-device.png||height="279" width="500"]]
31 31  
32 32  
33 -Go to [[https:~~/~~/thingsboard.io/>>https://thingsboard.io/]]
34 34  
35 -Click on the **Try it now**.
31 += Data Converters =
36 36  
37 37  
38 -[[image:thingsboard-1.png]]
34 +== Uplink ==
39 39  
36 +In the left navigation, click ‘Integrations center’, and then click ‘Data converters’.
40 40  
41 -Select either the **North America** or **Europe** region. Here, we use the Europe region.
42 42  
43 -[[image:thingsboard-2.png]]
39 +[[image:ThingsBoard-Data-Converters.png]]
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 +On the ‘Data converters’ page, click on the ‘+’ button, and then click on the ‘Create new converter’ from the dropdown menu.
47 47  
48 -Click on the **Sign up** button.
49 49  
50 -[[image:thingsboard-3.png||height="651" width="500"]]
45 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
51 51  
52 52  
53 -You will be navigated to the following page.
48 +The ‘Add data converter’ window will appear. Name it ‘**UDP Uplink Converter NB/CB**’ and select the Type as ‘Uplink’.
54 54  
55 -[[image:thingsboard-5.png||height="109" width="500"]]
50 +Click on the ‘JavaScript’ button. Now copy and paste the following script to the ‘Decoder function’ section:
56 56  
57 -
58 -simultaneously, you will receive an email to confirm your email address. Click on the **Activate Your Account** button.
59 -
60 -
61 -[[image:thingsboard-4.png||height="249" width="500"]]
62 -
63 -
64 -Now losing to the account using your credentials:
65 -
66 -
67 -[[image:thingsboard-6.png||height="244" width="500"]]
68 -
69 -
70 -== 2.2 HiveMQ Cloud ==
71 -
72 -=== 2.2.1 HiveMQ Cloud ===
73 -
74 -
75 -Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
76 -
77 -Click on the **Start Free** button.
78 -
79 -[[image:hivwmq-1.png]]
80 -
81 -
82 -Click on the **Sign Up FREE Now** button in the **HIVEMQ CLOUD** section.
83 -
84 -[[image:hivemq-2.png]]
85 -
86 -
87 -Click on the **Sign Up** button.
88 -
89 -You can sign up with HiveMQ using your **GitHub**, **Google**, or **LinkedIn** account.
90 -
91 -If not, provide your **email address** and a **password** to create an account by clicking on the **Sign Up** button.
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 -(% class="wikigeneratedid" %)
168 -= 3. Creating Devices =
169 -
170 -
171 -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.
172 -
173 -
174 -In the left navigation, click Entities -> Devices.
175 -
176 -Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
177 -
178 -In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
179 -
180 -Click the **Add** button.
181 -
182 -Skip the **connectivity testing** by clicking the **Close** button.
183 -
184 -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.
185 -
186 -
187 -= 4. Data Converters =
188 -
189 -
190 -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.
191 -
192 -
193 -== 4.1 Uplink ==
194 -
195 -
196 -In the left navigation, click **Integrations center**, and then click **Data converters**.
197 -
198 -
199 -[[image:data-converters-list-empty.png]]
200 -
201 -
202 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
203 -
204 -
205 -
206 -[[image:create-new-converter-menu.png||height="259" width="500"]]
207 -
208 -
209 -The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
210 -
211 -Click on the **JavaScript** button.
212 -
213 -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.
214 -
215 -{{info}}
216 -Please note that the value assigned to the IMEI field in the payload will be used by ThingsBoard to create a device on the platform with the same name.
217 -{{/info}}
218 -
219 219  {{code language="JavaScript"}}
220 220  //Version: 0.1
221 221  // decode payload to string
... ... @@ -336,313 +336,137 @@
336 336  }
337 337  
338 338  return result;
172 +
339 339  {{/code}}
340 340  
175 +Click on the ‘Add’ button.
341 341  
342 -Click on the **Add** button.
343 343  
178 +[[image:ThingsBoard-add-data-converter-uplink.png||width="500"]]
344 344  
345 -[[image:mqtt-uplink.png||width="500"]]
346 346  
181 +The uplink data converter is added to ThingsBoard and appears on the ‘Data Converters’ page
347 347  
348 348  
349 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
184 +== Downlink ==
350 350  
186 +On the ‘Data converters’ page, click on the ‘+’ button, and then click on the ‘Create new converter’ from the dropdown menu.
351 351  
352 -[[image:data-converter-list-showing-uplink-dc.png]]
353 353  
189 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
354 354  
355 -= 5. Add Integration =
356 356  
192 +The ‘**Add data converter**’ window will appear. Name it ‘**UDP Downlink Converter NB/CB**’ and select the Type as ‘**Downlink**’.
357 357  
358 -In the left navigation, click **Integrations center**, and then click **Integrations**.
194 +Click on the ‘**JavaScript**’ button. Now copy and paste the following script to the ‘**Encoder function**’ section:
359 359  
360 360  
361 -[[image:integrations-list-empty.png]]
197 +{{code language="JavaScript"}}
198 +function hexToBase64(hexString) {
199 + // 将16进制字符串两个字符转换为一个字节
200 + var bytes = hexString.match(/.{2}/g);
201 + // 对每个字节进行解析，并转换为对应的字符
202 + var binaryString = bytes.map(function(byte) {
203 + return String.fromCharCode(parseInt(byte, 16));
204 + }).join('');
205 +
206 + // 使用btoa进行base64编码
207 + return btoa(binaryString);
208 +}
362 362  
210 +// Result object with encoded downlink payload
211 +var result = {
212 + // downlink data content type: JSON, TEXT or BINARY (base64 format)
213 + contentType: "BINARY",
363 363  
364 -On the **Integrations** page, click on the '**+**' button.
215 + // downlink data
216 + data:hexToBase64(metadata.shared_value)
365 365  
218 + // Optional metadata object presented in key/value format
219 + //metadata: {}
366 366  
367 -The **Add integration** window appears.
221 +};
368 368  
369 -In the **Add integration** window, configure the following settings:
223 +return result;
224 +{{/code}}
370 370  
371 371  
372 -**Basic settings:**
373 -
374 -* **Integration type**: MQTT
375 -* **Name**: MQTT integration NB/CB
376 -* **Enable integration**: YES
377 -* **Allows create devices or assets**: YES
378 -
379 -Click **Next** button.
380 -
381 -
382 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
383 -
384 -
385 -**Uplink data converter:**
386 -
387 -* Click on the **Select existing** button.
388 -* **Uplink data converter**: Select **MQTT Uplink Converter NB/CB **from the dropdown list.
389 -
390 -Click **Next** button.
391 -
392 -
393 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
394 -
395 -
396 -**Downlink data converter:**
397 -
398 -Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
399 -
400 -* Click on the **Skip **button in the Downlink data converter section.
401 -
402 -Click **Skip** button.
403 -
404 -
405 -[[image:integration-dl-skip.png||height="511" width="500"]]
406 -
407 -
408 -
409 -**Connection:**
410 -
411 -* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
412 -* **Port**: 8883
413 -* **Credentials**: Basic
414 -* **Enable SSL**: YES
415 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
416 -* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
417 -* **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 S31B-NB.)
418 -* **QoS:** 0-At most once
419 -
420 -
421 -[[image:add-integration-connection.png||height="511" width="500"]]
422 -
423 -
424 -Click on the **Advanced settings** button.
425 -
426 -* **Clean session:** YES
427 -* **Retained**: YES
428 -
429 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
430 -
431 -
432 -Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
433 -
434 -
435 -[[image:check-connection.png||height="83" width="300"]]
436 -
437 -
438 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
439 -
440 -
441 -[[image:connection-success.png||height="511" width="500"]]
442 -
443 -
444 444  Click on the **Add** button.
445 445  
446 -You should see that the newly added integration is listed on the **Integrations** page.
447 447  
448 -Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
230 +[[image:ThingsBoard-add-data-converter-downlink.png||height="532" width="500"]]
449 449  
450 450  
451 -[[image:new-integration-pending.png]]
233 += Add Integration =
452 452  
235 +In the left navigation, click ‘Integrations center’, and then click ‘Integrations’.
453 453  
454 -= 6. Verifying the receipt of data from virtual devices =
237 +On the ‘Integrations’ page, click on the “+” button.
455 455  
456 456  
457 -== 6.1 How does it work? ==
240 +[[image:ThingsBoard-add-integration.png]]
458 458  
459 459  
460 -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.
243 +The ‘Add integration’ window appears.
461 461  
462 -The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
245 +In the Add Integration window, configure the following settings:
463 463  
464 -(% 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.
247 +**Basic settings:**
465 465  
466 -{{code language="none"}}
467 -{"IMEI": "S31B-NB", "temperature": 27, ......}
468 -{{/code}}
249 +* **Integration type**: UDP
250 +* **Name**: UDP Integration NB/CB
469 469  
470 -Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
252 +Click **Next** button.
471 471  
472 472  
473 -== 5.2 Sending messages ==
255 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
474 474  
475 475  
476 -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.
258 +**Uplink data converter:**
477 477  
478 -{{code language="none"}}
479 -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}'
480 -{{/code}}
260 +* Click on the ‘**Select existing**’ button.
261 +* Uplink data converter: Select ‘**UDP Uplink Converter NB/CB**’ from the dropdown list.
481 481  
482 -If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
263 +Click **Next** button.
483 483  
484 484  
485 -[[image:integration-active.png]]
266 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
486 486  
487 487  
488 -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**.
269 +**Downlink data converter:**
489 489  
271 +* Click on the ‘**Select existing**’ button.
272 +* Downlink data converter: Select ‘**UDP Downlink Converter NB/CB**’ from the dropdown list.
490 490  
491 -[[image:new-device.png]]
274 +Click **Next** button.
492 492  
493 493  
494 -== 6.3 Viewing messages ==
277 +[[image:add-integration-downlink-data-converter.png||height="512" width="500"]]
495 495  
496 496  
497 -Go back to the **Integrations** page.
280 +**Connection:**
498 498  
499 -Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
282 +**Port**: 11582
500 500  
501 -Click on the **Edit** button (//**pen icon**//).
284 +**Size of the buffer for inbound socket (in KB)**: 64
502 502  
503 -Click on the **Disabled** button in the upper-right corner.
286 +**Cache Size**: 10000000
504 504  
505 -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.
288 +**Cache time to live in minutes**: 1440
506 506  
507 -Click on the **Apply** button.
508 508  
509 -Then click on the **Apply changes** (//**tick icon**//) button.
291 +Copy the two keys, **Integration key** and **Integration secret** into a text editor, as you will need them in the section ‘xxxxx’.
510 510  
511 -
512 -[[image:Screenshot 2025-03-18 at 09.23.10.png]]
513 -
514 -
515 -Now go to the **Events** tab.
516 -
517 -Select the Event type as **Debug** from the dropdown list.
518 -
519 -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.
520 -
521 -
522 -[[image:Screenshot 2025-03-16 at 18.38.59.png]]
523 -
524 -
525 -Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
526 -
527 -
528 -[[image:Screenshot 2025-03-16 at 18.39.12.png]]
529 -
530 -
531 -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.
532 -
533 -
534 -= 7. Creating a Dashboard =
535 -
536 -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.
537 -
538 -
539 -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.
540 -
541 -
542 -First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
543 -
544 -{{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}}
545 -
546 -
547 -In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
548 -
549 -
550 -[[image:dashboard-1.png]]
551 -
552 -
553 -In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
554 -
555 555  Click on the **Add** button.
556 556  
557 557  
558 -[[image:dashboard-2.png||height="526" width="500"]]
296 +[[image:add-integration-connection.png||height="511" width="500"]]
559 559  
560 560  
561 -Click on the **Add widget / Add new widget** button.
562 562  
300 += Verifying the receipt of data from the device =
563 563  
564 -[[image:dashboard-3.png]]
302 +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.
565 565  
566 566  
567 -In the **Select widgets bundle** window, click **Charts**.
568 -
569 -
570 -[[image:dashboard-4.png||height="537" width="700"]]
571 -
572 -
573 -
574 -In the **Charts: select widget** window, click **Time series chart**.
575 -
576 -
577 -[[image:dashboard-5.png||height="525" width="700"]]
578 -
579 -
580 -Configure the **Time series chart** widget as follows:
581 -
582 -* **Datasource** - select S31B-NB device you provisioned.
583 -* **Series**:
584 -** **temperature** - you can see this key by default.
585 -** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
586 -* Click on the **Add** button.
587 -
588 -[[image:timeseries-1.png||height="491" width="700"]]
589 -
590 -
591 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
592 -
593 -Click the **Save** button to add the widget to the dashboard.
594 -
595 -
596 -[[image:timeseries-3.png||height="347" width="700"]]
597 -
598 -
599 -Now send the following MQTT messages from the terminal to simulate the data.
600 -
601 -
602 -{{code language="none"}}
603 -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}'
604 -
605 -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}'
606 -
607 -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}'
608 -
609 -{{/code}}
610 -
611 -The chart will update with the values in realtime, as shown in the below image.
612 -
613 -
614 -[[image:timeseries-4.png||height="316" width="700"]]
615 -
616 -
617 -= 8. Configure NB-IoT Sensor =
618 -
619 -
620 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
621 -
622 -First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
623 -
624 -
625 -**AT Commands**
626 -
627 -* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
628 -* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
629 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
630 -* **AT+CLIENT=null**
631 -* **AT+UNAME=<MQTT Username>**
632 -* **AT+PWD=<MQTT Password>**
633 -* **AT+SERVADDR=<Broker address, Port>**
634 -
635 -Test your uplink by pressing the ACT button for 1 second.
636 636  
637 -
638 -
639 -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**.
640 -
641 -{{info}}
642 -The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
643 -{{/info}}
644 -
645 -[[image:image-4.png]]
646 -
647 -
648 -
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
add-downlink-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -175.2 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
Size
... ... @@ -1,1 +1,1 @@
1 -158.1 KB
1 +124.4 KB
Content
add-uplink-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -174.1 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
create-new-converter-menu.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -31.5 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-empty.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -260.7 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
integration-dl-skip.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -105.5 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
Data-converter-list-uplink-only.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
Data-converter-list.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-Data-Converters.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +100.3 KB
Content
ThingsBoard-Device.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +225.5 KB
Content
ThingsBoard-add-data-converter-downlink.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-add-data-converter-uplink.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-add-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-add-integration.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-add-new-device.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +89.7 KB
Content
ThingsBoard-new-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +100.3 KB
Content