Asset Tracker V2 and AWS Cloud

RE: Asset Tracker V2 and AWS Cloud

Albrecht Markus Schellenberger — Wed, 01 Dec 2021 13:40:04 GMT

[quote user="tracking"]but i still have problems, I think there are missing configurations that are not clarified in the step guide.[/quote]

If you are using NCS v1.7.1, then I’m not really able to explain:

[quote user=""]CONFIG_AWS_IOT_APP_SUBSCRIPTION_LIST_COUNT=2[/quote]

in your prj.conf.

[quote user="tracking"]If I have the code without editing it.[/quote]

Because you said you use the application without any modifications, right? In NCS v1.7.1, CONFIG_AWS_IOT_APP_SUBSCRIPTION_LIST_COUNT is 3, which is aligned to APP_SUB_TOPICS_COUNT.

Regards,

Markus

RE: Asset Tracker V2 and AWS Cloud

tracking — Wed, 01 Dec 2021 13:28:32 GMT

Hi Markus :)

I use the version v1.7.1.

APP_SUB_TOPICS_COUNT = 3 ,

but i still have problems, I think there are missing configurations that are not clarified in the step guide. From already thank you very much

RE: Asset Tracker V2 and AWS Cloud

Albrecht Markus Schellenberger — Wed, 01 Dec 2021 13:12:44 GMT

Hello Agustin,

[quote user="tracking"]How many themes should I put? If I have the code without editing it.[/quote]

Could you check the value of APP_SUB_TOPICS_COUNT in aws_iot_integration.c and match CONFIG_AWS_IOT_APP_SUBSCRIPTION_LIST_COUNT with this value?

By the way, which NCS version are using?

Regards,

Markus

RE: Asset Tracker V2 and AWS Cloud

tracking — Tue, 30 Nov 2021 12:27:55 GMT

Hi Markus :)

How many themes should I put? If I have the code without editing it.

RE: Asset Tracker V2 and AWS Cloud

Albrecht Markus Schellenberger — Mon, 29 Nov 2021 14:45:02 GMT

Hello Agustin,

could you please check the number of application specific topics that will be sent into the AWS IoT client library from aws_iot_integration.c? The number has to match CONFIG_AWS_IOT_APP_SUBSCRIPTION_LIST_COUNT.

Regards,

Markus

RE: Asset Tracker V2 and AWS Cloud

tracking — Fri, 26 Nov 2021 15:26:36 GMT

Hi, ok.

Thanks

