Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 171.1
edited by Dilisi S
on 2025/03/20 15:24
Change comment: Uploaded new attachment "integration-dl-skip.png", version {1}
To version 16.1
edited by Dilisi S
on 2025/03/03 02:45
Change comment: Mar 2 edits - part 2

Summary

Details

Page properties
Content
... ... @@ -6,193 +6,47 @@
6 6  Draft Document
7 7  {{/warning}}
8 8  
9 += Introduction =
9 9  
11 +This document guides you on integrating Dragino -NB and -CB series devices with ThingsBoard. For this guide, we use ThingsBoard Cloud, which is one of the ThingsBoard versions that allows you to try it for free.
10 10  
11 11  
12 -= 1. Introduction =
14 += Add New Device =
13 13  
16 +In the left navigation, click **Entities** and then click **Devices**.
14 14  
15 -This document guides you on integrating Dragino **-NB** and **-CB** series devices data with ThingsBoard. For this guide, we use ThingsBoard Cloud, which is one of the ThingsBoard versions that allows you to try it for free.
16 16  
17 -The **NB series** devices end with the suffix **-NB**, and the **CB series** devices end with the suffix **-CB**. For example, **S31B-NB** is an **NB device**, and **S31-CB** is a **CB device**.
19 +[[image:ThingsBoard-Device.png]]
18 18  
19 19  
20 -= 2. Prerequisites =
22 +On the ‘**Devices**’ page, click on the ‘**+**’ button, and then click on the ‘**Add new device**’ from the dropdown menu.
21 21  
22 -To complete this tutorial, you need to have the following:
23 23  
24 -* ThingsBoard cloud account
25 -* MQTT Broker (public or private) such as,
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 -** [[lns1.thingseye.io>>http://lns1.thingseye.io/]] - This is Dragino's MQTT broker, which requires a CA certificate to use.
25 +[[image:ThingsBoard-add-new-device.png||height="279" width="500"]]
29 29  
30 -== 2.1 ThingsBoard Cloud ==
31 31  
32 32  
33 -Go to [[https:~~/~~/thingsboard.io/>>https://thingsboard.io/]]
29 += Data Converters =
34 34  
35 -Click on the **Try it now**.
36 36  
32 +== Uplink ==
37 37  
38 -[[image:thingsboard-1.png]]
34 +In the left navigation, click ‘Integrations center’, and then click ‘Data converters’.
39 39  
40 40  
41 -Select either the **North America** or **Europe** region. Here, we use the Europe region.
37 +[[image:ThingsBoard-Data-Converters.png]]
42 42  
43 -[[image:thingsboard-2.png]]
44 44  
40 +On the ‘Data converters’ page, click on the ‘+’ button, and then click on the ‘Create new converter’ from the dropdown menu.
45 45  
46 -You can sign up with your **Google**, **GitHub**, **Facebook**, or **Apple** account. If not you can create an account with providing your **name**, **email address** and a **password**.
47 47  
48 -Click on the **Sign up** button.
43 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
49 49  
50 -[[image:thingsboard-3.png||height="651" width="500"]]
51 51  
46 +The ‘Add data converter’ window will appear. Name it ‘**UDP Uplink Converter NB/CB**’ and select the Type as ‘Uplink’.
52 52  
53 -You will be navigated to the following page.
48 +Click on the ‘JavaScript’ button. Now copy and paste the following script to the ‘Decoder function’ section:
54 54  
55 -[[image:thingsboard-5.png||height="109" width="500"]]
56 -
57 -
58 -simultaneously, you will receive an email to confirm your email address. Click on the **Activate Your Account** button.
59 -
60 -
61 -[[image:thingsboard-4.png||height="249" width="500"]]
62 -
63 -
64 -Now losing to the account using your credentials:
65 -
66 -
67 -[[image:thingsboard-6.png||height="244" width="500"]]
68 -
69 -
70 -== 2.2 HiveMQ Cloud ==
71 -
72 -=== 2.2.1 HiveMQ Cloud ===
73 -
74 -
75 -Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
76 -
77 -Click on the **Start Free** button.
78 -
79 -[[image:hivwmq-1.png]]
80 -
81 -
82 -Click on the **Sign Up FREE Now** button in the **HIVEMQ CLOUD** section.
83 -
84 -[[image:hivemq-2.png]]
85 -
86 -
87 -Click on the **Sign Up** button.
88 -
89 -You can sign up with HiveMQ using your **GitHub**, **Google**, or **LinkedIn** account.
90 -
91 -If not, provide your **email address** and a **password** to create an account by clicking on the **Sign Up** button.
92 -
93 -
94 -[[image:hivemq-3.png]]
95 -
96 -
97 -You will receive an email to verify your email address. Click on the **Confirm my account** button.
98 -
99 -
100 -[[image:hivemq-4.jpg||height="889" width="400"]]
101 -
102 -
103 -You will be redirected to a page asking you to complete your profile. Once done, click the **Continue** button.
104 -
105 -
106 -[[image:hivemq-5.png||height="655" width="700"]]
107 -
108 -
109 -Select the CloudMQ Cloud plan you need. For testing purposes, select the **Serverless FREE** plan by clicking on the **Create Serverless Cluster** button.
110 -
111 -
112 -[[image:hivemq-6.png]]
113 -
114 -
115 -You will be navigated to the **Your Clusters** page. Click on the **Manage Cluster** button.
116 -
117 -[[image:hivemq-7.png]]
118 -
119 -
120 -In your cluster page, you can find some useful parameters you need to create a MQTT connection.
121 -
122 -**URL**: This is the host name. Click on the copy button to copy it.
123 -
124 -**Port**: 8883
125 -
126 -
127 -Click on the **Getting Started** tab to setup the username and the password as the connection credentials.
128 -
129 -
130 -[[image:hivemq-8.png]]
131 -
132 -
133 -In the '**Create Connection Credentials**' section, provide a **username** and **password**, then click the **Add** button.
134 -
135 -
136 -[[image:hivemq-9.png]]
137 -
138 -
139 -
140 -If everything is successful, you will see the following message.
141 -
142 -
143 -[[image:hivemq-10.png||height="206" width="500"]]
144 -
145 -
146 -You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
147 -
148 -
149 -=== 2.2.2 emqx ===
150 -
151 -
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.
153 -
154 -
155 -[[image:emqx.png||height="420" width="500"]]
156 -
157 -
158 -=== 2.2.3 Ins1.thingseye.io ===
159 -
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 -
162 -If customers need to use this MQTT connection with ThingsBoard, they need to contact the TE team to obtain three license files.
163 -
164 -[[image:ins1.png||height="310" width="500"]]
165 -
166 -
167 -= 3. Data Converters =
168 -
169 -
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 -
172 -
173 -== 3.1 Uplink ==
174 -
175 -
176 -In the left navigation, click **Integrations center**, and then click **Data converters**.
177 -
178 -
179 -[[image:data-converters-list-empty.png]]
180 -
181 -
182 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
183 -
184 -
185 -
186 -[[image:create-new-converter-menu.png||height="259" width="500"]]
187 -
188 -
189 -The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
190 -
191 -Click on the **JavaScript** button.
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.
194 -
195 -
196 196  {{code language="JavaScript"}}
197 197  //Version: 0.1
198 198  // decode payload to string
... ... @@ -313,310 +313,138 @@
313 313  }
314 314  
315 315  return result;
170 +
316 316  {{/code}}
317 317  
173 +Click on the ‘Add’ button.
318 318  
319 -Click on the **Add** button.
320 320  
176 +[[image:ThingsBoard-add-data-converter-uplink.png||width="500"]]
321 321  
322 -[[image:mqtt-uplink.png||width="500"]]
323 323  
179 +The uplink data converter is added to ThingsBoard and appears on the ‘Data Converters’ page
324 324  
325 325  
326 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
182 +== Downlink ==
327 327  
184 +On the ‘Data converters’ page, click on the ‘+’ button, and then click on the ‘Create new converter’ from the dropdown menu.
328 328  
329 -[[image:data-converter-list-showing-uplink-dc.png]]
330 330  
187 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
331 331  
332 332  
190 +The ‘**Add data converter**’ window will appear. Name it ‘**UDP Downlink Converter NB/CB**’ and select the Type as ‘**Downlink**’.
333 333  
192 +Click on the ‘**JavaScript**’ button. Now copy and paste the following script to the ‘**Encoder function**’ section:
334 334  
335 335  
336 -= 4. Add Integration =
195 +{{code language="JavaScript"}}
196 +function hexToBase64(hexString) {
197 + // 将16进制字符串两个字符转换为一个字节
198 + var bytes = hexString.match(/.{2}/g);
199 + // 对每个字节进行解析，并转换为对应的字符
200 + var binaryString = bytes.map(function(byte) {
201 + return String.fromCharCode(parseInt(byte, 16));
202 + }).join('');
203 +
204 + // 使用btoa进行base64编码
205 + return btoa(binaryString);
206 +}
337 337  
208 +// Result object with encoded downlink payload
209 +var result = {
210 + // downlink data content type: JSON, TEXT or BINARY (base64 format)
211 + contentType: "BINARY",
338 338  
339 -In the left navigation, click **Integrations center**, and then click **Integrations**.
213 + // downlink data
214 + data:hexToBase64(metadata.shared_value)
340 340  
216 + // Optional metadata object presented in key/value format
217 + //metadata: {}
341 341  
342 -[[image:integrations-list-empty.png]]
219 +};
343 343  
221 +return result;
222 +{{/code}}
344 344  
345 -On the **Integrations** page, click on the '**+**' button.
346 346  
225 +Click on the **Add** button.
347 347  
348 -The **Add integration** window appears.
349 349  
350 -In the **Add integration** window, configure the following settings:
228 +[[image:ThingsBoard-add-data-converter-downlink.png||height="532" width="500"]]
351 351  
352 352  
353 -**Basic settings:**
231 += Add Integration =
354 354  
355 -* **Integration type**: MQTT
356 -* **Name**: MQTT integration NB/CB
357 -* **Enable integration**: YES
358 -* **Allows create devices or assets**: YES
233 +In the left navigation, click ‘Integrations center’, and then click ‘Integrations’.
359 359  
360 -Click **Next** button.
235 +On the ‘Integrations’ page, click on the “+” button.
361 361  
362 362  
363 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
238 +[[image:ThingsBoard-add-integration.png]]
364 364  
365 365  
366 -**Uplink data converter:**
241 +The ‘Add integration’ window appears.
367 367  
368 -* Click on the **Select existing** button.
369 -* **Uplink data converter**: Select **MQTT Uplink Converter NB/CB **from the dropdown list.
243 +In the Add Integration window, configure the following settings:
370 370  
371 -Click **Next** button.
245 +**Basic settings:**
372 372  
247 +* **Integration type**: UDP
248 +* **Name**: UDP Integration NB/CB
373 373  
374 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
375 -
376 -
377 -**Downlink data converter:**
378 -
379 -* Click on the **Select existing** button.
380 -* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
381 -
382 382  Click **Next** button.
383 383  
384 384  
385 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
253 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
386 386  
387 387  
388 -**Connection:**
256 +**Uplink data converter:**
389 389  
390 -* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
391 -* **Port**: 8883
392 -* **Credentials**: Basic
393 -* **Enable SSL**: YES
394 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
395 -* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
396 -* **Topic: v1/devices/+/telemetry** (the + replaces any 'device name' will create a device in the Entities -> Devices)
397 -* **QoS:** 0-At most once
258 +* Click on the ‘**Select existing**’ button.
259 +* Uplink data converter: Select ‘**UDP Uplink Converter NB/CB**’ from the dropdown list.
398 398  
399 -[[image:add-integration-connection.png||height="511" width="500"]]
261 +Click **Next** button.
400 400  
401 401  
402 -Click on the **Advanced settings** button.
264 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
403 403  
404 -* **Clean session:** YES
405 -* **Retained**: YES
406 406  
407 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
267 +**Downlink data converter:**
408 408  
269 +* Click on the ‘**Select existing**’ button.
270 +* Downlink data converter: Select ‘**UDP Downlink Converter NB/CB**’ from the dropdown list.
409 409  
410 -Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
411 411  
273 +Click **Next** button.
412 412  
413 -[[image:check-connection.png||height="83" width="300"]]
414 414  
276 +[[image:add-integration-downlink-data-converter.png||height="512" width="500"]]
415 415  
416 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
417 417  
279 +**Connection:**
418 418  
419 -[[image:connection-success.png||height="511" width="500"]]
281 +**Port**: 11582
420 420  
283 +**Size of the buffer for inbound socket (in KB)**: 64
421 421  
422 -Click on the **Add** button.
285 +**Cache Size**: 10000000
423 423  
424 -You should see that the newly added integration is listed on the **Integrations** page.
287 +**Cache time to live in minutes**: 1440
425 425  
426 -Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
427 427  
290 +Copy the two keys, **Integration key** and **Integration secret** into a text editor, as you will need them in the section ‘xxxxx’.
428 428  
429 -
430 -[[image:new-integration-pending.png]]
431 -
432 -
433 -= 5. Verifying the receipt of data from virtual devices =
434 -
435 -
436 -== 5.1 How does it work? ==
437 -
438 -
439 -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.
440 -
441 -The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
442 -
443 -(% 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.
444 -
445 -{{code language="none"}}
446 -{"IMEI": "S31B-NB", "temperature": 27, ......}
447 -{{/code}}
448 -
449 -Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
450 -
451 -
452 -== 5.2 Sending messages ==
453 -
454 -
455 -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.
456 -
457 -{{code language="none"}}
458 -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}'
459 -{{/code}}
460 -
461 -If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
462 -
463 -
464 -[[image:integration-active.png]]
465 -
466 -
467 -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**.
468 -
469 -
470 -[[image:new-device.png]]
471 -
472 -
473 -== 5.3 Viewing messages ==
474 -
475 -
476 -Go back to the **Integrations** page.
477 -
478 -Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
479 -
480 -Click on the **Edit** button (//**pen icon**//).
481 -
482 -Click on the **Disabled** button in the upper-right corner.
483 -
484 -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.
485 -
486 -Click on the **Apply** button.
487 -
488 -Then click on the **Apply changes** (//**tick icon**//) button.
489 -
490 -
491 -[[image:Screenshot 2025-03-18 at 09.23.10.png]]
492 -
493 -
494 -Now go to the **Events** tab.
495 -
496 -Select the Event type as **Debug** from the dropdown list.
497 -
498 -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.
499 -
500 -
501 -[[image:Screenshot 2025-03-16 at 18.38.59.png]]
502 -
503 -
504 -Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
505 -
506 -
507 -[[image:Screenshot 2025-03-16 at 18.39.12.png]]
508 -
509 -
510 -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.
511 -
512 -
513 -= 6. Creating a Dashboard =
514 -
515 -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.
516 -
517 -
518 -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.
519 -
520 -
521 -First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
522 -
523 -{{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}}
524 -
525 -
526 -In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
527 -
528 -
529 -[[image:dashboard-1.png]]
530 -
531 -
532 -In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
533 -
534 534  Click on the **Add** button.
535 535  
536 536  
537 -[[image:dashboard-2.png||height="526" width="500"]]
295 +[[image:add-integration-connection.png||height="511" width="500"]]
538 538  
539 539  
540 -Click on the **Add widget / Add new widget** button.
541 541  
299 += Verifying the receipt of data from the device =
542 542  
543 -[[image:dashboard-3.png]]
301 +Connect **S31B-NB** to transfer information. If the integration was performed without errors, after the transmission of the first telemetry, a new device with the name “xxxxx” will appear in the Devices → All. Also, you can verify the input and output data, respectively, before and after conversion in Data converters → UDP Uplink Converter NB/CB → Events.
544 544  
545 545  
546 -In the **Select widgets bundle** window, click **Charts**.
547 -
548 -
549 -[[image:dashboard-4.png||height="537" width="700"]]
550 -
551 -
552 -
553 -In the **Charts: select widget** window, click **Time series chart**.
554 -
555 -
556 -[[image:dashboard-5.png||height="525" width="700"]]
557 -
558 -
559 -Configure the **Time series chart** widget as follows:
560 -
561 -* **Datasource** - select S31B-NB device you provisioned.
562 -* **Series**:
563 -** **temperature** - you can see this key by default.
564 -** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
565 -* Click on the **Add** button.
566 -
567 -[[image:timeseries-1.png||height="491" width="700"]]
568 -
569 -
570 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
571 -
572 -Click the **Save** button to add the widget to the dashboard.
573 -
574 -
575 -[[image:timeseries-3.png||height="347" width="700"]]
576 -
577 -
578 -Now send the following MQTT messages from the terminal to simulate the data.
579 -
580 -
581 -{{code language="none"}}
582 -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}'
583 -
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": 27, "humidity":72}'
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": 19, "humidity":80}'
587 -
588 -{{/code}}
589 -
590 -The chart will update with the values in realtime, as shown in the below image.
591 -
592 -
593 -[[image:timeseries-4.png||height="316" width="700"]]
594 -
595 -
596 -= 7. Configure NB-IoT Sensor =
597 -
598 -
599 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
600 -
601 -First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
602 -
603 -
604 -**AT Commands**
605 -
606 -* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
607 -* **AT+SUBTOPIC=<MQTT subscribe topic> **
608 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
609 -* **AT+CLIENT=null**
610 -* **AT+UNAME=<MQTT Username>**
611 -* **AT+PWD=<MQTT Password>**
612 -* **AT+SERVADDR=<Broker address, Port>**
613 -
614 -Test your uplink by pressing the ACT button for 1 second.
615 -
616 -
617 -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**.
618 -
619 -[[image:image-4.png]]
620 -
621 -
622 622  
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 -277.0 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
add-downlink-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -175.2 KB
Content
add-integration-connection-advanced-settings.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -155.2 KB
Content
add-integration-connection.png
Size
... ... @@ -1,1 +1,1 @@
1 -153.2 KB
1 +124.4 KB
Content
add-uplink-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -174.1 KB
Content
check-connection.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -14.7 KB
Content
connection-success.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -90.0 KB
Content
create-new-converter-menu.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -31.5 KB
Content
dashboard-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -271.1 KB
Content
dashboard-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -112.2 KB
Content
dashboard-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -141.3 KB
Content
dashboard-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -803.7 KB
Content
dashboard-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -476.1 KB
Content
data-converter-list-showing-uplink-dc.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -194.9 KB
Content
data-converters-list-empty.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -260.7 KB
Content
data-converters-list.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -212.2 KB
Content
device-provision-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -265.7 KB
Content
device-provision-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -213.9 KB
Content
emqx.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -39.1 KB
Content
hivemq-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -82.7 KB
Content
hivemq-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -300.7 KB
Content
hivemq-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -535.2 KB
Content
hivemq-4.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -309.8 KB
Content
hivemq-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -115.0 KB
Content
hivemq-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -321.0 KB
Content
hivemq-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -203.5 KB
Content
hivemq-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -268.7 KB
Content
hivemq-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -303.7 KB
Content
hivwmq-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -380.3 KB
Content
image-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -96.0 KB
Content
ins1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -28.8 KB
Content
integration-active.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -64.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
integrations-list-empty.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -264.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
new-integration-pending.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -199.7 KB
Content
telemetry-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -191.9 KB
Content
telemetry-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -185.1 KB
Content
thingsboard-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -1.9 MB
Content
thingsboard-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -901.1 KB
Content
thingsboard-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -146.3 KB
Content
thingsboard-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -122.1 KB
Content
thingsboard-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -106.7 KB
Content
thingsboard-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -119.3 KB
Content
timeseries-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -179.1 KB
Content
timeseries-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -174.2 KB
Content
timeseries-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -159.0 KB
Content
ThingsBoard-Data-Converters.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +100.3 KB
Content
ThingsBoard-Device.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +225.5 KB
Content
ThingsBoard-add-data-converter-downlink.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-add-data-converter-uplink.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-add-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-add-integration.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-add-new-device.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +89.7 KB
Content
ThingsBoard-new-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +100.3 KB
Content