Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 203.1
edited by Dilisi S
on 2025/04/21 16:48
Change comment: Uploaded new attachment "data-converters-list.png", version {1}
To version 221.1
edited by Dilisi S
on 2025/04/23 01:38
Change comment: April 22 edits

Summary

Details

Page properties
Content
... ... @@ -23,8 +23,9 @@
23 23  
24 24  * ThingsBoard cloud account
25 25  * MQTT Broker (public or private) such as,
26 +** [[ThingsBoard MQTT broker>>https://thingsboard.io/docs/mqtt-broker/]] (TBMQ)
26 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 +** [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] - The public MQTT server is only used for MQTT learning and testing, and should not be used in the production environment.
28 28  ** [[lns1.thingseye.io>>http://lns1.thingseye.io/]] - This is Dragino's MQTT broker, which requires a CA certificate to use.
29 29  
30 30  == 2.1 ThingsBoard Cloud ==
... ... @@ -67,11 +67,19 @@
67 67  [[image:thingsboard-6.png||height="244" width="500"]]
68 68  
69 69  
70 -== 2.2 HiveMQ Cloud ==
71 +== 2.2 MQTT Brokers ==
71 71  
72 -=== 2.2.1 HiveMQ Cloud ===
73 +This section introduces some MQTT brokers that you can use to publish messages from the device side and subscribe from the ThingsBoard side.
73 73  
74 74  
76 +=== 2.2.1 ThingsBoard MQTT broker (TBMQ) ===
77 +
78 +The complete instructions for installing, configuring, and using the TBMQ can be found [[here>>https://thingsboard.io/docs/mqtt-broker/getting-started/]].
79 +
80 +
81 +=== 2.2.2 HiveMQ Cloud ===
82 +
83 +
75 75  Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
76 76  
77 77  Click on the **Start Free** button.
... ... @@ -146,7 +146,7 @@
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 ===
158 +=== 2.2.3 emqx ===
150 150  
151 151  
152 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.
... ... @@ -155,7 +155,7 @@
155 155  [[image:emqx.png||height="420" width="500"]]
156 156  
157 157  
158 -=== 2.2.3 Ins1.thingseye.io ===
167 +=== 2.2.4 Ins1.thingseye.io ===
159 159  
160 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  
... ... @@ -164,37 +164,18 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
167 -= 3. Creating Devices (Optional) =
168 168  
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.**
171 -{{/info}}
177 += 3. Data Converters =
172 172  
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.
174 174  
175 -
176 -In the left navigation, click **Entities -> Devices**.
177 -
178 -Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
179 -
180 -In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
181 -
182 -Click the **Add** button.
183 -
184 -Skip the **connectivity testing** by clicking the **Close** button.
185 -
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.
187 -
188 -
189 -= 4. Data Converters =
190 -
191 -
192 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.
193 193  
182 +**In this section, you will create a universal uplink data converter for all Dragino NB-IoT devices. The uplink decoder converts any MQTT message coming from a device into key-value pairs that can be used to display and visualize data using various widgets on the dashboard**.
194 194  
195 -== 4.1 Uplink ==
196 196  
185 +== 3.1 Uplink ==
197 197  
187 +
198 198  In the left navigation, click **Integrations center**, and then click **Data converters**.
199 199  
200 200  
... ... @@ -201,7 +201,7 @@
201 201  [[image:data-converters-list-empty.png]]
202 202  
203 203  
204 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
194 +On the **Data converters** page, click on the ‘**+**’ button, and then click on **Create new converter** from the dropdown menu.
205 205  
206 206  
207 207  
... ... @@ -208,79 +208,67 @@
208 208  [[image:create-new-converter-menu.png||height="259" width="500"]]
209 209  
210 210  
211 -The **Add data converter** window will appear.
201 +The **Add data converter** window appears.
212 212  
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**.
203 +Name it ‘**MQTT Uplink Converter**’ and select the Type as **Uplink**.
214 214  
215 215  Click on the **TBEL** button if it has not been selected by default.
216 216  
217 -Modify the default TBEL function to match with your device as described below:
207 +Replace the default TBEL decoder function with the following universal TBEL decoder function, which decodes MQTT payload from any Dragino NB-IoT device.
218 218  
219 219  
220 -* Uncomment** line 11**:
221 -
222 -//var data = decodeToJson(payload)//
223 -
224 -
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.
227 -
228 -//telemetry: {
229 - temperature: data.temperature,
230 - humidity: data.humidity,
231 - rawData: payloadStr
232 - }//
233 -
234 -
235 -The modified uplink decoder function to match with **Device A** is shown below.
236 -
237 237  {{code language="JavaScript"}}
238 -// Decode an uplink message from a buffer
239 -// payload - array of bytes
240 -// metadata - key/value object
241 -
242 -/** Decoder **/
243 -
244 -// decode payload to string
245 -var payloadStr = decodeToString(payload);
246 -
247 247  // decode payload to JSON
212 +var pattern = "yyyy/MM/dd HH:mm:ss";
213 +var objdata = {};
214 +var obj1 = {};
248 248  var data = decodeToJson(payload);
249 -
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';
259 -
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 - }
216 +var deviceName = data.IMEI;
217 +data.remove("IMEI");
218 +var modelname = "Dragino "+ data.Model;
219 +//var mod = data.mod
220 +data.remove("Model");
221 +//delete data.mod
222 +var timestamp = new Date().getTime();
223 +foreach (entry: data.entrySet()) {
224 + var key = entry.getKey();
225 + var value = entry.getValue();
226 + //objdata[key] = data[key]
227 + if(key.matches("^-?\\d+$")){ //is number
228 + obj1[key]=data[key];
229 + var index = obj1[key].length-1;
230 + obj1[key][index]=new Date(obj1[key][index],pattern).getTime();
231 + }
232 + else if (key==="bat"||key==="BAT"){
233 + objdata["battery"] = data[key];
234 + }
235 + else{
236 + objdata[key] = data[key];
237 +}}
238 +var listdata = [{"ts":timestamp,"values":objdata}];
239 +foreach ( entry1: obj1.entrySet()){
240 + var key1 = entry1.getKey();
241 + var value1 = entry1.getValue();
242 + var index = obj1[key1].length-1;
243 + var ts = obj1[key1][index];
244 + if (modelname=="Dragino RS485-NB"){
245 + listdata.push({"ts":ts,"values":{"Payload":obj1[key1][0]}});
246 + }
247 + else{
248 + listdata.push({"ts":ts,"values":{"values":obj1[key1]}});
249 + }
250 +}
251 + var result = {
252 + deviceName: deviceName,
253 + deviceType: modelname,
254 + attributes: {
255 + model: modelname
256 + //customerName: "NB-CB",
257 + //groupName: "NB-CB",
258 + //integrationName: metadata['integrationName']
259 + },
260 + telemetry: listdata
280 280  };
281 -
282 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
283 -
284 284  return result;
285 285  {{/code}}
286 286  
... ... @@ -288,18 +288,18 @@
288 288  Once you modify the decoder function, click on the **Add** button.
289 289  
290 290  
269 +[[image:mqtt-uplink-converter.png||height="498" width="500"]]
291 291  
292 -[[image:ul-data-converter-device-a.png||height="524" width="500"]]
293 293  
294 294  
295 295  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
296 296  
297 297  
298 -[[image:ul-data-converter-added.png||height="257"]]
299 299  
277 +[[image:data-converters-list.png]]
300 300  
301 301  
302 -= 5. Add Integration =
280 += 4. Add Integration =
303 303  
304 304  
305 305  In the left navigation, click **Integrations center**, and then click **Integrations**.
... ... @@ -319,7 +319,7 @@
319 319  **Basic settings:**
320 320  
321 321  * **Integration type**: MQTT
322 -* **Name**: MQTT integration - Device A
300 +* **Name**: MQTT integration
323 323  * **Enable integration**: YES
324 324  * **Allow create devices or assets**: YES
325 325  
... ... @@ -326,11 +326,10 @@
326 326  Click **Next** button.
327 327  
328 328  
329 -[[image:add-integration-basic-settings.png||height="504" width="500"]]
330 330  
308 +[[image:add-integration-part-1.png||height="483" width="500"]]
331 331  
332 332  
333 -
334 334  **Uplink data converter:**
335 335  
336 336  * Click on the **Select existing** button.
... ... @@ -339,8 +339,8 @@
339 339  Click **Next** button.
340 340  
341 341  
342 -[[image:add-integration-ul-data-converter.png||height="505" width="500"]]
343 343  
320 +[[image:add-integration-part-2.png||height="484" width="500"]]
344 344  
345 345  
346 346  **Downlink data converter:**
... ... @@ -358,16 +358,16 @@
358 358  
359 359  **Connection:**
360 360  
361 -* **Host**: Host URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
362 -* **Port**: 8883
338 +* **Host**: Host URL (Eg, **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
339 +* **Port**: 8883 (the port number may differ based on your MQTT broker)
363 363  * **Credentials type**: Basic
364 364  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
365 365  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
366 366  * **Enable SSL**: YES
367 -* **Topic: device/a** (The topic can be anything; you can even use just the device name.)
344 +* **Topic**: # (the # symbol indicates that it filters all topics).
368 368  * **QoS:** 0-At most once
369 369  
370 -[[image:add-integartion-connection.png||height="505" width="500"]]
347 +[[image:add-integration-4.png||height="484" width="500"]]
371 371  
372 372  
373 373  Click on the **Advanced settings** button.
... ... @@ -397,50 +397,59 @@
397 397  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
398 398  
399 399  
400 -[[image:integration-added.png]]
401 401  
378 +[[image:integrations-pending.png]]
402 402  
403 403  
404 -= 6. Verifying the receipt of data from virtual devices =
381 += 5. Verifying the receipt of data from virtual devices =
405 405  
406 406  
407 -== 6.1 How does it work? ==
384 +== 5.1 How does it work? ==
408 408  
409 409  
410 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 411  
412 -The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
389 +The Mosquitto client publishes messages (payloads) to a topic - for example, # or device/ts01-nb. You can, of course, use any topic you prefer.
413 413  
414 -(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
415 415  
392 +(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows. The **IMEI **and **Model **are mandatory fields. For other fields, you can use any number of key-value pairs.
393 +
416 416  {{code language="none"}}
417 -{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
395 +{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}
418 418  {{/code}}
419 419  
420 -Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
421 421  
422 -
423 423  == 5.2 Sending messages ==
424 424  
425 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.
402 +On your computer's terminal, issue the following MQTT command, which simulates the device named '**350693903995577'**. The message payload contains the fields IMEI, Model, temperature, humidity, and pressure, which hold the values 350693903995577,  TS01-NB, 30, 80, and 1005 respectively. This payload is also (technically) known as telemetry.
427 427  
428 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}'
405 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/350693903995577" -m '{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}'
430 430  {{/code}}
431 431  
432 -If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
408 +If the integration was performed without errors, a new device named **350693903995577 **is created in the **Devices **section.
433 433  
434 434  
435 -[[image:integration-active.png]]
411 +[[image:new-device-1.png]]
436 436  
437 437  
438 -== 6.3 Viewing messages ==
414 +The status of the integration also changes to '**Active**' after the first telemetry transmission.
439 439  
440 440  
417 +[[image:Screenshot 2025-04-21 122154.png]]
418 +
419 +
420 +
421 +**When ThingsBoard receives this message for the first time, it will automatically create a new device named '350693903995577' in the Devices section. The device name is based on the IMEI number. For subsequent messages with the same IMEI, no duplicate devices will be created. Each new IMEI number will result in a unique entry in the Devices section, representing a physical device.**
422 +
423 +
424 +== 5.3 Viewing messages ==
425 +
426 +
441 441  Go back to the **Integrations** page.
442 442  
443 -Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
429 +Click on the **MQTT integration** in the **Integrations** page to see its details.
444 444  
445 445  Click on the **Edit** button (//**pen icon**//).
446 446  
... ... @@ -453,11 +453,10 @@
453 453  Then click on the **Apply changes** (//**tick icon**//) button.
454 454  
455 455  
456 -[[image:debug-enabled.png||height="301" width="700"]]
457 457  
443 +[[image:Screenshot 2025-04-21 122936.png||height="247" width="500"]]
458 458  
459 459  
460 -
461 461  Now go to the **Events** tab.
462 462  
463 463  Select the **Event type** as **Debug** from the dropdown list.
... ... @@ -465,28 +465,23 @@
465 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 466  
467 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}'
453 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/350693903995577" -m '{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":82, "pressure":1005}'
469 469  {{/code}}
470 470  
471 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 472  
473 473  
474 -[[image:Screenshot 2025-03-26 at 19.49.31.png]]
475 -
476 -
477 -
478 478  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
479 479  
480 480  
481 -[[image:Screenshot 2025-03-26 at 19.47.52.png]]
482 482  
463 +[[image:Screenshot 2025-04-21 122909.png]]
483 483  
484 484  
485 -
486 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 487  
488 488  
489 -= 7. Creating a Dashboard =
469 += 6. Creating a Dashboard =
490 490  
491 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 492  
... ... @@ -494,11 +494,6 @@
494 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 495  
496 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 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":22, "humidity":80, "pressure":1005}'{{/code}}
500 -
501 -
502 502  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
503 503  
504 504  
... ... @@ -534,10 +534,11 @@
534 534  
535 535  Configure the **Time series chart** widget as follows:
536 536  
537 -* **Datasource** - select **Device A** device you provisioned.
512 +* **Datasource** - select **350693903995577 **you provisioned.
538 538  * **Series**:
539 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.
515 +** **humidity** - Click **Add series** button. Then choose **humidity** for the key, and then type **%** as its unit.
516 +** pressure -  Click **Add series** button. Then choose **humidity** for the key, and then type Pa as its unit.
541 541  * Click on the **Add** button.
542 542  
543 543  {{info}}
... ... @@ -544,34 +544,27 @@
544 544  You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
545 545  {{/info}}
546 546  
547 -[[image:Screenshot 2025-03-31 at 06.51.15.png||height="485" width="700"]]
548 548  
549 549  
525 +[[image:Screenshot 2025-04-21 123647.png||height="466" width="700"]]
526 +
527 +
550 550  The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
551 551  
552 552  Click the **Save** button to add the widget to the dashboard.
553 553  
554 554  
555 -[[image:timeseries-3.png||height="347" width="700"]]
533 +[[image:Screenshot 2025-04-21 124145.png||height="443" width="700"]]
556 556  
557 557  
558 -Now send the following MQTT messages from the terminal to simulate the data.
536 +**Now send a few MQTT messages from the terminal to simulate the data. Use different values for temperature, humidity, and pressure in each message.**
559 559  
538 +**The chart will update with the values in real time, and you will see a live chart similar to this:**
560 560  
561 -{{code language="none"}}
562 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":22, "humidity":70, "pressure":1005}'
563 563  
564 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":27, "humidity":72, "pressure":1005}'
541 +[[image:Screenshot 2025-04-21 124054.png||height="441" width="700"]]
565 565  
566 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":19, "humidity":80, "pressure":1005}'
567 -{{/code}}
568 568  
569 -The chart will update with the values in realtime, as shown in the below image.
570 -
571 -
572 -[[image:timeseries-4.png||height="316" width="700"]]
573 -
574 -
575 575  = 8. Configure Physical NB-IoT Sensor =
576 576  
577 577  
... ... @@ -583,8 +583,8 @@
583 583  **AT Commands**
584 584  
585 585  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
586 -* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
587 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
555 +* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: # -  **You can leave the SUBTOPIC configuration as it is, since we are not sending downlink messages to the device at the moment.
556 +* **AT+PUBTOPIC=<MQTT publish topic> Eg: #**
588 588  * **AT+CLIENT=null**
589 589  * **AT+UNAME=<MQTT Username>**
590 590  * **AT+PWD=<MQTT Password>**
... ... @@ -593,7 +593,6 @@
593 593  Test your uplink by pressing the ACT button for 1 second.
594 594  
595 595  
596 -
597 597  The following image shows the uplink payload of a real Dragino device. The publish topic is '**TS01-NB' that contains fields in the payload, IMEI, IMSI, Model, temperature, etc**. Note that we have created a device named **TS01-NB** in the **Devices** section in advance.
598 598  
599 599  
Screenshot 2025-04-21 122154.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +21.2 KB
Content
Screenshot 2025-04-21 122909.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +59.9 KB
Content
Screenshot 2025-04-21 122936.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +72.0 KB
Content
Screenshot 2025-04-21 123647.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +77.9 KB
Content
Screenshot 2025-04-21 124054.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +60.4 KB
Content
Screenshot 2025-04-21 124145.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +50.9 KB
Content
add-integration-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +63.1 KB
Content
add-integration-part-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +48.6 KB
Content
add-integration-part-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +47.7 KB
Content
device-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +34.5 KB
Content
integrations-pending.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +19.8 KB
Content
new-device-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +34.7 KB
Content