Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 162.1
edited by Dilisi S
on 2025/03/18 04:56
Change comment: Uploaded new attachment "Screenshot 2025-03-16 at 18.38.59.png", version {1}
To version 205.1
edited by Dilisi S
on 2025/04/21 16:52
Change comment: Uploaded new attachment "add-integration-part-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -164,12 +164,15 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
167 +
167 167  = 3. Data Converters =
168 168  
169 169  
170 170  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.
171 171  
173 +**In this section, you will create a universal uplink data converter for all Dragino NB-IoT devices. The uplink decoder converts any MQTT message coming from a device into key-value pairs that can be used to display and visualize data using various widgets on the dashboard**.
172 172  
175 +
173 173  == 3.1 Uplink ==
174 174  
175 175  
... ... @@ -179,7 +179,7 @@
179 179  [[image:data-converters-list-empty.png]]
180 180  
181 181  
182 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
185 +On the **Data converters** page, click on the ‘**+**’ button, and then click on **Create new converter** from the dropdown menu.
183 183  
184 184  
185 185  
... ... @@ -186,140 +186,75 @@
186 186  [[image:create-new-converter-menu.png||height="259" width="500"]]
187 187  
188 188  
189 -The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
192 +The **Add data converter** window appears.
190 190  
191 -Click on the **JavaScript** button.
194 +Name it ‘**MQTT Uplink Converter**’ and select the Type as **Uplink**.
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.
196 +Click on the **TBEL** button if it has not been selected by default.
194 194  
198 +Replace the default TBEL decoder function with the following universal TBEL decoder function, which decodes MQTT payload from any Dragino NB-IoT device.
195 195  
196 -{{code language="JavaScript"}}
197 -//Version: 0.1
198 -// decode payload to string
199 -var payloadStr = decodeToString(payload);
200 200  
201 +{{code language="JavaScript"}}
201 201  // decode payload to JSON
203 +var pattern = "yyyy/MM/dd HH:mm:ss";
202 202  var objdata = {};
203 203  var obj1 = {};
204 204  var data = decodeToJson(payload);
205 205  var deviceName = data.IMEI;
206 -delete data.IMEI;
207 -var modelname = "Dragino " + data.Model;
208 +data.remove("IMEI");
209 +var modelname = "Dragino "+ data.Model;
208 208  //var mod = data.mod
209 -delete data.Model;
211 +data.remove("Model");
210 210  //delete data.mod
211 211  var timestamp = new Date().getTime();
212 -
213 -for (var key in data) {
214 -
215 - if (Number(key)) {
216 - obj1[key] = data[key];
217 - obj1[key][obj1[key].length - 1] = Number(new Date(
218 - obj1[key][obj1[key].length - 1]));
219 -
214 +foreach (entry: data.entrySet()) {
215 + var key = entry.getKey();
216 + var value = entry.getValue();
217 + //objdata[key] = data[key]
218 + if(key.matches("^-?\\d+$")){ //is number
219 + obj1[key]=data[key];
220 + var index = obj1[key].length-1;
221 + obj1[key][index]=new Date(obj1[key][index],pattern).getTime();
220 220   }
221 -//Alec submitted25/02/25
222 -//turn old key into new
223 - else if (key === "Reading") {
224 - objdata["reading"] = data[key];
225 - } else if (key === "work mode") {
226 - objdata["work_mode"] = data[key];
227 - } else if (key === "hum") {
228 - objdata["humidity"] = data[key];
229 - }else if (key === "hum2") {
230 - objdata["humidity2"] = data[key];
231 - } else if (key === "hum3") {
232 - objdata["humidity3"] = data[key];
233 - } else if (key === "tem") {
234 - objdata["temperature"] = data[key];
235 - } else if (key === "tem2") {
236 - objdata["temperature2"] = data[key];
237 - } else if (key === "tem3") {
238 - objdata["temperature3"] = data[key];
239 - } else if (key === "DS18B20_Temp") {
240 - objdata["temperature_pro"] = data[key];
241 - } else if (key === "ds18b20_temperature") {
242 - objdata["temperature_pro"] = data[key];
243 - } else if (key === "DS18B20_temperature_pro") {
244 - objdata["temperature_pro"] = data[key];
245 - } else if (key === "tdc send flag") {
246 - objdata["tdc_send_flag"] = data[key];
247 - } else if (key === "trigger mode") {
248 - objdata["trigger_mode"] = data[key];
249 - } else if (key === "soil dielectric constant") {
250 - objdata["soil_dielectric_constant"] = data[key];
251 - } else if (key === "door open num") {
252 - objdata["door_open_num"] = data[key];
253 - } else if (key === "door duration") {
254 - objdata["door_duration"] = data[key];
255 - } else if (key === "count time") {
256 - objdata["count_time"] = data[key];
257 - } else if (key === "last open time2") {
258 - objdata["last_open_time2"] = data[key];
259 - } else if (key === "last open time3") {
260 - objdata["last_open_time3"] = data[key];
223 + else if (key==="bat"||key==="BAT"){
224 + objdata["battery"] = data[key];
261 261   }
262 -//Alec submitted25/02/25
263 - else {
264 - objdata[key] = data[key]
226 + else{
227 + objdata[key] = data[key];
228 +}}
229 +var listdata = [{"ts":timestamp,"values":objdata}];
230 +foreach ( entry1: obj1.entrySet()){
231 + var key1 = entry1.getKey();
232 + var value1 = entry1.getValue();
233 + var index = obj1[key1].length-1;
234 + var ts = obj1[key1][index];
235 + if (modelname=="Dragino RS485-NB"){
236 + listdata.push({"ts":ts,"values":{"Payload":obj1[key1][0]}});
265 265   }
266 -}
267 -var listdata = [{
268 - "ts": timestamp,
269 - "values": objdata
270 -}]
271 -for (var key1 in obj1) {
272 - if (modelname == "Dragino RS485-NB") {
273 - listdata.push({
274 - "ts": obj1[key1][obj1[key1].length - 1],
275 - "values": {
276 - "Payload": obj1[key1][0],
277 - }
278 - })
279 - } else {
280 - listdata.push({
281 - "ts": obj1[key1][obj1[key1].length - 1],
282 - "values": {
283 - "values": obj1[key1]
284 - },
285 - })
238 + else{
239 + listdata.push({"ts":ts,"values":{"values":obj1[key1]}});
286 286   }
287 287  }
288 -var result = {
289 -
242 + var result = {
290 290   deviceName: deviceName,
291 291   deviceType: modelname,
292 292   attributes: {
293 - model: modelname,
246 + model: modelname
294 294   //customerName: "NB-CB",
295 295   //groupName: "NB-CB",
296 296   //integrationName: metadata['integrationName']
297 -
298 298   },
299 299   telemetry: listdata
300 -}
301 -
302 -function decodeToString(payload) {
303 - return String.fromCharCode.apply(String, payload);
304 -}
305 -
306 -function decodeToJson(payload) {
307 - // covert payload to string.
308 - var str = decodeToString(payload);
309 -
310 - // parse string to JSON
311 - var data = JSON.parse(str);
312 - return data;
313 -}
314 -
252 +};
315 315  return result;
316 316  {{/code}}
317 317  
318 318  
319 -Click on the **Add** button.
257 +Once you modify the decoder function, click on the **Add** button.
320 320  
321 321  
322 -[[image:mqtt-uplink.png||width="500"]]
260 +[[image:mqtt-uplink-converter.png||height="498" width="500"]]
323 323  
324 324  
325 325  
... ... @@ -326,72 +326,7 @@
326 326  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
327 327  
328 328  
329 -[[image:data-converter-list-showing-uplink-dc.png]]
330 330  
331 -
332 -== 3.2 Downlink ==
333 -
334 -
335 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
336 -
337 -
338 -[[image:create-new-converter-menu.png||width="500"]]
339 -
340 -
341 -
342 -The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
343 -
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.
345 -
346 -
347 -{{code language="JavaScript"}}
348 -// Encode downlink data from incoming Rule Engine message
349 -
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 -
366 -// Result object with encoded downlink payload
367 -var result = {
368 -
369 - // downlink data content type: JSON, TEXT or BINARY (base64 format)
370 - contentType: "JSON",
371 -
372 - // downlink data
373 - data: JSON.stringify(data),
374 -
375 - // Optional metadata object presented in key/value format
376 - metadata: {
377 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
378 - }
379 -
380 -};
381 -
382 -return result;
383 -{{/code}}
384 -
385 -
386 -Click on the **Add** button.
387 -
388 -
389 -[[image:add-downlink-data-converter.png||height="529" width="500"]]
390 -
391 -
392 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
393 -
394 -
395 395  [[image:data-converters-list.png]]
396 396  
397 397  
... ... @@ -415,16 +415,18 @@
415 415  **Basic settings:**
416 416  
417 417  * **Integration type**: MQTT
418 -* **Name**: MQTT integration NB/CB
291 +* **Name**: MQTT integration - Device A
419 419  * **Enable integration**: YES
420 -* **Allows create devices or assets**: YES
293 +* **Allow create devices or assets**: YES
421 421  
422 422  Click **Next** button.
423 423  
424 424  
425 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
298 +[[image:add-integration-basic-settings.png||height="504" width="500"]]
426 426  
427 427  
301 +
302 +
428 428  **Uplink data converter:**
429 429  
430 430  * Click on the **Select existing** button.
... ... @@ -433,35 +433,37 @@
433 433  Click **Next** button.
434 434  
435 435  
436 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
311 +[[image:add-integration-ul-data-converter.png||height="505" width="500"]]
437 437  
438 438  
314 +
439 439  **Downlink data converter:**
440 440  
441 -* Click on the **Select existing** button.
442 -* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
317 +Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
443 443  
444 -Click **Next** button.
319 +* Click on the **Skip **button in the Downlink data converter section.
445 445  
321 +Click **Skip** button.
446 446  
447 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
448 448  
324 +[[image:integration-dl-skip.png||height="511" width="500"]]
449 449  
326 +
327 +
450 450  **Connection:**
451 451  
452 -* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
330 +* **Host**: Host URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
453 453  * **Port**: 8883
454 -* **Credentials**: Basic
455 -* **Enable SSL**: YES
332 +* **Credentials type**: Basic
456 456  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
457 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)
335 +* **Enable SSL**: YES
336 +* **Topic: device/a** (The topic can be anything; you can even use just the device name.)
459 459  * **QoS:** 0-At most once
460 460  
339 +[[image:add-integartion-connection.png||height="505" width="500"]]
461 461  
462 -[[image:add-integration-connection.png||height="511" width="500"]]
463 463  
464 -
465 465  Click on the **Advanced settings** button.
466 466  
467 467  * **Clean session:** YES
... ... @@ -489,8 +489,8 @@
489 489  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
490 490  
491 491  
369 +[[image:integration-added.png]]
492 492  
493 -[[image:new-integration-pending.png]]
494 494  
495 495  
496 496  = 5. Verifying the receipt of data from virtual devices =
... ... @@ -501,24 +501,24 @@
501 501  
502 502  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.
503 503  
504 -The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
381 +The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
505 505  
506 -(% 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.
383 +(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
507 507  
508 508  {{code language="none"}}
509 -{"IMEI": "S31B-NB", "temperature": 27, ......}
386 +{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
510 510  {{/code}}
511 511  
512 -Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
389 +Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
513 513  
514 514  
515 515  == 5.2 Sending messages ==
516 516  
517 517  
518 -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.
395 +On your computer's terminal, issue the following MQTT command which simulates the device '**Device A'**. The message payload contains the fields IMEI, temperature, humidity, and pressure, which hold the values 350693903995577, 30, 80, and 1005 respectively. This payload is also (technically) known as telemetry.
519 519  
520 520  {{code language="none"}}
521 -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}'
398 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":30, "humidity":80, "pressure":1005}'
522 522  {{/code}}
523 523  
524 524  If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
... ... @@ -527,42 +527,57 @@
527 527  [[image:integration-active.png]]
528 528  
529 529  
530 -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**.
407 +== 5.3 Viewing messages ==
531 531  
532 532  
410 +Go back to the **Integrations** page.
533 533  
534 -[[image:new-device.png]]
412 +Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
535 535  
414 +Click on the **Edit** button (//**pen icon**//).
536 536  
537 -Click on the device S31B-NB on the devices list to see its details.
416 +Click on the **Disabled** button in the upper-right corner.
538 538  
539 -Then go to the **Latest telemetry** tab.
418 +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.
540 540  
541 -You can see the fields temperature and humidity with the values you previously sent using the MQTT message.
420 +Click on the **Apply** button.
542 542  
422 +Then click on the **Apply changes** (//**tick icon**//) button.
543 543  
544 -[[image:telemetry-1.png]]
545 545  
425 +[[image:debug-enabled.png||height="301" width="700"]]
546 546  
547 -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//.
548 548  
549 549  
550 -[[image:telemetry-2.png]]
551 551  
430 +Now go to the **Events** tab.
552 552  
553 -Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
432 +Select the **Event type** as **Debug** from the dropdown list.
554 554  
434 +Publish another message (of course, you can repeat the previous message by pressing the UP arrow on your keyboard and then press Enter key) to your MQTT broker from your terminal, for example:
555 555  
556 556  {{code language="none"}}
557 -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}'
437 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":30, "humidity":80, "pressure":1005}'
558 558  {{/code}}
559 559  
560 -Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
440 +Now you can see that uplink message in the **Events** tab (Click the **refresh** button if you didn't see any messages in the Events tab). The status should be **OK **if there is no errors in your integration.
561 561  
562 562  
563 -[[image:device-provision-2.png]]
443 +[[image:Screenshot 2025-03-26 at 19.49.31.png]]
564 564  
565 565  
446 +
447 +Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
448 +
449 +
450 +[[image:Screenshot 2025-03-26 at 19.47.52.png]]
451 +
452 +
453 +
454 +
455 +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.
456 +
457 +
566 566  = 6. Creating a Dashboard =
567 567  
568 568  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.
... ... @@ -571,6 +571,11 @@
571 571  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.
572 572  
573 573  
466 +First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
467 +
468 +{{code language="none"}}mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":22, "humidity":80, "pressure":1005}'{{/code}}
469 +
470 +
574 574  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
575 575  
576 576  
... ... @@ -606,15 +606,19 @@
606 606  
607 607  Configure the **Time series chart** widget as follows:
608 608  
609 -* **Datasource** - select S31B-NB device you provisioned.
506 +* **Datasource** - select **Device A** device you provisioned.
610 610  * **Series**:
611 611  ** **temperature** - you can see this key by default.
612 612  ** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
613 613  * Click on the **Add** button.
614 614  
615 -[[image:timeseries-1.png||height="491" width="700"]]
512 +{{info}}
513 +You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
514 +{{/info}}
616 616  
516 +[[image:Screenshot 2025-03-31 at 06.51.15.png||height="485" width="700"]]
617 617  
518 +
618 618  The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
619 619  
620 620  Click the **Save** button to add the widget to the dashboard.
... ... @@ -627,12 +627,11 @@
627 627  
628 628  
629 629  {{code language="none"}}
630 -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}'
531 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":22, "humidity":70, "pressure":1005}'
631 631  
632 -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}'
533 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":27, "humidity":72, "pressure":1005}'
633 633  
634 -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}'
635 -
535 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":19, "humidity":80, "pressure":1005}'
636 636  {{/code}}
637 637  
638 638  The chart will update with the values in realtime, as shown in the below image.
... ... @@ -641,10 +641,10 @@
641 641  [[image:timeseries-4.png||height="316" width="700"]]
642 642  
643 643  
644 -= 7. Configure NB-IoT Sensor =
544 += 8. Configure Physical NB-IoT Sensor =
645 645  
646 646  
647 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
547 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
648 648  
649 649  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
650 650  
... ... @@ -652,8 +652,8 @@
652 652  **AT Commands**
653 653  
654 654  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
655 -* **AT+SUBTOPIC=<MQTT topic>**
656 -* **AT+PUBTOPIC=<MQTT topic>**
555 +* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
556 +* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
657 657  * **AT+CLIENT=null**
658 658  * **AT+UNAME=<MQTT Username>**
659 659  * **AT+PWD=<MQTT Password>**
... ... @@ -660,3 +660,10 @@
660 660  * **AT+SERVADDR=<Broker address, Port>**
661 661  
662 662  Test your uplink by pressing the ACT button for 1 second.
563 +
564 +
565 +
566 +The following image shows the uplink payload of a real Dragino device. The publish topic is '**TS01-NB' that contains fields in the payload, IMEI, IMSI, Model, temperature, etc**. Note that we have created a device named **TS01-NB** in the **Devices** section in advance.
567 +
568 +
569 +[[image:image-4.png]]
add-integration-basic-settings.png
Size
... ... @@ -1,1 +1,1 @@
1 -122.5 KB
1 +123.8 KB
Content
add-integration-connection.png
Size
... ... @@ -1,1 +1,1 @@
1 -153.2 KB
1 +158.1 KB
Content
data-converters-list.png
Size
... ... @@ -1,1 +1,1 @@
1 -212.2 KB
1 +19.0 KB
Content
integration-active.png
Size
... ... @@ -1,1 +1,1 @@
1 -64.2 KB
1 +64.1 KB
Content
Screenshot 2025-03-16 at 18.39.12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +211.9 KB
Content
Screenshot 2025-03-18 at 09.23.10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +78.7 KB
Content
Screenshot 2025-03-26 at 18.15.08.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +92.2 KB
Content
Screenshot 2025-03-26 at 19.47.52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +168.4 KB
Content
Screenshot 2025-03-26 at 19.49.31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +133.0 KB
Content
Screenshot 2025-03-31 at 06.51.15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +179.5 KB
Content
add-integartion-connection.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +110.3 KB
Content
add-integartion-connetcion.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +146.0 KB
Content
add-integration-part-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +48.6 KB
Content
add-integration-ul-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +121.2 KB
Content
debug-enabled.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.3 KB
Content
image-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +96.0 KB
Content
integration-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.2 KB
Content
integration-dl-skip.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +105.5 KB
Content
mqtt-uplink-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +75.3 KB
Content
ul-data-converter-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +189.4 KB
Content
ul-data-converter-device-a.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +168.3 KB
Content