Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 220.1
edited by Dilisi S
on 2025/04/21 18:49
Change comment: April 17 edits - part final
To version 179.1
edited by Dilisi S
on 2025/03/27 01:21
Change comment: There is no comment for this version

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,17 +288,16 @@
288 288  **Basic settings:**
289 289  
290 290  * **Integration type**: MQTT
291 -* **Name**: MQTT integration
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  
336 +[[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  
347 +[[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,16 +326,16 @@
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
365 +* **Host**: Cluster URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
366 +* **Port**: 8883
367 +* **Credentials**: Basic
368 +* **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).
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.)
336 336  * **QoS:** 0-At most once
337 337  
338 -[[image:add-integration-4.png||height="484" width="500"]]
374 +[[image:add-integration-connection.png||height="511" width="500"]]
339 339  
340 340  
341 341  Click on the **Advanced settings** button.
... ... @@ -365,59 +365,55 @@
365 365  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
366 366  
367 367  
404 +[[image:new-integration-pending.png]]
368 368  
369 -[[image:integrations-pending.png]]
370 370  
407 += 6. Verifying the receipt of data from virtual devices =
371 371  
372 -= 5. Verifying the receipt of data from virtual devices =
373 373  
410 +== 6.1 How does it work? ==
374 374  
375 -== 5.1 How does it work? ==
376 376  
377 -
378 378  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.
379 379  
380 -The Mosquitto client publishes messages (payloads) to a topic - for example, # or device/ts01-nb. You can, of course, use any topic you prefer.
415 +The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
381 381  
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.
382 382  
383 -(% 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.
384 -
385 385  {{code language="none"}}
386 -{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}
420 +{"IMEI": "S31B-NB", "temperature": 27, ......}
387 387  {{/code}}
388 388  
423 +Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
389 389  
425 +
390 390  == 5.2 Sending messages ==
391 391  
392 392  
393 -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.
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.
394 394  
395 395  {{code language="none"}}
396 -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}'
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}'
397 397  {{/code}}
398 398  
399 -If the integration was performed without errors, a new device named **350693903995577 **is created in the **Devices **section.
435 +If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
400 400  
401 401  
402 -[[image:new-device-1.png]]
438 +[[image:integration-active.png]]
403 403  
404 404  
405 -The status of the integration also changes to '**Active**' after the first telemetry transmission.
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**.
406 406  
407 407  
408 -[[image:Screenshot 2025-04-21 122154.png]]
444 +[[image:new-device.png]]
409 409  
410 410  
447 +== 6.3 Viewing messages ==
411 411  
412 -**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.**
413 413  
414 -
415 -== 5.3 Viewing messages ==
416 -
417 -
418 418  Go back to the **Integrations** page.
419 419  
420 -Click on the **MQTT integration** in the **Integrations** page to see its details.
452 +Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
421 421  
422 422  Click on the **Edit** button (//**pen icon**//).
423 423  
... ... @@ -430,34 +430,29 @@
430 430  Then click on the **Apply changes** (//**tick icon**//) button.
431 431  
432 432  
465 +[[image:Screenshot 2025-03-18 at 09.23.10.png]]
433 433  
434 -[[image:Screenshot 2025-04-21 122936.png||height="247" width="500"]]
435 435  
436 -
437 437  Now go to the **Events** tab.
438 438  
439 -Select the **Event type** as **Debug** from the dropdown list.
470 +Select the Event type as **Debug** from the dropdown list.
440 440  
441 -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.
442 442  
443 -{{code language="none"}}
444 -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":82, "pressure":1005}'
445 -{{/code}}
446 446  
447 -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]]
448 448  
449 449  
450 450  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
451 451  
452 452  
481 +[[image:Screenshot 2025-03-16 at 18.39.12.png]]
453 453  
454 -[[image:Screenshot 2025-04-21 122909.png]]
455 455  
456 -
457 457  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.
458 458  
459 459  
460 -= 6. Creating a Dashboard =
487 += 7. Creating a Dashboard =
461 461  
462 462  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.
463 463  
... ... @@ -465,6 +465,11 @@
465 465  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.
466 466  
467 467  
495 +First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
496 +
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}}
498 +
499 +
468 468  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
469 469  
470 470  
... ... @@ -500,41 +500,44 @@
500 500  
501 501  Configure the **Time series chart** widget as follows:
502 502  
503 -* **Datasource** - select **350693903995577 **you provisioned.
535 +* **Datasource** - select S31B-NB device you provisioned.
504 504  * **Series**:
505 505  ** **temperature** - you can see this key by default.
506 -** **humidity** - Click **Add series** button. Then choose **humidity** for the key, and then type **%** as its unit.
507 -** pressure -  Click **Add series** button. Then choose **humidity** for the key, and then type Pa as its unit.
538 +** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
508 508  * Click on the **Add** button.
509 509  
510 -{{info}}
511 -You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
512 -{{/info}}
541 +[[image:timeseries-1.png||height="491" width="700"]]
513 513  
514 514  
544 +The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
515 515  
516 -[[image:Screenshot 2025-04-21 123647.png||height="466" width="700"]]
546 +Click the **Save** button to add the widget to the dashboard.
517 517  
518 518  
519 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
549 +[[image:timeseries-3.png||height="347" width="700"]]
520 520  
521 -Click the **Save** button to add the widget to the dashboard.
522 522  
552 +Now send the following MQTT messages from the terminal to simulate the data.
523 523  
524 -[[image:Screenshot 2025-04-21 124145.png||height="443" width="700"]]
525 525  
555 +{{code language="none"}}
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}'
526 526  
527 -**Now send a few MQTT messages from the terminal to simulate the data. Use different values for temperature, humidity, and pressure in each message.**
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}'
528 528  
529 -**The chart will update with the values in real time, and you will see a live chart similar to this:**
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}'
530 530  
562 +{{/code}}
531 531  
532 -[[image:Screenshot 2025-04-21 124054.png||height="441" width="700"]]
564 +The chart will update with the values in realtime, as shown in the below image.
533 533  
534 534  
535 -= 8. Configure Physical NB-IoT Sensor =
567 +[[image:timeseries-4.png||height="316" width="700"]]
536 536  
537 537  
570 += 8. Configure NB-IoT Sensor =
571 +
572 +
538 538  Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
539 539  
540 540  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
... ... @@ -543,18 +543,24 @@
543 543  **AT Commands**
544 544  
545 545  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
546 -* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: # -  **You can leave the SUBTOPIC configuration as it is, since we are not sending downlink messages to the device at the moment.
547 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: #**
581 +* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
582 +* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
548 548  * **AT+CLIENT=null**
549 549  * **AT+UNAME=<MQTT Username>**
550 550  * **AT+PWD=<MQTT Password>**
551 551  * **AT+SERVADDR=<Broker address, Port>**
552 552  
553 -
554 554  Test your uplink by pressing the ACT button for 1 second.
555 555  
556 556  
557 -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.
558 558  
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**.
559 559  
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}}
597 +
560 560  [[image:image-4.png]]
599 +
600 +
601 +
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
Screenshot 2025-04-21 123647.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
Screenshot 2025-04-21 124054.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -60.4 KB
Content
Screenshot 2025-04-21 124145.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -50.9 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