Nrf cloud unknown pre onboarding status issue

Hello,

I am facing an issue with nRF Cloud device provisioning. I am using the nrfcloud-util tool to provision the device to nRF Cloud (as recommended for production provisioning).

From the logs (attached from both the device and nrfcloud-util), the device successfully connects to nRF Cloud. However, in the nRF Cloud Device Portal, the device status does not change from “Unknown (Pre-Onboarding)”.

According to DevZone, the possible reasons could be:

  • Incorrect device ID 

  • Device not provisioned correctly

  • Certificate mismatch

In my case:

  • Device ID is correct

  • Provisioning is successful (logs confirm the device connects to nRF Cloud)

  • Certificates are valid (device connection proves this)

References:

  • Attached: device debug logs and device ID(wheelchair-351901930694181)

  • Hardware: nRF9160 DK

  • Sample: nRF Cloud Multi-Service sample

  • Currently testing with DK, but will use custom PCB later, so provisioning via nrfcloud-util must work reliably.

Issue:
Device remains in “Unknown (Pre-Onboarding)” state in nRF Cloud despite successful provisioning and connection.

Request:
Need guidance/solution for why the device status is not updating and how to resolve this issue.

kind Regards

Akbar Shah

[00:00:19.279,754] <dbg> message_queue: consume_device_message: Consuming an enqueued device message
[00:00:19.279,815] <inf> CLOUD_CONNECTIVITY: Enabling connectivity...
[00:00:19.283,630] <inf> CLOUD_CONNECTIVITY: Setting up nRF Cloud library...
[00:00:19.285,583] <inf> nrf_cloud_info: Device ID: wheelchair-351901930694181
[00:00:19.286,163] <inf> nrf_cloud_info: IMEI:      351901930694181
[00:00:19.286,560] <inf> nrf_cloud_info: Modem FW:  mfw_nrf9160_1.3.5
[00:00:19.286,621] <inf> nrf_cloud_info: Protocol:          MQTT
[00:00:19.286,651] <inf> nrf_cloud_info: Download protocol: HTTPS
[00:00:19.286,651] <inf> nrf_cloud_info: Sec tag:           16842753
[00:00:19.286,682] <inf> nrf_cloud_info: Host name:         mqtt.nrfcloud.com
[00:00:19.413,543] <inf> nrf_cloud_credentials: Sec Tag: 16842753; CA: Yes, Client Cert: Yes, Private Key: Yes
[00:00:19.413,635] <inf> nrf_cloud_credentials: CA Size: 1208, AWS: Likely, CoAP: Unlikely
[00:00:19.413,635] <inf> CLOUD_CONNECTIVITY: Waiting for network ready...
+CGEV: ME PDN ACT 0,0
+CNEC_ESM: 50,0
%MDMEV: SEARCH STATUS 2
+CEREG: 5,"B8CE","032AB903",7,,,"00001111","11100000"
[00:00:20.008,239] <inf> lte_manager: Network registration status: Connected - roaming
%XTIME: "80","52809240856180","01"
[00:00:20.008,758] <inf> CLOUD_CONNECTIVITY: Network connectivity gained!
[00:00:20.066,070] <inf> lte_manager: PSM parameter update: Periodic TAU: 4680 s, Active time: 30 s
[00:00:21.008,972] <inf> CLOUD_CONNECTIVITY: Network is ready
[00:00:21.009,002] <inf> CLOUD_CONNECTIVITY: Connecting to nRF Cloud
[00:00:21.009,063] <dbg> CLOUD_CONNECTIVITY: cloud_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING
[00:00:23.098,754] <dbg> CLOUD_CONNECTIVITY: cloud_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED
[00:00:23.098,815] <inf> CLOUD_CONNECTIVITY: Connected to nRF Cloud
[00:00:23.098,846] <dbg> CLOUD_CONNECTIVITY: start_readiness_timeout: Starting cloud connection readiness timeout for 600 seconds
[00:00:23.098,876] <dbg> CLOUD_CONNECTIVITY: cloud_connection_thread_fn: Monitoring nRF Cloud connection
[00:00:23.601,165] <dbg> CLOUD_CONNECTIVITY: cloud_event_handler: NRF_CLOUD_EVT_RX_DATA_SHADOW
[00:00:23.601,165] <dbg> CLOUD_CONNECTIVITY: handle_shadow_event: Shadow: Accepted
[00:00:23.601,196] <inf> shadow_config: Sending reported configuration
[00:00:23.652,557] <dbg> CLOUD_CONNECTIVITY: cloud_event_handler: NRF_CLOUD_EVT_USER_ASSOCIATED
[00:00:23.949,432] <dbg> CLOUD_CONNECTIVITY: cloud_event_handler: NRF_CLOUD_EVT_RX_DATA_SHADOW
[00:00:23.949,462] <dbg> CLOUD_CONNECTIVITY: handle_shadow_event: Shadow: Delta - version: 600, timestamp: 1756443501
[00:00:24.048,004] <dbg> CLOUD_CONNECTIVITY: cloud_event_handler: NRF_CLOUD_EVT_USER_ASSOCIATED
[00:00:24.506,927] <dbg> CLOUD_CONNECTIVITY: cloud_event_handler: NRF_CLOUD_EVT_READY
[00:00:24.506,927] <dbg> CLOUD_CONNECTIVITY: clear_readiness_timeout: Stopping cloud connection readiness timeout
[00:00:24.506,988] <inf> application: Waiting for modem to determine current date and time
[00:00:24.506,988] <inf> application: Current date and time determined
[00:00:24.507,324] <inf> NVS_HELPER: Geofence read from NVS: enabled=0, lat=0.000000, lon=0.000000, radius=0.00

