Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 122.1
edited by Dilisi S
on 2025/03/08 20:41
Change comment: Uploaded new attachment "thingsboard-1.png", version {1}
To version 195.1
edited by Dilisi S
on 2025/03/28 00:38
Change comment: Mar 17 edits - part 3

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,145 +107,160 @@
107 107  You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
108 108  
109 109  
110 -= 3. Data Converters =
149 +=== 2.2.2 emqx ===
111 111  
112 112  
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.
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.
114 114  
115 115  
116 -== 3.1 Uplink ==
155 +[[image:emqx.png||height="420" width="500"]]
117 117  
118 118  
119 -In the left navigation, click **Integrations center**, and then click **Data converters**.
158 +=== 2.2.3 Ins1.thingseye.io ===
120 120  
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.
121 121  
162 +If customers need to use this MQTT connection with ThingsBoard, they need to contact the TE team to obtain three license files.
122 122  
123 -[[image:data-converters-list-empty.png]]
164 +[[image:ins1.png||height="310" width="500"]]
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.
167 += 3. Creating Devices (Optional) =
127 127  
169 +{{info}}
170 +**The following procedure is optional. If you haven't created any device in ThingsBoard first, ThingsBoard will automatically create a device for you based on the integration settings (the device name defined in the uplink decoder) just after it receives the first uplink from your device.Type your information message here.**
171 +{{/info}}
128 128  
173 +First, you need to create devices in ThingsBoard to represent your physical devices. For example, you can name it **Device A**, and the second device could be **Device B** or any name you prefer. The device name should be unique within the **Devices** space.
129 129  
130 -[[image:create-new-converter-menu.png||height="259" width="500"]]
131 131  
176 +In the left navigation, click **Entities -> Devices**.
132 132  
133 -The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
178 +Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
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.
180 +In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
136 136  
137 -{{code language="JavaScript"}}
138 -/** Decoder **/
182 +Click the **Add** button.
139 139  
140 -// decode payload to string
141 -var payloadStr = decodeToString(payload);
142 -var data = JSON.parse(payloadStr);
184 +Skip the **connectivity testing** by clicking the **Close** button.
143 143  
144 -var deviceName = metadata.topic.split("/")[3];
145 -// decode payload to JSON
146 -var deviceType = 'sensor';
186 +The device is created and listed on the **Devices** page. Note that its initial state is **Inactive** because it has not received any data yet.
147 147  
148 -// Result object with device attributes/telemetry data
149 -var result = {
150 - deviceName: deviceName,
151 - deviceType: deviceType,
152 - attributes: {
153 - integrationName: metadata['integrationName'],
154 - },
155 - telemetry: {
156 - temperature: data.temperature,
157 - humidity: data.humidity,
158 - }
159 -};
160 160  
161 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
189 += 4. Data Converters =
162 162  
163 -return result;
164 -{{/code}}
165 165  
192 +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.
166 166  
167 -Click on the **Add** button.
168 168  
195 +== 4.1 Uplink ==
169 169  
170 170  
171 -[[image:add-uplink-data-converter.png||height="529" width="500"]]
198 +In the left navigation, click **Integrations center**, and then click **Data converters**.
172 172  
173 173  
174 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
201 +[[image:data-converters-list-empty.png]]
175 175  
176 -[[image:data-converter-list-showing-uplink-dc.png]]
177 177  
204 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
178 178  
179 179  
180 -== 3.2 Downlink ==
181 181  
208 +[[image:create-new-converter-menu.png||height="259" width="500"]]
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  
211 +The **Add data converter** window will appear.
185 185  
186 -[[image:create-new-converter-menu.png||width="500"]]
213 +Let's create an uplink data converter for the device named '**Device A**'. Name it ‘**MQTT Uplink Converter - Device A**’ and select the Type as **Uplink**.
187 187  
215 +Click on the **TBEL** button if it has not been selected by default.
188 188  
217 +Modify the default TBEL function to match with your device as described below:
189 189  
190 -The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
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.
220 +* Uncomment** line 11**:
193 193  
222 +//var data = decodeToJson(payload)//
194 194  
195 -{{code language="JavaScript"}}
196 -// Encode downlink data from incoming Rule Engine message
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
225 +* **Line 13**: Assign your device name to the **deviceName** field. - We used **Device A** as it is to match with our device, **Device A **in the Devices section.
226 +* From **line 38**: Modify the telemetry section to allow parsed data to be assigned to the fields.
202 202  
203 -/** Encoder **/
228 +//telemetry: {
229 + temperature: data.temperature,
230 + humidity: data.humidity,
231 + rawData: payloadStr
232 + }//
204 204  
205 -var data = {};
206 206  
207 -// Process data from incoming message and metadata
235 +The modified uplink decoder function to match with **Device A** is shown below.
208 208  
209 -data.tempFreq = msg.temperatureUploadFrequency;
210 -data.humFreq = msg.humidityUploadFrequency;
237 +{{code language="JavaScript"}}
238 +// Decode an uplink message from a buffer
239 +// payload - array of bytes
240 +// metadata - key/value object
211 211  
212 -data.devSerialNumber = metadata['ss_serialNumber'];
242 +/** Decoder **/
213 213  
214 -// Result object with encoded downlink payload
215 -var result = {
244 +// decode payload to string
245 +var payloadStr = decodeToString(payload);
216 216  
217 - // downlink data content type: JSON, TEXT or BINARY (base64 format)
218 - contentType: "JSON",
247 +// decode payload to JSON
248 +var data = decodeToJson(payload);
219 219  
220 - // downlink data
221 - data: JSON.stringify(data),
250 +var deviceName = 'Device A';
251 +var deviceType = 'thermostat';
252 +var customerName = 'Customer C';
253 +var groupName = 'thermostat devices';
254 +var manufacturer = 'Example corporation';
255 +// use assetName and assetType instead of deviceName and deviceType
256 +// to automatically create assets instead of devices.
257 +// var assetName = 'Asset A';
258 +// var assetType = 'building';
222 222  
223 - // Optional metadata object presented in key/value format
224 - metadata: {
225 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
226 - }
227 -
260 +// Result object with device/asset attributes/telemetry data
261 +var result = {
262 +// Use deviceName and deviceType or assetName and assetType, but not both.
263 + deviceName: deviceName,
264 + deviceType: deviceType,
265 +// assetName: assetName,
266 +// assetType: assetType,
267 +// customerName: customerName,
268 + groupName: groupName,
269 + attributes: {
270 + model: 'Model A',
271 + serialNumber: 'SN111',
272 + integrationName: metadata['integrationName'],
273 + manufacturer: manufacturer
274 + },
275 + telemetry: {
276 + temperature: data.temperature,
277 + humidity: data.humidity,
278 + rawData: payloadStr
279 + }
228 228  };
229 229  
282 +/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
283 +
230 230  return result;
231 231  {{/code}}
232 232  
233 233  
234 -Click on the **Add** button.
288 +Once you modify the decoder function, click on the **Add** button.
235 235  
236 236  
237 237  
238 -[[image:add-downlink-data-converter.png||height="529" width="500"]]
292 +[[image:ul-data-converter-device-a.png||height="524" width="500"]]
239 239  
240 240  
241 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
295 +You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
242 242  
243 243  
244 -[[image:data-converters-list.png]]
298 +[[image:ul-data-converter-added.png||height="257"]]
245 245  
246 246  
247 247  
248 -= 4. Add Integration =
302 += 5. Add Integration =
249 249  
250 250  
251 251  In the left navigation, click **Integrations center**, and then click **Integrations**.
... ... @@ -265,7 +265,7 @@
265 265  **Basic settings:**
266 266  
267 267  * **Integration type**: MQTT
268 -* **Name**: MQTT integration NB/CB
322 +* **Name**: MQTT integration - Device A
269 269  * **Enable integration**: YES
270 270  * **Allows create devices or assets**: YES
271 271  
... ... @@ -272,10 +272,11 @@
272 272  Click **Next** button.
273 273  
274 274  
329 +[[image:add-integration-basic-settings.png||height="504" width="500"]]
275 275  
276 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
277 277  
278 278  
333 +
279 279  **Uplink data converter:**
280 280  
281 281  * Click on the **Select existing** button.
... ... @@ -284,40 +284,41 @@
284 284  Click **Next** button.
285 285  
286 286  
342 +[[image:add-integration-ul-data-converter.png||height="505" width="500"]]
287 287  
288 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
289 289  
290 290  
291 291  **Downlink data converter:**
292 292  
293 -* Click on the **Select existing** button.
294 -* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
348 +Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
295 295  
296 -Click **Next** button.
350 +* Click on the **Skip **button in the Downlink data converter section.
297 297  
352 +Click **Skip** button.
298 298  
299 299  
300 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
355 +[[image:integration-dl-skip.png||height="511" width="500"]]
301 301  
302 302  
358 +
303 303  **Connection:**
304 304  
305 -* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
361 +* **Host**: Host URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
306 306  * **Port**: 8883
307 -* **Credentials**: Basic
308 -* **Enable SSL**: YES
363 +* **Credentials type**: Basic
309 309  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
310 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)
366 +* **Enable SSL**: YES
367 +* **Topic: device/a** (The topic can be anything; you can even use just the device name.)
312 312  * **QoS:** 0-At most once
313 313  
314 -[[image:add-integration-connection.png||height="511" width="500"]]
370 +[[image:add-integartion-connection.png||height="505" width="500"]]
315 315  
316 316  
317 317  Click on the **Advanced settings** button.
318 318  
319 -* **Clean session:** NO
320 -* **Retained**: NO
375 +* **Clean session:** YES
376 +* **Retained**: YES
321 321  
322 322  [[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
323 323  
... ... @@ -341,17 +341,204 @@
341 341  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
342 342  
343 343  
400 +[[image:integration-added.png]]
344 344  
345 -[[image:new-integration-pending.png]]
346 346  
347 347  
348 -= 5. Verifying the receipt of data from the device =
404 += 6. Verifying the receipt of data from virtual devices =
349 349  
350 350  
351 -On the terminal, issue the following MQTT command which simulates the device S31B-NB.
407 +== 6.1 How does it work? ==
352 352  
409 +
410 +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.
411 +
412 +The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
413 +
414 +(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
415 +
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}"
417 +{"IMEI": "350693903995577", "temperature":25, "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.
420 +Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
421 +
422 +
423 +== 5.2 Sending messages ==
424 +
425 +
426 +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.
427 +
428 +{{code language="none"}}
429 +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}'
430 +{{/code}}
431 +
432 +If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
433 +
434 +
435 +[[image:integration-active.png]]
436 +
437 +
438 +== 6.3 Viewing messages ==
439 +
440 +
441 +Go back to the **Integrations** page.
442 +
443 +Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
444 +
445 +Click on the **Edit** button (//**pen icon**//).
446 +
447 +Click on the **Disabled** button in the upper-right corner.
448 +
449 +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.
450 +
451 +Click on the **Apply** button.
452 +
453 +Then click on the **Apply changes** (//**tick icon**//) button.
454 +
455 +
456 +[[image:debug-enabled.png||height="301" width="700"]]
457 +
458 +
459 +
460 +
461 +Now go to the **Events** tab.
462 +
463 +Select the **Event type** as **Debug** from the dropdown list.
464 +
465 +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:
466 +
467 +{{code language="none"}}
468 +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}'
469 +{{/code}}
470 +
471 +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.
472 +
473 +
474 +[[image:Screenshot 2025-03-26 at 19.49.31.png]]
475 +
476 +
477 +
478 +Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
479 +
480 +
481 +[[image:Screenshot 2025-03-26 at 19.47.52.png]]
482 +
483 +
484 +
485 +
486 +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.
487 +
488 +
489 += 7. Creating a Dashboard =
490 +
491 +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.
492 +
493 +
494 +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.
495 +
496 +
497 +First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
498 +
499 +{{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}}
500 +
501 +
502 +In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
503 +
504 +
505 +[[image:dashboard-1.png]]
506 +
507 +
508 +In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
509 +
510 +Click on the **Add** button.
511 +
512 +
513 +[[image:dashboard-2.png||height="526" width="500"]]
514 +
515 +
516 +Click on the **Add widget / Add new widget** button.
517 +
518 +
519 +[[image:dashboard-3.png]]
520 +
521 +
522 +In the **Select widgets bundle** window, click **Charts**.
523 +
524 +
525 +[[image:dashboard-4.png||height="537" width="700"]]
526 +
527 +
528 +
529 +In the **Charts: select widget** window, click **Time series chart**.
530 +
531 +
532 +[[image:dashboard-5.png||height="525" width="700"]]
533 +
534 +
535 +Configure the **Time series chart** widget as follows:
536 +
537 +* **Datasource** - select S31B-NB device you provisioned.
538 +* **Series**:
539 +** **temperature** - you can see this key by default.
540 +** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
541 +* Click on the **Add** button.
542 +
543 +[[image:timeseries-1.png||height="491" width="700"]]
544 +
545 +
546 +The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
547 +
548 +Click the **Save** button to add the widget to the dashboard.
549 +
550 +
551 +[[image:timeseries-3.png||height="347" width="700"]]
552 +
553 +
554 +Now send the following MQTT messages from the terminal to simulate the data.
555 +
556 +
557 +{{code language="none"}}
558 +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}'
559 +
560 +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}'
561 +
562 +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}'
563 +
564 +{{/code}}
565 +
566 +The chart will update with the values in realtime, as shown in the below image.
567 +
568 +
569 +[[image:timeseries-4.png||height="316" width="700"]]
570 +
571 +
572 += 8. Configure NB-IoT Sensor =
573 +
574 +
575 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
576 +
577 +First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
578 +
579 +
580 +**AT Commands**
581 +
582 +* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
583 +* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
584 +* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
585 +* **AT+CLIENT=null**
586 +* **AT+UNAME=<MQTT Username>**
587 +* **AT+PWD=<MQTT Password>**
588 +* **AT+SERVADDR=<Broker address, Port>**
589 +
590 +Test your uplink by pressing the ACT button for 1 second.
591 +
592 +
593 +
594 +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**.
595 +
596 +{{info}}
597 +The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
598 +{{/info}}
599 +
600 +[[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
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
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-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.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-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +901.1 KB
Content
thingsboard-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +146.3 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