Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 177.1
edited by Dilisi S
on 2025/03/26 21:03
Change comment: Mar 26 edits - part 2
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,34 +164,18 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
167 -= 3. Creating Devices =
168 168  
177 += 3. Data Converters =
169 169  
170 -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.
171 171  
172 -
173 -In the left navigation, click Entities -> Devices.
174 -
175 -Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
176 -
177 -In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
178 -
179 -Click the **Add** button.
180 -
181 -Skip the **connectivity testing** by clicking the **Close** button.
182 -
183 -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.
184 -
185 -
186 -= 4. Data Converters =
187 -
188 -
189 189  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.
190 190  
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**.
191 191  
192 -== 4.1 Uplink ==
193 193  
185 +== 3.1 Uplink ==
194 194  
187 +
195 195  In the left navigation, click **Integrations center**, and then click **Data converters**.
196 196  
197 197  
... ... @@ -198,7 +198,7 @@
198 198  [[image:data-converters-list-empty.png]]
199 199  
200 200  
201 -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.
202 202  
203 203  
204 204  
... ... @@ -205,81 +205,75 @@
205 205  [[image:create-new-converter-menu.png||height="259" width="500"]]
206 206  
207 207  
208 -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.
209 209  
203 +Name it ‘**MQTT Uplink Converter**’ and select the Type as **Uplink**.
204 +
210 210  Click on the **TBEL** button if it has not been selected by default.
211 211  
212 -The default TBEL function is shown below.
207 +Replace the default TBEL decoder function with the following universal TBEL decoder function, which decodes MQTT payload from any Dragino NB-IoT device.
213 213  
214 214  
215 215  {{code language="JavaScript"}}
216 -// Decode an uplink message from a buffer
217 -// payload - array of bytes
218 -// metadata - key/value object
219 -
220 -/** Decoder **/
221 -
222 -// decode payload to string
223 -var payloadStr = decodeToString(payload);
224 -
225 225  // decode payload to JSON
226 -// var data = decodeToJson(payload);
227 -
228 -var deviceName = 'Device A';
229 -var deviceType = 'thermostat';
230 -var customerName = 'Customer C';
231 -var groupName = 'thermostat devices';
232 -var manufacturer = 'Example corporation';
233 -// use assetName and assetType instead of deviceName and deviceType
234 -// to automatically create assets instead of devices.
235 -// var assetName = 'Asset A';
236 -// var assetType = 'building';
237 -
238 -// Result object with device/asset attributes/telemetry data
239 -var result = {
240 -// Use deviceName and deviceType or assetName and assetType, but not both.
241 - deviceName: deviceName,
242 - deviceType: deviceType,
243 -// assetName: assetName,
244 -// assetType: assetType,
245 -// customerName: customerName,
246 - groupName: groupName,
247 - attributes: {
248 - model: 'Model A',
249 - serialNumber: 'SN111',
250 - integrationName: metadata['integrationName'],
251 - manufacturer: manufacturer
252 - },
253 - telemetry: {
254 - temperature: 42,
255 - humidity: 80,
256 - rawData: payloadStr
257 - }
212 +var pattern = "yyyy/MM/dd HH:mm:ss";
213 +var objdata = {};
214 +var obj1 = {};
215 +var data = decodeToJson(payload);
216 +var deviceName = data.IMEI;
217 +data.remove("IMEI");
218 +var modelname = "Dragino "+ data.Model;
219 +//var mod = data.mod
220 +data.remove("Model");
221 +//delete data.mod
222 +var timestamp = new Date().getTime();
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();
231 + }
232 + else if (key==="bat"||key==="BAT"){
233 + objdata["battery"] = data[key];
234 + }
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]}});
246 + }
247 + else{
248 + listdata.push({"ts":ts,"values":{"values":obj1[key1]}});
249 + }
250 +}
251 + var result = {
252 + deviceName: deviceName,
253 + deviceType: modelname,
254 + attributes: {
255 + model: modelname
256 + //customerName: "NB-CB",
257 + //groupName: "NB-CB",
258 + //integrationName: metadata['integrationName']
259 + },
260 + telemetry: listdata
258 258  };
259 -
260 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
261 -
262 262  return result;
263 263  {{/code}}
264 264  
265 -We use the same decoder function for all our devices. However, you need to modify a few things for each device. Among these, **deviceName** is a **mandatory** field. You should assign a device name to the **deviceName** field that matches the name of your device in the **Devices** section.
266 266  
267 -For example, if your device name is **Device B**, you can change **Device A** to **Device B**.
268 -
269 -
270 -{{code language="JavaScript"}}
271 -var deviceName = 'Device A';
272 -var deviceType = 'thermostat';
273 -var customerName = 'Customer C';
274 -var groupName = 'thermostat devices';
275 -var manufacturer = 'Example corporation';
276 -{{/code}}
277 -
278 -
279 279  Once you modify the decoder function, click on the **Add** button.
280 280  
281 281  
282 -[[image:mqtt-uplink.png||width="500"]]
269 +[[image:mqtt-uplink-converter.png||height="498" width="500"]]
283 283  
284 284  
285 285  
... ... @@ -286,12 +286,13 @@
286 286  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
287 287  
288 288  
289 -[[image:data-converter-list-showing-uplink-dc.png]]
290 290  
277 +[[image:data-converters-list.png]]
291 291  
292 -= 5. Add Integration =
293 293  
280 += 4. Add Integration =
294 294  
282 +
295 295  In the left navigation, click **Integrations center**, and then click **Integrations**.
296 296  
297 297  
... ... @@ -309,16 +309,17 @@
309 309  **Basic settings:**
310 310  
311 311  * **Integration type**: MQTT
312 -* **Name**: MQTT integration NB/CB
300 +* **Name**: MQTT integration
313 313  * **Enable integration**: YES
314 -* **Allows create devices or assets**: YES
302 +* **Allow create devices or assets**: YES
315 315  
316 316  Click **Next** button.
317 317  
318 318  
319 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
320 320  
308 +[[image:add-integration-part-1.png||height="483" width="500"]]
321 321  
310 +
322 322  **Uplink data converter:**
323 323  
324 324  * Click on the **Select existing** button.
... ... @@ -327,9 +327,10 @@
327 327  Click **Next** button.
328 328  
329 329  
330 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
331 331  
320 +[[image:add-integration-part-2.png||height="484" width="500"]]
332 332  
322 +
333 333  **Downlink data converter:**
334 334  
335 335  Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
... ... @@ -345,16 +345,16 @@
345 345  
346 346  **Connection:**
347 347  
348 -* **Host**: Cluster URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
349 -* **Port**: 8883
350 -* **Credentials**: Basic
351 -* **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
352 352  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
353 353  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
354 -* **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 devices/a/telemetry.)
343 +* **Enable SSL**: YES
344 +* **Topic**: # (the # symbol indicates that it filters all topics).
355 355  * **QoS:** 0-At most once
356 356  
357 -[[image:add-integration-connection.png||height="511" width="500"]]
347 +[[image:add-integration-4.png||height="484" width="500"]]
358 358  
359 359  
360 360  Click on the **Advanced settings** button.
... ... @@ -384,55 +384,59 @@
384 384  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
385 385  
386 386  
387 -[[image:new-integration-pending.png]]
388 388  
378 +[[image:integrations-pending.png]]
389 389  
390 -= 6. Verifying the receipt of data from virtual devices =
391 391  
381 += 5. Verifying the receipt of data from virtual devices =
392 392  
393 -== 6.1 How does it work? ==
394 394  
384 +== 5.1 How does it work? ==
395 395  
386 +
396 396  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.
397 397  
398 -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.
399 399  
400 -(% 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.
401 401  
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 +
402 402  {{code language="none"}}
403 -{"IMEI": "S31B-NB", "temperature": 27, ......}
395 +{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}
404 404  {{/code}}
405 405  
406 -Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
407 407  
408 -
409 409  == 5.2 Sending messages ==
410 410  
411 411  
412 -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.
413 413  
414 414  {{code language="none"}}
415 -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}'
416 416  {{/code}}
417 417  
418 -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.
419 419  
420 420  
421 -[[image:integration-active.png]]
411 +[[image:new-device-1.png]]
422 422  
423 423  
424 -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.
425 425  
426 426  
427 -[[image:new-device.png]]
417 +[[image:Screenshot 2025-04-21 122154.png]]
428 428  
429 429  
430 -== 6.3 Viewing messages ==
431 431  
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.**
432 432  
423 +
424 +== 5.3 Viewing messages ==
425 +
426 +
433 433  Go back to the **Integrations** page.
434 434  
435 -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.
436 436  
437 437  Click on the **Edit** button (//**pen icon**//).
438 438  
... ... @@ -445,29 +445,34 @@
445 445  Then click on the **Apply changes** (//**tick icon**//) button.
446 446  
447 447  
448 -[[image:Screenshot 2025-03-18 at 09.23.10.png]]
449 449  
443 +[[image:Screenshot 2025-04-21 122936.png||height="247" width="500"]]
450 450  
445 +
451 451  Now go to the **Events** tab.
452 452  
453 -Select the Event type as **Debug** from the dropdown list.
448 +Select the **Event type** as **Debug** from the dropdown list.
454 454  
455 -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:
456 456  
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}}
457 457  
458 -[[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.
459 459  
460 460  
461 461  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
462 462  
463 463  
464 -[[image:Screenshot 2025-03-16 at 18.39.12.png]]
465 465  
463 +[[image:Screenshot 2025-04-21 122909.png]]
466 466  
465 +
467 467  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.
468 468  
469 469  
470 -= 7. Creating a Dashboard =
469 += 6. Creating a Dashboard =
471 471  
472 472  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.
473 473  
... ... @@ -475,11 +475,6 @@
475 475  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.
476 476  
477 477  
478 -First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
479 -
480 -{{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}}
481 -
482 -
483 483  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
484 484  
485 485  
... ... @@ -515,44 +515,41 @@
515 515  
516 516  Configure the **Time series chart** widget as follows:
517 517  
518 -* **Datasource** - select S31B-NB device you provisioned.
512 +* **Datasource** - select **350693903995577 **you provisioned.
519 519  * **Series**:
520 520  ** **temperature** - you can see this key by default.
521 -** **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.
522 522  * Click on the **Add** button.
523 523  
524 -[[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}}
525 525  
526 526  
527 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
528 528  
529 -Click the **Save** button to add the widget to the dashboard.
525 +[[image:Screenshot 2025-04-21 123647.png||height="466" width="700"]]
530 530  
531 531  
532 -[[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.
533 533  
530 +Click the **Save** button to add the widget to the dashboard.
534 534  
535 -Now send the following MQTT messages from the terminal to simulate the data.
536 536  
533 +[[image:Screenshot 2025-04-21 124145.png||height="443" width="700"]]
537 537  
538 -{{code language="none"}}
539 -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}'
540 540  
541 -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.**
542 542  
543 -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:**
544 544  
545 -{{/code}}
546 546  
547 -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"]]
548 548  
549 549  
550 -[[image:timeseries-4.png||height="316" width="700"]]
544 += 8. Configure Physical NB-IoT Sensor =
551 551  
552 552  
553 -= 8. Configure NB-IoT Sensor =
554 -
555 -
556 556  Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
557 557  
558 558  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
... ... @@ -561,8 +561,8 @@
561 561  **AT Commands**
562 562  
563 563  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
564 -* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
565 -* **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: #**
566 566  * **AT+CLIENT=null**
567 567  * **AT+UNAME=<MQTT Username>**
568 568  * **AT+PWD=<MQTT Password>**
... ... @@ -571,14 +571,7 @@
571 571  Test your uplink by pressing the ACT button for 1 second.
572 572  
573 573  
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.
574 574  
575 -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**.
576 576  
577 -{{info}}
578 -The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
579 -{{/info}}
580 -
581 581  [[image:image-4.png]]
582 -
583 -
584 -
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