Can I add our custom nrf9160 to nrf Cloud?

[Stratosphere]

Hi, 

Most of the posts I have seen are related to adding nrf DK or thingy to nrf cloud. Is there any way to add custom nrf9160 devices to nrf Cloud? Is nrf Cloud even meant for handling 1000s of devices in production?

Regards

Noaman

[flau]

Hi Øyvind,

The COM port issue is resolved.  So I followed your instructures and downloaded the new certificate onto my board.  I also added the 2 CONFIG_NRF_CLOUD_CLIENT_ID into the prj.conf.  However, I couldn't add my device in the nrf Cloud.  I kept getting "There was an error adding your device: No device found for this id. The device has not yet been provisioned. Troubleshoot nRF Code 40412".  How can I resolve this?  Thank you.

Regards,

Floyd

[Øyvind]

Hi Floyd, 

The device needs to run e.g. Asset Tracker v2 with the correct device ID and use the certificates you added (sec_tag), then follow the instructions provided in the link you pasted:

40412

No device found for this id. The device has not yet been provisioned.

The device cannot be found in the device registry, i.e., it is not 'known' by the IoT cloud platform. Possible reasons: You entered the device id and/or ownership code (PIN or HWID) incorrectly. Before attempting association, you did not wait for the LEDs to indicate the device was provisioned. Corrupt modem firmware. Corrupt, wrongly flashed, or illegitimate device certificates. Poor LTE connection

Solutions that match the possible reasons are listed here. For items 2-4, refer to the nRF9160 DK Getting Started Guide or Thingy:91 Getting Started Guide. Verify the values and try again. For Nordic Semiconductor products, please see the solution for nRF Code 40411, above. Check the LED status indicators to ensure the device indicates it was provisioned. (Re-)flash the latest modem firmware. Flash new device certificates obtained from the CreateDeviceCertificate endpoint. Move to a location with a better LTE connection.