Asset Tracker v2 data module timeouts not having effect

[zachary_z]

I have been experimenting with the data module configuration file, namely the Kconfig.data_module in Asset Tracker v2. Currently, my device (nRF9160 dev kit) sends data to nRF Cloud every 5 minutes, which I have observed in the serial terminal. Currently, I have tried to change the default value of DATA_ACTIVE_TIMEOUT_SECONDS, DATA_MOVEMENT_RESOLUTION_SECONDS, DATA_MOVEMENT_TIMEOUT_SECONDS and DATA_LOCATION_TIMEOUT_SECONDS ranging from 120 to 600 seconds, and the device still sends data every 5 minutes. I have compiled and flashed the program each time I have changed the values. If none of these parameters affect the data time interval, then what does affect it?

[dejans]

Hi,

The behavior of the application can be changed using real-time configurations which are updated through the nRF Cloud Service. The default values of the configuration options can be changed, but it is cloud service which determines the actual values. You can read more by following the first above-mentioned link. 
You can also look at the "change configuration" section in the nRF Cloud and asset_tracker_v2 blog post.
You could log in to nRF Cloud and go to "Device Management" -> "View Config" to check current configuration for your device on the nRF Cloud.

Best regards,
Dejan

[zachary_z]

Thank you for these! Is there a way to set up the device such that it ignores real-time configuration from the cloud?

[dejans]

Hi,

You could try to use optional library options to unsubscribe from the AWS IoT Device Shadow Topics by setting their values to "n".

Best regards,
Dejan

[dejans]

Hi,

Our developers suggest that you try to comment out the following line:

config_distribute(DATA_EVT_CONFIG_READY);

Best regards,
Dejan