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

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

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:114px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:154px" %)**APN**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**

28

|(% style="width:114px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:154px" %)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:114px" %)China Mobile|(% style="width:154px" %) |(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)

34

|(% style="width:114px" %)China Telecom|(% style="width:154px" %) |(% style="width:474px" %)China Mainland|(% style="width:135px" %)

= 3. Configure to connect to different servers =

39

40

== 3.1 General UDP Connection ==

41

42

43

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

44

45

46

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

47

48

49

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

50

51

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

52

53

54

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

55

56

==== 3.1.2.1 AT Commands ====

57

58

59

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

60

61

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

62

63

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

64

65

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

66

67

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

68

69

70

==== 3.1.2.2 Uplink Example ====

71

72

73

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

74

75

76

== 3.2 General MQTT Connection ==

77

78

79

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

80

81

Below are the commands.

82

83

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

84

85

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

86

87

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

88

89

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

90

91

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

92

93

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

94

95

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

96

97

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

98

99

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

100

101

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

102

103

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

104

105

106

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

107

108

=== 3.3.1 Get MQTT Credentials ===

109

110

111

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

112

113

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

114

115

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

116

117

118

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

119

120

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

121

122

123

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

124

125

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

126

127

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

128

129

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

130

131

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

132

133

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

134

135

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

136

137

138

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

139

140

141

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

142

143

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

144

145

146

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

147

148

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

149

150

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

151

152

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

153

154

155

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

156

157

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

158

159

160

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

161

162

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

163

164

165

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

166

167

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

168

169

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

170

171

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

172

173

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

174

175

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

176

177

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

178

179

180

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

209

210

211

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.

212

213

214

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

215

216

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

217

218

219

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

220

221

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

222

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

234

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

235

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

236

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

237

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

238

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

239

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

240

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

246

247

248

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.

249

250

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

251

252

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

253

254

255

=== 3.4.2 Create Device ===

256

257

258

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

259

260

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

261

262

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.

263

264

265

=== 3.4.3 Create Database Fields ===

266

267

268

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.

269

270

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

271

272

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

273

274

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

275

276

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

277

278

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

279

280

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

281

282

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

283

284

285

=== 3.4.4 Set up Broker ===

286

287

288

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.

289

290

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.

291

292

View your Personal Access Token

293

294

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:

295

296

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

297

298

299

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

300

301

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

302

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

303

304

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

305

306

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

307

308

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

309

310

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

311

312

313

=== 3.4.5 Create your first Subscription ===

314

315

316

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

317

318

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

319

320

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.

321

322

323

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

324

325

326

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

327

328

329

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

330

331

332

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

333

334

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

335

336

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

337

338

339

=== 3.4.6 Define Publish Topic ===

340

341

342

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

343

344

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

345

346

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

347

348

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

349

350

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

351

352

353

=== 3.4.7 upload data ===

354

355

356

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

357

358

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

359

360

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

361

362

363

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

364

365

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

366

367

368

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

369

370

371

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

372

373

374

=== 3.5.2 Simulate Connection ===

375

376

377

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

378

379

380

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

381

382

383

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

384

385

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

386

387

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

388

389

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

390

391

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

392

393

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

394

395

396

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

397

398

=== 3.6.1 Configure ThingsBoard ===

399

400

==== 3.6.1.1 Create Device ====

401

402

403

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

404

405

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

406

407

408

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

409

410

411

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

412

413

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.

414

415

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.

416

417

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

418

419

420

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

421

422

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

423

424

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

425

426

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

427

428

429

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

430

431

432

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

433

434

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

435

436

437

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

438

439

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

440

441

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

442

443

444

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

445

446

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

447

448

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

449

450

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

451

452

453

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

454

455

456

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

457

458

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

459

460

461

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

462

463

464

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

465

466

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

467

468

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

469

470

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

471

472

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

473

474

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

475

476

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

477

478

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

479

480

481

Test Uplink by click the button for 1 second

482

483

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

484

485

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

486

487

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

488

489

490

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

491

492

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

493

494

495

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.

496

497

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

498

499

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

500

501

502

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

503

504

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

505

506

507

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

508

509

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

510

511

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

512

513

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

514

515

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

516

517

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

518

519

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

520

521

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

522

523

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

524

525

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

526

527

528

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

529

530

531

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

532

533

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

534

535

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

536

537

538

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

539

540

541

=== 3.7.3 tago data ===

542

543

544

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

545

546

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

547

548

549

=== 3.7.4 TLS mode ===

550

551

552

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

553

554

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

555

556

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

557

558

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

559

560

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

561

562

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

563

564

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

565

566

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

567

568

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

569

570

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

571

572

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

573

574

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

575

576

577

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

Applications

Navigation