Difficulty Provisioning Thingy91 to AWS IoT Fleet Provisioning (Claim Method)

Dear Team,

I am attempting to provision my Thingy91 device to AWS IoT Core using Fleet Provisioning with the Claim method. I've been closely following the instructions in the repository "https://github.com/NordicPlayground/aws-iot-core-fleet-provisioning-with-nrf9160".

Here's a breakdown of my progress and where I'm facing issues:

Steps Completed:

  1. Certificate and Key Generation: Successfully generated a provisioning certificate and private key.
  2. Connectivity Test: Established a connection with AWS IoT Core using the generated certificate and key with the "Fleet-Provisioning-for-AWS-IoT-embedded-sdk" project. I was able to receive the provisioning certificate and the private key when running the fleet_provisioning_keys_cert demo (running natively on Ubuntu).

Issue: I'm unable to complete the Fleet Provisioning process with the claim method when using the same generated credentials with Thingy91. I'm unsure where the issue lies within the provisioning flow.

Device and Software Details:

  • Device: Thingy91
  • Modem Firmware Version: v1.3.5
  • nRF Connect SDK Version: v2.5.2

Could you kindly help recommend known issues or specific configuration steps I might be missing in the Fleet Provisioning flow for the Thingy91. I would like to attach the project config file, log message console and the modem trace that I collected from the RTT. Thank you in advance for your expertise and assistance.

Sincerely,
Thuan.

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
#
# Copyright (c) 2020 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
# General config
CONFIG_NCS_SAMPLES_DEFAULTS=y
CONFIG_REBOOT=y
# NEWLIB C
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
# Network
CONFIG_NETWORKING=y
CONFIG_NET_NATIVE=n
# LTE link control
CONFIG_LTE_LINK_CONTROL=y
# Prioritise NB-IoT
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20:50:19:877 -> �*** Booting nRF Connect SDK v2.5.2 ***
20:50:21:021 -> I: AWS-IoT <-> UART bridge, app version: v1.0.0
20:50:21:255 -> I: Trace thread ready
20:50:21:299 -> I: Trace level override: 2
20:50:21:301 -> I: Subscribed to uplink/2024203/accepted and uplink/2024203/rejected
20:50:23:909 -> +CEREG: 2,"B03D","07CB1E15",9
20:50:23:909 -> I: LTE cell changed: Cell ID: 130752021, Tracking area: 45117
20:50:24:302 -> +CSCON: 1
20:50:24:302 -> I: RRC mode: Connected
20:50:25:840 -> +CEREG: 1,"B03D","07CB1E15",9,,,"11100000","11100000"
20:50:25:840 -> I: Network registration status: Connected - home network
20:50:25:840 -> I: PSM parameter update: TAU: 3240, Active time: -1
20:50:25:866 -> %XTIME: "82","42301231055282","00"
20:50:25:866 -> I: Date time obtained
20:50:25:866 -> I: Next connection retry in 30 seconds
20:50:36:124 -> +CSCON: 0
20:50:36:124 -> I: RRC mode: Idle
20:50:55:868 -> I: Next connection retry in 30 seconds
20:51:25:894 -> I: Next connection retry in 30 seconds
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
0728.RTTLogger_Channel_modem_trace.log