Shared configurations in KNX IoT add-on

The KNX IoT add-on provides a set of Kconfig options that are shared across all of its samples.

Use these options to enable the KNX IoT stack, control commissioning behavior, and tune the runtime and logging of the shared KNX integration library.

Configuration options

CONFIG_KNX_IOT_ADD_ON

(bool) KNX IoT stack

Enable the KNX IoT add-on. This brings in the third-party KNX IoT stack (libknx) together with the add-on’s shared KNX integration library under subsys/knx/.

CONFIG_KNX_HARDCODED_COMMISSIONING

(bool) Apply hardcoded KNX/Thread commissioning on boot

When enabled, the device applies a hardcoded commissioning profile (individual address, group object/publisher/recipient tables and a shared group OSCORE key) on boot, so two boards can talk without ETS or a Thread commissioner. Gates subsys/knx/knx_presets.c.

CONFIG_KNX_THREAD_PRIORITY

(int) KNX event-loop thread priority

Scheduling priority of the KNX worker thread that runs the stack event loop (oc_main_poll). A preemptible (positive) priority is the usual choice so networking and system work can run alongside it. The thread’s stack size is taken from KNX_THREAD_STACK_SIZE.

CONFIG_KNX_VERBOSE_STACK_LOGS

(bool) Enable verbose libknx stack logging

When enabled, libknx logs at DEBUG level and stack PRINT output is routed to Zephyr logging.