Changes for page ThingsBoard
Last modified by Dilisi S on 2025/04/23 19:23
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 17 added, 27 removed)
- add-downlink-data-converter.png
- add-integration-connection-advanced-settings.png
- add-uplink-data-converter.png
- check-connection.png
- connection-success.png
- create-new-converter-menu.png
- data-converters-list-empty.png
- data-converters-list.png
- hivemq-10.png
- hivemq-2.png
- hivemq-3.png
- hivemq-4.jpg
- hivemq-5.png
- hivemq-6.png
- hivemq-7.png
- hivemq-8.png
- hivemq-9.png
- hivwmq-1.png
- integration-active.png
- integrations-list-empty.png
- new-integration-pending.png
- thingsboard-1.png
- thingsboard-2.png
- thingsboard-3.png
- thingsboard-4.png
- thingsboard-5.png
- thingsboard-6.png
- ThingsBoard-add-data-converter.png
- ThingsBoard-add-new-device.png
- ThingsBoard-new-data-converter.png
- add-connection-success.png
- data-converter-list-page.png
- data-converter-list.png
- device-list-empty.png
- downlink-data-converter.png
- integrations-list-added-pending.png
- mqtt-command-1.png
- mqtt-command-2.png
- new-device-access-token.png
- new-device-check-connectivity.png
- new-device-device-details.png
- new-device-telemetry-test.png
- uplink-data-converter.png
- virtual-device-active.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. pradeeka1 +XWiki.Xiaoling - Content
-
... ... @@ -6,9 +6,6 @@ 6 6 Draft Document 7 7 {{/warning}} 8 8 9 - 10 - 11 - 12 12 = 1. Introduction = 13 13 14 14 ... ... @@ -17,130 +17,78 @@ 17 17 The **NB series** devices end with the suffix **-NB**, and the **CB series** devices end with the suffix **-CB**. For example, **S31B-NB** is an **NB device**, and **S31-CB** is a **CB device**. 18 18 19 19 20 -= 2. Prerequisites=17 += 2. Add New Device = 21 21 22 -To complete this tutorial, you need to have the following: 23 23 24 -* ThingsBoard cloud account 25 -* HiveMQ Cloud account 20 +First, we will add a device to simulate data using MQTT. This device does not represent a real physical device but serves as a common virtual device for all Dragino NB/CB devices. 26 26 27 - ==2.1 ThingsBoardCloud==22 +In the left navigation, click **Entities** and then click **Devices**. 28 28 24 +[[image:device-list-empty.png]] 29 29 30 -Go to [[https:~~/~~/thingsboard.io/>>https://thingsboard.io/]] 31 31 32 - Click on the **Tryit now**.27 +On the **Devices **page, click on the ‘**+**’ button, and then click on the **Add new device **from the dropdown menu. 33 33 34 34 35 -[[image: thingsboard-1.png]]30 +[[image:ThingsBoard-add-new-device.png||height="279" width="500"]] 36 36 37 37 38 - Select eitherthe**NorthAmerica** or**Europe**region.Here,weusetheEurope region.33 +The **Add new device** window appears. Name the device, for example '**Virtual NB/CB device**'. 39 39 40 - [[image:thingsboard-2.png]]35 +Click on the **Next: Credentials** button. 41 41 42 42 43 - You can signupwith your **Google**, **GitHub**, **Facebook**, or **Apple** account. If not you can createan accountwithprovidingyour **name**, **emailaddress** and a **password**.38 +[[image:new-device-device-details.png||height="529" width="500"]] 44 44 45 -Click on the **Sign up** button. 46 46 47 - [[image:thingsboard-3.png||height="651"width="500"]]41 +Click the **Access token** button if it is not selected by default. 48 48 43 +Copy the **Access token** to a text editor, as you will need it in the section **'Sending data from an MQTT client'**. 49 49 50 - You will be navigatedto thefollowing page.45 +Click on the **Add** button. 51 51 52 -[[image: thingsboard-5.png||height="109" width="500"]]47 +[[image:new-device-access-token.png||height="528" width="500"]] 53 53 54 54 55 - simultaneously, you will receive an email to confirm your email address.Click on the **Activate Your Account** button.50 +Click on the **MQTT** button. 56 56 52 +Then, select the operating system you are going to use with the **Mosquitto MQTT Broker**. This example shows sending a command from a computer running **MacOS**. First, install the necessary client tools on your computer. 57 57 58 - [[image:thingsboard-4.png||height="249"width="500"]]54 +Copy the MQTT pub command in the '**Execute the following command**' section. 59 59 56 +{{code language="none"}} 57 +mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/me/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:25}" 58 +{{/code}} 60 60 61 -No wlosingtotheccountusingyourcredentials:60 +Note that the **State** is still shown as **'Inactive'** in the **Latest telemetry** section. 62 62 62 +[[image:new-device-check-connectivity.png||height="522" width="500"]] 63 63 64 -[[image:thingsboard-6.png||height="244" width="500"]] 65 65 65 +On the terminal, enter the command you copied. This command sends the MQTT payload **{temperature:25}** as telemetry data from a virtual device named **'me'**. Of course, you can replace **'me'** with a device name or use the wildcard character **'+'** to match any device name. 66 66 67 -== 2.2 HiveMQ Cloud == 68 68 68 +[[image:mqtt-command-1.png||height="228" width="700"]] 69 69 70 -Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]] 71 71 72 - Clickon the **StartFree**button.71 +If the command is successful, you can see the telemetry data you sent under the **Latest telemetry** section. Note that the **State** is now **'Active'** in the **Latest telemetry** section. 73 73 74 -[[image:hivwmq-1.png]] 75 75 74 +[[image:new-device-telemetry-test.png||height="520" width="500"]] 76 76 77 -Click on the **Sign Up FREE Now** button in the **HIVEMQ CLOUD** section. 78 78 79 - [[image:hivemq-2.png]]77 +Send the same command again, only changing the **temperature** value, to see how the **Latest telemetry** section updates its data. 80 80 79 +Once you are done experimenting with this, close the window by clicking the **Close** button. 81 81 82 -Click on the **Sign Up** button. 83 83 84 - Youcansign upwithHiveMQ usingyour **GitHub**,**Google**, or **LinkedIn** account.82 +[[image:mqtt-command-2.png||height="227" width="700"]] 85 85 86 -If not, provide your **email address** and a **password** to create an account by clicking on the **Sign Up** button. 87 87 88 88 89 -[[image: hivemq-3.png]]86 +[[image:virtual-device-active.png]] 90 90 91 91 92 -You will receive an email to verify your email address. Click on the **Confirm my account** button. 93 - 94 - 95 -[[image:hivemq-4.jpg||height="889" width="400"]] 96 - 97 - 98 -You will be redirected to a page asking you to complete your profile. Once done, click the **Continue** button. 99 - 100 - 101 -[[image:hivemq-5.png||height="655" width="700"]] 102 - 103 - 104 -Select the CloudMQ Cloud plan you need. For testing purposes, select the **Serverless FREE** plan by clicking on the **Create Serverless Cluster** button. 105 - 106 - 107 -[[image:hivemq-6.png]] 108 - 109 - 110 -You will be navigated to the **Your Clusters** page. Click on the **Manage Cluster** button. 111 - 112 -[[image:hivemq-7.png]] 113 - 114 - 115 -In your cluster page, you can find some useful parameters you need to create a MQTT connection. 116 - 117 -**URL**: This is the host name. Click on the copy button to copy it. 118 - 119 -**Port**: 8883 120 - 121 - 122 -Click on the **Getting Started** tab to setup the username and the password as the connection credentials. 123 - 124 - 125 -[[image:hivemq-8.png]] 126 - 127 - 128 -In the '**Create Connection Credentials**' section, provide a **username** and **password**, then click the **Add** button. 129 - 130 - 131 -[[image:hivemq-9.png]] 132 - 133 - 134 - 135 -If everything is successful, you will see the following message. 136 - 137 - 138 -[[image:hivemq-10.png||height="206" width="500"]] 139 - 140 - 141 -You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section. 142 - 143 - 144 144 = 3. Data Converters = 145 145 146 146 ... ... @@ -152,112 +152,188 @@ 152 152 153 153 In the left navigation, click **Integrations center**, and then click **Data converters**. 154 154 100 +[[image:data-converter-list-page.png]] 155 155 156 156 157 - [[image:data-converters-list-empty.png]]103 +On the **Data converters** page, click on the ‘+’ button, and then click on the **Create new converter** from the dropdown menu. 158 158 105 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]] 159 159 160 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu. 161 161 162 - 163 - 164 -[[image:create-new-converter-menu.png||height="259" width="500"]] 165 - 166 - 167 167 The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**. 168 168 169 -Click on the ** TBEL** button if not selectedit by default. Delete the existing decoder function in the code editor. Now copy and paste the followingdecoderfunctionwrittenin**TBEL (ThingsBoardExpressionLanguage)** inthe**codeeditor**. This decoder function iscompatiblefor both NB and CB series devices.110 +Click on the **JavaScript** button. Now copy and paste the following JavaScript to the **Decoder function** section. This decoder function is valid for both NB and CB series devices. 170 170 171 171 {{code language="JavaScript"}} 172 -/** Decoder **/ 173 - 113 +//Version: 0.1 174 174 // decode payload to string 175 175 var payloadStr = decodeToString(payload); 176 -var data = JSON.parse(payloadStr); 177 177 178 -var deviceName = metadata.topic.split("/")[3]; 179 179 // decode payload to JSON 180 -var deviceType = 'sensor'; 118 +var objdata = {}; 119 +var obj1 = {}; 120 +var data = decodeToJson(payload); 121 +var deviceName = data.IMEI; 122 +delete data.IMEI; 123 +var modelname = "Dragino " + data.Model; 124 +//var mod = data.mod 125 +delete data.Model; 126 +//delete data.mod 127 +var timestamp = new Date().getTime(); 181 181 182 -// Result object with device attributes/telemetry data 129 +for (var key in data) { 130 + 131 + if (Number(key)) { 132 + obj1[key] = data[key]; 133 + obj1[key][obj1[key].length - 1] = Number(new Date( 134 + obj1[key][obj1[key].length - 1])); 135 + 136 + } 137 +//Alec submitted25/02/25 138 +//turn old key into new 139 + else if (key === "Reading") { 140 + objdata["reading"] = data[key]; 141 + } else if (key === "work mode") { 142 + objdata["work_mode"] = data[key]; 143 + } else if (key === "hum") { 144 + objdata["humidity"] = data[key]; 145 + }else if (key === "hum2") { 146 + objdata["humidity2"] = data[key]; 147 + } else if (key === "hum3") { 148 + objdata["humidity3"] = data[key]; 149 + } else if (key === "tem") { 150 + objdata["temperature"] = data[key]; 151 + } else if (key === "tem2") { 152 + objdata["temperature2"] = data[key]; 153 + } else if (key === "tem3") { 154 + objdata["temperature3"] = data[key]; 155 + } else if (key === "DS18B20_Temp") { 156 + objdata["temperature_pro"] = data[key]; 157 + } else if (key === "ds18b20_temperature") { 158 + objdata["temperature_pro"] = data[key]; 159 + } else if (key === "DS18B20_temperature_pro") { 160 + objdata["temperature_pro"] = data[key]; 161 + } else if (key === "tdc send flag") { 162 + objdata["tdc_send_flag"] = data[key]; 163 + } else if (key === "trigger mode") { 164 + objdata["trigger_mode"] = data[key]; 165 + } else if (key === "soil dielectric constant") { 166 + objdata["soil_dielectric_constant"] = data[key]; 167 + } else if (key === "door open num") { 168 + objdata["door_open_num"] = data[key]; 169 + } else if (key === "door duration") { 170 + objdata["door_duration"] = data[key]; 171 + } else if (key === "count time") { 172 + objdata["count_time"] = data[key]; 173 + } else if (key === "last open time2") { 174 + objdata["last_open_time2"] = data[key]; 175 + } else if (key === "last open time3") { 176 + objdata["last_open_time3"] = data[key]; 177 + } 178 +//Alec submitted25/02/25 179 + else { 180 + objdata[key] = data[key] 181 + } 182 +} 183 +var listdata = [{ 184 + "ts": timestamp, 185 + "values": objdata 186 +}] 187 +for (var key1 in obj1) { 188 + if (modelname == "Dragino RS485-NB") { 189 + listdata.push({ 190 + "ts": obj1[key1][obj1[key1].length - 1], 191 + "values": { 192 + "Payload": obj1[key1][0], 193 + } 194 + }) 195 + } else { 196 + listdata.push({ 197 + "ts": obj1[key1][obj1[key1].length - 1], 198 + "values": { 199 + "values": obj1[key1] 200 + }, 201 + }) 202 + } 203 +} 183 183 var result = { 205 + 184 184 deviceName: deviceName, 185 - deviceType: de viceType,207 + deviceType: modelname, 186 186 attributes: { 187 - integrationName: metadata['integrationName'], 209 + model: modelname, 210 + //customerName: "NB-CB", 211 + //groupName: "NB-CB", 212 + //integrationName: metadata['integrationName'] 213 + 188 188 }, 189 - telemetry: { 190 - temperature: data.temperature, 191 - humidity: data.humidity, 192 - } 193 -}; 215 + telemetry: listdata 216 +} 194 194 195 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/ 218 +function decodeToString(payload) { 219 + return String.fromCharCode.apply(String, payload); 220 +} 196 196 222 +function decodeToJson(payload) { 223 + // covert payload to string. 224 + var str = decodeToString(payload); 225 + 226 + // parse string to JSON 227 + var data = JSON.parse(str); 228 + return data; 229 +} 230 + 197 197 return result; 232 + 198 198 {{/code}} 199 199 200 200 201 201 Click on the **Add** button. 202 202 238 +[[image:uplink-data-converter.png||height="529" width="500"]] 203 203 204 204 205 - [[image:add-uplink-data-converter.png||height="529"width="500"]]241 +You should see that the newly added **uplink data converter** is listed on the **Data Converters** page. 206 206 207 - 208 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page. 209 - 210 210 [[image:data-converter-list-showing-uplink-dc.png]] 211 211 212 212 213 - 214 214 == 3.2 Downlink == 215 215 216 216 217 217 On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu. 218 218 251 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]] 219 219 220 -[[image:create-new-converter-menu.png||width="500"]] 221 221 222 - 223 - 224 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** buttonif not selected it by default. Now copy and paste the followingencoderfunctionwrittenin**TBEL (ThingsBoardExpressionLanguage)** inthe**codeeditor**.compatiblefor both NB and CB series devices.256 +Click on the **JavaScript** button. Now copy and paste the following JavaScript to the **Encoder function **section. This encoder function is valid for both NB and CB series devices. 227 227 228 228 229 229 {{code language="JavaScript"}} 230 -// Encode downlink data from incoming Rule Engine message 260 +function hexToBase64(hexString) { 261 + // 将16进制字符串两个字符转换为一个字节 262 + var bytes = hexString.match(/.{2}/g); 263 + // 对每个字节进行解析,并转换为对应的字符 264 + var binaryString = bytes.map(function(byte) { 265 + return String.fromCharCode(parseInt(byte, 16)); 266 + }).join(''); 267 + 268 + // 使用btoa进行base64编码 269 + return btoa(binaryString); 270 +} 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 236 - 237 -/** Encoder **/ 238 - 239 -var data = {}; 240 - 241 -// Process data from incoming message and metadata 242 - 243 -data.tempFreq = msg.temperatureUploadFrequency; 244 -data.humFreq = msg.humidityUploadFrequency; 245 - 246 -data.devSerialNumber = metadata['ss_serialNumber']; 247 - 248 248 // Result object with encoded downlink payload 249 249 var result = { 250 - 251 251 // downlink data content type: JSON, TEXT or BINARY (base64 format) 252 - contentType: " JSON",275 + contentType: "BINARY", 253 253 254 254 // downlink data 255 - data: JSON.stringify(data),278 + data:hexToBase64(metadata.shared_value) 256 256 257 257 // Optional metadata object presented in key/value format 258 - metadata: { 259 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload' 260 - } 281 + //metadata: {} 261 261 262 262 }; 263 263 ... ... @@ -267,30 +267,24 @@ 267 267 268 268 Click on the **Add** button. 269 269 291 +[[image:downlink-data-converter.png||height="530" width="500"]] 270 270 271 271 272 - [[image:add-downlink-data-converter.png||height="529"width="500"]]294 +You should see that the newly added **downlink data converter** is listed on the **Data Converters** page. 273 273 296 +[[image:data-converter-list.png]] 274 274 275 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page. 276 276 277 - 278 -[[image:data-converters-list.png]] 279 - 280 - 281 - 282 282 = 4. Add Integration = 283 283 284 284 285 285 In the left navigation, click **Integrations center**, and then click **Integrations**. 286 286 287 - 288 -[[image:integrations-list-empty.png]] 289 - 290 - 291 291 On the **Integrations** page, click on the '**+**' button. 292 292 306 +[[image:data-converter-list-page.png]] 293 293 308 + 294 294 The **Add integration** window appears. 295 295 296 296 In the **Add integration** window, configure the following settings: ... ... @@ -300,13 +300,9 @@ 300 300 301 301 * **Integration type**: MQTT 302 302 * **Name**: MQTT integration NB/CB 303 -* **Enable integration**: YES 304 -* **Allows create devices or assets**: YES 305 305 306 306 Click **Next** button. 307 307 308 - 309 - 310 310 [[image:add-integration-basic-settings.png||height="511" width="500"]] 311 311 312 312 ... ... @@ -317,11 +317,9 @@ 317 317 318 318 Click **Next** button. 319 319 331 +[[image:add-integration-uplink-data-converter.png||width="500"]] 320 320 321 321 322 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]] 323 - 324 - 325 325 **Downlink data converter:** 326 326 327 327 * Click on the **Select existing** button. ... ... @@ -329,93 +329,47 @@ 329 329 330 330 Click **Next** button. 331 331 341 +[[image:add-integration-downlink-data-converter.png||height="510" width="500"]] 332 332 333 333 334 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]] 335 - 336 - 337 337 **Connection:** 338 338 339 -* **Host**: ClusterURL(Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)340 -* **Port**: 88 83346 +* **Host**: mqtt.eu.thingsboard.cloud (This is the host name you copied from the device - See section xxxxx for more information) 347 +* **Port**: 1883 (This is the port number you copied from the device - See section xxxxx for more information) 341 341 * **Credentials**: Basic 342 -* **Enable SSL**: YES 343 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials) 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) 346 -* **QoS:** 0-At most once 349 +* **Username**: Access token (This is the access token you copied from the device) 350 +* **Password** - Leave it as blank 351 +* **Topic** - v1/devices/+/telemetry (sightly modify the topic 'v1/devices/me/telemetry' you copied from the device to enable receiving data from any 'device name') 352 +* **QoS** - 0-At most once 347 347 348 -[[image:add-integration-connection.png||height="511" width="500"]] 349 - 350 - 351 -Click on the **Advanced settings** button. 352 - 353 -* **Clean session:** NO 354 -* **Retained**: NO 355 - 356 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]] 357 - 358 - 359 359 Click on the **Check connection** button to verify the MQTT connection using the provided parameters. 360 360 356 +[[image:add-integration-connection.png||width="500"]] 361 361 362 -[[image:check-connection.png||height="83" width="300"]] 363 363 359 +If the connection is successful, you will see the **Connected** message. 364 364 365 - If the connection is successful,youwill seethe **Connected**message. If not, check your connectionparameters again.361 +Click on the **Add** button. 366 366 363 +[[image:add-connection-success.png||height="511" width="500"]] 367 367 368 -[[image:connection-success.png||height="511" width="500"]] 369 369 370 - 371 -Click on the **Add** button. 372 - 373 373 You should see that the newly added integration is listed on the **Integrations** page. 374 374 375 375 Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.** 376 376 370 +[[image:integrations-list-added-pending.png]] 377 377 378 378 379 - [[image:new-integration-pending.png]]373 += 5. Verifying the receipt of data from the device = 380 380 381 381 382 - =5.Verifyingthereceiptofdata fromvirtual devices=376 +On the terminal, issue the following MQTT command which simulates the device S31B-NB. 383 383 384 - 385 -== 5.1 How does it work? == 386 - 387 -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. 388 - 389 -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. 390 - 391 -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. 392 - 393 - 394 -**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.** 395 - 396 - 397 -For example, if you send two MQTT messages with different device names in the topic: 398 - 399 -1. v1/devices/**S31B-NB**/telemetry 400 -1. v1/devices/**S31B-CB**/telemetry 401 - 402 -ThingsBoard will create two devices named **S31B-NB** and **S31B-CB** in the **//Devices//** section. 403 - 404 - 405 -The MQTT payload format is as follows, for example: 406 - 407 407 {{code language="none"}} 408 - {"temperature":10.4,"humidity":85}379 +mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}" 409 409 {{/code}} 410 410 411 - 412 -== 5.2 Sending messages == 413 - 414 - 415 -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. 416 - 417 -{{code language="none"}} 418 -mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/SN-001/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":10.4, "humidity":85}' 419 -{{/code}} 420 - 421 421 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. 383 + 384 +
- add-downlink-data-converter.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -175.2 KB - Content
- add-integration-connection-advanced-settings.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -155.2 KB - Content
- add-uplink-data-converter.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -174.1 KB - Content
- check-connection.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -14.7 KB - Content
- connection-success.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -90.0 KB - Content
- create-new-converter-menu.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.5 KB - Content
- data-converters-list-empty.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -260.7 KB - Content
- data-converters-list.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -212.2 KB - Content
- hivemq-10.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -82.7 KB - Content
- hivemq-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -300.7 KB - Content
- hivemq-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -535.2 KB - Content
- hivemq-4.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -309.8 KB - Content
- hivemq-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -115.0 KB - Content
- hivemq-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -321.0 KB - Content
- hivemq-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -203.5 KB - Content
- hivemq-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -268.7 KB - Content
- hivemq-9.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -303.7 KB - Content
- hivwmq-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -380.3 KB - Content
- integration-active.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.2 KB - Content
- integrations-list-empty.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -264.5 KB - Content
- new-integration-pending.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -199.7 KB - Content
- thingsboard-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -1.9 MB - Content
- thingsboard-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -901.1 KB - Content
- thingsboard-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -146.3 KB - Content
- thingsboard-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -122.1 KB - Content
- thingsboard-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -106.7 KB - Content
- thingsboard-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -119.3 KB - Content
- ThingsBoard-add-data-converter.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +128.6 KB - Content
- ThingsBoard-add-new-device.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +89.7 KB - Content
- ThingsBoard-new-data-converter.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +100.3 KB - Content
- add-connection-success.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +202.8 KB - Content
- data-converter-list-page.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +190.8 KB - Content
- data-converter-list.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +202.8 KB - Content
- device-list-empty.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +202.8 KB - Content
- downlink-data-converter.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +207.8 KB - Content
- integrations-list-added-pending.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +202.8 KB - Content
- mqtt-command-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +202.8 KB - Content
- mqtt-command-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +202.8 KB - Content
- new-device-access-token.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +202.8 KB - Content
- new-device-check-connectivity.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +202.8 KB - Content
- new-device-device-details.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +88.4 KB - Content
- new-device-telemetry-test.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +202.8 KB - Content
- uplink-data-converter.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +128.6 KB - Content
- virtual-device-active.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +202.8 KB - Content