Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 121.1
edited by Dilisi S
on 2025/03/08 20:30
Change comment: Mar 8 edits - part 2
To version 175.1
edited by Dilisi S
on 2025/03/20 16:51
Change comment: Mar 20 edits - part 2

Summary

Details

Page properties
Content
... ... @@ -22,17 +22,56 @@
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 -
28 28  == 2.1 ThingsBoard Cloud ==
29 29  
30 30  
31 -Add details here
33 +Go to [[https:~~/~~/thingsboard.io/>>https://thingsboard.io/]]
32 32  
35 +Click on the **Try it now**.
36 +
37 +
38 +[[image:thingsboard-1.png]]
39 +
40 +
41 +Select either the **North America** or **Europe** region. Here, we use the Europe region.
42 +
43 +[[image:thingsboard-2.png]]
44 +
45 +
46 +You can sign up with your **Google**, **GitHub**, **Facebook**, or **Apple** account. If not you can create an account with providing your **name**, **email address** and a **password**.
47 +
48 +Click on the **Sign up** button.
49 +
50 +[[image:thingsboard-3.png||height="651" width="500"]]
51 +
52 +
53 +You will be navigated to the following page.
54 +
55 +[[image:thingsboard-5.png||height="109" width="500"]]
56 +
57 +
58 +simultaneously, you will receive an email to confirm your email address. Click on the **Activate Your Account** button.
59 +
60 +
61 +[[image:thingsboard-4.png||height="249" width="500"]]
62 +
63 +
64 +Now losing to the account using your credentials:
65 +
66 +
67 +[[image:thingsboard-6.png||height="244" width="500"]]
68 +
69 +
33 33  == 2.2 HiveMQ Cloud ==
34 34  
72 +=== 2.2.1 HiveMQ Cloud ===
35 35  
74 +
36 36  Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
37 37  
38 38  Click on the **Start Free** button.
... ... @@ -107,6 +107,24 @@
107 107  You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
108 108  
109 109  
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 +
110 110  = 3. Data Converters =
111 111  
112 112  
... ... @@ -119,7 +119,6 @@
119 119  In the left navigation, click **Integrations center**, and then click **Data converters**.
120 120  
121 121  
122 -
123 123  [[image:data-converters-list-empty.png]]
124 124  
125 125  
... ... @@ -132,34 +132,133 @@
132 132  
133 133  The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
134 134  
135 -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.
191 +Click on the **JavaScript** button.
136 136  
137 -{{code language="JavaScript"}}
138 -/** Decoder **/
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.
139 139  
195 +{{info}}
196 +Please note that the value assigned to the IMEI field in the payload will be used by ThingsBoard to create a device on the platform with the same name.
197 +{{/info}}
198 +
199 +{{code language="JavaScript"}}
200 +//Version: 0.1
140 140  // decode payload to string
141 141  var payloadStr = decodeToString(payload);
142 -var data = JSON.parse(payloadStr);
143 143  
144 -var deviceName = metadata.topic.split("/")[3];
145 145  // decode payload to JSON
146 -var deviceType = 'sensor';
205 +var objdata = {};
206 +var obj1 = {};
207 +var data = decodeToJson(payload);
208 +var deviceName = data.IMEI;
209 +delete data.IMEI;
210 +var modelname = "Dragino " + data.Model;
211 +//var mod = data.mod
212 +delete data.Model;
213 +//delete data.mod
214 +var timestamp = new Date().getTime();
147 147  
148 -// Result object with device attributes/telemetry data
216 +for (var key in data) {
217 +
218 + if (Number(key)) {
219 + obj1[key] = data[key];
220 + obj1[key][obj1[key].length - 1] = Number(new Date(
221 + obj1[key][obj1[key].length - 1]));
222 +
223 + }
224 +//Alec submitted25/02/25
225 +//turn old key into new
226 + else if (key === "Reading") {
227 + objdata["reading"] = data[key];
228 + } else if (key === "work mode") {
229 + objdata["work_mode"] = data[key];
230 + } else if (key === "hum") {
231 + objdata["humidity"] = data[key];
232 + }else if (key === "hum2") {
233 + objdata["humidity2"] = data[key];
234 + } else if (key === "hum3") {
235 + objdata["humidity3"] = data[key];
236 + } else if (key === "tem") {
237 + objdata["temperature"] = data[key];
238 + } else if (key === "tem2") {
239 + objdata["temperature2"] = data[key];
240 + } else if (key === "tem3") {
241 + objdata["temperature3"] = data[key];
242 + } else if (key === "DS18B20_Temp") {
243 + objdata["temperature_pro"] = data[key];
244 + } else if (key === "ds18b20_temperature") {
245 + objdata["temperature_pro"] = data[key];
246 + } else if (key === "DS18B20_temperature_pro") {
247 + objdata["temperature_pro"] = data[key];
248 + } else if (key === "tdc send flag") {
249 + objdata["tdc_send_flag"] = data[key];
250 + } else if (key === "trigger mode") {
251 + objdata["trigger_mode"] = data[key];
252 + } else if (key === "soil dielectric constant") {
253 + objdata["soil_dielectric_constant"] = data[key];
254 + } else if (key === "door open num") {
255 + objdata["door_open_num"] = data[key];
256 + } else if (key === "door duration") {
257 + objdata["door_duration"] = data[key];
258 + } else if (key === "count time") {
259 + objdata["count_time"] = data[key];
260 + } else if (key === "last open time2") {
261 + objdata["last_open_time2"] = data[key];
262 + } else if (key === "last open time3") {
263 + objdata["last_open_time3"] = data[key];
264 + }
265 +//Alec submitted25/02/25
266 + else {
267 + objdata[key] = data[key]
268 + }
269 +}
270 +var listdata = [{
271 + "ts": timestamp,
272 + "values": objdata
273 +}]
274 +for (var key1 in obj1) {
275 + if (modelname == "Dragino RS485-NB") {
276 + listdata.push({
277 + "ts": obj1[key1][obj1[key1].length - 1],
278 + "values": {
279 + "Payload": obj1[key1][0],
280 + }
281 + })
282 + } else {
283 + listdata.push({
284 + "ts": obj1[key1][obj1[key1].length - 1],
285 + "values": {
286 + "values": obj1[key1]
287 + },
288 + })
289 + }
290 +}
149 149  var result = {
292 +
150 150   deviceName: deviceName,
151 - deviceType: deviceType,
294 + deviceType: modelname,
152 152   attributes: {
153 - integrationName: metadata['integrationName'],
296 + model: modelname,
297 + //customerName: "NB-CB",
298 + //groupName: "NB-CB",
299 + //integrationName: metadata['integrationName']
300 +
154 154   },
155 - telemetry: {
156 - temperature: data.temperature,
157 - humidity: data.humidity,
158 - }
159 -};
302 + telemetry: listdata
303 +}
160 160  
161 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
305 +function decodeToString(payload) {
306 + return String.fromCharCode.apply(String, payload);
307 +}
162 162  
309 +function decodeToJson(payload) {
310 + // covert payload to string.
311 + var str = decodeToString(payload);
312 +
313 + // parse string to JSON
314 + var data = JSON.parse(str);
315 + return data;
316 +}
317 +
163 163  return result;
164 164  {{/code}}
165 165  
... ... @@ -167,191 +167,308 @@
167 167  Click on the **Add** button.
168 168  
169 169  
325 +[[image:mqtt-uplink.png||width="500"]]
170 170  
171 -[[image:add-uplink-data-converter.png||height="529" width="500"]]
172 172  
173 173  
174 174  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
175 175  
331 +
176 176  [[image:data-converter-list-showing-uplink-dc.png]]
177 177  
178 178  
335 += 4. Add Integration =
179 179  
180 -== 3.2 Downlink ==
181 181  
338 +In the left navigation, click **Integrations center**, and then click **Integrations**.
182 182  
183 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
184 184  
341 +[[image:integrations-list-empty.png]]
185 185  
186 -[[image:create-new-converter-menu.png||width="500"]]
187 187  
344 +On the **Integrations** page, click on the '**+**' button.
188 188  
189 189  
190 -The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
347 +The **Add integration** window appears.
191 191  
192 -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.
349 +In the **Add integration** window, configure the following settings:
193 193  
194 194  
195 -{{code language="JavaScript"}}
196 -// Encode downlink data from incoming Rule Engine message
352 +**Basic settings:**
197 197  
198 -// msg - JSON message payload downlink message json
199 -// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
200 -// metadata - list of key-value pairs with additional data about the message
201 -// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
354 +* **Integration type**: MQTT
355 +* **Name**: MQTT integration NB/CB
356 +* **Enable integration**: YES
357 +* **Allows create devices or assets**: YES
202 202  
203 -/** Encoder **/
359 +Click **Next** button.
204 204  
205 -var data = {};
206 206  
207 -// Process data from incoming message and metadata
362 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
208 208  
209 -data.tempFreq = msg.temperatureUploadFrequency;
210 -data.humFreq = msg.humidityUploadFrequency;
211 211  
212 -data.devSerialNumber = metadata['ss_serialNumber'];
365 +**Uplink data converter:**
213 213  
214 -// Result object with encoded downlink payload
215 -var result = {
367 +* Click on the **Select existing** button.
368 +* **Uplink data converter**: Select **MQTT Uplink Converter NB/CB **from the dropdown list.
216 216  
217 - // downlink data content type: JSON, TEXT or BINARY (base64 format)
218 - contentType: "JSON",
370 +Click **Next** button.
219 219  
220 - // downlink data
221 - data: JSON.stringify(data),
222 222  
223 - // Optional metadata object presented in key/value format
224 - metadata: {
225 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
226 - }
373 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
227 227  
228 -};
229 229  
230 -return result;
231 -{{/code}}
376 +**Downlink data converter:**
232 232  
378 +Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
233 233  
380 +* Click on the **Skip **button in the Downlink data converter section.
381 +
382 +Click **Skip** button.
383 +
384 +
385 +[[image:integration-dl-skip.png||height="511" width="500"]]
386 +
387 +
388 +
389 +**Connection:**
390 +
391 +* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
392 +* **Port**: 8883
393 +* **Credentials**: Basic
394 +* **Enable SSL**: YES
395 +* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
396 +* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
397 +* **Topic: v1/devices/me/telemetry** (The topic can be anything; you can even use just the device name. For example, you can use your device name here, such as S31B-NB.)
398 +* **QoS:** 0-At most once
399 +
400 +
401 +
402 +[[image:add-integration-connection.png||height="511" width="500"]]
403 +
404 +
405 +Click on the **Advanced settings** button.
406 +
407 +* **Clean session:** YES
408 +* **Retained**: YES
409 +
410 +[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
411 +
412 +
413 +Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
414 +
415 +
416 +[[image:check-connection.png||height="83" width="300"]]
417 +
418 +
419 +If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
420 +
421 +
422 +[[image:connection-success.png||height="511" width="500"]]
423 +
424 +
234 234  Click on the **Add** button.
235 235  
427 +You should see that the newly added integration is listed on the **Integrations** page.
236 236  
429 +Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
237 237  
238 -[[image:add-downlink-data-converter.png||height="529" width="500"]]
239 239  
432 +[[image:new-integration-pending.png]]
240 240  
241 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
242 242  
435 += 5. Verifying the receipt of data from virtual devices =
243 243  
244 -[[image:data-converters-list.png]]
245 245  
438 +== 5.1 How does it work? ==
246 246  
247 247  
248 -= 4. Add Integration =
441 +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.
249 249  
443 +The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
250 250  
251 -In the left navigation, click **Integrations center**, and then click **Integrations**.
445 +(% 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.
252 252  
447 +{{code language="none"}}
448 +{"IMEI": "S31B-NB", "temperature": 27, ......}
449 +{{/code}}
253 253  
254 -[[image:integrations-list-empty.png]]
451 +Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
255 255  
256 256  
257 -On the **Integrations** page, click on the '**+**' button.
454 +== 5.2 Sending messages ==
258 258  
259 259  
260 -The **Add integration** window appears.
457 +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.
261 261  
262 -In the **Add integration** window, configure the following settings:
459 +{{code language="none"}}
460 +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}'
461 +{{/code}}
263 263  
463 +If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
264 264  
265 -**Basic settings:**
266 266  
267 -* **Integration type**: MQTT
268 -* **Name**: MQTT integration NB/CB
269 -* **Enable integration**: YES
270 -* **Allows create devices or assets**: YES
466 +[[image:integration-active.png]]
271 271  
272 -Click **Next** button.
273 273  
469 +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**.
274 274  
275 275  
276 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
472 +[[image:new-device.png]]
277 277  
278 278  
279 -**Uplink data converter:**
475 +== 5.3 Viewing messages ==
280 280  
281 -* Click on the **Select existing** button.
282 -* **Uplink data converter**: Select **MQTT Uplink Converter NB/CB **from the dropdown list.
283 283  
284 -Click **Next** button.
478 +Go back to the **Integrations** page.
285 285  
480 +Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
286 286  
482 +Click on the **Edit** button (//**pen icon**//).
287 287  
288 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
484 +Click on the **Disabled** button in the upper-right corner.
289 289  
486 +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.
290 290  
291 -**Downlink data converter:**
488 +Click on the **Apply** button.
292 292  
293 -* Click on the **Select existing** button.
294 -* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
490 +Then click on the **Apply changes** (//**tick icon**//) button.
295 295  
296 -Click **Next** button.
297 297  
493 +[[image:Screenshot 2025-03-18 at 09.23.10.png]]
298 298  
299 299  
300 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
496 +Now go to the **Events** tab.
301 301  
498 +Select the Event type as **Debug** from the dropdown list.
302 302  
303 -**Connection:**
500 +Now you can see all the Uplink messages you are simulating through the MQTT broker. The status should be OK if there is no errors in your integration.
304 304  
305 -* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
306 -* **Port**: 8883
307 -* **Credentials**: Basic
308 -* **Enable SSL**: YES
309 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
310 -* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
311 -* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
312 -* **QoS:** 0-At most once
313 313  
314 -[[image:add-integration-connection.png||height="511" width="500"]]
503 +[[image:Screenshot 2025-03-16 at 18.38.59.png]]
315 315  
316 316  
317 -Click on the **Advanced settings** button.
506 +Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
318 318  
319 -* **Clean session:** NO
320 -* **Retained**: NO
321 321  
322 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
509 +[[image:Screenshot 2025-03-16 at 18.39.12.png]]
323 323  
324 324  
325 -Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
512 +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.
326 326  
327 327  
328 -[[image:check-connection.png||height="83" width="300"]]
515 += 6. Creating a Dashboard =
329 329  
517 +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.
330 330  
331 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
332 332  
520 +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.
333 333  
334 -[[image:connection-success.png||height="511" width="500"]]
335 335  
523 +First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
336 336  
525 +{{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}}
526 +
527 +
528 +In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
529 +
530 +
531 +[[image:dashboard-1.png]]
532 +
533 +
534 +In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
535 +
337 337  Click on the **Add** button.
338 338  
339 -You should see that the newly added integration is listed on the **Integrations** page.
340 340  
341 -Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
539 +[[image:dashboard-2.png||height="526" width="500"]]
342 342  
343 343  
542 +Click on the **Add widget / Add new widget** button.
344 344  
345 -[[image:new-integration-pending.png]]
346 346  
545 +[[image:dashboard-3.png]]
347 347  
348 -= 5. Verifying the receipt of data from the device =
349 349  
548 +In the **Select widgets bundle** window, click **Charts**.
350 350  
351 -On the terminal, issue the following MQTT command which simulates the device S31B-NB.
352 352  
551 +[[image:dashboard-4.png||height="537" width="700"]]
552 +
553 +
554 +
555 +In the **Charts: select widget** window, click **Time series chart**.
556 +
557 +
558 +[[image:dashboard-5.png||height="525" width="700"]]
559 +
560 +
561 +Configure the **Time series chart** widget as follows:
562 +
563 +* **Datasource** - select S31B-NB device you provisioned.
564 +* **Series**:
565 +** **temperature** - you can see this key by default.
566 +** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
567 +* Click on the **Add** button.
568 +
569 +[[image:timeseries-1.png||height="491" width="700"]]
570 +
571 +
572 +The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
573 +
574 +Click the **Save** button to add the widget to the dashboard.
575 +
576 +
577 +[[image:timeseries-3.png||height="347" width="700"]]
578 +
579 +
580 +Now send the following MQTT messages from the terminal to simulate the data.
581 +
582 +
353 353  {{code language="none"}}
354 -mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}"
584 +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}'
585 +
586 +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}'
587 +
588 +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}'
589 +
355 355  {{/code}}
356 356  
357 -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.
592 +The chart will update with the values in realtime, as shown in the below image.
593 +
594 +
595 +[[image:timeseries-4.png||height="316" width="700"]]
596 +
597 +
598 += 7. Configure NB-IoT Sensor =
599 +
600 +
601 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
602 +
603 +First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
604 +
605 +
606 +**AT Commands**
607 +
608 +* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
609 +* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
610 +* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
611 +* **AT+CLIENT=null**
612 +* **AT+UNAME=<MQTT Username>**
613 +* **AT+PWD=<MQTT Password>**
614 +* **AT+SERVADDR=<Broker address, Port>**
615 +
616 +Test your uplink by pressing the ACT button for 1 second.
617 +
618 +
619 +
620 +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**.
621 +
622 +{{info}}
623 +The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
624 +{{/info}}
625 +
626 +[[image:image-4.png]]
627 +
628 +
629 +
add-integration-connection.png
Size
... ... @@ -1,1 +1,1 @@
1 -124.4 KB
1 +158.1 KB
Content
Screenshot 2025-03-16 at 18.38.59.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +221.2 KB
Content
Screenshot 2025-03-16 at 18.39.12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +211.9 KB
Content
Screenshot 2025-03-18 at 09.23.10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +78.7 KB
Content
dashboard-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +271.1 KB
Content
dashboard-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +112.2 KB
Content
dashboard-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +141.3 KB
Content
dashboard-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +803.7 KB
Content
dashboard-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +476.1 KB
Content
device-provision-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +265.7 KB
Content
device-provision-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +213.9 KB
Content
emqx.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +39.1 KB
Content
image-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +96.0 KB
Content
ins1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +28.8 KB
Content
integration-active.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +64.2 KB
Content
integration-dl-skip.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +105.5 KB
Content
mqtt-uplink.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +175.1 KB
Content
new-device.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
telemetry-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +191.9 KB
Content
telemetry-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +185.1 KB
Content
thingsboard-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +1.9 MB
Content
thingsboard-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +901.1 KB
Content
thingsboard-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +146.3 KB
Content
thingsboard-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +122.1 KB
Content
thingsboard-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +106.7 KB
Content
thingsboard-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +119.3 KB
Content
timeseries-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +179.1 KB
Content
timeseries-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +174.2 KB
Content
timeseries-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +159.0 KB
Content