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.
CI: run all the pytest example builds with the same IDF version and fix managed component example build on release/v1.4.2
See merge request app-frameworks/esp-matter!1283
As we are using the static file for showing versions in the drop-down
this would be outdated with each new release, so use it from the main
branch, with the assumption that it would always be up-to-date.
controller: Initialize group data provider listener when initializing the controller instance (v1.4.2)
See merge request app-frameworks/esp-matter!1251
esp-idf v4.4 requires construct==2.10.56, but latest changes in
esp-secure-cert-tool changed it to construct>=2.10.76.
install.sh script installs the esp-matter-mfg-tool which depends on
esp-secure-cert-tool which depends on construct>=2.10.76
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.
Introduce a precedence-based implementation for reading manufacturing
data.
Manufacturing data can reside in either the secure-cert partition or the
fctry partition. To ensure backward compatibility with older modules
(where manufacturing data was stored in the fctry partition), this implementation
supports setting precedence between the available storage options.
Default precedence is factory first, i.e. implementation checks the data
in factory partition first and if not found falls back to check secure
cert partition.
This allows newer modules using secure-cert to coexist seamlessly with legacy ones.
Shu Chen
Shubham Patil
Hrishikesh Dhayagude
mahesh
WanqQixiang
chendejin
Rohit
shripad621git
Mahesh Pimpale