nRF Cloud Provisioning Service

[Bard]

Hi 

I'm trying to use the nRF Cloud Provisioning Service with the nRF Cloud multi-service sample in SDK 2.6 on a nRF9151DK.

I have got the token from the device using AT%ATTESTTOKEN and claimed the device in nRF Cloud

Then I compiled the sample with 

-DEXTRA_CONF_FILE="overlay-http_nrf_provisioning.conf"

But the provisioning is not ok...What am I missing?

[00:00:00.256,439] <inf> spi_nor: gd25wb256e3ir@1: 32 MiBy flash
*** Booting nRF Connect SDK v3.5.99-ncs1 ***
[00:00:00.259,643] <inf> main: iAMP-Hydro has started, version: 1.0.2, protocol: MQTT
[00:00:00.259,704] <inf> cloud_connection: Enabling connectivity...
[00:00:00.544,769] <inf> cloud_connection: Setting up nRF Cloud library...
[00:00:00.725,860] <inf> cloud_connection: Waiting for network ready...
[00:00:05.010,375] <inf> cloud_connection: Network connectivity gained!
[00:00:06.010,589] <inf> cloud_provisioning: Initializing the nRF Provisioning library...
[00:00:06.010,833] <inf> cloud_connection: Network is ready
[00:00:07.050,079] <inf> cloud_provisioning: Provisioning is active.
[00:00:07.152,038] <inf> nrf_provisioning_http: Requesting commands
[00:00:09.535,980] <inf> nrf_provisioning_http: Connected
[00:00:09.536,010] <inf> nrf_provisioning_http: No more commands to process on server side
[00:00:14.536,102] <inf> cloud_provisioning: Provisioning is idle.
[00:00:14.536,163] <inf> cloud_connection: Connecting to nRF Cloud
[00:00:14.536,224] <inf> cloud_connection: Device ID: 50333648-3230-48f5-xxxx-xxxxxxxxxxx
[00:00:18.436,676] <err> nrf_cloud_transport: MQTT input error: -128
[00:00:18.436,737] <err> nrf_cloud_transport: Error disconnecting from cloud: -128
[00:00:18.436,798] <inf> cloud_connection: Disconnecting from nRF Cloud
[00:00:18.436,828] <err> cloud_connection: Could not connect to nRF Cloud
[00:00:18.436,828] <inf> cloud_connection: Retrying in 30 seconds...

Bård

[Mariano Goluboff]

Did you create a provisioning configuration as detailed in Step 4 of the Process section?

From the log, it looks like the provisioning firmware connected but had no steps to provision.

[Bard]

Could you list the minimum required commands to add to a rule in order to provision a device? I don't know what is needed. How to install CA Certificate?

[00:00:02.480,010] <err> nrf_cloud_credentials: CA Certificate not found in sec tag 16842753
[00:00:02.480,041] <wrn> cloud_connection: nRF Cloud credentials are not installed. Claim and onboard device on nrfcloud.com to continue.

I have claimed the device using token.

[Mariano Goluboff]

When you claim the device, there is a button to "Create new rule for onboarding to nRF Cloud". You can use that to create a provisioning rule that does the defaults.

What it creates is two requests:

- Cloud Access Key Generation

- Server Certificate

If you didn't do that when claiming the device, you can create the provisioning rule in Security Services->Provisioning Rules. Add the commands above, then assign it to a group of claimed devices.

See more information on that here:

docs.nordicsemi.com/.../GettingStarted.html

[Bard]

Hi

When I try to do the above, this dialog appears:

What to write in the Content field?

[Bard]

I unclaimed the device and entered the commands above when reclaiming. Now it works :-) BUT I still get these messages every minute:

[01:04:03.238,281] <inf> cloud_provisioning: Provisioning is active.
[01:04:03.340,118] <inf> nrf_provisioning_http: Requesting commands
[01:04:06.536,895] <inf> nrf_provisioning_http: Connected
[01:04:06.536,926] <inf> nrf_provisioning_http: No more commands to process on server side
[01:04:11.537,017] <inf> cloud_provisioning: Provisioning is idle.
[01:05:07.537,750] <inf> cloud_provisioning: Provisioning is active.
[01:05:07.639,587] <inf> nrf_provisioning_http: Requesting commands
[01:05:09.404,327] <inf> nrf_provisioning_http: Connected
[01:05:09.404,357] <inf> nrf_provisioning_http: No more commands to process on server side
[01:05:14.404,479] <inf> cloud_provisioning: Provisioning is idle.

How to complete provisioning? (not active/idle)