Custome NRF9151 is not able to be provisioned to NRF cloud

RE: Custome NRF9151 is not able to be provisioned to NRF cloud

Pascal Hdz — Mon, 11 Aug 2025 08:06:25 GMT

I will proceed to close the ticket, please open a new one in case you face a new challenge.

Pascal.

RE: Custome NRF9151 is not able to be provisioned to NRF cloud

Pascal Hdz — Wed, 06 Aug 2025 08:55:24 GMT

Hello,

It is good that you managed to onboard your device but JITP is not something we recommend. This will be soon deprecated, our recommendation will be to use nRF Cloud Utils.

Pascal.

RE: Custome NRF9151 is not able to be provisioned to NRF cloud

Audiblemaple — Tue, 05 Aug 2025 18:08:50 GMT

Hi Pascal,

Yes I was able to provision using the JITP however I will also take a look at the utils repositiry Link you provided.
I have not had a chance to look at it as we are restricted with time.

I will publish here a full explaination on how I got it working since Im sure many people are facing the same issues I did.
Hopefully I will get to it soon.

Thanks for the support.

Best regards,
Lior

RE: Custome NRF9151 is not able to be provisioned to NRF cloud

Pascal Hdz — Tue, 05 Aug 2025 13:55:31 GMT

Hello,

Were you able to onboard your devices using nRF Cloud Utils?

Pascal.

RE: Custome NRF9151 is not able to be provisioned to NRF cloud

Pascal Hdz — Mon, 28 Jul 2025 17:57:48 GMT

Hello,

JITP is no longer recommended as the way to onboard the nRF91 products. Instead could you install nRF Cloud Utils from this repo:
https://github.com/nRFCloud/utils
And follow the instructions in the README.

Please let me know if you have any other question.

Pascal.

RE: Custome NRF9151 is not able to be provisioned to NRF cloud

Menon — Thu, 24 Jul 2025 13:34:15 GMT

Hello,

Sorry for getting back to you a bit late, it's summer vacation here in Norway, and only a few people are working. That's why it's taking longer to respond to this issue.

I'm not able to access (or see) the image you shared. It's throwing a "not found" error when I try to open or click on it. Could you please share it once more?

Kind regards,
Abhijith

RE: Custome NRF9151 is not able to be provisioned to NRF cloud

Audiblemaple — Tue, 22 Jul 2025 19:52:26 GMT

Quick update:

After using: CONFIG_NRF_CLOUD_CLIENT_ID_SRC_INTERNAL_UUID=y in order to use the modem UUID as the client ID for nrf cloud.
I did the provisioning in nrf cloud again using:

Device ID: 5034474b-3731-4f56-8079-210df3998f26
PIN/HWID: 5034474b-3731-4f56-8079-210df3998f26

Writing it again using certificate manager.

I got it to work ONCE and got my location, after this it stopped wotrking, I did not change anything.
you can see in the image that it got the location once in nrf cloud (hope the image works..):

devzone.nordicsemi.com/.../'Screenshot from 2025-07-22 22-49-59.png'

Log of the successful run attached:

*** Booting MCUboot v2.1.0-dev-bf852c9bb388 ***
*** Using nRF Connect SDK v3.0.0-3bfc46578e42 ***
*** Using Zephyr OS v4.0.99-3e0ce7636fa6 ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 0, Swap type: none
I: Bootloader chainload address offset: 0x10000
I: Image version: v0.0.0
*** Booting nRF Connect SDK v3.0.0-3bfc46578e42 ***
*** Using Zephyr OS v4.0.99-3e0ce7636fa6 ***
[00:00:00.260,681] <inf> nrf_cloud_rest_cell_location_sample: nRF Cloud REST Cellular Location Sample, version: 1.0.0
[00:00:00.623,352] <inf> nrf_cloud_rest_cell_location_sample: Device ID: 5034474b-3731-4f56-8079-210df3998f26
[00:00:00.640,594] <inf> nrf_cloud_rest_cell_location_sample: Using LTE LC neighbor search type GCI extended complete for 5 cells
[00:00:00.652,862] 00:00:00.654,907] <dbg> nrf_cloud_rest_cell_location_sample: app_event_handler: Button pressed
m<inf> nrf_cloud_rest_cell_location_sample: ---> Press button 0 to request just-in-time provisioning (JITP)
[00:00:00.674,072] <inf> nrf_cloud_rest_cell_location_sample: This only needs to be done once per device
[00:00:00.684,722] <inf> nrf_cloud_rest_cell_location_sample: Waiting 10 seconds...
[00:00:00.693,634] <inf> nrf_cloud_rest_cell_location_sample: JITP will be performed after network connection is obtained
[00:00:00.826,629] <inf> nrf_cloud_credentials: Sec Tag: 16842753; CA: Yes, Client Cert: Yes, Private Key: Yes
[00:00:00.837,310] <inf> nrf_cloud_credentials: CA Size: 1187, AWS: Likely, CoAP: Unlikely
[00:00:00.846,221] <inf> nrf_cloud_rest_cell_location_sample: Waiting for network...
+CEREG: 2,"5E9E","00436201",7
[00:00:01.952,239] <dbg> nrf_cloud_rest_cell_location_sample: lte_handler: LTE_LC_EVT_NW_REG_STATUS: 2
+CSCON: 1
[00:00:02.007,080] <inf> nrf_cloud_rest_cell_location_sample: RRC mode: connected
+CEREG: 5,"5E9E","00436201",7,,,"11100000","11100000"
[00:00:06.692,596] <dbg> nrf_cloud_rest_cell_location_sample: lte_handler: LTE_LC_EVT_NW_REG_STATUS: 5
[00:00:06.702,301] <dbg> nrf_cloud_rest_cell_location_sample: lte_handler: Network registration status: Connected - roaming
[00:00:06.713,989] <inf> nrf_cloud_rest_cell_location_sample: Connected to network
[00:00:06.722,076] <inf> nrf_cloud_rest_cell_location_sample: Waiting for modem to acquire network time...
[00:00:09.741,882] <inf> nrf_cloud_rest_cell_location_sample: Network time obtained
[00:00:09.750,030] <inf> nrf_cloud_rest_cell_location_sample: Performing JITP...
[00:00:19.018,005] <inf> nrf_cloud_rest_cell_location_sample: Device already provisioned
[00:00:19.032,989] <inf> nrf_cloud_info: Device ID: 5034474b-3731-4f56-8079-210df3998f26
[00:00:19.042,236] <inf> nrf_cloud_info: IMEI: 359404230490956
[00:00:19.167,236] <inf> nrf_cloud_info: UUID: 5034474b-3731-4f56-8079-210df3998f26
[00:00:19.176,330] <inf> nrf_cloud_info: Modem FW: mfw_nrf91x1_2.0.2
[00:00:19.183,380] <inf> nrf_cloud_info: Protocol: REST
[00:00:19.189,971] <inf> nrf_cloud_info: Download protocol: HTTPS
[00:00:19.196,655] <inf> nrf_cloud_info: Sec tag: 16842753
[00:00:19.203,613] <inf> nrf_cloud_info: Host name: api.nrfcloud.com
[00:00:23.023,040] <inf> nrf_cloud_rest_cell_location_sample: Device status sent to nRF Cloud
[00:00:23.032,257] <inf> nrf_cloud_rest_cell_location_sample: Getting current cell info...
[00:00:23.050,781] <inf> nrf_cloud_rest_cell_location_sample: Current cell info: Cell ID: 4416001, TAC: 24222, MCC: 425, MNC: 7
[00:00:23.063,079] <inf> nrf_cloud_rest_cell_location_sample: Performing single-cell request
[00:00:23.072,265] <inf> nrf_cloud_rest_cell_location_sample: Request configuration:
[00:00:23.080,688] <inf> nrf_cloud_rest_cell_location_sample: High confidence interval = false
[00:00:23.090,332] <inf> nrf_cloud_rest_cell_location_sample: Fallback to rough location = true
[00:00:23.099,945] <inf> nrf_cloud_rest_cell_location_sample: Reply with result = true
[00:00:24.035,827] <inf> nrf_cloud_rest_cell_location_sample: Cellular location request fulfilled with single-cell
[00:00:24.046,844] <inf> nrf_cloud_rest_cell_location_sample: Lat: 32.850623, Lon: 35.101383, Uncertainty: 774
+CSCON: 0
[00:00:34.852,386] <inf> nrf_cloud_rest_cell_location_sample: RRC mode: idle

RE: Custome NRF9151 is not able to be provisioned to NRF cloud

Audiblemaple — Tue, 22 Jul 2025 12:42:42 GMT

Hi Abhijith,

Thanks for your prompt response.
However, As stated before, CA, cert and private key were generated with NRF cloud as a json file and written to the modem using the nrf desktop certificate manager.
So nothing I can do wrong here, the 9151-DK was provisioned the same way and worked, so process was verified.

Anything else i can try?
Specific naming for Device ID or HWID, should I put the SIM pin there maybe?

Thanks,
Lior

RE: Custome NRF9151 is not able to be provisioned to NRF cloud

Menon — Tue, 22 Jul 2025 12:28:28 GMT

Hello,

See the error code here. Ensure you are generating a valid JWT on the device, using the correct private key that matches the public key registered with nRF Cloud. Please go through the following documents:

Kind Regards,

Abhijith

RE: Custome NRF9151 is not able to be provisioned to NRF cloud

Audiblemaple — Tue, 22 Jul 2025 07:15:17 GMT

Edit:

Just noticed that I did not explicitly state what the exact issue is, we get the REST error msg: Auth token is malformed. error followed by REST error code 40100

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian