Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 53.27 >
edited by Xiaoling
on 2023/08/02 14:54
To version < 60.1 >
edited by Edwin Chen
on 2023/08/07 23:28
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -10,21 +10,30 @@
10 10  This configure instruction is for Dragino NB-IoT models with -NB or -NS suffix, for example DDS75-NB. These models use the same NB-IoT Module **[[BC660K-GL>>https://www.quectel.com/product/lpwa-bc660k-gl-nb2]]** and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers.
11 11  
12 12  
13 -= 2. Network Connection =
13 += 2. Attach Network =
14 14  
15 15  
16 -The -NB and -NS models support (% style="color:blue" %)**LTE Cat NB2**(%%), with below frequency band: multiple frequency bands of (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85**(%%) . Make sure you use a the NB-IoT SIM card.
16 +To attache NB-IoT sensors to NB-IoT Network, You need to:
17 17  
18 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
19 -|(% style="background-color:#4f81bd; color:white" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white" %)**APN**|(% style="background-color:#4f81bd; color:white" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white" %)**Comments**
20 -|1NCE| | |
21 -|China Mobile| | |
18 +1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
19 +1. Insert the SIM card to Sensor
20 +1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (% class="mark" %)(补充 APN 指令(%%))
22 22  
22 +(% class="mark" %)插入 SIM 卡图片
23 23  
24 +After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
24 24  
25 -== 2.1 1NCE SIM Card. ==
26 +The -NB and -NS models support (% style="color:blue" %)**LTE Cat NB2**(%%), with below frequency band: multiple frequency bands of (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85**(%%) . Make sure you use a the NB-IoT SIM card.
26 26  
28 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
29 +|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**APN**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
30 +|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
31 +**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
27 27  
33 +Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
34 +)))|(% style="width:135px" %)
35 +|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
36 +|(% style="width:117px" %)China Telecom|(% style="width:151px" %) |(% style="width:474px" %)China Mainland|(% style="width:135px" %)
28 28  
29 29  = 3. Configure to connect to different servers =
30 30  
... ... @@ -125,12 +125,14 @@
125 125  
126 126  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
127 127  
128 -=== 3.3.2.2 Publish Data to ThingSpeak Channel ===
137 +==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
129 129  
139 +
130 130  [[image:image-20230802112413-9.png]]
131 131  
132 132  [[image:image-20230802112413-10.png]]
133 133  
144 +
134 134  (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
135 135  
136 136  * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
... ... @@ -145,9 +145,9 @@
145 145  [[image:image-20230802112413-11.png]]
146 146  
147 147  
148 -== 3.3 Configure NB-IoT Sensor for connection ==
159 +=== 3.3.3 Configure NB-IoT Sensor for connection ===
149 149  
150 -=== 3.3.1 AT Commands: ===
161 +==== 3.3.3.1 AT Commands: ====
151 151  
152 152  
153 153  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
... ... @@ -164,10 +164,9 @@
164 164  
165 165  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
166 166  
178 +==== 3.3.3.2 Uplink Examples ====
167 167  
168 -=== 3.3.2 Uplink Examples ===
169 169  
170 -
171 171  For S31-NB
172 172  
173 173  For SE01-NB
... ... @@ -193,7 +193,7 @@
193 193  For SN50V3-NB
194 194  
195 195  
196 -=== 3.3.3 Map fields to sensor value ===
206 +==== 3.3.3.3 Map fields to sensor value ====
197 197  
198 198  
199 199  When NB-IoT sensor upload to ThingSpeak. The payload already specify which fileds related to which sensor value. Use need to create fileds in Channels Settings. with name so to see the value correctly.
... ... @@ -219,142 +219,26 @@
219 219  |(% style="background-color:#4f81bd; color:white; width:124px" %)NMDS200-NB|(% style="width:91px" %)distance1|(% style="width:102px" %)distance2|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
220 220  |(% style="background-color:#4f81bd; color:white; width:124px" %)CPN01-NB|(% style="width:91px" %)alarm|(% style="width:102px" %)count|(% style="width:159px" %)door open duration|(% style="width:153px" %)calc flag|(% style="width:152px" %)Battery|(% style="width:148px" %)RSSI|(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
221 221  |(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:91px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:159px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:153px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:152px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:148px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:164px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:66px" %)Battery|(% colspan="1" rowspan="1" style="width:66px" %)RSSI
222 -|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB|(% colspan="1" rowspan="1" style="width:91px" %) |(% colspan="1" rowspan="1" style="width:102px" %) |(% colspan="1" rowspan="1" style="width:159px" %) |(% colspan="1" rowspan="1" style="width:153px" %) |(% colspan="1" rowspan="1" style="width:152px" %) |(% colspan="1" rowspan="1" style="width:148px" %) |(% colspan="1" rowspan="1" style="width:164px" %) |(% colspan="1" rowspan="1" style="width:152px" %) |(% colspan="1" rowspan="1" style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %)
223 -|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod1|(% colspan="1" rowspan="1" style="width:91px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:159px" %)RSSI|(% colspan="1" rowspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:148px" %)adc0|(% colspan="1" rowspan="1" style="width:164px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %)
224 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod2|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc0|(% colspan="1" style="width:164px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
225 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod3|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc1|(% colspan="1" style="width:164px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:66px" %)adc4|(% colspan="1" style="width:66px" %)
226 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod4|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)adc0|(% colspan="1" style="width:148px" %)exit_state/input PA4|(% colspan="1" style="width:164px" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
227 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod5|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)adc0|(% colspan="1" style="width:148px" %)exit_state/input PA4|(% colspan="1" style="width:164px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
228 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod6|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)count|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:148px" %) |(% colspan="1" style="width:164px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
232 +|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:91px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:159px" %)RSSI|(% colspan="1" rowspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:148px" %)adc0|(% colspan="1" rowspan="1" style="width:164px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %)
233 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod2|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc0|(% colspan="1" style="width:164px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
234 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod3|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc1|(% colspan="1" style="width:164px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:66px" %)adc4|(% colspan="1" style="width:66px" %)
235 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod4|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)adc0|(% colspan="1" style="width:148px" %)exit_state/input PA4|(% colspan="1" style="width:164px" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
236 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod5|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)adc0|(% colspan="1" style="width:148px" %)exit_state/input PA4|(% colspan="1" style="width:164px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
237 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod6|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)count|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:148px" %) |(% colspan="1" style="width:164px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
229 229  
230 230  == 3.4 Datacake ==
231 231  
232 -== 3.4.1 Define Product ==
233 233  
234 234  
235 -Firstly, we need to set the MQTT mode to datacake, and we need to run(% style="color:blue" %)** AT+PRO=3,2**(%%). This command is set to datacake. After running the command, the device automatically sets the server address, port.
236 236  
237 -By chosing to add the device under a (% style="color:blue" %)**"New Product"**(%%) you are required to give a name for this product. You can name it something like (% style="color:blue" %)**"My First MQTT Product"**.
238 -
239 -[[image:image-20230802112413-14.png]]
240 -
241 -
242 -=== 3.4.2 Create Device ===
243 -
244 -
245 -In the second step you have to define the device which should be added to the product.
246 -
247 -[[image:image-20230802112413-15.png]]
248 -
249 -Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the (% style="color:blue" %)**"Next"**(%%) button.
250 -
251 -
252 -=== 3.4.3 Create Database Fields ===
253 -
254 -
255 -After creating the device, it is listed in the table of the fleet view. Now open the device by clicking on the entry in the list.
256 -
257 -You will then see a device view with an empty dashboard. Now, the first thing we want to do is navigate to the Device configuration. To do this, use the tab bar and click on (% style="color:blue" %)**"Configuration"**.
258 -
259 -[[image:image-20230802112413-16.png]]
260 -
261 -[[image:image-20230802112413-17.png]]
262 -
263 -To create a first database field, please click on the (% style="color:blue" %)**"Add Field"**(%%) button as marked in the screenshot above.
264 -
265 -This will open another modal asking for some required input for your first field.
266 -
267 -[[image:image-20230802112413-18.png]]
268 -
269 -[[image:image-20230802112413-19.png]]
270 -
271 -
272 -=== 3.4.4 Set up Broker ===
273 -
274 -
275 -The broker is running on mqtt.datacake.co on ports (% style="color:blue" %)**1883 and 8883**(%%). Port 1883 is unsecured and should not be used in production environments. Port 8883 uses a CA signed server certificate.
276 -
277 -You will need an access token to log into the Datacake MQTT Broker. You can use your own personal token or create a token explicitly for individual devices or groups of devices.
278 -
279 -View your Personal Access Token
280 -
281 -You can view your own token via the User-Settings-Menu. You can reach this menu by clicking on (% style="color:blue" %)**"Edit Profile"**(%%) at the end of the list using the Workspace Selector:
282 -
283 -[[image:image-20230802112413-20.png]]
284 -
285 -(% style="color:blue" %)**MQTT Client-ID**
286 -
287 -The Datacake Broker manages the client IDs internally. You do not need to worry about a client ID. If your client optionally supports the specification of a client ID, please leave this specification blank. Your client then creates a randomly generated ID.
288 -
289 -(% style="color:blue" %)**AT+CLIENT=“Any value”**
290 -
291 -(% style="color:blue" %)**AT+UNAME=Token**
292 -
293 -(% style="color:blue" %)**AT+PWD=Token**
294 -
295 -[[image:image-20230802112413-21.png]]
296 -
297 -
298 -=== 3.4.5 Create your first Subscription ===
299 -
300 -
301 -(% style="color:blue" %)**Subscribe**
302 -
303 -Data is published according to the following structure:
304 -
305 -dtck~/~//
306 -
307 -Subscribe to topics using this structure to receive messages via MQTT when readings (via API or MQTT) arrive in the Datacake Cloud. Messages are published whenever there is a change to a corresponding database field.
308 -
309 -
310 -[[image:image-20230802112413-22.png]]
311 -
312 -
313 -[[image:image-20230802112413-23.png]]
314 -
315 -
316 -[[image:image-20230802112413-24.png]]
317 -
318 -
319 -(% style="color:blue" %)**example:**
320 -
321 -AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
322 -
323 -[[image:image-20230802112413-25.png]]
324 -
325 -
326 -=== 3.4.6 Define Publish Topic ===
327 -
328 -
329 -(% style="color:blue" %)**Publish**
330 -
331 -To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure.
332 -
333 -Due to the nature of MQTT, the topic prefix differs as follows:
334 -
335 -dtck-pub~/~//
336 -
337 -(% style="color:blue" %)**example:**
338 -
339 -AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
340 -
341 -
342 -=== 3.4.7 upload data ===
343 -
344 -
345 -[[image:image-20230802112413-26.png]]
346 -
347 -[[image:image-20230802112413-27.png]]
348 -
349 -[[image:image-20230802112413-28.png]]
350 -
351 -
352 352  == 3.5 Node-Red (via MQTT) ==
353 353  
354 -=== 3.5.1 Configure Node-Red ===
246 +=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
355 355  
248 +
356 356  [[image:image-20230802112413-29.png]]
357 357  
251 +
358 358  [[image:image-20230802112413-30.png]]
359 359  
360 360  
... ... @@ -367,7 +367,7 @@
367 367  === 3.5.3 Configure NB-IoT Sensors ===
368 368  
369 369  
370 -* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%)    ~/~/Set to mqtt Server and  Payload
264 +* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%)    ~/~/  Set to mqtt Server and  Payload
371 371  
372 372  * (% style="color:blue" %)**AT+CLIENT=any value**
373 373  
... ... @@ -385,20 +385,22 @@
385 385  
386 386  ==== 3.6.1.1 Create Device ====
387 387  
388 -Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].
389 389  
283 +Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
284 +
390 390  [[image:image-20230802112413-32.png]]
391 391  
392 392  
393 393  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
394 394  
290 +
395 395  (% style="color:blue" %)**Uplink Converter**
396 396  
397 397  The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
398 398  
399 -To create an uplink converter go to the Integrations center -> Data converters page and click “plus” button. Name it “MQTT Uplink Converter” and select type Uplink. Use debug mode for now.
295 +To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
400 400  
401 -[[image:image-20230802112413-33.png]]
297 +[[image:image-20230802112413-33.png||height="732" width="1302"]]
402 402  
403 403  
404 404  (% style="color:blue" %)**Downlink Converter**
... ... @@ -405,7 +405,7 @@
405 405  
406 406  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
407 407  
408 -[[image:image-20230802112413-34.png]]
304 +[[image:image-20230802112413-34.png||height="734" width="1305"]]
409 409  
410 410  (% style="color:red" %)**Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
411 411  
... ... @@ -413,28 +413,30 @@
413 413  ==== 3.6.1.3 MQTT Integration Setup ====
414 414  
415 415  
416 -Go to the Integrations center -> Integrations page and click **“plus”** icon to add a new integration. Name it “MQTT Integration”, select type MQTT;
312 +Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**;
417 417  
418 -[[image:image-20230802112413-35.png]]
314 +[[image:image-20230802112413-35.png||height="738" width="1312"]]
419 419  
316 +
420 420  * The next steps is to add the recently created uplink and downlink converters;
421 421  
422 -[[image:image-20230802112413-36.png]]
319 +[[image:image-20230802112413-36.png||height="736" width="1308"]]
423 423  
424 -[[image:image-20230802112413-37.png]]
321 +[[image:image-20230802112413-37.png||height="735" width="1307"]]
425 425  
323 +
426 426  (% style="color:blue" %)**Add a topic filter:**
427 427  
326 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
428 428  
429 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。
430 -
431 431  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
432 432  
433 -[[image:image-20230802112413-38.png]]
330 +[[image:image-20230802112413-38.png||height="731" width="1300"]]
434 434  
435 435  
436 436  === 3.6.2 Simulate with MQTT.fx ===
437 437  
335 +
438 438  [[image:image-20230802112413-39.png]]
439 439  
440 440  [[image:image-20230802112413-40.png]]
... ... @@ -445,21 +445,15 @@
445 445  
446 446  (% style="color:blue" %)**AT Commands**
447 447  
448 -* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard.
346 +* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
449 449  
450 -* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的
348 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>** (%%)
349 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
350 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
351 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
352 +* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
451 451  
452 -* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的
453 453  
454 -Users do not need to fill in the client, username, and password. But the configuration information of the device requires setting the client, username, and password, which can be entered freely. (软件自动填充为 Device Name 吧).这边不用提示了，客户不需要输入。（大部分客户还是会自己去设置这个的，提高安全性）
455 -
456 -(% style="color:blue" %)**CLIENT :“Any value”**
457 -
458 -(% style="color:blue" %)**User Name:“Any value”**
459 -
460 -(% style="color:blue" %)**Password:“Any value”**
461 -
462 -
463 463  Test Uplink by click the button for 1 second
464 464  
465 465  [[image:image-20230802112413-41.png]]
... ... @@ -486,7 +486,7 @@
486 486  [[image:image-20230802112413-46.png]]
487 487  
488 488  
489 -On the Connection Profile window, set the following information: (这边加一个截图)
381 +On the Connection Profile window, set the following information: **(这边加一个截图)**
490 490  
491 491  * (% style="color:blue" %)**Profile Name: “Any name”**
492 492  
... ... @@ -496,15 +496,15 @@
496 496  
497 497  * (% style="color:blue" %)**Client ID: “Any value”**
498 498  
499 -On the section User credentials, set the following information:(这边加一个截图)
391 +On the section User credentials, set the following information: **(这边加一个截图)**
500 500  
501 -* **User Name: “Any value”**  Tago validates your user by the token only
393 +* (% style="color:blue" %)**User Name: “Any value”**  (%%) ~/~/  Tago validates your user by the token only
502 502  
503 -* **Password: “Your device token”**
395 +* (% style="color:blue" %)**Password: “Your device token”**
504 504  
505 -* **PUBTOPIC: “Any value”**
397 +* (% style="color:blue" %)**PUBTOPIC: “Any value”**
506 506  
507 -* **SUBTOPIC: “Any value”**
399 +* (% style="color:blue" %)**SUBTOPIC: “Any value”**
508 508  
509 509  === 3.7.2 Simulate with MQTT.fx ===
510 510  
... ... @@ -513,8 +513,9 @@
513 513  
514 514  [[image:image-20230802112413-48.png]]
515 515  
516 -Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format.
408 +Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
517 517  
410 +
518 518  [[image:image-20230802112413-49.png]]
519 519  
520 520  
... ... @@ -523,7 +523,7 @@
523 523  
524 524  [[image:image-20230802112413-50.png]]
525 525  
526 -[[image:image-20230802112413-51.png]]
419 +[[image:image-20230802112413-51.png||height="184" width="696"]]
527 527  
528 528  
529 529  === 3.7.4 TLS mode ===
... ... @@ -543,7 +543,7 @@
543 543  
544 544  * (% style="color:blue" %)**Client ID: “Any value”**
545 545  
546 -* (% style="color:blue" %)**User Name: “Any value”** (%%) Tago validates your user by the token only
439 +* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only
547 547  
548 548  * (% style="color:blue" %)**Password: “Your device token”**
549 549  

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0