Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 153.1
edited by Dilisi S
on 2025/03/17 00:09
Change comment: Uploaded new attachment "emqx.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,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  
... ... @@ -66,7 +66,9 @@
66 66  
67 67  == 2.2 HiveMQ Cloud ==
68 68  
72 +=== 2.2.1 HiveMQ Cloud ===
69 69  
74 +
70 70  Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
71 71  
72 72  Click on the **Start Free** button.
... ... @@ -141,145 +141,160 @@
141 141  You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
142 142  
143 143  
144 -= 3. Data Converters =
149 +=== 2.2.2 emqx ===
145 145  
146 146  
147 -In **ThingsBoard**, **Data Converters** are components used to transform incoming or outgoing data between different formats, typically to convert raw telemetry data from devices into a structured format that ThingsBoard can understand, or vice versa.
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.
148 148  
149 149  
150 -== 3.1 Uplink ==
155 +[[image:emqx.png||height="420" width="500"]]
151 151  
152 152  
153 -In the left navigation, click **Integrations center**, and then click **Data converters**.
158 +=== 2.2.3 Ins1.thingseye.io ===
154 154  
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.
155 155  
162 +If customers need to use this MQTT connection with ThingsBoard, they need to contact the TE team to obtain three license files.
156 156  
157 -[[image:data-converters-list-empty.png]]
164 +[[image:ins1.png||height="310" width="500"]]
158 158  
159 159  
160 -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) =
161 161  
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}}
162 162  
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.
163 163  
164 -[[image:create-new-converter-menu.png||height="259" width="500"]]
165 165  
176 +In the left navigation, click **Entities -> Devices**.
166 166  
167 -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**.
168 168  
169 -Click on the **TBEL** button if not selected it by default. Delete the existing decoder function in the code editor. Now copy and paste the following decoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
180 +In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
170 170  
171 -{{code language="JavaScript"}}
172 -/** Decoder **/
182 +Click the **Add** button.
173 173  
174 -// decode payload to string
175 -var payloadStr = decodeToString(payload);
176 -var data = JSON.parse(payloadStr);
184 +Skip the **connectivity testing** by clicking the **Close** button.
177 177  
178 -var deviceName = metadata.topic.split("/")[3];
179 -// decode payload to JSON
180 -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.
181 181  
182 -// Result object with device attributes/telemetry data
183 -var result = {
184 - deviceName: deviceName,
185 - deviceType: deviceType,
186 - attributes: {
187 - integrationName: metadata['integrationName'],
188 - },
189 - telemetry: {
190 - temperature: data.temperature,
191 - humidity: data.humidity,
192 - }
193 -};
194 194  
195 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
189 += 4. Data Converters =
196 196  
197 -return result;
198 -{{/code}}
199 199  
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.
200 200  
201 -Click on the **Add** button.
202 202  
195 +== 4.1 Uplink ==
203 203  
204 204  
205 -[[image:add-uplink-data-converter.png||height="529" width="500"]]
198 +In the left navigation, click **Integrations center**, and then click **Data converters**.
206 206  
207 207  
208 -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]]
209 209  
210 -[[image:data-converter-list-showing-uplink-dc.png]]
211 211  
204 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
212 212  
213 213  
214 -== 3.2 Downlink ==
215 215  
208 +[[image:create-new-converter-menu.png||height="259" width="500"]]
216 216  
217 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
218 218  
211 +The **Add data converter** window will appear.
219 219  
220 -[[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**.
221 221  
215 +Click on the **TBEL** button if it has not been selected by default.
222 222  
217 +Modify the default TBEL function to match with your device as described below:
223 223  
224 -The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
225 225  
226 -Click on the **TBEL** button if not selected it by default. Now copy and paste the following encoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This encoder function is compatible for both NB and CB series devices.
220 +* Uncomment** line 11**:
227 227  
222 +//var data = decodeToJson(payload)//
228 228  
229 -{{code language="JavaScript"}}
230 -// Encode downlink data from incoming Rule Engine message
231 231  
232 -// msg - JSON message payload downlink message json
233 -// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
234 -// metadata - list of key-value pairs with additional data about the message
235 -// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
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.
236 236  
237 -/** Encoder **/
228 +//telemetry: {
229 + temperature: data.temperature,
230 + humidity: data.humidity,
231 + rawData: payloadStr
232 + }//
238 238  
239 -var data = {};
240 240  
241 -// Process data from incoming message and metadata
235 +The modified uplink decoder function to match with **Device A** is shown below.
242 242  
243 -data.tempFreq = msg.temperatureUploadFrequency;
244 -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
245 245  
246 -data.devSerialNumber = metadata['ss_serialNumber'];
242 +/** Decoder **/
247 247  
248 -// Result object with encoded downlink payload
249 -var result = {
244 +// decode payload to string
245 +var payloadStr = decodeToString(payload);
250 250  
251 - // downlink data content type: JSON, TEXT or BINARY (base64 format)
252 - contentType: "JSON",
247 +// decode payload to JSON
248 +var data = decodeToJson(payload);
253 253  
254 - // downlink data
255 - 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';
256 256  
257 - // Optional metadata object presented in key/value format
258 - metadata: {
259 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
260 - }
261 -
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 + }
262 262  };
263 263  
282 +/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
283 +
264 264  return result;
265 265  {{/code}}
266 266  
267 267  
268 -Click on the **Add** button.
288 +Once you modify the decoder function, click on the **Add** button.
269 269  
270 270  
271 271  
272 -[[image:add-downlink-data-converter.png||height="529" width="500"]]
292 +[[image:ul-data-converter-device-a.png||height="524" width="500"]]
273 273  
274 274  
275 -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.
276 276  
277 277  
278 -[[image:data-converters-list.png]]
298 +[[image:ul-data-converter-added.png||height="257"]]
279 279  
280 280  
281 281  
282 -= 4. Add Integration =
302 += 5. Add Integration =
283 283  
284 284  
285 285  In the left navigation, click **Integrations center**, and then click **Integrations**.
... ... @@ -299,7 +299,7 @@
299 299  **Basic settings:**
300 300  
301 301  * **Integration type**: MQTT
302 -* **Name**: MQTT integration NB/CB
322 +* **Name**: MQTT integration - Device A
303 303  * **Enable integration**: YES
304 304  * **Allows create devices or assets**: YES
305 305  
... ... @@ -306,10 +306,11 @@
306 306  Click **Next** button.
307 307  
308 308  
329 +[[image:add-integration-basic-settings.png||height="504" width="500"]]
309 309  
310 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
311 311  
312 312  
333 +
313 313  **Uplink data converter:**
314 314  
315 315  * Click on the **Select existing** button.
... ... @@ -318,34 +318,35 @@
318 318  Click **Next** button.
319 319  
320 320  
342 +[[image:add-integration-ul-data-converter.png||height="505" width="500"]]
321 321  
322 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
323 323  
324 324  
325 325  **Downlink data converter:**
326 326  
327 -* Click on the **Select existing** button.
328 -* **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.
329 329  
330 -Click **Next** button.
350 +* Click on the **Skip **button in the Downlink data converter section.
331 331  
352 +Click **Skip** button.
332 332  
333 333  
334 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
355 +[[image:integration-dl-skip.png||height="511" width="500"]]
335 335  
336 336  
358 +
337 337  **Connection:**
338 338  
339 -* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
361 +* **Host**: Host URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
340 340  * **Port**: 8883
341 -* **Credentials**: Basic
342 -* **Enable SSL**: YES
363 +* **Credentials type**: Basic
343 343  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
344 344  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
345 -* **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.)
346 346  * **QoS:** 0-At most once
347 347  
348 -[[image:add-integration-connection.png||height="511" width="500"]]
370 +[[image:add-integartion-connection.png||height="505" width="500"]]
349 349  
350 350  
351 351  Click on the **Advanced settings** button.
... ... @@ -375,48 +375,36 @@
375 375  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
376 376  
377 377  
400 +[[image:integration-added.png]]
378 378  
379 -[[image:new-integration-pending.png]]
380 380  
381 381  
382 -= 5. Verifying the receipt of data from virtual devices =
404 += 6. Verifying the receipt of data from virtual devices =
383 383  
384 384  
385 -== 5.1 How does it work? ==
407 +== 6.1 How does it work? ==
386 386  
387 387  
388 388  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.
389 389  
390 -The Mosquitto client publishes messages on the topic v1/devices/[device_name]/telemetry. The [device_name]placeholder can be replaced with any device name, for example, 'S31B-NB'. Then, the MQTT topic would be v1/devices/S31B-NB/telemetry.
412 +The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
391 391  
392 -On the ThingsBoard side, we configure the MQTT topic subscription as v1/devices/+/telemetry. The + wildcard represents any device name and allows ThingsBoard to automatically create (provision) a device with that name, such as S31B-NB, for example.
414 +(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
393 393  
394 -
395 -**The new device is created the first time the MQTT topic is received. For subsequent MQTT topics with the same device name, no duplicate devices will be created.**
396 -
397 -
398 -For example, if you send two MQTT messages with different device names in the topic:
399 -
400 -1. v1/devices/**S31B-NB**/telemetry
401 -1. v1/devices/**LDS25-NB**/telemetry
402 -
403 -ThingsBoard will create two devices named **S31B-NB** and **LDS25-NB** in the **//Devices//** section.
404 -
405 -
406 -The MQTT payload format is as follows, which is common for all ~-~-NB and ~-~-CB series devices:
407 -
408 408  {{code language="none"}}
409 -{"temperature":10.4, "humidity":85}
417 +{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
410 410  {{/code}}
411 411  
420 +Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
412 412  
422 +
413 413  == 5.2 Sending messages ==
414 414  
415 415  
416 -On the terminal, issue the following MQTT command which simulates the device S31B-NB. The message payload contains the fields temperature and humidity, which hold the values 10.4 and 85, respectively. This payload is also (technically) known as telemetry.
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.
417 417  
418 418  {{code language="none"}}
419 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":10.4, "humidity":85}'
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}'
420 420  {{/code}}
421 421  
422 422  If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
... ... @@ -425,43 +425,59 @@
425 425  [[image:integration-active.png]]
426 426  
427 427  
428 -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**.
438 +== 6.3 Viewing messages ==
429 429  
430 430  
431 -[[image:device-provision-1.png]]
441 +Go back to the **Integrations** page.
432 432  
443 +Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
433 433  
434 -Click on the device S31B-NB on the devices list to see its details.
445 +Click on the **Edit** button (//**pen icon**//).
435 435  
436 -Then go to the **Latest telemetry** tab.
447 +Click on the **Disabled** button in the upper-right corner.
437 437  
438 -You can see the fields temperature and humidity with the values you previously sent using the MQTT message.
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.
439 439  
451 +Click on the **Apply** button.
440 440  
441 -[[image:telemetry-1.png]]
453 +Then click on the **Apply changes** (//**tick icon**//) button.
442 442  
443 443  
444 -Now, change the values of the fields and send the MQTT message again. For example, set temperature to 20 and humidity to 70. Observe how the values update in //Latest Telemetry//.
456 +[[image:debug-enabled.png||height="301" width="700"]]
445 445  
446 446  
447 -[[image:telemetry-2.png]]
448 448  
449 449  
450 -Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
461 +Now go to the **Events** tab.
451 451  
463 +Select the **Event type** as **Debug** from the dropdown list.
452 452  
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 +
453 453  {{code language="none"}}
454 -mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/LDS25-NB/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":11, "humidity":87}'
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}'
455 455  {{/code}}
456 456  
457 -Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
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.
458 458  
459 459  
460 -[[image:device-provision-2.png]]
474 +[[image:Screenshot 2025-03-26 at 19.49.31.png]]
461 461  
462 462  
463 -= 6. Creating a Dashboard =
464 464  
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 +
465 465  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.
466 466  
467 467  
... ... @@ -468,6 +468,11 @@
468 468  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.
469 469  
470 470  
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 +
471 471  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
472 472  
473 473  
... ... @@ -524,11 +524,11 @@
524 524  
525 525  
526 526  {{code language="none"}}
527 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":20, "humidity":70}'
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}'
528 528  
529 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":22, "humidity":71}'
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}'
530 530  
531 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":18, "humidity":79}'
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}'
532 532  
533 533  {{/code}}
534 534  
... ... @@ -538,10 +538,10 @@
538 538  [[image:timeseries-4.png||height="316" width="700"]]
539 539  
540 540  
541 -= 7. Configure NB-IoT Sensor =
572 += 8. Configure NB-IoT Sensor =
542 542  
543 543  
544 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
575 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
545 545  
546 546  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
547 547  
... ... @@ -549,8 +549,8 @@
549 549  **AT Commands**
550 550  
551 551  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
552 -* **AT+SUBTOPIC=<MQTT topic>**
553 -* **AT+PUBTOPIC=<MQTT topic>**
583 +* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
584 +* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
554 554  * **AT+CLIENT=null**
555 555  * **AT+UNAME=<MQTT Username>**
556 556  * **AT+PWD=<MQTT Password>**
... ... @@ -557,3 +557,13 @@
557 557  * **AT+SERVADDR=<Broker address, Port>**
558 558  
559 559  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
integration-active.png
Size
... ... @@ -1,1 +1,1 @@
1 -64.2 KB
1 +64.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
debug-enabled.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.3 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-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
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