Changes for page ThingsBoard
Last modified by Dilisi S on 2025/04/02 02:09
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -17,75 +17,230 @@ 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. Add New Device = 20 20 21 21 23 +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. 22 22 23 - =2.DataConverters=25 +In the left navigation, click **Entities** and then click **Devices**. 24 24 27 +[[image:device-list-empty.png]] 25 25 26 -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. 27 27 30 +On the **Devices **page, click on the ‘**+**’ button, and then click on the **Add new device **from the dropdown menu. 28 28 29 - == 2.1 Uplink==32 +[[image:ThingsBoard-add-new-device.png||height="279" width="500"]] 30 30 31 31 32 - In theleftnavigation,click**Integrationscenter**,andthenclick**Dataconverters**.35 +The **Add new device** window appears. Name the device, for example '**Virtual NB/CB device**'. 33 33 37 +Click on the **Next: Credentials** button. 34 34 39 +[[image:new-device-device-details.png||height="529" width="500"]] 35 35 36 -[[image:data-converters-list-empty.png]] 37 37 42 +Click the **Access token** button if it is not selected by default. 38 38 39 - OntheDataconverters**page,click onthe‘**+**’ button, and thenclick on the**Create newconverter** fromthe dropdownmenu.44 +Copy the **Access token** to a text editor, as you will need it in the section **'Sending data from an MQTT client'**. 40 40 46 +Click on the **Add** button. 41 41 48 +[[image:new-device-access-token.png||height="528" width="500"]] 42 42 43 -[[image:create-new-converter-menu.png||height="259" width="500"]] 44 44 51 +Click on the **MQTT** button. 45 45 53 +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. 54 + 55 +Copy the MQTT pub command in the '**Execute the following command**' section. 56 + 57 +{{code language="none"}} 58 +mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/me/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:25}" 59 +{{/code}} 60 + 61 +Note that the **State** is still shown as **'Inactive'** in the **Latest telemetry** section. 62 + 63 +[[image:new-device-check-connectivity.png||height="522" width="500"]] 64 + 65 + 66 +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. 67 + 68 + 69 +[[image:mqtt-command-1.png||height="228" width="700"]] 70 + 71 + 72 +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 + 74 + 75 +[[image:new-device-telemetry-test.png||height="520" width="500"]] 76 + 77 + 78 +Send the same command again, only changing the **temperature** value, to see how the **Latest telemetry** section updates its data. 79 + 80 +Once you are done experimenting with this, close the window by clicking the **Close** button. 81 + 82 + 83 +[[image:mqtt-command-2.png||height="227" width="700"]] 84 + 85 + 86 + 87 +[[image:virtual-device-active.png]] 88 + 89 + 90 += 3. Data Converters = 91 + 92 + 93 +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. 94 + 95 + 96 +== 3.1 Uplink == 97 + 98 + 99 +In the left navigation, click **Integrations center**, and then click **Data converters**. 100 + 101 +[[image:data-converter-list-page.png]] 102 + 103 + 104 +On the **Data converters** page, click on the ‘+’ button, and then click on the **Create new converter** from the dropdown menu. 105 + 106 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]] 107 + 108 + 46 46 The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**. 47 47 48 -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.111 +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. 49 49 50 50 {{code language="JavaScript"}} 51 -/** Decoder **/ 52 - 114 +//Version: 0.1 53 53 // decode payload to string 54 54 var payloadStr = decodeToString(payload); 55 -var data = JSON.parse(payloadStr); 56 56 57 -var deviceName = metadata.topic.split("/")[3]; 58 58 // decode payload to JSON 59 -var deviceType = 'sensor'; 119 +var objdata = {}; 120 +var obj1 = {}; 121 +var data = decodeToJson(payload); 122 +var deviceName = data.IMEI; 123 +delete data.IMEI; 124 +var modelname = "Dragino " + data.Model; 125 +//var mod = data.mod 126 +delete data.Model; 127 +//delete data.mod 128 +var timestamp = new Date().getTime(); 60 60 61 -// Result object with device attributes/telemetry data 130 +for (var key in data) { 131 + 132 + if (Number(key)) { 133 + obj1[key] = data[key]; 134 + obj1[key][obj1[key].length - 1] = Number(new Date( 135 + obj1[key][obj1[key].length - 1])); 136 + 137 + } 138 +//Alec submitted25/02/25 139 +//turn old key into new 140 + else if (key === "Reading") { 141 + objdata["reading"] = data[key]; 142 + } else if (key === "work mode") { 143 + objdata["work_mode"] = data[key]; 144 + } else if (key === "hum") { 145 + objdata["humidity"] = data[key]; 146 + }else if (key === "hum2") { 147 + objdata["humidity2"] = data[key]; 148 + } else if (key === "hum3") { 149 + objdata["humidity3"] = data[key]; 150 + } else if (key === "tem") { 151 + objdata["temperature"] = data[key]; 152 + } else if (key === "tem2") { 153 + objdata["temperature2"] = data[key]; 154 + } else if (key === "tem3") { 155 + objdata["temperature3"] = data[key]; 156 + } else if (key === "DS18B20_Temp") { 157 + objdata["temperature_pro"] = data[key]; 158 + } else if (key === "ds18b20_temperature") { 159 + objdata["temperature_pro"] = data[key]; 160 + } else if (key === "DS18B20_temperature_pro") { 161 + objdata["temperature_pro"] = data[key]; 162 + } else if (key === "tdc send flag") { 163 + objdata["tdc_send_flag"] = data[key]; 164 + } else if (key === "trigger mode") { 165 + objdata["trigger_mode"] = data[key]; 166 + } else if (key === "soil dielectric constant") { 167 + objdata["soil_dielectric_constant"] = data[key]; 168 + } else if (key === "door open num") { 169 + objdata["door_open_num"] = data[key]; 170 + } else if (key === "door duration") { 171 + objdata["door_duration"] = data[key]; 172 + } else if (key === "count time") { 173 + objdata["count_time"] = data[key]; 174 + } else if (key === "last open time2") { 175 + objdata["last_open_time2"] = data[key]; 176 + } else if (key === "last open time3") { 177 + objdata["last_open_time3"] = data[key]; 178 + } 179 +//Alec submitted25/02/25 180 + else { 181 + objdata[key] = data[key] 182 + } 183 +} 184 +var listdata = [{ 185 + "ts": timestamp, 186 + "values": objdata 187 +}] 188 +for (var key1 in obj1) { 189 + if (modelname == "Dragino RS485-NB") { 190 + listdata.push({ 191 + "ts": obj1[key1][obj1[key1].length - 1], 192 + "values": { 193 + "Payload": obj1[key1][0], 194 + } 195 + }) 196 + } else { 197 + listdata.push({ 198 + "ts": obj1[key1][obj1[key1].length - 1], 199 + "values": { 200 + "values": obj1[key1] 201 + }, 202 + }) 203 + } 204 +} 62 62 var result = { 206 + 63 63 deviceName: deviceName, 64 - deviceType: de viceType,208 + deviceType: modelname, 65 65 attributes: { 66 - integrationName: metadata['integrationName'], 210 + model: modelname, 211 + //customerName: "NB-CB", 212 + //groupName: "NB-CB", 213 + //integrationName: metadata['integrationName'] 214 + 67 67 }, 68 - telemetry: { 69 - temperature: data.temperature, 70 - humidity: data.humidity, 71 - } 72 -}; 216 + telemetry: listdata 217 +} 73 73 74 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/ 219 +function decodeToString(payload) { 220 + return String.fromCharCode.apply(String, payload); 221 +} 75 75 223 +function decodeToJson(payload) { 224 + // covert payload to string. 225 + var str = decodeToString(payload); 226 + 227 + // parse string to JSON 228 + var data = JSON.parse(str); 229 + return data; 230 +} 231 + 76 76 return result; 233 + 77 77 {{/code}} 78 78 79 79 80 80 Click on the **Add** button. 81 81 239 +[[image:uplink-data-converter.png||height="529" width="500"]] 82 82 83 83 84 - [[image:add-uplink-data-converter.png||height="529"width="500"]]242 +You should see that the newly added **uplink data converter** is listed on the **Data Converters** page. 85 85 86 - 87 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page. 88 - 89 89 [[image:data-converter-list-showing-uplink-dc.png]] 90 90 91 91 ... ... @@ -99,41 +99,32 @@ 99 99 100 100 The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**. 101 101 102 -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.257 +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. 103 103 104 104 105 105 {{code language="JavaScript"}} 106 -// Encode downlink data from incoming Rule Engine message 261 +function hexToBase64(hexString) { 262 + // 将16进制字符串两个字符转换为一个字节 263 + var bytes = hexString.match(/.{2}/g); 264 + // 对每个字节进行解析,并转换为对应的字符 265 + var binaryString = bytes.map(function(byte) { 266 + return String.fromCharCode(parseInt(byte, 16)); 267 + }).join(''); 268 + 269 + // 使用btoa进行base64编码 270 + return btoa(binaryString); 271 +} 107 107 108 -// msg - JSON message payload downlink message json 109 -// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc. 110 -// metadata - list of key-value pairs with additional data about the message 111 -// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter 112 - 113 -/** Encoder **/ 114 - 115 -var data = {}; 116 - 117 -// Process data from incoming message and metadata 118 - 119 -data.tempFreq = msg.temperatureUploadFrequency; 120 -data.humFreq = msg.humidityUploadFrequency; 121 - 122 -data.devSerialNumber = metadata['ss_serialNumber']; 123 - 124 124 // Result object with encoded downlink payload 125 125 var result = { 126 - 127 127 // downlink data content type: JSON, TEXT or BINARY (base64 format) 128 - contentType: " JSON",276 + contentType: "BINARY", 129 129 130 130 // downlink data 131 - data: JSON.stringify(data),279 + data:hexToBase64(metadata.shared_value) 132 132 133 133 // Optional metadata object presented in key/value format 134 - metadata: { 135 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload' 136 - } 282 + //metadata: {} 137 137 138 138 }; 139 139 ... ... @@ -143,20 +143,17 @@ 143 143 144 144 Click on the **Add** button. 145 145 292 +[[image:downlink-data-converter.png||height="530" width="500"]] 146 146 147 147 148 - [[image:add-downlink-data-converter.png||height="529"width="500"]]295 +You should see that the newly added **downlink data converter** is listed on the **Data Converters** page. 149 149 297 +[[image:data-converter-list.png]] 150 150 151 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page. 152 152 300 += 4. Add Integration = 153 153 154 154 155 -[[image:data-converters-list.png]] 156 - 157 -= 3. Add Integration = 158 - 159 - 160 160 In the left navigation, click **Integrations center**, and then click **Integrations**. 161 161 162 162 On the **Integrations** page, click on the '**+**' button. ... ... @@ -201,16 +201,13 @@ 201 201 202 202 **Connection:** 203 203 204 -* **Host**: ClusterURL(Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)205 -* **Port**: 88 83347 +* **Host**: mqtt.eu.thingsboard.cloud (This is the host name you copied from the device - See section xxxxx for more information) 348 +* **Port**: 1883 (This is the port number you copied from the device - See section xxxxx for more information) 206 206 * **Credentials**: Basic 207 -* **Enable SSL**: YES 208 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials) 209 -* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials) 210 -* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices) 211 -* **QoS:** 0-At most once 212 -* **Clean session:** NO 213 -* **Retained**: NO 350 +* **Username**: Access token (This is the access token you copied from the device) 351 +* **Password** - Leave it as blank 352 +* **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') 353 +* **QoS** - 0-At most once 214 214 215 215 Click on the **Check connection** button to verify the MQTT connection using the provided parameters. 216 216