Unable to connect to Cloud using Asset Tracker on nRF9160 DK

[AlbertSerica]

Hello, I am currently learning to use nRF9160 DK in Guangzhou, China. 

It is weird that my China Mobile cellphone SIM card can be used on this DK to connect to Cloud. However, iBasics SIM and China Telecom NBIOT SIM cannot connect to Cloud. 

While using iBasics, it's LED3 that keeps blinking. While using China Telecom, LED3 blinks first, then LED4 blinks, LED1 and LED4 blinks at last.

The following is from nRF Connect during the entire session for China Telecom

+CSCON: 1

 

 

[00:00:08.419,586]

[0m<inf> asset_tracker: RRC mode: Connected

[0m

 

 

+CEREG: 1,"765E","075D6450",9,,,"11100000","00111000"

 

 

[00:00:10.095,031]

[0m<inf> asset_tracker: Connected to LTE network.

[0m

 

 

[00:00:10.101,623]

[0m<inf> asset_tracker: Connecting to cloud, attempt 1 of 8

[0m

 

 

[00:00:10.109,039]

[0m<inf> asset_tracker: Cloud connection request sent.

[0m

 

 

[00:00:10.115,966]

[0m<inf> asset_tracker: Connection response timeout is set to 30 seconds.

[0m

 

 

[00:00:10.124,664]

[0m<inf> asset_tracker: Network registration status: Connected - home network

[0m

 

 

[00:00:10.133,544]

[0m<inf> asset_tracker: PSM parameter update: TAU: 86400, Active time: -1

[0m

 

[00:00:10.142,242]

[0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING

[0m

 

 

[00:00:10.150,695]

[0m<inf> asset_tracker: CLOUD_EVT_CONNECTING

[0m

 

 

[00:00:20.343,505]

[0m<dbg> nrf_cloud_transport.nct_connect: IPv4 address: 54.166.31.114

[0m

 

 

[00:00:20.351,715]

[0m<dbg> nrf_cloud_transport.nct_mqtt_connect: MQTT clean session flag: 0

[0m

 

 

[00:00:25.044,555]

[1;33m<wrn> date_time: sntp_query, error: -116

[0m

 

 

[00:00:32.817,443]

[1;33m<wrn> date_time: sntp_query, error: -116

[0m

 

 

[00:00:38.944,549]

[1;33m<wrn> date_time: sntp_query, error: -116

[0m

 

[00:00:44.977,661]

[1;33m<wrn> date_time: sntp_query, error: -116

[0m

 

 

[00:00:51.057,739]

[1;33m<wrn> date_time: sntp_query, error: -116

[0m

 

 

[00:00:51.064,270]

[1;33m<wrn> date_time: Not getting time from any NTP server

[0m

 

 

[00:00:51.072,357]

[0m<inf> asset_tracker: DATE_TIME_OBTAINED_MODEM

[0m

 

 

+CSCON: 0

 

 

[00:01:16.166,137]

[0m<inf> asset_tracker: RRC mode: Idle

[0m

 

 

+CSCON: 1

 

 

[00:01:21.380,767]

[0m<inf> asset_tracker: RRC mode: Connected

[0m

 

 

+CSCON: 0

 

 

[00:01:43.162,567]

[0m<inf> asset_tracker: RRC mode: Idle

[0m

 

 

+CSCON: 1

 

 

[00:02:13.541,534]

[0m<inf> asset_tracker: RRC mode: Connected

[0m

 

 

+CSCON: 0

 

 

[00:02:35.173,370]

[0m<inf> asset_tracker: RRC mode: Idle

[0m

 

 

[00:03:00.723,693]

[0m<dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect failed -22

[0m

 

 

[00:03:00.732,025]

[0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING

[0m

 

 

[00:03:00.740,509]

[0m<inf> asset_tracker: CLOUD_EVT_CONNECTING

[0m

 

 

[00:03:00.746,582]

[1;31m<err> asset_tracker: Failed to connect to cloud, error -7

[0m

 

 

[00:03:00.754,333]

[1;31m<err> asset_tracker: Ensure device has a valid private key

[0m

 

 

[00:03:00.762,145]

[1;31m<err> asset_tracker: Device will reboot in 300 seconds

[0m

 

 

[00:03:00.769,653]

[1;31m<err> asset_tracker: LTE link disconnect

[0m

 

 

+CSCON: 1

 

 

[00:03:01.222,259]

[0m<inf> asset_tracker: RRC mode: Connected

[0m

 

 

+CEREG: 0,"765E","075D6450",9,0,0,"11100000","11100000"

 

 

+CSCON: 0

 

 

[00:03:06.757,415]

[0m<inf> asset_tracker: RRC mode: Idle

[0m

 

 

[00:03:07.170,684]

[1;31m<err> asset_tracker: Shutdown modem

[0m

[Heidi]

Hi!

1. When using the Chine Mobile Cellphone SIM, is it connecting through LTE-M or NB-IoT? The +CEREG response field AcT will return 7 for LTE-M and 9 for NB-IoT.

2. You say LED1 and LED4 blinks at last, which isn't one of the defined application states (see Asset Tracker: User interface). Could you take a look at the documentation and tell me if the LED blinking pattern matches any of them?

3. From the iBasis log it doesn't look like it's done connecting to the network. Please wait at least 10 minutes as it can take a while for the device to connect to the network and to nRF Cloud. 

[00:00:00.343,688] [0m<inf> asset_tracker: Connecting to LTE network.[0m
[00:00:00.350,280] [0m<inf> asset_tracker: This may take several minutes.[0m
+CEREG: 2,"FFFE","FFFFFFFF",7,0,0,"11100000","11100000"
[00:00:58.980,285] [0m<inf> asset_tracker: LTE cell changed: Cell ID: -1, Tracking area: 65534[0m

4. As for the issues with China Telecom NB-IoT SIM, we're going to need a modem trace to investigate further (see Collecting a modem trace for the nRF9160 DK). 

[AlbertSerica]

Hello, 

China doesn't have LTE-M so only NB-IoT is used. CEREG returns 9.

Blinking in cross pattern (LED 1 and 4, LED 2 and 3): Communication error with the nRF Connect for Cloud.

The asset tracker connected to the Internet after a few minutes. 

2021-06-15T01:56:50.457Z DEBUG modem << [00:00:10.103,912] [0m<inf> asset_tracker: Connected to LTE network.[0m

The problem I encountered seems to be related to zzhc library, there is a page about zzhc but it's not clear about how to use it:

developer.nordicsemi.com/.../zzhc.html

[Heidi]

AlbertSerica said:

The asset tracker connected to the Internet after a few minutes. 

 Not in the first log you provided. I thought those logs were from two different SIM cards.

 

AlbertSerica said:

The problem I encountered seems to be related to zzhc library, there is a page about zzhc but it's not clear about how to use it:

 Please provide your prj.conf file and Kconfig file and I will take a look. 

[AlbertSerica]

Hello, please have a look, I have to put .txt as a suffix to get Kconfig uploaded:

4237.prj.conf

Fullscreen Kconfig - copy.txt Download

#
# Copyright (c) 2018 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

menu "Asset tracker"

rsource "src/ui/Kconfig"

config APPLICATION_WORKQUEUE_STACK_SIZE
	int "Application workqueue stack size"
	default 4096

config APPLICATION_WORKQUEUE_PRIORITY
	int "Application workqueue priority"
	default SYSTEM_WORKQUEUE_PRIORITY

menu "GPS"

choice
	prompt "GPS device"
	default GPS_USE_SIM
	help
	  Select from which device GPS data will be fetched.

config GPS_USE_SIM
	bool "Use GPS simulator"
	select GPS_SIM
	select GPS_SIM_TRIGGER
	help
	  Use simulated GPS data.

config GPS_USE_EXTERNAL
	bool "User provided GPS device"
	help
	  Provide a GPS device that location data will be fetched from and
	  sent to nRF Cloud

endchoice

config GPS_DEV_NAME
	string "GPS device name"
	default GPS_SIM_DEV_NAME if GPS_USE_SIM
	help
	  GPS device from which location data will be fetched and sent
	  to nRF Cloud.

config GPS_CONTROL_ON_LONG_PRESS
	bool "Control the GPS state with button"
	default y
	help
	  Control the GPS operation with long-press on the button.
	  Press for 5 seconds to enable, or 5 seconds to disable.

config GPS_CONTROL_PSM_ENABLE_ON_START
	bool "Enable PSM when starting GPS"
	help
	  The nRF9160 modem needs to be set in PSM mode for the GPS to start
	  searching for satellites. Enabling this option will do so
	  automatically, otherwise the application must handle it.

config GPS_CONTROL_PSM_DISABLE_ON_STOP
	bool "Disable PSM when stopping GPS"
	help
	  Selecting this option will disable PSM when the GPS is stopped.
	  During a PSM interval, the device is not reachable from the outside
	  until the interval times out, or the device itself attempts to
	  send data on the link.

config GPS_CONTROL_FIRST_FIX_CHECK_DELAY
	int "Time from Cloud conenction until first fix check"
	default 30
	help
	  The amount of time that should pass between successfully establishing
	  connection to cloud until first attempt to get position fix.
	  Attempting to get a fix means entering PSM mode, in which the device
	  is not reachable for the duration of the interval, or until the
	  device itself sends data and then for the duration for the set
	  active time thereafter.

config GPS_CONTROL_FIX_CHECK_INTERVAL
	int "Interval in seconds to between check for position fix"
	default 120
	help
	  The fix check interval gives the interval for how long it will go
	  between each retry to achieve position fix. The actual fix time will
	  vary with factors such as satellite coverage, surrounding buildings
	  and landscape, PSM interval and activity time requested and granted
	  by the network.

config GPS_CONTROL_FIX_CHECK_OVERDUE
	int "Longest allowed time in seconds between checks for position fix"
	default 900
	help
	  The fix check interval gives the interval for how long it will go
	  between each retry to achieve position fix, when GPS_START_ON_MOTION
	  enabled, even if no motion is detected.

config GPS_CONTROL_FIX_TRY_TIME
	int "Time in seconds to try to get fix"
	default 180
	help
	  Amount of time the device will attempt to get position fix. Note that
	  if the interval is interrupted by the device sending data, the timer
	  is not reset, and the actual try time will be shortened due to
	  the device not being in PSM mode all the time. If fix is not acquired
	  before it times out, the device will try to get fix again in
	  GPS_CONTROL_FIX_CHECK_INTERVAL seconds. If GPS_CONTROL_FIX_COUNT is reached
	  before the full GPS_CONTROL_FIX_TRY_TIME has passed, the GPS will be stopped.

config GPS_CONTROL_FIX_COUNT
	int "Number of position fix before stopping GPS"
	default 3
	help
	  The number of fixes to get before stopping the GPS, within the time
	  set in GPS_CONTROL_FIX_CHECK_INTERVAL.

config GPS_CONTROL_MAX_FAILED_FIX_ATTEMPTS
	int "Number of failed fix attempts before stopping GPS"
	default 3
	help
	  Number of retries to get fix before shutting down the GPS until user
	  input tells it to start retrying.

config GPS_START_ON_MOTION
	bool "Motion triggered GPS update"
	default n
	help
	  When accelerometer detects movement, and GPS is enabled, update GPS
	  position, but if no movement, wait a longer delay between updates
	  to conserve power.

endmenu # GPS

menu "Device and modem"

config POWER_OPTIMIZATION_ENABLE
	bool "Enable power optimization"
	default y
	select LTE_EDRX_REQ

if MODEM_INFO

config HOLD_TIME_RSRP
	int "Minimum time [s] between RSRP subscription messages"
	default 60
	help
	  The minimum time in seconds where the modem
	  informer is allowed to submit RSRP data to the cloud.

endif

endmenu # Device

menuconfig MOTION
	bool "Enable motion sensing in Asset Tracker"
	default y
	help
	  Enables motion sensing in asset tracker with real
	  sensors or simulated ones.

if MOTION

choice
	prompt "Accelerometer device"
	default ACCEL_USE_SIM
	help
	  Select which device will provide accelerometer data.

config ACCEL_USE_SIM
	bool "Use simulated accelerometer data"
	select SENSOR
	select SENSOR_SIM
	select SENSOR_SIM_TRIGGER
	help
	  Use sensor simulator to generate accelerometer data for
	  flip detection data sent to nRF Cloud.

config ACCEL_USE_EXTERNAL
	bool "User provided accelerometer device"
	help
	  The user will provide an accelerometer device that will
	  be used for flip detection.

endchoice

if ACCEL_USE_SIM
config ACCEL_DEV_NAME
	string
	default SENSOR_SIM_DEV_NAME

config ACCEL_TRIGGER
	bool
	default SENSOR_SIM_TRIGGER

config FLIP_INPUT
	int "Button or switch number to simulate flip"
	range 1 4 if BOARD_NRF9160DK_NRF9160NS
	range 1 1 if BOARD_THINGY91_NRF9160NS
	default 3 if BOARD_NRF9160DK_NRF9160NS
	default 1 if BOARD_THINGY91_NRF9160NS
	help
	  Button or switch number to use for simulating
	  a board flip event.
	  1 - Button 1
	  2 - Button 2
	  3 - Switch 1
	  4 - Switch 2
endif

if ACCEL_USE_EXTERNAL

config ACCEL_DEV_NAME
	string "Accelerometer device name"
	help
	  Device from which accelerometer data will be fetched and used
	  for orientation detection and sent to nRF Cloud.

endif

config ACCEL_INVERTED
	bool "Accelerometer inverted"
	default y if BOARD_THINGY91_NRF9160NS
	help
	  Enable if the accelerometer is mounted with the top side facing
	  down when the board itself is in normal position.

endif # MOTION

menu "Cloud"

config MQTT_KEEPALIVE
	int "Time after last transmission to send a ping to keep connection on"
	default 1200
	help
	  This should be set to the expected time between messages sent from
	  this device. Making it larger than the expected data period does not
	  conserve bandwidth, as the ping is only sent if nothing else
	  has been within the specified period. Shorter values can prevent hidden
	  NAT timeouts at the carrier, but also will interrupt GPS fix attempts
	  and slow down TTFF.

config CLOUD_BUTTON
	bool "Enable button sensor"
	default y

config CLOUD_BUTTON_INPUT
	int "Set button sensor button number"
	range 1 4 if BOARD_NRF9160DK_NRF9160NS
	range 1 1 if BOARD_THINGY91_NRF9160NS
	default 1

config CLOUD_CONNECT_RETRY_DELAY
	int "Cloud connection retry delay in seconds"
	default 480
	help
	  Time to wait before trying to reconnect to the cloud if the
	  previous attempt failed (in seconds).

config CLOUD_CONNECT_COUNT_MAX
	int "Maximum number of cloud connection attempts"
	default 8
	help
	  Maximum number of unsuccessful cloud connection attempts.
	  Device will wait for the value defined by CLOUD_CONNECT_RETRY_DELAY
	  between attempts.

config CLOUD_WAIT_DURATION
	int "Cloud connection acknowledge wait duration"
	default 30
	help
	  How long the device should wait for a CONNACK
	  event from the cloud when connecting.  Device will reboot
	  if an ack is not received within the duration.

config CLOUD_FOTA_APP
	bool "Enable firmware over-the-air upgrades for application"
	depends on AWS_FOTA || NRF_CLOUD_FOTA
	depends on DFU_TARGET_MCUBOOT
	default y

config CLOUD_FOTA_MODEM
	bool "Enable firmware over-the-air upgrades for modem"
	depends on AWS_FOTA || NRF_CLOUD_FOTA
	depends on DFU_TARGET_MODEM_DELTA
	default y

config CLOUD_FOTA_BOOT
	bool "Enable firmware over-the-air upgrades for bootloader"
	depends on AWS_FOTA || NRF_CLOUD_FOTA
	depends on DFU_TARGET_MCUBOOT
	depends on SECURE_BOOT
	default y

config CLOUD_CONNECT_ERR_REBOOT_S
	int "Seconds to wait before rebooting when a cloud connect error occurs"
	default 300

if NRF_CLOUD_CLIENT_ID_SRC_RUNTIME

config CLOUD_RUNTIME_CLIENT_ID
	string "Client ID used for cloud connection"
	default "my_runtime_client_id"

endif # NRF_CLOUD_CLIENT_ID_SRC_RUNTIME

endmenu # Cloud

menuconfig ENVIRONMENT_SENSORS
	bool "Enable environment sensing in Asset Tracker"
	default y
	help
	  Enables environment sensing in asset tracker with real
	  sensors or simulated ones.

if ENVIRONMENT_SENSORS

config USE_BME680_BSEC
	bool "Use Bosch BME680 BSEC lib"
	default n
	help
	  Enable use of Bosch BSEC library. The library itself is not a part of
	  NCS and must be downloaded from Bosch Sensortec.

config BOSCH_BSEC_LIBRARY_PATH
	string "Path to Bosch BSEC library folder"
	default "$(ZEPHYR_BASE)/../nrf/ext/BSEC_1.4.8.0_Generic_Release"
	help
	  Path to the folder where the Bosch BSEC library is placed.

config ENVIRONMENT_DATA_SEND_INTERVAL
	int "Interval in seconds for sending environment data"
	default 30
	help
	  Interval between each sampling and sending of environment sensor data.
	  If the GPS is active, sensor data will not be sent before it is
	  stopped. The unit is seconds.

config ENVIRONMENT_DATA_BACKOFF_TIME
	int "Time to delay sending environment data if GPS active"
	default 20
	help
	  Time in seconds before retrying to send environment sensor data if
	  the GPS is active.

choice
	prompt "Temperature measurement device"
	default TEMP_USE_SIM
	help
	  Select which device will provide temperature data.

config TEMP_USE_SIM
	bool "Use simulated temperature data"
	select SENSOR
	select SENSOR_SIM
	help
	  Use sensor simulator to generate temperature data to send to
	  nRF Cloud.

config TEMP_USE_EXTERNAL
	bool "User provided temperature device"
	help
	  The user provides a temperature device that is
	  used for temperature measurement.

endchoice

if TEMP_USE_SIM
config TEMP_DEV_NAME
	string
	default SENSOR_SIM_DEV_NAME

config TEMP_TRIGGER
	bool
	default SENSOR_SIM_TRIGGER

config TEMP_SIM_BUTTON
	int "Button or switch to trigger 'data ready' event"
	range 1 4 if BOARD_NRF9160DK_NRF9160NS
	range 1 1 if BOARD_THINGY91_NRF9160NS
	default 3 if BOARD_NRF9160DK_NRF9160NS
	default 1 if BOARD_THINGY91_NRF9160NS
	help
	  Button or switch number to use for triggering
	  a 'data ready' event.
	  1 - Button 1
	  2 - Button 2
	  3 - Switch 1
	  4 - Switch 2
endif

if TEMP_USE_EXTERNAL

config TEMP_DEV_NAME
	string "Temperature device name"
	help
	  Device from which temperature data will be fetched and
	  sent to nRF Cloud.

endif

endif # ENVIRONMENT_SENSORS

menuconfig LIGHT_SENSOR
	bool "Light sensor"
	select BH1749 if BOARD_THINGY91_NRF9160NS
	default y if BOARD_THINGY91_NRF9160NS

if LIGHT_SENSOR

config LIGHT_SENSOR_DEV_NAME
	string "Light sensor device name"
	default "BH1749" if BOARD_THINGY91_NRF9160NS

config LIGHT_SENSOR_DATA_SEND_INTERVAL
	int "Interval in seconds for sending light sensor data"
	default 60
	help
	  Interval between each sampling and sending of light sensor data.
	  If the GPS is active, sensor data will not be sent before it is
	  stopped. The unit is seconds.

endif # LIGHT_SENSOR

config GPS_START_AFTER_CLOUD_EVT_READY
	bool "Automatic start of GPS on CLOUD_EVT_READY event after reset"
	default n
	help
	  Enabling this will make the GPS automatically start after a reset.
	  Useful when operating as a GPS tracker outdoors for a longer period
	  of time.

config ASSET_TRACKER_WATCHDOG_TIMEOUT_MSEC
	int "Watchdog timeout in milliseconds"
	default 60000

config USE_AT_HOST
	bool "Enable AT commands"
	default y
	select AT_HOST_LIBRARY
	help
	  Enable the AT host library so that AT commands can be sent to and
	  received from a serial terminal.

endmenu

menu "Zephyr Kernel"
source "Kconfig.zephyr"
endmenu

config ZZHC
    bool "Self-Registration Daemon"
    select NRF_MODEM_LIB
    select SETTINGS
    select AT_CMD
    select AT_CMD_PARSER
    select AT_NOTIF
    select BASE64
    select JSON_LIBRARY
    depends on TRUSTED_EXECUTION_NONSECURE

module = ASSET_TRACKER
module-str = Asset Tracker
source "${ZEPHYR_BASE}/subsys/logging/Kconfig.template.log_config"

[Heidi]

Hi, it doesn't look like you've added "CONFIG_ZZHC=y" to the prj.conf file?

[AlbertSerica]

Hello, I haven't not added it yet. I'm not sure the correct to do the following:

• Configure the following option if you want to use this library:

CONFIG_TRUSTED_EXECUTION_NONSECURE

• In Kconfig, enable CONFIG_ZZHC.

In other public posts, I saw others also raised similar questions

[Heidi]

I see. Yes, that is a bit confusing. 

You can just add "CONFIG_ZZHC=y" to the prj.conf file, no need to do anything with it in the Kconfig, since it's already defined here.

[AlbertSerica]

Hello,Heidi,

I added  "CONFIG_ZZHC=y" to the prj.conf file, but the dev kit is still unable to connect to nrf cloud. I tried to update the certificate as well. The attachment is the log

Fullscreen 2021-06-28T06_25_16.287Z-log.txt Download

2021-06-28T06:25:16.710Z INFO Application data folder: C:\Users\aaa\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2021-06-28T06:25:16.768Z DEBUG App pc-nrfconnect-linkmonitor v1.1.10 official
2021-06-28T06:25:16.768Z DEBUG App path: C:\Users\aaa\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-06-28T06:25:16.768Z DEBUG nRFConnect 3.7.0, required by the app is (^3.6.0)
2021-06-28T06:25:16.768Z DEBUG nRFConnect path: C:\Users\aaa\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-06-28T06:25:16.769Z DEBUG HomeDir: C:\Users\aaa
2021-06-28T06:25:16.769Z DEBUG TmpDir: C:\Users\aaa\AppData\Local\Temp
2021-06-28T06:25:18.147Z INFO Modem port is opened
2021-06-28T06:26:11.747Z DEBUG modem << G: 2,"FFFE","FFFFFFFF",7,0,0,"11100000","11100000"
2021-06-28T06:26:11.761Z DEBUG modem << [00:01:01.849,670] [0m<inf> asset_tracker: LTE cell changed: Cell ID: -1, Tracking area: 65534[0m
2021-06-28T06:35:10.378Z DEBUG modem << [00:10:00.475,616] [0m<inf> lte_lc: Network connection attempt timed out[0m
2021-06-28T06:35:10.392Z DEBUG modem << +CEREG: 0,"FFFE","FFFFFFFF",7,0,0,"11100000","11100000"
2021-06-28T06:35:10.404Z DEBUG modem << %XSIM: 0
2021-06-28T06:35:10.410Z DEBUG modem << [00:10:00.499,328] [0m<inf> lte_lc: Using fallback network mode[0m
2021-06-28T06:35:14.619Z DEBUG modem << %XSIM: 1
2021-06-28T06:35:19.422Z DEBUG modem << +CEREG: 2,"765E","075D6450",9,0,0,"11100000","11100000"
2021-06-28T06:35:19.431Z DEBUG modem << [00:10:09.527,191] [0m<inf> asset_tracker: LTE cell changed: Cell ID: 123561040, Tracking area: 30302[0m
2021-06-28T06:35:20.071Z DEBUG modem << +CSCON: 1
2021-06-28T06:35:20.079Z DEBUG modem << [00:10:10.175,964] [0m<inf> asset_tracker: RRC mode: Connected[0m
2021-06-28T06:35:21.760Z DEBUG modem << +CEREG: 1,"765E","075D6450",9,,,"11100000","00111000"
2021-06-28T06:35:21.767Z DEBUG modem << [00:10:11.865,234] [0m<inf> asset_tracker: Connected to LTE network.[0m
2021-06-28T06:35:21.778Z DEBUG modem << [00:10:11.871,826] [0m<inf> asset_tracker: Connecting to cloud, attempt 1 of 8[0m
2021-06-28T06:35:21.783Z DEBUG modem << [00:10:11.879,241] [0m<inf> asset_tracker: Cloud connection request sent.[0m
2021-06-28T06:35:21.790Z DEBUG modem << [00:10:11.886,169] [0m<inf> asset_tracker: Connection response timeout is set to 30 seconds.[0m
2021-06-28T06:35:21.799Z DEBUG modem << [00:10:11.894,927] [0m<inf> asset_tracker: Network registration status: Connected - home network[0m
2021-06-28T06:35:21.808Z DEBUG modem << [00:10:11.903,808] [0m<inf> asset_tracker: PSM parameter update: TAU: 86400, Active time: -1[0m
2021-06-28T06:35:21.817Z DEBUG modem << [00:10:11.912,933] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING[0m
2021-06-28T06:35:21.823Z DEBUG modem << [00:10:11.921,600] [0m<inf> asset_tracker: CLOUD_EVT_CONNECTING[0m
2021-06-28T06:35:22.375Z DEBUG modem << [00:10:12.471,832] [0m<dbg> nrf_cloud_transport.nct_connect: IPv4 address: 52.54.83.79[0m
2021-06-28T06:35:22.385Z DEBUG modem << [00:10:12.479,888] [0m<dbg> nrf_cloud_transport.nct_mqtt_connect: MQTT clean session flag: 0[0m
2021-06-28T06:35:27.053Z DEBUG modem << [00:10:17.151,763] [1;33m<wrn> date_time: sntp_query, error: -116[0m
2021-06-28T06:35:32.447Z DEBUG modem << [00:10:22.545,684] [1;33m<wrn> date_time: sntp_query, error: -116[0m
2021-06-28T06:35:38.395Z DEBUG modem << [00:10:28.493,774] [1;33m<wrn> date_time: sntp_query, error: -116[0m
2021-06-28T06:35:44.517Z DEBUG modem << [00:10:34.615,875] [1;33m<wrn> date_time: sntp_query, error: -116[0m
2021-06-28T06:35:50.602Z DEBUG modem << [00:10:40.700,988] [1;33m<wrn> date_time: sntp_query, error: -116[0m
2021-06-28T06:35:50.610Z DEBUG modem << [00:10:40.707,489] [1;33m<wrn> date_time: Not getting time from any NTP server[0m
2021-06-28T06:35:50.617Z DEBUG modem << [00:10:40.715,576] [0m<inf> asset_tracker: DATE_TIME_OBTAINED_MODEM[0m
2021-06-28T06:36:18.599Z DEBUG modem << +CSCON: 0
2021-06-28T06:36:18.604Z DEBUG modem << [00:11:08.704,406] [0m<inf> asset_tracker: RRC mode: Idle[0m
2021-06-28T06:36:22.152Z DEBUG modem << +CSCON: 1
2021-06-28T06:36:22.158Z DEBUG modem << [00:11:12.256,958] [0m<inf> asset_tracker: RRC mode: Connected[0m
2021-06-28T06:36:43.658Z DEBUG modem << +CSCON: 0
2021-06-28T06:36:43.663Z DEBUG modem << [00:11:33.762,786] [0m<inf> asset_tracker: RRC mode: Idle[0m
2021-06-28T06:37:14.359Z DEBUG modem << +CSCON: 1
2021-06-28T06:37:14.364Z DEBUG modem << [00:12:04.463,775] [0m<inf> asset_tracker: RRC mode: Connected[0m
2021-06-28T06:37:36.618Z DEBUG modem << +CSCON: 0
2021-06-28T06:37:36.624Z DEBUG modem << [00:12:26.723,602] [0m<inf> asset_tracker: RRC mode: Idle[0m
2021-06-28T06:38:04.702Z DEBUG modem << [00:12:54.799,957] [0m<dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect failed -22[0m
2021-06-28T06:38:04.712Z DEBUG modem << [00:12:54.808,288] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING[0m
2021-06-28T06:38:04.717Z DEBUG modem << [00:12:54.816,772] [0m<inf> asset_tracker: CLOUD_EVT_CONNECTING[0m
2021-06-28T06:38:04.727Z DEBUG modem << [00:12:54.822,875] [1;31m<err> asset_tracker: Failed to connect to cloud, error -7[0m
2021-06-28T06:38:04.733Z DEBUG modem << [00:12:54.830,627] [1;31m<err> asset_tracker: Ensure device has a valid private key[0m
2021-06-28T06:38:04.743Z DEBUG modem << [00:12:54.838,470] [1;31m<err> asset_tracker: Device will reboot in 300 seconds[0m
2021-06-28T06:38:04.748Z DEBUG modem << [00:12:54.845,947] [1;31m<err> asset_tracker: LTE link disconnect[0m
2021-06-28T06:38:05.193Z DEBUG modem << +CSCON: 1
2021-06-28T06:38:05.199Z DEBUG modem << [00:12:55.298,522] [0m<inf> asset_tracker: RRC mode: Connected[0m