Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 128.1
edited by Dilisi S
on 2025/03/08 22:01
Change comment: Uploaded new attachment "thingsboard-6.png", version {1}
To version 194.1
edited by Dilisi S
on 2025/03/28 00:23
Change comment: Mar 27 edits - part 3

Summary

Details

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