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
Going through the configs and docs lead to the introducing
of few fixes:
* Removed enabling DAC migration, as it triggered warning for
Wi-Fi that does not support PSA
* Fixed nrf70eb mentions in docs
* Added info about network commissioning cluster to the
certification page
* Added experimental for few bridge configurations
Signed-off-by: Kamil Kasperczyk <[email protected]>
Copy file name to clipboardExpand all lines: doc/nrf/protocols/matter/end_product/certification.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -357,7 +357,7 @@ Especially, make sure that:
357
357
* ``ClusterRevision`` attributes for all clusters match the value of the Matter stack version that you want to use for your application certification.
358
358
* ``Attribute List``, ``Accepted Command List`` and ``Generated Command List`` attributes for all clusters contain all the values that need to be there and nothing more.
359
359
* Only the clusters, attributes and commands required by your application are enabled.
360
-
For example, the default configurations for the samples use both Thread Network Diagnostics and Wi-Fi Network Diagnostics clusters.
360
+
For example, the default configurations for the samples use both Thread Network Diagnostics and Wi-Fi Network Diagnostics clusters, and the Network Commissioning cluster has attributes for both Thread and Wi-Fi protocols enabled.
361
361
This is done due to the Thread and Wi-Fi platforms common maintenance reasons, but should not be used in the final product.
362
362
363
363
See the :ref:`ug_matter_creating_accessory` page for how to configure your application using the ZAP Tool.
0 commit comments