Help¶

The nrf- prefix is reserved on nRF Connect for Cloud for official Nordic devices (e.g. the nRF9160 DK or the Thingy:91). In case you wish to use nrf_cloud with your own devices you need to modify the prefix used to generate the MQTT client ID from the IMEI.

Direct dependencies¶

NRF_CLOUD

(Includes any dependencies from ifs and menus.)

Default¶

“nrf-“

Kconfig definition¶

At <nRF>/subsys/net/lib/nrf_cloud/Kconfig:40

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:8

Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf) → Nordic nRF Connect → Networking → Application protocols → nRF Cloud library

config NRF_CLOUD_CLIENT_ID_PREFIX
    string "Prefix used when constructing the MQTT client ID from the IMEI"
    default "nrf-"
    depends on NRF_CLOUD
    help
      The nrf- prefix is reserved on nRF Connect for Cloud for official Nordic
      devices (e.g. the nRF9160 DK or the Thingy:91).
      In case you wish to use nrf_cloud with your own devices you need to modify
      the prefix used to generate the MQTT client ID from the IMEI.

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