This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Asset Tracker V2 - How to enable passive mode

Is there a straight forward guide that demonstrates how to changes the Asset Tracker V2 application from "Active Mode" to "Passive Mode"?

Referencing the notes on the application:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/asset_tracker_v2/README.html#nrf-cloud-limitations

The option CONFIG_DATA_DEVICE_MODE must be changed

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/asset_tracker_v2/README.html#cmdoption-arg-CONFIG_DATA_DEVICE_MODE

Does this change occur before building the config? The latest firmware already comes with .hex application file, can "Active" and "Passive" modes be toggled with an application already built.  

I have been unable to find an obvious answer from the documentation.  Any clarity is greatly appreciated.

Parents
  • Hei JMaze,

    I assume you are using the asset_tracker_v2 sample with nRF Connect for Cloud.

    In this case, and with the pre-built HEX file that connects to nRF Connect for Cloud, the default compile time value of CONFIG_DATA_DEVICE_MODE is enabled, meaning the device is in active mode.

    In order to enable passive mode at runtime, you need to set the "activeMode" property to false in the device shadow, as documented here:

    The nRF Cloud web application does not support the manipulation of real-time configurations. However, this is possible by using the REST API calls described in nRF Cloud Patch Device State. To manipulate the device configuration, the desired section of the device state must be populated with the desired configuration of the device. The following schema sets the various device configuration parameters to their default values:

    {
              "desired":{
                      "config":{
                              "activeMode":true,
                              "activeWaitTime":120,
                              "movementTimeout":3600,
                              "movementResolution":120,
                              "gpsTimeout":60,
                              "movementThreshold":10
                      }
              }
      }
Reply
  • Hei JMaze,

    I assume you are using the asset_tracker_v2 sample with nRF Connect for Cloud.

    In this case, and with the pre-built HEX file that connects to nRF Connect for Cloud, the default compile time value of CONFIG_DATA_DEVICE_MODE is enabled, meaning the device is in active mode.

    In order to enable passive mode at runtime, you need to set the "activeMode" property to false in the device shadow, as documented here:

    The nRF Cloud web application does not support the manipulation of real-time configurations. However, this is possible by using the REST API calls described in nRF Cloud Patch Device State. To manipulate the device configuration, the desired section of the device state must be populated with the desired configuration of the device. The following schema sets the various device configuration parameters to their default values:

    {
              "desired":{
                      "config":{
                              "activeMode":true,
                              "activeWaitTime":120,
                              "movementTimeout":3600,
                              "movementResolution":120,
                              "gpsTimeout":60,
                              "movementThreshold":10
                      }
              }
      }
Children
Related