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. Network Connection =

14

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.

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

|1NCE| | |

|China Mobile| | |

== 2.1 1NCE SIM Card. ==

= 3. Configure to connect to different servers =

30

31

== 3.1 General UDP Connection ==

32

33

34

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

35

36

37

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

38

39

40

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

41

42

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

43

44

45

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

46

47

==== 3.1.2.1 AT Commands ====

48

49

50

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

51

52

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

53

54

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

55

56

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

57

58

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

59

60

61

==== 3.1.2.2 Uplink Example ====

62

63

64

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

65

66

67

== 3.2 General MQTT Connection ==

68

69

70

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

71

72

Below are the commands.

73

74

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

75

76

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

77

78

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

79

80

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

81

82

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

83

84

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

85

86

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

87

88

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

89

90

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

91

92

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

93

94

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

95

96

97

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

98

99

=== 3.3.1 Get MQTT Credentials ===

100

101

102

[[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.

103

104

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

105

106

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

107

108

109

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

110

111

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

112

113

114

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

115

116

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

117

118

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

119

120

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

121

122

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

123

124

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

125

126

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

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

131

132

133

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

134

135

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

136

137

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

138

139

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

140

141

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

142

143

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

144

145

146

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

147

148

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

149

150

151

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

152

153

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

154

155

156

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

157

158

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

159

160

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

161

162

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

163

164

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

165

166

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

167

168

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

169

170

171

==== 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 ====

200

201

202

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.

203

204

205

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

206

207

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

208

209

210

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

211

212

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

213

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

225

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

226

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

227

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

228

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

229

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

230

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

231

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

236

237

238

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.

239

240

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

241

242

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

243

244

245

=== 3.4.2 Create Device ===

246

247

248

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

249

250

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

251

252

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.

253

254

255

=== 3.4.3 Create Database Fields ===

256

257

258

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.

259

260

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

261

262

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

263

264

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

265

266

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

267

268

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

269

270

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

271

272

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

273

274

275

=== 3.4.4 Set up Broker ===

276

277

278

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.

279

280

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.

281

282

View your Personal Access Token

283

284

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:

285

286

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

287

288

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

289

290

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.

291

292

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

293

294

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

295

296

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

297

298

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

299

300

301

=== 3.4.5 Create your first Subscription ===

302

303

304

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

305

306

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

307

308

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.

309

310

311

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

312

313

314

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

315

316

317

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

318

319

320

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

321

322

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

323

324

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

325

326

327

=== 3.4.6 Define Publish Topic ===

328

329

330

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

331

332

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

333

334

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

335

336

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

337

338

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

339

340

341

=== 3.4.7 upload data ===

342

343

344

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

345

346

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

347

348

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

349

350

351

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

352

353

=== 3.5.1 Configure Node-Red ===

354

355

356

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

357

358

359

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

360

361

362

=== 3.5.2 Simulate Connection ===

363

364

365

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

366

367

368

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

369

370

371

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

372

373

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

374

375

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

376

377

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

378

379

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

380

381

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

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

386

387

=== 3.6.1 Configure ThingsBoard ===

388

389

==== 3.6.1.1 Create Device ====

390

391

392

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

393

394

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

395

396

397

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

398

399

400

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

401

402

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.

403

404

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.

405

406

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

407

408

409

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

410

411

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

412

413

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

414

415

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

416

417

418

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

419

420

421

Go to the **Integrations center** -> **Integrations page** and click **“plus”** icon to add a new integration. Name it **“MQTT Integration”**, select type MQTT;

422

423

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

424

425

426

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

427

428

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

429

430

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

431

432

433

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

434

435

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

436

437

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

438

439

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

440

441

442

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

443

444

445

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

446

447

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

448

449

450

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

451

452

453

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

454

455

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

456

457

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

458

459

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

460

461

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

462

463

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

464

465

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

466

467

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

468

469

470

Test Uplink by click the button for 1 second

471

472

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

473

474

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

475

476

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

477

478

479

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

480

481

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

482

483

484

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.

485

486

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

487

488

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

489

490

491

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

492

493

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

494

495

496

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

497

498

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

499

500

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

501

502

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

503

504

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

505

506

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

507

508

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

509

510

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

511

512

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

513

514

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

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

520

521

522

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

523

524

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

525

526

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

527

528

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

529

530

531

=== 3.7.3 tago data ===

532

533

534

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

535

536

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

537

538

539

=== 3.7.4 TLS mode ===

540

541

542

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

543

544

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

545

546

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

547

548

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

549

550

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

551

552

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

553

554

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

555

556

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

557

558

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

559

560

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

561

562

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

563

564

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

565

566

567

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

Applications

Navigation