Skip to Content

Changes for page ThingsBoard

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

Summary

Details

Page properties
Content
... ... @@ -164,18 +164,35 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
167 +(% class="wikigeneratedid" %)
168 += 3. Creating Devices =
167 167  
168 -= 3. Data Converters =
169 169  
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.
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**.
174 +In the left navigation, click Entities -> Devices.
174 174  
176 +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 ==
178 +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  
180 +Click the **Add** button.
178 178  
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 +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 +
192 +
193 +== 4.1 Uplink ==
194 +
195 +
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.
202 +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,143 @@
189 189  [[image:create-new-converter-menu.png||height="259" width="500"]]
190 190  
191 191  
192 -The **Add data converter** window appears.
209 +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**.
211 +Click on the **JavaScript** button.
195 195  
196 -Click on the **TBEL** button if it has not been selected by default.
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.
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.
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}}
199 199  
200 -
201 201  {{code language="JavaScript"}}
220 +//Version: 0.1
221 +// decode payload to string
222 +var payloadStr = decodeToString(payload);
223 +
202 202  // decode payload to JSON
203 -var pattern = "yyyy/MM/dd HH:mm:ss";
204 204  var objdata = {};
205 205  var obj1 = {};
206 206  var data = decodeToJson(payload);
207 207  var deviceName = data.IMEI;
208 -data.remove("IMEI");
209 -var modelname = "Dragino "+ data.Model;
229 +delete data.IMEI;
230 +var modelname = "Dragino " + data.Model;
210 210  //var mod = data.mod
211 -data.remove("Model");
232 +delete data.Model;
212 212  //delete data.mod
213 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();
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 +
222 222   }
223 - else if (key==="bat"||key==="BAT"){
224 - objdata["battery"] = data[key];
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];
225 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]}});
285 +//Alec submitted25/02/25
286 + else {
287 + objdata[key] = data[key]
237 237   }
238 - else{
239 - listdata.push({"ts":ts,"values":{"values":obj1[key1]}});
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 + })
240 240   }
241 241  }
242 - var result = {
311 +var result = {
312 +
243 243   deviceName: deviceName,
244 244   deviceType: modelname,
245 245   attributes: {
246 - model: modelname
316 + model: modelname,
247 247   //customerName: "NB-CB",
248 248   //groupName: "NB-CB",
249 249   //integrationName: metadata['integrationName']
320 +
250 250   },
251 251   telemetry: listdata
252 -};
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 +
253 253  return result;
254 254  {{/code}}
255 255  
256 256  
257 -Once you modify the decoder function, click on the **Add** button.
342 +Click on the **Add** button.
258 258  
259 259  
260 -[[image:mqtt-uplink-converter.png||height="498" width="500"]]
345 +[[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  
352 +[[image:data-converter-list-showing-uplink-dc.png]]
267 267  
268 -[[image:data-converters-list.png]]
269 269  
355 += 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,17 +288,16 @@
288 288  **Basic settings:**
289 289  
290 290  * **Integration type**: MQTT
291 -* **Name**: MQTT integration
375 +* **Name**: MQTT integration NB/CB
292 292  * **Enable integration**: YES
293 -* **Allow create devices or assets**: YES
377 +* **Allows create devices or assets**: YES
294 294  
295 295  Click **Next** button.
296 296  
297 297  
382 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
298 298  
299 -[[image:add-integration-part-1.png||height="483" width="500"]]
300 300  
301 -
302 302  **Uplink data converter:**
303 303  
304 304  * Click on the **Select existing** button.
... ... @@ -307,10 +307,9 @@
307 307  Click **Next** button.
308 308  
309 309  
393 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
310 310  
311 -[[image:add-integration-part-2.png||height="484" width="500"]]
312 312  
313 -
314 314  **Downlink data converter:**
315 315  
316 316  Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
... ... @@ -326,17 +326,17 @@
326 326  
327 327  **Connection:**
328 328  
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
411 +* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
412 +* **Port**: 8883
413 +* **Credentials**: Basic
414 +* **Enable SSL**: YES
332 332  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
333 333  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
334 -* **Enable SSL**: YES
335 -* **Topic**: # (the # symbol indicates that it filters all topics).
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.)
336 336  * **QoS:** 0-At most once
337 337  
338 338  
339 -[[image:add-integration-4.png||height="484" width="500"]]
421 +[[image:add-integration-connection.png||height="511" width="500"]]
340 340  
341 341  
342 342  Click on the **Advanced settings** button.
... ... @@ -366,56 +366,52 @@
366 366  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
367 367  
368 368  
451 +[[image:new-integration-pending.png]]
369 369  
370 -[[image:integrations-pending.png]]
371 371  
454 += 6. Verifying the receipt of data from virtual devices =
372 372  
373 -= 5. Verifying the receipt of data from virtual devices =
374 374  
457 +== 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) to a topic - for example, # or device/ts01-nb. You can, of course, use any topic you prefer.
462 +The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
382 382  
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.
383 383  
384 -(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows. The **IMEI **and **Model **are mandatory fields. For other fields, you can use any number of key-value pairs.
385 -
386 386  {{code language="none"}}
387 -{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}
467 +{"IMEI": "S31B-NB", "temperature": 27, ......}
388 388  {{/code}}
389 389  
470 +Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
390 390  
472 +
391 391  == 5.2 Sending messages ==
392 392  
393 393  
394 -On your computer's terminal, issue the following MQTT command, which simulates the device named '**350693903995577'**. The message payload contains the fields IMEI, Model, temperature, humidity, and pressure, which hold the values 350693903995577,  TS01-NB, 30, 80, and 1005 respectively. This payload is also (technically) known as telemetry.
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.
395 395  
396 396  {{code language="none"}}
397 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/350693903995577" -m '{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}'
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}'
398 398  {{/code}}
399 399  
400 -If the integration was performed without errors, a new device named **350693903995577 **is created in the **Devices **section.
482 +If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
401 401  
402 402  
403 -[[image:new-device-1.png]]
485 +[[image:integration-active.png]]
404 404  
405 405  
406 -The status of the integration also changes to '**Active**' after the first telemetry transmission.
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**.
407 407  
408 408  
409 -[[image:Screenshot 2025-04-21 122154.png]]
491 +[[image:new-device.png]]
410 410  
411 411  
494 +== 6.3 Viewing messages ==
412 412  
413 -**When ThingsBoard receives this message for the first time, it will automatically create a new device named '350693903995577' in the Devices section. The device name is based on the IMEI number. For subsequent messages with the same IMEI, no duplicate devices will be created. Each new IMEI number will result in a unique entry in the Devices section, representing a physical device.**
414 414  
415 -
416 -== 5.3 Viewing messages ==
417 -
418 -
419 419  Go back to the **Integrations** page.
420 420  
421 421  Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
... ... @@ -431,40 +431,29 @@
431 431  Then click on the **Apply changes** (//**tick icon**//) button.
432 432  
433 433  
434 -[[image:debug-enabled.png||height="301" width="700"]]
512 +[[image:Screenshot 2025-03-18 at 09.23.10.png]]
435 435  
436 436  
437 -
438 -
439 439  Now go to the **Events** tab.
440 440  
441 -Select the **Event type** as **Debug** from the dropdown list.
517 +Select the Event type as **Debug** from the dropdown list.
442 442  
443 -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:
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.
444 444  
445 -{{code language="none"}}
446 -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}'
447 -{{/code}}
448 448  
449 -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.
522 +[[image:Screenshot 2025-03-16 at 18.38.59.png]]
450 450  
451 451  
452 -[[image:Screenshot 2025-03-26 at 19.49.31.png]]
453 -
454 -
455 -
456 456  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
457 457  
458 458  
459 -[[image:Screenshot 2025-03-26 at 19.47.52.png]]
528 +[[image:Screenshot 2025-03-16 at 18.39.12.png]]
460 460  
461 461  
462 -
463 -
464 464  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.
465 465  
466 466  
467 -= 6. Creating a Dashboard =
534 += 7. Creating a Dashboard =
468 468  
469 469  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.
470 470  
... ... @@ -474,7 +474,7 @@
474 474  
475 475  First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
476 476  
477 -{{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}}
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}}
478 478  
479 479  
480 480  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
... ... @@ -512,19 +512,15 @@
512 512  
513 513  Configure the **Time series chart** widget as follows:
514 514  
515 -* **Datasource** - select **Device A** device you provisioned.
582 +* **Datasource** - select S31B-NB device you provisioned.
516 516  * **Series**:
517 517  ** **temperature** - you can see this key by default.
518 518  ** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
519 519  * Click on the **Add** button.
520 520  
521 -{{info}}
522 -You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
523 -{{/info}}
588 +[[image:timeseries-1.png||height="491" width="700"]]
524 524  
525 -[[image:Screenshot 2025-03-31 at 06.51.15.png||height="485" width="700"]]
526 526  
527 -
528 528  The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
529 529  
530 530  Click the **Save** button to add the widget to the dashboard.
... ... @@ -537,11 +537,12 @@
537 537  
538 538  
539 539  {{code language="none"}}
540 -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}'
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}'
541 541  
542 -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}'
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}'
543 543  
544 -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}'
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 +
545 545  {{/code}}
546 546  
547 547  The chart will update with the values in realtime, as shown in the below image.
... ... @@ -550,7 +550,7 @@
550 550  [[image:timeseries-4.png||height="316" width="700"]]
551 551  
552 552  
553 -= 8. Configure Physical NB-IoT Sensor =
617 += 8. Configure NB-IoT Sensor =
554 554  
555 555  
556 556  Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
... ... @@ -572,7 +572,13 @@
572 572  
573 573  
574 574  
575 -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.
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**.
576 576  
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}}
577 577  
578 578  [[image:image-4.png]]
646 +
647 +
648 +
Screenshot 2025-03-26 at 18.15.08.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -92.2 KB
Content
Screenshot 2025-03-26 at 19.47.52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -168.4 KB
Content
Screenshot 2025-03-26 at 19.49.31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -133.0 KB
Content
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
Screenshot 2025-04-21 122154.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -21.2 KB
Content
Screenshot 2025-04-21 122909.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -59.9 KB
Content
Screenshot 2025-04-21 122936.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
add-integartion-connection.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -110.3 KB
Content
add-integartion-connetcion.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -146.0 KB
Content
add-integration-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -63.1 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
device-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -34.5 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
integrations-pending.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -19.8 KB
Content
mqtt-uplink-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -75.3 KB
Content
new-device-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -34.7 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