This is a middle layer between application and chip submodule.
esp_matter_core: Data model APIs in the form of linked lists. It also has the APIs for initialisations for matter.
esp_matter_endpoint: APIs for endpoint. This adds the mandatory clusters for the endpoint.
esp_matter_cluster: APIs for cluster. This adds the mandatory attributes and commands for the cluster.
esp_matter_attribute: APIs for attribute value. It also manages the attribute related matter callbacks.
esp_matter_command: Callback APIs for commands.
esp_matter_attribute: Giving 2 callbacks to the application, pre_attribute and post_attribute.
app_main: Dynamically creating the data model using the top level APIs.
app_matter: Moved to esp_matter_start() in esp_matter. Also moved the post_attribute_callback to esp_matter_attribute and moved the event_callback to app_main.
app_driver: Moved with app_main. Using IDs instead of macros.
app_driver: Changing the console usage from names to IDs.
app_rainmaker: Dynamically creating the rainmaker data model from the matter data model. The endpoint_id, cluster_id, attribute_id need to be handled accordingly.
cmake: Moved the chip submodule sources and includes from app_main to esp_matter.
zap-generated: Using esp_matter_command instead of IMClusterCommandHandler. Dynamically creating the data model instead of using macros from endpoint_config.
zap-generated: Regenerated using the zap tool with matter_root_node and matter_color_dimmable_light device types. Also enabled wifi and thread for network commissioning cluster.
device_hal: Added support for esp32s2 with hollow drivers.
zap_light: Adding another example which uses the zap-generated data model instead of the esp_matter data model.
ci: Added zap_light example to ci.
PSONALl
Chirag Atal
WanqQixiang