A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://developers.home.google.com/matter/get-started below:

Get started with Matter | Google Home Developers

Get started with Matter

Stay organized with collections Save and categorize content based on your preferences.

Google's Home Developer program allows device manufacturers to connect their smart home devices with the Google Home ecosystem. We are expanding the Smart Home Actions local fulfillment path with the ability to add Matter-enabled devices for setup using the Google Home app (GHA) and control them using Google Assistant, GHA, or smart displays like the Google Nest Hub (2nd gen).

This documentation describes how to get started with building and integrating a Matter-supported platform in the Google Home ecosystem.

Disclaimers

Regarding the procedures described in the Matter documentation, be aware of the following:

How to build

To build a Matter-enabled device that integrates with the Google Home ecosystem, you'll work with a Matter-compatible development board and the Matter SDK.

The easiest way to get started is by going through our codelabs. We recommend doing at least one of the following codelabs:

After that, check our list of supported devices to ensure that what you plan to integrate is supported in the Google Home ecosystem. Then read through the Developer Checklist to understand the entire development flow from project creation to launch.

Supported Devices Developer Checklist

Definitions

The following terms are used throughout this documentation:

Border router
A hub that implements a general-purpose Thread Border Router for Thread-enabled devices.
Hub
A supported Google Nest device, such as the Google Nest Hub (2nd gen). A hub is required to control Matter-enabled devices through other surfaces such as Assistant, the GHA, and smart displays.
Matter-enabled device
A device or development board that has been flashed with a Matter-enabled build or sample app.
Mobile device
The test phone used to assist with pairing. Currently this is an Android phone.
Prerequisites

Recommended IDE extensions for Matter development

In order to fully integrate a Matter-enabled device with the Google Home ecosystem, a developer must have:

  1. A Google hub with Thread support to serve as both a Border Router for Thread-enabled devices and as a local fulfillment path for routing Smart Home intents.
  2. A mobile device (test phone) that meets the minimum requirements:
  3. A Vendor ID (VID) and Product ID (PID) for the Matter-enabled device.
  4. A Matter-enabled device. This device should be one of the Matter device types supported in the Google Home ecosystem, and could be:
Vendor ID

By default, you can use one of the VIDs allocated by the CSA for testing purposes. Select one of the following: 0xFFF1, 0xFFF2, 0xFFF3, 0xFFF4.

To use a Production VID so that your integration can be certified and launched, you must first have it verified by Google to ensure that it has been issued to you by the CSA.

This VID should be implemented in your device's firmware.

A Matter device can only be paired in the Google Home ecosystem in certain Vendor ID and device type scenarios.

VID and PID can only be used once for one integration. If you want to use the same VID or PID in your integration, you need to either:

Table: Vendor ID (VID) and device type pairing scenarios Which types of users can commission the device into the Google Home ecosystem? VID type VID certification and console integration status Production
(Consumer users) Development
(Developers, Field Trial users) Test No integration in the Developer Console (cannot be certified) Test Integration exists in the Developer Console (cannot be certified) Production Not certified, integration does not exist in the Developer Console Production Not certified, integration exists in the Developer Console Production Certified in the Alliance DCL, integration does not exist in the Developer Console Production Certified in the Alliance DCL and integration exists in the Developer Console Product ID

Information about the device is read from the Matter Basic Information Cluster. The Product ID encoded in your device's firmware must match the Product ID of the Matter integration in the Developer Console.

Unsupported features

Some Matter clusters are not yet exposed to users, though they may be used by the system. In most cases, this means that attributes exposed through these clusters aren't visible to end users:

Table: Matter clusters not exposed to users in the Google Home ecosystem Cluster Type Clusters Core Application

¹ See On/Off Light Switches for how this impacts On/Off Light Switches.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2023-07-17 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Incorrect information","incorrectInformation","thumb-down"],["Not enough information/samples","notEnoughInformationSamples","thumb-down"],["Too complicated","tooComplicated","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2023-07-17 UTC."],[],[]]


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.3