Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 194.1
edited by Dilisi S
on 2025/03/28 00:23
Change comment: Mar 27 edits - part 3
To version 162.1
edited by Dilisi S
on 2025/03/18 04:56
Change comment: Uploaded new attachment "Screenshot 2025-03-16 at 18.38.59.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -164,141 +164,240 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
167 -= 3. Creating Devices =
167 += 3. Data Converters =
168 168  
169 169  
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.
170 +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.
171 171  
172 172  
173 -In the left navigation, click **Entities -> Devices**.
173 +== 3.1 Uplink ==
174 174  
175 -Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
176 176  
177 -In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
176 +In the left navigation, click **Integrations center**, and then click **Data converters**.
178 178  
179 -Click the **Add** button.
180 180  
181 -Skip the **connectivity testing** by clicking the **Close** button.
179 +[[image:data-converters-list-empty.png]]
182 182  
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.
184 184  
182 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
185 185  
186 -= 4. Data Converters =
187 187  
188 188  
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.
186 +[[image:create-new-converter-menu.png||height="259" width="500"]]
190 190  
191 191  
192 -== 4.1 Uplink ==
189 +The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
193 193  
191 +Click on the **JavaScript** button.
194 194  
195 -In the left navigation, click **Integrations center**, and then click **Data converters**.
193 +Delete the default decoder function in the code editor. Now copy and paste the following decoder function written in **JavaScript** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
196 196  
197 197  
198 -[[image:data-converters-list-empty.png]]
196 +{{code language="JavaScript"}}
197 +//Version: 0.1
198 +// decode payload to string
199 +var payloadStr = decodeToString(payload);
199 199  
201 +// decode payload to JSON
202 +var objdata = {};
203 +var obj1 = {};
204 +var data = decodeToJson(payload);
205 +var deviceName = data.IMEI;
206 +delete data.IMEI;
207 +var modelname = "Dragino " + data.Model;
208 +//var mod = data.mod
209 +delete data.Model;
210 +//delete data.mod
211 +var timestamp = new Date().getTime();
200 200  
201 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
213 +for (var key in data) {
214 +
215 + if (Number(key)) {
216 + obj1[key] = data[key];
217 + obj1[key][obj1[key].length - 1] = Number(new Date(
218 + obj1[key][obj1[key].length - 1]));
202 202  
220 + }
221 +//Alec submitted25/02/25
222 +//turn old key into new
223 + else if (key === "Reading") {
224 + objdata["reading"] = data[key];
225 + } else if (key === "work mode") {
226 + objdata["work_mode"] = data[key];
227 + } else if (key === "hum") {
228 + objdata["humidity"] = data[key];
229 + }else if (key === "hum2") {
230 + objdata["humidity2"] = data[key];
231 + } else if (key === "hum3") {
232 + objdata["humidity3"] = data[key];
233 + } else if (key === "tem") {
234 + objdata["temperature"] = data[key];
235 + } else if (key === "tem2") {
236 + objdata["temperature2"] = data[key];
237 + } else if (key === "tem3") {
238 + objdata["temperature3"] = data[key];
239 + } else if (key === "DS18B20_Temp") {
240 + objdata["temperature_pro"] = data[key];
241 + } else if (key === "ds18b20_temperature") {
242 + objdata["temperature_pro"] = data[key];
243 + } else if (key === "DS18B20_temperature_pro") {
244 + objdata["temperature_pro"] = data[key];
245 + } else if (key === "tdc send flag") {
246 + objdata["tdc_send_flag"] = data[key];
247 + } else if (key === "trigger mode") {
248 + objdata["trigger_mode"] = data[key];
249 + } else if (key === "soil dielectric constant") {
250 + objdata["soil_dielectric_constant"] = data[key];
251 + } else if (key === "door open num") {
252 + objdata["door_open_num"] = data[key];
253 + } else if (key === "door duration") {
254 + objdata["door_duration"] = data[key];
255 + } else if (key === "count time") {
256 + objdata["count_time"] = data[key];
257 + } else if (key === "last open time2") {
258 + objdata["last_open_time2"] = data[key];
259 + } else if (key === "last open time3") {
260 + objdata["last_open_time3"] = data[key];
261 + }
262 +//Alec submitted25/02/25
263 + else {
264 + objdata[key] = data[key]
265 + }
266 +}
267 +var listdata = [{
268 + "ts": timestamp,
269 + "values": objdata
270 +}]
271 +for (var key1 in obj1) {
272 + if (modelname == "Dragino RS485-NB") {
273 + listdata.push({
274 + "ts": obj1[key1][obj1[key1].length - 1],
275 + "values": {
276 + "Payload": obj1[key1][0],
277 + }
278 + })
279 + } else {
280 + listdata.push({
281 + "ts": obj1[key1][obj1[key1].length - 1],
282 + "values": {
283 + "values": obj1[key1]
284 + },
285 + })
286 + }
287 +}
288 +var result = {
203 203  
290 + deviceName: deviceName,
291 + deviceType: modelname,
292 + attributes: {
293 + model: modelname,
294 + //customerName: "NB-CB",
295 + //groupName: "NB-CB",
296 + //integrationName: metadata['integrationName']
204 204  
205 -[[image:create-new-converter-menu.png||height="259" width="500"]]
298 + },
299 + telemetry: listdata
300 +}
206 206  
302 +function decodeToString(payload) {
303 + return String.fromCharCode.apply(String, payload);
304 +}
207 207  
208 -The **Add data converter** window will appear.
306 +function decodeToJson(payload) {
307 + // covert payload to string.
308 + var str = decodeToString(payload);
209 209  
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**.
310 + // parse string to JSON
311 + var data = JSON.parse(str);
312 + return data;
313 +}
211 211  
212 -Click on the **TBEL** button if it has not been selected by default.
315 +return result;
316 +{{/code}}
213 213  
214 -Modify the default TBEL function to match with your device as described below:
215 215  
319 +Click on the **Add** button.
216 216  
217 -* Uncomment** line 11**:
218 218  
219 -//var data = decodeToJson(payload)//
322 +[[image:mqtt-uplink.png||width="500"]]
220 220  
221 221  
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.
224 224  
225 -//telemetry: {
226 - temperature: data.temperature,
227 - humidity: data.humidity,
228 - rawData: payloadStr
229 - }//
326 +You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
230 230  
231 231  
232 -The modified uplink decoder function to match with **Device A** is shown below.
329 +[[image:data-converter-list-showing-uplink-dc.png]]
233 233  
331 +
332 +== 3.2 Downlink ==
333 +
334 +
335 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
336 +
337 +
338 +[[image:create-new-converter-menu.png||width="500"]]
339 +
340 +
341 +
342 +The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
343 +
344 +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.
345 +
346 +
234 234  {{code language="JavaScript"}}
235 -// Decode an uplink message from a buffer
236 -// payload - array of bytes
237 -// metadata - key/value object
348 +// Encode downlink data from incoming Rule Engine message
238 238  
239 -/** Decoder **/
350 +// msg - JSON message payload downlink message json
351 +// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
352 +// metadata - list of key-value pairs with additional data about the message
353 +// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
240 240  
241 -// decode payload to string
242 -var payloadStr = decodeToString(payload);
355 +/** Encoder **/
243 243  
244 -// decode payload to JSON
245 -var data = decodeToJson(payload);
357 +var data = {};
246 246  
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';
359 +// Process data from incoming message and metadata
256 256  
257 -// Result object with device/asset attributes/telemetry data
361 +data.tempFreq = msg.temperatureUploadFrequency;
362 +data.humFreq = msg.humidityUploadFrequency;
363 +
364 +data.devSerialNumber = metadata['ss_serialNumber'];
365 +
366 +// Result object with encoded downlink payload
258 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 - }
277 -};
278 278  
279 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
369 + // downlink data content type: JSON, TEXT or BINARY (base64 format)
370 + contentType: "JSON",
280 280  
281 -return result;
282 -{{/code}}
372 + // downlink data
373 + data: JSON.stringify(data),
283 283  
375 + // Optional metadata object presented in key/value format
376 + metadata: {
377 + topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
378 + }
284 284  
285 -Once you modify the decoder function, click on the **Add** button.
380 +};
286 286  
382 +return result;
383 +{{/code}}
287 287  
288 288  
289 -[[image:ul-data-converter-device-a.png||height="524" width="500"]]
386 +Click on the **Add** button.
290 290  
291 291  
292 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
389 +[[image:add-downlink-data-converter.png||height="529" width="500"]]
293 293  
294 294  
295 -[[image:ul-data-converter-added.png||height="257"]]
392 +You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
296 296  
297 297  
395 +[[image:data-converters-list.png]]
298 298  
299 -= 5. Add Integration =
300 300  
398 += 4. Add Integration =
301 301  
400 +
302 302  In the left navigation, click **Integrations center**, and then click **Integrations**.
303 303  
304 304  
... ... @@ -316,7 +316,7 @@
316 316  **Basic settings:**
317 317  
318 318  * **Integration type**: MQTT
319 -* **Name**: MQTT integration - Device A
418 +* **Name**: MQTT integration NB/CB
320 320  * **Enable integration**: YES
321 321  * **Allows create devices or assets**: YES
322 322  
... ... @@ -323,11 +323,9 @@
323 323  Click **Next** button.
324 324  
325 325  
326 -[[image:add-integration-basic-settings.png||height="504" width="500"]]
425 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
327 327  
328 328  
329 -
330 -
331 331  **Uplink data converter:**
332 332  
333 333  * Click on the **Select existing** button.
... ... @@ -336,37 +336,35 @@
336 336  Click **Next** button.
337 337  
338 338  
339 -[[image:add-integration-ul-data-converter.png||height="505" width="500"]]
436 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
340 340  
341 341  
342 -
343 343  **Downlink data converter:**
344 344  
345 -Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
441 +* Click on the **Select existing** button.
442 +* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
346 346  
347 -* Click on the **Skip **button in the Downlink data converter section.
444 +Click **Next** button.
348 348  
349 -Click **Skip** button.
350 350  
447 +[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
351 351  
352 -[[image:integration-dl-skip.png||height="511" width="500"]]
353 353  
354 -
355 -
356 356  **Connection:**
357 357  
358 -* **Host**: Host URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
452 +* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
359 359  * **Port**: 8883
360 -* **Credentials type**: Basic
454 +* **Credentials**: Basic
455 +* **Enable SSL**: YES
361 361  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
362 362  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
363 -* **Enable SSL**: YES
364 -* **Topic: device/a** (The topic can be anything; you can even use just the device name.)
458 +* **Topic: v1/devices/+/telemetry** (the + replaces any 'device name' will create a device in the Entities -> Devices)
365 365  * **QoS:** 0-At most once
366 366  
367 -[[image:add-integartion-connection.png||height="505" width="500"]]
368 368  
462 +[[image:add-integration-connection.png||height="511" width="500"]]
369 369  
464 +
370 370  Click on the **Advanced settings** button.
371 371  
372 372  * **Clean session:** YES
... ... @@ -394,36 +394,36 @@
394 394  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
395 395  
396 396  
397 -[[image:integration-added.png]]
398 398  
493 +[[image:new-integration-pending.png]]
399 399  
400 400  
401 -= 6. Verifying the receipt of data from virtual devices =
496 += 5. Verifying the receipt of data from virtual devices =
402 402  
403 403  
404 -== 6.1 How does it work? ==
499 +== 5.1 How does it work? ==
405 405  
406 406  
407 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 408  
409 -The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
504 +The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
410 410  
411 -(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
506 +(% 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.
412 412  
413 413  {{code language="none"}}
414 -{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
509 +{"IMEI": "S31B-NB", "temperature": 27, ......}
415 415  {{/code}}
416 416  
417 -Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
512 +Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
418 418  
419 419  
420 420  == 5.2 Sending messages ==
421 421  
422 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.
518 +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.
424 424  
425 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}'
521 +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}'
427 427  {{/code}}
428 428  
429 429  If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
... ... @@ -432,59 +432,44 @@
432 432  [[image:integration-active.png]]
433 433  
434 434  
435 -== 6.3 Viewing messages ==
530 +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**.
436 436  
437 437  
438 -Go back to the **Integrations** page.
439 439  
440 -Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
534 +[[image:new-device.png]]
441 441  
442 -Click on the **Edit** button (//**pen icon**//).
443 443  
444 -Click on the **Disabled** button in the upper-right corner.
537 +Click on the device S31B-NB on the devices list to see its details.
445 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.
539 +Then go to the **Latest telemetry** tab.
447 447  
448 -Click on the **Apply** button.
541 +You can see the fields temperature and humidity with the values you previously sent using the MQTT message.
449 449  
450 -Then click on the **Apply changes** (//**tick icon**//) button.
451 451  
544 +[[image:telemetry-1.png]]
452 452  
453 -[[image:debug-enabled.png||height="301" width="700"]]
454 454  
547 +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//.
455 455  
456 456  
550 +[[image:telemetry-2.png]]
457 457  
458 -Now go to the **Events** tab.
459 459  
460 -Select the **Event type** as **Debug** from the dropdown list.
553 +Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
461 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 463  
464 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}'
557 +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}'
466 466  {{/code}}
467 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.
560 +Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
469 469  
470 470  
471 -[[image:Screenshot 2025-03-26 at 19.49.31.png]]
563 +[[image:device-provision-2.png]]
472 472  
473 473  
566 += 6. Creating a Dashboard =
474 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 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 489  
490 490  
... ... @@ -491,11 +491,6 @@
491 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 492  
493 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 499  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
500 500  
501 501  
... ... @@ -552,11 +552,11 @@
552 552  
553 553  
554 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}'
630 +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}'
556 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}'
632 +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}'
558 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}'
634 +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}'
560 560  
561 561  {{/code}}
562 562  
... ... @@ -566,10 +566,10 @@
566 566  [[image:timeseries-4.png||height="316" width="700"]]
567 567  
568 568  
569 -= 8. Configure NB-IoT Sensor =
644 += 7. Configure NB-IoT Sensor =
570 570  
571 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**.
647 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
573 573  
574 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 575  
... ... @@ -577,8 +577,8 @@
577 577  **AT Commands**
578 578  
579 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**
655 +* **AT+SUBTOPIC=<MQTT topic>**
656 +* **AT+PUBTOPIC=<MQTT topic>**
582 582  * **AT+CLIENT=null**
583 583  * **AT+UNAME=<MQTT Username>**
584 584  * **AT+PWD=<MQTT Password>**
... ... @@ -585,13 +585,3 @@
585 585  * **AT+SERVADDR=<Broker address, Port>**
586 586  
587 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]]
Screenshot 2025-03-16 at 18.39.12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -211.9 KB
Content
Screenshot 2025-03-18 at 09.23.10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -78.7 KB
Content
Screenshot 2025-03-26 at 18.15.08.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -92.2 KB
Content
Screenshot 2025-03-26 at 19.47.52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -168.4 KB
Content
Screenshot 2025-03-26 at 19.49.31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -133.0 KB
Content
add-integartion-connection.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -110.3 KB
Content
add-integartion-connetcion.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -146.0 KB
Content
add-integration-basic-settings.png
Size
... ... @@ -1,1 +1,1 @@
1 -123.8 KB
1 +122.5 KB
Content
add-integration-connection.png
Size
... ... @@ -1,1 +1,1 @@
1 -158.1 KB
1 +153.2 KB
Content
add-integration-ul-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -121.2 KB
Content
debug-enabled.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -196.3 KB
Content
image-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -96.0 KB
Content
integration-active.png
Size
... ... @@ -1,1 +1,1 @@
1 -64.1 KB
1 +64.2 KB
Content
integration-added.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -196.2 KB
Content
integration-dl-skip.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -105.5 KB
Content
ul-data-converter-added.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -189.4 KB
Content
ul-data-converter-device-a.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -168.3 KB
Content