Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 89.1
edited by Dilisi S
on 2025/03/08 03:43
Change comment: Uploaded new attachment "create-new-converter-menu.png", version {1}
To version 157.1
edited by Dilisi S
on 2025/03/17 01:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,76 +17,153 @@
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. Add New Device =
20 += 2. Prerequisites =
21 21  
22 +To complete this tutorial, you need to have the following:
22 22  
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.
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.
24 24  
25 -In the left navigation, click **Entities** and then click **Devices**.
30 +== 2.1 ThingsBoard Cloud ==
26 26  
27 -[[image:device-list-empty.png]]
28 28  
33 +Go to [[https:~~/~~/thingsboard.io/>>https://thingsboard.io/]]
29 29  
30 -On the **Devices **page, click on the ‘**+**’ button, and then click on the **Add new device **from the dropdown menu.
35 +Click on the **Try it now**.
31 31  
32 -[[image:ThingsBoard-add-new-device.png||height="279" width="500"]]
33 33  
38 +[[image:thingsboard-1.png]]
34 34  
35 -The **Add new device** window appears. Name the device, for example '**Virtual NB/CB device**'.
36 36  
37 -Click on the **Next: Credentials** button.
41 +Select either the **North America** or **Europe** region. Here, we use the Europe region.
38 38  
39 -[[image:new-device-device-details.png||height="529" width="500"]]
43 +[[image:thingsboard-2.png]]
40 40  
41 41  
42 -Click the **Access token** button if it is not selected by default.
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**.
43 43  
44 -Copy the **Access token** to a text editor, as you will need it in the section **'Sending data from an MQTT client'**.
48 +Click on the **Sign up** button.
45 45  
46 -Click on the **Add** button.
50 +[[image:thingsboard-3.png||height="651" width="500"]]
47 47  
48 -[[image:new-device-access-token.png||height="528" width="500"]]
49 49  
53 +You will be navigated to the following page.
50 50  
51 -Click on the **MQTT** button.
55 +[[image:thingsboard-5.png||height="109" width="500"]]
52 52  
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.
54 54  
55 -Copy the MQTT pub command in the '**Execute the following command**' section.
58 +simultaneously, you will receive an email to confirm your email address. Click on the **Activate Your Account** button.
56 56  
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 -Note that the **State** is still shown as **'Inactive'** in the **Latest telemetry** section.
61 +[[image:thingsboard-4.png||height="249" width="500"]]
62 62  
63 -[[image:new-device-check-connectivity.png||height="522" width="500"]]
64 64  
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.
67 67  
67 +[[image:thingsboard-6.png||height="244" width="500"]]
68 68  
69 -[[image:mqtt-command-1.png||height="228" width="700"]]
70 70  
70 +== 2.2 HiveMQ Cloud ==
71 71  
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.
72 +=== 2.2.1 HiveMQ Cloud ===
73 73  
74 74  
75 -[[image:new-device-telemetry-test.png||height="520" width="500"]]
75 +Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
76 76  
77 +Click on the **Start Free** button.
77 77  
78 -Send the same command again, only changing the **temperature** value, to see how the **Latest telemetry** section updates its data.
79 +[[image:hivwmq-1.png]]
79 79  
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.
82 82  
83 -[[image:mqtt-command-2.png||height="227" width="700"]]
84 +[[image:hivemq-2.png]]
84 84  
85 85  
87 +Click on the **Sign Up** button.
86 86  
87 -[[image:virtual-device-active.png]]
89 +You can sign up with HiveMQ using your **GitHub**, **Google**, or **LinkedIn** account.
88 88  
91 +If not, provide your **email address** and a **password** to create an account by clicking on the **Sign Up** button.
89 89  
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 +
90 90  = 3. Data Converters =
91 91  
92 92  
... ... @@ -98,18 +98,24 @@
98 98  
99 99  In the left navigation, click **Integrations center**, and then click **Data converters**.
100 100  
101 -[[image:data-converter-list-page.png]]
102 102  
179 +[[image:data-converters-list-empty.png]]
103 103  
104 -On the **Data converters** page, click on the ‘+’ button, and then click on the **Create new converter** from the dropdown menu.
105 105  
106 -[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
182 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
107 107  
108 108  
185 +
186 +[[image:create-new-converter-menu.png||height="259" width="500"]]
187 +
188 +
109 109  The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
110 110  
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.
191 +Click on the **JavaScript** button.
112 112  
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 +
113 113  {{code language="JavaScript"}}
114 114  //Version: 0.1
115 115  // decode payload to string
... ... @@ -230,17 +230,19 @@
230 230  }
231 231  
232 232  return result;
233 -
234 234  {{/code}}
235 235  
236 236  
237 237  Click on the **Add** button.
238 238  
239 -[[image:uplink-data-converter.png||height="529" width="500"]]
240 240  
322 +[[image:mqtt-uplink.png||width="500"]]
241 241  
242 -You should see that the newly added **uplink data converter** is listed on the **Data Converters** page.
243 243  
325 +
326 +You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
327 +
328 +
244 244  [[image:data-converter-list-showing-uplink-dc.png]]
245 245  
246 246  
... ... @@ -249,37 +249,48 @@
249 249  
250 250  On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
251 251  
252 -[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
253 253  
338 +[[image:create-new-converter-menu.png||width="500"]]
254 254  
340 +
341 +
255 255  The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
256 256  
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.
344 +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.
258 258  
259 259  
260 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 -}
348 +// Encode downlink data from incoming Rule Engine message
272 272  
350 +// msg - JSON message payload downlink message json
351 +// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
352 +// metadata - list of key-value pairs with additional data about the message
353 +// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
354 +
355 +/** Encoder **/
356 +
357 +var data = {};
358 +
359 +// Process data from incoming message and metadata
360 +
361 +data.tempFreq = msg.temperatureUploadFrequency;
362 +data.humFreq = msg.humidityUploadFrequency;
363 +
364 +data.devSerialNumber = metadata['ss_serialNumber'];
365 +
273 273  // Result object with encoded downlink payload
274 274  var result = {
368 +
275 275   // downlink data content type: JSON, TEXT or BINARY (base64 format)
276 - contentType: "BINARY",
370 + contentType: "JSON",
277 277  
278 278   // downlink data
279 - data:hexToBase64(metadata.shared_value)
373 + data: JSON.stringify(data),
280 280  
281 281   // Optional metadata object presented in key/value format
282 - //metadata: {}
376 + metadata: {
377 + topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
378 + }
283 283  
284 284  };
285 285  
... ... @@ -289,24 +289,28 @@
289 289  
290 290  Click on the **Add** button.
291 291  
292 -[[image:downlink-data-converter.png||height="530" width="500"]]
293 293  
389 +[[image:add-downlink-data-converter.png||height="529" width="500"]]
294 294  
295 -You should see that the newly added **downlink data converter** is listed on the **Data Converters** page.
296 296  
297 -[[image:data-converter-list.png]]
392 +You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
298 298  
299 299  
395 +[[image:data-converters-list.png]]
396 +
397 +
300 300  = 4. Add Integration =
301 301  
302 302  
303 303  In the left navigation, click **Integrations center**, and then click **Integrations**.
304 304  
305 -On the **Integrations** page, click on the '**+**' button.
306 306  
307 -[[image:data-converter-list-page.png]]
404 +[[image:integrations-list-empty.png]]
308 308  
309 309  
407 +On the **Integrations** page, click on the '**+**' button.
408 +
409 +
310 310  The **Add integration** window appears.
311 311  
312 312  In the **Add integration** window, configure the following settings:
... ... @@ -316,9 +316,12 @@
316 316  
317 317  * **Integration type**: MQTT
318 318  * **Name**: MQTT integration NB/CB
419 +* **Enable integration**: YES
420 +* **Allows create devices or assets**: YES
319 319  
320 320  Click **Next** button.
321 321  
424 +
322 322  [[image:add-integration-basic-settings.png||height="511" width="500"]]
323 323  
324 324  
... ... @@ -329,9 +329,10 @@
329 329  
330 330  Click **Next** button.
331 331  
332 -[[image:add-integration-uplink-data-converter.png||width="500"]]
333 333  
436 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
334 334  
438 +
335 335  **Downlink data converter:**
336 336  
337 337  * Click on the **Select existing** button.
... ... @@ -339,47 +339,230 @@
339 339  
340 340  Click **Next** button.
341 341  
342 -[[image:add-integration-downlink-data-converter.png||height="510" width="500"]]
343 343  
447 +[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
344 344  
449 +
345 345  **Connection:**
346 346  
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)
452 +* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
453 +* **Port**: 8883
349 349  * **Credentials**: Basic
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
455 +* **Enable SSL**: YES
456 +* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
457 +* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
458 +* **Topic: v1/devices/+/telemetry** (the + replaces any 'device name' will create a device in the Entities -> Devices)
459 +* **QoS:** 0-At most once
354 354  
461 +[[image:add-integration-connection.png||height="511" width="500"]]
462 +
463 +
464 +Click on the **Advanced settings** button.
465 +
466 +* **Clean session:** YES
467 +* **Retained**: YES
468 +
469 +[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
470 +
471 +
355 355  Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
356 356  
357 -[[image:add-integration-connection.png||width="500"]]
358 358  
475 +[[image:check-connection.png||height="83" width="300"]]
359 359  
360 -If the connection is successful, you will see the **Connected** message.
361 361  
362 -Click on the **Add** button.
478 +If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
363 363  
364 -[[image:add-connection-success.png||height="511" width="500"]]
365 365  
481 +[[image:connection-success.png||height="511" width="500"]]
366 366  
483 +
484 +Click on the **Add** button.
485 +
367 367  You should see that the newly added integration is listed on the **Integrations** page.
368 368  
369 369  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
370 370  
371 -[[image:integrations-list-added-pending.png]]
372 372  
373 373  
374 -= 5. Verifying the receipt of data from the device =
492 +[[image:new-integration-pending.png]]
375 375  
376 376  
377 -On the terminal, issue the following MQTT command which simulates the device S31B-NB.
495 += 5. Verifying the receipt of data from virtual devices =
378 378  
497 +
498 +== 5.1 How does it work? ==
499 +
500 +
501 +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.
502 +
503 +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.
504 +
505 +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.
506 +
507 +
508 +**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.**
509 +
510 +
511 +For example, if you send two MQTT messages with different device names in the topic:
512 +
513 +1. v1/devices/**S31B-NB**/telemetry
514 +1. v1/devices/**LDS25-NB**/telemetry
515 +
516 +ThingsBoard will create two devices named **S31B-NB** and **LDS25-NB** in the **//Devices//** section.
517 +
518 +
519 +The MQTT payload format is as follows, which is common for all ~-~-NB and ~-~-CB series devices:
520 +
379 379  {{code language="none"}}
380 -mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}"
522 +{"temperature":10.4, "humidity":85}
381 381  {{/code}}
382 382  
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.
384 384  
385 -
526 +== 5.2 Sending messages ==
527 +
528 +
529 +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.
530 +
531 +{{code language="none"}}
532 +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}'
533 +{{/code}}
534 +
535 +If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
536 +
537 +
538 +[[image:integration-active.png]]
539 +
540 +
541 +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**.
542 +
543 +
544 +[[image:device-provision-1.png]]
545 +
546 +
547 +Click on the device S31B-NB on the devices list to see its details.
548 +
549 +Then go to the **Latest telemetry** tab.
550 +
551 +You can see the fields temperature and humidity with the values you previously sent using the MQTT message.
552 +
553 +
554 +[[image:telemetry-1.png]]
555 +
556 +
557 +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//.
558 +
559 +
560 +[[image:telemetry-2.png]]
561 +
562 +
563 +Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
564 +
565 +
566 +{{code language="none"}}
567 +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}'
568 +{{/code}}
569 +
570 +Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
571 +
572 +
573 +[[image:device-provision-2.png]]
574 +
575 +
576 += 6. Creating a Dashboard =
577 +
578 +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.
579 +
580 +
581 +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.
582 +
583 +
584 +In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
585 +
586 +
587 +[[image:dashboard-1.png]]
588 +
589 +
590 +In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
591 +
592 +Click on the **Add** button.
593 +
594 +
595 +[[image:dashboard-2.png||height="526" width="500"]]
596 +
597 +
598 +Click on the **Add widget / Add new widget** button.
599 +
600 +
601 +[[image:dashboard-3.png]]
602 +
603 +
604 +In the **Select widgets bundle** window, click **Charts**.
605 +
606 +
607 +[[image:dashboard-4.png||height="537" width="700"]]
608 +
609 +
610 +
611 +In the **Charts: select widget** window, click **Time series chart**.
612 +
613 +
614 +[[image:dashboard-5.png||height="525" width="700"]]
615 +
616 +
617 +Configure the **Time series chart** widget as follows:
618 +
619 +* **Datasource** - select S31B-NB device you provisioned.
620 +* **Series**:
621 +** **temperature** - you can see this key by default.
622 +** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
623 +* Click on the **Add** button.
624 +
625 +[[image:timeseries-1.png||height="491" width="700"]]
626 +
627 +
628 +The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
629 +
630 +Click the **Save** button to add the widget to the dashboard.
631 +
632 +
633 +[[image:timeseries-3.png||height="347" width="700"]]
634 +
635 +
636 +Now send the following MQTT messages from the terminal to simulate the data.
637 +
638 +
639 +{{code language="none"}}
640 +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}'
641 +
642 +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}'
643 +
644 +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}'
645 +
646 +{{/code}}
647 +
648 +The chart will update with the values in realtime, as shown in the below image.
649 +
650 +
651 +[[image:timeseries-4.png||height="316" width="700"]]
652 +
653 +
654 += 7. Configure NB-IoT Sensor =
655 +
656 +
657 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
658 +
659 +First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
660 +
661 +
662 +**AT Commands**
663 +
664 +* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
665 +* **AT+SUBTOPIC=<MQTT topic>**
666 +* **AT+PUBTOPIC=<MQTT topic>**
667 +* **AT+CLIENT=null**
668 +* **AT+UNAME=<MQTT Username>**
669 +* **AT+PWD=<MQTT Password>**
670 +* **AT+SERVADDR=<Broker address, Port>**
671 +
672 +Test your uplink by pressing the ACT button for 1 second.
add-downlink-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +175.2 KB
Content
add-integration-basic-settings.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +122.5 KB
Content
add-integration-connection-advanced-settings.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +155.2 KB
Content
add-integration-connection.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +124.4 KB
Content
add-integration-downlink-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +123.0 KB
Content
add-integration-uplink-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +120.7 KB
Content
add-uplink-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +174.1 KB
Content
check-connection.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +14.7 KB
Content
connection-success.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +90.0 KB
Content
dashboard-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +271.1 KB
Content
dashboard-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +112.2 KB
Content
dashboard-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +141.3 KB
Content
dashboard-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +803.7 KB
Content
dashboard-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +476.1 KB
Content
data-converter-list-showing-uplink-dc.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +194.9 KB
Content
data-converters-list.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +212.2 KB
Content
device-provision-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +265.7 KB
Content
device-provision-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +213.9 KB
Content
emqx.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +39.1 KB
Content
hivemq-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +82.7 KB
Content
hivemq-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +300.7 KB
Content
hivemq-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +535.2 KB
Content
hivemq-4.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +309.8 KB
Content
hivemq-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +115.0 KB
Content
hivemq-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +321.0 KB
Content
hivemq-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +203.5 KB
Content
hivemq-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +268.7 KB
Content
hivemq-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +303.7 KB
Content
hivwmq-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +380.3 KB
Content
ins1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +28.8 KB
Content
integration-active.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +64.2 KB
Content
integrations-list-empty.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +264.5 KB
Content
mqtt-uplink.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +175.1 KB
Content
new-integration-pending.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +199.7 KB
Content
telemetry-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +191.9 KB
Content
telemetry-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +185.1 KB
Content
thingsboard-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +1.9 MB
Content
thingsboard-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +901.1 KB
Content
thingsboard-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +146.3 KB
Content
thingsboard-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +122.1 KB
Content
thingsboard-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +106.7 KB
Content
thingsboard-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +119.3 KB
Content
timeseries-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +179.1 KB
Content
timeseries-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +174.2 KB
Content
timeseries-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +159.0 KB
Content