Nordic Thingy 91 Low power version of Asset tracker v2 now does not send Barometric pressure nor button press data

[iarakis]

Hi,

I followed the procedure described here with Nordic Thingy 91 https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/nowi-powered-energy-autonomous-nordic-thingy-91-platform

and now it works with low power consumption and sends data to NrfCloud, that is fine.

However, after adding the prj.conf file, now it does not send emvironmental pressure and button press values. How can still receilve those values into NrfCloud, along with temperature and moisture that I already receive?

Regards

[Simonr]

Hi

If you check out the prj.conf file, you can see that a lot of configs has been disabled, like the CONFIG_LED_CONTROL, the serial interface, and a lot of log event configs has been set to "n". You can't expect super low current consumption and being able to get continuous logging information I'm afraid. You'll need to enable the configs you need again if you still want environmental pressure and button press values, etc.

Best regards,

Simon

[iarakis]

I managed to configure so that I receive also button presses. But I don´t receive atmosferic pressure. What should I enable to receive pressure data?

[Markus Tacker (he/him)]

Looks like the connection indicator on nRF Cloud UI is not working properly.

It looks like your device is able to send data to the cloud, while at the same time nRF Cloud UI reports the device as disconnected.

Could you verify that the message your device is sending arrives on the cloud side? You will find all messages received by nRF Cloud using the ListMessages REST endpoint. If the endpoint returns your messages, and you can verify that your device keeps sending in more messages, then you (and your device) are fine, and it's a bug with the connection indicator.

[iarakis]

But once it shows as disconnected, I can see no data into NRFCLOUD dashboard.

[Markus Tacker (he/him)]

The fetching of new data on the web UI is stopped because device is considered to be disconnected.

[iarakis]

Hi,

Now the Thingy is not even connecting to NRFCLOUD:

This is the serial output I am getting:

[00:00:59.679,687] <inf> event_manager: UI_EVT_BUTTON_DATA_READY
[00:00:59.686,370] <inf> event_manager: DATA_EVT_UI_DATA_READY
%CESQ: 52,2,10,1
%CESQ: 47,2,10,1
%CESQ: 52,2,11,1
[00:01:33.579,101] <inf> event_manager: UI_EVT_BUTTON_DATA_READY
[00:01:33.585,784] <inf> event_manager: DATA_EVT_UI_DATA_READY
%CESQ: 47,2,12,1
[00:01:42.830,718] <inf> event_manager: CLOUD_EVT_CONNECTION_TIMEOUT
[00:01:42.837,860] <wrn> cloud_module: Cloud connection establishment in progress
[00:01:42.845,947] <wrn> cloud_module: New connection attempt in 128 seconds if not successful
%CESQ: 41,2,10,1
%CESQ: 46,2,13,1
[00:01:54.116,149] <inf> event_manager: CLOUD_EVT_DISCONNECTED
[00:01:54.122,802] <err> nrf_cloud_transport: MQTT input error: -128
[00:01:54.129,913] <inf> event_manager: CLOUD_EVT_DISCONNECTED
%CESQ: 50,2,18,2
%CESQ: 50,2,12,1
[00:02:00.273,315] <inf> event_manager: APP_EVT_DATA_GET_ALL
[00:02:00.280,029] <inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS, MOD_STAT)
[00:02:00.307,312] <inf> event_manager: GPS_EVT_ACTIVE
[00:02:00.313,446] <inf> event_manager: GPS_EVT_AGPS_NEEDED
[00:02:00.320,098] <wrn> data_module: Failed to request A-GPS data, error: -13
[00:02:00.328,308] <wrn> data_module: This is expected to fail if we are not in a connected state
[00:02:00.339,263] <inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY
[00:02:00.413,330] <inf> event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY
[00:02:00.475,463] <inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY
%CESQ: 45,2,14,2
[00:02:00.518,096] <inf> event_manager: MODEM_EVT_BATTERY_DATA_READY
[00:02:00.527,435] <inf> event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY
%CESQ: 45,2,9,1
%CESQ: 34,1,0,0
%CESQ: 47,2,16,2
%CESQ: 47,2,11,1

[Markus Tacker (he/him)]

Try moving to another place, it could be that the signal quality in your current place is too bad, and that's why the device loses connection.