NRFCloud not accepting nrf9160 DK connection

[Eric S.]

I started a new ticket since I got a solution to not connecting to the cellular network. Apparently the iBasis sim is not working so I acquired a Hologram sim. I now can connect to the cellular network but the nrfcloud will not allow connection to the nrf9160 DK board. (see log below). I reflashed the asset tracker firmware, the modem firmware and created new certificates and successfully loaded the certificates into the nrf9160 DK.  I then installed the Hologram SIM. I also did a "reset device" in the NRFCloud before I generated the certificates since I did have this board working and connecting last July. 

I would appreciate any suggestions.

Following are the hardware software specifics I have.

nrf9160 DK  Hardware: PCA10090, 0.9.0,  2019 19

Asset tracker firmware: "\Nordic\nrf9160dk_fw_2021-03-01_8e8c6089\img_app_bl\nrf9160dk_asset_tracker_ltem_2021-03-01_8e8c6089.hex"

Modem Firmware: "\Nordic\nrf9160dk_fw_2021-03-01_8e8c6089\mfwnrf9160123.zip"

NRFConnect Programmer: v1.4.11

NRFConnect LTE Link Monitor: v1.1.10

Log file:

2021-06-18T04:00:19.297Z DEBUG modem << [00:00:02.062,957] [0m<inf> asset_tracker: RRC mode: Connected[0m
2021-06-18T04:00:19.994Z DEBUG modem << +CEREG: 5,"800B","07551811",7,,,"11100000","11100000"
2021-06-18T04:00:20.005Z DEBUG modem << [00:00:02.766,754] [0m<inf> asset_tracker: Connected to LTE network.[0m
2021-06-18T04:00:20.064Z DEBUG modem << [00:00:02.773,345] [0m<inf> asset_tracker: Connecting to cloud, attempt 1 of 8[0m
2021-06-18T04:00:20.067Z DEBUG modem << [00:00:02.780,731] [0m<inf> asset_tracker: Cloud connection request sent.[0m
2021-06-18T04:00:20.070Z DEBUG modem << [00:00:02.787,658] [0m<inf> asset_tracker: Connection response timeout is set to 30 seconds.[0m
2021-06-18T04:00:20.073Z DEBUG modem << [00:00:02.796,325] [0m<inf> asset_tracker: Network registration status: Connected - roaming[0m
2021-06-18T04:00:20.076Z DEBUG modem << [00:00:02.804,779] [0m<inf> asset_tracker: PSM parameter update: TAU: -1, Active time: -1[0m
2021-06-18T04:00:20.079Z DEBUG modem << [00:00:02.813,201] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING[0m
2021-06-18T04:00:20.081Z DEBUG modem << [00:00:02.821,655] [0m<inf> asset_tracker: CLOUD_EVT_CONNECTING[0m
2021-06-18T04:00:20.923Z DEBUG modem << [00:00:03.688,995] [0m<dbg> nrf_cloud_transport.nct_connect: IPv4 address: 52.201.133.155[0m
2021-06-18T04:00:20.959Z DEBUG modem << [00:00:03.697,296] [0m<dbg> nrf_cloud_transport.nct_mqtt_connect: MQTT clean session flag: 1[0m
2021-06-18T04:00:20.962Z DEBUG modem << [00:00:03.714,111] [0m<inf> asset_tracker: DATE_TIME_OBTAINED_NTP[0m
2021-06-18T04:00:21.944Z DEBUG modem << [00:00:04.709,289] [0m<dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect failed -95[0m
2021-06-18T04:00:21.982Z DEBUG modem << [00:00:04.717,620] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING[0m
2021-06-18T04:00:21.984Z DEBUG modem << [00:00:04.726,104] [0m<inf> asset_tracker: CLOUD_EVT_CONNECTING[0m
2021-06-18T04:00:21.990Z DEBUG modem << [00:00:04.732,177] [1;31m<err> asset_tracker: Failed to connect to cloud, error -8[0m
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
2021-06-18T04:00:22.029Z DEBUG modem << [00:00:04.748,992] [1;31m<err> asset_tracker: Device will reboot in 300 seconds[0m
2021-06-18T04:00:22.032Z DEBUG modem << [00:00:04.756,469] [1;31m<err> asset_tracker: LTE link disconnect[0m
2021-06-18T04:00:22.090Z DEBUG modem << +CEREG: 0,"800B","07551811",7,0,0,"11100000","11100000"
2021-06-18T04:00:23.651Z DEBUG modem << +CSCON: 0
2021-06-18T04:00:23.685Z DEBUG modem << [00:00:06.425,415] [0m<inf> asset_tracker: RRC mode: Idle[0m
2021-06-18T04:00:23.899Z DEBUG modem << [00:00:06.667,022] [1;31m<err> asset_tracker: Shutdown modem[0m

[Albrecht Markus Schellenberger]

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

[Eric S.]

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