Hi,
I am trying to evaluate the asset_tracker_v2 on the thingy91, and its low-power items.
Perhaps I am missing something, but changing the config in the cloud seems to be untrivial, so at this point I am forcing the mode to passive in code. (otherwise, if it ran once, it will store "active mode" as the config in the flash anyway, regardless of CONFIG_DATA_DEVICE_MODE). After like 3 minutes, the "led" eventually starts becoming dark blue and slow breathing (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/asset_tracker_v2/README.html) meaning it is in passive mode. I can also tell by the logs that it is enabling APP_EVT_ACTIVITY_DETECTION_ENABLE (detection based on accelero movement) at this time.
However, I never seem to get any result from "shaking" the board. => It does not react/detect this.
As far I imagine, the thresholds are all default. I breaked through the debugger, and verified that ext_sensors_accelerometer_trigger_callback_set really is called. However, accelerometer_trigger_handler is never called. I'd expect the accelero to trigger an interrupt, causing zephyr to call that from some interrupt-triggered context, but that doesnt happen.
From the user guide, it also states that there is INT1 and INT2 on both accelero's, and that INT2 isn't connected. But.. I am assuming the trigger comes from INT1? (I did not double check the zephyr driver, dts, etc, but I would image the demo just working on the board, hence INT1 is the logical choice)
Any idea what is going wrong? I imagined firing up the demo would be a bit more plug-and-play that I am getting now. Is the accelero-trigger behavior supported?
(Note: I also disabled the GPS mode, as I have difficulties getting a lock. But I was just checking the accelero behavior now)
Thanks for your feedback,
Arnout
