General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

1

(% class="wikigeneratedid" %)

2

**Table of Contents:**

= 1. The use of this guideline =

8

9

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

12

13

= 2. Attach Network =

14

15

16

To attache NB-IoT sensors to NB-IoT Network, You need to:

17

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 指令(%%))

21

22

After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .

23

24

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.

25

26

(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)

27

|(% 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**

28

|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((

29

**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**

30

31

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

32

)))|(% style="width:135px" %)

33

|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)

34

|(% style="width:117px" %)China Telecom|(% style="width:151px" %) |(% style="width:474px" %)China Mainland|(% style="width:135px" %)

35

36

37

= 3. Configure to connect to different servers =

38

39

== 3.1 General UDP Connection ==

40

41

42

The NB-IoT Sensor can send packet to server use UDP protocol.

43

44

45

=== 3.1.1 Simulate UDP Connection by PC tool ===

46

47

48

We can use PC tool to simulate UDP connection to make sure server works ok.

49

50

[[image:image-20230802112413-1.png]]

51

52

53

=== 3.1.2 Configure NB-IoT Sensor ===

54

55

==== 3.1.2.1 AT Commands ====

56

57

58

(% style="color:blue" %)**AT Commands:**

59

60

* (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload

61

62

* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601** (%%) ~/~/ Set UDP server address and port

63

64

* (% style="color:#037691" %)**AT+CFM=1** (%%) ~/~/ If the server does not respond, this command is unnecessary

65

66

[[image:image-20230802112413-2.png]]

67

68

69

==== 3.1.2.2 Uplink Example ====

70

71

72

[[image:image-20230802112413-3.png]]

73

74

75

== 3.2 General MQTT Connection ==

76

77

78

The NB-IoT Sensor can send packet to server use MQTT protocol.

79

80

Below are the commands.

81

82

(% style="color:blue" %)**AT Commands:**

83

84

* (% style="color:#037691" %)**AT+PRO=3,0** (%%) ~/~/ Set to use MQTT protocol to uplink, Payload Type select Hex payload.

85

86

* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883** (%%) ~/~/ Set MQTT server address and port

87

88

* (% style="color:#037691" %)**AT+CLIENT=CLIENT** (%%) ~/~/ Set up the CLIENT of MQTT

89

90

* (% style="color:#037691" %)**AT+UNAME=UNAME** (%%) ~/~/ Set the username of MQTT

91

92

* (% style="color:#037691" %)**AT+PWD=PWD** (%%) ~/~/ Set the password of MQTT

93

94

* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB** (%%) ~/~/ Set the sending topic of MQTT

95

96

* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB** (%%) ~/~/ Set the subscription topic of MQTT

97

98

[[image:image-20230802112413-4.png]]

99

100

[[image:image-20230802112413-5.png]]

101

102

(% style="color:red" %)**Notice: MQTT protocol has a much higher power consumption compare with UDP/CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.**

103

104

105

== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==

106

107

=== 3.3.1 Get MQTT Credentials ===

108

109

110

[[ThingSpeak>>url:https://thingspeak.com/]] connection uses MQTT Connection. So we need to get MQTT Credentials first. You need to point MQTT Devices to ThingSpeak Channel as well.

111

112

[[image:image-20230802112413-6.png]]

113

114

[[image:image-20230802112413-7.png]]

115

116

117

=== 3.3.2 Simulate with MQTT.fx ===

118

119

==== 3.3.2.1 Establish MQTT Connection ====

120

121

122

After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.

123

124

[[image:image-20230802112413-8.png]]

125

126

* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com

127

128

* (% style="color:#037691" %)**Broker Port:**(%%) 1883

129

130

* (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>

131

132

* (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>

133

134

* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>

135

136

137

==== 3.3.2.2 Publish Data to ThingSpeak Channel ====

138

139

140

[[image:image-20230802112413-9.png]]

141

142

[[image:image-20230802112413-10.png]]

143

144

145

(% style="color:blue" %)**In MQTT.fx, we can publish below info:**

146

147

* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish

148

149

* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH

150

151

Where 63 and 67 are the value to be published to field1 & field2.

152

153

154

(% style="color:blue" %)**Result: **

155

156

[[image:image-20230802112413-11.png]]

157

158

159

=== 3.3.3 Configure NB-IoT Sensor for connection ===

160

161

==== 3.3.3.1 AT Commands: ====

162

163

164

In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx

165

166

* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload

167

168

* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**

169

170

* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**

171

172

* (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**

173

174

* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**

175

176

* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**

177

178

179

==== 3.3.3.2 Uplink Examples ====

For S31-NB

For SE01-NB

For DDS20-NB

For DDS45-NB

For DDS75-NB

For NMDS120-NB

For SPH01-NB

For NLM01-NB

For NMDS200-NB

For CPN01-NB

For DS03A-NB

For SN50V3-NB

==== 3.3.3.3 Map fields to sensor value ====

208

209

210

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.

211

212

213

[[image:image-20230802112413-12.png]]

214

215

[[image:image-20230802112413-13.png]]

216

217

218

Below is the NB-IoT Product Table show the mapping.

219

220

(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1386px" %)

221

|(% style="background-color:#4f81bd; width:124px" %) |(% style="background-color:#4f81bd; color:white; width:91px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:159px" %)Field3|(% style="background-color:#4f81bd; color:white; width:153px" %)Field4|(% style="background-color:#4f81bd; color:white; width:152px" %)Field5|(% style="background-color:#4f81bd; color:white; width:148px" %)Field6|(% style="background-color:#4f81bd; color:white; width:164px" %)Field7|(% style="background-color:#4f81bd; color:white; width:152px" %)Field8|(% style="background-color:#4f81bd; color:white; width:66px" %)Field9|(% style="background-color:#4f81bd; color:white; width:66px" %)Field10

|(% 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

233

|(% 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" %)

234

|(% 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" %)

235

|(% 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" %)

236

|(% 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" %)

237

|(% 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" %)

238

|(% 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" %)

239

|(% 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" %)

== 3.4 Datacake ==

=== 3.4.1 Define Product ===

245

246

247

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.

248

249

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"**.

250

251

[[image:image-20230802112413-14.png||height="1095" width="1302"]]

252

253

254

=== 3.4.2 Create Device ===

255

256

257

In the second step you have to define the device which should be added to the product.

258

259

[[image:image-20230802112413-15.png||height="859" width="1290"]]

260

261

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.

262

263

264

=== 3.4.3 Create Database Fields ===

265

266

267

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.

268

269

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"**.

270

271

[[image:image-20230802112413-16.png||height="495" width="1310"]]

272

273

[[image:image-20230802112413-17.png||height="741" width="1303"]]

274

275

To create a first database field, please click on the (% style="color:blue" %)**"Add Field"**(%%) button as marked in the screenshot above.

276

277

This will open another modal asking for some required input for your first field.

278

279

[[image:image-20230802112413-18.png||height="878" width="1305"]]

280

281

[[image:image-20230802112413-19.png]]

282

283

284

=== 3.4.4 Set up Broker ===

285

286

287

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.

288

289

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.

290

291

View your Personal Access Token

292

293

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:

294

295

[[image:image-20230802112413-20.png]]

296

297

298

(% style="color:blue" %)**MQTT Client-ID**

299

300

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

301

specification blank. Your client then creates a randomly generated ID.

302

303

* (% style="color:blue" %)**AT+CLIENT=“Any value”**

304

305

* (% style="color:blue" %)**AT+UNAME=Token**

306

307

* (% style="color:blue" %)**AT+PWD=Token**

308

309

[[image:image-20230802112413-21.png]]

310

311

312

=== 3.4.5 Create your first Subscription ===

313

314

315

(% style="color:blue" %)**Subscribe**

316

317

Data is published according to the following structure: (% style="color:blue" %)**dtck~/~//**(%%)** **

318

319

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.

320

321

322

[[image:image-20230802112413-22.png]]

323

324

325

[[image:image-20230802112413-23.png]]

326

327

328

[[image:image-20230802112413-24.png]]

329

330

331

(% style="color:blue" %)**example:**

332

333

AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature

334

335

[[image:image-20230802112413-25.png]]

336

337

338

=== 3.4.6 Define Publish Topic ===

339

340

341

(% style="color:blue" %)**Publish**

342

343

To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure.

344

345

Due to the nature of MQTT, the topic prefix differs as follows: (% style="color:blue" %)**dtck-pub~/~//**

346

347

(% style="color:blue" %)**example:**

348

349

AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature

350

351

352

=== 3.4.7 upload data ===

353

354

355

[[image:image-20230802112413-26.png]]

356

357

[[image:image-20230802112413-27.png]]

358

359

[[image:image-20230802112413-28.png]]

360

361

362

== 3.5 Node-Red (via MQTT) ==

363

364

=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===

365

366

367

[[image:image-20230802112413-29.png]]

368

369

370

[[image:image-20230802112413-30.png]]

371

372

373

=== 3.5.2 Simulate Connection ===

374

375

376

[[image:image-20230802112413-31.png]]

377

378

379

=== 3.5.3 Configure NB-IoT Sensors ===

380

381

382

* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%) ~/~/ Set to mqtt Server and Payload

383

384

* (% style="color:blue" %)**AT+CLIENT=any value**

385

386

* (% style="color:blue" %)**AT+UNAME=any value**

387

388

* (% style="color:blue" %)**AT+PWD=any value**

389

390

* (% style="color:blue" %)**AT+PUBTOPIC=any value**

391

392

* (% style="color:blue" %)**AT+SUBTOPIC=any value**

393

394

395

== 3.6 ThingsBoard.Cloud (via MQTT) ==

396

397

=== 3.6.1 Configure ThingsBoard ===

398

399

==== 3.6.1.1 Create Device ====

400

401

402

Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].

403

404

[[image:image-20230802112413-32.png]]

405

406

407

==== 3.6.1.2 Create Uplink & Downlink Converter ====

408

409

410

(% style="color:blue" %)**Uplink Converter**

411

412

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.

413

414

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.

415

416

[[image:image-20230802112413-33.png||height="732" width="1302"]]

417

418

419

(% style="color:blue" %)**Downlink Converter**

420

421

The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke

422

423

[[image:image-20230802112413-34.png||height="734" width="1305"]]

424

425

(% style="color:red" %)**Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**

426

427

428

==== 3.6.1.3 MQTT Integration Setup ====

429

430

431

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**;

432

433

[[image:image-20230802112413-35.png||height="738" width="1312"]]

434

435

436

* The next steps is to add the recently created uplink and downlink converters;

437

438

[[image:image-20230802112413-36.png||height="736" width="1308"]]

439

440

[[image:image-20230802112413-37.png||height="735" width="1307"]]

441

442

443

(% style="color:blue" %)**Add a topic filter:**

444

445

tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature **固定的? 对的。**

446

447

You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;

448

449

[[image:image-20230802112413-38.png||height="731" width="1300"]]

450

451

452

=== 3.6.2 Simulate with MQTT.fx ===

453

454

455

[[image:image-20230802112413-39.png]]

456

457

[[image:image-20230802112413-40.png]]

458

459

460

=== 3.6.3 Configure NB-IoT Sensor ===

461

462

463

(% style="color:blue" %)**AT Commands**

464

465

* (% style="color:#037691" %)**AT+PRO=3,3 **(%%)** **~/~/ Use MQTT to connect to ThingsBoard.

466

467

* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的**

468

469

* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的**

470

471

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 吧).这边不用提示了，客户不需要输入。（大部分客户还是会自己去设置这个的，提高安全性）**

472

473

(% style="color:blue" %)**CLIENT :“Any value”**

474

475

(% style="color:blue" %)**User Name:“Any value”**

476

477

(% style="color:blue" %)**Password:“Any value”**

478

479

480

Test Uplink by click the button for 1 second

481

482

[[image:image-20230802112413-41.png]]

483

484

[[image:image-20230802112413-42.png]]

485

486

[[image:image-20230802112413-43.png]]

487

488

489

== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==

490

491

=== 3.7.1 Create device & Get Credentials ===

492

493

494

We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.

495

496

[[image:image-20230802112413-44.png]]

497

498

[[image:image-20230802112413-45.png]]

499

500

501

Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.

502

503

[[image:image-20230802112413-46.png]]

504

505

506

On the Connection Profile window, set the following information: **(这边加一个截图)**

507

508

* (% style="color:blue" %)**Profile Name: “Any name”**

509

510

* (% style="color:blue" %)**Broker Address: mqtt.tago.io**

511

512

* (% style="color:blue" %)**Broker Port: 1883**

513

514

* (% style="color:blue" %)**Client ID: “Any value”**

515

516

On the section User credentials, set the following information: **(这边加一个截图)**

517

518

* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only

519

520

* (% style="color:blue" %)**Password: “Your device token”**

521

522

* (% style="color:blue" %)**PUBTOPIC: “Any value”**

523

524

* (% style="color:blue" %)**SUBTOPIC: “Any value”**

525

526

=== 3.7.2 Simulate with MQTT.fx ===

527

528

529

[[image:image-20230802112413-47.png]]

530

531

[[image:image-20230802112413-48.png]]

532

533

Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.

534

535

536

[[image:image-20230802112413-49.png]]

537

538

539

=== 3.7.3 tago data ===

540

541

542

[[image:image-20230802112413-50.png]]

543

544

[[image:image-20230802112413-51.png]]

545

546

547

=== 3.7.4 TLS mode ===

548

549

550

Users can choose to use (% style="color:blue" %)**SSL/TLS**(%%) mode.

551

552

On the SSL/TLS section, check the option **Enable SSL/TLS**, and click OK.

553

554

The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.

555

556

* (% style="color:blue" %)**Profile Name: “Any name”**

557

558

* (% style="color:blue" %)**Broker Address: mqtt.tago.io**

559

560

* (% style="color:blue" %)**Broker Port: 8883**

561

562

* (% style="color:blue" %)**Client ID: “Any value”**

563

564

* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only

565

566

* (% style="color:blue" %)**Password: “Your device token”**

567

568

* (% style="color:blue" %)**PUBTOPIC: “Any value”**

569

570

* (% style="color:blue" %)**SUBTOPIC: “Any value”**

571

572

[[image:image-20230802112413-52.png]]

573

574

575

Wiki source code of General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Applications

Navigation