Request Guidance for Testing a Non-Certified Matter Bridge with Google Home (POC Development)

[RoshanKasper]

Hello All,

I am currently working on a Matter-based development project and would like to create a Proof of Concept (POC) that includes a custom, non-certified Matter bridge and several bridged devices for internal testing purposes. For testing, I am using a Google Nest Hub (2nd Gen) as the Matter controller together with the Google Home app.

I understand that production devices must be fully certified through both the CSA Matter certification process and Google’s “Works With Google Home” program. However, I am trying to clarify the correct procedure for developers who want to test Matter devices or bridges in a non-certified, development-only environment before starting the certification process.

Specifically, I would like your guidance on the following points,

1. How can developers commission and test non-certified Matter devices or virtual Matter bridges (e.g., software prototypes, custom bridge, Node-RED bridge, Linux Matter bridge example, or the Google Codelab “Virtual Matter Device”) with Google Home during development while using a Nest Hub (2nd Gen) as the controller?

2. Is there an official developer mode, test environment, or device attestation override that allows experimental Matter devices to be paired with the Google Home ecosystem for development purposes only?

3. If the only supported method is through the Google Home Developer Console, could you please provide:

   The correct setup steps required to enable commissioning of an uncertified test device or bridge, and Any restrictions or known limitations specifically for Matter bridges, since bridges normally require full certification.

4. Are there additional tools (e.g., Google Home Test App, GHMSDK commissioning flows, reference apps, development test environments) that developers should use when testing Matter devices or bridges prior to certification?

My goal is to validate Matter functionality, bridge behavior, commissioning flows, and interactions with Google Home before beginning the full certification process. Any official guidance or recommended developer workflow would be greatly appreciated.

Thank you for your assistance. I look forward to your support and any documentation regarding the correct development pathway.

Kind regards,

Roshan Madusanka

[arm_dpe · Accepted solution]

Hi Roshan,
The official and supported method for commissioning and testing uncertified Matter devices, including custom or virtual bridges, with a Google Nest Hub (2nd Gen) controller is through the Google Home Developer Console.

There is no general "developer mode" or device attestation override on the Nest Hub itself. The mechanism to allow uncertified devices to commission is managed entirely by setting up an integration project within the Google Home Developer Console and using specific Test Vendor ID (VID) and Test Product ID (PID) combinations.

1. Developer Console Setup Steps

To enable commissioning of your uncertified test device or bridge:

• Go to the Google Home Developer Console and create a new project.

• Create a Matter integration within that project.

• In the Setup phase of the integration, you must use one of the officially designated Test VIDs for development. The most common and recommended Test VID is 0xFFF1.

• You must also configure a Test PID that matches the one configured in your device or bridge's firmware/code (e.g., 0x8005 for a Light, 0x800E for a Thermostat). The combination of the Test VID and Test PID tells the Google Home ecosystem that this is a non-certified, development-only device that should be allowed to commission.

2. Commissioning Your Test Device

Once your project is configured in the Developer Console:

1. Ensure Prerequisites are Met:

   • Your Nest Hub (2nd Gen) is set up in the same Google Home structure (house) as the Google account used in the Developer Console.

   • The Nest Hub and your development device (Matter bridge) are on the same Wi-Fi network.

   • You are running the commissioning process from an Android phone (Android 8.1+ is compatible, but newer is recommended) or an iOS device with the latest Google Home app.

   • Your development device is powered on and in pairing mode (broadcasting its Matter commissioning information).

2. Use the Google Home App (GHA):

   • Open the Google Home app and initiate the device setup process (usually a pop-up, or by tapping Devices > Add > Matter-enabled device).

   • Scan the Matter QR code or enter the manual setup code provided by your virtual or custom Matter device/bridge.

The GHA will use the Test VID/PID registered in the Developer Console to bypass the production device certification check and allow the device to be commissioned onto the fabric, using your Nest Hub as the Matter Controller.

3. Restrictions and Limitations for Matter Bridges

While the above process supports both end-devices and bridges, here are key considerations for testing your uncertified Matter bridge:

• Bridged Devices: The devices exposed by your custom bridge (the "bridged devices") will also be commissioned under the same Test VID/PID as the bridge itself. You do not need to create separate integration projects for each device type exposed by the bridge, but their device types must be correctly configured in your bridge's Matter implementation.

• Certification Requirement: As you noted, bridges normally require full certification. While you can test a non-certified bridge using the Test VID/PID, this is strictly for development and internal testing. You cannot launch a product with a bridge integration using a Test VID.

• Google Home Test Suite: You should use the Google Home Test Suite (accessible via the Developer Console) to validate your bridge's behavior. For bridges in particular, you need to ensure the Test Suite runs checks against all the bridged device types (endpoints) to ensure they comply with Google's requirements, even in the development phase.