:orphan:

.. title:: CONFIG_LWM2M_CANCEL_OBSERVE_BY_PATH

.. kconfig:: CONFIG_LWM2M_CANCEL_OBSERVE_BY_PATH

CONFIG_LWM2M_CANCEL_OBSERVE_BY_PATH
###################################

*Use path matching as fallback for cancel-observe*

Type: ``bool``

Help
====

.. code-block:: none

    Some ambiguous language in the LwM2M spec causes some LwM2M server
    implementations to implement cancel-observe by specifying the resource
    path rather than the token of the original observe request. Without
    this option, cancel-observe may not work properly when connecting to
    those servers.

Direct dependencies
===================

\ :kconfig:`LWM2M <CONFIG_LWM2M>` && \ :kconfig:`NETWORKING <CONFIG_NETWORKING>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Kconfig definition
==================



At ``<Zephyr Subsystem>/net/lib/lwm2m/Kconfig:90``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:44`` → ``<Zephyr Subsystem>/Kconfig:39`` → ``<Zephyr Subsystem>/net/Kconfig:89`` → ``<Zephyr Subsystem>/net/lib/Kconfig:18``

Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → Network Protocols → OMA LWM2M protocol stack

.. code-block:: kconfig

    config LWM2M_CANCEL_OBSERVE_BY_PATH
    	bool "Use path matching as fallback for cancel-observe"
    	depends on LWM2M && NETWORKING
    	help
    	  Some ambiguous language in the LwM2M spec causes some LwM2M server
    	  implementations to implement cancel-observe by specifying the resource
    	  path rather than the token of the original observe request. Without
    	  this option, cancel-observe may not work properly when connecting to
    	  those servers.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*