Asset Tracker v2 CLOUD_EVT_CONNECTION_TIMEOUT

Question

Hello,

I'm using a Nordic Thingy:91 device for testing the asset tracker v2 application. I have a Verizon SIM card that's activated and is successfully registering with the network, however the log file and LED indicate that the device is not being provisioned with the nRF Cloud service. When I try to add the device via IMEI and PIN to the portal, I receive

The device appears to be attempting to connect with the message CLOUD_EVT_CONNECTING, but times out after some time with CLOUD_EVT_CONNNECTION TIMEOUT. The LED is green and blinking three

I would like to understand if this is an issue with the device software or with the Verizon LTE connection, and if I can resolve this. Below is the log file from LTE Link Monitor:

2022-09-12T14:53:39.474Z DEBUG Application data folder: C:\Users\[me]\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2022-09-12T14:53:39.583Z INFO Using nrf-device-lib-js version: 0.4.13
2022-09-12T14:53:39.583Z INFO Using nrf-device-lib version: 0.12.8
2022-09-12T14:53:39.584Z INFO Using nrfjprog DLL version: 10.16.0
2022-09-12T14:53:39.584Z INFO Using JLink version: JLink_V7.58b
2022-09-12T14:53:39.616Z DEBUG App pc-nrfconnect-linkmonitor v2.0.2 official
2022-09-12T14:53:39.616Z DEBUG App path: C:\Users\[me]\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2022-09-12T14:53:39.616Z DEBUG nRFConnect 3.12.0, required by the app is (^3.12.0)
2022-09-12T14:53:39.616Z DEBUG nRFConnect path: C:\Users\[me]\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-09-12T14:53:39.617Z DEBUG HomeDir: C:\Users\[me]
2022-09-12T14:53:39.617Z DEBUG TmpDir: C:\Users\[me]\AppData\Local\Temp
2022-09-12T14:53:39.618Z INFO Installed JLink version does not match the provided version (V7.66a)
2022-09-12T14:54:11.100Z INFO Modem port is opened
2022-09-12T14:54:11.112Z DEBUG modem >> AT+CFUN?
2022-09-12T14:54:11.133Z DEBUG modem << +CFUN: 1
2022-09-12T14:54:11.135Z DEBUG modem << OK
2022-09-12T14:54:11.151Z DEBUG modem >> AT+CGSN=1
2022-09-12T14:54:11.169Z DEBUG modem << +CGSN: "352656101498650"
2022-09-12T14:54:11.172Z DEBUG modem << OK
2022-09-12T14:54:11.177Z DEBUG modem >> AT+CGMI
2022-09-12T14:54:11.194Z DEBUG modem << Nordic Semiconductor ASA
2022-09-12T14:54:11.195Z DEBUG modem << OK
2022-09-12T14:54:11.198Z DEBUG modem >> AT+CGMM
2022-09-12T14:54:11.210Z DEBUG modem << nRF9160-SICA
2022-09-12T14:54:11.213Z DEBUG modem << 
2022-09-12T14:54:11.216Z DEBUG modem << OK
2022-09-12T14:54:11.219Z DEBUG modem >> AT+CGMR
2022-09-12T14:54:11.231Z DEBUG modem << mfw_nrf9160_1.3.2
2022-09-12T14:54:11.233Z DEBUG modem << OK
2022-09-12T14:54:11.235Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.2] SerNr: 352656101498650
2022-09-12T14:54:11.239Z DEBUG modem >> AT+CEMODE?
2022-09-12T14:54:11.250Z DEBUG modem << +CEMODE: 2
2022-09-12T14:54:11.252Z DEBUG modem << OK
2022-09-12T14:54:11.264Z DEBUG modem >> AT%XCBAND=?
2022-09-12T14:54:11.275Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
2022-09-12T14:54:11.277Z DEBUG modem << OK
2022-09-12T14:54:11.285Z DEBUG modem >> AT+CMEE?
2022-09-12T14:54:11.297Z DEBUG modem << +CMEE: 0
2022-09-12T14:54:11.299Z DEBUG modem << OK
2022-09-12T14:54:11.303Z DEBUG modem >> AT+CMEE=1
2022-09-12T14:54:11.315Z DEBUG modem << OK
2022-09-12T14:54:11.318Z DEBUG modem >> AT+CNEC?
2022-09-12T14:54:11.328Z DEBUG modem << +CNEC: 0
2022-09-12T14:54:11.329Z DEBUG modem << OK
2022-09-12T14:54:11.332Z DEBUG modem >> AT+CNEC=24
2022-09-12T14:54:11.340Z DEBUG modem << OK
2022-09-12T14:54:11.344Z DEBUG modem >> AT+CGEREP?
2022-09-12T14:54:11.357Z DEBUG modem << +CGEREP: 0,0
2022-09-12T14:54:11.360Z DEBUG modem << OK
2022-09-12T14:54:11.364Z DEBUG modem >> AT+CGDCONT?
2022-09-12T14:54:11.382Z DEBUG modem << +CGDCONT: 0,"IPV4V6","vzwadmin","10.132.230.208 2600:1007:F001:CA13:0000:0053:8219:0301",0,0
2022-09-12T14:54:11.384Z DEBUG modem << 
2022-09-12T14:54:11.385Z DEBUG modem << OK
2022-09-12T14:54:11.397Z DEBUG modem >> AT+CGACT?
2022-09-12T14:54:11.411Z DEBUG modem << +CGACT: 0,1
2022-09-12T14:54:11.413Z DEBUG modem << 
2022-09-12T14:54:11.414Z DEBUG modem << OK
2022-09-12T14:54:11.428Z DEBUG modem >> AT+CGEREP=1
2022-09-12T14:54:11.444Z DEBUG modem << OK
2022-09-12T14:54:11.448Z DEBUG modem >> AT+CIND=1,1,1
2022-09-12T14:54:11.461Z DEBUG modem << OK
2022-09-12T14:54:11.467Z DEBUG modem >> AT+CEREG=5
2022-09-12T14:54:11.474Z DEBUG modem << OK
2022-09-12T14:54:11.480Z DEBUG modem >> AT+CEREG?
2022-09-12T14:54:11.497Z DEBUG modem << +CEREG: 5,1,"E002","036FBF01",7,,,"00001010","11000010"
2022-09-12T14:54:11.499Z DEBUG modem << OK
2022-09-12T14:54:11.512Z DEBUG modem >> AT+COPS=3,2
2022-09-12T14:54:11.528Z DEBUG modem << OK
2022-09-12T14:54:11.531Z DEBUG modem >> AT+COPS?
2022-09-12T14:54:11.545Z DEBUG modem << +COPS: 1,2,"311480",7
2022-09-12T14:54:11.548Z DEBUG modem << OK
2022-09-12T14:54:11.562Z DEBUG modem >> AT%XCBAND
2022-09-12T14:54:11.577Z DEBUG modem << %XCBAND: 13
2022-09-12T14:54:11.579Z DEBUG modem << OK
2022-09-12T14:54:11.590Z DEBUG modem >> AT+CGDCONT?
2022-09-12T14:54:11.613Z DEBUG modem << +CGDCONT: 0,"IPV4V6","vzwadmin","10.132.230.208 2600:1007:F001:CA13:0000:0053:8219:0301",0,0
2022-09-12T14:54:11.614Z DEBUG modem << OK
2022-09-12T14:54:11.627Z DEBUG modem >> AT+CGACT?
2022-09-12T14:54:11.642Z DEBUG modem << +CGACT: 0,1
2022-09-12T14:54:11.643Z DEBUG modem << OK
2022-09-12T14:54:11.647Z DEBUG modem >> AT%CESQ=1
2022-09-12T14:54:11.651Z DEBUG modem << OK
2022-09-12T14:54:11.658Z DEBUG modem >> AT+CESQ
2022-09-12T14:54:11.674Z DEBUG modem << +CESQ: 99,99,255,255,21,51
2022-09-12T14:54:11.678Z DEBUG modem << OK
2022-09-12T14:54:11.684Z DEBUG modem >> AT%XSIM=1
2022-09-12T14:54:11.692Z DEBUG modem << OK
2022-09-12T14:54:11.695Z DEBUG modem >> AT%XSIM?
2022-09-12T14:54:11.707Z DEBUG modem << %XSIM: 1
2022-09-12T14:54:11.708Z DEBUG modem << OK
2022-09-12T14:54:11.715Z DEBUG modem >> AT+CPIN?
2022-09-12T14:54:11.725Z DEBUG modem << +CPIN: READY
2022-09-12T14:54:11.727Z DEBUG modem << OK
2022-09-12T14:54:11.732Z DEBUG modem >> AT+CPINR="SIM PIN"
2022-09-12T14:54:11.749Z DEBUG modem << +CPINR: "SIM PIN",3
2022-09-12T14:54:11.751Z DEBUG modem << OK
2022-09-12T14:54:11.760Z DEBUG modem >> AT+CIMI
2022-09-12T14:54:11.765Z DEBUG modem << 311480955947905
2022-09-12T14:54:11.767Z DEBUG modem << 
2022-09-12T14:54:11.768Z DEBUG modem << OK
2022-09-12T14:54:11.769Z INFO IMSIdentity: 311480955947905
2022-09-12T14:54:21.089Z DEBUG modem << %CESQ: 255,0,255,0
2022-09-12T14:55:39.195Z DEBUG modem << %CESQ: 46,2,18,2
2022-09-12T14:55:39.216Z DEBUG modem << %MDMEV: SEARCH STATUS 2
2022-09-12T14:55:39.885Z DEBUG modem << +CSCON: 1
2022-09-12T14:55:40.090Z DEBUG modem << %CESQ: 51,2,21,3
2022-09-12T14:55:40.119Z DEBUG modem << [00:03:46.642,791] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
2022-09-12T14:55:40.168Z DEBUG modem << [00:03:46.643,310] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-09-12T14:55:40.170Z DEBUG modem << [00:03:46.643,310] [1;33m<wrn> cloud_module: New connection attempt in 256 seconds if not successful[0m
2022-09-12T14:55:40.174Z DEBUG modem << [00:03:46.643,463] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-09-12T14:55:43.330Z DEBUG modem << %CESQ: 46,2,22,3
2022-09-12T14:55:49.928Z DEBUG modem << %CESQ: 51,2,23,3
2022-09-12T14:55:50.982Z DEBUG modem << +CSCON: 0
2022-09-12T14:55:51.144Z DEBUG modem << +CSCON: 1
2022-09-12T14:55:54.056Z DEBUG modem << %NCELLMEAS: 0,"036FBF01","311480","E002",128,5230,353,51,17,241085,238538
2022-09-12T14:55:54.981Z DEBUG modem << [00:04:01.506,866] [0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL[0m
2022-09-12T14:55:54.992Z DEBUG modem << [00:04:01.507,507] [0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS)[0m
2022-09-12T14:55:55.004Z DEBUG modem << [00:04:01.508,361] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2022-09-12T14:55:55.007Z DEBUG modem << [00:04:01.541,412] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
2022-09-12T14:55:55.014Z DEBUG modem << [00:04:01.580,444] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
2022-09-12T14:55:55.025Z DEBUG modem << [00:04:01.589,019] [0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2022-09-12T14:55:55.029Z DEBUG modem << [00:04:01.589,752] [0m<inf> app_event_manager: DATA_EVT_DATA_READY[0m
2022-09-12T14:55:57.710Z DEBUG modem << +CSCON: 0
2022-09-12T14:56:02.464Z DEBUG modem << +CSCON: 1
2022-09-12T14:56:04.880Z DEBUG modem << [00:04:11.406,616] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-09-12T14:56:08.536Z DEBUG modem << %CESQ: 49,2,18,2
2022-09-12T14:56:09.150Z DEBUG modem << +CSCON: 0
2022-09-12T14:56:09.570Z DEBUG modem << %CESQ: 41,2,11,1
2022-09-12T14:56:12.130Z DEBUG modem << %CESQ: 43,2,16,2
2022-09-12T14:56:29.153Z DEBUG modem << %CESQ: 255,0,255,0
2022-09-12T14:57:54.132Z DEBUG modem << %CESQ: 40,2,4,0
2022-09-12T14:57:54.548Z DEBUG modem << %CESQ: 40,2,17,2
2022-09-12T14:57:54.559Z DEBUG modem << %NCELLMEAS: 0,"036FBF01","311480","E002",65535,5230,353,44,11,361626,0
2022-09-12T14:57:54.977Z DEBUG modem << [00:06:01.506,896] [0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL[0m
2022-09-12T14:57:54.989Z DEBUG modem << [00:06:01.507,537] [0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS)[0m
2022-09-12T14:57:55.002Z DEBUG modem << [00:06:01.522,399] [0m<inf> app_event_manager: GNSS_EVT_ACTIVE[0m
2022-09-12T14:57:55.005Z DEBUG modem << [00:06:01.522,857] [0m<inf> app_event_manager: GNSS_EVT_AGPS_NEEDED[0m
2022-09-12T14:57:55.009Z DEBUG modem << [00:06:01.523,529] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2022-09-12T14:57:55.018Z DEBUG modem << [00:06:01.523,895] [1;33m<wrn> data_module: Failed to request A-GPS data, error: -13[0m
2022-09-12T14:57:55.025Z DEBUG modem << [00:06:01.523,895] [1;33m<wrn> data_module: This is expected to fail if we are not in a connected state[0m
2022-09-12T14:57:55.035Z DEBUG modem << [00:06:01.554,504] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
2022-09-12T14:57:55.041Z DEBUG modem << [00:06:01.567,474] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
2022-09-12T14:57:55.054Z DEBUG modem << [00:06:02.091,064] [0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2022-09-12T14:58:55.508Z DEBUG modem << [00:07:02.040,649] [0m<inf> app_event_manager: GNSS_EVT_TIMEOUT[0m
2022-09-12T14:58:55.521Z DEBUG modem << [00:07:02.041,137] [0m<inf> app_event_manager: GNSS_EVT_INACTIVE[0m
2022-09-12T14:58:55.525Z DEBUG modem << [00:07:02.041,564] [0m<inf> app_event_manager: DATA_EVT_DATA_READY[0m
2022-09-12T14:59:54.131Z DEBUG modem << %CESQ: 45,2,15,2
2022-09-12T14:59:54.868Z DEBUG modem << %CESQ: 50,2,25,3
2022-09-12T14:59:54.890Z DEBUG modem << %NCELLMEAS: 0,"036FBF01","311480","E002",65535,5230,353,46,11,481945,0
2022-09-12T14:59:54.975Z DEBUG modem << [00:08:01.506,927] [0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL[0m
2022-09-12T14:59:54.986Z DEBUG modem << [00:08:01.507,568] [0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS)[0m
2022-09-12T14:59:55.001Z DEBUG modem << [00:08:01.520,812] [0m<inf> app_event_manager: GNSS_EVT_ACTIVE[0m
2022-09-12T14:59:55.004Z DEBUG modem << [00:08:01.521,453] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2022-09-12T14:59:55.008Z DEBUG modem << [00:08:01.554,412] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
2022-09-12T14:59:55.020Z DEBUG modem << [00:08:01.567,016] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
2022-09-12T14:59:55.022Z DEBUG modem << [00:08:02.413,787] [0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2022-09-12T14:59:55.192Z DEBUG modem << %CESQ: 40,2,8,1
2022-09-12T14:59:55.214Z DEBUG modem << %MDMEV: SEARCH STATUS 2
2022-09-12T14:59:55.893Z DEBUG modem << +CSCON: 1
2022-09-12T14:59:55.910Z DEBUG modem << %CESQ: 50,2,20,2
2022-09-12T14:59:56.112Z DEBUG modem << [00:08:02.643,493] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
2022-09-12T14:59:56.126Z DEBUG modem << [00:08:02.644,012] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-09-12T14:59:56.139Z DEBUG modem << [00:08:02.644,012] [1;33m<wrn> cloud_module: New connection attempt in 512 seconds if not successful[0m
2022-09-12T14:59:56.152Z DEBUG modem << [00:08:02.644,165] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-09-12T14:59:59.487Z DEBUG modem << %CESQ: 50,2,25,3
2022-09-12T15:00:06.819Z DEBUG modem << +CSCON: 0
2022-09-12T15:00:18.972Z DEBUG modem << %CESQ: 52,2,12,1
2022-09-12T15:00:19.083Z DEBUG modem << +CSCON: 1
2022-09-12T15:00:19.288Z DEBUG modem << %CESQ: 55,2,17,2
2022-09-12T15:00:24.140Z DEBUG modem << %CESQ: 55,2,22,3
2022-09-12T15:00:25.300Z DEBUG modem << %CESQ: 50,2,22,3
2022-09-12T15:00:27.364Z DEBUG modem << [00:08:33.897,583] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-09-12T15:00:29.000Z DEBUG modem << +CSCON: 0
2022-09-12T15:00:41.172Z DEBUG modem << %CESQ: 39,1,5,0
2022-09-12T15:00:42.211Z DEBUG modem << %CESQ: 51,2,25,3
2022-09-12T15:00:49.878Z DEBUG modem << %CESQ: 255,0,255,0
2022-09-12T15:01:09.987Z DEBUG modem << [00:09:16.521,881] [0m<inf> app_event_manager: DATA_EVT_DATA_READY[0m
2022-09-12T15:01:17.962Z DEBUG modem << [00:09:24.496,734] [0m<inf> app_event_manager: GNSS_EVT_TIMEOUT[0m
2022-09-12T15:01:17.983Z DEBUG modem << [00:09:24.497,222] [0m<inf> app_event_manager: GNSS_EVT_INACTIVE[0m
2022-09-12T15:01:54.132Z DEBUG modem << %CESQ: 34,1,0,0
2022-09-12T15:01:54.972Z DEBUG modem << [00:10:01.506,958] [0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL[0m
2022-09-12T15:01:54.987Z DEBUG modem << [00:10:01.507,598] [0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS)[0m
2022-09-12T15:01:54.991Z DEBUG modem << [00:10:01.520,843] [0m<inf> app_event_manager: GNSS_EVT_ACTIVE[0m
2022-09-12T15:01:55.003Z DEBUG modem << [00:10:01.521,484] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2022-09-12T15:01:55.006Z DEBUG modem << [00:10:01.554,779] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
2022-09-12T15:01:55.020Z DEBUG modem << [00:10:01.567,291] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
2022-09-12T15:01:55.189Z DEBUG modem << %CESQ: 43,2,21,3
2022-09-12T15:01:55.203Z DEBUG modem << %NCELLMEAS: 0,"036FBF01","311480","E002",65535,5230,353,37,-3,602265,0
2022-09-12T15:01:56.202Z DEBUG modem << [00:10:02.736,633] [0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m

Thanks in advance!

nRF Code	Error	Reason	Solution
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.

nRF Code	Error	Reason	Solution
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.