Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 195.1
edited by Dilisi S
on 2025/03/28 00:38
Change comment: Mar 17 edits - part 3
To version 155.1
edited by Dilisi S
on 2025/03/17 00:27
Change comment: Mar 16 edits - part 1

Summary

Details

Page properties
Content
... ... @@ -67,6 +67,7 @@
67 67  [[image:thingsboard-6.png||height="244" width="500"]]
68 68  
69 69  
70 +(% class="wikigeneratedid" %)
70 70  == 2.2 HiveMQ Cloud ==
71 71  
72 72  === 2.2.1 HiveMQ Cloud ===
... ... @@ -164,142 +164,145 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
167 -= 3. Creating Devices (Optional) =
168 += 3. Data Converters =
168 168  
169 -{{info}}
170 -**The following procedure is optional. If you haven't created any device in ThingsBoard first, ThingsBoard will automatically create a device for you based on the integration settings (the device name defined in the uplink decoder) just after it receives the first uplink from your device.Type your information message here.**
171 -{{/info}}
172 172  
173 -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 +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.
174 174  
175 175  
176 -In the left navigation, click **Entities -> Devices**.
174 +== 3.1 Uplink ==
177 177  
178 -Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
179 179  
180 -In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
177 +In the left navigation, click **Integrations center**, and then click **Data converters**.
181 181  
182 -Click the **Add** button.
183 183  
184 -Skip the **connectivity testing** by clicking the **Close** button.
185 185  
186 -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.
181 +[[image:data-converters-list-empty.png]]
187 187  
188 188  
189 -= 4. Data Converters =
184 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
190 190  
191 191  
192 -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.
193 193  
188 +[[image:create-new-converter-menu.png||height="259" width="500"]]
194 194  
195 -== 4.1 Uplink ==
196 196  
191 +The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
197 197  
198 -In the left navigation, click **Integrations center**, and then click **Data converters**.
193 +Click on the **TBEL** button if not selected it by default. Delete the existing decoder function in the code editor. Now copy and paste the following decoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
199 199  
195 +{{code language="JavaScript"}}
196 +/** Decoder **/
200 200  
201 -[[image:data-converters-list-empty.png]]
198 +// decode payload to string
199 +var payloadStr = decodeToString(payload);
200 +var data = JSON.parse(payloadStr);
202 202  
202 +var deviceName = metadata.topic.split("/")[3];
203 +// decode payload to JSON
204 +var deviceType = 'sensor';
203 203  
204 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
206 +// Result object with device attributes/telemetry data
207 +var result = {
208 + deviceName: deviceName,
209 + deviceType: deviceType,
210 + attributes: {
211 + integrationName: metadata['integrationName'],
212 + },
213 + telemetry: {
214 + temperature: data.temperature,
215 + humidity: data.humidity,
216 + }
217 +};
205 205  
219 +/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
206 206  
221 +return result;
222 +{{/code}}
207 207  
208 -[[image:create-new-converter-menu.png||height="259" width="500"]]
209 209  
225 +Click on the **Add** button.
210 210  
211 -The **Add data converter** window will appear.
212 212  
213 -Let's create an uplink data converter for the device named '**Device A**'. Name it ‘**MQTT Uplink Converter - Device A**’ and select the Type as **Uplink**.
214 214  
215 -Click on the **TBEL** button if it has not been selected by default.
229 +[[image:add-uplink-data-converter.png||height="529" width="500"]]
216 216  
217 -Modify the default TBEL function to match with your device as described below:
218 218  
232 +You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
219 219  
220 -* Uncomment** line 11**:
234 +[[image:data-converter-list-showing-uplink-dc.png]]
221 221  
222 -//var data = decodeToJson(payload)//
223 223  
224 224  
225 -* **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.
226 -* From **line 38**: Modify the telemetry section to allow parsed data to be assigned to the fields.
238 +== 3.2 Downlink ==
227 227  
228 -//telemetry: {
229 - temperature: data.temperature,
230 - humidity: data.humidity,
231 - rawData: payloadStr
232 - }//
233 233  
241 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
234 234  
235 -The modified uplink decoder function to match with **Device A** is shown below.
236 236  
244 +[[image:create-new-converter-menu.png||width="500"]]
245 +
246 +
247 +
248 +The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
249 +
250 +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.
251 +
252 +
237 237  {{code language="JavaScript"}}
238 -// Decode an uplink message from a buffer
239 -// payload - array of bytes
240 -// metadata - key/value object
254 +// Encode downlink data from incoming Rule Engine message
241 241  
242 -/** Decoder **/
256 +// msg - JSON message payload downlink message json
257 +// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
258 +// metadata - list of key-value pairs with additional data about the message
259 +// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
243 243  
244 -// decode payload to string
245 -var payloadStr = decodeToString(payload);
261 +/** Encoder **/
246 246  
247 -// decode payload to JSON
248 -var data = decodeToJson(payload);
263 +var data = {};
249 249  
250 -var deviceName = 'Device A';
251 -var deviceType = 'thermostat';
252 -var customerName = 'Customer C';
253 -var groupName = 'thermostat devices';
254 -var manufacturer = 'Example corporation';
255 -// use assetName and assetType instead of deviceName and deviceType
256 -// to automatically create assets instead of devices.
257 -// var assetName = 'Asset A';
258 -// var assetType = 'building';
265 +// Process data from incoming message and metadata
259 259  
260 -// Result object with device/asset attributes/telemetry data
267 +data.tempFreq = msg.temperatureUploadFrequency;
268 +data.humFreq = msg.humidityUploadFrequency;
269 +
270 +data.devSerialNumber = metadata['ss_serialNumber'];
271 +
272 +// Result object with encoded downlink payload
261 261  var result = {
262 -// Use deviceName and deviceType or assetName and assetType, but not both.
263 - deviceName: deviceName,
264 - deviceType: deviceType,
265 -// assetName: assetName,
266 -// assetType: assetType,
267 -// customerName: customerName,
268 - groupName: groupName,
269 - attributes: {
270 - model: 'Model A',
271 - serialNumber: 'SN111',
272 - integrationName: metadata['integrationName'],
273 - manufacturer: manufacturer
274 - },
275 - telemetry: {
276 - temperature: data.temperature,
277 - humidity: data.humidity,
278 - rawData: payloadStr
279 - }
280 -};
281 281  
282 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
275 + // downlink data content type: JSON, TEXT or BINARY (base64 format)
276 + contentType: "JSON",
283 283  
278 + // downlink data
279 + data: JSON.stringify(data),
280 +
281 + // Optional metadata object presented in key/value format
282 + metadata: {
283 + topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
284 + }
285 +
286 +};
287 +
284 284  return result;
285 285  {{/code}}
286 286  
287 287  
288 -Once you modify the decoder function, click on the **Add** button.
292 +Click on the **Add** button.
289 289  
290 290  
291 291  
292 -[[image:ul-data-converter-device-a.png||height="524" width="500"]]
296 +[[image:add-downlink-data-converter.png||height="529" width="500"]]
293 293  
294 294  
295 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
299 +You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
296 296  
297 297  
298 -[[image:ul-data-converter-added.png||height="257"]]
302 +[[image:data-converters-list.png]]
299 299  
300 300  
301 301  
302 -= 5. Add Integration =
306 += 4. Add Integration =
303 303  
304 304  
305 305  In the left navigation, click **Integrations center**, and then click **Integrations**.
... ... @@ -319,7 +319,7 @@
319 319  **Basic settings:**
320 320  
321 321  * **Integration type**: MQTT
322 -* **Name**: MQTT integration - Device A
326 +* **Name**: MQTT integration NB/CB
323 323  * **Enable integration**: YES
324 324  * **Allows create devices or assets**: YES
325 325  
... ... @@ -326,11 +326,10 @@
326 326  Click **Next** button.
327 327  
328 328  
329 -[[image:add-integration-basic-settings.png||height="504" width="500"]]
330 330  
334 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
331 331  
332 332  
333 -
334 334  **Uplink data converter:**
335 335  
336 336  * Click on the **Select existing** button.
... ... @@ -339,35 +339,34 @@
339 339  Click **Next** button.
340 340  
341 341  
342 -[[image:add-integration-ul-data-converter.png||height="505" width="500"]]
343 343  
346 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
344 344  
345 345  
346 346  **Downlink data converter:**
347 347  
348 -Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
351 +* Click on the **Select existing** button.
352 +* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
349 349  
350 -* Click on the **Skip **button in the Downlink data converter section.
354 +Click **Next** button.
351 351  
352 -Click **Skip** button.
353 353  
354 354  
355 -[[image:integration-dl-skip.png||height="511" width="500"]]
358 +[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
356 356  
357 357  
358 -
359 359  **Connection:**
360 360  
361 -* **Host**: Host URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
363 +* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
362 362  * **Port**: 8883
363 -* **Credentials type**: Basic
365 +* **Credentials**: Basic
366 +* **Enable SSL**: YES
364 364  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
365 365  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
366 -* **Enable SSL**: YES
367 -* **Topic: device/a** (The topic can be anything; you can even use just the device name.)
369 +* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
368 368  * **QoS:** 0-At most once
369 369  
370 -[[image:add-integartion-connection.png||height="505" width="500"]]
372 +[[image:add-integration-connection.png||height="511" width="500"]]
371 371  
372 372  
373 373  Click on the **Advanced settings** button.
... ... @@ -397,36 +397,48 @@
397 397  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
398 398  
399 399  
400 -[[image:integration-added.png]]
401 401  
403 +[[image:new-integration-pending.png]]
402 402  
403 403  
404 -= 6. Verifying the receipt of data from virtual devices =
406 += 5. Verifying the receipt of data from virtual devices =
405 405  
406 406  
407 -== 6.1 How does it work? ==
409 +== 5.1 How does it work? ==
408 408  
409 409  
410 410  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.
411 411  
412 -The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
414 +The Mosquitto client publishes messages on the topic v1/devices/[device_name]/telemetry. The [device_name]placeholder can be replaced with any device name, for example, 'S31B-NB'. Then, the MQTT topic would be v1/devices/S31B-NB/telemetry.
413 413  
414 -(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
416 +On the ThingsBoard side, we configure the MQTT topic subscription as v1/devices/+/telemetry. The + wildcard represents any device name and allows ThingsBoard to automatically create (provision) a device with that name, such as S31B-NB, for example.
415 415  
418 +
419 +**The new device is created the first time the MQTT topic is received. For subsequent MQTT topics with the same device name, no duplicate devices will be created.**
420 +
421 +
422 +For example, if you send two MQTT messages with different device names in the topic:
423 +
424 +1. v1/devices/**S31B-NB**/telemetry
425 +1. v1/devices/**LDS25-NB**/telemetry
426 +
427 +ThingsBoard will create two devices named **S31B-NB** and **LDS25-NB** in the **//Devices//** section.
428 +
429 +
430 +The MQTT payload format is as follows, which is common for all ~-~-NB and ~-~-CB series devices:
431 +
416 416  {{code language="none"}}
417 -{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
433 +{"temperature":10.4, "humidity":85}
418 418  {{/code}}
419 419  
420 -Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
421 421  
422 -
423 423  == 5.2 Sending messages ==
424 424  
425 425  
426 -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.
440 +On the terminal, issue the following MQTT command which simulates the device S31B-NB. The message payload contains the fields temperature and humidity, which hold the values 10.4 and 85, respectively. This payload is also (technically) known as telemetry.
427 427  
428 428  {{code language="none"}}
429 -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}'
443 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":10.4, "humidity":85}'
430 430  {{/code}}
431 431  
432 432  If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
... ... @@ -435,59 +435,43 @@
435 435  [[image:integration-active.png]]
436 436  
437 437  
438 -== 6.3 Viewing messages ==
452 +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**.
439 439  
440 440  
441 -Go back to the **Integrations** page.
455 +[[image:device-provision-1.png]]
442 442  
443 -Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
444 444  
445 -Click on the **Edit** button (//**pen icon**//).
458 +Click on the device S31B-NB on the devices list to see its details.
446 446  
447 -Click on the **Disabled** button in the upper-right corner.
460 +Then go to the **Latest telemetry** tab.
448 448  
449 -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.
462 +You can see the fields temperature and humidity with the values you previously sent using the MQTT message.
450 450  
451 -Click on the **Apply** button.
452 452  
453 -Then click on the **Apply changes** (//**tick icon**//) button.
465 +[[image:telemetry-1.png]]
454 454  
455 455  
456 -[[image:debug-enabled.png||height="301" width="700"]]
468 +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//.
457 457  
458 458  
471 +[[image:telemetry-2.png]]
459 459  
460 460  
461 -Now go to the **Events** tab.
474 +Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
462 462  
463 -Select the **Event type** as **Debug** from the dropdown list.
464 464  
465 -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:
466 -
467 467  {{code language="none"}}
468 -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}'
478 +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}'
469 469  {{/code}}
470 470  
471 -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.
481 +Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
472 472  
473 473  
474 -[[image:Screenshot 2025-03-26 at 19.49.31.png]]
484 +[[image:device-provision-2.png]]
475 475  
476 476  
487 += 6. Creating a Dashboard =
477 477  
478 -Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
479 -
480 -
481 -[[image:Screenshot 2025-03-26 at 19.47.52.png]]
482 -
483 -
484 -
485 -
486 -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.
487 -
488 -
489 -= 7. Creating a Dashboard =
490 -
491 491  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.
492 492  
493 493  
... ... @@ -494,11 +494,6 @@
494 494  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.
495 495  
496 496  
497 -First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
498 -
499 -{{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}}
500 -
501 -
502 502  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
503 503  
504 504  
... ... @@ -555,11 +555,11 @@
555 555  
556 556  
557 557  {{code language="none"}}
558 -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}'
551 +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}'
559 559  
560 -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}'
553 +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}'
561 561  
562 -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}'
555 +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}'
563 563  
564 564  {{/code}}
565 565  
... ... @@ -569,10 +569,10 @@
569 569  [[image:timeseries-4.png||height="316" width="700"]]
570 570  
571 571  
572 -= 8. Configure NB-IoT Sensor =
565 += 7. Configure NB-IoT Sensor =
573 573  
574 574  
575 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
568 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
576 576  
577 577  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
578 578  
... ... @@ -580,8 +580,8 @@
580 580  **AT Commands**
581 581  
582 582  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
583 -* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
584 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
576 +* **AT+SUBTOPIC=<MQTT topic>**
577 +* **AT+PUBTOPIC=<MQTT topic>**
585 585  * **AT+CLIENT=null**
586 586  * **AT+UNAME=<MQTT Username>**
587 587  * **AT+PWD=<MQTT Password>**
... ... @@ -588,13 +588,3 @@
588 588  * **AT+SERVADDR=<Broker address, Port>**
589 589  
590 590  Test your uplink by pressing the ACT button for 1 second.
591 -
592 -
593 -
594 -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**.
595 -
596 -{{info}}
597 -The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
598 -{{/info}}
599 -
600 -[[image:image-4.png]]
Screenshot 2025-03-16 at 18.38.59.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -221.2 KB
Content
Screenshot 2025-03-16 at 18.39.12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -211.9 KB
Content
Screenshot 2025-03-18 at 09.23.10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -78.7 KB
Content
Screenshot 2025-03-26 at 18.15.08.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -92.2 KB
Content
Screenshot 2025-03-26 at 19.47.52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -168.4 KB
Content
Screenshot 2025-03-26 at 19.49.31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -133.0 KB
Content
add-integartion-connection.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -110.3 KB
Content
add-integartion-connetcion.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -146.0 KB
Content
add-integration-basic-settings.png
Size
... ... @@ -1,1 +1,1 @@
1 -123.8 KB
1 +122.5 KB
Content
add-integration-connection.png
Size
... ... @@ -1,1 +1,1 @@
1 -158.1 KB
1 +124.4 KB
Content
add-integration-ul-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -121.2 KB
Content
debug-enabled.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -196.3 KB
Content
image-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -96.0 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
integration-dl-skip.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -105.5 KB
Content
mqtt-uplink.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -175.1 KB
Content
new-device.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
ul-data-converter-added.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -189.4 KB
Content
ul-data-converter-device-a.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -168.3 KB
Content