No connection to nRF cloud (Attempts to use AGPS)

RE: No connection to nRF cloud (Attempts to use AGPS)

justin — Sun, 10 Apr 2022 21:59:49 GMT

Please review this guide:
https://docs.nrfcloud.com/Guides/GettingStarted/Devices

There are two type of provisioning: JITP and "pre-connect". If you are downloading credentials from nrfcloud.com then you are doing JITP. I have described JITP in my previous reply. Pre-connect provisioning is what custom/manufactured devices would use.

Your device must have credentials installed into a sec tag in the modem. This includes: the amazon root CA, device certificate(s) and device private key. Your FW application (CONFIG_NRF_CLOUD_SEC_TAG) must use the sec tag containing those credentials. The sec tag is only for your device, the cloud does not know or care about the sec tag.

For JITP credentials, using LTE Link Monitor's Certificate Manager is the easiest way to do this. It will parse the credentials from the downloaded JSON file and send them to the device in the correct format. Before updating the credentials, you must send the AT command: AT+CFUN=4 to deactivate the modem.

RE: No connection to nRF cloud (Attempts to use AGPS)

Stas Jis — Sun, 10 Apr 2022 11:47:13 GMT

Dear justin_nordic,
You said:
Next, the device must be associated with your account (AWS tenant). This step cannot be done unless the device is provisioned with the cloud. If you attempt to associate a device that is not provisioned, you will get error 40412. Once associated, the device will successfully connect to the cloud.

What exactly is required to prepare a device for adding to the nRF cloud?
I've been trying to get at least one of the two devices (nRF9160 DK, Custom Board) to no avail for two weeks now.

RE: No connection to nRF cloud (Attempts to use AGPS)

justin — Thu, 07 Apr 2022 16:44:33 GMT

i see you have another active ticket for this provisioning issue, so i won't continue that here.
but i will explain briefly how JITP works and why you are getting 40412.
here are the steps:

1. First, the device must be provisioned with AWS/nRF Cloud. This means that there is a record of your device and its certificate on the cloud. For a device with JITP credentials, the provisioning step happens automatically when the device first connects to the cloud. The cloud will immediately disconnect the device while it performs provisioning.

2. Next, the device must be associated with your account (AWS tenant). This step cannot be done unless the device is provisioned with the cloud. If you attempt to associate a device that is not provisioned, you will get error 40412. Once associated, the device will successfully connect to the cloud.

note: the sec tag, credentials, and device id must be consistent throughout these steps.

RE: No connection to nRF cloud (Attempts to use AGPS)

Stas Jis — Thu, 07 Apr 2022 06:55:45 GMT

justin_nordic:
Your device has been removed from the old account.
I still can't add device to nRF cloud, error - Code 40412.

RE: No connection to nRF cloud (Attempts to use AGPS)

justin — Wed, 06 Apr 2022 16:33:15 GMT

Ah, ok, that is expected. A device can only belong to one account at a time.
Your device has been removed from the old account.
You should be able to add the device to a new account now.

If the device has JITP (the default) certs in 16842753, nRF Cloud (AWS) will disconnect the device on the first connection attempt so it can do provisioning. The device will need to then reconnect and you can associate the device with your account.

You can also look into using the nRF Cloud "Teams" feature: https://docs.nrfcloud.com/Reference/Teams
It might be useful if you have multiple users.

RE: No connection to nRF cloud (Attempts to use AGPS)

Stas Jis — Wed, 06 Apr 2022 08:38:33 GMT

justin:

How can we return the default certificates for nRF Cloud with the tag (16842753 )?

RE: No connection to nRF cloud (Attempts to use AGPS)

Stas Jis — Wed, 06 Apr 2022 08:34:48 GMT

justin,
did you use sec tag 321 when you added your device to nrf cloud? if so, rebuild your serial LTE modem application with:

No, I'm having problems registering the device (gives error 40101).
This board was previously registered by our former employee, and we were unable to access his account. Can we somehow transfer the device to my profile?

RE: No connection to nRF cloud (Attempts to use AGPS)

justin — Tue, 05 Apr 2022 16:47:32 GMT

the modem sec tags allow you to have credentials for multiple servers.
so if you used 321 for AWS IoT and kept 16842753 for nrf cloud, there shouldn't be a problem.

did you use sec tag 321 when you added your device to nrf cloud? if so, rebuild your serial LTE modem application with:
CONFIG_NRF_CLOUD_SEC_TAG=321

If that isn't the solution, deleting the device from nrf cloud and re-provisioning with the correct credentials should work.

RE: No connection to nRF cloud (Attempts to use AGPS)

Stas Jis — Tue, 05 Apr 2022 11:45:13 GMT

justin,

Have you changed or deleted the credentials in the modem sec_tag 16842753?

The problem may be related to the fact that before that we installed our certificates to communicate with the Amazon MQTT Broker (in this evaluation board)?
Used commands:
AT%CMNG=0,321,0,-----BEGIN CERTIFICATE-----\n"....
AT%CMNG=0,321,1,-----BEGIN CERTIFICATE-----\n" ...
AT%CMNG=0,321,2,-----BEGIN EC PRIVATE KEY-----\n" ...

RE: No connection to nRF cloud (Attempts to use AGPS)

Stas Jis — Tue, 05 Apr 2022 07:00:07 GMT

justin,
Have you changed or deleted the credentials in the modem sec_tag 16842753?

