MQTT Forward Instruction

* Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]

15

* LG01N, OLG01N ((% class="mark" %)**Warning**(%%): LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>url:https://wiki.dragino.com/index.php/Through_MQTT_to_upload_data]])

16

* LG02, OLG02

* LG308, DLOS8

* LPS8

* LIG16

* MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support)

21

22

= 2. Firmware Change Log for MQTT feature =

23

24

(((

25

This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware.

26

)))

27

28

* LG02_LG08-5.3.1580178039

29

** Initiate version

30

31

= 3. MQTT forward operating principle =

32

33

== 3.1 Network Structure ==

34

35

Below shows the network structure for MQTT forwarding.

36

37

* For Uplink: The sensor sends data to LoRa Gateway via LoRa wireless, The gateway will process these data and forward to remote MQTT Broker via Internet.

38

* For Downlink: The gateway subscribe a topic in the MQTT broker, when there is update on the topic, the gateway will know and broadcast the data to Local LoRa network,

39

40

[[image:https://wiki.dragino.com/images/thumb/4/45/MQTT_Forward_1.png/600px-MQTT_Forward_1.png||height="348" width="600"]]

41

42

General MQTT structure

43

44

45

== 3.2 How sensor data is forwarded ==

46

47

In this MQTT forward feature, the key point is how the gateway process the sensor data.

48

49

50

=== 3.2.1 Upstream ===

51

52

Assume there are two sensor nodes, their ID are Node1 ID: 6734 , Node2 ID: 7456. In the remote MQTT broker there are two topics: Topic1: /channel/765800, Topic2: /channel/367860. We can set up in the gateway to map Node1 to Topic1 and Node2 to Topic2. So when there is a sensor data from Node1, the gateway will forward the data to Topic1, when there is sensor data from Node2, the gateway will forward to Topic2.

53

54

(((

55

The data flow works as below diagram.

56

)))

57

58

[[~[~[image:https://wiki.dragino.com/images/thumb/2/2a/MQTT_Forward_2.png/600px-MQTT_Forward_2.png~|~|height="355" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_2.png]]

(((

Upstream path

)))

(((

Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span>

)))

(((

)))

=== 3.2.2 Downstream ===

73

74

The gateway subscribes to a topic of the remote MQTT broker topic. When there is some one publish a value on this topic. The gateway will get it and broadcast to local LoRa Network.

75

76

(((

77

Below are the data flow for downstream.

78

)))

79

80

[[image:https://wiki.dragino.com/images/thumb/3/3a/MQTT_Forward_3.png/600px-MQTT_Forward_3.png||height="368" width="600"]]

Downstream path

== 3.3 Macro Definition ==

86

87

The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.

88

89

(((

90

Currently the (% class="mark" %)**-t (topic)**(%%) and (% class="mark" %)**-m (message)**(%%) support Macros.

91

)))

92

93

=== 3.3.1 -t topic macro ===

94

95

* CHANNEL: Remote Channel ID

96

* CLIENTID: Client ID , Same as -i

97

* WRITE_API: Remote Channel Write API

98

* USERNAME: User ID (-u)

99

* HOSTNAME: Device Hostname

100

101

=== 3.3.2 -m message macro ===

102

103

* HOSTNAME: Device Hostname

104

* CHANNEL: Remote Channel ID

105

* DATA: Sensor Data without time stamp and rssi

106

* META: Completely sensor data with time stamp and rssi

107

* JSON: Convert META to json format.

108

109

=== 3.3.3 Example for Macro ===

110

111

[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]

112

113

MQTT Publish configure

114

115

Above screen shots shows below format:

116

117

* -t: CLIENTID/CHANNEL/data

118

* -m: DATA

119

120

When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below:

121

122

[[image:https://wiki.dragino.com/images/thumb/c/c4/MQTT_Command_20.png/600px-MQTT_Command_20.png||height="325" width="600"]]

Sensor Data

(((

According to above macro. Gateway will publish (% class="mark" %)**field1=22.0&field2=49.0**(%%) to topic: (% class="mark" %)**dragino-1b7060/78901/data**(%%), where 78901 is the remote channel for this node ID.

)))

== 3.4 Modify the MQTT to support more options ==

132

133

The MQTT Client Utility used in Dragino is **mosquitto_pub** and **mosquitto_sub**. User can add more options to the mqtt commands. User can check the valid options by command mosquitto_pub ~-~-help. as below:

(% class="box" %)

(((

root@dragino-1ec39c:~~# mosquitto_pub ~-~-help

138

mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit.

139

mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4.

140

\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}

141

{-f file | -l | -n | -m message}

142

[-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time]

143

[-A bind_address]

144

[-i id] [-I id_prefix]

145

[-d] [~-~-quiet]

146

[-M max_inflight]

147

[-u username [-P password]]

148

[~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]]

149

[{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file]

150

[~-~-ciphers ciphers] [~-~-insecure]

151

[~-~-tls-alpn protocol]

152

[~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]

153

[~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]]

154

[~-~-proxy socks-url]

155

[~-~-property command identifier value]

156

[-D command identifier value]

157

mosquitto_pub ~-~-help

158

\\-A : bind the outgoing socket to this host/ip address. Use to control which interface

159

the client communicates over.

160

-d : enable debug messages.

161

-D : Define MQTT v5 properties. See the documentation for more details.

162

-f : send the contents of a file as the message.

163

-h : mqtt host to connect to. Defaults to localhost.

164

-i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id.

165

-I : define the client id as id_prefix appended with the process id. Useful for when the

166

broker is using the clientid_prefixes option.

167

-k : keep alive in seconds for this client. Defaults to 60.

168

-L : specify user, password, hostname, port and topic as a URL in the form:

169

mqtt(s):~/~/[username[:password]@]host[:port]/topic

170

-l : read messages from stdin, sending a separate message for each line.

171

-m : message payload to send.

172

-M : the maximum inflight messages for QoS 1/2..

173

-n : send a null (zero length) message.

174

-p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS.

175

-P : provide a password

176

-q : quality of service level to use for all messages. Defaults to 0.

177

-r : message should be retained.

178

-s : read message from stdin, sending the entire input as a message.

179

-t : mqtt topic to publish to.

180

-u : provide a username

181

-V : specify the version of the MQTT protocol to use when connecting.

182

Can be mqttv5, mqttv311 or mqttv31. Defaults to mqttv311.

183

~-~-help : display this message.

184

~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.

185

~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0.

186

~-~-quiet : (% class="mark" %)don't print error messages.

187

~-~-will-payload : payload for the client Will, which is sent by the broker in case of

188

unexpected disconnection. If not given and will-topic is set, a zero

189

length message will be sent.

190

~-~-will-qos : QoS level for the client Will.

191

~-~-will-retain : if given, make the client Will retained.

192

~-~-will-topic : the topic on which to publish the client Will.

193

~-~-cafile : path to a file containing trusted CA certificates to enable encrypted

194

communication.

195

~-~-capath : path to a directory containing trusted CA certificates to enable encrypted

196

communication.

197

~-~-cert : client certificate for authentication, if required by server.

198

~-~-key : client private key for authentication, if required by server.

199

~-~-keyform : keyfile type, can be either "pem" or "engine".

200

~-~-ciphers : openssl compatible list of TLS ciphers to support.

201

~-~-tls-version : TLS protocol version, can be one of tlsv1.3 tlsv1.2 or tlsv1.1.

202

Defaults to tlsv1.2 if available.

203

~-~-insecure : do not check that the server certificate hostname matches the remote

204

hostname. Using this option means that you cannot be sure that the

205

remote host is the server you wish to connect to and so is insecure.

206

Do not use this option in a production environment.

207

~-~-tls-engine : If set, enables the use of a TLS engine device.

208

~-~-tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine.

209

~-~-psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode.

210

~-~-psk-identity : client identity string for TLS-PSK mode.

211

~-~-proxy : SOCKS5 proxy URL of the form:

212

socks5h:~/~/[username[:password]@]hostname[:port]

213

Only "none" and "username" authentication is supported.

214

\\See https:~/~/mosquitto.org/ for more information.

)))

(((

and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines:

)))

(% class="box" %)

(((

# Call MQTT Publish command

225

\\# 1. Case with User, Password and Client ID present (e.g. Azure)

226

if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then

227

case="1"

228

mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user -P "$pass" $C $cafile $PUB_FLAG "$mqtt_data"

229

\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS)

230

elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then

231

case="2"

232

mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic ~-~-cert $cert ~-~-key $key $C $cafile $PUB_FLAG "$mqtt_data"

233

\\# 3. Case with no User, Certificate or ClientID present

234

elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then

235

case="3"

236

mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data"

237

\\# 4. Case with no User, Certificate, but with ClientID present

238

elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then

239

case="4"

240

mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data"

241

\\# 5. Case with User and ClientID present, but no Password and no Certificate present

242

elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then

243

case="5"

244

mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data"

245

\\# 6. Case with User and Password present, but no ClientID and no Certificate present

246

elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then

247

case="6"

248

mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data"

249

\\# 0. Else - invalid parameters, just log

250

else

251

case="Invalid parameters"

252

logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."

fi

)))

= 4. Example to communicate to a simple MQTT server =

== 4.1 Overview ==

This section is an example to show how to set up LG01-N to communicate with a MQTT server. The MQTT server is a simple utility set up in a local PC. Note: User can set up same server via [[this instruction>>url:http://www.steves-internet-guide.com/install-mosquitto-broker/]].

262

263

== 4.2 Simulate via MQTT.fx utility ==

264

265

The [[MQTT.fx>>url:http://mqttfx.jensd.de/index.php/download]] is a MQTT client tool. We can use this to simulate a MQTT connection to our MQTT broker first to make sure the MQTT broker works. This will also help us understand how it works.

266

267

(((

268

In this test, the MQTT broker and MQTT.fx are installed in the same PC, so the MQTT server address in MQTT.fx should be localhost. Below shows how to connect to the server.

269

)))

270

271

[[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png||height="201" width="600"]]

272

273

Connect to MQTT Broker

274

275

After connected, use publish to public some thing to MQTT server. This to simulate upsteam

276

277

[[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png||height="149" width="600"]]

278

279

Upstream: Publish message to MQTT Broker

280

281

To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:

282

283

[[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png||height="279" width="600"]]

284

285

Downstream: Subscribe a topic to get downstream

286

287

288

== 4.3 Simulate via Dragino Command Line ==

289

290

For first try of MQTT connection, simulate via command line is recommend, there are many servers / connection type for MQTT. They are using different connection parameters. Simulating the connection via command line will help us rapidly connect to server and debug.

291

292

In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.

293

294

295

(% class="mark" %)**For Upstream**

296

297

command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]

298

299

Example: mosquitto_pub -h 192.168.199.148 -p 1883 -t /channel/6543 -m temp=36

300

301

Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network.

302

303

[[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png||height="188" width="600"]]

mosquitto_pub

(% class="mark" %)**For Downstream**

309

310

Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.

311

312

[[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png||height="267" width="600"]]

mosquitto_sub

== 4.4 Configure Dragino UI for MQTT connection ==

318

319

This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.

320

321

(((

322

Go to (% class="mark" %)**Dragino Menu ~-~-> MQTT Client**

323

)))

324

325

[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]]

326

327

go to mqtt configure menu

328

329

(((

330

Select **Forward to MQTT server**. (% class="mark" %)**Notice**(%%): This option is removed from the latest firmware, in the latest firmware, if user submit "SAVE & APPLY" in MQTT page, the gateway will use MQTT service.

331

)))

332

333

[[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png||height="240" width="600"]]

forward to MQTT

=== 4.4.1 Configure the MQTT Client for Upstream ===

339

340

Below screenshot is same as the publish command:

(% class="box" %)

(((

mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA

345

~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for

346

~/~/CLIENTID: dragino-1b7060

347

~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456

348

~/~/DATA: The data stores in /var/iot/channels/

349

)))

350

351

[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]

352

353

MQTT Publish configure

354

355

356

[[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]]

357

358

MQTT Channel settings

359

360

(((

361

For example, if we put a data(temp=46) on the file /var/iot/channels/4567, because 4567 match the remote channel 78901. the gateway will run this command:

)))

(% class="box" %)

(((

mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46

)))

(((

to MQTT broker.

)))

(((

Below is a simulation to put this data to active the MQTT publish.

376

)))

377

378

[[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]]

MQTT Publish

=== 4.4.2 Configure the MQTT Client for Downstream ===

384

385

Below screen shot equal to this subscribe command:

(% class="box" %)

(((

mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.

390

)))

391

392

[[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]]

MQTT Subscribe

(((

When MQTT broker receive a update on this topic, the gateway will get the update and use LoRa radio to broadcast this message. The LoRa parameters used for update is:

399

)))

400

401

[[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]]

402

403

LoRa Broadcast parameters.

404

405

406

And below is the subscribe simulation:

407

408

[[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png||height="255" width="600"]]

409

410

downstream simulation

411

412

413

== 4.5 Add LoRa support to communicate with remote sensor ==

414

415

In above section, we have configured the UI to support MQTT upstream and downstream. We can simulate via Linux command. In this section, we will guide how to communicate with remote LoRa End Node for upstream and downstream.

416

417

=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===

418

419

(((

420

We can use [[LoRa Shield>>url:http://www.dragino.com/products/lora/item/102-lora-shield.html]] to send LoRa Raw data to Gateway and receive data from gateway.

)))

(((

The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]

)))

(((

And this link is the required library: [[arduino-LoRa-master>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]. Unzip this library and put in Arduino library location.

)))

(((

What does the Arduino Sketch do? The Arduino Sketch will:

433

)))

434

435

* Upstream: Keep sending a LoRa Message every minutes with this payload : <4567>tem=xx&hum=yy (Where xx and yy are temperature and humidity value generated randomly).

436

* Downstream: Listening broadcast message from gateway, and print it in console.

437

* The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below:

438

439

[[image:https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png||height="197" width="600"]]

440

441

LoRa Parameter should match

442

443

444

Below is the test result after the Arduino Sketch is running.

445

446

[[image:https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png||height="319" width="600"]]

Upstream Data Flow

[[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png||height="309" width="600"]]

Downstream Data Flow

=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===

456

457

(((

458

Since firmware (% class="mark" %)**LG02_LG08~-~-build-v5.3.1585192026-20200326-1109,**(%%) Dragino LoRaWAN gateways support the communication to LoRaWAN (% class="mark" %)**ABP end node**(%%) locally without the need of LoRaWAN server. This feature allow us to integrate MQTT in the gateway to support LoRaWAN to MQTT forwarding or visa verse.

)))

(((

When use test this feature, please use the version higher then : (% class="mark" %)**LG02_LG08~-~-build-v5.4.1593400722-20200629-1120**(%%), in this version, the upload format is changed and readable, which is easier for integration.

463

(% class="mark" %)**Video Instruction**(%%):[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]

)))

(((

**Step 1**: Refer [[Communicate with ABP End Node>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node]] to know how to set up LG308 to work with LoRaWAN End node.

)))

(((

**Step 2**: Make sure your Radio settings match the End Node settings.

472

)))

473

474

[[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png||height="387" width="600"]]

475

476

Use Same Frequency Band as End Node

(((

**Step 3**: Set up publish format and MQTT channel. The LG308 will store the Data from End node in HEX format in the file. And we need to config the format to META

481

)))

482

483

[[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png||height="385" width="600"]]

484

485

Publish mush use META as data format for LG308

486

487

488

**Step 4**: Map the Device Address to Remote ID in MQTT server.

489

490

[[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png||height="335" width="600"]]

491

492

Map Dev Addr to remote ID

493

494

495

**Step 5: Upstream**: Save the change, we can see the log info via "sytem log", End Node and MQTT Server

496

497

[[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png||height="279" width="600"]]

Upstream Process

[[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png||height="246" width="600"]]

Choose ASCII Format

[[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png||height="248" width="600"]]

LHT65 Decoder

**Step 6: Set up subscribe:** Subscribe a topci for downstream.

511

512

[[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]]

Subscribe to a topic

**Step 7**: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.

518

519

[[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]]

Downstream Flow

Notice: The text use for Downstream must meet the requirement from [[LG308 Downstream Payload>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node#Downstream]]

524

525

526

= 5. Example For Different MQTT Servers =

527

528

(% style="width:731.222px" %)

529

|=(% style="width: 270px;" %)(((

530

[[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png||alt="ThingSpeak1.png" height="114" width="233"]]

531

532

== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ==

533

534

535

[[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]]

536

)))|=(% style="width: 242px;" %)(((

537

[[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png||alt="Lewei50.png" height="65" width="223"]]

== ==

== [[乐联网平台>>url:https://www.lewei50.com/]] ==

542

543

544

[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]]

545

)))|=(% style="width: 214px;" %)(((

546

[[image:https://wiki.dragino.com/images/thumb/a/aa/AWS-IOT.png/200px-AWS-IOT.png||alt="AWS-IOT.png" height="112" width="183"]]

547

548

== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ==

549

550

551

[[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]]

)))

= 6. How to Debug =

User can login the gateway's console and run (% class="mark" %)**logread -f**(%%). It will shows the output when there is packet arrive.User can see if it is correct.

557

558

= 7. How to ask for Support =

559

560

If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:

561

562

* Detail of your LoRaWAN end node.

563

* Gateway Model and firmware version

564