Help¶

Azure IoT Hub uses dynamically constructed topics to transfer information elements such as response codes, direct method names and property bag keys and values. This option configures the maximum length of such an element. Note that all values are also represented as strings, regardless of their content, so a boolean or a number will require its length as a string, and not the size of its binary representation.

Direct dependencies¶

AZURE_IOT_HUB

(Includes any dependencies from ifs and menus.)

Default¶

22

Kconfig definition¶

At <nRF>/subsys/net/lib/azure_iot_hub/Kconfig:78

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:23 → <Zephyr>/modules/Kconfig:6 → <BuildDir>/Kconfig/Kconfig.modules:2 → <nRF>/Kconfig.nrf:25 → <nRF>/subsys/Kconfig:18 → <nRF>/subsys/net/Kconfig:8 → <nRF>/subsys/net/lib/Kconfig:15

Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf) → Nordic nRF Connect → Networking → Application protocols → Azure IoT Hub [EXPERIMENTAL]

config AZURE_IOT_HUB_TOPIC_ELEMENT_MAX_LEN
    int "Maximum length of topic element strings"
    default 22
    depends on AZURE_IOT_HUB
    help
      Azure IoT Hub uses dynamically constructed topics to transfer
      information elements such as response codes, direct method names and
      property bag keys and values.
      This option configures the maximum length of such an element.
      Note that all values are also represented as strings, regardless
      of their content, so a boolean or a number will require its length as
      a string, and not the size of its binary representation.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)