No, we didn't do anything like that.
I am attaching the results of the AT%CMNG=1 command:

2022-04-05T06:55:56.140Z DEBUG modem >> AT%CMNG=1
2022-04-05T06:55:56.155Z DEBUG modem << %CMNG: 0,0,"0000000000000000000000000000000000000000000000000000000000000000"
2022-04-05T06:55:56.169Z DEBUG modem << %CMNG: 0,1,"0101010101010101010101010101010101010101010101010101010101010101"
2022-04-05T06:55:56.186Z DEBUG modem << %CMNG: 0,2,"0202020202020202020202020202020202020202020202020202020202020202"
2022-04-05T06:55:56.195Z DEBUG modem << %CMNG: 0,6,"0606060606060606060606060606060606060606060606060606060606060606"
2022-04-05T06:55:56.205Z DEBUG modem << %CMNG: 123,0,"0000000000000000000000000000000000000000000000000000000000000000"
2022-04-05T06:55:56.215Z DEBUG modem << %CMNG: 123,1,"0101010101010101010101010101010101010101010101010101010101010101"
2022-04-05T06:55:56.222Z DEBUG modem << %CMNG: 123,2,"0202020202020202020202020202020202020202020202020202020202020202"
2022-04-05T06:55:56.233Z DEBUG modem << %CMNG: 321,0,"0000000000000000000000000000000000000000000000000000000000000000"
2022-04-05T06:55:56.241Z DEBUG modem << %CMNG: 321,1,"0101010101010101010101010101010101010101010101010101010101010101"
2022-04-05T06:55:56.250Z DEBUG modem << %CMNG: 321,2,"0202020202020202020202020202020202020202020202020202020202020202"
2022-04-05T06:55:56.254Z DEBUG modem << %CMNG: 325,0,"0000000000000000000000000000000000000000000000000000000000000000"
2022-04-05T06:55:56.268Z DEBUG modem << %CMNG: 325,1,"0101010101010101010101010101010101010101010101010101010101010101"
2022-04-05T06:55:56.276Z DEBUG modem << %CMNG: 325,2,"0202020202020202020202020202020202020202020202020202020202020202"
2022-04-05T06:55:56.283Z DEBUG modem << %CMNG: 696,0,"0000000000000000000000000000000000000000000000000000000000000000"
2022-04-05T06:55:56.291Z DEBUG modem << %CMNG: 696,1,"0101010101010101010101010101010101010101010101010101010101010101"
2022-04-05T06:55:56.299Z DEBUG modem << %CMNG: 696,2,"0202020202020202020202020202020202020202020202020202020202020202"
2022-04-05T06:55:56.313Z DEBUG modem << %CMNG: 757,0,"0000000000000000000000000000000000000000000000000000000000000000"
2022-04-05T06:55:56.320Z DEBUG modem << %CMNG: 757,1,"0101010101010101010101010101010101010101010101010101010101010101"
2022-04-05T06:55:56.325Z DEBUG modem << %CMNG: 757,2,"0202020202020202020202020202020202020202020202020202020202020202"
2022-04-05T06:55:56.334Z DEBUG modem << %CMNG: 1234,0,"0000000000000000000000000000000000000000000000000000000000000000"
2022-04-05T06:55:56.339Z DEBUG modem << %CMNG: 1234,1,"0101010101010101010101010101010101010101010101010101010101010101"
2022-04-05T06:55:56.346Z DEBUG modem << %CMNG: 1234,2,"0202020202020202020202020202020202020202020202020202020202020202"
2022-04-05T06:55:56.363Z DEBUG modem << %CMNG: 1684,0,"0000000000000000000000000000000000000000000000000000000000000000"
2022-04-05T06:55:56.370Z DEBUG modem << %CMNG: 1684,1,"0101010101010101010101010101010101010101010101010101010101010101"
2022-04-05T06:55:56.379Z DEBUG modem << %CMNG: 1684,2,"0202020202020202020202020202020202020202020202020202020202020202"
2022-04-05T06:55:56.385Z DEBUG modem << %CMNG: 16842753,0,"0000000000000000000000000000000000000000000000000000000000000000"
2022-04-05T06:55:56.389Z DEBUG modem << %CMNG: 16842753,1,"0101010101010101010101010101010101010101010101010101010101010101"
2022-04-05T06:55:56.397Z DEBUG modem << %CMNG: 16842753,2,"0202020202020202020202020202020202020202020202020202020202020202"
2022-04-05T06:55:56.403Z DEBUG modem << %CMNG: 4294967293,10,"0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A"
2022-04-05T06:55:56.417Z DEBUG modem << %CMNG: 4294967292,11,"0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B"
2022-04-05T06:55:56.423Z DEBUG modem << OK

RE: No connection to nRF cloud (Attempts to use AGPS)

justin — Mon, 04 Apr 2022 18:40:19 GMT

Great, thanks!

nrf_cloud_transport.nct_mqtt_connect: mqtt_connect failed -111
nrf_cloud.nfsm_set_current_state_and_notify: state: 1
nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING
slm_gnss.cloud_event_handler: CLOUD_EVT_CONNECTING: status -9

mqtt_connect returned a ECONNREFUSED error.
This usually indicates an issue with the device credentials.
Have you changed or deleted the credentials in the modem sec_tag 16842753?
To list the installed credentials, can use the AT command: AT%CMNG=1

you should see:

