Test Suite: bridge error & Local Fulfillment mismatch

[winglee]

Dear Google Home Developer Support,

We are developing a Cloud-to-cloud smart home integration in the Google Home Developer Console. We are blocked or confused on several related points and would appreciate guidance on the correct configuration and where to escalate if the console or Test Suite behavior is incorrect.

1. “No bridge device is found” (Device type check)
When running the Google Home Test Suite, we see warnings/errors such as “No bridge device is found in FAN” (or similar, listing device types under test). Our devices are Wi‑Fi / cloud-connected; we do not expose a Matter Control Bridge in SYNC.

2. Local Fulfillment shown in Test Suite while Console toggle is OFF
The Test environment header shows our integration as “… Local Fulfillment”, but in Setup & configuration the Local fulfillment toggle is OFF and we have not intentionally enabled Local Home. Question: Why would the Test Suite still label the run as Local Fulfillment? Should we create a new test plan and ensure no “Local Home / Local fulfillment” options are selected in Test Suite settings, or is this a display/backend inconsistency?

Thank you for your time.

[arm_dpe · Accepted solution]

Thanks for reaching out. Please find my troubleshooting guide below.

1. “No bridge device is found” typically occurs because the Test Suite expects to validate Bridge and Sub-device logic if it detects certain traits or attributes in your SYNC response that imply a parent-child relationship. If your devices are standalone Wi-Fi fans, Google expects them to be top-level devices. However, if your SYNC response includes an otherDeviceIds field or if the fan is logically nested under another device ID, the Test Suite looks for a device with the action.devices.types.BRIDGE type to "bridge" the communication.
2. Seeing "Local Fulfillment" in the Test Suite while the toggle is OFF in the Console could point to a caching issue or a legacy Test Plan configuration. When you create a new Test Plan in the Test Suite, there is a checkbox for "Local Home SDK". If this was checked during the initial plan creation, the Test Suite will attempt to route discovery via mDNS/UDP even if the Console toggle is now off. My recommendation is to delete your current Test Plan, clear your browser cache (or use an Incognito window) and create a new test plan.