Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 173.1
edited by Dilisi S
on 2025/03/20 16:21
Change comment: Uploaded new attachment "add-integration-connection.png", version {1}
To version 221.1
edited by Dilisi S
on 2025/04/23 01:38
Change comment: April 22 edits

Summary

Details

Page properties
Content
... ... @@ -23,8 +23,9 @@
23 23  
24 24  * ThingsBoard cloud account
25 25  * MQTT Broker (public or private) such as,
26 +** [[ThingsBoard MQTT broker>>https://thingsboard.io/docs/mqtt-broker/]] (TBMQ)
26 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 +** [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] - The public MQTT server is only used for MQTT learning and testing, and should not be used in the production environment.
28 28  ** [[lns1.thingseye.io>>http://lns1.thingseye.io/]] - This is Dragino's MQTT broker, which requires a CA certificate to use.
29 29  
30 30  == 2.1 ThingsBoard Cloud ==
... ... @@ -67,11 +67,19 @@
67 67  [[image:thingsboard-6.png||height="244" width="500"]]
68 68  
69 69  
70 -== 2.2 HiveMQ Cloud ==
71 +== 2.2 MQTT Brokers ==
71 71  
72 -=== 2.2.1 HiveMQ Cloud ===
73 +This section introduces some MQTT brokers that you can use to publish messages from the device side and subscribe from the ThingsBoard side.
73 73  
74 74  
76 +=== 2.2.1 ThingsBoard MQTT broker (TBMQ) ===
77 +
78 +The complete instructions for installing, configuring, and using the TBMQ can be found [[here>>https://thingsboard.io/docs/mqtt-broker/getting-started/]].
79 +
80 +
81 +=== 2.2.2 HiveMQ Cloud ===
82 +
83 +
75 75  Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
76 76  
77 77  Click on the **Start Free** button.
... ... @@ -146,7 +146,7 @@
146 146  You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
147 147  
148 148  
149 -=== 2.2.2 emqx ===
158 +=== 2.2.3 emqx ===
150 150  
151 151  
152 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.
... ... @@ -155,7 +155,7 @@
155 155  [[image:emqx.png||height="420" width="500"]]
156 156  
157 157  
158 -=== 2.2.3 Ins1.thingseye.io ===
167 +=== 2.2.4 Ins1.thingseye.io ===
159 159  
160 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 161  
... ... @@ -164,12 +164,15 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
176 +
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  
182 +**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  
184 +
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.
194 +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**.
201 +The **Add data converter** window appears.
190 190  
191 -Click on the **JavaScript** button.
203 +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.
205 +Click on the **TBEL** button if it has not been selected by default.
194 194  
207 +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  
210 +{{code language="JavaScript"}}
201 201  // decode payload to JSON
212 +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;
217 +data.remove("IMEI");
218 +var modelname = "Dragino "+ data.Model;
208 208  //var mod = data.mod
209 -delete data.Model;
220 +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 -
223 +foreach (entry: data.entrySet()) {
224 + var key = entry.getKey();
225 + var value = entry.getValue();
226 + //objdata[key] = data[key]
227 + if(key.matches("^-?\\d+$")){ //is number
228 + obj1[key]=data[key];
229 + var index = obj1[key].length-1;
230 + 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];
232 + else if (key==="bat"||key==="BAT"){
233 + objdata["battery"] = data[key];
261 261   }
262 -//Alec submitted25/02/25
263 - else {
264 - objdata[key] = data[key]
235 + else{
236 + objdata[key] = data[key];
237 +}}
238 +var listdata = [{"ts":timestamp,"values":objdata}];
239 +foreach ( entry1: obj1.entrySet()){
240 + var key1 = entry1.getKey();
241 + var value1 = entry1.getValue();
242 + var index = obj1[key1].length-1;
243 + var ts = obj1[key1][index];
244 + if (modelname=="Dragino RS485-NB"){
245 + 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 - })
247 + else{
248 + listdata.push({"ts":ts,"values":{"values":obj1[key1]}});
286 286   }
287 287  }
288 -var result = {
289 -
251 + var result = {
290 290   deviceName: deviceName,
291 291   deviceType: modelname,
292 292   attributes: {
293 - model: modelname,
255 + 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 -
261 +};
315 315  return result;
316 316  {{/code}}
317 317  
318 318  
319 -Click on the **Add** button.
266 +Once you modify the decoder function, click on the **Add** button.
320 320  
321 321  
322 -[[image:mqtt-uplink.png||width="500"]]
269 +[[image:mqtt-uplink-converter.png||height="498" width="500"]]
323 323  
324 324  
325 325  
... ... @@ -326,13 +326,10 @@
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  
277 +[[image:data-converters-list.png]]
331 331  
332 332  
333 -
334 -
335 -
336 336  = 4. Add Integration =
337 337  
338 338  
... ... @@ -353,16 +353,17 @@
353 353  **Basic settings:**
354 354  
355 355  * **Integration type**: MQTT
356 -* **Name**: MQTT integration NB/CB
300 +* **Name**: MQTT integration
357 357  * **Enable integration**: YES
358 -* **Allows create devices or assets**: YES
302 +* **Allow create devices or assets**: YES
359 359  
360 360  Click **Next** button.
361 361  
362 362  
363 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
364 364  
308 +[[image:add-integration-part-1.png||height="483" width="500"]]
365 365  
310 +
366 366  **Uplink data converter:**
367 367  
368 368  * Click on the **Select existing** button.
... ... @@ -371,9 +371,10 @@
371 371  Click **Next** button.
372 372  
373 373  
374 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
375 375  
320 +[[image:add-integration-part-2.png||height="484" width="500"]]
376 376  
322 +
377 377  **Downlink data converter:**
378 378  
379 379  Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
... ... @@ -389,16 +389,16 @@
389 389  
390 390  **Connection:**
391 391  
392 -* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
393 -* **Port**: 8883
394 -* **Credentials**: Basic
395 -* **Enable SSL**: YES
338 +* **Host**: Host URL (Eg, **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
339 +* **Port**: 8883 (the port number may differ based on your MQTT broker)
340 +* **Credentials type**: Basic
396 396  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
397 397  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
398 -* **Topic: v1/devices/me/telemetry** (The topic can be anything, even you can use just the device name, for example ts02-nb)
343 +* **Enable SSL**: YES
344 +* **Topic**: # (the # symbol indicates that it filters all topics).
399 399  * **QoS:** 0-At most once
400 400  
401 -[[image:add-integration-connection.png||height="511" width="500"]]
347 +[[image:add-integration-4.png||height="484" width="500"]]
402 402  
403 403  
404 404  Click on the **Advanced settings** button.
... ... @@ -429,7 +429,7 @@
429 429  
430 430  
431 431  
432 -[[image:new-integration-pending.png]]
378 +[[image:integrations-pending.png]]
433 433  
434 434  
435 435  = 5. Verifying the receipt of data from virtual devices =
... ... @@ -440,44 +440,47 @@
440 440  
441 441  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.
442 442  
443 -The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
389 +The Mosquitto client publishes messages (payloads) to a topic - for example, # or device/ts01-nb. You can, of course, use any topic you prefer.
444 444  
445 -(% 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.
446 446  
392 +(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows. The **IMEI **and **Model **are mandatory fields. For other fields, you can use any number of key-value pairs.
393 +
447 447  {{code language="none"}}
448 -{"IMEI": "S31B-NB", "temperature": 27, ......}
395 +{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}
449 449  {{/code}}
450 450  
451 -Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
452 452  
453 -
454 454  == 5.2 Sending messages ==
455 455  
456 456  
457 -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.
402 +On your computer's terminal, issue the following MQTT command, which simulates the device named '**350693903995577'**. The message payload contains the fields IMEI, Model, temperature, humidity, and pressure, which hold the values 350693903995577,  TS01-NB, 30, 80, and 1005 respectively. This payload is also (technically) known as telemetry.
458 458  
459 459  {{code language="none"}}
460 -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}'
405 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/350693903995577" -m '{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}'
461 461  {{/code}}
462 462  
463 -If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
408 +If the integration was performed without errors, a new device named **350693903995577 **is created in the **Devices **section.
464 464  
465 465  
466 -[[image:integration-active.png]]
411 +[[image:new-device-1.png]]
467 467  
468 468  
469 -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**.
414 +The status of the integration also changes to '**Active**' after the first telemetry transmission.
470 470  
471 471  
472 -[[image:new-device.png]]
417 +[[image:Screenshot 2025-04-21 122154.png]]
473 473  
474 474  
420 +
421 +**When ThingsBoard receives this message for the first time, it will automatically create a new device named '350693903995577' in the Devices section. The device name is based on the IMEI number. For subsequent messages with the same IMEI, no duplicate devices will be created. Each new IMEI number will result in a unique entry in the Devices section, representing a physical device.**
422 +
423 +
475 475  == 5.3 Viewing messages ==
476 476  
477 477  
478 478  Go back to the **Integrations** page.
479 479  
480 -Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
429 +Click on the **MQTT integration** in the **Integrations** page to see its details.
481 481  
482 482  Click on the **Edit** button (//**pen icon**//).
483 483  
... ... @@ -490,25 +490,30 @@
490 490  Then click on the **Apply changes** (//**tick icon**//) button.
491 491  
492 492  
493 -[[image:Screenshot 2025-03-18 at 09.23.10.png]]
494 494  
443 +[[image:Screenshot 2025-04-21 122936.png||height="247" width="500"]]
495 495  
445 +
496 496  Now go to the **Events** tab.
497 497  
498 -Select the Event type as **Debug** from the dropdown list.
448 +Select the **Event type** as **Debug** from the dropdown list.
499 499  
500 -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.
450 +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:
501 501  
452 +{{code language="none"}}
453 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/350693903995577" -m '{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":82, "pressure":1005}'
454 +{{/code}}
502 502  
503 -[[image:Screenshot 2025-03-16 at 18.38.59.png]]
456 +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.
504 504  
505 505  
506 506  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
507 507  
508 508  
509 -[[image:Screenshot 2025-03-16 at 18.39.12.png]]
510 510  
463 +[[image:Screenshot 2025-04-21 122909.png]]
511 511  
465 +
512 512  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.
513 513  
514 514  
... ... @@ -520,11 +520,6 @@
520 520  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.
521 521  
522 522  
523 -First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
524 -
525 -{{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}}
526 -
527 -
528 528  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
529 529  
530 530  
... ... @@ -560,44 +560,41 @@
560 560  
561 561  Configure the **Time series chart** widget as follows:
562 562  
563 -* **Datasource** - select S31B-NB device you provisioned.
512 +* **Datasource** - select **350693903995577 **you provisioned.
564 564  * **Series**:
565 565  ** **temperature** - you can see this key by default.
566 -** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
515 +** **humidity** - Click **Add series** button. Then choose **humidity** for the key, and then type **%** as its unit.
516 +** pressure -  Click **Add series** button. Then choose **humidity** for the key, and then type Pa as its unit.
567 567  * Click on the **Add** button.
568 568  
569 -[[image:timeseries-1.png||height="491" width="700"]]
519 +{{info}}
520 +You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
521 +{{/info}}
570 570  
571 571  
572 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
573 573  
574 -Click the **Save** button to add the widget to the dashboard.
525 +[[image:Screenshot 2025-04-21 123647.png||height="466" width="700"]]
575 575  
576 576  
577 -[[image:timeseries-3.png||height="347" width="700"]]
528 +The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
578 578  
530 +Click the **Save** button to add the widget to the dashboard.
579 579  
580 -Now send the following MQTT messages from the terminal to simulate the data.
581 581  
533 +[[image:Screenshot 2025-04-21 124145.png||height="443" width="700"]]
582 582  
583 -{{code language="none"}}
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": 22, "humidity":70}'
585 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": 27, "humidity":72}'
536 +**Now send a few MQTT messages from the terminal to simulate the data. Use different values for temperature, humidity, and pressure in each message.**
587 587  
588 -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}'
538 +**The chart will update with the values in real time, and you will see a live chart similar to this:**
589 589  
590 -{{/code}}
591 591  
592 -The chart will update with the values in realtime, as shown in the below image.
541 +[[image:Screenshot 2025-04-21 124054.png||height="441" width="700"]]
593 593  
594 594  
595 -[[image:timeseries-4.png||height="316" width="700"]]
544 += 8. Configure Physical NB-IoT Sensor =
596 596  
597 597  
598 -= 7. Configure NB-IoT Sensor =
599 -
600 -
601 601  Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
602 602  
603 603  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
... ... @@ -606,8 +606,8 @@
606 606  **AT Commands**
607 607  
608 608  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
609 -* **AT+SUBTOPIC=<MQTT subscribe topic> **
610 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
555 +* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: # -  **You can leave the SUBTOPIC configuration as it is, since we are not sending downlink messages to the device at the moment.
556 +* **AT+PUBTOPIC=<MQTT publish topic> Eg: #**
611 611  * **AT+CLIENT=null**
612 612  * **AT+UNAME=<MQTT Username>**
613 613  * **AT+PWD=<MQTT Password>**
... ... @@ -616,14 +616,7 @@
616 616  Test your uplink by pressing the ACT button for 1 second.
617 617  
618 618  
565 +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.
619 619  
620 -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**.
621 621  
622 -{{info}}
623 -The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
624 -{{/info}}
625 -
626 626  [[image:image-4.png]]
627 -
628 -
629 -
Screenshot 2025-03-16 at 18.39.12.png
Size
... ... @@ -1,1 +1,1 @@
1 -277.0 KB
1 +211.9 KB
Content
add-integration-basic-settings.png
Size
... ... @@ -1,1 +1,1 @@
1 -122.5 KB
1 +123.8 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-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
Screenshot 2025-04-21 122154.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +21.2 KB
Content
Screenshot 2025-04-21 122909.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +59.9 KB
Content
Screenshot 2025-04-21 122936.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +72.0 KB
Content
Screenshot 2025-04-21 123647.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +77.9 KB
Content
Screenshot 2025-04-21 124054.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +60.4 KB
Content
Screenshot 2025-04-21 124145.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +50.9 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-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +63.1 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-part-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +47.7 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
device-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +34.5 KB
Content
integration-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.2 KB
Content
integrations-pending.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +19.8 KB
Content
mqtt-uplink-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +75.3 KB
Content
new-device-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +34.7 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