[00:00:24.507,354] <dbg> NRFCLOUD_LOCATION: start_location_tracking: Starting location tracking
[00:00:24.507,598] <dbg> CLOUD_CONNECTIVITY: cloud_ready: Setting CLOUD_READY
[00:00:24.507,659] <inf> nrf_cloud_info: Team ID:   51fe210d-99e6-4850-9804-275fdb1a28d7
[00:00:24.507,904] <dbg> NRFCLOUD_LOCATION: start_location_tracking: Selected the GNSS location tracking method.
[00:00:24.507,934] <dbg> NRFCLOUD_LOCATION: start_location_tracking: Selected the Cellular location tracking method.
+CSCON: 0
[00:00:38.069,427] <inf> lte_manager: RRC mode: idle
[00:01:04.558,929] <inf> location: Method specific timeout expired
[00:01:04.558,959] <wrn> location: GNSS timed out possibly due to too short GNSS time windows
[00:01:04.559,539] <inf> location: Location retrieval failed using 'GNSS', trying with 'Cellular' next
%NCELLMEAS: 0,"032AB903","26202","B8CE",17,6300,73,69,28,63949,36455
%NCELLMEAS: 0,"032AB903","26202","B8CE",17,36455,6300,73,69,28,63949,1,0
%NCELLMEAS: 0,"032AB903","26202","B8CE",17,36455,6300,73,69,28,68109,1,0,"02814201","26201","63A1",65535,0,1300,357,42,28,68228,0,0
%MDMEV: SEARCH STATUS 2
+CSCON: 1
[00:01:09.379,241] <inf> lte_manager: RRC mode: connected
[00:01:10.470,977] <inf> location: LOCATION_REQ_MODE_ALL: all methods done
[00:01:10.471,038] <inf> NRFCLOUD_LOCATION: Location Event: Got location
[00:01:10.471,099] <inf> application: Location Updated: 48.861354 N 9.178880 W, accuracy: 293.0 m, Method: Cellular

