Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 124.1
edited by Dilisi S
on 2025/03/08 20:45
Change comment: Uploaded new attachment "thingsboard-3.png", version {1}
To version 205.1
edited by Dilisi S
on 2025/04/21 16:52
Change comment: Uploaded new attachment "add-integration-part-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -22,17 +22,56 @@
22 22  To complete this tutorial, you need to have the following:
23 23  
24 24  * ThingsBoard cloud account
25 -* HiveMQ 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.
26 26  
27 -
28 28  == 2.1 ThingsBoard Cloud ==
29 29  
30 30  
31 -Add details here
33 +Go to [[https:~~/~~/thingsboard.io/>>https://thingsboard.io/]]
32 32  
35 +Click on the **Try it now**.
36 +
37 +
38 +[[image:thingsboard-1.png]]
39 +
40 +
41 +Select either the **North America** or **Europe** region. Here, we use the Europe region.
42 +
43 +[[image:thingsboard-2.png]]
44 +
45 +
46 +You can sign up with your **Google**, **GitHub**, **Facebook**, or **Apple** account. If not you can create an account with providing your **name**, **email address** and a **password**.
47 +
48 +Click on the **Sign up** button.
49 +
50 +[[image:thingsboard-3.png||height="651" width="500"]]
51 +
52 +
53 +You will be navigated to the following page.
54 +
55 +[[image:thingsboard-5.png||height="109" width="500"]]
56 +
57 +
58 +simultaneously, you will receive an email to confirm your email address. Click on the **Activate Your Account** button.
59 +
60 +
61 +[[image:thingsboard-4.png||height="249" width="500"]]
62 +
63 +
64 +Now losing to the account using your credentials:
65 +
66 +
67 +[[image:thingsboard-6.png||height="244" width="500"]]
68 +
69 +
33 33  == 2.2 HiveMQ Cloud ==
34 34  
72 +=== 2.2.1 HiveMQ Cloud ===
35 35  
74 +
36 36  Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
37 37  
38 38  Click on the **Start Free** button.
... ... @@ -107,12 +107,33 @@
107 107  You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
108 108  
109 109  
149 +=== 2.2.2 emqx ===
150 +
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.
153 +
154 +
155 +[[image:emqx.png||height="420" width="500"]]
156 +
157 +
158 +=== 2.2.3 Ins1.thingseye.io ===
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 +
162 +If customers need to use this MQTT connection with ThingsBoard, they need to contact the TE team to obtain three license files.
163 +
164 +[[image:ins1.png||height="310" width="500"]]
165 +
166 +
167 +
110 110  = 3. Data Converters =
111 111  
112 112  
113 113  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.
114 114  
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**.
115 115  
175 +
116 116  == 3.1 Uplink ==
117 117  
118 118  
... ... @@ -119,11 +119,10 @@
119 119  In the left navigation, click **Integrations center**, and then click **Data converters**.
120 120  
121 121  
122 -
123 123  [[image:data-converters-list-empty.png]]
124 124  
125 125  
126 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
185 +On the **Data converters** page, click on the ‘**+**’ button, and then click on **Create new converter** from the dropdown menu.
127 127  
128 128  
129 129  
... ... @@ -130,228 +130,381 @@
130 130  [[image:create-new-converter-menu.png||height="259" width="500"]]
131 131  
132 132  
133 -The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
192 +The **Add data converter** window appears.
134 134  
135 -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.
194 +Name it ‘**MQTT Uplink Converter**’ and select the Type as **Uplink**.
136 136  
137 -{{code language="JavaScript"}}
138 -/** Decoder **/
196 +Click on the **TBEL** button if it has not been selected by default.
139 139  
140 -// decode payload to string
141 -var payloadStr = decodeToString(payload);
142 -var data = JSON.parse(payloadStr);
198 +Replace the default TBEL decoder function with the following universal TBEL decoder function, which decodes MQTT payload from any Dragino NB-IoT device.
143 143  
144 -var deviceName = metadata.topic.split("/")[3];
145 -// decode payload to JSON
146 -var deviceType = 'sensor';
147 147  
148 -// Result object with device attributes/telemetry data
149 -var result = {
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();
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 = {
150 150   deviceName: deviceName,
151 - deviceType: deviceType,
244 + deviceType: modelname,
152 152   attributes: {
153 - integrationName: metadata['integrationName'],
246 + model: modelname
247 + //customerName: "NB-CB",
248 + //groupName: "NB-CB",
249 + //integrationName: metadata['integrationName']
154 154   },
155 - telemetry: {
156 - temperature: data.temperature,
157 - humidity: data.humidity,
158 - }
251 + telemetry: listdata
159 159  };
160 -
161 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
162 -
163 163  return result;
164 164  {{/code}}
165 165  
166 166  
167 -Click on the **Add** button.
257 +Once you modify the decoder function, click on the **Add** button.
168 168  
169 169  
260 +[[image:mqtt-uplink-converter.png||height="498" width="500"]]
170 170  
171 -[[image:add-uplink-data-converter.png||height="529" width="500"]]
172 172  
173 173  
174 174  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
175 175  
176 -[[image:data-converter-list-showing-uplink-dc.png]]
177 177  
178 178  
268 +[[image:data-converters-list.png]]
179 179  
180 -== 3.2 Downlink ==
181 181  
271 += 4. Add Integration =
182 182  
183 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
184 184  
274 +In the left navigation, click **Integrations center**, and then click **Integrations**.
185 185  
186 -[[image:create-new-converter-menu.png||width="500"]]
187 187  
277 +[[image:integrations-list-empty.png]]
188 188  
189 189  
190 -The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
280 +On the **Integrations** page, click on the '**+**' button.
191 191  
192 -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.
193 193  
283 +The **Add integration** window appears.
194 194  
195 -{{code language="JavaScript"}}
196 -// Encode downlink data from incoming Rule Engine message
285 +In the **Add integration** window, configure the following settings:
197 197  
198 -// msg - JSON message payload downlink message json
199 -// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
200 -// metadata - list of key-value pairs with additional data about the message
201 -// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
202 202  
203 -/** Encoder **/
288 +**Basic settings:**
204 204  
205 -var data = {};
290 +* **Integration type**: MQTT
291 +* **Name**: MQTT integration - Device A
292 +* **Enable integration**: YES
293 +* **Allow create devices or assets**: YES
206 206  
207 -// Process data from incoming message and metadata
295 +Click **Next** button.
208 208  
209 -data.tempFreq = msg.temperatureUploadFrequency;
210 -data.humFreq = msg.humidityUploadFrequency;
211 211  
212 -data.devSerialNumber = metadata['ss_serialNumber'];
298 +[[image:add-integration-basic-settings.png||height="504" width="500"]]
213 213  
214 -// Result object with encoded downlink payload
215 -var result = {
216 216  
217 - // downlink data content type: JSON, TEXT or BINARY (base64 format)
218 - contentType: "JSON",
219 219  
220 - // downlink data
221 - data: JSON.stringify(data),
222 222  
223 - // Optional metadata object presented in key/value format
224 - metadata: {
225 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
226 - }
303 +**Uplink data converter:**
227 227  
228 -};
305 +* Click on the **Select existing** button.
306 +* **Uplink data converter**: Select **MQTT Uplink Converter NB/CB **from the dropdown list.
229 229  
230 -return result;
231 -{{/code}}
308 +Click **Next** button.
232 232  
233 233  
311 +[[image:add-integration-ul-data-converter.png||height="505" width="500"]]
312 +
313 +
314 +
315 +**Downlink data converter:**
316 +
317 +Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
318 +
319 +* Click on the **Skip **button in the Downlink data converter section.
320 +
321 +Click **Skip** button.
322 +
323 +
324 +[[image:integration-dl-skip.png||height="511" width="500"]]
325 +
326 +
327 +
328 +**Connection:**
329 +
330 +* **Host**: Host URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
331 +* **Port**: 8883
332 +* **Credentials type**: Basic
333 +* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
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.)
337 +* **QoS:** 0-At most once
338 +
339 +[[image:add-integartion-connection.png||height="505" width="500"]]
340 +
341 +
342 +Click on the **Advanced settings** button.
343 +
344 +* **Clean session:** YES
345 +* **Retained**: YES
346 +
347 +[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
348 +
349 +
350 +Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
351 +
352 +
353 +[[image:check-connection.png||height="83" width="300"]]
354 +
355 +
356 +If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
357 +
358 +
359 +[[image:connection-success.png||height="511" width="500"]]
360 +
361 +
234 234  Click on the **Add** button.
235 235  
364 +You should see that the newly added integration is listed on the **Integrations** page.
236 236  
366 +Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
237 237  
238 -[[image:add-downlink-data-converter.png||height="529" width="500"]]
239 239  
369 +[[image:integration-added.png]]
240 240  
241 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
242 242  
243 243  
244 -[[image:data-converters-list.png]]
373 += 5. Verifying the receipt of data from virtual devices =
245 245  
246 246  
376 +== 5.1 How does it work? ==
247 247  
248 -= 4. Add Integration =
249 249  
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.
250 250  
251 -In the left navigation, click **Integrations center**, and then click **Integrations**.
381 +The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
252 252  
383 +(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
253 253  
254 -[[image:integrations-list-empty.png]]
385 +{{code language="none"}}
386 +{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
387 +{{/code}}
255 255  
389 +Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
256 256  
257 -On the **Integrations** page, click on the '**+**' button.
258 258  
392 +== 5.2 Sending messages ==
259 259  
260 -The **Add integration** window appears.
261 261  
262 -In the **Add integration** window, configure the following settings:
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.
263 263  
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}}
264 264  
265 -**Basic settings:**
401 +If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
266 266  
267 -* **Integration type**: MQTT
268 -* **Name**: MQTT integration NB/CB
269 -* **Enable integration**: YES
270 -* **Allows create devices or assets**: YES
271 271  
272 -Click **Next** button.
404 +[[image:integration-active.png]]
273 273  
274 274  
407 +== 5.3 Viewing messages ==
275 275  
276 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
277 277  
410 +Go back to the **Integrations** page.
278 278  
279 -**Uplink data converter:**
412 +Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
280 280  
281 -* Click on the **Select existing** button.
282 -* **Uplink data converter**: Select **MQTT Uplink Converter NB/CB **from the dropdown list.
414 +Click on the **Edit** button (//**pen icon**//).
283 283  
284 -Click **Next** button.
416 +Click on the **Disabled** button in the upper-right corner.
285 285  
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.
286 286  
420 +Click on the **Apply** button.
287 287  
288 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
422 +Then click on the **Apply changes** (//**tick icon**//) button.
289 289  
290 290  
291 -**Downlink data converter:**
425 +[[image:debug-enabled.png||height="301" width="700"]]
292 292  
293 -* Click on the **Select existing** button.
294 -* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
295 295  
296 -Click **Next** button.
297 297  
298 298  
430 +Now go to the **Events** tab.
299 299  
300 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
432 +Select the **Event type** as **Debug** from the dropdown list.
301 301  
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:
302 302  
303 -**Connection:**
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}'
438 +{{/code}}
304 304  
305 -* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
306 -* **Port**: 8883
307 -* **Credentials**: Basic
308 -* **Enable SSL**: YES
309 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
310 -* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
311 -* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
312 -* **QoS:** 0-At most once
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.
313 313  
314 -[[image:add-integration-connection.png||height="511" width="500"]]
315 315  
443 +[[image:Screenshot 2025-03-26 at 19.49.31.png]]
316 316  
317 -Click on the **Advanced settings** button.
318 318  
319 -* **Clean session:** NO
320 -* **Retained**: NO
321 321  
322 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
447 +Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
323 323  
324 324  
325 -Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
450 +[[image:Screenshot 2025-03-26 at 19.47.52.png]]
326 326  
327 327  
328 -[[image:check-connection.png||height="83" width="300"]]
329 329  
330 330  
331 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
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.
332 332  
333 333  
334 -[[image:connection-success.png||height="511" width="500"]]
458 += 6. Creating a Dashboard =
335 335  
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.
336 336  
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 +
337 337  Click on the **Add** button.
338 338  
339 -You should see that the newly added integration is listed on the **Integrations** page.
340 340  
341 -Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
482 +[[image:dashboard-2.png||height="526" width="500"]]
342 342  
343 343  
485 +Click on the **Add widget / Add new widget** button.
344 344  
345 -[[image:new-integration-pending.png]]
346 346  
488 +[[image:dashboard-3.png]]
347 347  
348 -= 5. Verifying the receipt of data from the device =
349 349  
491 +In the **Select widgets bundle** window, click **Charts**.
350 350  
351 -On the terminal, issue the following MQTT command which simulates the device S31B-NB.
352 352  
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 +
353 353  {{code language="none"}}
354 -mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}"
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}'
355 355  {{/code}}
356 356  
357 -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.
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]]
add-integration-basic-settings.png
Size
... ... @@ -1,1 +1,1 @@
1 -122.5 KB
1 +123.8 KB
Content
add-integration-connection.png
Size
... ... @@ -1,1 +1,1 @@
1 -124.4 KB
1 +158.1 KB
Content
data-converters-list.png
Size
... ... @@ -1,1 +1,1 @@
1 -212.2 KB
1 +19.0 KB
Content
Screenshot 2025-03-16 at 18.38.59.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +221.2 KB
Content
Screenshot 2025-03-16 at 18.39.12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +211.9 KB
Content
Screenshot 2025-03-18 at 09.23.10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +78.7 KB
Content
Screenshot 2025-03-26 at 18.15.08.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +92.2 KB
Content
Screenshot 2025-03-26 at 19.47.52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +168.4 KB
Content
Screenshot 2025-03-26 at 19.49.31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +133.0 KB
Content
Screenshot 2025-03-31 at 06.51.15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +179.5 KB
Content
add-integartion-connection.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +110.3 KB
Content
add-integartion-connetcion.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +146.0 KB
Content
add-integration-part-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +48.6 KB
Content
add-integration-ul-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +121.2 KB
Content
dashboard-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +271.1 KB
Content
dashboard-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +112.2 KB
Content
dashboard-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +141.3 KB
Content
dashboard-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +803.7 KB
Content
dashboard-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +476.1 KB
Content
debug-enabled.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.3 KB
Content
device-provision-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +265.7 KB
Content
device-provision-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +213.9 KB
Content
emqx.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +39.1 KB
Content
image-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +96.0 KB
Content
ins1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +28.8 KB
Content
integration-active.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +64.1 KB
Content
integration-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.2 KB
Content
integration-dl-skip.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +105.5 KB
Content
mqtt-uplink-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +75.3 KB
Content
mqtt-uplink.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +175.1 KB
Content
new-device.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
telemetry-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +191.9 KB
Content
telemetry-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +185.1 KB
Content
thingsboard-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +122.1 KB
Content
thingsboard-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +106.7 KB
Content
thingsboard-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +119.3 KB
Content
timeseries-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +179.1 KB
Content
timeseries-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +174.2 KB
Content
timeseries-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +159.0 KB
Content
ul-data-converter-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +189.4 KB
Content
ul-data-converter-device-a.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +168.3 KB
Content