Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 175.1
edited by Dilisi S
on 2025/03/20 16:51
Change comment: Mar 20 edits - part 2
To version 137.1
edited by Dilisi S
on 2025/03/09 03:27
Change comment: Uploaded new attachment "device-provision-2.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,175 +146,126 @@
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  
167 -= 3. Data Converters =
160 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
168 168  
169 169  
170 -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.
171 171  
164 +[[image:create-new-converter-menu.png||height="259" width="500"]]
172 172  
173 -== 3.1 Uplink ==
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 -In the left navigation, click **Integrations center**, and then click **Data converters**.
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 -[[image:data-converters-list-empty.png]]
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 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
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  
197 +return result;
198 +{{/code}}
185 185  
186 -[[image:create-new-converter-menu.png||height="259" width="500"]]
187 187  
201 +Click on the **Add** button.
188 188  
189 -The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
190 190  
191 -Click on the **JavaScript** button.
192 192  
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.
205 +[[image:add-uplink-data-converter.png||height="529" width="500"]]
194 194  
195 -{{info}}
196 -Please note that the value assigned to the IMEI field in the payload will be used by ThingsBoard to create a device on the platform with the same name.
197 -{{/info}}
198 198  
208 +You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
209 +
210 +[[image:data-converter-list-showing-uplink-dc.png]]
211 +
212 +
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 +
199 199  {{code language="JavaScript"}}
200 -//Version: 0.1
201 -// decode payload to string
202 -var payloadStr = decodeToString(payload);
230 +// Encode downlink data from incoming Rule Engine message
203 203  
204 -// decode payload to JSON
205 -var objdata = {};
206 -var obj1 = {};
207 -var data = decodeToJson(payload);
208 -var deviceName = data.IMEI;
209 -delete data.IMEI;
210 -var modelname = "Dragino " + data.Model;
211 -//var mod = data.mod
212 -delete data.Model;
213 -//delete data.mod
214 -var timestamp = new Date().getTime();
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
215 215  
216 -for (var key in data) {
217 -
218 - if (Number(key)) {
219 - obj1[key] = data[key];
220 - obj1[key][obj1[key].length - 1] = Number(new Date(
221 - obj1[key][obj1[key].length - 1]));
237 +/** Encoder **/
222 222  
223 - }
224 -//Alec submitted25/02/25
225 -//turn old key into new
226 - else if (key === "Reading") {
227 - objdata["reading"] = data[key];
228 - } else if (key === "work mode") {
229 - objdata["work_mode"] = data[key];
230 - } else if (key === "hum") {
231 - objdata["humidity"] = data[key];
232 - }else if (key === "hum2") {
233 - objdata["humidity2"] = data[key];
234 - } else if (key === "hum3") {
235 - objdata["humidity3"] = data[key];
236 - } else if (key === "tem") {
237 - objdata["temperature"] = data[key];
238 - } else if (key === "tem2") {
239 - objdata["temperature2"] = data[key];
240 - } else if (key === "tem3") {
241 - objdata["temperature3"] = data[key];
242 - } else if (key === "DS18B20_Temp") {
243 - objdata["temperature_pro"] = data[key];
244 - } else if (key === "ds18b20_temperature") {
245 - objdata["temperature_pro"] = data[key];
246 - } else if (key === "DS18B20_temperature_pro") {
247 - objdata["temperature_pro"] = data[key];
248 - } else if (key === "tdc send flag") {
249 - objdata["tdc_send_flag"] = data[key];
250 - } else if (key === "trigger mode") {
251 - objdata["trigger_mode"] = data[key];
252 - } else if (key === "soil dielectric constant") {
253 - objdata["soil_dielectric_constant"] = data[key];
254 - } else if (key === "door open num") {
255 - objdata["door_open_num"] = data[key];
256 - } else if (key === "door duration") {
257 - objdata["door_duration"] = data[key];
258 - } else if (key === "count time") {
259 - objdata["count_time"] = data[key];
260 - } else if (key === "last open time2") {
261 - objdata["last_open_time2"] = data[key];
262 - } else if (key === "last open time3") {
263 - objdata["last_open_time3"] = data[key];
264 - }
265 -//Alec submitted25/02/25
266 - else {
267 - objdata[key] = data[key]
268 - }
269 -}
270 -var listdata = [{
271 - "ts": timestamp,
272 - "values": objdata
273 -}]
274 -for (var key1 in obj1) {
275 - if (modelname == "Dragino RS485-NB") {
276 - listdata.push({
277 - "ts": obj1[key1][obj1[key1].length - 1],
278 - "values": {
279 - "Payload": obj1[key1][0],
280 - }
281 - })
282 - } else {
283 - listdata.push({
284 - "ts": obj1[key1][obj1[key1].length - 1],
285 - "values": {
286 - "values": obj1[key1]
287 - },
288 - })
289 - }
290 -}
291 -var result = {
239 +var data = {};
292 292  
293 - deviceName: deviceName,
294 - deviceType: modelname,
295 - attributes: {
296 - model: modelname,
297 - //customerName: "NB-CB",
298 - //groupName: "NB-CB",
299 - //integrationName: metadata['integrationName']
241 +// Process data from incoming message and metadata
300 300  
301 - },
302 - telemetry: listdata
303 -}
243 +data.tempFreq = msg.temperatureUploadFrequency;
244 +data.humFreq = msg.humidityUploadFrequency;
304 304  
305 -function decodeToString(payload) {
306 - return String.fromCharCode.apply(String, payload);
307 -}
246 +data.devSerialNumber = metadata['ss_serialNumber'];
308 308  
309 -function decodeToJson(payload) {
310 - // covert payload to string.
311 - var str = decodeToString(payload);
248 +// Result object with encoded downlink payload
249 +var result = {
312 312  
313 - // parse string to JSON
314 - var data = JSON.parse(str);
315 - return data;
316 -}
251 + // downlink data content type: JSON, TEXT or BINARY (base64 format)
252 + contentType: "JSON",
317 317  
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'
260 + }
261 +
262 +};
263 +
318 318  return result;
319 319  {{/code}}
320 320  
... ... @@ -322,16 +322,17 @@
322 322  Click on the **Add** button.
323 323  
324 324  
325 -[[image:mqtt-uplink.png||width="500"]]
326 326  
272 +[[image:add-downlink-data-converter.png||height="529" width="500"]]
327 327  
328 328  
329 -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.
330 330  
331 331  
332 -[[image:data-converter-list-showing-uplink-dc.png]]
278 +[[image:data-converters-list.png]]
333 333  
334 334  
281 +
335 335  = 4. Add Integration =
336 336  
337 337  
... ... @@ -359,6 +359,7 @@
359 359  Click **Next** button.
360 360  
361 361  
309 +
362 362  [[image:add-integration-basic-settings.png||height="511" width="500"]]
363 363  
364 364  
... ... @@ -370,42 +370,40 @@
370 370  Click **Next** button.
371 371  
372 372  
321 +
373 373  [[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
374 374  
375 375  
376 376  **Downlink data converter:**
377 377  
378 -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.
379 379  
380 -* Click on the **Skip **button in the Downlink data converter section.
330 +Click **Next** button.
381 381  
382 -Click **Skip** button.
383 383  
384 384  
385 -[[image:integration-dl-skip.png||height="511" width="500"]]
334 +[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
386 386  
387 387  
388 -
389 389  **Connection:**
390 390  
391 -* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
339 +* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
392 392  * **Port**: 8883
393 393  * **Credentials**: Basic
394 394  * **Enable SSL**: YES
395 395  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
396 396  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
397 -* **Topic: v1/devices/me/telemetry** (The topic can be anything; you can even use just the device name. For example, you can use your device name here, such as S31B-NB.)
345 +* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
398 398  * **QoS:** 0-At most once
399 399  
400 -
401 -
402 402  [[image:add-integration-connection.png||height="511" width="500"]]
403 403  
404 404  
405 405  Click on the **Advanced settings** button.
406 406  
407 -* **Clean session:** YES
408 -* **Retained**: YES
353 +* **Clean session:** NO
354 +* **Retained**: NO
409 409  
410 410  [[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
411 411  
... ... @@ -429,6 +429,7 @@
429 429  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
430 430  
431 431  
378 +
432 432  [[image:new-integration-pending.png]]
433 433  
434 434  
... ... @@ -437,193 +437,38 @@
437 437  
438 438  == 5.1 How does it work? ==
439 439  
440 -
441 441  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.
442 442  
443 -The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. 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.
444 444  
445 -(% 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.
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.
446 446  
447 -{{code language="none"}}
448 -{"IMEI": "S31B-NB", "temperature": 27, ......}
449 -{{/code}}
450 450  
451 -Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
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.**
452 452  
453 453  
454 -== 5.2 Sending messages ==
397 +For example, if you send two MQTT messages with different device names in the topic:
455 455  
399 +1. v1/devices/**S31B-NB**/telemetry
400 +1. v1/devices/**S31B-CB**/telemetry
456 456  
457 -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.
402 +ThingsBoard will create two devices named **S31B-NB** and **S31B-CB** in the **//Devices//** section.
458 458  
404 +
405 +The MQTT payload format is as follows, for example:
406 +
459 459  {{code language="none"}}
460 -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}'
408 +{"temperature":10.4, "humidity":85}
461 461  {{/code}}
462 462  
463 -If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
464 464  
412 +== 5.2 Sending messages ==
465 465  
466 -[[image:integration-active.png]]
467 467  
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.
468 468  
469 -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**.
470 -
471 -
472 -[[image:new-device.png]]
473 -
474 -
475 -== 5.3 Viewing messages ==
476 -
477 -
478 -Go back to the **Integrations** page.
479 -
480 -Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
481 -
482 -Click on the **Edit** button (//**pen icon**//).
483 -
484 -Click on the **Disabled** button in the upper-right corner.
485 -
486 -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.
487 -
488 -Click on the **Apply** button.
489 -
490 -Then click on the **Apply changes** (//**tick icon**//) button.
491 -
492 -
493 -[[image:Screenshot 2025-03-18 at 09.23.10.png]]
494 -
495 -
496 -Now go to the **Events** tab.
497 -
498 -Select the Event type as **Debug** from the dropdown list.
499 -
500 -Now you can see all the Uplink messages you are simulating through the MQTT broker. The status should be OK if there is no errors in your integration.
501 -
502 -
503 -[[image:Screenshot 2025-03-16 at 18.38.59.png]]
504 -
505 -
506 -Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
507 -
508 -
509 -[[image:Screenshot 2025-03-16 at 18.39.12.png]]
510 -
511 -
512 -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.
513 -
514 -
515 -= 6. Creating a Dashboard =
516 -
517 -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.
518 -
519 -
520 -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.
521 -
522 -
523 -First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
524 -
525 -{{code language="none"}}mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 22, "humidity":80}'{{/code}}
526 -
527 -
528 -In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
529 -
530 -
531 -[[image:dashboard-1.png]]
532 -
533 -
534 -In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
535 -
536 -Click on the **Add** button.
537 -
538 -
539 -[[image:dashboard-2.png||height="526" width="500"]]
540 -
541 -
542 -Click on the **Add widget / Add new widget** button.
543 -
544 -
545 -[[image:dashboard-3.png]]
546 -
547 -
548 -In the **Select widgets bundle** window, click **Charts**.
549 -
550 -
551 -[[image:dashboard-4.png||height="537" width="700"]]
552 -
553 -
554 -
555 -In the **Charts: select widget** window, click **Time series chart**.
556 -
557 -
558 -[[image:dashboard-5.png||height="525" width="700"]]
559 -
560 -
561 -Configure the **Time series chart** widget as follows:
562 -
563 -* **Datasource** - select S31B-NB device you provisioned.
564 -* **Series**:
565 -** **temperature** - you can see this key by default.
566 -** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
567 -* Click on the **Add** button.
568 -
569 -[[image:timeseries-1.png||height="491" width="700"]]
570 -
571 -
572 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
573 -
574 -Click the **Save** button to add the widget to the dashboard.
575 -
576 -
577 -[[image:timeseries-3.png||height="347" width="700"]]
578 -
579 -
580 -Now send the following MQTT messages from the terminal to simulate the data.
581 -
582 -
583 583  {{code language="none"}}
584 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 22, "humidity":70}'
585 -
586 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 27, "humidity":72}'
587 -
588 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 19, "humidity":80}'
589 -
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}'
590 590  {{/code}}
591 591  
592 -The chart will update with the values in realtime, as shown in the below image.
593 -
594 -
595 -[[image:timeseries-4.png||height="316" width="700"]]
596 -
597 -
598 -= 7. Configure NB-IoT Sensor =
599 -
600 -
601 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
602 -
603 -First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
604 -
605 -
606 -**AT Commands**
607 -
608 -* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
609 -* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
610 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
611 -* **AT+CLIENT=null**
612 -* **AT+UNAME=<MQTT Username>**
613 -* **AT+PWD=<MQTT Password>**
614 -* **AT+SERVADDR=<Broker address, Port>**
615 -
616 -Test your uplink by pressing the ACT button for 1 second.
617 -
618 -
619 -
620 -The following image shows the uplink payload of a real Dragino device. The publish topic is **TS01-NB**, and the device name is **861275077962896**, which is represented by the **IMEI**.
621 -
622 -{{info}}
623 -The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
624 -{{/info}}
625 -
626 -[[image:image-4.png]]
627 -
628 -
629 -
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
add-integration-connection.png
Size
... ... @@ -1,1 +1,1 @@
1 -158.1 KB
1 +124.4 KB
Content
dashboard-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -271.1 KB
Content
dashboard-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -112.2 KB
Content
dashboard-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -141.3 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
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-dl-skip.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -105.5 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