Asset Tracker V2, connecting problem to AWS Iot

RE: Asset Tracker V2, connecting problem to AWS Iot

Minyaev — Fri, 07 Jan 2022 15:42:13 GMT

Okay thanks well, I’ll try that later, and come back here,

RE: Asset Tracker V2, connecting problem to AWS Iot

Didrik Rokhaug — Fri, 07 Jan 2022 09:18:51 GMT

When using the asset_tracker_v2 with AWS, you are supposed to set up the corresponding web app as well: https://nordicsemiconductor.github.io/asset-tracker-cloud-docs/v1.8.x/docs/aws/GettingStarted/Index.html

If you haven't set that up yet, that might be why there is no configuration for the device.

RE: Asset Tracker V2, connecting problem to AWS Iot

Minyaev — Thu, 06 Jan 2022 17:02:40 GMT

In my AWS account/my_thing :

RE: Asset Tracker V2, connecting problem to AWS Iot

Didrik Rokhaug — Thu, 06 Jan 2022 13:37:19 GMT

[quote user="Didrik Rokhaug"]Where do you look for the data?[/quote]

Have you set up the web application?

RE: Asset Tracker V2, connecting problem to AWS Iot

Minyaev — Wed, 05 Jan 2022 18:15:05 GMT

Hello, Line 37

RE: Asset Tracker V2, connecting problem to AWS Iot

Didrik Rokhaug — Mon, 03 Jan 2022 16:23:48 GMT

Where do you look for the data?

From the log, it looks like everything is okay.

RE: Asset Tracker V2, connecting problem to AWS Iot

Minyaev — Wed, 29 Dec 2021 08:40:53 GMT

Yes, you are right, the certificates were loaded incorrectly, i reloaded it, and i don't have the error, but an other probleme, no data in my aws,

i checked the log file, and i see: "cloud_module: Device configuration empty!"

But my configuration is:

i don't know what is missing,

