IssueTracker

NOTE: This issue tracker is for Matter developer bugs and feature requests on Google Smart Home Ecosystem only. Please include include your project id, vendor id and product id in the project information section if available. [PLEASE DO NOT REMOVE THE DEFAULT HOTLISTS OR CHANGE THE DEFAULT ASSIGNEE]

Description of the issue

Hello, I am currently developing Matter-over-Wifi bridge device. I have noticed strange behavior: when device reboots, Google Home loses all bridged devices, even though all endpoints for bridged devices are still present on a device.

• Test Environment: Google Nest Gen 2 Hub as a Matter controller, Matter bridge device with slightly modified ESP32 Matter Bridge Example project. Additionally, Home Assistant OS is used as second fabric for testing. Also, chip-tool is used for reading attribute values. Google Home Matter network consists of 2 devices: smart lighting and DUT.
• When did it fail? Observed behavior occurs on any reboot condition of the device: soft reset, off-on cycle, firmware update with storing device credentials/network information intact etc.
• What was the error?
  • Phone app shows next device steps during bridge device reboot: "bridge and bridged devices offline" -> "bridge device online, bridged - offline" -> "bridge device online, bridged devices disappear from UI"
  • In Google Home UI - bridged devices just disappear

Reproduction Information

1. A device with ESP32 board. ESP32 firmware - Matter-Zigbee Bridge Example project with modifications: Zigbee-related functionality removed, test program that adds virtual bridged devices after network commissioning once. For adding bridged devices,
2. Project Matter configuration: Test certificates, Vendor ID 0xFFF2, Device ID 0x8002. Attestation, Device Instance Info - Test, Device Info - none, Commissionable Data - Custom (Dynamic Commissionable Data Provider from ESP32 example code)
3. Device Is commissioned to Google Nest fabric first, then device is added to chip-tool and HA OS fabrics via device sharing.
4. Test project execution flow: start Matter Core, open commissioning window if device is not yet connected to fabric. If commissioned - add 2 virtual test devices (On-Off light, Dimmable light) once, then idle.

• After virtual devices are added, after some time they appear on Google Home UI as 'Lamp' and 'Lamp(2)'. These virtual devices are responsive and can be controlled with Google Home UI.

• If Bridge device reboots for any reason and reconnects to the fabric, Google Home UI does not show these virtual devices anymore.

• Issue is consistent with Google Nest Gen 2 fabric. Until device is rebooted, none of bridged devices do not disappear.

Analysis

• As for now, no Google-related logs are collected. To pinpoint issue to Google Nest fabric, Bridge device is shared to chip-tool and Home Assistant fabrics.
• Home Assistant continues holding bridged device information after Bridge device reboot.
• chip-tool is used to read Bridge device's PartsList attribute of Descriptor Cluster of Aggregator Endpoint. PartsList data is persistent across device reboot cycles. Bridged endpoints continue to receive commands and perform application-related functions (OnOff and LevelControl clusters).
• This indicated to me that something in this behavior is related to Google Home Matter network alone.

App Info

• Google Home App Version: 3.28.1.7
• Platform Version/OS Version: 00WW_2_350_SP03
• GMS Core Version: 25.02.34 (190400-716794385)

Device Info

• Thread Version On Device (if applicable):
• Device/dev board version:
• Firmware Version:
• Devices Impacted:

Hub Info (If applicable)

• Hub Type: Nest Gen 2 (GUIK2)
• Firmware Version: 62.0.7.676990136 (Software), 22.20240805.103.161 (Fuchsia), 3.75.446835 (Chromecast)

Matter project information

• Project ID: dimmer-temperature-combi-77313
• Vendor ID: 0xFFF2
• Device ID: 0x8002
• Device Type: Control Bridge

Attachments

None