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 =

9

10

11

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.

12

13

14

= 2. Network Connection =

15

16

17

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.

18

19

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

20

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

29

30

== 3.1 General UDP Connection ==

31

32

33

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

34

35

36

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

37

38

39

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

40

41

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

42

43

44

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

45

46

==== 3.1.2.1 AT Commands ====

47

48

49

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

50

51

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

52

53

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

54

55

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

56

57

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

58

59

60

==== 3.1.2.2 Uplink Example ====

61

62

63

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

64

65

66

== 3.2 General MQTT Connection ==

67

68

69

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

70

71

Below are the commands.

72

73

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

74

75

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

76

77

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

78

79

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

80

81

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

82

83

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

84

85

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

86

87

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

88

89

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

90

91

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

92

93

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

94

95

96

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

97

98

=== 3.3.1 Get MQTT Credentials ===

99

100

101

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

102

103

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

104

105

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

106

107

108

== 3.3.2 Simulate with MQTT.fx ==

109

110

=== 3.3.2.1 Establish MQTT Connection ===

111

112

113

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

114

115

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

116

117

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

118

119

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

120

121

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

122

123

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

124

125

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

126

127

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

128

129

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

130

131

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

132

133

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

134

135

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

136

137

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

138

139

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

140

141

142

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

143

144

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

145

146

147

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

148

149

=== 3.3.1 AT Commands: ===

150

151

152

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

153

154

* **AT+PRO=3,1** ~/~/ Set to use ThingSpeak Server and Related Payload

155

156

* **AT+CLIENT=<Your ThingSpeak MQTT ClientID>**

157

158

* **AT+UNAME=<Your ThingSpeak MQTT User Name>**

159

160

* **AT+PWD=<Your ThingSpeak MQTT Password>**

161

162

* **AT+PUBTOPIC=<YOUR_CHANNEL_ID>**

163

164

* **AT+SUBTOPIC=<YOUR_CHANNEL_ID>**

165

166

=== 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 Map fields to sensor value ===

195

196

197

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.

198

199

200

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

201

202

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

203

204

205

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

206

207

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

208

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

220

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

221

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

222

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

223

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

224

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

225

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

226

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

232

233

234

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.

235

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:

dtck~/~//

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:

dtck-pub~/~//

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

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

353

354

=== 3.5.1 Configure Node-Red ===

355

356

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

357

358

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

359

360

361

=== 3.5.2 Simulate Connection ===

362

363

364

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

365

366

367

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

368

369

370

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

371

372

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

373

374

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

375

376

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

377

378

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

379

380

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

381

382

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

383

384

=== 3.6.1 Configure ThingsBoard ===

385

386

==== 3.6.1.1 Create Device ====

387

388

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

389

390

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

391

392

393

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

394

395

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

396

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

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.

400

401

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

402

403

404

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

405

406

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

407

408

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

409

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

412

413

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

414

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;

417

418

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

419

420

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

421

422

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

423

424

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

425

426

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

427

428

429

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

430

431

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

432

433

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

434

435

436

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

437

438

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

439

440

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

441

442

443

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

444

445

446

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

447

448

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

449

450

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

451

452

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

453

454

455

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

456

457

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

458

459

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

460

461

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

462

463

464

Test Uplink by click the button for 1 second

465

466

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

467

468

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

469

470

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

471

472

473

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

474

475

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

476

477

478

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.

479

480

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

481

482

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

483

484

485

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

486

487

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

488

489

490

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

491

492

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

493

494

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

495

496

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

497

498

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

499

500

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

501

502

* **User Name: “Any value”** Tago validates your user by the token only

503

504

* **Password: “Your device token”**

505

506

* **PUBTOPIC: “Any value”**

507

508

* **SUBTOPIC: “Any value”**

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

513

514

515

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

516

517

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

518

519

Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format.

520

521

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

522

523

524

=== 3.7.3 tago data ===

525

526

527

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

528

529

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

530

531

532

=== 3.7.4 TLS mode ===

533

534

535

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

536

537

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

538

539

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

540

541

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

542

543

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

544

545

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

546

547

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

548

549

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

550

551

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

552

553

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

554

555

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

556

557

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

558

559

560

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

Applications

Navigation