With some difficulty I have managed to provision a nrf9160 feather on nrfCloud, device feather-3526………..
To get that done I had flashed cloud_client sample (plus CONFIG_BOOTLOADER_MCUBOOT=y) and was online with a working SIM while provisioning. I used the PIN code that came with the feather.
But I can’t get the cloud_client sample to connect to nrfCloud. I get “cloud_connect, error -11”.
I have tried setting the MQTT client id to feather-3526…….. but same problem.
Any ideas?

very odd, it works now. Maybe a delay at nordic with the registration. I used the following in the prj.conf
CONFIG_NRF_CLOUD_CLIENT_ID_SRC_COMPILE_TIME=y
CONFIG_NRF_CLOUD_CLIENT_ID=“feather-3526………..”

    intelcomdk all nRF9160 Feathers come pre-provisioned for nRF Cloud and use the passcode 1337. You can always open up your LTE Link Monitor and run AT%CMNG=1 in AT mode (at_client is a good sample for that). This will list all the current certificates that are active on the device. It will not show the contents for security reasons though.

    If you re-provisioned, you’ll have to use the appropriate password you used during the API call to set the device up.

    Also, very important, the device will not fully provision until you attempt to connect (which appears what you’ve done). Make sure though that your SIM is active and you have a good network connection.

    I hope that helps!

    Thank you! As you can tell I did get it working by myself. I did not change the certificates.
    But having to set the CLIENT_ID is not funny. It would be nicer to just set CONFIG_NRF_CLOUD_CLIENT_ID_SRC_IMEI=y but that does not work (require a setting change at nrfCloud I assume? (to change the expected mqtt client id to be a plain EMEI))
    I am using nrfCloud for test only for now, I don’t think I will use nrfCloud for anything in production.
    sending data (a json) from nrfcloud to the feather works perfect. Pressing the button to upload a json to nrfCloud is not 100% reliable. I don’t know if this is related to the wake up from RRC mode idle, or just a problem with the nrfcloud web interface. Do you know?

    Hmm I haven’t played with nRF Cloud in a long while. It could be a slew of different things. Sorry I don’t have as much useful insight here.

    ok thanks. Have you worked with eSIM? I noticed that the nrf9160DK has room for it (and the thingy91 according to the doc.s)

    It should work just as a regular SIM. I haven’t seen any other differences besides the physical differences.

    Terms and Conditions | Privacy Policy