compatibility adjustments
Added global variable for temperature unit for deferred
setting when enabling endpoint. Compatibility functions to
handle temperature unit attribute reads and writes,
ensuring seamless integration with previous versions.
Also, added a function to retrieve the cluster id and endpoint id for
internally managed attribues.
Storage of this attribute was moved from esp-matter to
connectedhomeip during the v1.4.2 release by implementing the AAI in
connectedhomeip. For most clusters, AAI registration occurs in the
cluster-init callback, but for this Air Quality cluster, it is
delegated to the application layer. So, in the esp-matter's workflow,
no one registers the AAI. And, as this attribute is of primitive type,
we can discard the ATTRIBUTE_FLAG_MANAGED_INTERNALLY flag and storage
can be managed by esp-matter.
controller: Initialize group data provider listener when initializing the controller instance (v1.4.2)
See merge request app-frameworks/esp-matter!1251
components/esp_matter: Add the missing bits from pressure measurement cluster, solar power and battery storage device type.
See merge request app-frameworks/esp-matter!1207
- 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 features
After restructuring we were only adding features that are marked with
O.a or O.a+ conformance. But, it leads to the inconsistency where user
speicied features will not be added.
For clusters which has O.a or O.a+ feature conformance, linking all the
supported features in cluster create to address the incosistency.
Also, moved the feature create in the server part.
- 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.
- Removed the static-cluster-config files from the generated files to support esp-matter codegen integration.
- Modified the generate_zap_common_files.py script to remove the generation of static-cluster-config files.
- Executed ./components/esp_matter/utils/cluster_select/generate_cluster_select_files.py to generate the cluster_select files.
- Executed ./components/esp_matter/zap_common/generate_zap_common_files.py to generate the files in zap_common directory.
endpoint, cluster, and command ids
current api to get the command handler is a bit overkill to use, it
requires additional parameter which is flag and to get that we need to
look into the cluster create apis and then jump to command create apis
to figure out that parameter.
resize the group data provider when new endpoint is added to the node or
existing one is removed from the node. This is to ensure that endpoints
containing groups cluster that are added after esp_matter::start()
should have storage for groups.
Fixes https://github.com/espressif/esp-matter/issues/1467
Shu Chen
Shubham Patil
mahesh
Rohit
WanqQixiang
Hrishikesh Dhayagude
shripad621git
chendejin
liyashuai
Mahesh Pimpale