Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 176.1
edited by Dilisi S
on 2025/03/26 20:27
Change comment: Mar 26 edits - part 1
To version 210.1
edited by Dilisi S
on 2025/04/21 18:14
Change comment: Uploaded new attachment "device-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -164,35 +164,18 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
167 -(% class="wikigeneratedid" %)
168 -= 3. Creating Devices =
169 169  
168 += 3. Data Converters =
170 170  
171 -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.
172 172  
173 -
174 -In the left navigation, click Entities -> Devices.
175 -
176 -Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
177 -
178 -In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
179 -
180 -Click the **Add** button.
181 -
182 -Skip the **connectivity testing** by clicking the **Close** button.
183 -
184 -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.
185 -
186 -
187 -= 4. Data Converters =
188 -
189 -
190 190  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.
191 191  
173 +**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**.
192 192  
193 -== 4.1 Uplink ==
194 194  
176 +== 3.1 Uplink ==
195 195  
178 +
196 196  In the left navigation, click **Integrations center**, and then click **Data converters**.
197 197  
198 198  
... ... @@ -199,7 +199,7 @@
199 199  [[image:data-converters-list-empty.png]]
200 200  
201 201  
202 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
185 +On the **Data converters** page, click on the ‘**+**’ button, and then click on **Create new converter** from the dropdown menu.
203 203  
204 204  
205 205  
... ... @@ -206,143 +206,75 @@
206 206  [[image:create-new-converter-menu.png||height="259" width="500"]]
207 207  
208 208  
209 -The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
192 +The **Add data converter** window appears.
210 210  
211 -Click on the **JavaScript** button.
194 +Name it ‘**MQTT Uplink Converter**’ and select the Type as **Uplink**.
212 212  
213 -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.
196 +Click on the **TBEL** button if it has not been selected by default.
214 214  
215 -{{info}}
216 -Please note that the value assigned to the IMEI field in the payload will be used by ThingsBoard to create a device on the platform with the same name.
217 -{{/info}}
198 +Replace the default TBEL decoder function with the following universal TBEL decoder function, which decodes MQTT payload from any Dragino NB-IoT device.
218 218  
219 -{{code language="JavaScript"}}
220 -//Version: 0.1
221 -// decode payload to string
222 -var payloadStr = decodeToString(payload);
223 223  
201 +{{code language="JavaScript"}}
224 224  // decode payload to JSON
203 +var pattern = "yyyy/MM/dd HH:mm:ss";
225 225  var objdata = {};
226 226  var obj1 = {};
227 227  var data = decodeToJson(payload);
228 228  var deviceName = data.IMEI;
229 -delete data.IMEI;
230 -var modelname = "Dragino " + data.Model;
208 +data.remove("IMEI");
209 +var modelname = "Dragino "+ data.Model;
231 231  //var mod = data.mod
232 -delete data.Model;
211 +data.remove("Model");
233 233  //delete data.mod
234 234  var timestamp = new Date().getTime();
235 -
236 -for (var key in data) {
237 -
238 - if (Number(key)) {
239 - obj1[key] = data[key];
240 - obj1[key][obj1[key].length - 1] = Number(new Date(
241 - obj1[key][obj1[key].length - 1]));
242 -
214 +foreach (entry: data.entrySet()) {
215 + var key = entry.getKey();
216 + var value = entry.getValue();
217 + //objdata[key] = data[key]
218 + if(key.matches("^-?\\d+$")){ //is number
219 + obj1[key]=data[key];
220 + var index = obj1[key].length-1;
221 + obj1[key][index]=new Date(obj1[key][index],pattern).getTime();
243 243   }
244 -//Alec submitted25/02/25
245 -//turn old key into new
246 - else if (key === "Reading") {
247 - objdata["reading"] = data[key];
248 - } else if (key === "work mode") {
249 - objdata["work_mode"] = data[key];
250 - } else if (key === "hum") {
251 - objdata["humidity"] = data[key];
252 - }else if (key === "hum2") {
253 - objdata["humidity2"] = data[key];
254 - } else if (key === "hum3") {
255 - objdata["humidity3"] = data[key];
256 - } else if (key === "tem") {
257 - objdata["temperature"] = data[key];
258 - } else if (key === "tem2") {
259 - objdata["temperature2"] = data[key];
260 - } else if (key === "tem3") {
261 - objdata["temperature3"] = data[key];
262 - } else if (key === "DS18B20_Temp") {
263 - objdata["temperature_pro"] = data[key];
264 - } else if (key === "ds18b20_temperature") {
265 - objdata["temperature_pro"] = data[key];
266 - } else if (key === "DS18B20_temperature_pro") {
267 - objdata["temperature_pro"] = data[key];
268 - } else if (key === "tdc send flag") {
269 - objdata["tdc_send_flag"] = data[key];
270 - } else if (key === "trigger mode") {
271 - objdata["trigger_mode"] = data[key];
272 - } else if (key === "soil dielectric constant") {
273 - objdata["soil_dielectric_constant"] = data[key];
274 - } else if (key === "door open num") {
275 - objdata["door_open_num"] = data[key];
276 - } else if (key === "door duration") {
277 - objdata["door_duration"] = data[key];
278 - } else if (key === "count time") {
279 - objdata["count_time"] = data[key];
280 - } else if (key === "last open time2") {
281 - objdata["last_open_time2"] = data[key];
282 - } else if (key === "last open time3") {
283 - objdata["last_open_time3"] = data[key];
223 + else if (key==="bat"||key==="BAT"){
224 + objdata["battery"] = data[key];
284 284   }
285 -//Alec submitted25/02/25
286 - else {
287 - objdata[key] = data[key]
226 + else{
227 + objdata[key] = data[key];
228 +}}
229 +var listdata = [{"ts":timestamp,"values":objdata}];
230 +foreach ( entry1: obj1.entrySet()){
231 + var key1 = entry1.getKey();
232 + var value1 = entry1.getValue();
233 + var index = obj1[key1].length-1;
234 + var ts = obj1[key1][index];
235 + if (modelname=="Dragino RS485-NB"){
236 + listdata.push({"ts":ts,"values":{"Payload":obj1[key1][0]}});
288 288   }
289 -}
290 -var listdata = [{
291 - "ts": timestamp,
292 - "values": objdata
293 -}]
294 -for (var key1 in obj1) {
295 - if (modelname == "Dragino RS485-NB") {
296 - listdata.push({
297 - "ts": obj1[key1][obj1[key1].length - 1],
298 - "values": {
299 - "Payload": obj1[key1][0],
300 - }
301 - })
302 - } else {
303 - listdata.push({
304 - "ts": obj1[key1][obj1[key1].length - 1],
305 - "values": {
306 - "values": obj1[key1]
307 - },
308 - })
238 + else{
239 + listdata.push({"ts":ts,"values":{"values":obj1[key1]}});
309 309   }
310 310  }
311 -var result = {
312 -
242 + var result = {
313 313   deviceName: deviceName,
314 314   deviceType: modelname,
315 315   attributes: {
316 - model: modelname,
246 + model: modelname
317 317   //customerName: "NB-CB",
318 318   //groupName: "NB-CB",
319 319   //integrationName: metadata['integrationName']
320 -
321 321   },
322 322   telemetry: listdata
323 -}
324 -
325 -function decodeToString(payload) {
326 - return String.fromCharCode.apply(String, payload);
327 -}
328 -
329 -function decodeToJson(payload) {
330 - // covert payload to string.
331 - var str = decodeToString(payload);
332 -
333 - // parse string to JSON
334 - var data = JSON.parse(str);
335 - return data;
336 -}
337 -
252 +};
338 338  return result;
339 339  {{/code}}
340 340  
341 341  
342 -Click on the **Add** button.
257 +Once you modify the decoder function, click on the **Add** button.
343 343  
344 344  
345 -[[image:mqtt-uplink.png||width="500"]]
260 +[[image:mqtt-uplink-converter.png||height="498" width="500"]]
346 346  
347 347  
348 348  
... ... @@ -349,12 +349,13 @@
349 349  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
350 350  
351 351  
352 -[[image:data-converter-list-showing-uplink-dc.png]]
353 353  
268 +[[image:data-converters-list.png]]
354 354  
355 -= 5. Add Integration =
356 356  
271 += 4. Add Integration =
357 357  
273 +
358 358  In the left navigation, click **Integrations center**, and then click **Integrations**.
359 359  
360 360  
... ... @@ -372,16 +372,17 @@
372 372  **Basic settings:**
373 373  
374 374  * **Integration type**: MQTT
375 -* **Name**: MQTT integration NB/CB
291 +* **Name**: MQTT integration
376 376  * **Enable integration**: YES
377 -* **Allows create devices or assets**: YES
293 +* **Allow create devices or assets**: YES
378 378  
379 379  Click **Next** button.
380 380  
381 381  
382 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
383 383  
299 +[[image:add-integration-part-1.png||height="483" width="500"]]
384 384  
301 +
385 385  **Uplink data converter:**
386 386  
387 387  * Click on the **Select existing** button.
... ... @@ -390,9 +390,10 @@
390 390  Click **Next** button.
391 391  
392 392  
393 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
394 394  
311 +[[image:add-integration-part-2.png||height="484" width="500"]]
395 395  
313 +
396 396  **Downlink data converter:**
397 397  
398 398  Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
... ... @@ -408,19 +408,20 @@
408 408  
409 409  **Connection:**
410 410  
411 -* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
412 -* **Port**: 8883
413 -* **Credentials**: Basic
414 -* **Enable SSL**: YES
329 +* **Host**: Host URL (Eg, **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
330 +* **Port**: 8883 (the port number may differ based on your MQTT broker)
331 +* **Credentials type**: Basic
415 415  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
416 416  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
417 -* **Topic: v1/devices/me/telemetry** (The topic can be anything; you can even use just the device name. For example, you can use your device name here, such as S31B-NB.)
334 +* **Enable SSL**: YES
335 +* **Topic**: # (the # symbol indicates that it filters all topics).
418 418  * **QoS:** 0-At most once
419 419  
420 420  
421 -[[image:add-integration-connection.png||height="511" width="500"]]
422 422  
340 +[[image:add-integration-4.png||height="484" width="500"]]
423 423  
342 +
424 424  Click on the **Advanced settings** button.
425 425  
426 426  * **Clean session:** YES
... ... @@ -448,35 +448,36 @@
448 448  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
449 449  
450 450  
451 -[[image:new-integration-pending.png]]
370 +[[image:integration-added.png]]
452 452  
453 453  
454 -= 6. Verifying the receipt of data from virtual devices =
455 455  
374 += 5. Verifying the receipt of data from virtual devices =
456 456  
457 -== 6.1 How does it work? ==
458 458  
377 +== 5.1 How does it work? ==
459 459  
379 +
460 460  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.
461 461  
462 -The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
382 +The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
463 463  
464 -(% 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.
384 +(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
465 465  
466 466  {{code language="none"}}
467 -{"IMEI": "S31B-NB", "temperature": 27, ......}
387 +{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
468 468  {{/code}}
469 469  
470 -Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
390 +Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
471 471  
472 472  
473 473  == 5.2 Sending messages ==
474 474  
475 475  
476 -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.
396 +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.
477 477  
478 478  {{code language="none"}}
479 -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}'
399 +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}'
480 480  {{/code}}
481 481  
482 482  If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
... ... @@ -485,15 +485,9 @@
485 485  [[image:integration-active.png]]
486 486  
487 487  
488 -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**.
408 +== 5.3 Viewing messages ==
489 489  
490 490  
491 -[[image:new-device.png]]
492 -
493 -
494 -== 6.3 Viewing messages ==
495 -
496 -
497 497  Go back to the **Integrations** page.
498 498  
499 499  Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
... ... @@ -509,29 +509,40 @@
509 509  Then click on the **Apply changes** (//**tick icon**//) button.
510 510  
511 511  
512 -[[image:Screenshot 2025-03-18 at 09.23.10.png]]
426 +[[image:debug-enabled.png||height="301" width="700"]]
513 513  
514 514  
429 +
430 +
515 515  Now go to the **Events** tab.
516 516  
517 -Select the Event type as **Debug** from the dropdown list.
433 +Select the **Event type** as **Debug** from the dropdown list.
518 518  
519 -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.
435 +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:
520 520  
437 +{{code language="none"}}
438 +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}'
439 +{{/code}}
521 521  
522 -[[image:Screenshot 2025-03-16 at 18.38.59.png]]
441 +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.
523 523  
524 524  
444 +[[image:Screenshot 2025-03-26 at 19.49.31.png]]
445 +
446 +
447 +
525 525  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
526 526  
527 527  
528 -[[image:Screenshot 2025-03-16 at 18.39.12.png]]
451 +[[image:Screenshot 2025-03-26 at 19.47.52.png]]
529 529  
530 530  
454 +
455 +
531 531  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.
532 532  
533 533  
534 -= 7. Creating a Dashboard =
459 += 6. Creating a Dashboard =
535 535  
536 536  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.
537 537  
... ... @@ -541,7 +541,7 @@
541 541  
542 542  First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
543 543  
544 -{{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}}
469 +{{code language="none"}}mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":22, "humidity":80, "pressure":1005}'{{/code}}
545 545  
546 546  
547 547  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
... ... @@ -579,15 +579,19 @@
579 579  
580 580  Configure the **Time series chart** widget as follows:
581 581  
582 -* **Datasource** - select S31B-NB device you provisioned.
507 +* **Datasource** - select **Device A** device you provisioned.
583 583  * **Series**:
584 584  ** **temperature** - you can see this key by default.
585 585  ** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
586 586  * Click on the **Add** button.
587 587  
588 -[[image:timeseries-1.png||height="491" width="700"]]
513 +{{info}}
514 +You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
515 +{{/info}}
589 589  
517 +[[image:Screenshot 2025-03-31 at 06.51.15.png||height="485" width="700"]]
590 590  
519 +
591 591  The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
592 592  
593 593  Click the **Save** button to add the widget to the dashboard.
... ... @@ -600,12 +600,11 @@
600 600  
601 601  
602 602  {{code language="none"}}
603 -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}'
532 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":22, "humidity":70, "pressure":1005}'
604 604  
605 -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}'
534 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":27, "humidity":72, "pressure":1005}'
606 606  
607 -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}'
608 -
536 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":19, "humidity":80, "pressure":1005}'
609 609  {{/code}}
610 610  
611 611  The chart will update with the values in realtime, as shown in the below image.
... ... @@ -614,7 +614,7 @@
614 614  [[image:timeseries-4.png||height="316" width="700"]]
615 615  
616 616  
617 -= 8. Configure NB-IoT Sensor =
545 += 8. Configure Physical NB-IoT Sensor =
618 618  
619 619  
620 620  Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
... ... @@ -636,13 +636,7 @@
636 636  
637 637  
638 638  
639 -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 +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.
640 640  
641 -{{info}}
642 -The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
643 -{{/info}}
644 644  
645 645  [[image:image-4.png]]
646 -
647 -
648 -
add-integration-basic-settings.png
Size
... ... @@ -1,1 +1,1 @@
1 -122.5 KB
1 +123.8 KB
Content
data-converters-list.png
Size
... ... @@ -1,1 +1,1 @@
1 -212.2 KB
1 +19.0 KB
Content
integration-active.png
Size
... ... @@ -1,1 +1,1 @@
1 -64.2 KB
1 +64.1 KB
Content
Screenshot 2025-03-26 at 18.15.08.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +92.2 KB
Content
Screenshot 2025-03-26 at 19.47.52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +168.4 KB
Content
Screenshot 2025-03-26 at 19.49.31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +133.0 KB
Content
Screenshot 2025-03-31 at 06.51.15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +179.5 KB
Content
add-integartion-connection.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +110.3 KB
Content
add-integartion-connetcion.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +146.0 KB
Content
add-integration-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +63.1 KB
Content
add-integration-part-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +48.6 KB
Content
add-integration-part-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +47.7 KB
Content
add-integration-ul-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +121.2 KB
Content
debug-enabled.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.3 KB
Content
device-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +34.5 KB
Content
integration-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.2 KB
Content
integrations-pending.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +19.8 KB
Content
mqtt-uplink-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +75.3 KB
Content
ul-data-converter-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +189.4 KB
Content
ul-data-converter-device-a.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +168.3 KB
Content