How to disable location services in asset tracker with lwm2m

RE: How to disable location services in asset tracker with lwm2m

hubert_11 — Thu, 27 Jun 2024 11:11:15 GMT

Thanks, that indeed solved it.

I case anybody else encounters this same use case, I had to change these lines to n too in the lwm2m overlay:

CONFIG_LWM2M_CLIENT_UTILS_GNSS_ASSIST_OBJ_SUPPORT=n

CONFIG_LWM2M_CLIENT_UTILS_LOCATION_ASSIST_AGNSS=n

CONFIG_LWM2M_CLIENT_UTILS_LOCATION_ASSIST_CELL=n

RE: How to disable location services in asset tracker with lwm2m

Kenneth — Thu, 20 Jun 2024 09:02:08 GMT

[quote user="hubert_11"]Furthermore, if I try to add CONFIG_LOCATION_MODULE=n to my prj.conf it throws this error:[/quote]

Looks like this did the job, the remaining problem now is that you still have code that try to use the location api (e.g. undefined reference to `nrf_cloud_agnss_process') so you need to comment or remove those.

Kenenth

RE: How to disable location services in asset tracker with lwm2m

hubert_11 — Wed, 19 Jun 2024 14:10:40 GMT

I don't think so, I can't find them anywhere in my code. And I'm using just the unaltered config files for the asset tracker expect for the inclusion of the lwm2m overlay.

Furthermore, if I try to add CONFIG_LOCATION_MODULE=n to my prj.conf it throws this error:

/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: modules/nrf/subsys/net/lib/lwm2m_client_utils/lib..__nrf__subsys__net__lib__lwm2m_client_utils.a(gnss_assistance_obj.c.obj): in function `gnss_assist_write_agnss':
/opt/nordic/ncs/v2.6.1/nrf/subsys/net/lib/lwm2m_client_utils/lwm2m/gnss_assistance_obj.c:116: undefined reference to `nrf_cloud_agnss_process'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

and it can't find CONFIG_MOSH_LOCATION=n:
prj.conf:117: warning: attempt to assign the value 'n' to the undefined symbol MOSH_LOCATION

RE: How to disable location services in asset tracker with lwm2m

Kenneth — Wed, 19 Jun 2024 13:51:49 GMT

Good point, I was hoping it threw a bit more information.

If I search through ncs for the following:

select LOCATION

I can for instance find the following results:

Is it possible that you have enabled CONFIG_MOSH_LOCATION or CONFIG_LOCATION_MODULE?

Best regards,
Kenneth

RE: How to disable location services in asset tracker with lwm2m

hubert_11 — Wed, 19 Jun 2024 12:22:38 GMT

Thank you for the reply. I do indeed see that warning in the build output, but it doesn't really help me to narrow down the cause:

warning: LOCATION (defined at /opt/nordic/ncs/v2.6.1/nrf/lib/location/Kconfig:7) was assigned the
value 'n' but got the value 'y'. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LOCATION and/or look up LOCATION in the
menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values,
and Kconfig - Tips and Best Practices sections of the manual might be helpful too.

From the documentation on the location module it seems that just setting the CONFIG_LOCATION to n would be enough.

Is there a way to find out which code/kconfig setting makes it go back to y?

RE: How to disable location services in asset tracker with lwm2m

Kenneth — Wed, 19 Jun 2024 11:30:13 GMT

Hello,

If you set CONFIG_LOCATION=n in your prj.conf, and it is still set in the application, then you should get a warning during build where is says that the config option was set to CONFIG_LOCATION=y during building, I suggest to look at the build output to understand why it was still set to y.

Kenneth