Matter controller
A Matter controller is the software brain that commissions Matter devices onto its fabric and controls them: Apple Home (via a home hub), Google Home, Amazon Alexa, SmartThings, Home Assistant, Hubitat, or Homey. Every Matter setup needs at least one, and the controller — not the device — decides which device types and features you can actually use.
The controller holds the fabric’s credentials, runs automations, and provides the app and voice interface. In most consumer ecosystems the controller function lives in a hub-like device that stays home and online: an Apple TV or HomePod for Apple Home, a Nest hub or speaker for Google, an Echo for Alexa. Home Assistant, Hubitat, and Homey run the controller on the hub itself.
Controllers differ meaningfully in coverage. A device type added in a recent Matter release may be supported by one ecosystem and ignored by another for a year, and features like a lock’s user codes or a thermostat’s schedules are exposed unevenly. This is why “Matter-certified” answers only half of “will it work with my setup” — the other half is the controller, which is what our per-hub compatibility pages are for.
| Hubs in this dataset that are Matter controllers | 19 of the 32 we track |
|---|---|
| Apple Home | Apple TV 4K, HomePod, HomePod mini — a phone alone is not a controller |
| Google Home | Nest Hub (2nd gen), Nest Hub Max, Google TV Streamer, Nest Wifi Pro |
| Alexa / SmartThings | Echo (4th gen), Echo Hub, Echo Show 10; SmartThings Station and Aeotec Smart Home Hub |
| Independent | Home Assistant, Hubitat Elevation C-8 / C-8 Pro, Homey Pro, Aqara Hub M3 |
| Controllers per device | At least 5 fabrics required by the spec, one admin each |
Controller, commissioner, admin
Matter uses three words that people conflate. The controller is the node that holds a fabric’s operational credentials and issues commands. The commissioner is whatever performs the setup handshake — usually your phone, borrowing the controller’s authority for the duration. The administrator is the controller privilege level that can add and remove other fabrics.
This is why your phone is not the answer to “what is my Matter controller”. The Home app on an iPhone commissions a device, but the Apple TV or HomePod holds the fabric and keeps talking to the device when the phone is in your pocket or out of the house. Apple, Google, and Amazon all work this way. Home Assistant, Hubitat, and Homey collapse the roles onto one box you own.
The practical test is simple: unplug the candidate device and see whether scheduled automations still fire. If they stop, that box was your controller. If they were never running locally to begin with, the automation engine is in a vendor cloud and the controller is doing less than the marketing implies.
The controller, not the device, sets your feature ceiling
A Matter device advertises the clusters it implements; the controller decides which of them to surface. When those two disagree, the device silently loses features. Energy reporting on a smart plug, a lock’s user-code management, a thermostat’s weekly schedule, a robot vacuum’s room selection, and camera streams are all places where certified devices routinely show up as a stripped-down on/off switch in one ecosystem and a full device in another.
The lag is structural. A device type lands in the specification, silicon vendors ship SDK support, manufacturers certify, and only then do the ecosystems build UI for it — a chain that has typically taken six to eighteen months per step. Home Assistant tends to move first because it exposes raw clusters rather than waiting for a designed experience; the big three move later but with more polish.
So the useful buying question is not “is this Matter certified?” but “does my controller support this Matter device type today?” Certification is a floor, not a promise. Our per-hub works-with pages compute exactly this intersection from the certification ledger and each hub’s documented capabilities.
Choosing one, and running several
Four things separate controllers in practice: whether automations execute locally, which extra radios the hardware carries, whether a subscription gates anything, and how quickly the vendor adopts new device types. Home Assistant, Hubitat, and Homey Pro run everything locally and add Zigbee and Z-Wave radios; Apple Home runs locally through its home hub but adds no other radios; Alexa, Google Home, and SmartThings still execute a large share of routines in the cloud.
Running more than one controller is normal, not a compromise. Multi-admin means a single device can sit in Apple Home for family voice control and in Home Assistant for the automation logic, each talking to it directly. The cost is that scenes, room assignments, and automations do not sync between them, so you should pick one controller as the automation brain and treat the others as interfaces.
One caution: each ecosystem consumes a fabric slot, and the specification only requires five. A household running Apple, Google, Alexa, and the maker’s own app is already at four, and cheap devices rarely exceed the minimum. If a device refuses to join a fifth ecosystem, that limit — not a fault — is usually why.
Frequently asked questions
Is my phone a Matter controller?
Not on its own. The phone commissions devices and gives you the app, but the fabric credentials live on a device that stays home and online — an Apple TV or HomePod, a Nest hub or speaker, an Echo, a SmartThings hub, or a Home Assistant, Hubitat, or Homey box. Without one, Matter devices work only while your phone is on the same network, and automations do not run at all.
Can I use two Matter controllers at once?
Yes. Multi-admin lets one device join several fabrics simultaneously, each controller talking to it directly and locally. Pair it in the first ecosystem, generate a share code, add it in the second. Automations and names stay separate per ecosystem, and most devices support around five fabrics before slots run out.
Do I need a Matter controller if all my Matter devices are Wi-Fi?
Yes. Transport and control are separate questions: Thread devices need a border router, but every Matter device needs a controller to hold its credentials, run automations, and provide the interface. A Wi-Fi Matter plug with no controller is just a plug that never got commissioned.
Which Matter controller supports the most device types?
Home Assistant, generally — it surfaces clusters as soon as its Matter stack understands them rather than waiting for designed UI, so new device types appear months earlier. Apple Home and SmartThings tend to follow, with Google Home and Alexa varying by category. For any specific device, check the per-hub compatibility page rather than trusting a general ranking.
What happens if my Matter controller fails?
The devices keep their other fabric credentials, so anything shared with a second ecosystem keeps working. Devices that only knew the dead controller need to be re-commissioned, which usually means a factory reset and the original QR code. This is the strongest practical argument for keeping the setup codes and for having a second controller on important devices.