Connect to nRF cloud using eSIM.

[Stas Jis]

We are using nRF9160 chip (in own custom board), SDK 1.9.1 board with "serial lte modem" firmware.
We are unable to get coordinates using AGPS.
I suppose this is due to the fact that the eSIM needs to be somehow registered on the nRF Cloud.
We used the sequence of commands from the "GNSS_AT_commands" example:

  AT%XSYSTEMMODE=1,0,1,0

  OK
  AT%XCOEX0=1,1,1565,1586

  OK
  AT+CPSMS=1

  OK
  AT+CFUN=1

  OK
  AT#XNRFCLOUD=1

  OK

  AT#XAGPS=1,1
  ERROR
  
  AT#XNRFCLOUD?
  #XNRFCLOUD: 0,0,16842753,"nrf-350916060695718" 

But there is no connection to the nRF cloud. eSIM is already used to upload / unload  data via MQTT using AT commands, so the SIM card is working.

[Stas Jis]

We need to have access to the nRF cloud in the device to work with AGPS, and we also work separately with an Amazon broker to unload / upload data.
Since we installed certificates and keys to communicate with Amazon in our custom board, we cannot reach the nRF Cloud.
Is there any way to check that we have not removed the certificates needed for nRF clouds (with the tag 16842753)?

You also say that on custom devices (with nrf9160) not need use nrf-<IMEI> for cloud registration, but any attempts to register devices fail (Code 40412).

Is there a sequence of actions required to add a user device to the nRF cloud?

Now any attempt to connect to the cloud gives the result:

AT#XNRFCLOUD=1
OK

#XNRFCLOUD: 0,0

#XNRFCLOUD: 0,0

AT#XNRFCLOUD?

#XNRFCLOUD: 0,0,654321,"nrf-350916060695718"

OK

[Øyvind]

Stas Jis said:

You also say that on custom devices (with nrf9160) not need use nrf-<IMEI> for cloud registration, but any attempts to register devices fail (Code 40412).

Yes, so when you have generated the certificates the device still needs to connect to nRF Cloud once. Usually this is done by running e.g. Asset Tracker v2, which will give you the prompt in the LTE Link Monitor that the device is ready to be provisioned. From here you should be able to add the device to nRF Cloud. 

This can be more cumbersome adding one and one, so adding the device using Preconnect provisioning might be better. You can also add multiple devices using the Provisioning Devices in nRF Cloud where you can upload a .csv file that has information to multiple devices.

As the JITP certification generator states: 

Certificates are used to provision a device on nRF Cloud. There are two certificate types: non-JITP and JITP. Please read about these types and cloud-provisioning. If you are certain you want to use a JITP certificate, use the form below. In most cases, however, it is better to generate your own certificates and provision your devices using the Provision Devices endpoint, as explained in the guide.

[Øyvind]

Our nRF Cloud team has provided the following information:

The first AT#XNRFCLOUD=1 command initiates the connection to the cloud. on the initial connection, the JITP step is performed and nRF Cloud immediately disconnects the device, hence the #XNRFCLOUD: 0,0 responses.

At this point the user should associate the device with their account, the UI on the cloud will spin and/or time out.

Send another connect attempt from SLM: AT#XNRFCLOUD=1 and it should connect properly.

Refresh the device page on nRF Cloud and they should see the device listed.