Asset Tracker v2 application. How to subscribe to non-AWS specific topic:

RE: Asset Tracker v2 application. How to subscribe to non-AWS specific topic:

Didrik Rokhaug — Wed, 19 Jan 2022 09:46:08 GMT

Yes, opening a new ticket would be nice.

But in general, I recommend you read through the Asset Tracker v2 documentation.

It contains a lot of useful information about the application architecture, and how it can be extended.

RE: Asset Tracker v2 application. How to subscribe to non-AWS specific topic:

Jacek Majda — Tue, 18 Jan 2022 16:42:41 GMT

Problem solved.

Once I followed the recommended steps on how to use the Kconfig overlays, I was able to successfully build and run the application: asset_tracker_v2.

I am now able to see the battery voltage value (and its time stamp) reported from my nRF9160DK device to the shadow topics on the AWS IoT Core, every minute.

I am also able to see the button press data reported from my device to the AWS IoT Core topic: <IMEI>/messages.

As a next step, I would like to be able to see the data on the state (On/Off) of the sliding switches: sw1 and sw2 reported from my nRF9160DK device to a topic on AWS IoT Core , every 1 minute.

How can this be done? Shall I open a new ticket for this query?

RE: Asset Tracker v2 application. How to subscribe to non-AWS specific topic:

Didrik Rokhaug — Tue, 18 Jan 2022 11:03:29 GMT

No, overlay files are not automatically included.

This part of the asset_tracker_v2 documentation explains how to use Kconfig overlays: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/asset_tracker_v2/doc/asset_tracker_v2_description.html#building-with-overlays

RE: Asset Tracker v2 application. How to subscribe to non-AWS specific topic:

Jacek Majda — Tue, 18 Jan 2022 10:53:09 GMT

I did not take any action to include the overlay config in my build, as I assumed that this inclusion of the overlay config was already taken care of in some other files in the .src directory for asset_tracker_v2 application.

RE: Asset Tracker v2 application. How to subscribe to non-AWS specific topic:

Didrik Rokhaug — Tue, 18 Jan 2022 10:21:25 GMT

How did you include the overlay config in your build?

RE: Asset Tracker v2 application. How to subscribe to non-AWS specific topic:

Jacek Majda — Mon, 17 Jan 2022 17:12:03 GMT

Hi,

Yes, I did.

However, I did enable it NOT in the prj.conf file but only in the ovelay-aws.conf file, where many lines of code that used to be listed in the prj.conf file as AWS IoT mandatory application specific configurations for AWS IoT (under the nRF Connect SDK 1.7.0) , have now been placed, under nRF Connect SDK 1.8.0.

I attach copies of the ovelay-aws.conf file and the prj.conf file that I used with the application: asset_tracker_v2 ,using nRF Connect SDK 1.8.0.

Regards,

devzone.nordicsemi.com/.../overlay_2D00_aws-for-asset_5F00_tracker_5F00_v2.txt

devzone.nordicsemi.com/.../7651.prj.txt

RE: Asset Tracker v2 application. How to subscribe to non-AWS specific topic:

Didrik Rokhaug — Mon, 17 Jan 2022 16:04:37 GMT

When you disabled CONFIG_NRF_CLOUD_MQTT, did you remember to enable CONFIG_AWS_IOT?

RE: Asset Tracker v2 application. How to subscribe to non-AWS specific topic:

Jacek Majda — Sun, 16 Jan 2022 21:42:21 GMT

Hi,

After some further analysis and experimenting I found that the data about the button presses on my nRF9160DK device was in fact being sent from my device to the aws IoT Core and it was available in the aws IoT topic: <IMEI>/messages , as expected.

The only reason why I have not found this data was the incorrect value (number) that I was using for <IMEI> while trying to subscribe to the aws IoT topic: <IMEI>/messages.

Once I used the correct value (number) for the <IMEI> , as per data obtained from the modem of my nRF9160DK device, using AT command: AT+CGSN , this problem has been resolved and I was able to see both:

1. the data about the battery voltage (with its time stamp) sent from my device to the shadow topics of the aws IoT Core and

