Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 222.1
edited by Dilisi S
on 2025/04/23 19:23
Change comment: There is no comment for this version
To version 188.1
edited by Dilisi S
on 2025/03/27 22:53
Change comment: Uploaded new attachment "add-integartion-connection.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -23,9 +23,8 @@
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)
27 -** **[[HiveMQ Cloud>>https://www.hivemq.com]] **-** **You can create a free account to try it or subscribe for a paid account.
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.
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.
29 29  ** [[lns1.thingseye.io>>http://lns1.thingseye.io/]] - This is Dragino's MQTT broker, which requires a CA certificate to use.
30 30  
31 31  == 2.1 ThingsBoard Cloud ==
... ... @@ -68,19 +68,11 @@
68 68  [[image:thingsboard-6.png||height="244" width="500"]]
69 69  
70 70  
71 -== 2.2 MQTT Brokers ==
70 +== 2.2 HiveMQ Cloud ==
72 72  
73 -This section introduces some MQTT brokers that you can use to publish messages from the device side and subscribe from the ThingsBoard side.
72 +=== 2.2.1 HiveMQ Cloud ===
74 74  
75 75  
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 -
84 84  Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
85 85  
86 86  Click on the **Start Free** button.
... ... @@ -155,7 +155,7 @@
155 155  You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
156 156  
157 157  
158 -=== 2.2.3 emqx ===
149 +=== 2.2.2 emqx ===
159 159  
160 160  
161 161  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.
... ... @@ -164,7 +164,7 @@
164 164  [[image:emqx.png||height="420" width="500"]]
165 165  
166 166  
167 -=== 2.2.4 Ins1.thingseye.io ===
158 +=== 2.2.3 Ins1.thingseye.io ===
168 168  
169 169  [[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.
170 170  
... ... @@ -173,18 +173,34 @@
173 173  [[image:ins1.png||height="310" width="500"]]
174 174  
175 175  
167 += 3. Creating Devices =
176 176  
177 -= 3. Data Converters =
178 178  
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.
179 179  
180 -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.
181 181  
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**.
173 +In the left navigation, click Entities -> Devices.
183 183  
175 +Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
184 184  
185 -== 3.1 Uplink ==
177 +In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
186 186  
179 +Click the **Add** button.
187 187  
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 +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 +
191 +
192 +== 4.1 Uplink ==
193 +
194 +
188 188  In the left navigation, click **Integrations center**, and then click **Data converters**.
189 189  
190 190  
... ... @@ -191,7 +191,7 @@
191 191  [[image:data-converters-list-empty.png]]
192 192  
193 193  
194 -On the **Data converters** page, click on the ‘**+**’ button, and then click on **Create new converter** from the dropdown menu.
201 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
195 195  
196 196  
197 197  
... ... @@ -198,67 +198,77 @@
198 198  [[image:create-new-converter-menu.png||height="259" width="500"]]
199 199  
200 200  
201 -The **Add data converter** window appears.
208 +The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
202 202  
203 -Name it ‘**MQTT Uplink Converter**’ and select the Type as **Uplink**.
204 -
205 205  Click on the **TBEL** button if it has not been selected by default.
206 206  
207 -Replace the default TBEL decoder function with the following universal TBEL decoder function, which decodes MQTT payload from any Dragino NB-IoT device.
212 +Modify the default TBEL function to match with your device as described below:
208 208  
209 209  
215 +* Uncomment** line 11**:
216 +
217 +//var data = decodeToJson(payload)//
218 +
219 +
220 +* **Line 13**: Assign your device name to the **deviceName** field. - We used **Device A** as it is to match with our device, **Device A **in the Devices section.
221 +* From **line 38**: Modify the telemetry section to allow parsed data to be assigned to the fields.
222 +
223 +//telemetry: {
224 + temperature: data.temperature,
225 + humidity: data.humidity,
226 + rawData: payloadStr
227 + }//
228 +
229 +
230 +The modified uplink decoder function to match with **Device A** is shown below.
231 +
210 210  {{code language="JavaScript"}}
233 +// Decode an uplink message from a buffer
234 +// payload - array of bytes
235 +// metadata - key/value object
236 +
237 +/** Decoder **/
238 +
239 +// decode payload to string
240 +var payloadStr = decodeToString(payload);
241 +
211 211  // decode payload to JSON
212 -var pattern = "yyyy/MM/dd HH:mm:ss";
213 -var objdata = {};
214 -var obj1 = {};
215 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
244 +
245 +var deviceName = 'Device A';
246 +var deviceType = 'thermostat';
247 +var customerName = 'Customer C';
248 +var groupName = 'thermostat devices';
249 +var manufacturer = 'Example corporation';
250 +// use assetName and assetType instead of deviceName and deviceType
251 +// to automatically create assets instead of devices.
252 +// var assetName = 'Asset A';
253 +// var assetType = 'building';
254 +
255 +// Result object with device/asset attributes/telemetry data
256 +var result = {
257 +// Use deviceName and deviceType or assetName and assetType, but not both.
258 + deviceName: deviceName,
259 + deviceType: deviceType,
260 +// assetName: assetName,
261 +// assetType: assetType,
262 +// customerName: customerName,
263 + groupName: groupName,
264 + attributes: {
265 + model: 'Model A',
266 + serialNumber: 'SN111',
267 + integrationName: metadata['integrationName'],
268 + manufacturer: manufacturer
269 + },
270 + telemetry: {
271 + temperature: data.temperature,
272 + humidity: data.humidity,
273 + rawData: payloadStr
274 + }
261 261  };
276 +
277 +/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
278 +
262 262  return result;
263 263  {{/code}}
264 264  
... ... @@ -266,7 +266,7 @@
266 266  Once you modify the decoder function, click on the **Add** button.
267 267  
268 268  
269 -[[image:mqtt-uplink-converter.png||height="498" width="500"]]
286 +[[image:mqtt-uplink.png||width="500"]]
270 270  
271 271  
272 272  
... ... @@ -273,13 +273,12 @@
273 273  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
274 274  
275 275  
293 +[[image:data-converter-list-showing-uplink-dc.png]]
276 276  
277 -[[image:data-converters-list.png]]
278 278  
296 += 5. Add Integration =
279 279  
280 -= 4. Add Integration =
281 281  
282 -
283 283  In the left navigation, click **Integrations center**, and then click **Integrations**.
284 284  
285 285  
... ... @@ -297,17 +297,16 @@
297 297  **Basic settings:**
298 298  
299 299  * **Integration type**: MQTT
300 -* **Name**: MQTT integration
316 +* **Name**: MQTT integration NB/CB
301 301  * **Enable integration**: YES
302 -* **Allow create devices or assets**: YES
318 +* **Allows create devices or assets**: YES
303 303  
304 304  Click **Next** button.
305 305  
306 306  
323 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
307 307  
308 -[[image:add-integration-part-1.png||height="483" width="500"]]
309 309  
310 -
311 311  **Uplink data converter:**
312 312  
313 313  * Click on the **Select existing** button.
... ... @@ -316,10 +316,9 @@
316 316  Click **Next** button.
317 317  
318 318  
334 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
319 319  
320 -[[image:add-integration-part-2.png||height="484" width="500"]]
321 321  
322 -
323 323  **Downlink data converter:**
324 324  
325 325  Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
... ... @@ -335,16 +335,16 @@
335 335  
336 336  **Connection:**
337 337  
338 -* **Host**: Host URL (Eg, **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
339 -* **Port**: 8883 (the port number may differ based on your MQTT broker)
352 +* **Host**: Host URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
353 +* **Port**: 8883
340 340  * **Credentials type**: Basic
341 341  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
342 342  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
343 343  * **Enable SSL**: YES
344 -* **Topic**: # (the # symbol indicates that it filters all topics).
358 +* **Topic: device/a** (The topic can be anything; you can even use just the device name.)
345 345  * **QoS:** 0-At most once
346 346  
347 -[[image:add-integration-4.png||height="484" width="500"]]
361 +[[image:add-integration-connection.png||height="511" width="500"]]
348 348  
349 349  
350 350  Click on the **Advanced settings** button.
... ... @@ -374,59 +374,51 @@
374 374  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
375 375  
376 376  
391 +[[image:new-integration-pending.png]]
377 377  
378 -[[image:integrations-pending.png]]
379 379  
394 += 6. Verifying the receipt of data from virtual devices =
380 380  
381 -= 5. Verifying the receipt of data from virtual devices =
382 382  
397 +== 6.1 How does it work? ==
383 383  
384 -== 5.1 How does it work? ==
385 385  
386 -
387 387  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.
388 388  
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.
402 +The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
390 390  
404 +(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
391 391  
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 -
394 394  {{code language="none"}}
395 -{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}
407 +{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
396 396  {{/code}}
397 397  
410 +Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
398 398  
412 +
399 399  == 5.2 Sending messages ==
400 400  
401 401  
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.
416 +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.
403 403  
404 404  {{code language="none"}}
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}'
419 +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}'
406 406  {{/code}}
407 407  
408 -If the integration was performed without errors, a new device named **350693903995577 **is created in the **Devices **section.
422 +If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
409 409  
410 410  
411 -[[image:new-device-1.png]]
425 +[[image:integration-active.png]]
412 412  
413 413  
414 -The status of the integration also changes to '**Active**' after the first telemetry transmission.
415 415  
416 416  
417 -[[image:Screenshot 2025-04-21 122154.png]]
430 +== 6.3 Viewing messages ==
418 418  
419 419  
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 -
424 -== 5.3 Viewing messages ==
425 -
426 -
427 427  Go back to the **Integrations** page.
428 428  
429 -Click on the **MQTT integration** in the **Integrations** page to see its details.
435 +Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
430 430  
431 431  Click on the **Edit** button (//**pen icon**//).
432 432  
... ... @@ -439,34 +439,33 @@
439 439  Then click on the **Apply changes** (//**tick icon**//) button.
440 440  
441 441  
448 +[[image:Screenshot 2025-03-18 at 09.23.10.png]]
442 442  
443 -[[image:Screenshot 2025-04-21 122936.png||height="247" width="500"]]
444 444  
445 -
446 446  Now go to the **Events** tab.
447 447  
448 -Select the **Event type** as **Debug** from the dropdown list.
453 +Select the Event type as **Debug** from the dropdown list.
449 449  
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:
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.
451 451  
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}}
455 455  
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.
458 +[[image:Screenshot 2025-03-26 at 19.49.31.png]]
457 457  
458 458  
461 +
462 +
459 459  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
460 460  
461 461  
466 +[[image:Screenshot 2025-03-26 at 19.47.52.png]]
462 462  
463 -[[image:Screenshot 2025-04-21 122909.png]]
464 464  
465 465  
470 +
466 466  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.
467 467  
468 468  
469 -= 6. Creating a Dashboard =
474 += 7. Creating a Dashboard =
470 470  
471 471  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.
472 472  
... ... @@ -474,6 +474,11 @@
474 474  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.
475 475  
476 476  
482 +First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
483 +
484 +{{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}}
485 +
486 +
477 477  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
478 478  
479 479  
... ... @@ -509,41 +509,44 @@
509 509  
510 510  Configure the **Time series chart** widget as follows:
511 511  
512 -* **Datasource** - select **350693903995577 **you provisioned.
522 +* **Datasource** - select S31B-NB device you provisioned.
513 513  * **Series**:
514 514  ** **temperature** - you can see this key by default.
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.
525 +** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
517 517  * Click on the **Add** button.
518 518  
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}}
528 +[[image:timeseries-1.png||height="491" width="700"]]
522 522  
523 523  
531 +The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
524 524  
525 -[[image:Screenshot 2025-04-21 123647.png||height="466" width="700"]]
533 +Click the **Save** button to add the widget to the dashboard.
526 526  
527 527  
528 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
536 +[[image:timeseries-3.png||height="347" width="700"]]
529 529  
530 -Click the **Save** button to add the widget to the dashboard.
531 531  
539 +Now send the following MQTT messages from the terminal to simulate the data.
532 532  
533 -[[image:Screenshot 2025-04-21 124145.png||height="443" width="700"]]
534 534  
542 +{{code language="none"}}
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": 22, "humidity":70}'
535 535  
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.**
545 +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}'
537 537  
538 -**The chart will update with the values in real time, and you will see a live chart similar to this:**
547 +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}'
539 539  
549 +{{/code}}
540 540  
541 -[[image:Screenshot 2025-04-21 124054.png||height="441" width="700"]]
551 +The chart will update with the values in realtime, as shown in the below image.
542 542  
543 543  
544 -= 8. Configure Physical NB-IoT Sensor =
554 +[[image:timeseries-4.png||height="316" width="700"]]
545 545  
546 546  
557 += 8. Configure NB-IoT Sensor =
558 +
559 +
547 547  Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
548 548  
549 549  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
... ... @@ -552,8 +552,8 @@
552 552  **AT Commands**
553 553  
554 554  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
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: #**
568 +* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
569 +* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
557 557  * **AT+CLIENT=null**
558 558  * **AT+UNAME=<MQTT Username>**
559 559  * **AT+PWD=<MQTT Password>**
... ... @@ -562,7 +562,14 @@
562 562  Test your uplink by pressing the ACT button for 1 second.
563 563  
564 564  
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.
566 566  
579 +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**.
567 567  
581 +{{info}}
582 +The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
583 +{{/info}}
584 +
568 568  [[image:image-4.png]]
586 +
587 +
588 +
Screenshot 2025-03-31 at 06.51.15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -179.5 KB
Content
Screenshot 2025-04-21 122154.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -21.2 KB
Content
Screenshot 2025-04-21 122909.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -59.9 KB
Content
Screenshot 2025-04-21 122936.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
Screenshot 2025-04-21 123647.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
Screenshot 2025-04-21 124054.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -60.4 KB
Content
Screenshot 2025-04-21 124145.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -50.9 KB
Content
add-integration-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -63.1 KB
Content
add-integration-part-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -48.6 KB
Content
add-integration-part-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -47.7 KB
Content
data-converters-list.png
Size
... ... @@ -1,1 +1,1 @@
1 -19.0 KB
1 +212.2 KB
Content
debug-enabled.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -196.3 KB
Content
device-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -34.5 KB
Content
integration-active.png
Size
... ... @@ -1,1 +1,1 @@
1 -64.1 KB
1 +64.2 KB
Content
integration-added.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -196.2 KB
Content
integrations-pending.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -19.8 KB
Content
mqtt-uplink-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -75.3 KB
Content
new-device-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -34.7 KB
Content