You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/nrf/protocols/matter/getting_started/advanced_kconfigs.rst
+53Lines changed: 53 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,9 @@ Logging configuration
72
72
Logging is handled with the :kconfig:option:`CONFIG_LOG` option.
73
73
This option enables logging for both the stack and Zephyr's :ref:`zephyr:logging_api` API.
74
74
75
+
Logging level configuration
76
+
---------------------------
77
+
75
78
Zephyr allows you to configure log levels of different software modules independently.
76
79
To change the log level configuration for the Matter module, set one of the available options:
77
80
@@ -83,6 +86,56 @@ To change the log level configuration for the Matter module, set one of the avai
83
86
.. note::
84
87
:kconfig:option:`CONFIG_MATTER_LOG_LEVEL_WRN` is not used in Matter.
85
88
89
+
Detailed message logging
90
+
------------------------
91
+
92
+
You can enable detailed logging of Matter interaction messages using the :kconfig:option:`CONFIG_CHIP_IM_PRETTY_PRINT` Kconfig option.
93
+
94
+
When enabled, this option increases the verbosity of the logs by including protocol-level details such as:
95
+
96
+
* Cluster ID
97
+
* Endpoint ID
98
+
* Attribute ID or Command ID
99
+
* Payload contents for interaction messages (for example Read Request or Invoke Request)
100
+
101
+
This is particularly useful for debugging and understanding communication flows within the Matter data model.
102
+
103
+
The following is an example log output showing a ``ConnectNetwork`` command (0x06) from the Network Commissioning cluster (0x31), sent with a ``NetworkID`` of ``0x1111111122222222``.
This option requires the debug log level :kconfig:option:`CONFIG_MATTER_LOG_LEVEL_DBG` to be enabled and :kconfig:option:`CONFIG_CHIP_LOG_SIZE_OPTIMIZATION` to be disabled.
0 commit comments