2. the data about the button presses on my device sent from my device to the topic: <IMEI>/messages on the aws IoT Core.

However, when I thought that this problem has been resolved or good, something happened on the 14th January 2022.

I started receiving messages like:

1. ERROR: cmake failed

2. create_nordic_project.py failed

3. CMake error at: C:/.../v1.7.0/zephyr/cmake/kconfig:268 (message): command failed with return code 1.

4. src/watchdog/kconfig - not found (in 'rsource "src/watchdog/kconfig")

As I run into problems on 14 January 2022 with creating Nordic projects using nRF Connect SDK 1.7.0 , I decided to upgrade to the latest version of the nRF Connect SDK 1.8.0 and I was able to successfully build and run the sample: AWS-IoT, using the nRF Connect SDK 1.8.0.

However, there were issues when I tried to build and run the application: Asset Tracker v2, using nRF Connect SDK 1.8.0.

In the past, when I was using the nRF Connect SDK 1.7.0 to build and run the application: Asset Tracker v2, I noticed that in order to be able to see the data sent from my nRF9160DK device to the AWS IoT in the relevant AWS IoT Core topics , I had to make the following changes in the prj.conf file for asset_tracker_v2 application:

I had to disable the following option (by setting it to 'n'): CONFIG_NRF_CLOUD_MQTT=n

and I had to enable the following option (by setting it to 'y'): CONFIG_AWS_IOT=y

However, when I was using the nRF Connect SDK 1.8.0 and I tried to disable (by setting it to 'n') the option: CONFIG_NRF_CLOUD_MQTT=n in the prj.conf file for app: asset_tracker_v2, I was unable to complete the process of "Build Solution" in Segger IDE, with the following error messages popping up: Build solution failed. Error was detected while compiling cloud_module.c. "A cloud transport service must be enabled".

And in order to be able to successfully complete the process of "Build Solution" by Segger IDE, I had to enable this option (by setting it to 'y') as follows: CONFIG_NRF_CLOUD_MQTT=y

This resulted in the successful build of the application: asset_tracker_v2, that I programmed into my nRF9160DK device.

Once my nRF9160DK was programmed with the above version of the "Build Solution" for application: asset_tracker_v2, I could see ,via the Link Monitor, that all activities on my nRF9160DK device were running as expected and that my device was communicating with AWS IoT Core.

However, I could not see any data from my device displayed in the relevant topics on the AWS IoT Core (neither in the shadow topics nor in the <IMEI>/messages topic). This was in contrast to my earlier experience with the same application: asset_tracker_v2, that was built using the nRF Connect SDK 1.7.0 with the following option disabled by 'n': CONFIG_NRF_CLOUD_MQTT=n.

What can be done to allow me to see the data sent from my nRF9160DK device to the AWS IoT Core, in the relevant topics of the AWS IoT Core that is: the shadow topics and the <IMEI>/messages topic?

From my experience, it seems that one needs to be able to successfully complete the "Build Solution" process in Segger IDE with the following option in the prj.conf file disabled by 'n': CONFIG_NRF_CLOUD_MQTT=n.

What is the solution to this problem?

Regards,

RE: Asset Tracker v2 application. How to subscribe to non-AWS specific topic:

Didrik Rokhaug — Tue, 28 Dec 2021 13:25:47 GMT

Hi,

[quote user=""]1. Is the non AWS specific topic the same as the application specific topic?[/quote]

Yes. They are topics that AWS doesn't use for some special/predifined purpose. Note that they are not allowed to start with $.

[quote user=""]2. If I need to insert the section of code from the main.c of the sample: AWS-IoT to the main.c of the app: Asset Tracker v2 (in order to be able to see the data in the AWS IoT topic: <imei>/messages) , where exactly shall I insert this section of code in the main.c source file for app: Asset Tracker v2 (or may be in another source .c file for this app)?[/quote]

The cloud_wrap_*_send() functions might be the best place: https://github.com/nrfconnect/sdk-nrf/blob/main/applications/asset_tracker_v2/src/cloud/aws_iot_integration.c#L380-L540

Best regards,

Didrik