espressif/esp-matter
1
0
Fork 0
mirror of https://github.com/espressif/esp-matter.git synced 2026-04-27 19:13:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'esp_matter/data_model_directory' into 'main'

Browse Source 
esp_matter: create a data_model directory and move data_model related codes to it

See merge request app-frameworks/esp-matter!1032
This commit is contained in:
Shu Chen
2025-07-29 04:25:55 +00:00
parent b7f84046aa 13a15243cc
commit 6ab9b8fa3a
50 changed files with 3454 additions and 3094 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/Doxyfile
+8 -7
View File
@@ -21,13 +21,14 @@ PROJECT_NAME = "Programming Guide"
## and used to include in API reference documentation
INPUT = \
$(PROJECT_PATH)/components/esp_matter/esp_matter_endpoint.h \
$(PROJECT_PATH)/components/esp_matter/esp_matter_cluster.h \
$(PROJECT_PATH)/components/esp_matter/esp_matter_attribute.h \
$(PROJECT_PATH)/components/esp_matter/esp_matter_command.h \
$(PROJECT_PATH)/components/esp_matter/esp_matter_core.h \
$(PROJECT_PATH)/components/esp_matter/esp_matter_event.h \
$(PROJECT_PATH)/components/esp_matter/esp_matter_client.h \
$(PROJECT_PATH)/components/esp_matter/data_model/esp_matter_endpoint.h \
$(PROJECT_PATH)/components/esp_matter/data_model/esp_matter_cluster.h \
$(PROJECT_PATH)/components/esp_matter/data_model/esp_matter_attribute.h \
$(PROJECT_PATH)/components/esp_matter/data_model/esp_matter_command.h \
$(PROJECT_PATH)/components/esp_matter/data_model/esp_matter_event.h \
$(PROJECT_PATH)/components/esp_matter/data_model/esp_matter_data_model.h \
$(PROJECT_PATH)/components/esp_matter/esp_matter_core.h \
$(PROJECT_PATH)/components/esp_matter/esp_matter_client.h \
## Get warnings for functions that have no documentation for their parameters or return value
##
docs/en/api-reference/esp_matter_data_model.rst
+9
View File
@@ -0,0 +1,9 @@
Data Model
==========
This has the high level APIs for Data Model.
API reference
-------------
.. include-build-file:: inc/esp_matter_data_model.inc
docs/en/api-reference/index.rst
+1
View File
@@ -4,6 +4,7 @@
.. toctree::
:maxdepth: 1
esp_matter_data_model.rst
esp_matter_endpoint.rst
esp_matter_cluster.rst
esp_matter_attribute.rst
docs/en/developing.rst
+1 -1
View File
@@ -654,7 +654,7 @@ for clarity on the terms like endpoints, clusters, etc. that are used in this se
node_t *node = node::create(&node_config, app_attribute_update_cb, NULL);
- We will use the ``color_temperature_light`` standard device type in this
case. All standard device types are available in :project_file:`esp_matter_endpoint.h <components/esp_matter/esp_matter_endpoint.h>` header file.
case. All standard device types are available in :project_file:`esp_matter_endpoint.h <components/esp_matter/data_model/esp_matter_endpoint.h>` header file.
Each device type has a set of default configuration that can be
specific as well.
docs/en/faq.rst
+1 -1
View File
@@ -170,7 +170,7 @@ A1.8 Why does free RAM increase after first commissioning
After the first commissioning, you may notice that the free RAM increases. This is because, by default,
BLE is only used for the commissioning process. Once the commissioning is complete, BLE is deinitialized,
and all the memory allocated to it is recovered. Here's the link to the
:project_file:`implementation which frees the BLE memory <components/esp_matter/esp_matter_core.cpp#L859-L891>`.
:project_file:`implementation which frees the BLE memory <components/esp_matter/esp_matter_core.cpp#L287-L290>`.
However, if you want to continue using the BLE even after the commissioning process, you can disable the
``CONFIG_USE_BLE_ONLY_FOR_COMMISSIONING``. This will ensure that the memory allocated to the BLE functionality