Which device types Matter supports
Ninety-two device types in the specification. A much shorter list in your app. Here is where the line falls.
"Supported" means three different things#
This is the distinction that makes the rest of the page readable. A category can pass one, two or all three of these tests, and marketing rarely says which.
| Level | The question | How to check |
|---|---|---|
| 1. In the specification | Has the alliance defined a device type for this? | The release history in every Matter version |
| 2. Certified in a product | Has anyone built and certified hardware for it? | The alliance's certified product database |
| 3. Exposed by your controller | Does your app render it as something usable? | Your ecosystem's own supported device type documentation |
All three have to be true before you get a working device. Level 1 without level 2 is a specification with no hardware, which is where soil sensors and irrigation sit. Levels 1 and 2 without level 3 is hardware your app will not show properly, which is where energy management and cameras sit for most people. The compatibility checker answers all three for a given device class and platform, and the Matter feature gap tracker keeps the third column current.
Fully supported: buy on the logo#
These categories are in the 1.0 to 1.2 baseline, have hundreds of certified products, and are implemented by every major controller. If a device in this list carries the Matter logo, it will work.
| Category | Since | What you get |
|---|---|---|
| On/off, dimmable and color lights | 1.0 | On, off, brightness, color temperature, solid color |
| Wall switches and dimmers | 1.0 | Switch state, dim level, generic switch events for buttons |
| Smart plugs and outlets | 1.0 | On, off, and power and energy readings if the device implements them |
| Door locks | 1.0 | Lock, unlock, state, credential management on capable controllers |
| Thermostats | 1.0 | Mode, setpoints, current temperature and humidity |
| Window coverings | 1.0 | Open, close, position, tilt on capable hardware |
| Fans | 1.0 | Speed, mode, direction |
| Contact, motion, occupancy, temperature, humidity, light sensors | 1.0 | State and readings |
| Smoke and CO alarms | 1.2 | Alarm state, test state, battery |
| Air quality sensors | 1.2 | Particulates, CO2, NO2, VOCs, CO, ozone, radon, formaldehyde |
The caveats inside this list are about features, not support. Color bulbs lose animated effects, because effects are not in any Matter cluster: see smart lighting that stays compatible. Locks expose the lock, not the vendor's guest scheduling: see smart locks and the Aliro standard. Thermostats expose setpoints, not the vendor's learning behavior or multi-zone logic: see smart thermostats and HVAC.
Partially supported: the specification has it, your app shrinks it#
Every category here exists in the specification and has certified hardware. What varies, sometimes wildly, is what your controller does with it.
Robot vacuums (1.2). Matter carries start, stop, run mode and dock state. It does not carry maps, no-go zones, virtual walls, scheduling or consumable life, because those are not in the specification at all. The optional service area cluster offers only a list of vendor-named area IDs, Google Home does not implement it, and Alexa maps only run mode. Apple Home added robot vacuums in iOS 18.4. Keep the vendor app. Robot vacuums in a smart home has the detail.
Large appliances (1.2 and 1.3). Refrigerators, temperature controlled cabinets, room air conditioners, dishwashers, laundry washers, air purifiers, then ovens, cooktops, microwaves, extractor hoods and laundry dryers. Certified hardware is thin outside a few brands, and controller support is the newest of any category: Google shipped the 1.2 appliance types in September 2025, roughly 23 months after the specification. Apple Home still lacks air purifiers and dishwashers.
Cameras and video doorbells (1.5). The specification is thorough, the hardware barely exists, and one ecosystem supports it. Only SmartThings ships user-facing Matter camera support. Apple, Google and Amazon have shipped nothing, and Home Assistant's support runs in its Matter server console rather than as normal camera entities. Matter cameras: what is real is the full picture, including which certified cameras you can actually buy.
Closures (1.5). The redesigned closures model covers garage doors, gates and shades with consistent position reporting. Older window covering device types still work everywhere; the new model is shipping on SmartThings and partially on Home Assistant. Blinds, shades and garage doors covers the safety implications of position control.
Energy (1.3, 1.4 and 1.5). EV chargers and device energy management since May 2024, solar, battery storage, heat pumps and water heaters since November 2024, tariff and carbon intensity data since November 2025. SmartThings and Home Assistant expose them. Apple Home, Google Home and Alexa expose none of it, and Apple Home has no energy monitoring of any kind. Matter for energy explains what to do about that.
Water and irrigation (1.3 and 1.5). Water valves, leak, freeze and rain detectors are well supported. Soil sensors and irrigation systems are in the specification with almost no certified hardware behind them.
Media players (1.0). The media playback and content launcher clusters exist and are used mostly for TV-like devices. They do not address multi-room audio in any form, which is the next section.
Not covered at all#
These are the categories that do not exist in Matter as of 1.6. No device type, no cluster, no partial path. If you need one, Matter is not part of the answer.
| Missing category | Why it matters | What to do instead |
|---|---|---|
| Security and alarm panels | The hub of a whole product class has no representation | Vendor app, or a local platform integration |
| Keypads | Arming, disarming and PIN entry have nowhere to go | Vendor ecosystem, or Z-Wave keypads on a local hub |
| Sirens | Cannot be triggered by a Matter automation | Zigbee or Z-Wave siren on a local hub |
| Multi-room and streaming audio | An open request since January 2024, still unaddressed | AirPlay, Chromecast, Sonos, or a platform-native integration |
| Humidifiers and dehumidifiers | Common device, no device type | Vendor app, or expose as a plug for on/off only |
| Circuit breakers and electrical panels | The most useful energy data in the house is unreachable | Vendor cloud integration on a local platform |
| Camera AI analytics | Zone triggers have exactly one reason value: motion | Vendor app for person and package detection |
| Robot mowers | No device type despite mature hardware | Vendor app |
| Pet feeders | No device type | Vendor app |
Most of these appear in the draft 1.7. Treat that as direction, not as a date, and remember that Fabric Sync appeared in a release and was then never implemented by anyone.
The workaround that actually works#
For anything in the not-covered table, the realistic pattern is the same: run one platform that integrates the device natively, and let Matter carry only what it carries well.
A hub can also act as a Matter bridge, presenting Zigbee, Z-Wave, infrared or cloud devices to your Matter controllers as bridged devices. That gets a siren or a keypad into a Matter ecosystem in reduced form, and it is a genuinely good on-ramp for older gear. The costs are fixed and worth knowing in advance: bridged devices lose vendor-specific features, and firmware updates for bridged sub-devices are never available over Matter.
Four checks before you buy#
How many device types does Matter support?
Ninety-two, as of Matter 1.6 in June 2026. That count comes from the published data model and differs slightly from marketing counts, which sometimes group or split types differently. Matter 1.6 added none; the last release to add device types was 1.5 in November 2025, which added 18.
Does Matter support security systems?
No. There is no device type for a security or alarm panel, a keypad or a siren. Individual sensors work fine, so contact and motion sensors will appear in your app, but the panel that arms and disarms them has no Matter representation. Security panels are expected in a future release.
Does Matter support speakers and multi-room audio?
No. Media playback clusters exist for TV-like devices, but multi-room and streaming audio has no device type. It has been an open request in the alliance's public repository since January 2024. Use AirPlay, Chromecast or a platform-native integration for audio.
Why does my Matter appliance show as a plug?
Because your controller does not implement that appliance's device type and is falling back to the nearest thing it understands. The device is reporting correctly. Check your ecosystem's supported device type list; appliance support is the newest and least even part of every controller.
Can I use Matter with my robot vacuum's maps?
No. Maps, no-go zones, virtual walls, schedules and consumable life are not in the Matter specification. Matter gives you start, stop, run mode and dock state, which is enough for an automation and not enough to replace the vendor app.
Does a Matter certified device work with every ecosystem?
It works with every ecosystem that implements its device type. Certification is against the specification, not against Apple Home or Google Home. A certified water heater is genuinely certified and will still be invisible in three of the five major controllers.
What is the difference between a device type and a cluster?
A cluster is one bundle of attributes, commands and events, such as on/off or level control. A device type is a named recipe that says which clusters an endpoint must and may implement. Controllers build their user interface from the device type, which is why an unrecognized device type produces a stripped-down tile.
Primary sources
Specification and vendor documentation we checked while writing this page. Where a claim depends on firmware behaviour rather than a published spec, the page says so inline.