%CMNG: 16842753,0,"0000000000000000000000000000000000000000000000000000000000000000"

%CMNG: 16842753,1,"0101010101010101010101010101010101010101010101010101010101010101"

%CMNG: 16842753,2,"0202020202020202020202020202020202020202020202020202020202020202"

I believe at this point your options are:

1. Delete your device from your nRF Cloud account and then re-provision it to ensure the credentials are correct. See https://docs.nrfcloud.com/Reference/DeviceManagement/Provisioning. I assume you used the JITP method since this is a DK. You can re-download new JITP certs from nRF Cloud or you can create your own and use the pre-connect provisioning method.
https://docs.nrfcloud.com/Guides/GettingStarted/Devices

2. If you are confident your credentials are correct: capture modem traces and inspect via wireshark to see why the MQTT connection fails.
https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_trace_collector%2FUG%2Ftrace_collector%2Fintro.html

RE: No connection to nRF cloud (Attempts to use AGPS)

Stas Jis — Mon, 04 Apr 2022 06:43:17 GMT

justin,
I added to the code what you asked for, I am attaching the result:

[00:01:05.608,154] [0m<dbg> slm_gnss.cloud_event_handler: CLOUD_EVT_CONNECTING: status -9

2022-04-04T06:39:16.705Z DEBUG modem << Ready
2022-04-04T06:39:16.718Z DEBUG modem << [00:00:00.221,405] [0m<inf> slm: Serial LTE Modem[0m
2022-04-04T06:39:16.760Z DEBUG modem << [00:00:00.228,424] [0m<dbg> slm_at_host.slm_at_host_init: UART baud: 115200 d/p/s-bits: 3/0/1 HWFC: 1[0m
2022-04-04T06:39:16.766Z DEBUG modem << [00:00:00.228,424] [0m<dbg> slm_at_host.slm_uart_configure: Set uart baudrate to: 115200, hw flow control 1[0m
2022-04-04T06:39:16.768Z DEBUG modem << [00:00:00.244,903] [0m<dbg> nrf_cloud_transport.nct_client_id_set: client_id = nrf-352656108600480[0m
2022-04-04T06:39:16.781Z DEBUG modem << [00:00:00.245,605] [0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656108600480/shadow/get/accepted[0m
2022-04-04T06:39:16.795Z DEBUG modem << [00:00:00.245,635] [0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656108600480/shadow/get/re~[0m
2022-04-04T06:39:16.812Z DEBUG modem << [00:00:00.245,635] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656108600480/shadow/update~[0m
2022-04-04T06:39:16.822Z DEBUG modem << [00:00:00.245,697] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: <log_strdup alloc failed>[0m
2022-04-04T06:39:16.837Z DEBUG modem << [00:00:00.245,697] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: <log_strdup alloc failed>[0m
2022-04-04T06:39:16.848Z DEBUG modem << [00:00:00.245,727] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 1[0m
2022-04-04T06:39:16.853Z DEBUG modem << [00:00:00.245,849] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:16.868Z DEBUG modem <<                                       52 65 61 64 79 0d 0a                             |Ready..          [0m
2022-04-04T06:39:16.879Z DEBUG modem << [00:00:00.245,941] [0m<dbg> slm_fota.slm_fota_post_process: FOTA result 0,0,0[0m
2022-04-04T06:39:16.885Z DEBUG modem << [00:00:00.252,777] [0m<inf> slm_at_host: at_host init done[0m
2022-04-04T06:39:18.987Z DEBUG modem >> AT
2022-04-04T06:39:18.998Z DEBUG modem << OK
2022-04-04T06:39:19.996Z DEBUG modem << [00:00:02.531,982] [0m<dbg> slm_at_host: RX
2022-04-04T06:39:20.009Z DEBUG modem <<                                       41 54                                            |AT               [0m
2022-04-04T06:39:20.015Z DEBUG modem << [00:00:02.538,604] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:20.032Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:39:20.035Z DEBUG modem << [00:00:02.538,635] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:20.050Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-04T06:39:21.371Z DEBUG modem >> AT+CFUN?
2022-04-04T06:39:21.382Z DEBUG modem << +CFUN: 0
2022-04-04T06:39:21.394Z DEBUG modem << OK
2022-04-04T06:39:22.379Z DEBUG modem << [00:00:04.915,802] [0m<dbg> slm_at_host: RX
2022-04-04T06:39:22.395Z DEBUG modem <<                                       41 54 2b 43 46 55 4e 3f                          |AT+CFUN?         [0m
2022-04-04T06:39:22.402Z DEBUG modem << [00:00:04.916,290] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-04T06:39:22.408Z DEBUG modem << [00:00:04.922,424] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:22.422Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:39:22.429Z DEBUG modem << [00:00:04.922,454] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:22.441Z DEBUG modem <<                                       2b 43 46 55 4e 3a 20 30  0d 0a 4f 4b 0d 0a       |+CFUN: 0 ..OK..  [0m
2022-04-04T06:39:30.548Z DEBUG modem >> AT%XSYSTEMMODE=1,0,1,0
2022-04-04T06:39:30.563Z DEBUG modem << OK
2022-04-04T06:39:31.558Z DEBUG modem << [00:00:14.095,367] [0m<dbg> slm_at_host: RX
2022-04-04T06:39:31.572Z DEBUG modem <<                                       41 54 25 58 53 59 53 54  45 4d 4d 4f 44 45 3d 31 |AT%XSYST EMMODE=1
2022-04-04T06:39:31.585Z DEBUG modem <<                                       2c 30 2c 31 2c 30                                |,0,1,0           [0m
2022-04-04T06:39:31.594Z DEBUG modem << [00:00:14.095,855] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-04T06:39:31.600Z DEBUG modem << [00:00:14.103,424] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:31.613Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:39:31.619Z DEBUG modem << [00:00:14.103,454] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:31.632Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-04T06:39:36.251Z DEBUG modem >> AT%XMAGPIO=1,0,0,1,1,1574,1577
2022-04-04T06:39:36.264Z DEBUG modem << OK
2022-04-04T06:39:37.263Z DEBUG modem << [00:00:19.799,560] [0m<dbg> slm_at_host: RX
2022-04-04T06:39:37.279Z DEBUG modem <<                                       41 54 25 58 4d 41 47 50  49 4f 3d 31 2c 30 2c 30 |AT%XMAGP IO=1,0,0
2022-04-04T06:39:37.289Z DEBUG modem <<                                       2c 31 2c 31 2c 31 35 37  34 2c 31 35 37 37       |,1,1,157 4,1577  [0m
2022-04-04T06:39:37.303Z DEBUG modem << [00:00:19.800,048] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-04T06:39:37.306Z DEBUG modem << [00:00:19.806,396] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:37.322Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:39:37.327Z DEBUG modem << [00:00:19.806,457] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:37.342Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-04T06:39:42.266Z DEBUG modem >> AT%XCOEX0
2022-04-04T06:39:42.278Z DEBUG modem << OK
2022-04-04T06:39:43.276Z DEBUG modem << [00:00:25.813,812] [0m<dbg> slm_at_host: RX
2022-04-04T06:39:43.290Z DEBUG modem <<                                       41 54 25 58 43 4f 45 58  30                      |AT%XCOEX 0       [0m
2022-04-04T06:39:43.298Z DEBUG modem << [00:00:25.814,300] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-04T06:39:43.308Z DEBUG modem << [00:00:25.820,495] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:43.323Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:39:43.327Z DEBUG modem << [00:00:25.820,526] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:43.339Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-04T06:39:47.394Z DEBUG modem >> AT+CEREG=5
2022-04-04T06:39:47.407Z DEBUG modem << OK
2022-04-04T06:39:48.404Z DEBUG modem << [00:00:30.940,826] [0m<dbg> slm_at_host: RX
2022-04-04T06:39:48.417Z DEBUG modem <<                                       41 54 2b 43 45 52 45 47  3d 35                   |AT+CEREG =5      [0m
2022-04-04T06:39:48.427Z DEBUG modem << [00:00:30.941,314] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-04T06:39:48.433Z DEBUG modem << [00:00:30.947,448] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:48.445Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:39:48.450Z DEBUG modem << [00:00:30.947,479] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:48.464Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-04T06:39:52.619Z DEBUG modem >> AT+CPSMS=1
2022-04-04T06:39:52.630Z DEBUG modem << OK
2022-04-04T06:39:53.629Z DEBUG modem << [00:00:36.166,290] [0m<dbg> slm_at_host: RX
2022-04-04T06:39:53.642Z DEBUG modem <<                                       41 54 2b 43 50 53 4d 53  3d 31                   |AT+CPSMS =1      [0m
2022-04-04T06:39:53.650Z DEBUG modem << [00:00:36.166,778] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-04T06:39:53.657Z DEBUG modem << [00:00:36.172,943] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:53.670Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:39:53.675Z DEBUG modem << [00:00:36.172,973] [0m<dbg> slm_at_host: TX
2022-04-04T06:39:53.689Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-04T06:40:01.476Z DEBUG modem >> AT+CFUN=1
2022-04-04T06:40:01.526Z DEBUG modem << OK
2022-04-04T06:40:02.491Z DEBUG modem << [00:00:45.028,747] [0m<dbg> slm_at_host: RX
2022-04-04T06:40:02.506Z DEBUG modem <<                                       41 54 2b 43 46 55 4e 3d  31                      |AT+CFUN= 1       [0m
2022-04-04T06:40:02.513Z DEBUG modem << [00:00:45.029,235] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-04T06:40:02.519Z DEBUG modem << [00:00:45.068,969] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:02.533Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:40:02.543Z DEBUG modem << [00:00:45.069,000] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:02.553Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-04T06:40:02.893Z DEBUG modem << +CEREG: 2,"026F","00332521",7
2022-04-04T06:40:03.896Z DEBUG modem << [00:00:46.433,746] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:03.909Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:40:03.915Z DEBUG modem << [00:00:46.433,807] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:03.928Z DEBUG modem <<                                       2b 43 45 52 45 47 3a 20  32 2c 22 30 32 36 46 22 |+CEREG:  2,"026F"
2022-04-04T06:40:03.942Z DEBUG modem <<                                       2c 22 30 30 33 33 32 35  32 31 22 2c 37 0d 0a    |,"003325 21",7.. [0m
2022-04-04T06:40:04.591Z DEBUG modem << +CEREG: 5,"026F","00332521",7,,,"00011110","11100000"
2022-04-04T06:40:05.592Z DEBUG modem << [00:00:48.129,974] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:05.606Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:40:05.615Z DEBUG modem << [00:00:48.130,065] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:05.631Z DEBUG modem <<                                       2b 43 45 52 45 47 3a 20  35 2c 22 30 32 36 46 22 |+CEREG:  5,"026F"
2022-04-04T06:40:05.638Z DEBUG modem <<                                       2c 22 30 30 33 33 32 35  32 31 22 2c 37 2c 2c 2c |,"003325 21",7,,,
2022-04-04T06:40:05.664Z DEBUG modem <<                                       22 30 30 30 31 31 31 31  30 22 2c 22 31 31 31 30 |"0001111 0","1110                                      30 30 30 30 22 0d 0a                             |0000"..          [0m
2022-04-04T06:40:15.924Z DEBUG modem >> AT#XNRFCLOUD=1
2022-04-04T06:40:15.928Z DEBUG modem << OK
2022-04-04T06:40:16.933Z DEBUG modem << [00:00:59.471,496] [0m<dbg> slm_at_host: RX
2022-04-04T06:40:16.947Z DEBUG modem <<                                       41 54 23 58 4e 52 46 43  4c 4f 55 44 3d 31       |AT#XNRFC LOUD=1  [0m
2022-04-04T06:40:16.955Z DEBUG modem << [00:00:59.471,984] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-04T06:40:16.962Z DEBUG modem << [00:00:59.472,015] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:16.975Z DEBUG modem <<                                       0d 0a 4f 4b 0d 0a                                |..OK..           [0m
2022-04-04T06:40:16.988Z DEBUG modem << [00:00:59.472,137] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 1[0m
2022-04-04T06:40:16.999Z DEBUG modem << [00:00:59.472,137] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING[0m
2022-04-04T06:40:17.008Z DEBUG modem << [00:00:59.472,137] [0m<dbg> slm_gnss.cloud_event_handler: CLOUD_EVT_CONNECTING: status 0[0m
2022-04-04T06:40:17.021Z DEBUG modem << [00:00:59.927,124] [0m<dbg> nrf_cloud_transport.nct_connect: IPv4 address: 35.172.62.107[0m
2022-04-04T06:40:17.033Z DEBUG modem << [00:00:59.927,124] [0m<dbg> nrf_cloud_transport.nct_mqtt_connect: MQTT clean session flag: 1[0m
2022-04-04T06:40:23.075Z DEBUG modem << [00:01:05.608,123] [0m<dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect failed -111[0m
2022-04-04T06:40:23.086Z DEBUG modem << [00:01:05.608,154] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 1[0m
2022-04-04T06:40:23.100Z DEBUG modem << [00:01:05.608,154] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING[0m
2022-04-04T06:40:23.116Z DEBUG modem << [00:01:05.608,154] [0m<dbg> slm_gnss.cloud_event_handler: CLOUD_EVT_CONNECTING: status -9[0m
2022-04-04T06:40:28.614Z DEBUG modem << +CEREG: 5,"026F","00332520",7,,,"00011110","11100000"
2022-04-04T06:40:29.615Z DEBUG modem << [00:01:12.154,388] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:29.628Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:40:29.636Z DEBUG modem << [00:01:12.154,449] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:29.654Z DEBUG modem <<                                       2b 43 45 52 45 47 3a 20  35 2c 22 30 32 36 46 22 |+CEREG:  5,"026F"
2022-04-04T06:40:29.661Z DEBUG modem <<                                       2c 22 30 30 33 33 32 35  32 30 22 2c 37 2c 2c 2c |,"003325 20",7,,,
2022-04-04T06:40:29.687Z DEBUG modem <<                                       22 30 30 30 31 31 31 31  30 22 2c 22 31 31 31 30 |"0001111 0","1110                                      30 30 30 30 22 0d 0a                             |0000"..          [0m
2022-04-04T06:40:34.628Z DEBUG modem >> AT#XNRFCLOUD?
2022-04-04T06:40:34.639Z DEBUG modem << #XNRFCLOUD: 0,0,16842753,"nrf-352656108600480"
2022-04-04T06:40:34.640Z DEBUG modem << OK
2022-04-04T06:40:35.637Z DEBUG modem << [00:01:18.176,116] [0m<dbg> slm_at_host: RX
2022-04-04T06:40:35.650Z DEBUG modem <<                                       41 54 23 58 4e 52 46 43  4c 4f 55 44 3f          |AT#XNRFC LOUD?   [0m
2022-04-04T06:40:35.659Z DEBUG modem << [00:01:18.176,605] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-04T06:40:35.665Z DEBUG modem << [00:01:18.176,727] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:35.678Z DEBUG modem <<                                       0d 0a 23 58 4e 52 46 43  4c 4f 55 44 3a 20 30 2c |..#XNRFC LOUD: 0,
2022-04-04T06:40:35.704Z DEBUG modem <<                                       30 2c 31 36 38 34 32 37  35 33 2c 22 6e 72 66 2d |0,168427 53,"nrf-                                      33 35 32 36 35 36 31 30  38 36 30 30 34 38 30 22 |35265610 8600480"
2022-04-04T06:40:35.717Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:40:35.724Z DEBUG modem << [00:01:18.176,757] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:35.740Z DEBUG modem <<                                       0d 0a 4f 4b 0d 0a                                |..OK..           [0m
2022-04-04T06:40:40.603Z DEBUG modem >> AT#XAGPS=1,1
2022-04-04T06:40:40.612Z DEBUG modem << ERROR
2022-04-04T06:40:40.613Z ERROR Error: AT#XAGPS=1,1
 failed
2022-04-04T06:40:41.612Z DEBUG modem << [00:01:24.151,947] [0m<dbg> slm_at_host: RX
2022-04-04T06:40:41.628Z DEBUG modem <<                                       41 54 23 58 41 47 50 53  3d 31 2c 31             |AT#XAGPS =1,1    [0m
2022-04-04T06:40:41.634Z DEBUG modem << [00:01:24.152,435] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-04T06:40:41.640Z DEBUG modem << [00:01:24.152,465] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:41.654Z DEBUG modem <<                                       0d 0a 45 52 52 4f 52 0d  0a                      |..ERROR. .       [0m
2022-04-04T06:40:42.416Z DEBUG modem << +CEREG: 5,"026F","00332521",7,,,"00011110","11100000"
2022-04-04T06:40:43.416Z DEBUG modem << [00:01:25.956,268] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:43.437Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-04T06:40:43.439Z DEBUG modem << [00:01:25.956,329] [0m<dbg> slm_at_host: TX
2022-04-04T06:40:43.456Z DEBUG modem <<                                       2b 43 45 52 45 47 3a 20  35 2c 22 30 32 36 46 22 |+CEREG:  5,"026F"
2022-04-04T06:40:43.474Z DEBUG modem <<                                       2c 22 30 30 33 33 32 35  32 31 22 2c 37 2c 2c 2c |,"003325 21",7,,,
2022-04-04T06:40:43.489Z DEBUG modem <<                                       22 30 30 30 31 31 31 31  30 22 2c 22 31 31 31 30 |"0001111 0","1110                                      30 30 30 30 22 0d 0a                             |0000"..          [0m

RE: No connection to nRF cloud (Attempts to use AGPS)

justin — Mon, 04 Apr 2022 04:28:27 GMT

I see two CLOUD_EVT_CONNECTING events, but no CLOUD_EVT_CONNECTED event.

In the file slm_at_gnss.c, could you add a value to the log message:

case CLOUD_EVT_CONNECTING:
		LOG_DBG("CLOUD_EVT_CONNECTING: status %d", evt->data.err);

The value in evt->data.err is of type enum cloud_connect_result.

Setting CONFIG_NRF_CLOUD_LOG_LEVEL_DBG=y might be helpful too.

RE: No connection to nRF cloud (Attempts to use AGPS)

Stas Jis — Sun, 03 Apr 2022 06:56:41 GMT

justin,
I included on CONFIG_SLM_LOG_LEVEL_DBG=y,
I am attaching the logs:

2022-04-03T06:46:24.768Z DEBUG modem << *** Booting Zephyr OS build v2.7.99-ncs1-1  ***
2022-04-03T06:46:26.203Z DEBUG modem << Ready
2022-04-03T06:46:27.184Z DEBUG modem << [00:00:01.613,861] [0m<inf> slm: Serial LTE Modem[0m
2022-04-03T06:46:27.221Z DEBUG modem << [00:00:01.621,093] [0m<dbg> slm_at_host.slm_at_host_init: UART baud: 115200 d/p/s-bits: 3/0/1 HWFC: 1[0m
2022-04-03T06:46:27.223Z DEBUG modem << [00:00:01.621,093] [0m<dbg> slm_at_host.slm_uart_configure: Set uart baudrate to: 115200, hw flow control 1[0m
2022-04-03T06:46:27.228Z DEBUG modem << [00:00:01.638,946] [0m<dbg> slm_at_host: TX
2022-04-03T06:46:27.239Z DEBUG modem <<                                       52 65 61 64 79 0d 0a                             |Ready..          [0m
2022-04-03T06:46:27.251Z DEBUG modem << [00:00:01.639,038] [0m<dbg> slm_fota.slm_fota_post_process: FOTA result 0,0,0[0m
2022-04-03T06:46:27.253Z DEBUG modem << [00:00:01.646,362] [0m<inf> slm_at_host: at_host init done[0m
2022-04-03T06:46:29.953Z DEBUG modem >> AT
2022-04-03T06:46:29.964Z DEBUG modem << OK
2022-04-03T06:46:30.961Z DEBUG modem << [00:00:05.393,066] [0m<dbg> slm_at_host: RX
2022-04-03T06:46:30.976Z DEBUG modem <<                                       41 54                                            |AT               [0m
2022-04-03T06:46:30.981Z DEBUG modem << [00:00:05.399,627] [0m<dbg> slm_at_host: TX
2022-04-03T06:46:30.995Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-03T06:46:31.004Z DEBUG modem << [00:00:05.399,719] [0m<dbg> slm_at_host: TX
2022-04-03T06:46:31.019Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-03T06:46:32.159Z DEBUG modem >> AT+CFUN?
2022-04-03T06:46:32.171Z DEBUG modem << +CFUN: 0
2022-04-03T06:46:32.186Z DEBUG modem << OK
2022-04-03T06:46:33.168Z DEBUG modem << [00:00:07.599,395] [0m<dbg> slm_at_host: RX
2022-04-03T06:46:33.181Z DEBUG modem <<                                       41 54 2b 43 46 55 4e 3f                          |AT+CFUN?         [0m
2022-04-03T06:46:33.190Z DEBUG modem << [00:00:07.599,884] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-03T06:46:33.196Z DEBUG modem << [00:00:07.606,018] [0m<dbg> slm_at_host: TX
2022-04-03T06:46:33.209Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-03T06:46:33.216Z DEBUG modem << [00:00:07.606,048] [0m<dbg> slm_at_host: TX
2022-04-03T06:46:33.230Z DEBUG modem <<                                       2b 43 46 55 4e 3a 20 30  0d 0a 4f 4b 0d 0a       |+CFUN: 0 ..OK..  [0m
2022-04-03T06:46:47.628Z DEBUG modem >> AT%XSYSTEMMODE=1,0,1,0
2022-04-03T06:46:47.642Z DEBUG modem << OK
2022-04-03T06:46:48.638Z DEBUG modem << [00:00:23.070,587] [0m<dbg> slm_at_host: RX
2022-04-03T06:46:48.652Z DEBUG modem <<                                       41 54 25 58 53 59 53 54  45 4d 4d 4f 44 45 3d 31 |AT%XSYST EMMODE=1
2022-04-03T06:46:48.664Z DEBUG modem <<                                       2c 30 2c 31 2c 30                                |,0,1,0           [0m
2022-04-03T06:46:48.674Z DEBUG modem << [00:00:23.071,075] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-03T06:46:48.680Z DEBUG modem << [00:00:23.078,643] [0m<dbg> slm_at_host: TX
2022-04-03T06:46:48.693Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-03T06:46:48.703Z DEBUG modem << [00:00:23.078,674] [0m<dbg> slm_at_host: TX
2022-04-03T06:46:48.712Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-03T06:46:55.055Z DEBUG modem >> AT%XMAGPIO=1,0,0,1,1,1574,1577
2022-04-03T06:46:55.069Z DEBUG modem << OK
2022-04-03T06:46:56.067Z DEBUG modem << [00:00:30.500,122] [0m<dbg> slm_at_host: RX
2022-04-03T06:46:56.080Z DEBUG modem <<                                       41 54 25 58 4d 41 47 50  49 4f 3d 31 2c 30 2c 30 |AT%XMAGP IO=1,0,0
2022-04-03T06:46:56.094Z DEBUG modem <<                                       2c 31 2c 31 2c 31 35 37  34 2c 31 35 37 37       |,1,1,157 4,1577  [0m
2022-04-03T06:46:56.103Z DEBUG modem << [00:00:30.500,610] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-03T06:46:56.108Z DEBUG modem << [00:00:30.506,958] [0m<dbg> slm_at_host: TX
2022-04-03T06:46:56.124Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-03T06:46:56.130Z DEBUG modem << [00:00:30.507,019] [0m<dbg> slm_at_host: TX
2022-04-03T06:46:56.142Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-03T06:47:02.743Z DEBUG modem >> AT%XCOEX0
2022-04-03T06:47:02.755Z DEBUG modem << OK
2022-04-03T06:47:03.752Z DEBUG modem << [00:00:38.185,150] [0m<dbg> slm_at_host: RX
2022-04-03T06:47:03.768Z DEBUG modem <<                                       41 54 25 58 43 4f 45 58  30                      |AT%XCOEX 0       [0m
2022-04-03T06:47:03.774Z DEBUG modem << [00:00:38.185,638] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-03T06:47:03.782Z DEBUG modem << [00:00:38.191,833] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:03.794Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-03T06:47:03.799Z DEBUG modem << [00:00:38.191,894] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:03.815Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-03T06:47:10.735Z DEBUG modem >> AT+CEREG=5
2022-04-03T06:47:10.746Z DEBUG modem << OK
2022-04-03T06:47:11.744Z DEBUG modem << [00:00:46.177,764] [0m<dbg> slm_at_host: RX
2022-04-03T06:47:11.758Z DEBUG modem <<                                       41 54 2b 43 45 52 45 47  3d 35                   |AT+CEREG =5      [0m
2022-04-03T06:47:11.767Z DEBUG modem << [00:00:46.178,253] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-03T06:47:11.775Z DEBUG modem << [00:00:46.184,387] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:11.787Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-03T06:47:11.792Z DEBUG modem << [00:00:46.184,417] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:11.808Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-03T06:47:17.071Z DEBUG modem >> AT+CPSMS=1
2022-04-03T06:47:17.081Z DEBUG modem << OK
2022-04-03T06:47:18.079Z DEBUG modem << [00:00:52.513,580] [0m<dbg> slm_at_host: RX
2022-04-03T06:47:18.093Z DEBUG modem <<                                       41 54 2b 43 50 53 4d 53  3d 31                   |AT+CPSMS =1      [0m
2022-04-03T06:47:18.102Z DEBUG modem << [00:00:52.514,068] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-03T06:47:18.109Z DEBUG modem << [00:00:52.520,233] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:18.121Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-03T06:47:18.132Z DEBUG modem << [00:00:52.520,263] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:18.141Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-03T06:47:22.903Z DEBUG modem >> AT+CFUN=1
2022-04-03T06:47:22.947Z DEBUG modem << OK
2022-04-03T06:47:23.912Z DEBUG modem << [00:00:58.346,252] [0m<dbg> slm_at_host: RX
2022-04-03T06:47:23.925Z DEBUG modem <<                                       41 54 2b 43 46 55 4e 3d  31                      |AT+CFUN= 1       [0m
2022-04-03T06:47:23.936Z DEBUG modem << [00:00:58.346,740] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-03T06:47:23.942Z DEBUG modem << [00:00:58.386,474] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:23.954Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-03T06:47:23.960Z DEBUG modem << [00:00:58.386,505] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:23.973Z DEBUG modem <<                                       4f 4b 0d 0a                                      |OK..             [0m
2022-04-03T06:47:24.125Z DEBUG modem << +CEREG: 2,"026F","00332520",7
2022-04-03T06:47:25.128Z DEBUG modem << [00:00:59.562,683] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:25.143Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-03T06:47:25.149Z DEBUG modem << [00:00:59.562,744] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:25.161Z DEBUG modem <<                                       2b 43 45 52 45 47 3a 20  32 2c 22 30 32 36 46 22 |+CEREG:  2,"026F"
2022-04-03T06:47:25.174Z DEBUG modem <<                                       2c 22 30 30 33 33 32 35  32 30 22 2c 37 0d 0a    |,"003325 20",7.. [0m
2022-04-03T06:47:25.984Z DEBUG modem << +CEREG: 5,"026F","00332520",7,,,"00011110","11100000"
2022-04-03T06:47:26.985Z DEBUG modem << [00:01:01.418,945] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:26.998Z DEBUG modem <<                                       0d 0a                                            |..               [0m
2022-04-03T06:47:27.006Z DEBUG modem << [00:01:01.419,036] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:27.018Z DEBUG modem <<                                       2b 43 45 52 45 47 3a 20  35 2c 22 30 32 36 46 22 |+CEREG:  5,"026F"
2022-04-03T06:47:27.030Z DEBUG modem <<                                       2c 22 30 30 33 33 32 35  32 30 22 2c 37 2c 2c 2c |,"003325 20",7,,,
2022-04-03T06:47:27.056Z DEBUG modem <<                                       22 30 30 30 31 31 31 31  30 22 2c 22 31 31 31 30 |"0001111 0","1110                                      30 30 30 30 22 0d 0a                             |0000"..          [0m
2022-04-03T06:47:35.751Z DEBUG modem >> AT#XNRFCLOUD=1
2022-04-03T06:47:35.755Z DEBUG modem << OK
2022-04-03T06:47:36.760Z DEBUG modem << [00:01:11.194,671] [0m<dbg> slm_at_host: RX
2022-04-03T06:47:36.773Z DEBUG modem <<                                       41 54 23 58 4e 52 46 43  4c 4f 55 44 3d 31       |AT#XNRFC LOUD=1  [0m
2022-04-03T06:47:36.782Z DEBUG modem << [00:01:11.195,159] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-03T06:47:36.795Z DEBUG modem << [00:01:11.195,220] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:36.807Z DEBUG modem <<                                       0d 0a 4f 4b 0d 0a                                |..OK..           [0m
2022-04-03T06:47:36.817Z DEBUG modem << [00:01:11.195,312] [0m<dbg> slm_gnss.cloud_event_handler: CLOUD_EVT_CONNECTING[0m
2022-04-03T06:47:38.215Z DEBUG modem << [00:01:12.645,599] [0m<dbg> slm_gnss.cloud_event_handler: CLOUD_EVT_CONNECTING[0m
2022-04-03T06:47:56.407Z DEBUG modem >> AT#XAGPS=1,1
2022-04-03T06:47:56.412Z DEBUG modem << ERROR
2022-04-03T06:47:56.413Z ERROR Error: AT#XAGPS=1,1
 failed
2022-04-03T06:47:57.415Z DEBUG modem << [00:01:31.851,684] [0m<dbg> slm_at_host: RX
2022-04-03T06:47:57.429Z DEBUG modem <<                                       41 54 23 58 41 47 50 53  3d 31 2c 31             |AT#XAGPS =1,1    [0m
2022-04-03T06:47:57.438Z DEBUG modem << [00:01:31.852,172] [0m<dbg> slm_at_host.uart_callback: RX_DISABLED[0m
2022-04-03T06:47:57.444Z DEBUG modem << [00:01:31.852,203] [0m<dbg> slm_at_host: TX
2022-04-03T06:47:57.458Z DEBUG modem <<                                       0d 0a 45 52 52 4f 52 0d  0a                      |..ERROR. .       [0m

As for the SIM card, it is registered on the nRFcloud and the data is still available (Data Remaining 7.52 / 10.49 Mb).

RE: No connection to nRF cloud (Attempts to use AGPS)

justin — Fri, 01 Apr 2022 22:32:58 GMT

i can confirm that your device has not connected to nrf cloud (via MQTT) since: February 21, 2022, 00:19:10 (UTC-0800)

i tested with a DK, 1.9.1 tag, and your prj.conf and it worked as expected.
you could try uncommenting:
CONFIG_SLM_LOG_LEVEL_DBG=y
to get some more info.

or run asset_tracker_v2 on your device to see if it is able to connect to nRF Cloud.

Perhaps your SIM card is out of data or your device's nrf cloud credentials have been deleted/changed?

With this result:
2022-03-31T12:17:42.194Z DEBUG modem >> AT#XNRFCLOUD?
2022-03-31T12:17:42.206Z DEBUG modem << #XNRFCLOUD: 0,0,16842753,"nrf-352656108600480"

It is expected that you will get this result:
2022-03-31T12:17:36.432Z DEBUG modem >> AT#XAGPS=1,1
2022-03-31T12:17:36.439Z DEBUG modem << ERROR
2022-03-31T12:17:36.440Z ERROR Error: AT#XAGPS=1,1