Current version of AssetTracker

[Eau Du Puid]

Hi

There is a github repo https://github.com/nrfconnect/Asset-Tracker-Template/tree/main that receives updates as of yesterday.

However on the documentation website https://docs.nordicsemi.com/bundle/ncs-2.9.2/page/nrf/applications/asset_tracker_v2/README.html , I read:

Important

The Asset Tracker v2 application is in maintenance mode. For new projects, it is recommended to use the Cellular: nRF Cloud multi-service sample instead..

Could explain what that means ? Why should I use the multi-service sample ? Is the AssetTracker as implemented in the github repo obsolete or is there a difference in functionality ?

Kind regards

Peter

[Simon D-M]

Hi Peter,

However on the documentation website https://docs.nordicsemi.com/bundle/ncs-2.9.2/page/nrf/applications/asset_tracker_v2/README.html , I read:

The link you just sent is referring to an old version of the Asset Tracker application, which was called "Asset Tracker v2". The newest version of this application has been renamed to "Asset Tracker Template" which is the application you saw on GitHub.

You can find the documentation for the new application here.

The Asset tracker template is the recommended application to use for new Asset tracking projects.

Best regards,

Simon D-M

[Eau Du Puid]

Hi, Thank you Simon

What exactly is the difference between the Asset Tracker Template and the multi service sample ? Why would one choose one over the other ?

Kind regards 

Peter

[Simon D-M]

Hi Peter,

I just asked internally, and the Asset Tracker Template has other things that use the nRF Cloud Location service.

It uses the Location service for Cellular Positioning and Wi-Fi Positioning (Wi-Fi is only relevant for the Thingy:91 X).

To deactivate these service, you can disable the config "CONFIG_LOCATION_METHOD_CELLULAR=n" in prj.conf.

And :

• for the nRF9151 DK, disable in boards/nrf9151dk_nrf9151_ns.conf :
  • "CONFIG_LOCATION_REQUEST_DEFAULT_METHOD_SECOND_CELLULAR=n" 
• for the Thingy:91 X, disable in boards/thingy91x_nrf9151_ns.conf :
  • "CONFIG_LOCATION_METHOD_WIFI=n"
  • "CONFIG_LOCATION_REQUEST_DEFAULT_METHOD_FIRST_WIFI=n"
  • "CONFIG_LOCATION_REQUEST_DEFAULT_METHOD_THIRD_CELLULAR=n"

I hope this will solve your issue. If it still uses the Location Service I'll try to check if there is even more things that use it.

Best regards,

Simon D-M

[Eau Du Puid]

Hi Simon

Thank you , I will try this in a minute. I just upgraded to Pro but I still get the same error:

[00:00:30.428,436] <inf> nrf_cloud_fota_poll: No pending FOTA job
[00:00:30.428,436] <dbg> fota: state_polling_for_update_entry: No FOTA job available
[00:00:30.428,833] <dbg> fota: state_waiting_for_poll_request_entry: state_waiting_for_poll_request_entry
[00:00:30.869,415] <err> nrf_cloud_coap_transport: Unexpected response: {"message":"This request exceeds your monthly quota of 1500 location service requests.","code":40005}
[00:00:30.869,476] <err> nrf_cloud_coap: Unexpected response: {"message":"This request exceeds your monthly quota of 1500 location service requests.","code":40005}
[00:00:30.869,750] <err> nrf_cloud_coap: Error getting location; result code: 4.00
[00:00:30.869,781] <wrn> cloud: nRF Cloud CoAP location coordinates not found, error: 128

I don't need location so I am going to change prj.conf as you suggested, but since this is now Pro, maybe there is another issue ?

Kind regards

Peter

[Simon D-M]

Hi,

Yes, please try the suggested change first. And if you still have problems with the location service requests after that, I'll forward your issue internally to the nRF Cloud team.

Best regards,

Simon D-M

[Eau Du Puid]

Hi Simon

I disabled all location services:

# Location
CONFIG_LOCATION=n
CONFIG_LOCATION_DATA_DETAILS=n
CONFIG_LOCATION_METHOD_GNSS=n
CONFIG_LOCATION_METHOD_CELLULAR=n
CONFIG_LOCATION_SERVICE_EXTERNAL=n
CONFIG_LOCATION_REQUEST_DEFAULT_GNSS_TIMEOUT=60000
CONFIG_LOCATION_REQUEST_DEFAULT_CELLULAR_TIMEOUT=30000
CONFIG_LOCATION_REQUEST_DEFAULT_TIMEOUT=120000
CONFIG_LOCATION_REQUEST_DEFAULT_CELLULAR_CELL_COUNT=3
CONFIG_LOCATION_REQUEST_DEFAULT_GNSS_VISIBILITY_DETECTION=n
CONFIG_LTE_NETWORK_MODE_LTE_M_NBIOT_GPS=n
CONFIG_LTE_NETWORK_MODE_LTE_M_NBIOT=y
CONFIG_NRF_CLOUD_AGNSS=n
CONFIG_LOCATION_REQUEST_DEFAULT_METHOD_SECOND_CELLULAR=n

However, this doesn't compile out of the box because of missing guards. Also, this disables the button 1 function.

It might be interesting to refactor the template so that people who don't need location can easily disable it. Also, basic data upload should work in the free plan even when location quotas are exceeded.

Anyway, thank you very much for your help.

Kind regards

Peter

[Simon D-M]

Hi,

I'm glad you were able to find a solution!

I found that there is a branch on the GitHub repo that was made with the location module removed. It looks like it has not been updated, but it can be a good way to see what needs to be done to remove it cleanly.

Best regards,

Simon D-M