Help¶

Store Client Configuration Characteristic value right after it has
been updated.

By default, CCC is only stored on disconnection.
Choosing this option is safer for battery-powered devices or devices
that expect to be reset suddenly. However, it requires additional
workqueue stack space.

Direct dependencies¶

BT_CONN && BT_SETTINGS && BT_HCI_HOST && BT_HCI && BT

(Includes any dependencies from ifs and menus.)

Defaults¶

No defaults. Implicitly defaults to n.

Kconfig definition¶

At <Zephyr>/subsys/bluetooth/host/Kconfig:151

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:9 → <Zephyr>/subsys/bluetooth/Kconfig:306

Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Store Bluetooth state and configuration persistently

config BT_SETTINGS_CCC_STORE_ON_WRITE
    bool "Store CCC value immediately after it has been written"
    depends on BT_CONN && BT_SETTINGS && BT_HCI_HOST && BT_HCI && BT
    help
      Store Client Configuration Characteristic value right after it has
      been updated.

      By default, CCC is only stored on disconnection.
      Choosing this option is safer for battery-powered devices or devices
      that expect to be reset suddenly. However, it requires additional
      workqueue stack space.

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