2021-11-26T15:20:47.532Z VERBOSE Using nrfjprog dll version: 10.12.1
2021-11-26T15:20:47.532Z VERBOSE Using JLink version: 6.88a
2021-11-26T15:20:47.600Z DEBUG App pc-nrfconnect-linkmonitor v2.0.0 official
2021-11-26T15:20:47.601Z DEBUG App path: C:\Users\aeavi\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-11-26T15:20:47.601Z DEBUG nRFConnect 3.8.0 is not supported by the app (^3.8.0)
2021-11-26T15:20:47.601Z DEBUG nRFConnect path: C:\Users\aeavi\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-11-26T15:20:47.601Z DEBUG HomeDir: C:\Users\aeavi
2021-11-26T15:20:47.601Z DEBUG TmpDir: C:\Users\aeavi\AppData\Local\Temp
2021-11-26T15:20:49.775Z INFO Modem port is opened
2021-11-26T15:20:49.788Z DEBUG modem >> AT+CFUN?
2021-11-26T15:20:49.821Z DEBUG modem << +CFUN: 0
2021-11-26T15:20:49.824Z DEBUG modem << OK
2021-11-26T15:20:51.661Z DEBUG modem >> AT+CFUN=1
2021-11-26T15:20:51.707Z DEBUG modem << OK
2021-11-26T15:20:52.909Z DEBUG modem >> AT+CFUN?
2021-11-26T15:20:52.924Z DEBUG modem << +CFUN: 1
2021-11-26T15:20:52.937Z DEBUG modem << OK
2021-11-26T15:20:52.942Z DEBUG modem >> AT+CGSN=1
2021-11-26T15:20:52.952Z DEBUG modem << +CGSN: "imei-private"
2021-11-26T15:20:52.955Z DEBUG modem << OK
2021-11-26T15:20:52.966Z DEBUG modem >> AT+CGMI
2021-11-26T15:20:52.983Z DEBUG modem << Nordic Semiconductor ASA
2021-11-26T15:20:52.987Z DEBUG modem << OK
2021-11-26T15:20:52.991Z DEBUG modem >> AT+CGMM
2021-11-26T15:20:53.007Z DEBUG modem << nRF9160-SICA
2021-11-26T15:20:53.009Z DEBUG modem << OK
2021-11-26T15:20:53.019Z DEBUG modem >> AT+CGMR
2021-11-26T15:20:53.038Z DEBUG modem << mfw_nrf9160_1.3.1
2021-11-26T15:20:53.040Z DEBUG modem << OK
2021-11-26T15:20:53.041Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.1] SerNr: 352656106101499
2021-11-26T15:20:53.050Z DEBUG modem >> AT+CEMODE?
2021-11-26T15:20:53.068Z DEBUG modem << +CEMODE: 2
2021-11-26T15:20:53.073Z DEBUG modem << OK
2021-11-26T15:20:53.091Z DEBUG modem >> AT%XCBAND=?
2021-11-26T15:20:53.107Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
2021-11-26T15:20:53.116Z DEBUG modem << OK
2021-11-26T15:20:53.136Z DEBUG modem >> AT+CMEE?
2021-11-26T15:20:53.146Z DEBUG modem << +CMEE: 0
2021-11-26T15:20:53.148Z DEBUG modem << OK
2021-11-26T15:20:53.151Z DEBUG modem >> AT+CMEE=1
2021-11-26T15:20:53.169Z DEBUG modem << OK
2021-11-26T15:20:53.174Z DEBUG modem >> AT+CNEC?
2021-11-26T15:20:53.186Z DEBUG modem << +CNEC: 0
2021-11-26T15:20:53.189Z DEBUG modem << OK
2021-11-26T15:20:53.193Z DEBUG modem >> AT+CNEC=24
2021-11-26T15:20:53.203Z DEBUG modem << OK
2021-11-26T15:20:53.206Z DEBUG modem >> AT+CGEREP?
2021-11-26T15:20:53.217Z DEBUG modem << +CGEREP: 0,0
2021-11-26T15:20:53.221Z DEBUG modem << OK
2021-11-26T15:20:53.223Z DEBUG modem >> AT+CGDCONT?
2021-11-26T15:20:53.234Z DEBUG modem << +CGDCONT: 0,"","","",0,0
2021-11-26T15:20:53.238Z DEBUG modem << OK
2021-11-26T15:20:53.257Z DEBUG modem >> AT+CGACT?
2021-11-26T15:20:53.270Z DEBUG modem << +CGACT: 0,0
2021-11-26T15:20:53.273Z DEBUG modem << OK
2021-11-26T15:20:53.291Z DEBUG modem >> AT+CGEREP=1
2021-11-26T15:20:53.304Z DEBUG modem << OK
2021-11-26T15:20:53.307Z DEBUG modem >> AT+CIND=1,1,1
2021-11-26T15:20:53.318Z DEBUG modem << OK
2021-11-26T15:20:53.323Z DEBUG modem >> AT+CEREG=5
2021-11-26T15:20:53.334Z DEBUG modem << OK
2021-11-26T15:20:53.340Z DEBUG modem >> AT+CEREG?
2021-11-26T15:20:53.353Z DEBUG modem << +CEREG: 5,2,"6787","0016FB04",7
2021-11-26T15:20:53.357Z DEBUG modem << OK
2021-11-26T15:20:53.377Z DEBUG modem >> AT%CESQ=1
2021-11-26T15:20:53.390Z DEBUG modem << OK
2021-11-26T15:20:53.405Z DEBUG modem >> AT+CESQ
2021-11-26T15:20:53.419Z DEBUG modem << +CESQ: 99,99,255,255,1,24
2021-11-26T15:20:53.422Z DEBUG modem << OK
2021-11-26T15:20:53.440Z DEBUG modem >> AT%XSIM=1
2021-11-26T15:20:53.446Z DEBUG modem << %CESQ: 24,1,2,0
2021-11-26T15:20:53.471Z DEBUG modem << OK
2021-11-26T15:20:53.486Z DEBUG modem >> AT%XSIM?
2021-11-26T15:20:53.505Z DEBUG modem << %XSIM: 1
2021-11-26T15:20:53.508Z DEBUG modem << OK
2021-11-26T15:20:53.539Z DEBUG modem >> AT+CPIN?
2021-11-26T15:20:53.550Z DEBUG modem << +CPIN: READY
2021-11-26T15:20:53.553Z DEBUG modem << OK
2021-11-26T15:20:53.573Z DEBUG modem >> AT+CPINR="SIM PIN"
2021-11-26T15:20:53.586Z DEBUG modem << +CPINR: "SIM PIN",3
2021-11-26T15:20:53.588Z DEBUG modem << OK
2021-11-26T15:20:53.604Z DEBUG modem >> AT+CIMI
2021-11-26T15:20:53.621Z DEBUG modem << 204080813633967
2021-11-26T15:20:53.624Z DEBUG modem << OK
2021-11-26T15:20:53.634Z INFO IMSIdentity: 204080813633967
2021-11-26T15:20:58.337Z DEBUG modem << +CGEV: ME PDN ACT 0,0
2021-11-26T15:20:58.342Z DEBUG modem << +CNEC_ESM: 50,0
2021-11-26T15:20:58.346Z DEBUG modem << +CEREG: 5,"6787","0016FB04",7,,,"11100000","11100000"
2021-11-26T15:20:58.354Z DEBUG modem << [00:00:14.278,015] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTED[0m
2021-11-26T15:20:58.355Z DEBUG modem << [00:00:14.284,942] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2021-11-26T15:20:58.356Z DEBUG modem << [00:00:14.292,083] [0m<inf> event_manager: MODEM_EVT_LTE_PSM_UPDATE[0m
2021-11-26T15:20:58.358Z DEBUG modem << +CIND: "service",1
2021-11-26T15:20:58.362Z DEBUG modem << +CIND: "roam",1
2021-11-26T15:20:58.443Z DEBUG modem >> AT+CGDCONT?
2021-11-26T15:20:58.454Z DEBUG modem << +CGDCONT: 0,"IP","ibasis.iot","10.165.136.234",0,0
2021-11-26T15:20:58.456Z DEBUG modem << OK
2021-11-26T15:20:58.474Z DEBUG modem >> AT+COPS=3,2
2021-11-26T15:20:58.488Z DEBUG modem << OK
2021-11-26T15:20:58.492Z DEBUG modem >> AT+CGACT?
2021-11-26T15:20:58.507Z DEBUG modem << +CGACT: 0,1
2021-11-26T15:20:58.516Z DEBUG modem << OK
2021-11-26T15:20:58.534Z DEBUG modem >> AT+COPS?
2021-11-26T15:20:58.547Z DEBUG modem << +COPS: 0,2,"722310",7
2021-11-26T15:20:58.551Z DEBUG modem << OK
2021-11-26T15:20:58.571Z DEBUG modem >> AT%XCBAND
2021-11-26T15:20:58.582Z DEBUG modem << %XCBAND: 28
2021-11-26T15:20:58.584Z DEBUG modem << OK
2021-11-26T15:20:58.589Z DEBUG modem >> AT+CGDCONT?
2021-11-26T15:20:58.601Z DEBUG modem << +CGDCONT: 0,"IP","ibasis.iot","10.165.136.234",0,0
2021-11-26T15:20:58.604Z DEBUG modem << OK
2021-11-26T15:20:58.621Z DEBUG modem >> AT+CGACT?
2021-11-26T15:20:58.636Z DEBUG modem << +CGACT: 0,1
2021-11-26T15:20:58.639Z DEBUG modem << OK
2021-11-26T15:21:07.706Z DEBUG modem << %CESQ: 25,1,9,1
2021-11-26T15:21:12.825Z DEBUG modem << %CESQ: 24,1,3,0
2021-11-26T15:21:14.464Z DEBUG modem << [00:00:30.424,835] [1;31m<err> util_module: Rebooting![0m
2021-11-26T15:21:15.316Z DEBUG modem << *** Booting Zephyr OS build v2.6.99-ncs1-1  ***
2021-11-26T15:21:15.353Z DEBUG modem << [00:00:00.245,330] [0m<inf> event_manager: APP_EVT_START[0m
2021-11-26T15:21:15.388Z DEBUG modem << [00:00:00.265,563] [0m<inf> event_manager: DATA_EVT_CONFIG_INIT[0m
2021-11-26T15:21:15.389Z DEBUG modem << [00:00:00.272,064] [0m<inf> event_manager: APP_EVT_ACTIVITY_DETECTION_DISABLE[0m
2021-11-26T15:21:15.390Z DEBUG modem << [00:00:00.279,846] [0m<inf> event_manager: MODEM_EVT_INITIALIZED[0m
2021-11-26T15:21:15.446Z DEBUG modem << [00:00:00.294,311] [1;31m<err> aws_iot: Application subscription list count mismatch[0m
2021-11-26T15:21:15.447Z DEBUG modem << [00:00:00.302,917] [1;31m<err> aws_iot_integration: cloud_ep_subscriptions_add, error: -122[0m
2021-11-26T15:21:15.450Z DEBUG modem << [00:00:00.311,340] [1;31m<err> aws_iot_integration: populate_app_endpoint_topics, error: -122[0m
2021-11-26T15:21:15.451Z DEBUG modem << [00:00:00.319,946] [1;31m<err> cloud_module: cloud_wrap_init, error: -122[0m
2021-11-26T15:21:15.452Z DEBUG modem << ASSERTION FAIL [err == 0] @ ../src/modules/cloud_module.c:719
2021-11-26T15:21:15.453Z DEBUG modem << setp() failed
2021-11-26T15:21:15.454Z DEBUG modem << [00:00:00.333,618] [1;31m<err> os: r0/a1:  0x00000004  r1/a2:  0x000002cf  r2/a3:  0x00000001[0m
2021-11-26T15:21:15.625Z DEBUG modem << [00:00:00.342,224] [1;31m<err> os: r3/a4:  0x00024dc1 r12/ip:  0x0000a000 r14/lr:  0x0001c379[0m
2021-11-26T15:21:15.626Z DEBUG modem << [00:00:00.350,830] [1;31m<err> os:  xpsr:  0x41000000[0m
2021-11-26T15:21:15.627Z DEBUG modem << [00:00:00.355,987] [1;31m<err> os: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000[0m
2021-11-26T15:21:15.628Z DEBUG modem << [00:00:00.366,302] [1;31m<err> os: s[ 4]:  0x00000000  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x00000000[0m
2021-11-26T15:21:15.628Z DEBUG modem << [00:00:00.376,617] [1;31m<err> os: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000002[0m
2021-11-26T15:21:15.629Z DEBUG modem << [00:00:00.386,962] [1;31m<err> os: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000[0m
2021-11-26T15:21:15.629Z DEBUG modem << [00:00:00.397,277] [1;31m<err> os: fpscr:  0x00000000[0m
2021-11-26T15:21:15.630Z DEBUG modem << [00:00:00.402,435] [1;31m<err> os: Faulting instruction address (r15/pc): 0x0003e8cc[0m
2021-11-26T15:21:15.631Z DEBUG modem << [00:00:00.410,278] [1;31m<err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0[0m
2021-11-26T15:21:15.631Z DEBUG modem << [00:00:00.417,907] [1;31m<err> os: Current thread: 0x20015130 (unknown)[0m
2021-11-26T15:21:15.632Z DEBUG modem << ASSERTION FAIL [reason != K_ERR_KERNEL_PANIC] @ WEST_TOPDIR/zephyr/kernel/fatal.c:143
2021-11-26T15:21:15.632Z DEBUG modem << Attempted to recover from a kernel panic condition
2021-11-26T15:21:15.634Z DEBUG modem << [00:00:00.436,676] [1;31m<err> os: ***** HARD FAULT *****[0m
2021-11-26T15:21:15.634Z DEBUG modem << [00:00:00.442,169] [1;31m<err> os:   Fault escalation (see below)[0m
2021-11-26T15:21:15.635Z DEBUG modem << [00:00:00.448,394] [1;31m<err> os: r0/a1:  0x00000004  r1/a2:  0x0000008f  r2/a3:  0x00000001[0m
2021-11-26T15:21:15.636Z DEBUG modem << [00:00:00.457,000] [1;31m<err> os: r3/a4:  0x00024dc1 r12/ip:  0x0000a000 r14/lr:  0x00037db3[0m
2021-11-26T15:21:15.636Z DEBUG modem << [00:00:00.465,606] [1;31m<err> os:  xpsr:  0x4100000b[0m
2021-11-26T15:21:15.637Z DEBUG modem << [00:00:00.470,764] [1;31m<err> os: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000[0m
2021-11-26T15:21:15.638Z DEBUG modem << [00:00:00.481,079] [1;31m<err> os: s[ 4]:  0x00000000  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x00000000[0m
2021-11-26T15:21:15.639Z DEBUG modem << [00:00:00.491,424] [1;31m<err> os: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000000[0m
2021-11-26T15:21:15.639Z DEBUG modem << [00:00:00.501,770] [1;31m<err> os: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000[0m
2021-11-26T15:21:15.640Z DEBUG modem << [00:00:00.512,084] [1;31m<err> os: fpscr:  0x00000001[0m
2021-11-26T15:21:15.727Z DEBUG modem << [00:00:00.517,242] [1;31m<err> os: Faulting instruction address (r15/pc): 0x0003e8cc[0m
2021-11-26T15:21:15.730Z DEBUG modem << [00:00:00.525,085] [1;31m<err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0[0m
2021-11-26T15:21:15.731Z DEBUG modem << [00:00:00.532,836] [1;31m<err> os: Fault during interrupt handling
2021-11-26T15:21:15.732Z DEBUG modem << [0m
2021-11-26T15:21:15.733Z DEBUG modem << [00:00:00.539,215] [1;31m<err> os: Current thread: 0x20015130 (unknown)[0m
2021-11-26T15:21:15.734Z DEBUG modem << [00:00:00.545,959] [0m<inf> event_manager: UTIL_EVT_SHUTDOWN_REQUEST[0m
2021-11-26T15:21:15.735Z DEBUG modem << [00:00:00.553,009] [0m<inf> event_manager: UI_EVT_SHUTDOWN_READY[0m
2021-11-26T15:21:15.736Z DEBUG modem << [00:00:00.559,173] [1;33m<wrn> modules_common: Module "ui" shutdown registered[0m
2021-11-26T15:21:15.737Z DEBUG modem << [00:00:00.566,558] [0m<inf> event_manager: GPS_EVT_SHUTDOWN_READY[0m
2021-11-26T15:21:15.737Z DEBUG modem << [00:00:00.572,875] [1;33m<wrn> modules_common: Module "gps" shutdown registered[0m
2021-11-26T15:21:15.738Z DEBUG modem << [00:00:00.580,688] [0m<inf> event_manager: APP_EVT_SHUTDOWN_READY[0m
2021-11-26T15:21:15.738Z DEBUG modem << [00:00:00.586,944] [1;33m<wrn> modules_common: Module "app" shutdown registered[0m
2021-11-26T15:21:15.739Z DEBUG modem << [00:00:00.594,909] [0m<inf> event_manager: SENSOR_EVT_SHUTDOWN_READY[0m
2021-11-26T15:21:15.740Z DEBUG modem << [00:00:00.601,593] [1;33m<wrn> modules_common: Module "sensor" shutdown registered[0m
2021-11-26T15:21:15.740Z DEBUG modem << [00:00:00.609,680] [0m<inf> event_manager: DATA_EVT_SHUTDOWN_READY[0m
2021-11-26T15:21:15.741Z DEBUG modem << [00:00:00.615,997] [1;33m<wrn> modules_common: Module "data" shutdown registered[0m
2021-11-26T15:21:15.789Z DEBUG modem << [00:00:00.681,152] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTING[0m
2021-11-26T15:21:15.806Z DEBUG modem << +CEREG: 0
2021-11-26T15:21:15.815Z DEBUG modem << [00:00:00.690,734] [0m<inf> event_manager: MODEM_EVT_LTE_DISCONNECTED[0m
2021-11-26T15:21:15.816Z DEBUG modem << [00:00:00.697,906] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2021-11-26T15:21:17.342Z DEBUG modem << [00:00:02.225,830] [0m<inf> event_manager: MODEM_EVT_SHUTDOWN_READY[0m
2021-11-26T15:21:17.343Z DEBUG modem << [00:00:02.232,421] [1;33m<wrn> modules_common: Module "modem" shutdown registered[0m

RE: Asset Tracker V2 and AWS Cloud

Albrecht Markus Schellenberger — Fri, 26 Nov 2021 15:19:19 GMT

Thanks a lot! May I ask for the complete application log in text format, as it will be easier for me to analyse? :-) You can do that by clicking the button below and copy/pasting the output as code here in this ticket.

Thanks and regards,

//Markus

RE: Asset Tracker V2 and AWS Cloud

tracking — Fri, 26 Nov 2021 14:34:13 GMT

RE: Asset Tracker V2 and AWS Cloud

Albrecht Markus Schellenberger — Fri, 26 Nov 2021 13:37:14 GMT

[quote user="tracking"]Hello, thank you very much for answering.
I don't understand what you mean by a complete record. so I can show you.
I just followed the steps mentioned above, in Asset Tracker v2. I clarify that I am only trying to upload the GPS data to the AWS cloud.[/quote]

By a complete record, I mean the output of the Asset Tracker v2 from your device logged by a serial terminal. You can read more about logging here.

Regards,

Markus

RE: Asset Tracker V2 and AWS Cloud

tracking — Fri, 26 Nov 2021 13:14:32 GMT

Hello, thank you very much for answering. 
I don't understand what you mean by a complete record. so I can show you.
 I just followed the steps mentioned above, in Asset Tracker v2.

I clarify that I am only trying to upload the GPS data to the AWS cloud.

Thank you

Agustin.

Introducción — nRF Asset Tracker fc63f7fba8e6fe9e1ceae344d90b30d03292f92f documentation (nordicsemiconductor.github.io)

RE: Asset Tracker V2 and AWS Cloud

Albrecht Markus Schellenberger — Fri, 26 Nov 2021 12:55:02 GMT

[quote user="tracking"]well, thank you very much for answering. First, if I use aws iot I can receive the messages in the aws cloud, but when I follow the steps to use the asset tracker v2 I do not receive anything in aws cloud. The configuration of the files that the steps say leave them in the first message.[/quote]

Without a full application log showing the issue you are facing I will not be able to help you very much, I’m afraid.

Regards,

Markus

RE: Asset Tracker V2 and AWS Cloud

tracking — Thu, 25 Nov 2021 23:28:26 GMT

Introducción — nRF Asset Tracker fc63f7fba8e6fe9e1ceae344d90b30d03292f92f documentation (nordicsemiconductor.github.io)

RE: Asset Tracker V2 and AWS Cloud

tracking — Thu, 25 Nov 2021 23:26:49 GMT

well, thank you very much for answering. First, if I use aws iot I can receive the messages in the aws cloud, but when I follow the steps to use the asset tracker v2 I do not receive anything in aws cloud. The configuration of the files that the steps say leave them in the first message.

RE: Asset Tracker V2 and AWS Cloud

Albrecht Markus Schellenberger — Tue, 16 Nov 2021 08:28:13 GMT

Hello,

could you please provide me with a full application log starting from device boot, that shows the connection issues you are facing?

Thanks and regards,

//Markus