Matter 1.5 Air Quality Sensor: Endpoint merge threshold and missing sensor display issue

Johnny15 — Wed, 18 Mar 2026 10:44:13 GMT

My questions for Google Home Matter support team:

When I add more than a certain number of sensor clusters to my Air Quality Sensor (Endpoint 0x0310), Google Home automatically splits the Temperature & Humidity endpoints into a separate tile, instead of showing them together.

What is the exact threshold for endpoint merging/splitting in Google Home for Matter devices? Is it based on the number of clusters, device types, or other logic?
My device runs Matter 1.5, and I have implemented these sensor clusters:
- TVOC
- HCHO (Formaldehyde)
- PM1
- Radon
- CO
- PM10
These attributes are correctly reported over Matter, but Google Home App does NOT display them.

Could you clarify which sensor types Google Home currently supports, and whether support for the above sensors is planned?

Re: Matter 1.5 Air Quality Sensor: Endpoint merge threshold and missing sensor display issue

arm_dpe — Tue, 07 Apr 2026 19:37:24 GMT

The current documentation for the Google Home ecosystem and the Matter Virtual Device (MVD) provides specific details regarding Matter 1.5 sensor support and tools for testing upcoming features.

Supported Matter 1.5 Sensor Clusters

According to the supported devices list, the Air Quality Sensor device type (Matter 1.2+) is officially recognized, but visual rendering in the Google Home App (GHA) varies by cluster:

Currently Supported for GHA Rendering:

PM2.5 (Concentration Measurement)
CO2 (Carbon Dioxide Concentration Measurement)
Temperature (Temperature Measurement)
Relative Humidity (Relative Humidity Measurement)
Air Quality (General Air Quality Cluster)

Attributes Lacking GHA UI Support:

While Matter 1.2/1.5 includes clusters for TVOC, CO, PM1, PM10, Radon, and Formaldehyde (HCHO), these are not currently listed as having full "Google Home app (GHA)" control or visual support in the official ecosystem compatibility table.

Roadmap and Future Support

Public roadmaps for specific attribute rendering are generally not published in the developer documentation. However, support for newer Matter specifications is rolled out incrementally. To determine if a specific attribute is currently in the "pre-release" or "testing" phase for the ecosystem, developers are encouraged to use the Matter Virtual Device (MVD).

Using the Matter Virtual Device (MVD)

The Matter Virtual Device tool is a desktop application that emulates different Matter device types. It is the recommended way to:

Verify UI Rendering: Create a virtual Air Quality Sensor with various clusters (e.g., TVOC or PM10) to see exactly how the GHA renders them before committing to hardware development.
Test Future Releases: As Google updates the MVD and the GHA, new sensor types often appear in the virtual tool first. If a cluster is selectable in the MVD but doesn't appear in GHA, it indicates the ecosystem is still in the process of implementing the visual frontend for that attribute.

Debug Endpoint Logic: You can use MVD to test different endpoint configurations to see if the "tile splitting" behavior persists with virtual devices, helping you isolate whether the issue is with the hardware implementation or GHA's current UI logic.

topic Re: Matter 1.5 Air Quality Sensor: Endpoint merge threshold and missing sensor display issue in Smart Home Developer Forum

Matter 1.5 Air Quality Sensor: Endpoint merge threshold and missing sensor display issue

Re: Matter 1.5 Air Quality Sensor: Endpoint merge threshold and missing sensor display issue

Supported Matter 1.5 Sensor Clusters

Roadmap and Future Support

Using the Matter Virtual Device (MVD)