Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 206.1
edited by Dilisi S
on 2025/04/21 16:53
Change comment: Uploaded new attachment "add-integration-part-2.png", version {1}
To version 181.1
edited by Dilisi S
on 2025/03/27 02:49
Change comment: Uploaded new attachment "Screenshot 2025-03-26 at 19.49.31.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -164,18 +164,34 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
167 += 3. Creating Devices =
167 167  
168 -= 3. Data Converters =
169 169  
170 +First, you need to create devices in ThingsBoard to represent your physical devices. For example, you can name it **Device A**, and the second device could be **Device B** or any name you prefer. The device name should be unique within the **Devices** space.
170 170  
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.
172 172  
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**.
173 +In the left navigation, click Entities -> Devices.
174 174  
175 +Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
175 175  
176 -== 3.1 Uplink ==
177 +In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
177 177  
179 +Click the **Add** button.
178 178  
181 +Skip the **connectivity testing** by clicking the **Close** button.
182 +
183 +The device is created and listed on the **Devices** page. Note that its initial state is **Inactive** because it has not received any data yet.
184 +
185 +
186 += 4. Data Converters =
187 +
188 +
189 +In **ThingsBoard**, **Data Converters** are components used to transform incoming or outgoing data between different formats, typically to convert raw telemetry data from devices into a structured format that ThingsBoard can understand, or vice versa.
190 +
191 +
192 +== 4.1 Uplink ==
193 +
194 +
179 179  In the left navigation, click **Integrations center**, and then click **Data converters**.
180 180  
181 181  
... ... @@ -182,7 +182,7 @@
182 182  [[image:data-converters-list-empty.png]]
183 183  
184 184  
185 -On the **Data converters** page, click on the ‘**+**’ button, and then click on **Create new converter** from the dropdown menu.
201 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
186 186  
187 187  
188 188  
... ... @@ -189,75 +189,98 @@
189 189  [[image:create-new-converter-menu.png||height="259" width="500"]]
190 190  
191 191  
192 -The **Add data converter** window appears.
208 +The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
193 193  
194 -Name it ‘**MQTT Uplink Converter**’ and select the Type as **Uplink**.
195 -
196 196  Click on the **TBEL** button if it has not been selected by default.
197 197  
198 -Replace the default TBEL decoder function with the following universal TBEL decoder function, which decodes MQTT payload from any Dragino NB-IoT device.
212 +Modify the default TBEL function to match with your device as described below:
199 199  
200 200  
215 +~1. Uncomment line 11:
216 +
217 +var data = decodeToJson(payload)
218 +
219 +[[image:Screenshot 2025-03-26 at 18.15.08.png||height="219" width="500"]]
220 +
221 +
222 +3. Modify the telemetry section to allow parsed data to be assigned to the fields.
223 +
224 +telemetry: {
225 + temperature: data.temperature,
226 + humidity: data.humidity,
227 + rawData: payloadStr
228 + }
229 +
230 +
231 +
201 201  {{code language="JavaScript"}}
233 +// Decode an uplink message from a buffer
234 +// payload - array of bytes
235 +// metadata - key/value object
236 +
237 +/** Decoder **/
238 +
239 +// decode payload to string
240 +var payloadStr = decodeToString(payload);
241 +
202 202  // decode payload to JSON
203 -var pattern = "yyyy/MM/dd HH:mm:ss";
204 -var objdata = {};
205 -var obj1 = {};
206 206  var data = decodeToJson(payload);
207 -var deviceName = data.IMEI;
208 -data.remove("IMEI");
209 -var modelname = "Dragino "+ data.Model;
210 -//var mod = data.mod
211 -data.remove("Model");
212 -//delete data.mod
213 -var timestamp = new Date().getTime();
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();
222 - }
223 - else if (key==="bat"||key==="BAT"){
224 - objdata["battery"] = data[key];
225 - }
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]}});
237 - }
238 - else{
239 - listdata.push({"ts":ts,"values":{"values":obj1[key1]}});
240 - }
241 -}
242 - var result = {
243 - deviceName: deviceName,
244 - deviceType: modelname,
245 - attributes: {
246 - model: modelname
247 - //customerName: "NB-CB",
248 - //groupName: "NB-CB",
249 - //integrationName: metadata['integrationName']
250 - },
251 - telemetry: listdata
244 +
245 +var deviceName = 'Device B';
246 +var deviceType = 'thermostat';
247 +var customerName = 'Customer C';
248 +var groupName = 'thermostat devices';
249 +var manufacturer = 'Example corporation';
250 +// use assetName and assetType instead of deviceName and deviceType
251 +// to automatically create assets instead of devices.
252 +// var assetName = 'Asset A';
253 +// var assetType = 'building';
254 +
255 +// Result object with device/asset attributes/telemetry data
256 +var result = {
257 +// Use deviceName and deviceType or assetName and assetType, but not both.
258 + deviceName: deviceName,
259 + deviceType: deviceType,
260 +// assetName: assetName,
261 +// assetType: assetType,
262 +// customerName: customerName,
263 + groupName: groupName,
264 + attributes: {
265 + model: 'Model A',
266 + serialNumber: 'SN111',
267 + integrationName: metadata['integrationName'],
268 + manufacturer: manufacturer
269 + },
270 + telemetry: {
271 + temperature: data.temperature,
272 + humidity: data.humidity,
273 + rawData: payloadStr
274 + }
252 252  };
276 +
277 +/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
278 +
253 253  return result;
254 254  {{/code}}
255 255  
282 +We use the same decoder function for all our devices. However, you need to modify a few things for each device. Among these, **deviceName** is a **mandatory** field. You should assign a device name to the **deviceName** field that matches the name of your device in the **Devices** section.
256 256  
284 +For example, if your device name is **Device B**, you can change **Device A** to **Device B**.
285 +
286 +
287 +{{code language="JavaScript"}}
288 +var deviceName = 'Device A';
289 +var deviceType = 'thermostat';
290 +var customerName = 'Customer C';
291 +var groupName = 'thermostat devices';
292 +var manufacturer = 'Example corporation';
293 +{{/code}}
294 +
295 +
257 257  Once you modify the decoder function, click on the **Add** button.
258 258  
259 259  
260 -[[image:mqtt-uplink-converter.png||height="498" width="500"]]
299 +[[image:mqtt-uplink.png||width="500"]]
261 261  
262 262  
263 263  
... ... @@ -264,13 +264,12 @@
264 264  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
265 265  
266 266  
306 +[[image:data-converter-list-showing-uplink-dc.png]]
267 267  
268 -[[image:data-converters-list.png]]
269 269  
309 += 5. Add Integration =
270 270  
271 -= 4. Add Integration =
272 272  
273 -
274 274  In the left navigation, click **Integrations center**, and then click **Integrations**.
275 275  
276 276  
... ... @@ -288,18 +288,16 @@
288 288  **Basic settings:**
289 289  
290 290  * **Integration type**: MQTT
291 -* **Name**: MQTT integration - Device A
329 +* **Name**: MQTT integration NB/CB
292 292  * **Enable integration**: YES
293 -* **Allow create devices or assets**: YES
331 +* **Allows create devices or assets**: YES
294 294  
295 295  Click **Next** button.
296 296  
297 297  
298 -[[image:add-integration-basic-settings.png||height="504" width="500"]]
336 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
299 299  
300 300  
301 -
302 -
303 303  **Uplink data converter:**
304 304  
305 305  * Click on the **Select existing** button.
... ... @@ -308,10 +308,9 @@
308 308  Click **Next** button.
309 309  
310 310  
311 -[[image:add-integration-ul-data-converter.png||height="505" width="500"]]
347 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
312 312  
313 313  
314 -
315 315  **Downlink data converter:**
316 316  
317 317  Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
... ... @@ -327,16 +327,16 @@
327 327  
328 328  **Connection:**
329 329  
330 -* **Host**: Host URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
365 +* **Host**: Cluster URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
331 331  * **Port**: 8883
332 -* **Credentials type**: Basic
367 +* **Credentials**: Basic
368 +* **Enable SSL**: YES
333 333  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
334 334  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
335 -* **Enable SSL**: YES
336 -* **Topic: device/a** (The topic can be anything; you can even use just the device name.)
371 +* **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 devices/a/telemetry.)
337 337  * **QoS:** 0-At most once
338 338  
339 -[[image:add-integartion-connection.png||height="505" width="500"]]
374 +[[image:add-integration-connection.png||height="511" width="500"]]
340 340  
341 341  
342 342  Click on the **Advanced settings** button.
... ... @@ -366,36 +366,35 @@
366 366  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
367 367  
368 368  
369 -[[image:integration-added.png]]
404 +[[image:new-integration-pending.png]]
370 370  
371 371  
407 += 6. Verifying the receipt of data from virtual devices =
372 372  
373 -= 5. Verifying the receipt of data from virtual devices =
374 374  
410 +== 6.1 How does it work? ==
375 375  
376 -== 5.1 How does it work? ==
377 377  
378 -
379 379  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.
380 380  
381 -The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
415 +The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
382 382  
383 -(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
417 +(% 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 384  
385 385  {{code language="none"}}
386 -{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
420 +{"IMEI": "S31B-NB", "temperature": 27, ......}
387 387  {{/code}}
388 388  
389 -Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
423 +Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
390 390  
391 391  
392 392  == 5.2 Sending messages ==
393 393  
394 394  
395 -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.
429 +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 396  
397 397  {{code language="none"}}
398 -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}'
432 +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 399  {{/code}}
400 400  
401 401  If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
... ... @@ -404,9 +404,15 @@
404 404  [[image:integration-active.png]]
405 405  
406 406  
407 -== 5.3 Viewing messages ==
441 +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 408  
409 409  
444 +[[image:new-device.png]]
445 +
446 +
447 +== 6.3 Viewing messages ==
448 +
449 +
410 410  Go back to the **Integrations** page.
411 411  
412 412  Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
... ... @@ -422,40 +422,29 @@
422 422  Then click on the **Apply changes** (//**tick icon**//) button.
423 423  
424 424  
425 -[[image:debug-enabled.png||height="301" width="700"]]
465 +[[image:Screenshot 2025-03-18 at 09.23.10.png]]
426 426  
427 427  
428 -
429 -
430 430  Now go to the **Events** tab.
431 431  
432 -Select the **Event type** as **Debug** from the dropdown list.
470 +Select the Event type as **Debug** from the dropdown list.
433 433  
434 -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:
472 +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 435  
436 -{{code language="none"}}
437 -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}'
438 -{{/code}}
439 439  
440 -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.
475 +[[image:Screenshot 2025-03-16 at 18.38.59.png]]
441 441  
442 442  
443 -[[image:Screenshot 2025-03-26 at 19.49.31.png]]
444 -
445 -
446 -
447 447  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
448 448  
449 449  
450 -[[image:Screenshot 2025-03-26 at 19.47.52.png]]
481 +[[image:Screenshot 2025-03-16 at 18.39.12.png]]
451 451  
452 452  
453 -
454 -
455 455  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.
456 456  
457 457  
458 -= 6. Creating a Dashboard =
487 += 7. Creating a Dashboard =
459 459  
460 460  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.
461 461  
... ... @@ -465,7 +465,7 @@
465 465  
466 466  First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
467 467  
468 -{{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}}
497 +{{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 469  
470 470  
471 471  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
... ... @@ -503,19 +503,15 @@
503 503  
504 504  Configure the **Time series chart** widget as follows:
505 505  
506 -* **Datasource** - select **Device A** device you provisioned.
535 +* **Datasource** - select S31B-NB device you provisioned.
507 507  * **Series**:
508 508  ** **temperature** - you can see this key by default.
509 509  ** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
510 510  * Click on the **Add** button.
511 511  
512 -{{info}}
513 -You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
514 -{{/info}}
541 +[[image:timeseries-1.png||height="491" width="700"]]
515 515  
516 -[[image:Screenshot 2025-03-31 at 06.51.15.png||height="485" width="700"]]
517 517  
518 -
519 519  The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
520 520  
521 521  Click the **Save** button to add the widget to the dashboard.
... ... @@ -528,11 +528,12 @@
528 528  
529 529  
530 530  {{code language="none"}}
531 -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}'
556 +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 532  
533 -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}'
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": 27, "humidity":72}'
534 534  
535 -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}'
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": 19, "humidity":80}'
561 +
536 536  {{/code}}
537 537  
538 538  The chart will update with the values in realtime, as shown in the below image.
... ... @@ -541,7 +541,7 @@
541 541  [[image:timeseries-4.png||height="316" width="700"]]
542 542  
543 543  
544 -= 8. Configure Physical NB-IoT Sensor =
570 += 8. Configure NB-IoT Sensor =
545 545  
546 546  
547 547  Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
... ... @@ -563,7 +563,13 @@
563 563  
564 564  
565 565  
566 -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.
592 +The following image shows the uplink payload of a real Dragino device. The publish topic is **TS01-NB**, and the device name is **861275077962896**, which is represented by the **IMEI**.
567 567  
594 +{{info}}
595 +The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
596 +{{/info}}
568 568  
569 569  [[image:image-4.png]]
599 +
600 +
601 +
Screenshot 2025-03-31 at 06.51.15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -179.5 KB
Content
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-part-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -48.6 KB
Content
add-integration-part-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -47.7 KB
Content
add-integration-ul-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -121.2 KB
Content
data-converters-list.png
Size
... ... @@ -1,1 +1,1 @@
1 -19.0 KB
1 +212.2 KB
Content
debug-enabled.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -196.3 KB
Content
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
mqtt-uplink-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -75.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