Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 204.1
edited by Dilisi S
on 2025/04/21 16:49
Change comment: April 21 edits - part 1
To version 140.1
edited by Dilisi S
on 2025/03/09 03:42
Change comment: Uploaded new attachment "dashboard-3.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -22,10 +22,7 @@
22 22  To complete this tutorial, you need to have the following:
23 23  
24 24  * ThingsBoard cloud account
25 -* MQTT Broker (public or private) such as,
26 -** **[[HiveMQ Cloud>>https://www.hivemq.com]] - You can create a free account to try it or subscribe for a paid account. - We use HiveMQ Cloud as the MQTT broker to build example in this tutorial.**
27 -** [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] - The public MQTT server is only used for MOTT learning and testing, and should not be used in the production environment.
28 -** [[lns1.thingseye.io>>http://lns1.thingseye.io/]] - This is Dragino's MQTT broker, which requires a CA certificate to use.
25 +* HiveMQ Cloud account
29 29  
30 30  == 2.1 ThingsBoard Cloud ==
31 31  
... ... @@ -69,9 +69,7 @@
69 69  
70 70  == 2.2 HiveMQ Cloud ==
71 71  
72 -=== 2.2.1 HiveMQ Cloud ===
73 73  
74 -
75 75  Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
76 76  
77 77  Click on the **Start Free** button.
... ... @@ -146,128 +146,144 @@
146 146  You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
147 147  
148 148  
149 -=== 2.2.2 emqx ===
144 += 3. Data Converters =
150 150  
151 151  
152 -The [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] public MQTT server is only used for MOTT learning and testing, and should not be used in the production environment.
147 +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.
153 153  
154 154  
155 -[[image:emqx.png||height="420" width="500"]]
150 +== 3.1 Uplink ==
156 156  
157 157  
158 -=== 2.2.3 Ins1.thingseye.io ===
153 +In the left navigation, click **Integrations center**, and then click **Data converters**.
159 159  
160 -[[lns1.thingseye.io>>http://lns1.thingseye.io/]] is the Dragino's MQTT broker, which requires a CA certificate file, Certificate file, and the Private key file to use.
161 161  
162 -If customers need to use this MQTT connection with ThingsBoard, they need to contact the TE team to obtain three license files.
163 163  
164 -[[image:ins1.png||height="310" width="500"]]
157 +[[image:data-converters-list-empty.png]]
165 165  
166 166  
160 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
167 167  
168 -= 3. Data Converters =
169 169  
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.
164 +[[image:create-new-converter-menu.png||height="259" width="500"]]
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  
167 +The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
175 175  
176 -== 3.1 Uplink ==
169 +Click on the **TBEL** button if not selected it by default. Delete the existing decoder function in the code editor. Now copy and paste the following decoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
177 177  
171 +{{code language="JavaScript"}}
172 +/** Decoder **/
178 178  
179 -In the left navigation, click **Integrations center**, and then click **Data converters**.
174 +// decode payload to string
175 +var payloadStr = decodeToString(payload);
176 +var data = JSON.parse(payloadStr);
180 180  
178 +var deviceName = metadata.topic.split("/")[3];
179 +// decode payload to JSON
180 +var deviceType = 'sensor';
181 181  
182 -[[image:data-converters-list-empty.png]]
182 +// Result object with device attributes/telemetry data
183 +var result = {
184 + deviceName: deviceName,
185 + deviceType: deviceType,
186 + attributes: {
187 + integrationName: metadata['integrationName'],
188 + },
189 + telemetry: {
190 + temperature: data.temperature,
191 + humidity: data.humidity,
192 + }
193 +};
183 183  
195 +/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
184 184  
185 -On the **Data converters** page, click on the ‘**+**’ button, and then click on **Create new converter** from the dropdown menu.
197 +return result;
198 +{{/code}}
186 186  
187 187  
201 +Click on the **Add** button.
188 188  
189 -[[image:create-new-converter-menu.png||height="259" width="500"]]
190 190  
191 191  
192 -The **Add data converter** window appears.
205 +[[image:add-uplink-data-converter.png||height="529" width="500"]]
193 193  
194 -Name it ‘**MQTT Uplink Converter**’ and select the Type as **Uplink**.
195 195  
196 -Click on the **TBEL** button if it has not been selected by default.
208 +You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
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.
210 +[[image:data-converter-list-showing-uplink-dc.png]]
199 199  
200 200  
213 +
214 +== 3.2 Downlink ==
215 +
216 +
217 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
218 +
219 +
220 +[[image:create-new-converter-menu.png||width="500"]]
221 +
222 +
223 +
224 +The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
225 +
226 +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.
227 +
228 +
201 201  {{code language="JavaScript"}}
202 -// decode payload to JSON
203 -var pattern = "yyyy/MM/dd HH:mm:ss";
204 -var objdata = {};
205 -var obj1 = {};
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();
230 +// Encode downlink data from incoming Rule Engine message
231 +
232 +// msg - JSON message payload downlink message json
233 +// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
234 +// metadata - list of key-value pairs with additional data about the message
235 +// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
236 +
237 +/** Encoder **/
238 +
239 +var data = {};
240 +
241 +// Process data from incoming message and metadata
242 +
243 +data.tempFreq = msg.temperatureUploadFrequency;
244 +data.humFreq = msg.humidityUploadFrequency;
245 +
246 +data.devSerialNumber = metadata['ss_serialNumber'];
247 +
248 +// Result object with encoded downlink payload
249 +var result = {
250 +
251 + // downlink data content type: JSON, TEXT or BINARY (base64 format)
252 + contentType: "JSON",
253 +
254 + // downlink data
255 + data: JSON.stringify(data),
256 +
257 + // Optional metadata object presented in key/value format
258 + metadata: {
259 + topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
222 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
261 +
252 252  };
263 +
253 253  return result;
254 254  {{/code}}
255 255  
256 256  
257 -Once you modify the decoder function, click on the **Add** button.
268 +Click on the **Add** button.
258 258  
259 259  
260 -[[image:mqtt-uplink-converter.png||height="498" width="500"]]
261 261  
272 +[[image:add-downlink-data-converter.png||height="529" width="500"]]
262 262  
263 263  
264 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
275 +You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
265 265  
266 266  
267 -
268 268  [[image:data-converters-list.png]]
269 269  
270 270  
281 +
271 271  = 4. Add Integration =
272 272  
273 273  
... ... @@ -288,18 +288,17 @@
288 288  **Basic settings:**
289 289  
290 290  * **Integration type**: MQTT
291 -* **Name**: MQTT integration - Device A
302 +* **Name**: MQTT integration NB/CB
292 292  * **Enable integration**: YES
293 -* **Allow create devices or assets**: YES
304 +* **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"]]
299 299  
310 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
300 300  
301 301  
302 -
303 303  **Uplink data converter:**
304 304  
305 305  * Click on the **Select existing** button.
... ... @@ -308,41 +308,40 @@
308 308  Click **Next** button.
309 309  
310 310  
311 -[[image:add-integration-ul-data-converter.png||height="505" width="500"]]
312 312  
322 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
313 313  
314 314  
315 315  **Downlink data converter:**
316 316  
317 -Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
327 +* Click on the **Select existing** button.
328 +* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
318 318  
319 -* Click on the **Skip **button in the Downlink data converter section.
330 +Click **Next** button.
320 320  
321 -Click **Skip** button.
322 322  
323 323  
324 -[[image:integration-dl-skip.png||height="511" width="500"]]
334 +[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
325 325  
326 326  
327 -
328 328  **Connection:**
329 329  
330 -* **Host**: Host URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
339 +* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
331 331  * **Port**: 8883
332 -* **Credentials type**: Basic
341 +* **Credentials**: Basic
342 +* **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.)
345 +* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
337 337  * **QoS:** 0-At most once
338 338  
339 -[[image:add-integartion-connection.png||height="505" width="500"]]
348 +[[image:add-integration-connection.png||height="511" width="500"]]
340 340  
341 341  
342 342  Click on the **Advanced settings** button.
343 343  
344 -* **Clean session:** YES
345 -* **Retained**: YES
353 +* **Clean session:** NO
354 +* **Retained**: NO
346 346  
347 347  [[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
348 348  
... ... @@ -366,8 +366,8 @@
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]]
370 370  
379 +[[image:new-integration-pending.png]]
371 371  
372 372  
373 373  = 5. Verifying the receipt of data from virtual devices =
... ... @@ -375,195 +375,38 @@
375 375  
376 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.
389 +The Mosquitto client publishes messages on the topic v1/devices/[device_name]/telemetry. The [device_name]placeholder can be replaced with any device name, for example, 'S31B-NB'. Then, the MQTT topic would be v1/devices/S31B-NB/telemetry.
382 382  
383 -(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
391 +On the ThingsBoard side, we configure the MQTT topic subscription as v1/devices/+/telemetry. The + wildcard represents any device name and allows ThingsBoard to automatically create (provision) a device with that name, such as S31B-NB, for example.
384 384  
385 -{{code language="none"}}
386 -{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
387 -{{/code}}
388 388  
389 -Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
394 +**The new device is created the first time the MQTT topic is received. For subsequent MQTT topics with the same device name, no duplicate devices will be created.**
390 390  
391 391  
392 -== 5.2 Sending messages ==
397 +For example, if you send two MQTT messages with different device names in the topic:
393 393  
399 +1. v1/devices/**S31B-NB**/telemetry
400 +1. v1/devices/**S31B-CB**/telemetry
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.
402 +ThingsBoard will create two devices named **S31B-NB** and **S31B-CB** in the **//Devices//** section.
396 396  
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}'
399 -{{/code}}
400 400  
401 -If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
405 +The MQTT payload format is as follows, for example:
402 402  
403 -
404 -[[image:integration-active.png]]
405 -
406 -
407 -== 5.3 Viewing messages ==
408 -
409 -
410 -Go back to the **Integrations** page.
411 -
412 -Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
413 -
414 -Click on the **Edit** button (//**pen icon**//).
415 -
416 -Click on the **Disabled** button in the upper-right corner.
417 -
418 -Turn on the **All messages (15 min)** option. This will enable displaying all messages in the **Events** tab. This setting will expire in 15 minutes, and you will need to repeat the same steps if you want to view the messages in the Events tab later.
419 -
420 -Click on the **Apply** button.
421 -
422 -Then click on the **Apply changes** (//**tick icon**//) button.
423 -
424 -
425 -[[image:debug-enabled.png||height="301" width="700"]]
426 -
427 -
428 -
429 -
430 -Now go to the **Events** tab.
431 -
432 -Select the **Event type** as **Debug** from the dropdown list.
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:
435 -
436 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}'
408 +{"temperature":10.4, "humidity":85}
438 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.
441 441  
412 +== 5.2 Sending messages ==
442 442  
443 -[[image:Screenshot 2025-03-26 at 19.49.31.png]]
444 444  
415 +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 10.4 and 85, respectively. This payload is also (technically) known as telemetry.
445 445  
446 -
447 -Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
448 -
449 -
450 -[[image:Screenshot 2025-03-26 at 19.47.52.png]]
451 -
452 -
453 -
454 -
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 -
457 -
458 -= 6. Creating a Dashboard =
459 -
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 -
462 -
463 -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.
464 -
465 -
466 -First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
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}}
469 -
470 -
471 -In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
472 -
473 -
474 -[[image:dashboard-1.png]]
475 -
476 -
477 -In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
478 -
479 -Click on the **Add** button.
480 -
481 -
482 -[[image:dashboard-2.png||height="526" width="500"]]
483 -
484 -
485 -Click on the **Add widget / Add new widget** button.
486 -
487 -
488 -[[image:dashboard-3.png]]
489 -
490 -
491 -In the **Select widgets bundle** window, click **Charts**.
492 -
493 -
494 -[[image:dashboard-4.png||height="537" width="700"]]
495 -
496 -
497 -
498 -In the **Charts: select widget** window, click **Time series chart**.
499 -
500 -
501 -[[image:dashboard-5.png||height="525" width="700"]]
502 -
503 -
504 -Configure the **Time series chart** widget as follows:
505 -
506 -* **Datasource** - select **Device A** device you provisioned.
507 -* **Series**:
508 -** **temperature** - you can see this key by default.
509 -** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
510 -* Click on the **Add** button.
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}}
515 -
516 -[[image:Screenshot 2025-03-31 at 06.51.15.png||height="485" width="700"]]
517 -
518 -
519 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
520 -
521 -Click the **Save** button to add the widget to the dashboard.
522 -
523 -
524 -[[image:timeseries-3.png||height="347" width="700"]]
525 -
526 -
527 -Now send the following MQTT messages from the terminal to simulate the data.
528 -
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}'
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}'
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}'
418 +mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/SN-001/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":10.4, "humidity":85}'
536 536  {{/code}}
537 537  
538 -The chart will update with the values in realtime, as shown in the below image.
539 -
540 -
541 -[[image:timeseries-4.png||height="316" width="700"]]
542 -
543 -
544 -= 8. Configure Physical NB-IoT Sensor =
545 -
546 -
547 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
548 -
549 -First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
550 -
551 -
552 -**AT Commands**
553 -
554 -* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
555 -* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
556 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
557 -* **AT+CLIENT=null**
558 -* **AT+UNAME=<MQTT Username>**
559 -* **AT+PWD=<MQTT Password>**
560 -* **AT+SERVADDR=<Broker address, Port>**
561 -
562 -Test your uplink by pressing the ACT button for 1 second.
563 -
564 -
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.
567 -
568 -
569 -[[image:image-4.png]]
421 +If the integration was performed without errors, after the transmission of the first telemetry, a new device with the name “S31B-NB” will appear in the Devices → All. Also, you can verify the input and output data, respectively, before and after conversion in Data converters → UDP Uplink Converter NB/CB → Events.
Screenshot 2025-03-16 at 18.38.59.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -221.2 KB
Content
Screenshot 2025-03-16 at 18.39.12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -211.9 KB
Content
Screenshot 2025-03-18 at 09.23.10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -78.7 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-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 +124.4 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
dashboard-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -803.7 KB
Content
dashboard-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -476.1 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
emqx.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -39.1 KB
Content
image-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -96.0 KB
Content
ins1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -28.8 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
mqtt-uplink.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -175.1 KB
Content
new-device.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
timeseries-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -179.1 KB
Content
timeseries-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -174.2 KB
Content
timeseries-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -159.0 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