Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 159.1
edited by Dilisi S
on 2025/03/18 03:49
Change comment: There is no comment for this version
To version 53.1
edited by Dilisi S
on 2025/03/06 03:44
Change comment: Uploaded new attachment "new-device-device-details.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -6,193 +6,51 @@
6 6  Draft Document
7 7  {{/warning}}
8 8  
9 += Introduction =
9 9  
10 -
11 -
12 -= 1. Introduction =
13 -
14 -
15 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 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**.
18 18  
19 19  
20 -= 2. Prerequisites =
16 += Add New Device =
21 21  
22 -To complete this tutorial, you need to have the following:
18 +In the left navigation, click **Entities** and then click **Devices**.
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.
29 29  
30 -== 2.1 ThingsBoard Cloud ==
21 +[[image:ThingsBoard-Device.png]]
31 31  
32 32  
33 -Go to [[https:~~/~~/thingsboard.io/>>https://thingsboard.io/]]
24 +On the **Devices **page, click on the ‘**+**’ button, and then click on the **Add new device **from the dropdown menu.
34 34  
35 -Click on the **Try it now**.
36 36  
27 +[[image:ThingsBoard-add-new-device.png||height="279" width="500"]]
37 37  
38 -[[image:thingsboard-1.png]]
39 39  
40 40  
41 -Select either the **North America** or **Europe** region. Here, we use the Europe region.
31 += Data Converters =
42 42  
43 -[[image:thingsboard-2.png]]
44 -
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 -
48 -Click on the **Sign up** button.
49 -
50 -[[image:thingsboard-3.png||height="651" width="500"]]
51 -
52 -
53 -You will be navigated to the following page.
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 170  In **ThingsBoard**, **Data Converters** are components used to transform incoming or outgoing data between different formats, typically to convert raw telemetry data from devices into a structured format that ThingsBoard can understand, or vice versa.
171 171  
172 172  
173 -== 3.1 Uplink ==
36 +== Uplink ==
174 174  
175 -
176 176  In the left navigation, click **Integrations center**, and then click **Data converters**.
177 177  
178 178  
179 -[[image:data-converters-list-empty.png]]
41 +[[image:data-converter-list-page.png]]
180 180  
181 181  
182 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
44 +On the **Data converters** page, click on the ‘+’ button, and then click on the **Create new converter** from the dropdown menu.
183 183  
184 184  
47 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
185 185  
186 -[[image:create-new-converter-menu.png||height="259" width="500"]]
187 187  
188 -
189 189  The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
190 190  
191 -Click on the **JavaScript** button.
52 +Click on the **JavaScript** button. Now copy and paste the following JavaScript to the **Decoder function** section. This decoder function is valid for both NB and CB series devices.
192 192  
193 -Delete the default decoder function in the code editor. Now copy and paste the following decoder function written in **JavaScript** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
194 -
195 -
196 196  {{code language="JavaScript"}}
197 197  //Version: 0.1
198 198  // decode payload to string
... ... @@ -313,69 +313,58 @@
313 313  }
314 314  
315 315  return result;
174 +
316 316  {{/code}}
317 317  
318 -
319 319  Click on the **Add** button.
320 320  
321 321  
322 -[[image:mqtt-uplink.png||width="500"]]
180 +[[image:uplink-data-converter.png||height="529" width="500"]]
323 323  
324 324  
325 325  
326 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
184 +You should see that the newly added **uplink data converter** is listed on the **Data Converters** page.
327 327  
328 328  
329 329  [[image:data-converter-list-showing-uplink-dc.png]]
330 330  
331 331  
332 -== 3.2 Downlink ==
190 +== Downlink ==
333 333  
334 -
335 335  On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
336 336  
337 337  
338 -[[image:create-new-converter-menu.png||width="500"]]
195 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
339 339  
340 340  
341 -
342 342  The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
343 343  
344 -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.
200 +Click on the **JavaScript** button. Now copy and paste the following JavaScript to the **Encoder function **section. This encoder function is valid for both NB and CB series devices.
345 345  
346 346  
347 347  {{code language="JavaScript"}}
348 -// Encode downlink data from incoming Rule Engine message
204 +function hexToBase64(hexString) {
205 + // 将16进制字符串两个字符转换为一个字节
206 + var bytes = hexString.match(/.{2}/g);
207 + // 对每个字节进行解析，并转换为对应的字符
208 + var binaryString = bytes.map(function(byte) {
209 + return String.fromCharCode(parseInt(byte, 16));
210 + }).join('');
211 +
212 + // 使用btoa进行base64编码
213 + return btoa(binaryString);
214 +}
349 349  
350 -// msg - JSON message payload downlink message json
351 -// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
352 -// metadata - list of key-value pairs with additional data about the message
353 -// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
354 -
355 -/** Encoder **/
356 -
357 -var data = {};
358 -
359 -// Process data from incoming message and metadata
360 -
361 -data.tempFreq = msg.temperatureUploadFrequency;
362 -data.humFreq = msg.humidityUploadFrequency;
363 -
364 -data.devSerialNumber = metadata['ss_serialNumber'];
365 -
366 366  // Result object with encoded downlink payload
367 367  var result = {
368 -
369 369   // downlink data content type: JSON, TEXT or BINARY (base64 format)
370 - contentType: "JSON",
219 + contentType: "BINARY",
371 371  
372 372   // downlink data
373 - data: JSON.stringify(data),
222 + data:hexToBase64(metadata.shared_value)
374 374  
375 375   // Optional metadata object presented in key/value format
376 - metadata: {
377 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
378 - }
225 + //metadata: {}
379 379  
380 380  };
381 381  
... ... @@ -386,27 +386,26 @@
386 386  Click on the **Add** button.
387 387  
388 388  
389 -[[image:add-downlink-data-converter.png||height="529" width="500"]]
236 +[[image:downlink-data-converter.png||height="530" width="500"]]
390 390  
391 391  
392 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
393 393  
240 +You should see that the newly added **downlink data converter** is listed on the **Data Converters** page.
394 394  
395 -[[image:data-converters-list.png]]
396 396  
243 +[[image:data-converter-list.png]]
397 397  
398 -= 4. Add Integration =
399 399  
246 += Add Integration =
400 400  
401 401  In the left navigation, click **Integrations center**, and then click **Integrations**.
402 402  
250 +On the **Integrations** page, click on the '**+**' button.
403 403  
404 -[[image:integrations-list-empty.png]]
405 405  
253 +[[image:data-converter-list-page.png]]
406 406  
407 -On the **Integrations** page, click on the '**+**' button.
408 408  
409 -
410 410  The **Add integration** window appears.
411 411  
412 412  In the **Add integration** window, configure the following settings:
... ... @@ -416,8 +416,6 @@
416 416  
417 417  * **Integration type**: MQTT
418 418  * **Name**: MQTT integration NB/CB
419 -* **Enable integration**: YES
420 -* **Allows create devices or assets**: YES
421 421  
422 422  Click **Next** button.
423 423  
... ... @@ -425,6 +425,7 @@
425 425  [[image:add-integration-basic-settings.png||height="511" width="500"]]
426 426  
427 427  
272 +
428 428  **Uplink data converter:**
429 429  
430 430  * Click on the **Select existing** button.
... ... @@ -433,9 +433,10 @@
433 433  Click **Next** button.
434 434  
435 435  
436 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
281 +[[image:add-integration-uplink-data-converter.png||width="500"]]
437 437  
438 438  
284 +
439 439  **Downlink data converter:**
440 440  
441 441  * Click on the **Select existing** button.
... ... @@ -444,219 +444,46 @@
444 444  Click **Next** button.
445 445  
446 446  
447 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
293 +[[image:add-integration-downlink-data-converter.png||height="510" width="500"]]
448 448  
449 449  
296 +
450 450  **Connection:**
451 451  
452 -* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
453 -* **Port**: 8883
299 +* **Host**: mqtt.eu.thingsboard.cloud (This is the host name you copied from the device - See section xxxxx for more information)
300 +* **Port**: 1883 (This is the port number you copied from the device - See section xxxxx for more information)
454 454  * **Credentials**: Basic
455 -* **Enable SSL**: YES
456 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
457 -* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
458 -* **Topic: v1/devices/+/telemetry** (the + replaces any 'device name' will create a device in the Entities -> Devices)
459 -* **QoS:** 0-At most once
302 +* **Username**: Access token (This is the access token you copied from the device)
303 +* **Password** - Leave it as blank
304 +* **Topic** - v1/devices/+/telemetry (sightly modify the topic 'v1/devices/me/telemetry' you copied for the device to enable receiving data from any 'device name')
305 +* **QoS** - 0-At most once
460 460  
307 +Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
461 461  
462 462  
463 -[[image:add-integration-connection.png||height="511" width="500"]]
310 +[[image:add-integration-connection.png||width="500"]]
464 464  
465 465  
466 -Click on the **Advanced settings** button.
313 +If the connection is successful, you will see the **Connected** message.
467 467  
468 -* **Clean session:** YES
469 -* **Retained**: YES
315 +Click on the **Add** button.
470 470  
471 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
472 472  
318 +[[image:add-connection-success.png||height="511" width="500"]]
473 473  
474 -Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
475 475  
476 476  
477 -[[image:check-connection.png||height="83" width="300"]]
478 478  
479 479  
480 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
481 481  
482 482  
483 -[[image:connection-success.png||height="511" width="500"]]
484 -
485 -
486 -Click on the **Add** button.
487 -
488 488  You should see that the newly added integration is listed on the **Integrations** page.
489 489  
490 490  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
491 491  
330 +[[image:Integrations-list.png]]
492 492  
493 493  
494 -[[image:new-integration-pending.png]]
333 += Verifying the receipt of data from the device =
495 495  
496 -
497 -= 5. Verifying the receipt of data from virtual devices =
498 -
499 -
500 -== 5.1 How does it work? ==
501 -
502 -
503 -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.
504 -
505 -The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
506 -
507 -(% 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.
508 -
509 -{{code language="none"}}
510 -{"IMEI": "S31B-NB", "temperature": 27, ......}
511 -{{/code}}
512 -
513 -Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
514 -
515 -
516 -== 5.2 Sending messages ==
517 -
518 -
519 -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.
520 -
521 -{{code language="none"}}
522 -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}'
523 -{{/code}}
524 -
525 -If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
526 -
527 -
528 -[[image:integration-active.png]]
529 -
530 -
531 -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**.
532 -
533 -
534 -[[image:device-provision-1.png]]
535 -
536 -
537 -Click on the device S31B-NB on the devices list to see its details.
538 -
539 -Then go to the **Latest telemetry** tab.
540 -
541 -You can see the fields temperature and humidity with the values you previously sent using the MQTT message.
542 -
543 -
544 -[[image:telemetry-1.png]]
545 -
546 -
547 -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//.
548 -
549 -
550 -[[image:telemetry-2.png]]
551 -
552 -
553 -Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
554 -
555 -
556 -{{code language="none"}}
557 -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}'
558 -{{/code}}
559 -
560 -Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
561 -
562 -
563 -[[image:device-provision-2.png]]
564 -
565 -
566 -= 6. Creating a Dashboard =
567 -
568 -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.
569 -
570 -
571 -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.
572 -
573 -
574 -In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
575 -
576 -
577 -[[image:dashboard-1.png]]
578 -
579 -
580 -In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
581 -
582 -Click on the **Add** button.
583 -
584 -
585 -[[image:dashboard-2.png||height="526" width="500"]]
586 -
587 -
588 -Click on the **Add widget / Add new widget** button.
589 -
590 -
591 -[[image:dashboard-3.png]]
592 -
593 -
594 -In the **Select widgets bundle** window, click **Charts**.
595 -
596 -
597 -[[image:dashboard-4.png||height="537" width="700"]]
598 -
599 -
600 -
601 -In the **Charts: select widget** window, click **Time series chart**.
602 -
603 -
604 -[[image:dashboard-5.png||height="525" width="700"]]
605 -
606 -
607 -Configure the **Time series chart** widget as follows:
608 -
609 -* **Datasource** - select S31B-NB device you provisioned.
610 -* **Series**:
611 -** **temperature** - you can see this key by default.
612 -** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
613 -* Click on the **Add** button.
614 -
615 -[[image:timeseries-1.png||height="491" width="700"]]
616 -
617 -
618 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
619 -
620 -Click the **Save** button to add the widget to the dashboard.
621 -
622 -
623 -[[image:timeseries-3.png||height="347" width="700"]]
624 -
625 -
626 -Now send the following MQTT messages from the terminal to simulate the data.
627 -
628 -
629 -{{code language="none"}}
630 -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}'
631 -
632 -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}'
633 -
634 -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}'
635 -
636 -{{/code}}
637 -
638 -The chart will update with the values in realtime, as shown in the below image.
639 -
640 -
641 -[[image:timeseries-4.png||height="316" width="700"]]
642 -
643 -
644 -= 7. Configure NB-IoT Sensor =
645 -
646 -
647 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
648 -
649 -First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
650 -
651 -
652 -**AT Commands**
653 -
654 -* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
655 -* **AT+SUBTOPIC=<MQTT topic>**
656 -* **AT+PUBTOPIC=<MQTT topic>**
657 -* **AT+CLIENT=null**
658 -* **AT+UNAME=<MQTT Username>**
659 -* **AT+PWD=<MQTT Password>**
660 -* **AT+SERVADDR=<Broker address, Port>**
661 -
662 -Test your uplink by pressing the ACT button for 1 second.
335 +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.
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-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
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
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-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-add-data-converter.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
add-connection-success.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
data-converter-list-page.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +190.8 KB
Content
data-converter-list.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
device-list-empty.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
downlink-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +207.8 KB
Content
integrations-list-added-pending.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
new-device-device-details.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
uplink-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content