NRFCloud not accepting nrf9160 DK connection

RE: NRFCloud not accepting nrf9160 DK connection

Albrecht Markus Schellenberger — Fri, 25 Jun 2021 05:38:57 GMT

Thanks a lot for the feedback, Eric! I’m glad to hear that you could resolve this issue.

Cheers,

Markus

RE: NRFCloud not accepting nrf9160 DK connection

Eric S. — Thu, 24 Jun 2021 16:52:12 GMT

Hello Marcus,

Finally I am now connected to nrfCloud with the nrf9160 DK. Deleting the certificates and re-installing did the trick (along with getting the Hologram SIM). This ticket can be closed.

Thank you

Eric Scheidemantel

RE: NRFCloud not accepting nrf9160 DK connection

Albrecht Markus Schellenberger — Thu, 24 Jun 2021 07:55:36 GMT

Thanks for the feedback, Eric!

Instead of resetting the device in the nRF Could, could you just remove it and create new certificates afterwards. Before downloading them to the device, I would recommend you to delete all remaining certificates using the %CMNG AT command.

The following command example deletes a client certificate with tag 123:
AT%CMNG=3,123,1 OK

You can add the device again afterwards following this procedure.

Before running the Asset Tracker, you might wanna run through the AT client Testing procedure and check if your device can connect to the network without any problems.

I hope this will solve your problem!

Regards,

Markus

RE: NRFCloud not accepting nrf9160 DK connection

Eric S. — Wed, 23 Jun 2021 15:57:02 GMT

Hello Markus,

6/23/2021

Thanks for getting back to me.

LED1 and LED4 are blinking simultaneously at about 1 blink/second. (Note, not LED3 and LED4 as your tutorial video shows) If you refer to the log I posted above you will see that the nrf9160 DK connects with the cellular network, then attempts to connect with the nrfCloud but is unsuccessful and then the nrf9160 DK modem shuts down. The error message shows that I have the wrong certificates but I have reloaded them many times and loaded them, per your suggestion, with the ATclient and with double checking the security tag number.

I am still not able to add the board as an LTE device since it looks like it will not connect to the nrfCloud.

Best Regards

Eric Scheidemantel

RE: NRFCloud not accepting nrf9160 DK connection

Albrecht Markus Schellenberger — Wed, 23 Jun 2021 07:52:52 GMT

Hello again Eric,

if the device identification was entered correctly, the device is probably not connected the nRF Cloud. See, “Observe that the LED(s) indicate that the device is waiting for user association."

It has to be, otherwise you won’t be able to add the device. Could you double-check this?

Thanks and regards,

Markus

RE: NRFCloud not accepting nrf9160 DK connection

Albrecht Markus Schellenberger — Mon, 21 Jun 2021 07:08:23 GMT

Thanks for the feedback, Eric! I have to cross-check on this one with our nRF Cloud team. I will come back to you.

Regards,

Markus

RE: NRFCloud not accepting nrf9160 DK connection

Eric S. — Fri, 18 Jun 2021 17:39:07 GMT

Hello Marcus, Thank you for the response however your suggestions did not work. I suspect the problem is that I cannot add the LTE device in the nrfCloud. I had the nrf9160 dk previously added to my nrfCloud account but I did a "Reset a Device" in the nrfCloud to remove the board so i could update the certificate. However I now get an error message in the nrfCloud when I try to add the nrf9160 DK as an LTE device. The nrfCloud error message is: "There was an error adding your device: No device found for this id. The device has not yet been provisioned. Troubleshoot nRF Code 40412.

I have double checked that I did enter the device ID correctly with nrf- in front of it and double checked that the HWID: was entered properly.(I did use the colon separator but should not make a difference).

Your comments are appreciated.

Eric Scheidemantel

RE: NRFCloud not accepting nrf9160 DK connection

Albrecht Markus Schellenberger — Fri, 18 Jun 2021 07:57:14 GMT

Hello Eric,

2021-06-18T04:00:21.992Z DEBUG modem << [00:00:04.739,929] [1;31m<err> asset_tracker: Ensure device has a valid CA and client certificate[0m

might indicate that there is something wrong with your certificate.

You can cross-check the sec_tag by using AT%CMNG=1. As the LTE Link Monitor Certifcate Manager states: “Use security tag 16842753 to manage nRF Connect for Cloud certificate."

You might wanna update your nRF Connect for Cloud Certificate one more time. I would recommend you to use the AT Client instead of the Asset Tracker for certificate updates, since this application is very simple and does not do other things in parallel.

Afterwards, you can follow these steps for testing.

Maybe it could be helpful as well to remove your existing device from the nRF Cloud and add it one more time.

I hope this will help you!

Regards,

Markus