Notes for AWS-IoT-Core

1. //LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]//

15

1. //Firmware version since:[[lgw~~-~~-build-v5.4.1614945073>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/lgw--build-v5.4.1614945073-20210305-1953/]]//

16

17

**//What you'll learn in this tutorial//**

18

19

20

//1. How to register a gateway with AWS//

21

22

//2. How to register an end node with AWS//

23

24

//3. How to accept payload date with AWS//

25

26

27

= **2. Gateway Setup Instruction** =

28

29

30

== **2.1 sign up for [[an AWS >>url:https://portal.aws.amazon.com/]]account and select the area** ==

31

32

33

//Sign up for an AWS account//

34

35

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

//Select area//

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

41

42

43

//**Note:** Currently, AWS IoT Core for LoRaWAN is available today in US East (N. Virginia) and Europe (Ireland) Regions. if you are not in either of these areas, their options will not affect your usage.//

44

45

46

== 2.2 Step 2: [[Add an IAM role>>url:https://console.aws.amazon.com/iam/home#/roles]] ==

47

48

49

**//To add the IAM role to allow the Configuration and Update Server (CUPS) to manage gateway credentials:、//**

50

51

//**1.** Open the Roles hub of the IAM console and choose Create role.//

52

53

//**2.** If you think that you might have already added the IoTWirelessGatewayCertManagerRole role, in the search bar, enter IoTWirelessGatewayCertManagerRole.//

54

55

//If you see an IoTWirelessGatewayCertManagerRole role in the search results, you have the necessary IAM role. You can leave the procedure now.//

56

57

//If the search results are empty, you don't have the necessary IAM role. Continue the procedure to add it.//

58

59

//**3. **In Select type of trusted entity, choose Another AWS account.//

60

61

//**4.** In Account ID, enter your AWS account ID and then choose Next: Permissions.//

62

63

//**5.** In the search box, enter AWSIoTWirelessGatewayCertManager.//

64

65

//**6.** In the list of search results, select the policy named AWSIoTWirelessGatewayCertManager.//

66

67

//**7.** Choose Next: Tags, and then choose Next: Review.//

68

69

//**8.** In Role name, enter IoTWirelessGatewayCertManagerRole, and then choose to Create role.//

70

71

//**9.** To edit the new role, in the confirmation message, choose IoTWirelessGatewayCertManagerRole.//

72

73

//**10.** In Summary, choose the Trust relationships tab and then choose Edit trust relationship.//

74

75

//**11.** In the Policy Document, change the Principal property to look like this example.//

(% class="box" %)

(((

"Principal": {

"Service": "iotwireless.amazonaws.com"

},

)))

(% class="box" %)

(((

After you change the Principal property, the complete policy document should look like this example.

)))

(% class="box" %)

(((

{

"Version": "2012-10-17",

"Statement": [

{

"Effect": "Allow",

"Principal": {

"Service": "iotwireless.amazonaws.com"

99

},

100

"Action": "sts:AssumeRole",

"Condition": {}

}

]

}

)))

**12.** To save your changes and exit, choose Update Trust Policy. Note: You’ve now created the IoTWirelessGatewayCertManagerRole. You won’t need to do this again.

111

112

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

tart create role

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

117

118

Choose Another AWS account

119

120

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

start Create policy

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

Choose Next review

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

132

133

In role name,enter AWSIoTWirelessGatewayCertManagerRole,and then choose Create role.

134

135

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

To edit the_new role

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

141

142

143

Choose Edit trust relationship.

144

145

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

146

147

148

Change policy Document

149

150

151

== 2.3 Step 3: Add gateway ==

152

153

154

Locate IoT Core in the AWS Service Control Panel, and locate the Wireless Connection in the IoT Core Control Panel to start adding the Gateway

155

156

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

157

158

Locate IoT Core in the AWS Service Control Panel

159

160

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

161

162

locate the Wireless Connection in the IoT Core Control Panel

163

164

165

== 2.4 Step 4: Get a unique Gateway ID in the gateway ==

166

167

168

Every gateway has a Gateway ID, the ID can be found at Amazon AWS IoT.

169

170

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

Gateway ID

**Note**:User must use the Gateway ID of the Amazon AWS IoT page as the EUI

176

177

**Notice**: In latest firmware. the AWS-IoT configured page is under LoRaWAN Basic Station page.

178

179

180

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

181

182

LoRaWAN Basic Station

183

184

185

== 2.5 Step 5: Configure the gateway and Creation gateway certificates ==

186

187

Configure the gateway and Creation gateway certificates

188

189

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

190

191

Configure the gateway

192

193

[[image:image-20220525173615-15.png]]

194

195

Creation gateway certificates

196

197

**Note: **User Make sure the name of the downloaded file remains the same

198

199

== 2.6 Step 6: Add gateway file ==

200

201

user returns to your gateway, and start adding the three file they got to the gateway.

202

203

[[image:image-20220525173647-16.png]]

204

205

Configure the gateway

206

207

if the user Upload successfully you will see:

208

209

[[image:image-20220525173710-17.png]]

210

211

Uploaded successfully

212

213

(% style="color:red" %)**Notice: **(% style="color:black" %)User must select the correct Upload on the suffix name, otherwise the upload fails.

214

215

== 2.7 Step 7: Add CUPS URI ==

216

217

Users enter the CUPS endpoint copied in the previous step into the CUPS URI and click **"Save&Apply"**

218

219

[[image:image-20220525173735-18.png]]

CUPS URI

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

CUPS URI Setting

**Notice:** After the user hits "Save&Apply", the gateway will start Station mode on its own

228

229

== 2.8 Step 8:Last upLink received ==

230

231

After the above settings, the gateway should be able to connect, the figure below shows the data of the Last upLink received

232

233

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

UpLink received

= 3. Add wireless device =

238

239

== 3.1 step 1:Add device profile ==

240

241

=== 3.1.1 CREATE DEVICE PROFILE ===

242

243

select profile in the Control Panel and add configuration adn service files.the device's configuration paranmeters depend on the LoRaWAN specification it uses.The configuration parameters are found in the device's documentation or on the device itself.

244

245

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

Add device profile

**Provide device data**

(% class="box" %)

(((

**Device profile name** : a descriptive name of your choice for this profile, e.g. “Workshop device profile of ”

254

**Frequency band (RFRegion)** : please select a frequency band your device and gateway will be using. For most European countries EU868 is a right choice. For USA US915 is a right choice. If in doubt, you can review a regional parameters document, section “1.2 Quick cross reference table”.

255

**MAC version** : this parameter should specify the most recent version of LoRaWAN specification supported by your device. Unless device documentation states otherwise, please select 1.0.3.

256

**Regional parameters version**: please select RP002-1.0.1, unless specified otherwise in your device documentation

257

**MaxEIRP** : please enter the default value 15

258

**Supports class **: please select class A, unless you are aware of specific requirements to use classes B and C and your device supports it

259

)))

260

261

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

device profile

**Notice** **: **See the documentation for more information: [[https:~~/~~/docs.aws.amazon.com/iot/latest/developerguide/connect-iot-lorawan-define-profiles.html>>url:https://docs.aws.amazon.com/iot/latest/developerguide/connect-iot-lorawan-define-profiles.html]]

266

267

268

=== 3.1.2 CREATE SERVICE PROFILE ===

269

270

Select “Profiles” view and click on “Add service profile”

271

272

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

273

274

Add a service profile

(% class="box" %)

(((

Choose a service profile name (e.g. “Default service profile”)

279

Ensure that AddGWMetaData parameter is enabled. By enabling this parameter you will receive additional metadata with each device payload, for example RSSI and SNR for the data transmission.

280

This metadata could be used for network coverage optimization.

281

Finally, scroll down and click on “Add service profile”.

282

)))

283

284

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

Add service profile2

== 3.2 Step 2:Create an IAM roles for destinations ==

290

291

AWS IoT Core for LoRaWAN destinations require IAM roles that give AWS IoT Core for LoRaWAN the permissions necessary to send data to the AWS IoT rule. If such a role is not already defined, you'll need to define it so that it will appear in the list of roles.

292

293

**To create an IAM policy for your AWS IoT Core for LoRaWAN destination role**

294

295

**1.** Open the Policies hub of the IAM console.

296

297

**2. **Choose Create policy, and choose the JSON tab.

298

299

**3. **In the editor, delete any content from the editor and paste this policy document.

(% class="box" %)

(((

{

"Version": "2012-10-17",

"Statement": [

{

"Effect": "Allow",

"Action": [

"iot:DescribeEndpoint",

"iot:Publish"

],

"Resource": "*"

}

]

}

)))

**4.** Choose Review policy, and in Name, enter a name for this policy. You'll need this name to use in the next procedure. You can also describe this policy in Description, if you want.

319

320

**5.** Choose Create policy.

321

322

**To create an IAM role for an AWS IoT Core for LoRaWAN destination:**

323

324

**1.** Open the Roles hub of the IAM console and choose Create role.

325

326

**2.** In Select type of trusted entity, choose Another AWS account.

327

328

**3. **In Account ID, enter your AWS account ID, and then choose Next: Permissions.

329

330

**4.** In the search box, enter the name of the IAM policy that you created in the previous procedure.

331

332

**5.** In the search results, check the IAM policy that you created in the previous procedure.

333

334

**6.** Choose Next: Tags, and then choose Next: Review.

335

336

**7. **In Role name, enter the name of this role, and then choose Create role.

337

338

**8.** In the confirmation message, choose the name of the role you created to edit the new role.

339

340

**9. **In Summary, choose the Trust relationships tab, and then choose Edit trust relationship.

341

342

**10.** In Policy Document, change the Principal property to look like this example.

(% class="box" %)

(((

"Principal": {

"Service": "iotwireless.amazonaws.com"

},

)))

After you change the Principal property, the complete policy document should look like this example.

(% class="box" %)

(((

{

"Version": "2012-10-17",

"Statement": [

{

"Effect": "Allow",

"Principal": {

"Service": "iotwireless.amazonaws.com"

362

},

363

"Action": "sts:AssumeRole",

"Condition": {}

}

]

}

)))

**~11. **To save your changes and exit, choose Update Trust Policy.

371

372

With this role defined, you can find it in the list of roles when you configure your AWS IoT Core for LoRaWAN destinations.

373

374

=== 3.2.1 CREATE DESTINATION ===

375

376

**Select Destinations view**

377

378

Please click on “Destinations” menu and afterwards please click on “Add destination”.

379

380

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

Select destinations

**Provide input**

Please provide the following input:

(% class="box" %)

(((

Please choose an IAM role that shall be used for the invocation of AWS IoT Rule.

391

Please select the destination name (e.g. “WorkshopDestination<Your name without spaces>”)

392

Please select the AWS IoT Rule name (e.g. “MyWorkshopLoRaWANRule<Your name without spaces>”)

393

)))

394

395

click on “Add destination”

396

397

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

provide input

=== 3.2.2 CREATE IOT RULE ===

**Create Rule**

user navigating to AWS IoT , Act, Rules and clicking on “Create” button.

406

407

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

Rule create

//Provide a rule name'//

412

413

(((

414

Please input the same IoT Rule name you used in a previous step when creating a new AWS IoT Core for the LoRaWAN destination (e.g. “test_example”).

415

)))

416

417

[[image:image-20220524201202-2.png||height="351" width="611"]]

Enter Rule name

**Provide IoT SQL query statement**

422

423

Please put the following text into the rule query statement: **SELECT *, timestamp() as timestamp**

424

425

[[image:image-20220524201532-4.png||height="387" width="615"]]

426

427

428

Enter SQL query statement

429

430

**Select action “Republish to an AWS IoT Topic”**

431

432

[[image:image-20220524203543-8.png||height="637" width="601"]]

433

434

435

== 3.3 Step 3: Create a destination for end node payloadDate ==

436

437

The PayloadDate of the node will be sent to this destination

438

439

**a.** In the [[destinatons>>url:https://console.aws.amazon.com/iot/home?region=us-east-1#/wireless/destinations]],choose add destination.

440

441

**b.** In IMA Role, select the Role you created in the last step

442

443

**c.** In Destination name, give this destination a destination name.

444

445

**d.** In Rule name, give this rule a new name and remember it.

446

447

**e.** choose Add Destination.

448

449

[[image:image-20220524204934-9.png||height="663" width="627"]]

Add destination

**Note:**The destination rule configuration sent by the end node payloadDate will be in the next step

454

455

== 3.4 Step 4: CREATE WIRELESS DEVICE ==

456

457

Users can register end nodes with AWS

458

459

=== 3.4.1 Open Add wireless device ===

(% class="box" %)

(((

(((

**a.** In Device,choose Add wireless device.

465

**b.** In Wireless device specification，select OTTA 1.0.x

466

**c. **In OTTA 1.0.x

467

**d.** In Profiles,select profilees,and choose Next

)))

)))

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

Add device

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

Enter device keys

**Select device and service profile**

480

481

(((

482

Scroll down and endure that “Associate a thing with your wireless device” option is enabled. AWS will create a thing in AWS IoT for you and associate it with this device. Things in AWS IoT can make it easier to search for and manage your devices.

483

)))

484

485

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

Seleck profile

=== 3.4.2 Select a destination ===

490

491

**Plese select a destination you have created in one of the previous steps and choose add device**

492

493

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

494

495

Add device_choose destition

496

497

498

**REVIEW THE CREATED DEVICER**

499

500

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

Uplink Received

**VERIFY DEVICE CONNECTIVITY**

506

507

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

508

509

Verify device connectivity

510

511

=== 3.4.3 Verify date ingestion ===

512

513

**Open MQTT Test Client**

514

515

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

Open MQTT Client

**Subscribe to topic**

521

522

(((

523

Please input the topic name **workshop_lorawanmessages** in “Subscription topic” field and click on “Subscribe to topic”.

524

525

Users can choose to subscribe to "**#**" ,"#" indicates to subscribe to all.

526

)))

527

528

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

Subscription Topic

**Trigger your device to send telemetry**

533

534

User can start the registered device

535

536

**Review the incoming message from uesr's device**

537

538

Please find below an explanation for some of the attributes:

(% class="box" %)

(((

**PayloadData ** : Base64-encoded payload from the device

543

**~ WirelessMetadata.FPort** : FPort used by the device

544

**~ WirelessMetadata.LoRaWAN.DevEui** : EUI of the device sending the data

545

**~ WirelessMetadata.LoRaWAN.Gateways**: Information on RSSI and SNR per gateway

546

)))

547

548

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

Review message

(% class="box" %)

(((

{

"WirelessDeviceId": "3ff07678-0c3d-4ed7-a01a-4e2cc927e315",

556

"PayloadData": "AAAAAAAAAAAPo2I=",

557

"WirelessMetadata": {

558

"LoRaWAN": {

559

"DataRate": "5",

560

"DevEui": "a840410801818749",

561

"FCnt": 579,

562

"FPort": 2,

563

"Frequency": "867500000",

564

"Gateways": [

565

{

566

"GatewayEui": "a84041ffff1ec39f",

"Rssi": -79,

"Snr": 7.25

},

{

"GatewayEui": "a84041ffff1ee2a0",

"Rssi": -129,

"Snr": -4

}

],

"Timestamp": "2021-04-10T08:16:06Z"

577

}

578

},

579

"timestamp": 1618042566345

}

)))

**How to decode Base64 data into hexadecimal representation**

584

585

You can run the following command in your shell to decode Base64 payload data into their hexadecimal representation.

MacOS

(% class="box" %)

(((

$ echo -n "<Value of PayloadData>" | base64 -D | hexdump -v -e '/1 "%02x"'

)))

Linux

(% class="box" %)

(((

$ echo -n "<Value of PayloadData>" | base64 -d | hexdump -v -e '/1 "%02x"'

)))

Example

(% class="box" %)

(((

$ echo -n "7WkoOEfwfTTioxG6CatHBw==" | base64 -D | hexdump -v -e '/1 "%02x"'

606

ed69283847f07d34e2a311ba09ab4707

607

)))

608

609

= 4. Format a notification by using an AWS Lambda function =

610

611

== 4.1 Introduction ==

612

613

This tutorial demonstrates how to send MQTT message data to an AWS Lambda action for formatting and sending to another AWS service. In this tutorial, the AWS Lambda action uses the AWS SDK to send the formatted message to the Amazon SNS topic

614

615

=== 4.1.1 What you'll learn in this tutorial ===

616

617

How to create and test an AWS Lambda function

618

619

How to use the AWS SDK in an AWS Lambda function to publish an Amazon SNS notification

620

621

How to use simple SQL queries and functions in a rule query statement

622

623

How to use the MQTT client to test an AWS IoT rule

624

625

=== 4.1.2 In this tutorial, you'll: ===

626

627

(((

628

Create an AWS Lambda function that sends a text message

)))

(((

Create an AWS IoT rule with an AWS Lambda rule action

)))

(((

Test the AWS IoT rule and AWS Lambda rule action

637

)))

638

639

== 4.2 Approach A: DECODING BINARY PAYLOADS ==

640

641

=== 4.2.1 Step 1 :Start deployment of a severless application with AWS Lambda function and AWS ioT Rule ===

642

643

**1:Open AWS Lambda console by clicking on [[link>>url:https://console.aws.amazon.com/lambda/home?region=us-east-1#/create/app?applicationId=arn:aws:serverlessrepo:us-east-1:614797420359:applications/aws-iot-corelorawan-sampledecoder]]**

644

645

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

Deployment Lambda

**2:Select a decoder**

651

652

(((

653

Please scroll down to the bottom of the page. Please provide the parameter decoder name based on the following table.

)))

Device Decoder name

LHT65 dragino_lht65

LBT1 dragino_lbt1

LSE01 dragino_lse01

LGT92 dragino_lgt92

LDS01 dragino_lds01

After that please check the box **“I acknowledge that this app creates resource policies.”** and click on **“Deploy”**.

669

670

[[image:image-20220525093033-1.png||height="292" width="615"]]

671

672

Seleck a decoder name

673

674

675

**3:Review deployment**

676

677

(((

678

Please wait few seconds for a successful deployment. After that please click on the name of the Lambda function “TransformLoRaWANBinaryPayloadFunction”.

679

)))

680

681

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

Review deployment

**4. Create the test event**

687

688

Please click on “Configure the test event”

689

690

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

691

692

Create the test event

693

694

(((

695

In the window that opens, please provide the event name e.g. IoTCoreForLoRaWANEvent. After that please paste the following JSON content:

)))

(% class="box" %)

(((

{

"PayloadData": "<Sample PayloadData>",

702

"WirelessDeviceId": "57728ff8-5d1d-4130-9de2-f004d8722bc2",

703

"WirelessMetadata": {

704

"LoRaWAN": {

705

"DataRate": 0,

706

"DevEui": "a84041d55182720b",

707

"FPort": 2,

708

"Frequency": 867900000,

709

"Gateways": [

710

{

711

"GatewayEui": "dca632fffe45b3c0",

"Rssi": -76,

"Snr": 9.75

}

],

"Timestamp": "2020-12-07T14:41:48Z"

}

}

}

)))

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

Create a new event

**5. Provide PayloadData sample**

729

730

(((

731

Please replace the string <Sample PayloadData> in the JSON document with a sample payload for the device you selected in step 2 according to this table. After that please click on “Create”.

)))

(% class="box" %)

(((

(((

Device name Sample “PayloadData”

)))

(((

LHT65 ~-~- y6QHxgG4AQhmf/8=

)))

(((

LSE01 ~-~- AuHtlACmawQPVGM=

746

LGT92 ~-~- DSEAAAEVCMUGpAA=

747

LBT1 ~-~- DxwAAAIDQUJCQ0NEREVFRkYwMjcxMjFGNkFDMy0wNTk=

)))

)))

~[~[File:replace <Sample PayloadDate>.png|600px|none|thumb|replace <Sample PayloadDate>]]

752

753

**6.Edit project Files**

754

755

The project file needs to be modified when the user needs to test or add a new decoder, feel invited to switch to the “Code” section of the AWS Lambda function and inspect the Python source code. You will find the decoders for the individual devices in the directory decoders. The AWS Lambda function handler is in file **app.py**

756

757

Users can find the required decoder in this **[[link>>url:https://github.com/aws-samples/aws-iot-core-lorawan/tree/main/transform_binary_payload]], **then added to the project.

758

759

How to modify see the figure below:

(% class="box" %)

(((

1) Add a decoder in app.py ~-~--> For example, add code: import dragino_lht52

764

765

2) Add the decoder name to "VALID_PAYLOAD_DECODER_NAMES" ~-~--> add dragino_lht52

766

767

3) Add the statement ~-~--> DECODER_NAME = "dragino_lht52"

768

769

**(The user can input the decoding project that needs to be tested)**

770

771

4)Comment out "DECODER_NAME = os.environ.get("DECODER_NAME")"

772

773

**(Comment out it in order to use other project files)**

774

)))

775

776

[[image:image-20220525094832-3.png||height="276" width="627"]]

777

778

After the user finishes editing, Click on the **"Deploy"**

**7. Run a test**

Please click on **“Test”**.

783

784

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

785

786

**8. Check whether the decoding succeeds **

787

788

The following example is the successful decoding of LHT52,

789

790

[[image:image-20220525100532-4.png||height="488" width="612"]]

791

792

**9. Note the AWS Lamdbda function ARN**

793

794

(((

795

As a preparation for the next step, please note the ARN of the deployed AWS Lambda function. We will need this ARN later to review the created AWS IoT Rule.

796

)))

797

798

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

799

800

=== 4.2.2 Step 2:Update the Destination rule and get the device's payload ===

801

802

In this step, you update the IoT rule that forwards the device payload to your application. This rule is associated with the destination created earlier in Set up a Destination for device traffic.

803

804

(((

805

~1. Find the IoT Rule

806

807

2. Create a Destination with IoT Rule (MyWorkshopLoRaWANRuleWithDecoder_dragino_lht65)

808

809

3. Update the destination to the device

4. Check the payload

5. Approach A with MQTT

814

815

6. Approach B with Lambda

816

)))

817

818

==== 4.2.2.1 1. Find the IoT Rule MyWorkshopLoRaWANRuleWithDecoder_… ====

819

820

Please put the IoT Rule name prefix **MyWorkshopLoRaWANRuleWithDecoder_** into the search field and click on the search symbol. The rule named **MyWorkshopLoRaWANRuleWithDecoder_<Decoder name>** should appear:

821

822

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

Find the IoT rule

==== 4.2.2.2 2. Create a Destination with IoT Rule ====

827

828

(MyWorkshopLoRaWANRuleWithDecoder_dragino_lht65)

829

830

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

Create a Destnation

==== 4.2.2.3 3. Update the destination to the device ====

836

837

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

838

839

Update the destination to the device

840

841

842

==== 4.2.2.4 4.Check the payload ====

843

844

**Approach A with MQTT**

click the rule

[[image:image-20220525184325-18.png]]

click the rule

Copy the Topic name

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

copy the rule name

Open MQTT client and subscrlibe Topic

861

862

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

863

864

Open MQTT client and subscrlibe Topic

Get the payload

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

Get the payload

**Approach B with Lamdbda**

875

876

open lamdbda console and click the application

877

878

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

879

880

open lamdbda console and click the application

881

882

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

883

884

open lamdbda console and click the application

885

886

View logs in CloudWatch

887

888

[[image:image-20220525183907-15.png]]

889

890

View logs in CloudWatch

891

892

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

893

894

View logs in CloudWatch

895

896

== 4.3 Approach B Create an AWS Lambda function that sends a text message ==

897

898

The AWS Lambda function in this tutorial receives the result of the rule query statement, inserts the elements into a text string, and sends the resulting string to Amazon SNS as the message in a notification.

899

900

=== 4.3.1 Step.1: To create an AWS Lambda function that sends a text message ===

901

902

==== 4.3.1.1 1.Create a new AWS Lambda function. ====

903

904

**a.** In the [[AWS Lambda console>>url:https://console.aws.amazon.com/lambda/home]], choose Create function.

905

906

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

Create function

(((

**b.** In Create function, select Use a blueprint. Search for and select the hello-world-python blueprint, and then choose **Configure**.

912

)))

913

914

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

blueprint

**c. **In Basic information:

(% class="box" %)

(((

1). In Function name, enter the name of this function, format-high-temp-notification.

923

2). In Execution role, choose Create a new role from AWS policy templates.

924

3). In Role name, enter the name of the new role, format-high-temp-notification-role.

925

4). In Policy templates - optional, search for and select Amazon SNS publish policy.

926

5). Choose Create function.

927

)))

928

929

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

blueprint

==== 4.3.1.2 2.Modify the blueprint code to format and send an Amazon SNS notification. ====

935

936

(((

937

**a.** After you created your function, you should see the format-high-temp-notification details page. If you don't, open it from the Lambda Functions page.

)))

(((

**b.** In the format-high-temp-notification details page, choose the Configuration tab and scroll to the Function code panel.

)))

(((

**c. **In the Function code window, in the Environment pane, choose the Python file, lambda_function.py.

)))

(((

**d.** In the Function code window, delete all of the original program code from the blueprint and replace it with this code.

)))

(% class="box" %)

(((

from ~_~_future~_~_ import print_function

955

import json

956

import boto3

957

print('Loading function')

958

def lambda_handler(event, context):

959

# Parse the JSON message

960

eventText = json.dumps(event)

961

# Print the parsed JSON message to the console. You can view this text in the Monitoring tab in the AWS Lambda console or in the Amazon CloudWatch Logs console.

962

print('Received event: ', eventText)

963

# Create an SNS client

964

sns = boto3.client('sns')

965

# Publish a message to the specified topic

966

response = sns.publish (

967

TopicArn = 'arn:aws:iam::123456789012:My_IoT_SNS_Topic',

Message = eventText

)

print(response)

)))

**e.** Choose Deploy.

974

975

**Note: **Replace the value of **TopicArn** with the ARN of the Amazon SNS topic that you created SNS topic in which [[SNS>>url:https://console.aws.amazon.com/sns/home?region=us-east-1]]

976

977

**Note: **If you don't have SNS topic it does't affect the use of Lambda.About how to Create SNS topic will be show next chapter

978

979

980

==== 4.3.1.3 3.In a new window, look up the Amazon Resource Name (ARN) of your Amazon SNS topic from the tutorial about how to Send an Amazon SNS notification. ====

981

982

(((

983

**a. **In a new window, open the Topics page of the Amazon SNS console

)))

(((

**b.** In the Topics page, find the high_temp_notice notification topic in the list of Amazon SNS topics.

)))

(((

**c.** Find the ARN of the high_temp_notice notification topic to use in the next step.

)))

==== 4.3.1.4 4.Create a test case for your Lambda function. ====

997

998

**a.** In the Lambda Functionspage of the console,from **Select a test event**to select Configure test events

999

1000

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

1001

1002

Configure test events

(((

**b. **On Configure test event, enter a name for your test event and replace the message JSON with the following:

)))

(% class="box" %)

(((

{

"message" : "Hello, world"

}

)))

**c.** choose Create

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

event create

(((

**d. **In the upper right of the Lambda function details page, choose Test to test your Lambda function with the message you specified in the test event.

1025

)))

1026

1027

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

event test

**e.** Under your Lambda function code, on the Execution result tab, you see the output from the Lambda function.

1033

1034

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

event output

Now The Lambda function table is created

1039

1040

=== 4.3.2 Step.2: Create Rule with Lambda function ===

1041

1042

**~1. **Browse to the AWS IoT console, and in the navigation pane, select **Act**

1043

1044

[[File:Console Act.png>>url:https://wiki.dragino.com/index.php?title=Special:Upload&wpDestFile=Console_Act.png]]

(% class="box" %)

(((

console_Act

)))

**2. **Choose Create to create an AWS IoT rule.

1052

1053

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

create Rule

**3.** On the Create a rule page, enter a name for your rule.

1058

1059

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

enter a Rule name

**4.** In Rule query statement, enter the following query:

(% class="box" %)

(((

SELECT * FROM "my/lambda/topic"

1068

)))

1069

1070

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

1071

1072

enter the following query

1073

1074

**5.** In Set one or more actions, select Add action.

1075

1076

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

Add action

**6.** Under the select operation, select Send a Message to a Lambda Function and then select the configuration operation.

1081

1082

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

select operation

= 5. For End Node =

== 5.1 AWS Downlink Note ==

1089

1090

Prerequisites: The node must be online in real-time before downlink.

1091

1092

[[image:image-20220525113243-2.png||height="346" width="623"]]

1093

1094

Convert the data to Base64

1095

1096

[[image:image-20220525113612-3.png||height="377" width="622"]]

1097

1098

When the serial port logs of downlink are received, the Receive date is displayed

1099

1100

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

1101

1102

In addition to the above methods, there is also a downlink,This method requires a certain amount of manipulation,

1103

1104

Users can view this [[Downlink method 2>>url:https://github.com/aws-samples/aws-iot-core-lorawan/tree/main/send_downlink_payload]]

1105

1106

== 5.2 Node decoder ==

1107

1108

[[Decode LHT65>>url:https://github.com/aws-samples/aws-iot-core-lorawan/tree/main/transform_binary_payload]]

= 6. Reference =

* [[Video Introduction for how to use LoRaWAN AWS-IoT Core>>url:https://www.youtube.com/watch?v=eKK0M8iC6l4]]

1113

* [[AWS LoRaWAN Workshop>>url:https://iotwireless.workshop.aws/]]

Wiki source code of Notes for AWS-IoT-Core

Applications

Navigation