Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 208.1
edited by Dilisi S
on 2025/04/21 17:06
Change comment: There is no comment for this version
To version 168.1
edited by Dilisi S
on 2025/03/19 03:40
Change comment: Uploaded new attachment "image-4.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -164,15 +164,12 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
167 -
168 168  = 3. Data Converters =
169 169  
170 170  
171 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 174  
175 -
176 176  == 3.1 Uplink ==
177 177  
178 178  
... ... @@ -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.
182 +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,140 @@
189 189  [[image:create-new-converter-menu.png||height="259" width="500"]]
190 190  
191 191  
192 -The **Add data converter** window appears.
189 +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**.
191 +Click on the **JavaScript** button.
195 195  
196 -Click on the **TBEL** button if it has not been selected by default.
193 +Delete the default decoder function in the code editor. Now copy and paste the following decoder function written in **JavaScript** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
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.
199 199  
200 -
201 201  {{code language="JavaScript"}}
197 +//Version: 0.1
198 +// decode payload to string
199 +var payloadStr = decodeToString(payload);
200 +
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;
206 +delete data.IMEI;
207 +var modelname = "Dragino " + data.Model;
210 210  //var mod = data.mod
211 -data.remove("Model");
209 +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();
212 +
213 +for (var key in data) {
214 +
215 + if (Number(key)) {
216 + obj1[key] = data[key];
217 + obj1[key][obj1[key].length - 1] = Number(new Date(
218 + obj1[key][obj1[key].length - 1]));
219 +
222 222   }
223 - else if (key==="bat"||key==="BAT"){
224 - objdata["battery"] = data[key];
221 +//Alec submitted25/02/25
222 +//turn old key into new
223 + else if (key === "Reading") {
224 + objdata["reading"] = data[key];
225 + } else if (key === "work mode") {
226 + objdata["work_mode"] = data[key];
227 + } else if (key === "hum") {
228 + objdata["humidity"] = data[key];
229 + }else if (key === "hum2") {
230 + objdata["humidity2"] = data[key];
231 + } else if (key === "hum3") {
232 + objdata["humidity3"] = data[key];
233 + } else if (key === "tem") {
234 + objdata["temperature"] = data[key];
235 + } else if (key === "tem2") {
236 + objdata["temperature2"] = data[key];
237 + } else if (key === "tem3") {
238 + objdata["temperature3"] = data[key];
239 + } else if (key === "DS18B20_Temp") {
240 + objdata["temperature_pro"] = data[key];
241 + } else if (key === "ds18b20_temperature") {
242 + objdata["temperature_pro"] = data[key];
243 + } else if (key === "DS18B20_temperature_pro") {
244 + objdata["temperature_pro"] = data[key];
245 + } else if (key === "tdc send flag") {
246 + objdata["tdc_send_flag"] = data[key];
247 + } else if (key === "trigger mode") {
248 + objdata["trigger_mode"] = data[key];
249 + } else if (key === "soil dielectric constant") {
250 + objdata["soil_dielectric_constant"] = data[key];
251 + } else if (key === "door open num") {
252 + objdata["door_open_num"] = data[key];
253 + } else if (key === "door duration") {
254 + objdata["door_duration"] = data[key];
255 + } else if (key === "count time") {
256 + objdata["count_time"] = data[key];
257 + } else if (key === "last open time2") {
258 + objdata["last_open_time2"] = data[key];
259 + } else if (key === "last open time3") {
260 + 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]}});
262 +//Alec submitted25/02/25
263 + else {
264 + objdata[key] = data[key]
237 237   }
238 - else{
239 - listdata.push({"ts":ts,"values":{"values":obj1[key1]}});
266 +}
267 +var listdata = [{
268 + "ts": timestamp,
269 + "values": objdata
270 +}]
271 +for (var key1 in obj1) {
272 + if (modelname == "Dragino RS485-NB") {
273 + listdata.push({
274 + "ts": obj1[key1][obj1[key1].length - 1],
275 + "values": {
276 + "Payload": obj1[key1][0],
277 + }
278 + })
279 + } else {
280 + listdata.push({
281 + "ts": obj1[key1][obj1[key1].length - 1],
282 + "values": {
283 + "values": obj1[key1]
284 + },
285 + })
240 240   }
241 241  }
242 - var result = {
288 +var result = {
289 +
243 243   deviceName: deviceName,
244 244   deviceType: modelname,
245 245   attributes: {
246 - model: modelname
293 + model: modelname,
247 247   //customerName: "NB-CB",
248 248   //groupName: "NB-CB",
249 249   //integrationName: metadata['integrationName']
297 +
250 250   },
251 251   telemetry: listdata
252 -};
300 +}
301 +
302 +function decodeToString(payload) {
303 + return String.fromCharCode.apply(String, payload);
304 +}
305 +
306 +function decodeToJson(payload) {
307 + // covert payload to string.
308 + var str = decodeToString(payload);
309 +
310 + // parse string to JSON
311 + var data = JSON.parse(str);
312 + return data;
313 +}
314 +
253 253  return result;
254 254  {{/code}}
255 255  
256 256  
257 -Once you modify the decoder function, click on the **Add** button.
319 +Click on the **Add** button.
258 258  
259 259  
260 -[[image:mqtt-uplink-converter.png||height="498" width="500"]]
322 +[[image:mqtt-uplink.png||width="500"]]
261 261  
262 262  
263 263  
... ... @@ -264,7 +264,72 @@
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  
329 +[[image:data-converter-list-showing-uplink-dc.png]]
267 267  
331 +
332 +== 3.2 Downlink ==
333 +
334 +
335 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
336 +
337 +
338 +[[image:create-new-converter-menu.png||width="500"]]
339 +
340 +
341 +
342 +The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
343 +
344 +Click on the **TBEL** button if not selected it by default. Now copy and paste the following encoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This encoder function is compatible for both NB and CB series devices.
345 +
346 +
347 +{{code language="JavaScript"}}
348 +// Encode downlink data from incoming Rule Engine message
349 +
350 +// msg - JSON message payload downlink message json
351 +// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
352 +// metadata - list of key-value pairs with additional data about the message
353 +// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
354 +
355 +/** Encoder **/
356 +
357 +var data = {};
358 +
359 +// Process data from incoming message and metadata
360 +
361 +data.tempFreq = msg.temperatureUploadFrequency;
362 +data.humFreq = msg.humidityUploadFrequency;
363 +
364 +data.devSerialNumber = metadata['ss_serialNumber'];
365 +
366 +// Result object with encoded downlink payload
367 +var result = {
368 +
369 + // downlink data content type: JSON, TEXT or BINARY (base64 format)
370 + contentType: "JSON",
371 +
372 + // downlink data
373 + data: JSON.stringify(data),
374 +
375 + // Optional metadata object presented in key/value format
376 + metadata: {
377 + topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
378 + }
379 +
380 +};
381 +
382 +return result;
383 +{{/code}}
384 +
385 +
386 +Click on the **Add** button.
387 +
388 +
389 +[[image:add-downlink-data-converter.png||height="529" width="500"]]
390 +
391 +
392 +You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
393 +
394 +
268 268  [[image:data-converters-list.png]]
269 269  
270 270  
... ... @@ -288,17 +288,16 @@
288 288  **Basic settings:**
289 289  
290 290  * **Integration type**: MQTT
291 -* **Name**: MQTT integration
418 +* **Name**: MQTT integration NB/CB
292 292  * **Enable integration**: YES
293 -* **Allow create devices or assets**: YES
420 +* **Allows create devices or assets**: YES
294 294  
295 295  Click **Next** button.
296 296  
297 297  
425 +[[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,39 +307,34 @@
307 307  Click **Next** button.
308 308  
309 309  
436 +[[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 -Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
441 +* Click on the **Select existing** button.
442 +* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
317 317  
318 -* Click on the **Skip **button in the Downlink data converter section.
444 +Click **Next** button.
319 319  
320 -Click **Skip** button.
321 321  
447 +[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
322 322  
323 -[[image:integration-dl-skip.png||height="511" width="500"]]
324 324  
325 -
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
452 +* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
453 +* **Port**: 8883
454 +* **Credentials**: Basic
455 +* **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).
458 +* **Topic: v1/devices/+/telemetry** (the + replaces any 'device name' will create a device in the Entities -> Devices)
336 336  * **QoS:** 0-At most once
337 337  
461 +[[image:add-integration-connection.png||height="511" width="500"]]
338 338  
339 339  
340 -[[image:add-integration-4.png||height="484" width="500"]]
341 -
342 -
343 343  Click on the **Advanced settings** button.
344 344  
345 345  * **Clean session:** YES
... ... @@ -367,8 +367,8 @@
367 367  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
368 368  
369 369  
370 -[[image:integration-added.png]]
371 371  
492 +[[image:new-integration-pending.png]]
372 372  
373 373  
374 374  = 5. Verifying the receipt of data from virtual devices =
... ... @@ -379,24 +379,24 @@
379 379  
380 380  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.
381 381  
382 -The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
503 +The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
383 383  
384 -(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
505 +(% 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.
385 385  
386 386  {{code language="none"}}
387 -{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
508 +{"IMEI": "S31B-NB", "temperature": 27, ......}
388 388  {{/code}}
389 389  
390 -Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
511 +Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
391 391  
392 392  
393 393  == 5.2 Sending messages ==
394 394  
395 395  
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.
517 +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.
397 397  
398 398  {{code language="none"}}
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}'
520 +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}'
400 400  {{/code}}
401 401  
402 402  If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
... ... @@ -405,9 +405,16 @@
405 405  [[image:integration-active.png]]
406 406  
407 407  
529 +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**.
530 +
531 +
532 +[[image:new-device.png]]
533 +
534 +
408 408  == 5.3 Viewing messages ==
409 409  
410 410  
538 +
411 411  Go back to the **Integrations** page.
412 412  
413 413  Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
... ... @@ -423,36 +423,25 @@
423 423  Then click on the **Apply changes** (//**tick icon**//) button.
424 424  
425 425  
426 -[[image:debug-enabled.png||height="301" width="700"]]
554 +[[image:Screenshot 2025-03-18 at 09.23.10.png]]
427 427  
428 428  
429 -
430 -
431 431  Now go to the **Events** tab.
432 432  
433 -Select the **Event type** as **Debug** from the dropdown list.
559 +Select the Event type as **Debug** from the dropdown list.
434 434  
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:
561 +Now you can see all the Uplink messages you are simulating through the MQTT broker. The status should
436 436  
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}}
440 440  
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.
564 +[[image:Screenshot 2025-03-16 at 18.38.59.png]]
442 442  
443 443  
444 -[[image:Screenshot 2025-03-26 at 19.49.31.png]]
445 -
446 -
447 -
448 448  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
449 449  
450 450  
451 -[[image:Screenshot 2025-03-26 at 19.47.52.png]]
570 +[[image:Screenshot 2025-03-16 at 18.39.12.png]]
452 452  
453 453  
454 -
455 -
456 456  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.
457 457  
458 458  
... ... @@ -464,11 +464,6 @@
464 464  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.
465 465  
466 466  
467 -First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
468 -
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}}
470 -
471 -
472 472  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
473 473  
474 474  
... ... @@ -504,19 +504,15 @@
504 504  
505 505  Configure the **Time series chart** widget as follows:
506 506  
507 -* **Datasource** - select **Device A** device you provisioned.
619 +* **Datasource** - select S31B-NB device you provisioned.
508 508  * **Series**:
509 509  ** **temperature** - you can see this key by default.
510 510  ** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
511 511  * Click on the **Add** button.
512 512  
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}}
625 +[[image:timeseries-1.png||height="491" width="700"]]
516 516  
517 -[[image:Screenshot 2025-03-31 at 06.51.15.png||height="485" width="700"]]
518 518  
519 -
520 520  The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
521 521  
522 522  Click the **Save** button to add the widget to the dashboard.
... ... @@ -529,11 +529,12 @@
529 529  
530 530  
531 531  {{code language="none"}}
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}'
640 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":20, "humidity":70}'
533 533  
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}'
642 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":22, "humidity":71}'
535 535  
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}'
644 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":18, "humidity":79}'
645 +
537 537  {{/code}}
538 538  
539 539  The chart will update with the values in realtime, as shown in the below image.
... ... @@ -542,10 +542,10 @@
542 542  [[image:timeseries-4.png||height="316" width="700"]]
543 543  
544 544  
545 -= 8. Configure Physical NB-IoT Sensor =
654 += 7. Configure NB-IoT Sensor =
546 546  
547 547  
548 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
657 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
549 549  
550 550  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
551 551  
... ... @@ -553,8 +553,8 @@
553 553  **AT Commands**
554 554  
555 555  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
556 -* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
557 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
665 +* **AT+SUBTOPIC=<MQTT topic>**
666 +* **AT+PUBTOPIC=<MQTT topic>**
558 558  * **AT+CLIENT=null**
559 559  * **AT+UNAME=<MQTT Username>**
560 560  * **AT+PWD=<MQTT Password>**
... ... @@ -561,10 +561,7 @@
561 561  * **AT+SERVADDR=<Broker address, Port>**
562 562  
563 563  Test your uplink by pressing the ACT button for 1 second.
564 -
565 565  
566 566  
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.
568 568  
569 -
570 -[[image:image-4.png]]
676 +
Screenshot 2025-03-16 at 18.39.12.png
Size
... ... @@ -1,1 +1,1 @@
1 -211.9 KB
1 +277.0 KB
Content
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
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-connection.png
Size
... ... @@ -1,1 +1,1 @@
1 -158.1 KB
1 +153.2 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
integration-dl-skip.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -105.5 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