Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 128.1
edited by Dilisi S
on 2025/03/08 22:01
Change comment: Uploaded new attachment "thingsboard-6.png", version {1}
To version 216.1
edited by Dilisi S
on 2025/04/21 18:37
Change comment: Uploaded new attachment "Screenshot 2025-04-21 123647.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -22,7 +22,10 @@
22 22  To complete this tutorial, you need to have the following:
23 23  
24 24  * ThingsBoard cloud account
25 -* HiveMQ Cloud account
25 +* MQTT Broker (public or private) such as,
26 +** **[[HiveMQ Cloud>>https://www.hivemq.com]] - You can create a free account to try it or subscribe for a paid account. - We use HiveMQ Cloud as the MQTT broker to build example in this tutorial.**
27 +** [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] - The public MQTT server is only used for MOTT learning and testing, and should not be used in the production environment.
28 +** [[lns1.thingseye.io>>http://lns1.thingseye.io/]] - This is Dragino's MQTT broker, which requires a CA certificate to use.
26 26  
27 27  == 2.1 ThingsBoard Cloud ==
28 28  
... ... @@ -40,14 +40,35 @@
40 40  [[image:thingsboard-2.png]]
41 41  
42 42  
43 -You can sign up with your Google, GitHub, Facebook, or Apple account. If not you can create an account with providing your name, email address and a password.
46 +You can sign up with your **Google**, **GitHub**, **Facebook**, or **Apple** account. If not you can create an account with providing your **name**, **email address** and a **password**.
44 44  
48 +Click on the **Sign up** button.
49 +
45 45  [[image:thingsboard-3.png||height="651" width="500"]]
46 46  
47 47  
53 +You will be navigated to the following page.
54 +
55 +[[image:thingsboard-5.png||height="109" width="500"]]
56 +
57 +
58 +simultaneously, you will receive an email to confirm your email address. Click on the **Activate Your Account** button.
59 +
60 +
61 +[[image:thingsboard-4.png||height="249" width="500"]]
62 +
63 +
64 +Now losing to the account using your credentials:
65 +
66 +
67 +[[image:thingsboard-6.png||height="244" width="500"]]
68 +
69 +
48 48  == 2.2 HiveMQ Cloud ==
49 49  
72 +=== 2.2.1 HiveMQ Cloud ===
50 50  
74 +
51 51  Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
52 52  
53 53  Click on the **Start Free** button.
... ... @@ -122,12 +122,33 @@
122 122  You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
123 123  
124 124  
149 +=== 2.2.2 emqx ===
150 +
151 +
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.
153 +
154 +
155 +[[image:emqx.png||height="420" width="500"]]
156 +
157 +
158 +=== 2.2.3 Ins1.thingseye.io ===
159 +
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 +
162 +If customers need to use this MQTT connection with ThingsBoard, they need to contact the TE team to obtain three license files.
163 +
164 +[[image:ins1.png||height="310" width="500"]]
165 +
166 +
167 +
125 125  = 3. Data Converters =
126 126  
127 127  
128 128  In **ThingsBoard**, **Data Converters** are components used to transform incoming or outgoing data between different formats, typically to convert raw telemetry data from devices into a structured format that ThingsBoard can understand, or vice versa.
129 129  
173 +**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**.
130 130  
175 +
131 131  == 3.1 Uplink ==
132 132  
133 133  
... ... @@ -134,11 +134,10 @@
134 134  In the left navigation, click **Integrations center**, and then click **Data converters**.
135 135  
136 136  
137 -
138 138  [[image:data-converters-list-empty.png]]
139 139  
140 140  
141 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
185 +On the **Data converters** page, click on the ‘**+**’ button, and then click on **Create new converter** from the dropdown menu.
142 142  
143 143  
144 144  
... ... @@ -145,228 +145,390 @@
145 145  [[image:create-new-converter-menu.png||height="259" width="500"]]
146 146  
147 147  
148 -The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
192 +The **Add data converter** window appears.
149 149  
150 -Click on the **TBEL** button if not selected it by default. Delete the existing decoder function in the code editor. Now copy and paste the following decoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
194 +Name it ‘**MQTT Uplink Converter**’ and select the Type as **Uplink**.
151 151  
152 -{{code language="JavaScript"}}
153 -/** Decoder **/
196 +Click on the **TBEL** button if it has not been selected by default.
154 154  
155 -// decode payload to string
156 -var payloadStr = decodeToString(payload);
157 -var data = JSON.parse(payloadStr);
198 +Replace the default TBEL decoder function with the following universal TBEL decoder function, which decodes MQTT payload from any Dragino NB-IoT device.
158 158  
159 -var deviceName = metadata.topic.split("/")[3];
160 -// decode payload to JSON
161 -var deviceType = 'sensor';
162 162  
163 -// Result object with device attributes/telemetry data
164 -var result = {
201 +{{code language="JavaScript"}}
202 +// decode payload to JSON
203 +var pattern = "yyyy/MM/dd HH:mm:ss";
204 +var objdata = {};
205 +var obj1 = {};
206 +var data = decodeToJson(payload);
207 +var deviceName = data.IMEI;
208 +data.remove("IMEI");
209 +var modelname = "Dragino "+ data.Model;
210 +//var mod = data.mod
211 +data.remove("Model");
212 +//delete data.mod
213 +var timestamp = new Date().getTime();
214 +foreach (entry: data.entrySet()) {
215 + var key = entry.getKey();
216 + var value = entry.getValue();
217 + //objdata[key] = data[key]
218 + if(key.matches("^-?\\d+$")){ //is number
219 + obj1[key]=data[key];
220 + var index = obj1[key].length-1;
221 + obj1[key][index]=new Date(obj1[key][index],pattern).getTime();
222 + }
223 + else if (key==="bat"||key==="BAT"){
224 + objdata["battery"] = data[key];
225 + }
226 + else{
227 + objdata[key] = data[key];
228 +}}
229 +var listdata = [{"ts":timestamp,"values":objdata}];
230 +foreach ( entry1: obj1.entrySet()){
231 + var key1 = entry1.getKey();
232 + var value1 = entry1.getValue();
233 + var index = obj1[key1].length-1;
234 + var ts = obj1[key1][index];
235 + if (modelname=="Dragino RS485-NB"){
236 + listdata.push({"ts":ts,"values":{"Payload":obj1[key1][0]}});
237 + }
238 + else{
239 + listdata.push({"ts":ts,"values":{"values":obj1[key1]}});
240 + }
241 +}
242 + var result = {
165 165   deviceName: deviceName,
166 - deviceType: deviceType,
244 + deviceType: modelname,
167 167   attributes: {
168 - integrationName: metadata['integrationName'],
246 + model: modelname
247 + //customerName: "NB-CB",
248 + //groupName: "NB-CB",
249 + //integrationName: metadata['integrationName']
169 169   },
170 - telemetry: {
171 - temperature: data.temperature,
172 - humidity: data.humidity,
173 - }
251 + telemetry: listdata
174 174  };
175 -
176 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
177 -
178 178  return result;
179 179  {{/code}}
180 180  
181 181  
182 -Click on the **Add** button.
257 +Once you modify the decoder function, click on the **Add** button.
183 183  
184 184  
260 +[[image:mqtt-uplink-converter.png||height="498" width="500"]]
185 185  
186 -[[image:add-uplink-data-converter.png||height="529" width="500"]]
187 187  
188 188  
189 189  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
190 190  
191 -[[image:data-converter-list-showing-uplink-dc.png]]
192 192  
193 193  
268 +[[image:data-converters-list.png]]
194 194  
195 -== 3.2 Downlink ==
196 196  
271 += 4. Add Integration =
197 197  
198 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
199 199  
274 +In the left navigation, click **Integrations center**, and then click **Integrations**.
200 200  
201 -[[image:create-new-converter-menu.png||width="500"]]
202 202  
277 +[[image:integrations-list-empty.png]]
203 203  
204 204  
205 -The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
280 +On the **Integrations** page, click on the '**+**' button.
206 206  
207 -Click on the **TBEL** button if not selected it by default. Now copy and paste the following encoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This encoder function is compatible for both NB and CB series devices.
208 208  
283 +The **Add integration** window appears.
209 209  
210 -{{code language="JavaScript"}}
211 -// Encode downlink data from incoming Rule Engine message
285 +In the **Add integration** window, configure the following settings:
212 212  
213 -// msg - JSON message payload downlink message json
214 -// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
215 -// metadata - list of key-value pairs with additional data about the message
216 -// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
217 217  
218 -/** Encoder **/
288 +**Basic settings:**
219 219  
220 -var data = {};
290 +* **Integration type**: MQTT
291 +* **Name**: MQTT integration
292 +* **Enable integration**: YES
293 +* **Allow create devices or assets**: YES
221 221  
222 -// Process data from incoming message and metadata
295 +Click **Next** button.
223 223  
224 -data.tempFreq = msg.temperatureUploadFrequency;
225 -data.humFreq = msg.humidityUploadFrequency;
226 226  
227 -data.devSerialNumber = metadata['ss_serialNumber'];
228 228  
229 -// Result object with encoded downlink payload
230 -var result = {
299 +[[image:add-integration-part-1.png||height="483" width="500"]]
231 231  
232 - // downlink data content type: JSON, TEXT or BINARY (base64 format)
233 - contentType: "JSON",
234 234  
235 - // downlink data
236 - data: JSON.stringify(data),
302 +**Uplink data converter:**
237 237  
238 - // Optional metadata object presented in key/value format
239 - metadata: {
240 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
241 - }
304 +* Click on the **Select existing** button.
305 +* **Uplink data converter**: Select **MQTT Uplink Converter NB/CB **from the dropdown list.
242 242  
243 -};
307 +Click **Next** button.
244 244  
245 -return result;
246 -{{/code}}
247 247  
248 248  
311 +[[image:add-integration-part-2.png||height="484" width="500"]]
312 +
313 +
314 +**Downlink data converter:**
315 +
316 +Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
317 +
318 +* Click on the **Skip **button in the Downlink data converter section.
319 +
320 +Click **Skip** button.
321 +
322 +
323 +[[image:integration-dl-skip.png||height="511" width="500"]]
324 +
325 +
326 +
327 +**Connection:**
328 +
329 +* **Host**: Host URL (Eg, **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
330 +* **Port**: 8883 (the port number may differ based on your MQTT broker)
331 +* **Credentials type**: Basic
332 +* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
333 +* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
334 +* **Enable SSL**: YES
335 +* **Topic**: # (the # symbol indicates that it filters all topics).
336 +* **QoS:** 0-At most once
337 +
338 +
339 +[[image:add-integration-4.png||height="484" width="500"]]
340 +
341 +
342 +Click on the **Advanced settings** button.
343 +
344 +* **Clean session:** YES
345 +* **Retained**: YES
346 +
347 +[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
348 +
349 +
350 +Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
351 +
352 +
353 +[[image:check-connection.png||height="83" width="300"]]
354 +
355 +
356 +If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
357 +
358 +
359 +[[image:connection-success.png||height="511" width="500"]]
360 +
361 +
249 249  Click on the **Add** button.
250 250  
364 +You should see that the newly added integration is listed on the **Integrations** page.
251 251  
366 +Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
252 252  
253 -[[image:add-downlink-data-converter.png||height="529" width="500"]]
254 254  
255 255  
256 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
370 +[[image:integrations-pending.png]]
257 257  
258 258  
259 -[[image:data-converters-list.png]]
373 += 5. Verifying the receipt of data from virtual devices =
260 260  
261 261  
376 +== 5.1 How does it work? ==
262 262  
263 -= 4. Add Integration =
264 264  
379 +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.
265 265  
266 -In the left navigation, click **Integrations center**, and then click **Integrations**.
381 +The Mosquitto client publishes messages (payloads) to a topic - for example, # or device/ts01-nb. You can, of course, use any topic you prefer.
267 267  
268 268  
269 -[[image:integrations-list-empty.png]]
384 +(% 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.
270 270  
386 +{{code language="none"}}
387 +{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}
388 +{{/code}}
271 271  
272 -On the **Integrations** page, click on the '**+**' button.
273 273  
391 +== 5.2 Sending messages ==
274 274  
275 -The **Add integration** window appears.
276 276  
277 -In the **Add integration** window, configure the following settings:
394 +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.
278 278  
396 +{{code language="none"}}
397 +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}'
398 +{{/code}}
279 279  
280 -**Basic settings:**
400 +If the integration was performed without errors, a new device named **350693903995577 **is created in the **Devices **section.
281 281  
282 -* **Integration type**: MQTT
283 -* **Name**: MQTT integration NB/CB
284 -* **Enable integration**: YES
285 -* **Allows create devices or assets**: YES
286 286  
287 -Click **Next** button.
403 +[[image:new-device-1.png]]
288 288  
289 289  
406 +The status of the integration also changes to '**Active**' after the first telemetry transmission.
290 290  
291 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
292 292  
409 +[[image:Screenshot 2025-04-21 122154.png]]
293 293  
294 -**Uplink data converter:**
295 295  
296 -* Click on the **Select existing** button.
297 -* **Uplink data converter**: Select **MQTT Uplink Converter NB/CB **from the dropdown list.
298 298  
299 -Click **Next** button.
413 +**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.**
300 300  
301 301  
416 +== 5.3 Viewing messages ==
302 302  
303 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
304 304  
419 +Go back to the **Integrations** page.
305 305  
306 -**Downlink data converter:**
421 +Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
307 307  
308 -* Click on the **Select existing** button.
309 -* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
423 +Click on the **Edit** button (//**pen icon**//).
310 310  
311 -Click **Next** button.
425 +Click on the **Disabled** button in the upper-right corner.
312 312  
427 +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.
313 313  
429 +Click on the **Apply** button.
314 314  
315 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
431 +Then click on the **Apply changes** (//**tick icon**//) button.
316 316  
317 317  
318 -**Connection:**
434 +[[image:debug-enabled.png||height="301" width="700"]]
319 319  
320 -* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
321 -* **Port**: 8883
322 -* **Credentials**: Basic
323 -* **Enable SSL**: YES
324 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
325 -* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
326 -* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
327 -* **QoS:** 0-At most once
328 328  
329 -[[image:add-integration-connection.png||height="511" width="500"]]
330 330  
331 331  
332 -Click on the **Advanced settings** button.
439 +Now go to the **Events** tab.
333 333  
334 -* **Clean session:** NO
335 -* **Retained**: NO
441 +Select the **Event type** as **Debug** from the dropdown list.
336 336  
337 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
443 +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:
338 338  
445 +{{code language="none"}}
446 +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}'
447 +{{/code}}
339 339  
340 -Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
449 +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.
341 341  
342 342  
343 -[[image:check-connection.png||height="83" width="300"]]
452 +[[image:Screenshot 2025-03-26 at 19.49.31.png]]
344 344  
345 345  
346 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
347 347  
456 +Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
348 348  
349 -[[image:connection-success.png||height="511" width="500"]]
350 350  
459 +[[image:Screenshot 2025-03-26 at 19.47.52.png]]
351 351  
461 +
462 +
463 +
464 +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.
465 +
466 +
467 += 6. Creating a Dashboard =
468 +
469 +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.
470 +
471 +
472 +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.
473 +
474 +
475 +First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
476 +
477 +{{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}}
478 +
479 +
480 +In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
481 +
482 +
483 +[[image:dashboard-1.png]]
484 +
485 +
486 +In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
487 +
352 352  Click on the **Add** button.
353 353  
354 -You should see that the newly added integration is listed on the **Integrations** page.
355 355  
356 -Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
491 +[[image:dashboard-2.png||height="526" width="500"]]
357 357  
358 358  
494 +Click on the **Add widget / Add new widget** button.
359 359  
360 -[[image:new-integration-pending.png]]
361 361  
497 +[[image:dashboard-3.png]]
362 362  
363 -= 5. Verifying the receipt of data from the device =
364 364  
500 +In the **Select widgets bundle** window, click **Charts**.
365 365  
366 -On the terminal, issue the following MQTT command which simulates the device S31B-NB.
367 367  
503 +[[image:dashboard-4.png||height="537" width="700"]]
504 +
505 +
506 +
507 +In the **Charts: select widget** window, click **Time series chart**.
508 +
509 +
510 +[[image:dashboard-5.png||height="525" width="700"]]
511 +
512 +
513 +Configure the **Time series chart** widget as follows:
514 +
515 +* **Datasource** - select **Device A** device you provisioned.
516 +* **Series**:
517 +** **temperature** - you can see this key by default.
518 +** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
519 +* Click on the **Add** button.
520 +
521 +{{info}}
522 +You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
523 +{{/info}}
524 +
525 +[[image:Screenshot 2025-03-31 at 06.51.15.png||height="485" width="700"]]
526 +
527 +
528 +The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
529 +
530 +Click the **Save** button to add the widget to the dashboard.
531 +
532 +
533 +[[image:timeseries-3.png||height="347" width="700"]]
534 +
535 +
536 +Now send the following MQTT messages from the terminal to simulate the data.
537 +
538 +
368 368  {{code language="none"}}
369 -mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}"
540 +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}'
541 +
542 +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}'
543 +
544 +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}'
370 370  {{/code}}
371 371  
372 -If the integration was performed without errors, after the transmission of the first telemetry, a new device with the name “S31B-NB” will appear in the Devices → All. Also, you can verify the input and output data, respectively, before and after conversion in Data converters → UDP Uplink Converter NB/CB → Events.
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 Physical 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' 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.
576 +
577 +
578 +[[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
data-converters-list.png
Size
... ... @@ -1,1 +1,1 @@
1 -212.2 KB
1 +19.0 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
Screenshot 2025-03-31 at 06.51.15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +179.5 KB
Content
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
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-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
add-integration-ul-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +121.2 KB
Content
dashboard-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +271.1 KB
Content
dashboard-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +112.2 KB
Content
dashboard-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +141.3 KB
Content
dashboard-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +803.7 KB
Content
dashboard-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +476.1 KB
Content
debug-enabled.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.3 KB
Content
device-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +34.5 KB
Content
device-provision-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +265.7 KB
Content
device-provision-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +213.9 KB
Content
emqx.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +39.1 KB
Content
image-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +96.0 KB
Content
ins1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +28.8 KB
Content
integration-active.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +64.1 KB
Content
integration-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.2 KB
Content
integration-dl-skip.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +105.5 KB
Content
integrations-pending.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +19.8 KB
Content
mqtt-uplink-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +75.3 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-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +34.7 KB
Content
new-device.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
telemetry-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +191.9 KB
Content
telemetry-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +185.1 KB
Content
timeseries-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +179.1 KB
Content
timeseries-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +174.2 KB
Content
timeseries-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +159.0 KB
Content
ul-data-converter-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +189.4 KB
Content
ul-data-converter-device-a.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +168.3 KB
Content