2021-12-29T08:24:20.790Z DEBUG modem << *** Booting Zephyr OS build v2.7.0-ncs1  ***
2021-12-29T08:24:20.792Z DEBUG modem << I: Starting bootloader
2021-12-29T08:24:20.793Z DEBUG modem << I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
2021-12-29T08:24:20.809Z DEBUG modem << I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
2021-12-29T08:24:20.813Z DEBUG modem << I: Boot source: none
2021-12-29T08:24:20.816Z DEBUG modem << I: Swap type: none
2021-12-29T08:24:20.888Z DEBUG modem << I: Bootloader chainload address offset: 0x10000
2021-12-29T08:24:20.891Z DEBUG modem << I: Jumping to the first image slot
2021-12-29T08:24:21.372Z DEBUG modem << *** Booting Zephyr OS build v2.7.0-ncs1  ***
2021-12-29T08:24:21.407Z DEBUG modem << [00:00:00.205,993] [1;33m<wrn> at_notif: Already initialized. Nothing to do[0m
2021-12-29T08:24:21.414Z DEBUG modem << [00:00:00.213,867] [0m<inf> event_manager: APP_EVT_START[0m
2021-12-29T08:24:21.416Z DEBUG modem << [00:00:00.220,672] [0m<inf> event_manager: DATA_EVT_CONFIG_INIT[0m
2021-12-29T08:24:21.419Z DEBUG modem << [00:00:00.227,416] [0m<inf> event_manager: APP_EVT_ACTIVITY_DETECTION_DISABLE[0m
2021-12-29T08:24:21.444Z DEBUG modem << [00:00:00.235,443] [0m<inf> event_manager: MODEM_EVT_INITIALIZED[0m
2021-12-29T08:24:21.497Z DEBUG modem << [00:00:00.324,127] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTING[0m
2021-12-29T08:24:22.780Z DEBUG modem << %C[00:00:01.605,651] [0m<inf> event_manager: MODEM_EVT_LTE_DISCONNECTED[0m
2021-12-29T08:24:22.787Z DEBUG modem << [00:00:01.612,945] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2021-12-29T08:24:22.825Z DEBUG modem << ESQ: 43,2,18,2
2021-12-29T08:24:23.409Z DEBUG modem << %CESQ: 45,2,23,3
2021-12-29T08:24:23.837Z DEBUG modem << [00:00:02.664,337] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTED[0m
2021-12-29T08:24:23.849Z DEBUG modem << [00:00:02.671,478] [0m<inf> event_manager: MODEM_EVT_LTE_PSM_UPDATE[0m
2021-12-29T08:24:23.853Z DEBUG modem << [00:00:02.678,955] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2021-12-29T08:24:23.866Z DEBUG modem << [00:00:02.687,225] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
2021-12-29T08:24:23.870Z DEBUG modem << [00:00:02.696,868] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m
2021-12-29T08:24:28.488Z DEBUG modem << [00:00:07.316,406] [0m<inf> event_manager: CLOUD_EVT_CONNECTED[0m
2021-12-29T08:24:28.524Z DEBUG modem << [00:00:07.323,242] [0m<inf> event_manager: DATA_EVT_DATE_TIME_OBTAINED[0m
2021-12-29T08:24:28.528Z DEBUG modem << [00:00:07.330,627] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS, MOD_STAT)[0m
2021-12-29T08:24:28.532Z DEBUG modem << [00:00:07.349,945] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
2021-12-29T08:24:28.537Z DEBUG modem << [00:00:07.356,628] [0m<inf> event_manager: GPS_EVT_AGPS_NEEDED[0m
2021-12-29T08:24:28.578Z DEBUG modem << [00:00:07.363,769] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
2021-12-29T08:24:28.642Z DEBUG modem << [00:00:07.468,933] [0m<inf> event_manager: DATA_EVT_AGPS_REQUEST_DATA_SEND[0m
2021-12-29T08:24:28.652Z DEBUG modem << [00:00:07.477,844] [0m<inf> event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY[0m
2021-12-29T08:24:28.663Z DEBUG modem << [00:00:07.486,267] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
2021-12-29T08:24:28.702Z DEBUG modem << [00:00:07.529,144] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
2021-12-29T08:24:28.748Z DEBUG modem << [00:00:07.575,714] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
2021-12-29T08:24:28.760Z DEBUG modem << [00:00:07.585,296] [0m<inf> event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2021-12-29T08:24:29.176Z DEBUG modem << [00:00:08.002,624] [1;33m<wrn> cloud_module: Device configuration empty![0m
2021-12-29T08:24:29.197Z DEBUG modem << [00:00:08.009,735] [0m<inf> event_manager: CLOUD_EVT_CONFIG_EMPTY[0m
2021-12-29T08:24:29.199Z DEBUG modem << [00:00:08.018,768] [0m<inf> event_manager: DATA_EVT_CONFIG_SEND[0m
2021-12-29T08:24:29.202Z DEBUG modem << [00:00:08.027,252] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
2021-12-29T08:24:46.344Z DEBUG modem << %CESQ: 41,2,14,2
2021-12-29T08:24:46.780Z DEBUG modem << %CESQ: 44,2,24,3
2021-12-29T08:24:54.447Z DEBUG modem << %CESQ: 255,0,255,0
2021-12-29T08:25:35.064Z DEBUG modem << [00:01:13.893,585] [0m<inf> event_manager: GPS_EVT_TIMEOUT[0m
2021-12-29T08:25:35.076Z DEBUG modem << [00:01:13.899,810] [0m<inf> event_manager: GPS_EVT_INACTIVE[0m
2021-12-29T08:25:35.086Z DEBUG modem << [00:01:13.906,738] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
2021-12-29T08:25:35.091Z DEBUG modem << [00:01:13.916,870] [0m<inf> event_manager: DATA_EVT_NEIGHBOR_CELLS_DATA_SEND[0m
2021-12-29T08:25:35.101Z DEBUG modem << [00:01:13.931,488] [0m<inf> event_manager: DATA_EVT_DATA_SEND[0m
2021-12-29T08:25:35.142Z DEBUG modem << [00:01:13.973,144] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
2021-12-29T08:25:35.150Z DEBUG modem << [00:01:13.981,414] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
2021-12-29T08:25:35.184Z DEBUG modem << %CESQ: 41,2,16,2

RE: Asset Tracker V2, connecting problem to AWS Iot

Didrik Rokhaug — Tue, 28 Dec 2021 14:51:38 GMT

-111 ECONNREFUSED indicates that there is something wrong with the device's provisioning.

Does it have the correct certificates, and are they in the correct sec_tag (the default in overlay-aws.conf is 42)?

RE: Asset Tracker V2, connecting problem to AWS Iot

Minyaev — Mon, 27 Dec 2021 16:48:08 GMT

hi, thank you that is better this time, i see the traces of AWS, but we have an other error:

"aws_iot: mqtt_connect, error: -111"

2021-12-27T16:44:02.528Z DEBUG modem << *** Booting Zephyr OS build v2.7.0-ncs1  ***
2021-12-27T16:44:02.548Z DEBUG modem << I: Starting bootloader
2021-12-27T16:44:02.550Z DEBUG modem << I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
2021-12-27T16:44:02.558Z DEBUG modem << I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
2021-12-27T16:44:02.561Z DEBUG modem << I: Boot source: none
2021-12-27T16:44:02.563Z DEBUG modem << I: Swap type: none
2021-12-27T16:44:02.637Z DEBUG modem << I: Bootloader chainload address offset: 0x10000
2021-12-27T16:44:02.640Z DEBUG modem << I: Jumping to the first image slot
2021-12-27T16:44:03.121Z DEBUG modem << *** Booting Zephyr OS build v2.7.0-ncs1  ***
2021-12-27T16:44:03.138Z DEBUG modem << [00:00:00.205,993] [1;33m<wrn> at_notif: Already initialized. Nothing to do[0m
2021-12-27T16:44:03.143Z DEBUG modem << [00:00:00.213,867] [0m<inf> event_manager: APP_EVT_START[0m
2021-12-27T16:44:03.241Z DEBUG modem << [00:00:00.220,672] [0m<inf> event_manager: DATA_EVT_CONFIG_INIT[0m
2021-12-27T16:44:03.244Z DEBUG modem << [00:00:00.227,416] [0m<inf> event_manager: APP_EVT_ACTIVITY_DETECTION_DISABLE[0m
2021-12-27T16:44:03.247Z DEBUG modem << [00:00:00.235,443] [0m<inf> event_manager: MODEM_EVT_INITIALIZED[0m
2021-12-27T16:44:03.250Z DEBUG modem << [00:00:00.318,267] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTING[0m
2021-12-27T16:44:04.650Z DEBUG modem << %C[00:00:01.727,172] [0m<inf> event_manager: MODEM_EVT_LTE_DISCONNECTED[0m
2021-12-27T16:44:04.673Z DEBUG modem << [00:00:01.734,466] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2021-12-27T16:44:04.676Z DEBUG modem << ESQ: 44,2,17,2
2021-12-27T16:44:05.700Z DEBUG modem << [00:00:02.778,686] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTED[0m
2021-12-27T16:44:05.722Z DEBUG modem << [00:00:02.785,736] [0m<inf> event_manager: MODEM_EVT_LTE_PSM_UPDATE[0m
2021-12-27T16:44:05.726Z DEBUG modem << [00:00:02.793,273] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2021-12-27T16:44:05.731Z DEBUG modem << [00:00:02.801,513] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
2021-12-27T16:44:05.743Z DEBUG modem << [00:00:02.811,187] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m
2021-12-27T16:44:06.977Z DEBUG modem << [00:00:04.055,328] [1;31m<err> aws_iot: mqtt_connect, error: -111[0m
2021-12-27T16:44:06.995Z DEBUG modem << [00:00:04.061,828] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m

RE: Asset Tracker V2, connecting problem to AWS Iot

Didrik Rokhaug — Mon, 27 Dec 2021 15:22:16 GMT

My appologies, it should be DOVERLAY_CONFIG, without the _ between D and OVERLAY.

I'll edit my previous reply as well.

Note that you will also need to set you AWS hostname in CONFIG_AWS_IOT_BROKER_HOST_NAME on line 18 in overlay-aws.conf.

RE: Asset Tracker V2, connecting problem to AWS Iot

Minyaev — Mon, 27 Dec 2021 14:30:26 GMT

The configuration Work, i have no errors like this:

I make like you suggested me:

But the problem is : no data in my AWS account, i verify it in "activity":

i have no traces that asset_tracker_V2 is trying to connect in my AWS account with MQTT :

2021-12-27T14:23:40.968Z INFO Application data folder: C:\Users\Portable\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2021-12-27T14:23:41.113Z DEBUG App pc-nrfconnect-linkmonitor v2.0.0 official
2021-12-27T14:23:41.114Z DEBUG App path: C:\Users\Portable\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-12-27T14:23:41.114Z DEBUG nRFConnect 3.9.1, required by the app is (^3.8.0)
2021-12-27T14:23:41.114Z DEBUG nRFConnect path: C:\Users\Portable\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-12-27T14:23:41.114Z DEBUG HomeDir: C:\Users\Portable
2021-12-27T14:23:41.114Z DEBUG TmpDir: C:\Users\Portable\AppData\Local\Temp
2021-12-27T14:23:43.409Z INFO Modem port is opened
2021-12-27T14:23:43.424Z DEBUG modem >> AT+CFUN?
2021-12-27T14:23:43.441Z DEBUG modem << +CFUN: 1
2021-12-27T14:23:43.444Z DEBUG modem << 
2021-12-27T14:23:43.447Z DEBUG modem << OK
2021-12-27T14:23:43.468Z DEBUG modem >> AT+CGSN=1
2021-12-27T14:23:43.485Z DEBUG modem << +CGSN: "352656109828478"
2021-12-27T14:23:43.487Z DEBUG modem << OK
2021-12-27T14:23:43.493Z DEBUG modem >> AT+CGMI
2021-12-27T14:23:43.509Z DEBUG modem << Nordic Semiconductor ASA
2021-12-27T14:23:43.519Z DEBUG modem << 
2021-12-27T14:23:43.521Z DEBUG modem << OK
2021-12-27T14:23:43.525Z DEBUG modem >> AT+CGMM
2021-12-27T14:23:43.533Z DEBUG modem << nRF9160-SICA
2021-12-27T14:23:43.535Z DEBUG modem << OK
2021-12-27T14:23:43.538Z DEBUG modem >> AT+CGMR
2021-12-27T14:23:43.544Z DEBUG modem << mfw_nrf9160_1.3.1
2021-12-27T14:23:43.548Z DEBUG modem << OK
2021-12-27T14:23:43.550Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.1] SerNr: 352656109828478
2021-12-27T14:23:43.555Z DEBUG modem >> AT+CEMODE?
2021-12-27T14:23:43.560Z DEBUG modem << +CEMODE: 2
2021-12-27T14:23:43.569Z DEBUG modem << OK
2021-12-27T14:23:43.585Z DEBUG modem >> AT%XCBAND=?
2021-12-27T14:23:43.604Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
2021-12-27T14:23:43.606Z DEBUG modem << OK
2021-12-27T14:23:43.621Z DEBUG modem >> AT+CMEE?
2021-12-27T14:23:43.636Z DEBUG modem << +CMEE: 0
2021-12-27T14:23:43.639Z DEBUG modem << OK
2021-12-27T14:23:43.644Z DEBUG modem >> AT+CMEE=1
2021-12-27T14:23:43.658Z DEBUG modem << OK
2021-12-27T14:23:43.671Z DEBUG modem >> AT+CNEC?
2021-12-27T14:23:43.677Z DEBUG modem << +CNEC: 0
2021-12-27T14:23:43.685Z DEBUG modem << OK
2021-12-27T14:23:43.693Z DEBUG modem >> AT+CNEC=24
2021-12-27T14:23:43.704Z DEBUG modem << OK
2021-12-27T14:23:43.708Z DEBUG modem >> AT+CGEREP?
2021-12-27T14:23:43.719Z DEBUG modem << +CGEREP: 0,0
2021-12-27T14:23:43.722Z DEBUG modem << OK
2021-12-27T14:23:43.725Z DEBUG modem >> AT+CGDCONT?
2021-12-27T14:23:43.735Z DEBUG modem << %C[00:00:01.473,632] [0m<inf> event_manager: MODEM_EVT_LTE_DISCONNECTED[0m
2021-12-27T14:23:43.737Z DEBUG modem << [00:00:01.480,926] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2021-12-27T14:23:43.740Z DEBUG modem << ESQ: 43,2,18,2
2021-12-27T14:23:43.742Z DEBUG modem << +CGDCONT: 0,"","","",0,0
2021-12-27T14:23:43.744Z DEBUG modem << OK
2021-12-27T14:23:44.105Z DEBUG modem >> AT+CGACT?
2021-12-27T14:23:44.115Z DEBUG modem << +CGACT: 0,0
2021-12-27T14:23:44.117Z DEBUG modem << OK
2021-12-27T14:23:44.125Z DEBUG modem >> AT+CGEREP=1
2021-12-27T14:23:44.132Z DEBUG modem << OK
2021-12-27T14:23:44.135Z DEBUG modem >> AT+CIND=1,1,1
2021-12-27T14:23:44.141Z DEBUG modem << OK
2021-12-27T14:23:44.143Z DEBUG modem >> AT+CEREG=5
2021-12-27T14:23:44.148Z DEBUG modem << OK
2021-12-27T14:23:44.153Z DEBUG modem >> AT+CEREG?
2021-12-27T14:23:44.160Z DEBUG modem << +CEREG: 5,2,"332C","0110B208",7
2021-12-27T14:23:44.166Z DEBUG modem << OK
2021-12-27T14:23:44.175Z DEBUG modem >> AT%CESQ=1
2021-12-27T14:23:44.184Z DEBUG modem << OK
2021-12-27T14:23:44.188Z DEBUG modem >> AT+CESQ
2021-12-27T14:23:44.194Z DEBUG modem << +CESQ: 99,99,255,255,19,42
2021-12-27T14:23:44.202Z DEBUG modem << 
2021-12-27T14:23:44.204Z DEBUG modem << OK
2021-12-27T14:23:44.211Z DEBUG modem >> AT%XSIM=1
2021-12-27T14:23:44.218Z DEBUG modem << OK
2021-12-27T14:23:44.221Z DEBUG modem >> AT%XSIM?
2021-12-27T14:23:44.226Z DEBUG modem << %XSIM: 1
2021-12-27T14:23:44.234Z DEBUG modem << OK
2021-12-27T14:23:44.241Z DEBUG modem >> AT+CPIN?
2021-12-27T14:23:44.253Z DEBUG modem << +CPIN: READY
2021-12-27T14:23:44.255Z DEBUG modem << OK
2021-12-27T14:23:44.261Z DEBUG modem >> AT+CPINR="SIM PIN"
2021-12-27T14:23:44.274Z DEBUG modem << +CPINR: "SIM PIN",3
2021-12-27T14:23:44.275Z DEBUG modem << OK
2021-12-27T14:23:44.285Z DEBUG modem >> AT+CIMI
2021-12-27T14:23:44.291Z DEBUG modem << 204080813637384
2021-12-27T14:23:44.293Z DEBUG modem << OK
2021-12-27T14:23:44.295Z INFO IMSIdentity: 204080813637384
2021-12-27T14:23:45.508Z DEBUG modem << +CGEV:[00:00:03.252,014] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTED[0m
2021-12-27T14:23:45.525Z DEBUG modem << [00:00:03.259,033] [0m<inf> event_manager: MODEM_EVT_LTE_PSM_UPDATE[0m
2021-12-27T14:23:45.543Z DEBUG modem <<  ME PDN ACT 0,0
2021-12-27T14:23:45.552Z DEBUG modem << +CNEC_ESM: 50,0
2021-12-27T14:23:45.572Z DEBUG modem << +CEREG: 5,"332C","0110B208",7,,,"00001010","11000010"
2021-12-27T14:23:45.584Z DEBUG modem << +CIND: "service",1
2021-12-27T14:23:45.596Z DEBUG modem << +CIND: "roam",1
2021-12-27T14:23:45.608Z DEBUG modem >> AT+COPS=3,2
2021-12-27T14:23:45.615Z DEBUG modem << [00:00:03.278,076] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2021-12-27T14:23:45.616Z DEBUG modem << [00:00:03.286,437] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
2021-12-27T14:23:45.625Z DEBUG modem << OK
2021-12-27T14:23:45.631Z DEBUG modem >> AT+COPS?
2021-12-27T14:23:45.637Z DEBUG modem << +COPS: 0,2,"20610",7
2021-12-27T14:23:45.640Z DEBUG modem << OK
2021-12-27T14:23:45.652Z DEBUG modem >> AT%XCBAND
2021-12-27T14:23:45.657Z DEBUG modem << %XCBAND: 20
2021-12-27T14:23:45.659Z DEBUG modem << 
2021-12-27T14:23:45.661Z DEBUG modem << OK
2021-12-27T14:23:45.673Z DEBUG modem >> AT+CGDCONT?
2021-12-27T14:23:45.684Z DEBUG modem << +CGDCONT: 0,"IP","ibasis.iot","10.160.50.109",0,0
2021-12-27T14:23:45.687Z DEBUG modem << OK
2021-12-27T14:23:45.694Z DEBUG modem >> AT+CGACT?
2021-12-27T14:23:45.704Z DEBUG modem << +CGACT: 0,1
2021-12-27T14:23:45.706Z DEBUG modem << OK
2021-12-27T14:23:50.093Z DEBUG modem << [00:00:07.837,036] [0m<inf> event_manager: CLOUD_EVT_CONFIG_RECEIVED[0m
2021-12-27T14:23:50.112Z DEBUG modem << [00:00:07.851,348] [0m<inf> event_manager: DATA_EVT_CONFIG_SEND[0m
2021-12-27T14:23:50.952Z DEBUG modem << [00:00:08.697,052] [0m<inf> event_manager: CLOUD_EVT_CONNECTED[0m
2021-12-27T14:23:50.959Z DEBUG modem << [00:00:08.703,826] [0m<inf> event_manager: DATA_EVT_DATE_TIME_OBTAINED[0m
2021-12-27T14:23:50.979Z DEBUG modem << [00:00:08.711,242] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS, MOD_STAT)[0m
2021-12-27T14:23:50.987Z DEBUG modem << [00:00:08.731,964] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
2021-12-27T14:23:51.003Z DEBUG modem << [00:00:08.738,647] [0m<inf> event_manager: GPS_EVT_AGPS_NEEDED[0m
2021-12-27T14:23:51.006Z DEBUG modem << [00:00:08.746,398] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
2021-12-27T14:23:51.107Z DEBUG modem << [00:00:08.849,182] [0m<inf> event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY[0m
2021-12-27T14:23:51.188Z DEBUG modem << [00:00:08.931,610] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
2021-12-27T14:23:51.233Z DEBUG modem << [00:00:08.975,585] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
2021-12-27T14:23:51.242Z DEBUG modem << [00:00:08.985,015] [0m<inf> event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2021-12-27T14:24:07.886Z DEBUG modem << [00:00:25.630,218] [0m<inf> event_manager: UI_EVT_BUTTON_DATA_READY[0m
2021-12-27T14:24:07.905Z DEBUG modem << [00:00:25.637,084] [0m<inf> event_manager: DATA_EVT_UI_DATA_READY[0m
2021-12-27T14:24:07.929Z DEBUG modem << [00:00:25.645,263] [0m<inf> event_manager: DATA_EVT_UI_DATA_SEND[0m
2021-12-27T14:24:07.933Z DEBUG modem << [00:00:25.654,174] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
2021-12-27T14:24:08.215Z DEBUG modem << %CESQ: 35,1,8,1
2021-12-27T14:24:08.269Z DEBUG modem << %CESQ: 41,2,17,2

i received successfully data to nRF cloud:

But not in my AWS Iot account, maybe i do something wrong, can you help me whit this,

if i use aws_iot, all work great, but my goal is that asset_tracker work whit AWS Iot

Thank you

Minyaev

RE: Asset Tracker V2, connecting problem to AWS Iot

Didrik Rokhaug — Mon, 27 Dec 2021 12:45:01 GMT

It's not enough to just provide the path of the overlay configuration file, you must provide the whole command line argument:

-DOVERLAY_CONFIG=overlay-aws.conf

Edit: I originally wrote -D_OVERLAY_CONFIG. That is wrong. It should be -DOVERLAY_CONFIG.

RE: Asset Tracker V2, connecting problem to AWS Iot

Minyaev — Mon, 27 Dec 2021 08:43:24 GMT

Hi,

Yes it was done, but nothing has changed,

That is my overlay file:

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

CONFIG_AWS_IOT=y
CONFIG_AWS_IOT_TOPIC_UPDATE_DELTA_SUBSCRIBE=y
CONFIG_AWS_IOT_TOPIC_GET_REJECTED_SUBSCRIBE=y
CONFIG_AWS_IOT_AUTO_DEVICE_SHADOW_REQUEST=y
CONFIG_AWS_IOT_MQTT_RX_TX_BUFFER_LEN=2048
CONFIG_AWS_IOT_APP_SUBSCRIPTION_LIST_COUNT=3
CONFIG_AWS_IOT_CLIENT_ID_APP=y
CONFIG_AWS_FOTA=y

# Options that must be configured in order to establish a connection.
CONFIG_AWS_IOT_SEC_TAG=42
CONFIG_AWS_IOT_BROKER_HOST_NAME="a1t6ipfx1jqfnp-ats.iot.us-west-2.amazonaws.com"

# MQTT Transport library
# Maximum specified MQTT keepalive timeout for AWS IoT is 1200 seconds.
CONFIG_MQTT_KEEPALIVE=1200

And that is my include configuration:

Thank

Minyaev

RE: Asset Tracker V2, connecting problem to AWS Iot

Didrik Rokhaug — Mon, 27 Dec 2021 06:49:47 GMT

Hi,

The assertion fail happens because you have told the application in the configuration options that you will not subscribe to any topics, while in the application you try to subscribe to some.

The reason for this mismatch is probably that you didn't include the AWS Kconfig overlay file. See this part of the Asset tracker V2 documentation: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/asset_tracker_v2/doc/asset_tracker_v2_description.html#building-with-overlays

The overlay file you want to add is called 'overlay-aws.conf'.

Best regards,

Didrik