Initialization exception for an Aggregator-type dimmable light node (CON-1901)

[ethan-jy]

Describe the bug
"After powering on, I created an Aggregator node and added a Dimmable Light device to it (the Aggregator contains this Dimmable Light device). Then, I cut the power and restored it, but found that the OnOff attribute did not trigger an attribute update event.

Environment

• ESP-Matter Commit Id: Matter 1.3
• ESP-IDF Commit Id: 5.4
• SoC (eg: ESP32 or ESP32-C3):ESP32H2
• Device Logs (Please attach the log file):

• Host Machine OS:

• Host Machine Python version:

• Commissioner app and versions if present:

• Home hub app and versions if present:

• Commissioner's logs if present:

Any additional details
[0;31mE (1694) chip[DMG]: Endpoint 0, Cluster 0x0000_0031 not found in IncreaseClusterDataVersion!�[0m
�[0;31mE (1694) chip[DMG]: Endpoint 0, Cluster 0x0000_0031 not found in IncreaseClusterDataVersion!�[0m
�[0;32mI (1704) chip[SVR]: Initializing subscription resumption storage...�[0m
�[0;32mI (1714) chip[SVR]: Server initializing...�[0m
�[0;32mI (1724) chip[TS]: Last Known Good Time: 2023-10-14T01:16:48�[0m
�[0;32mI (1734) chip[FP]: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0xAEEF297A04316C35, FabricId 0x0000000000000001, NodeId 0x0000000000000001, VendorId 0xFFF1�[0m
�[0;32mI (1744) chip[DMG]: AccessControl: initializing�[0m
�[0;32mI (1744) chip[DMG]: Examples::AccessControlDelegate::Init�[0m
�[0;32mI (1754) chip[DMG]: AccessControl: setting�[0m
�[0;32mI (1754) chip[DMG]: DefaultAclStorage: initializing�[0m
�[0;32mI (1764) chip[DMG]: DefaultAclStorage: 1 entries loaded�[0m
�[0;32mI (1814) chip[ZCL]: Using ZAP configuration...�[0m
�[0;32mI (1814) esp_matter_cluster: Cluster plugin init common callback�[0m
�[0;32mI (1814) chip[DMG]: AccessControlCluster: initializing�[0m
�[0;32mI (1814) chip[ZCL]: 0x42169ac8 ep 0 clus 0x0000_0030 attr 0x0000_0000 not supported�[0m
�[0;32mI (1824) chip[ZCL]: Initiating Admin Commissioning cluster.�[0m
�[0;32mI (1834) chip[SVR]: Fabric already commissioned. Disabling BLE advertisement�[0m
�[0;32mI (1844) chip[IN]: CASE Server enabling CASE session setups�[0m
�[0;32mI (1844) chip[SVR]: Joining Multicast groups�[0m
�[0;32mI (1854) chip[SVR]: Server Listening...�[0m
�[0;32mI (1854) chip[DIS]: Updating services using commissioning mode 0�[0m
�[0;31mE (1864) chip[DIS]: Failed to remove advertised services: 3�[0m
�[0;32mI (1864) chip[DIS]: Advertise operational node AEEF297A04316C35-0000000000000001�[0m
�[0;31mE (1874) chip[DIS]: Failed to advertise operational node: 3�[0m
�[0;31mE (1884) chip[DIS]: Failed to finalize service update: 3�[0m
�[0;32mI (1894) esp_matter_core: Dynamic endpoint 0 added�[0m
�[0;32mI (1894) esp_matter_core: Dynamic endpoint 1 added�[0m
�[0;32mI (1904) app_bridged_device: !!!!!!!!!!!!!!!!!app_bridge_initialize_YD!!!!!!!!!!!!!!!!!!!!!�[0m
�[0;32mI (1914) app_bridged_device: chip::kInvalidEndpointId: 65535�[0m
�[0;32mI (1914) app_bridged_device: matter_endpoint_id_array 5�[0m
�[0;32mI (1924) app_bridged_device: app_bridge_read_bridged_device_info�[0m
�[0;32mI (1934) app_bridged_device: esp_matter_mem_calloc�[0m
�[0;32mI (1934) app_bridged_device: resume_device�[0m
�[0;33mW (1944) esp_matter_core: Server Cluster 0x0000001D on endpoint 0x0005 already exists. Not creating again.�[0m
�[0;33mW (1944) esp_matter_core: Attribute 0x00000000 on cluster 0x0000001D already exists. Not creating again.�[0m
�[0;33mW (1954) esp_matter_core: Attribute 0x00000001 on cluster 0x0000001D already exists. Not creating again.�[0m
�[0;33mW (1964) esp_matter_core: Attribute 0x00000002 on cluster 0x0000001D already exists. Not creating again.�[0m
�[0;33mW (1974) esp_matter_core: Attribute 0x00000003 on cluster 0x0000001D already exists. Not creating again.�[0m
�[0;33mW (1994) esp_matter_core: Attribute 0x0000FFFC on cluster 0x0000001D already exists. Not creating again.�[0m
�[0;33mW (2004) esp_matter_core: Attribute 0x0000FFFD on cluster 0x0000001D already exists. Not creating again.�[0m
�[0;32mI (2014) esp_matter_bridge: Cluster plugin init for the new added endpoint�[0m
�[0;32mI (2014) esp_matter_attribute: ********** W : Endpoint 0x0005's Cluster 0x00000003's Attribute 0x00000001 is 1 **********�[0m
�[0;32mI (2024) dipswitch_bridge: !!!!!!!!!!!app_dipswitch_bridge_attribute_update() !!!!!!!!!!!�[0m
�[0;32mI (2034) esp_matter_attribute: ********** W : Endpoint 0x0005's Cluster 0x00000004's Attribute 0x00000000 is 128 **********�[0m
�[0;32mI (2054) dipswitch_bridge: !!!!!!!!!!!app_dipswitch_bridge_attribute_update() !!!!!!!!!!!�[0m
�[0;32mI (2054) esp_matter_attribute: ********** W : Endpoint 0x0005's Cluster 0x00000004's Attribute 0x0000FFFC is <invalid type: 0> **********�[0m
�[0;32mI (2074) dipswitch_bridge: !!!!!!!!!!!app_dipswitch_bridge_attribute_update() !!!!!!!!!!!�[0m
�[0;32mI (2084) esp_matter_attribute: ********** R : Endpoint 0x0005's Cluster 0x00000006's Attribute 0x0000FFFC is 1 **********�[0m
�[0;32mI (2094) esp_matter_attribute: ********** R : Endpoint 0x0005's Cluster 0x00000006's Attribute 0x00004003 is 254 **********�[0m
�[0;32mI (2104) esp_matter_attribute: ********** R : Endpoint 0x0005's Cluster 0x00000006's Attribute 0x00000000 is 1 **********�[0m
�[0;32mI (2114) esp_matter_attribute: ********** R : Endpoint 0x0005's Cluster 0x00000006's Attribute 0x00000000 is 1 **********�[0m
�[0;32mI (2124) chip[ZCL]: Endpoint 5 On/off already set to new value�[0m
�[0;32mI (2134) esp_matter_attribute: ********** R : Endpoint 0x0005's Cluster 0x00000008's Attribute 0x00000002 is 1 **********�[0m
�[0;32mI (2144) esp_matter_attribute: ********** R : Endpoint 0x0005's Cluster 0x00000008's Attribute 0x00000003 is 254 **********�[0m
�[0;32mI (2154) esp_matter_attribute: ********** R : Endpoint 0x0005's Cluster 0x00000008's Attribute 0x0000FFFC is 3 **********�[0m
�[0;32mI (2164) esp_matter_attribute: ********** R : Endpoint 0x0005's Cluster 0x00000008's Attribute 0x00000000 is 254 **********�[0m
�[0;32mI (2184) esp_matter_attribute: ********** R : Endpoint 0x0005's Cluster 0x00000008's Attribute 0x00004000 is 254 **********�[0m
�[0;32mI (2194) esp_matter_attribute: ********** W : Endpoint 0x0005's Cluster 0x00000008's Attribute 0x00000000 is 254 **********�[0m
�[0;32mI (2204) dipswitch_bridge: !!!!!!!!!!!app_dipswitch_bridge_attribute_update() !!!!!!!!!!!�[0m
�[0;32mI (2214) dipswitch_bridge: gear_index : 0�[0m
�[0;32mI (2214) dipswitch_bridge: LED is off. Try to use move-to-level-with-on-off instead of move-to-level�[0m
�[0;32mI (2224) dipswitch_bridge: app_dipswitch_bridge_attribute_update() - level value 254�[0m
�[0;32mI (2234) esp_matter_core: Dynamic endpoint 5 added�[0m
�[0;32mI (2244) app_bridged_device: matter_endpoint_id_array 65535�[0m
�[0;32mI (2244) app_bridged_device: matter_endpoint_id_array 65535�[0m
�[0;32mI (2254) app_bridged_device: matter_endpoint_id_array 65535�[0m
�[0;32mI (2264) app_bridged_device: matter_endpoint_id_array 65535�[0m
�[0;32mI (2264) app_bridged_device: matter_endpoint_id_array 65535�[0m
�[0;32mI (2274) dipswitch_bridge: !!!!!!!!!!!!!!!!!dipswitch_poweron_bridge_device_init!!!!!!!!!!!!!!!!!!!!!�[0m
�[0;32mI (2284) dipswitch_bridge: current bridged device count: 1�[0m
�[0;32mI (2284) dipswitch_bridge: BRIDGE_DEVICE_MAX_UNIT: 6�[0m
�[0;32mI (2294) app_bridged_device: !!!!!!!!!!!!!!!!!app_bridge_get_espnow_all_macaddr!!!!!!!!!!!!!!!!!!!!!�[0m
�[0;32mI (2304) app_driver: !!!!!!!app_bridge_device_devicelist_update!!!!!!�[0m
�[0;32mI (2314) app_driver: dim_switch_mode: 1�[0m
�[0;32mI (2314) app_driver: gearindex: 0�[0m
�[0;32mI (2324) app_driver: device_type: 1�[0m
�[0;32mI (2324) app_driver: Init bridge device --- mac addr�[0m
�[0;32mI (2334) app_driver: dip_addr[0]: 1�[0m
�[0;32mI (2334) app_driver: dip_addr[1]: 0�[0m
�[0;32mI (2334) app_driver: dip_addr[2]: 1�[0m
�[0;32mI (2344) app_driver: dip_addr[3]: 0�[0m
�[0;32mI (2344) app_driver: dip_addr[4]: 0�[0m
�[0;32mI (2354) app_driver: dip_addr[5]: 2�[0m
�[0;32mI (2354) app_main: !!!!!!!!!!!!!!!!!!!!!!!!sus init!!!!!!!!!!!!!!!!!!!!!!!!!!!!�[0m
�[0;32mI (2364) app_driver: !!!!!!!!!!!!!!!!!!!!!!!!app_cycle_task!!!!!!!!!!!!!!!!!!!!!!!!!!!!�[0m
�[0;32mI (2384) app_driver: !!!!!!!!!!!!!!!!!!!!!!!!app_receive_queue_update_dimmer!!!!!!!!!!!!!!!!!!!!!!!!!!!!�[0m
�[0;32mI (2384) app_driver: !!!!!!!app_get_devicelist_by_macaddr!!!!!!�[0m
�[0;32mI (2394) app_driver: get DeviceList and index is : 0�[0m
�[0;32mI (2394) app_driver: level update - and the value is : 254�[0m
�[0;32mI (2404) app_driver: level update queue - and the power is : 254�[0m

[jadhavrohit924]

@ethan-jy We would love to know the endpoint hierarchy. Also, when you say cut the power and restored it, is it a physical device?

[ethan-jy]

@ethan-jy We would love to know the endpoint hierarchy. Also, when you say cut the power and restored it, is it a physical device?

MCU Supply PartList Response:
Endpoint 0 --- PartList[1,3]
Endpoint 1 -- Aggregator ---- Partlist[3]
Endpoint 3 -- Dimmable light

Note: Endpoint 3 is dynamically created during program execution (I detect DIP SWITCH changes, and different DIP SWITCH states will create varying numbers of lighting fixtures).

Scenario:
I disconnect and then restore power to the MCU. After power restoration, the MCU executes resume_device.

Question:
I want to confirm whether this process triggers an attribute change event. Specifically:

I expect the lights to turn ON via the attribute change event handler.
However, the On/Off event is not triggered, while the Level event does trigger.

[ethan-jy]

@ethan-jy We would love to know the endpoint hierarchy. Also, when you say cut the power and restored it, is it a physical device?

MCU Supply PartList Response: Endpoint 0 --- PartList[1,3] Endpoint 1 -- Aggregator ---- Partlist[3] Endpoint 3 -- Dimmable light

Note: Endpoint 3 is dynamically created during program execution (I detect DIP SWITCH changes, and different DIP SWITCH states will create varying numbers of lighting fixtures).

Scenario: I disconnect and then restore power to the MCU. After power restoration, the MCU executes resume_device.

Question: I want to confirm whether this process triggers an attribute change event. Specifically:

I expect the lights to turn ON via the attribute change event handler. However, the On/Off event is not triggered, while the Level event does trigger.

Supplement:
After initialization is completed, I pair the MCU with a Raspberry Pi. When controlling it via the onoff on/off command, it does trigger the attribute change event.

[jadhavrohit924]

Scenario:
I disconnect and then restore power to the MCU. After power restoration, the MCU executes resume_device.
Question:
I want to confirm whether this process triggers an attribute change event. Specifically:

Since you had power cycle to the matter device, it is not expected to generate any attribute change event/callback because powering off the MCU does not mean that OnOff attribute value is changed.