Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 120.1
edited by Dilisi S
on 2025/03/08 20:25
Change comment: Uploaded new attachment "hivemq-10.png", version {1}
To version 178.1
edited by Dilisi S
on 2025/03/27 01:16
Change comment: Uploaded new attachment "Screenshot 2025-03-26 at 18.15.08.png", version {1}

Summary

Details

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