nRF Cloud Provisioning Service

RE: nRF Cloud Provisioning Service

Mariano Goluboff — Fri, 13 Dec 2024 14:02:53 GMT

To use Device ID and PIN, you need to use JITP to onboard the device. That is a different process than the Auto-Onboarding, and you should only do one or the other.

A DK already comes with JITP done by Nordic, whereas for your own custom board, you have to do that yourself. JITP is not the recommended way for mass production, you should use either Auto-Onboarding or Preconnect onboarding.

More details here:

docs.nordicsemi.com/.../Onboarding.html

RE: nRF Cloud Provisioning Service

Bard — Thu, 12 Dec 2024 08:44:05 GMT

This works. But the device still start provisioning at regular intervals. Is there a way to disable the service after a time interval?

I have a nRF9151DK that I provisioned using DeviceID and Pin. I tried the same with a custom board using DeviceID and HWID, but got this error:

Is it possible to provision custom boards this way? If so, why the error? Do I need to download a certificate, or is it present in all nrf9151 SOC's?

RE: nRF Cloud Provisioning Service

Mariano Goluboff — Wed, 11 Dec 2024 21:06:03 GMT

It will help to get a complete log of the application, to understand what is going on at the firmware level. Also, any changes in configuration from the defaults.

I just re-read in your original message that you are using 2.6. In SDK 2.6.0, the default of the sample is to check once per minute if there's a change in provisioning. See the following in overlay-hittp_nrf_provisioning.conf:

# Set the provisioning interval to 60 seconds.
# This is a very frequent interval. To save power, set this to something approaching 24 hours.
# But note that provisioning may take up to twice as long as this interval, since it
# happens in two steps.
CONFIG_NRF_PROVISIONING_INTERVAL_S=60

So you might want to change CONFIG_NRF_PROVISIONING_INTERVAL_S to a different value.

If you are able to move to SDK 2.8.0, the provisioning library has a new API: nrf_provisioning_set_interval(). This is used in the nRF Cloud Multi Service sample to change the provisioning interval to a much longer interval after the initial provisioning is complete. The new interval is set with CONFIG_POST_PROVISIONING_INTERVAL_M.

RE: nRF Cloud Provisioning Service

Bard — Wed, 11 Dec 2024 15:47:35 GMT

I added Finished to Provisioning Configuration like this:

but Provisioning is still active/idle. Have I added it correctly?

RE: nRF Cloud Provisioning Service

Mariano Goluboff — Wed, 11 Dec 2024 14:58:09 GMT

To complete provisioning, add the Provisioning Command called "Finished".

RE: nRF Cloud Provisioning Service

Mariano Goluboff — Wed, 11 Dec 2024 14:57:34 GMT

I see below that you have it working. But for anybody else reading this thread, what you need there is the AWS CA certificate. That gets auto-populated when using the "Create new rule for onboarding to nRF Cloud" button.

RE: nRF Cloud Provisioning Service

Bard — Wed, 11 Dec 2024 14:19:25 GMT

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)

RE: nRF Cloud Provisioning Service

Bard — Wed, 11 Dec 2024 12:21:56 GMT

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

What to write in the Content field?

RE: nRF Cloud Provisioning Service

Mariano Goluboff — Wed, 11 Dec 2024 12:02:50 GMT

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

RE: nRF Cloud Provisioning Service

Bard — Wed, 11 Dec 2024 11:32:46 GMT

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.

RE: nRF Cloud Provisioning Service

Mariano Goluboff — Tue, 10 Dec 2024 17:41:29 GMT

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.