Skip the Network Commissioning cluster on the root node when
CONFIG_CUSTOM_NETWORK_CONFIG is enabled, per Matter spec condition
(!CustomNetworkConfig). This allows devices with out-of-band network
configuration (rich UI, manufacturer-specific means) to omit the
cluster as the spec permits.
- Add CONFIG_CUSTOM_NETWORK_CONFIG Kconfig option
- Conditionally skip network_commissioning in root_node config/add
- Exclude integration.cpp from build when custom config enabled
- Add weak stubs for Plugin callbacks as fallback
- Also guarded secondary network device type and all the
attributes and commands that are part of network commissioning
cluster
esp_matter: Add data model provider for esp_matter data model and remove upstream ember codes from esp_matter component
See merge request app-frameworks/esp-matter!1215
- moved cluster revision from 8 to 9
- thermostat cluster has schedule and preset attributes with quality T
i.e. atomic. It requires the cluster to implement atomic-request and
atomic-response command.
- Added esp-matter codegen integration files for migrated clusters.
- Fixed the commissioning flow for wifi and thread due to migration of network commissioning instances from platform to example.
- Fixed the spell check issues for the modified files.
- Fixed the decode method syntax for fabric scoped commands.
- Modified the cluster revisions for few clusters as per spec.