The device supports runtime configurations that allow you to modify the template's behavior without firmware updates.
The template uses runtime parameters to control data sampling and cloud update behavior. Cloud updates are triggered when the number of stored samples reaches a configurable threshold. These updates include sending data, checking for FOTA jobs, and retrieving configuration/command updates. For implementation details, see Configuration Flow.
| Parameter | Description | Unit | Valid range | Static configuration |
|---|---|---|---|---|
sample_interval |
Sample interval | Seconds | 1 to 4294967295 | CONFIG_APP_SAMPLING_INTERVAL_SECONDS (default: 600) |
storage_threshold |
Number of records to store before triggering a cloud update | Records | 1 to CONFIG_APP_STORAGE_MAX_RECORDS_PER_TYPE |
CONFIG_APP_STORAGE_INITIAL_THRESHOLD (default: 1) |
You can set the runtime configurations through the cloud device shadow and they will override the compile-time Kconfig defaults shown in the Static Configuration column.
The complete device shadow structure is defined in the CDDL schema at Asset-Tracker-Template/app/src/cbor/device_shadow.cddl. This schema specifies all supported configuration parameters, commands, and their valid value ranges.