Disabling LTE and GNSS...
INFO     Device IMEI: 351901930694181
INFO     Modem FW version: mfw_nrf9160_1.3.5
INFO     Deleting sectag 16842753...
INFO     Generating private key and requesting a CSR for sectag 16842753...
INFO     Parsing AT%KEYGEN output:
INFO     -----BEGIN CERTIFICATE REQUEST-----\nMIIBADCBpQIBADAlMSMwIQYDVQQDDBp3aGVlbGNoYWlyLTM1MTkwMTkzMDY5NDE4\nMTBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABKo3T6JPhGp1VxksXUZyhaFvLeya\nRYiyqzLMqEbsyUxbpzj2bH3zN+eEnphsBytetrrpeRrmQWbclmumFI73y82gHjAc\nBgkqhkiG9w0BCQ4xDzANMAsGA1UdDwQEAwID6DAMBggqhkjOPQQDAgUAA0gAMEUC\nICmz+pYyDqRGkLiyp7szfsiWFa9XhF0AAV0lcrLAmO0cAiEAzsux3r3Pwra5sTsJ\nz5Elu/A8OXhOYSH0ZY1T/oRy6y8=\n-----END CERTIFICATE REQUEST-----\n
INFO     Device public key: -----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEqjdPok+EanVXGSxdRnKFoW8t7JpF\niLKrMsyoRuzJTFunOPZsffM354SemGwHK162uul5GuZBZtyWa6YUjvfLzQ==\n-----END PUBLIC KEY-----\n
INFO     SHA256 Digest: 265720fcb1992e5560c196d424c6b65444e7180e8673b28eb897dd901642bcbf
INFO     * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
INFO     COSE:
INFO       Prot Hdr:   1 : -7 (ECDSA w/ SHA-256)
INFO       Unprot Hdr: 4 : -2 (identity_key)
INFO       ---------------
INFO       Attestation:
INFO         Payload ID: CSR_msg_v1
INFO         Dev UUID:   504b5839-3736-4411-8081-162786ad4057
INFO         sec_tag:    16842753
INFO         SHA256:     265720fcb1992e5560c196d424c6b65444e7180e8673b28eb897dd901642bcbf
INFO         Nonce:      c81d0e7396f2ea0a821b769074b6dd79
INFO       ---------------
INFO       Sig:
INFO           4102862dc01b54773fc061b6d369c5b009bbb1e63f2db565d2384d4a752fb846af84c07f1818ced1a720dac9c63598fb8c34b0e8adaf4afeb533ea8dfc05914e
INFO     COSE digest matches payload
INFO     * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
INFO     Device ID: wheelchair-351901930694181
INFO     Loading CA and key...
INFO     Creating device certificate...
INFO     Writing CA cert(s) to device...
INFO     Writing dev cert to device...
INFO     Verifying credentials...
INFO     Verifying CA Cert
INFO     Verifying Client Cert
INFO     Verifying Private Key
WARNING  Private Key exists, SHA not verified
INFO     Credential verification: PASS
INFO     Saving nRF Cloud device onboarding CSV file onboard.csv...
INFO     Onboarding CSV file saved, row count: 1
INFO     Devices to be onboarded: 1
INFO     Onboarding API call result: 202 - Accepted
INFO     Fetching results for bulkOpsRequestId: 01K3T30NKZPVHGTMK4G3T08ESR
INFO     Waiting 5s...
INFO     Onboarding status: SUCCEEDED
INFO     CSV-formatted results:
INFO     bulkOpsRequestId,01K3T30NKZPVHGTMK4G3T08ESR
endpoint,ONBOARD_DEVICES
status,SUCCEEDED
requestedAt,2025-08-29T04:57:45.343Z
completedAt,2025-08-29T04:57:48.566Z
uploadedDataUrl,https://bulk-ops-requests.nrfcloud.com/51fe210d-99e6-4850-9804-275fdb1a28d7/onboard_devices/01K3T30NKZPVHGTMK4G3T08ESR.csv
Error count,0

Device ID,Result
wheelchair-351901930694181,OK

Related