Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 221.1
edited by Dilisi S
on 2025/04/23 01:38
Change comment: April 22 edits
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,11 +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 -** [[ThingsBoard MQTT broker>>https://thingsboard.io/docs/mqtt-broker/]] (TBMQ)
27 -** **[[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.**
28 -** [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] - The public MQTT server is only used for MQTT learning and testing, and should not be used in the production environment.
29 -** [[lns1.thingseye.io>>http://lns1.thingseye.io/]] - This is Dragino's MQTT broker, which requires a CA certificate to use.
25 +* HiveMQ Cloud account
30 30  
31 31  == 2.1 ThingsBoard Cloud ==
32 32  
... ... @@ -68,19 +68,9 @@
68 68  [[image:thingsboard-6.png||height="244" width="500"]]
69 69  
70 70  
71 -== 2.2 MQTT Brokers ==
67 +== 2.2 HiveMQ Cloud ==
72 72  
73 -This section introduces some MQTT brokers that you can use to publish messages from the device side and subscribe from the ThingsBoard side.
74 74  
75 -
76 -=== 2.2.1 ThingsBoard MQTT broker (TBMQ) ===
77 -
78 -The complete instructions for installing, configuring, and using the TBMQ can be found [[here>>https://thingsboard.io/docs/mqtt-broker/getting-started/]].
79 -
80 -
81 -=== 2.2.2 HiveMQ Cloud ===
82 -
83 -
84 84  Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
85 85  
86 86  Click on the **Start Free** button.
... ... @@ -155,128 +155,144 @@
155 155  You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
156 156  
157 157  
158 -=== 2.2.3 emqx ===
144 += 3. Data Converters =
159 159  
160 160  
161 -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.
162 162  
163 163  
164 -[[image:emqx.png||height="420" width="500"]]
150 +== 3.1 Uplink ==
165 165  
166 166  
167 -=== 2.2.4 Ins1.thingseye.io ===
153 +In the left navigation, click **Integrations center**, and then click **Data converters**.
168 168  
169 -[[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.
170 170  
171 -If customers need to use this MQTT connection with ThingsBoard, they need to contact the TE team to obtain three license files.
172 172  
173 -[[image:ins1.png||height="310" width="500"]]
157 +[[image:data-converters-list-empty.png]]
174 174  
175 175  
160 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
176 176  
177 -= 3. Data Converters =
178 178  
179 179  
180 -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"]]
181 181  
182 -**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**.
183 183  
167 +The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
184 184  
185 -== 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.
186 186  
171 +{{code language="JavaScript"}}
172 +/** Decoder **/
187 187  
188 -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);
189 189  
178 +var deviceName = metadata.topic.split("/")[3];
179 +// decode payload to JSON
180 +var deviceType = 'sensor';
190 190  
191 -[[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 +};
192 192  
195 +/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
193 193  
194 -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}}
195 195  
196 196  
201 +Click on the **Add** button.
197 197  
198 -[[image:create-new-converter-menu.png||height="259" width="500"]]
199 199  
200 200  
201 -The **Add data converter** window appears.
205 +[[image:add-uplink-data-converter.png||height="529" width="500"]]
202 202  
203 -Name it ‘**MQTT Uplink Converter**’ and select the Type as **Uplink**.
204 204  
205 -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.
206 206  
207 -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]]
208 208  
209 209  
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 +
210 210  {{code language="JavaScript"}}
211 -// decode payload to JSON
212 -var pattern = "yyyy/MM/dd HH:mm:ss";
213 -var objdata = {};
214 -var obj1 = {};
215 -var data = decodeToJson(payload);
216 -var deviceName = data.IMEI;
217 -data.remove("IMEI");
218 -var modelname = "Dragino "+ data.Model;
219 -//var mod = data.mod
220 -data.remove("Model");
221 -//delete data.mod
222 -var timestamp = new Date().getTime();
223 -foreach (entry: data.entrySet()) {
224 - var key = entry.getKey();
225 - var value = entry.getValue();
226 - //objdata[key] = data[key]
227 - if(key.matches("^-?\\d+$")){ //is number
228 - obj1[key]=data[key];
229 - var index = obj1[key].length-1;
230 - 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'
231 231   }
232 - else if (key==="bat"||key==="BAT"){
233 - objdata["battery"] = data[key];
234 - }
235 - else{
236 - objdata[key] = data[key];
237 -}}
238 -var listdata = [{"ts":timestamp,"values":objdata}];
239 -foreach ( entry1: obj1.entrySet()){
240 - var key1 = entry1.getKey();
241 - var value1 = entry1.getValue();
242 - var index = obj1[key1].length-1;
243 - var ts = obj1[key1][index];
244 - if (modelname=="Dragino RS485-NB"){
245 - listdata.push({"ts":ts,"values":{"Payload":obj1[key1][0]}});
246 - }
247 - else{
248 - listdata.push({"ts":ts,"values":{"values":obj1[key1]}});
249 - }
250 -}
251 - var result = {
252 - deviceName: deviceName,
253 - deviceType: modelname,
254 - attributes: {
255 - model: modelname
256 - //customerName: "NB-CB",
257 - //groupName: "NB-CB",
258 - //integrationName: metadata['integrationName']
259 - },
260 - telemetry: listdata
261 +
261 261  };
263 +
262 262  return result;
263 263  {{/code}}
264 264  
265 265  
266 -Once you modify the decoder function, click on the **Add** button.
268 +Click on the **Add** button.
267 267  
268 268  
269 -[[image:mqtt-uplink-converter.png||height="498" width="500"]]
270 270  
272 +[[image:add-downlink-data-converter.png||height="529" width="500"]]
271 271  
272 272  
273 -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.
274 274  
275 275  
276 -
277 277  [[image:data-converters-list.png]]
278 278  
279 279  
281 +
280 280  = 4. Add Integration =
281 281  
282 282  
... ... @@ -297,15 +297,15 @@
297 297  **Basic settings:**
298 298  
299 299  * **Integration type**: MQTT
300 -* **Name**: MQTT integration
302 +* **Name**: MQTT integration NB/CB
301 301  * **Enable integration**: YES
302 -* **Allow create devices or assets**: YES
304 +* **Allows create devices or assets**: YES
303 303  
304 304  Click **Next** button.
305 305  
306 306  
307 307  
308 -[[image:add-integration-part-1.png||height="483" width="500"]]
310 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
309 309  
310 310  
311 311  **Uplink data converter:**
... ... @@ -317,40 +317,39 @@
317 317  
318 318  
319 319  
320 -[[image:add-integration-part-2.png||height="484" width="500"]]
322 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
321 321  
322 322  
323 323  **Downlink data converter:**
324 324  
325 -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.
326 326  
327 -* Click on the **Skip **button in the Downlink data converter section.
330 +Click **Next** button.
328 328  
329 -Click **Skip** button.
330 330  
331 331  
332 -[[image:integration-dl-skip.png||height="511" width="500"]]
334 +[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
333 333  
334 334  
335 -
336 336  **Connection:**
337 337  
338 -* **Host**: Host URL (Eg, **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
339 -* **Port**: 8883 (the port number may differ based on your MQTT broker)
340 -* **Credentials type**: Basic
339 +* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
340 +* **Port**: 8883
341 +* **Credentials**: Basic
342 +* **Enable SSL**: YES
341 341  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
342 342  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
343 -* **Enable SSL**: YES
344 -* **Topic**: # (the # symbol indicates that it filters all topics).
345 +* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
345 345  * **QoS:** 0-At most once
346 346  
347 -[[image:add-integration-4.png||height="484" width="500"]]
348 +[[image:add-integration-connection.png||height="511" width="500"]]
348 348  
349 349  
350 350  Click on the **Advanced settings** button.
351 351  
352 -* **Clean session:** YES
353 -* **Retained**: YES
353 +* **Clean session:** NO
354 +* **Retained**: NO
354 354  
355 355  [[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
356 356  
... ... @@ -375,7 +375,7 @@
375 375  
376 376  
377 377  
378 -[[image:integrations-pending.png]]
379 +[[image:new-integration-pending.png]]
379 379  
380 380  
381 381  = 5. Verifying the receipt of data from virtual devices =
... ... @@ -383,186 +383,38 @@
383 383  
384 384  == 5.1 How does it work? ==
385 385  
386 -
387 387  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.
388 388  
389 -The Mosquitto client publishes messages (payloads) to a topic - for example, # or device/ts01-nb. You can, of course, use any topic you prefer.
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.
390 390  
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.
391 391  
392 -(% 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.
393 393  
394 -{{code language="none"}}
395 -{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}
396 -{{/code}}
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.**
397 397  
398 398  
399 -== 5.2 Sending messages ==
397 +For example, if you send two MQTT messages with different device names in the topic:
400 400  
399 +1. v1/devices/**S31B-NB**/telemetry
400 +1. v1/devices/**S31B-CB**/telemetry
401 401  
402 -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.
402 +ThingsBoard will create two devices named **S31B-NB** and **S31B-CB** in the **//Devices//** section.
403 403  
404 +
405 +The MQTT payload format is as follows, for example:
406 +
404 404  {{code language="none"}}
405 -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}'
408 +{"temperature":10.4, "humidity":85}
406 406  {{/code}}
407 407  
408 -If the integration was performed without errors, a new device named **350693903995577 **is created in the **Devices **section.
409 409  
412 +== 5.2 Sending messages ==
410 410  
411 -[[image:new-device-1.png]]
412 412  
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.
413 413  
414 -The status of the integration also changes to '**Active**' after the first telemetry transmission.
415 -
416 -
417 -[[image:Screenshot 2025-04-21 122154.png]]
418 -
419 -
420 -
421 -**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.**
422 -
423 -
424 -== 5.3 Viewing messages ==
425 -
426 -
427 -Go back to the **Integrations** page.
428 -
429 -Click on the **MQTT integration** in the **Integrations** page to see its details.
430 -
431 -Click on the **Edit** button (//**pen icon**//).
432 -
433 -Click on the **Disabled** button in the upper-right corner.
434 -
435 -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.
436 -
437 -Click on the **Apply** button.
438 -
439 -Then click on the **Apply changes** (//**tick icon**//) button.
440 -
441 -
442 -
443 -[[image:Screenshot 2025-04-21 122936.png||height="247" width="500"]]
444 -
445 -
446 -Now go to the **Events** tab.
447 -
448 -Select the **Event type** as **Debug** from the dropdown list.
449 -
450 -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:
451 -
452 452  {{code language="none"}}
453 -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}'
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}'
454 454  {{/code}}
455 455  
456 -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.
457 -
458 -
459 -Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
460 -
461 -
462 -
463 -[[image:Screenshot 2025-04-21 122909.png]]
464 -
465 -
466 -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.
467 -
468 -
469 -= 6. Creating a Dashboard =
470 -
471 -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.
472 -
473 -
474 -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.
475 -
476 -
477 -In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
478 -
479 -
480 -[[image:dashboard-1.png]]
481 -
482 -
483 -In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
484 -
485 -Click on the **Add** button.
486 -
487 -
488 -[[image:dashboard-2.png||height="526" width="500"]]
489 -
490 -
491 -Click on the **Add widget / Add new widget** button.
492 -
493 -
494 -[[image:dashboard-3.png]]
495 -
496 -
497 -In the **Select widgets bundle** window, click **Charts**.
498 -
499 -
500 -[[image:dashboard-4.png||height="537" width="700"]]
501 -
502 -
503 -
504 -In the **Charts: select widget** window, click **Time series chart**.
505 -
506 -
507 -[[image:dashboard-5.png||height="525" width="700"]]
508 -
509 -
510 -Configure the **Time series chart** widget as follows:
511 -
512 -* **Datasource** - select **350693903995577 **you provisioned.
513 -* **Series**:
514 -** **temperature** - you can see this key by default.
515 -** **humidity** - Click **Add series** button. Then choose **humidity** for the key, and then type **%** as its unit.
516 -** pressure -  Click **Add series** button. Then choose **humidity** for the key, and then type Pa as its unit.
517 -* Click on the **Add** button.
518 -
519 -{{info}}
520 -You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
521 -{{/info}}
522 -
523 -
524 -
525 -[[image:Screenshot 2025-04-21 123647.png||height="466" width="700"]]
526 -
527 -
528 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
529 -
530 -Click the **Save** button to add the widget to the dashboard.
531 -
532 -
533 -[[image:Screenshot 2025-04-21 124145.png||height="443" width="700"]]
534 -
535 -
536 -**Now send a few MQTT messages from the terminal to simulate the data. Use different values for temperature, humidity, and pressure in each message.**
537 -
538 -**The chart will update with the values in real time, and you will see a live chart similar to this:**
539 -
540 -
541 -[[image:Screenshot 2025-04-21 124054.png||height="441" 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: # -  **You can leave the SUBTOPIC configuration as it is, since we are not sending downlink messages to the device at the moment.
556 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: #**
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 -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.
566 -
567 -
568 -[[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
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-connection.png
Size
... ... @@ -1,1 +1,1 @@
1 -158.1 KB
1 +124.4 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
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
device-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -34.5 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
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
mqtt-uplink.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -175.1 KB
Content
new-device-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -34.7 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