Matter Works on One Platform but Not Another? Multi-Admin
Your Matter device works in Apple Home but breaks in Google Home or Alexa. Why multi-admin sharing fails, and what to check before you buy.
You set up a bulb, a button, or a sensor, and it works perfectly in one app. Then you add it to a second ecosystem so the rest of the family can use it, and something goes sideways: the device shows up but a button is missing, or a mode you had yesterday is gone, or the thing just stops responding to either app. The promise of Matter is that this isn’t supposed to happen. The reality in June 2026 is that it happens a lot, and there are really only three causes underneath all of it.
This guide is the troubleshooting sibling to our Matter and Thread explainer, so it won’t re-walk the whole protocol. Quick reminder for context: Matter is a common language smart-home devices speak so they can work across Apple Home, Google Home, Alexa, and SmartThings instead of being chained to one app. We didn’t test any of these ecosystems ourselves. What follows is the consensus from the Connectivity Standards Alliance plus smart-home reporters who did, and we’ve flagged the parts that are changing week to week.
Why does my Matter device work on one platform but not another?
Almost always, one of three things: the controller you’re failing on runs an older Matter version than the one you set the device up with, that controller hasn’t added support for the device’s category yet, or the act of sharing the device across ecosystems (multi-admin) introduced a bug. The device itself is usually fine.
Think of it less as a device problem and more as a controller problem. A “controller” is the app and hub that commission and manage a Matter device: Apple Home, Google Home, the Alexa app, SmartThings, or Home Assistant. Each one ships its own Matter implementation, on its own schedule, and they don’t move in lockstep. As 9to5Mac framed it in March 2026, Apple, Google, and Amazon are “fully focused on pursuing their own agendas,” which leaves a “huge onus on each manufacturer” to make a device work on every platform before release. So a device built and certified to a newer spec can do everything in the app that’s caught up, and quietly less in the one that hasn’t. That’s the short version. The rest of this guide is the long one.
What is Matter multi-admin, and why does sharing across Apple, Google, and Alexa break it?
Matter multi-admin is the feature that lets a single Matter device be controlled by several ecosystems at the same time. Commission a bulb in Apple Home, generate a sharing code, and you can add that same bulb to Google Home and Alexa so each platform controls it independently. Under the hood, each ecosystem joins the device as its own “fabric,” and the spec is built to hold several at once.
Here’s the catch. As of June 2026, multi-admin is also Matter’s most fragile feature in practice. Android Authority, after living with it, called multi-admin “absolutely unreliable,” describing the pattern bluntly: “your device works well with one platform, you pair it with another, and boom, things start disappearing off the network or not responding to commands.” The reporter’s own Meross power strip started dropping off both Google Home and Home Assistant the moment it lived in two controllers at once. Owners report the same shape of failure across forums: the single-platform setup is rock solid, and the trouble starts at the moment of sharing.
Why is sharing the weak point? Each fabric maintains its own secure relationship with the device, and the device has to keep all of them in sync over a low-power radio. When the implementations disagree, even slightly, about state or timing, you get devices that look paired but behave like they’re not. It’s the seam between platforms, not any one platform, that tends to tear.
Why does the slowest controller in your house set the ceiling on features?
Because a shared device can only reliably expose what every controller it’s joined to understands. Add a device to three ecosystems and the weakest implementation among them effectively caps the shared experience.
A controller can’t surface a Matter feature it doesn’t yet implement. So if Apple Home understands a device’s full set of modes but Google Home only models the basics, the version of that device living in Google Home shows up thinner, and any automation built there has less to work with. Worse, when the laggard controller mishandles something the others rely on, sharing the device can degrade it everywhere, not just in the slow app. This is why the advice you’ll see repeated is to commission a device in your most capable, most up-to-date controller first, and to be conservative about how many ecosystems you share a single device into. More fabrics is more surface area for one weak link to spoil.
Why is a device recognized but missing buttons or modes on one app?
Usually because the two controllers support different Matter device categories, or different depths of the same category. The device pairs (basic recognition is the easy part), but the richer controls don’t render because that app hasn’t built them yet.
Basic control travels well across Matter: on, off, brightness, lock, set temperature. The advanced and device-specific stuff is where apps diverge. The clearest 2026 example is IKEA’s BILRESA smart button on Google Home. Per 9to5Google in February 2026, the button would pair but “wouldn’t show up in the automations flow even if it did successfully pair,” and there was a “weird delay” before buttons appeared as automation triggers at all. Google only started supporting smart buttons as automation triggers in a then-recent Home app update, which is why the same physical button could be a working trigger in one ecosystem and a dead end in another. None of that is the button being broken. It’s the controller’s support for that category lagging the device.
What changed with IKEA in 2026, and why are people hitting this now?
Two things landed close together and pushed a wave of people onto raw Matter at once. First, in late 2025 IKEA quietly removed its legacy cloud integrations for Google Home, Apple Home, and Alexa. Then in early January 2026 it launched a broad, cheap Matter-over-Thread lineup. So a lot of households went from “IKEA’s own cloud link” to “Matter is the only bridge” in one step, right as inexpensive new hardware flooded in.
Per Matter Alpha, the cloud-integration change (surfaced around November 11, 2025) means the Matter Bridge is now the only way for new users to connect IKEA smart products to third-party ecosystems, and once an old integration is disconnected, it can’t be re-established. The new range is large: SmartThings put it at 21 new Matter-over-Thread products launching in early January 2026 with dozens more through the year, spanning KAJPLATS bulbs, plugs, the BILRESA controls, and a stack of sensors (the MYGGBETT door/window sensor, MYGGSPRAY motion sensor, ALPSTUGA air-quality sensor, KLIPPBOK leak sensor). SmartThings says they work out of the box on its platform.
The reception has been rough. Android Authority and 9to5Google documented pairing failures and unreliable automations across Apple Home, Google Home, and Alexa, and IKEA itself acknowledged “some customers are experiencing connection issues when setting up their devices in certain home environments.” A couple of things to keep straight as a buyer. These are Thread devices, so they need a Thread border router on your network to work at all (the IKEA DIRIGERA hub is one, but so are many HomePods, Echos, and Nest devices, covered in the Matter and Thread explainer). And reporting traced a lot of the worst instability to multi-admin: routing everything through DIRIGERA and then sharing into multiple controllers. This whole IKEA situation is moving fast; treat the specifics here as a June 2026 snapshot and check current reporting before you make decisions on it.
What should you check before buying a Matter device?
Three things, in order, and the buy decision should turn on all three rather than the Matter logo alone. The logo guarantees the device speaks Matter. It does not guarantee your app does everything you want with it.
- Your controller’s Matter support. Open the app you actually live in (Apple Home, Google Home, Alexa, SmartThings) and confirm it’s updated. The newer the controller’s Matter version, the better your odds, especially for anything beyond a simple bulb or plug.
- The device category. Check that your controller supports that type of device, not just “Matter” in general. Buttons, scene controllers, air-quality sensors, and leak sensors are exactly the categories where support arrived late and unevenly. The BILRESA button is the cautionary tale.
- Whether you need a Thread border router. If the device is Matter-over-Thread (most of IKEA’s 2026 sensors and bulbs are), it’s useless without a border router on your network. Matter-over-Wi-Fi devices skip this. Know which one you’re buying.
If you’ve owned the device a while and it suddenly misbehaves, that’s a different problem; start with the general connection troubleshooting order instead.
| Controller | What generally works | Known multi-admin / feature gaps (June 2026) |
|---|---|---|
| Apple Home | Solid basics (lights, locks, plugs, thermostats); strong Thread support via HomePod/Apple TV border routers | Reports of devices timing out during onboarding; sharing a device out to other ecosystems can destabilize it; some newer device types lag |
| Google Home | Basics work; added smart-button automation triggers in an early-2026 Home app update | Heavily implicated in the IKEA rollout: late or missing button/automation support, intermittent triggers, shared devices dropping off |
| Amazon Alexa | Broad device support and easy commissioning for common categories | Multi-admin sharing into Alexa alongside other controllers is a common failure point; advanced/device-specific modes often need the maker’s app |
| SmartThings | Says IKEA’s 2026 Matter-over-Thread line works out of the box; border router built into many Samsung products | Strongest stated Matter support, but real-world multi-admin still depends on the other controllers a device is shared into |
Will it get better, and what does a firmware or app update actually fix?
Probably, slowly, and unevenly. The pattern so far is that updates fix real things but rarely the whole thing at once, because the gaps live in several places (the device firmware, each controller app, and the Thread network) and an update usually touches only one.
A controller app update is what adds support for new device categories and Matter versions; that’s the layer that turned IKEA’s button from “pairs but does nothing” toward “works as a trigger” on Google Home. Device firmware updates patch the device’s own Matter and Thread behavior, which is often where multi-admin sync bugs actually get resolved. Neither one fixes a missing Thread border router or a network-level snag, and Matter over Thread leans on IPv6, which reporting notes needs to be enabled on your network for that traffic to work at all. So the honest expectation: keep every controller app and every device’s firmware current, and understand that “the next update” might fix your symptom or might be aimed at someone else’s. The trajectory is upward. It is not finished.
Frequently asked questions
What is Matter multi-admin?
Matter multi-admin is the feature that lets one Matter device be controlled by several ecosystems at the same time, like Apple Home, Google Home, and Alexa together. You commission the device in one app, generate a sharing code, and add it to the others, with each platform controlling it independently.
Why does my Matter device work in Apple Home but not Google Home?
Most often the controller, not the device. Google Home may run an older Matter version or lack support for that device category, so the device pairs but loses buttons or modes. Sharing it across both apps can also trigger multi-admin instability that affects one platform more than the other.
Is it safe to add one Matter device to three ecosystems at once?
You can, but as of June 2026 it's the most common source of trouble. Owners and reporters describe shared devices dropping off the network or going unresponsive once they live in multiple controllers. If you don't truly need three, commissioning in one capable controller is more stable.
Do IKEA's 2026 Matter devices need a Thread border router?
Yes, for the Matter-over-Thread ones, which is most of the new sensors and bulbs. Without a border router on your network (an IKEA DIRIGERA, or many HomePods, Echos, and Nest devices), Thread devices can't reach your network at all, no matter which app you pair them in.
Will a firmware update fix my Matter sharing problem?
Sometimes. Controller app updates add device-category and version support; device firmware updates fix the device's own Matter and Thread bugs, including some multi-admin issues. Neither fixes a missing border router or a disabled-IPv6 network problem, so keep apps, firmware, and your network all current.
Bottom line
When a Matter device works on one platform but not another, look at the controllers before you blame the device. The cause is almost always a controller running an older Matter version, a controller that hasn’t added your device’s category yet, or multi-admin sharing introducing a bug at the seam between ecosystems. Commission in your most capable controller, share sparingly, keep everything updated, and confirm device-category support before you buy. For what Matter and Thread actually are and which devices need a border router, see Matter and Thread, Explained. For a device that used to work and suddenly won’t, run the general connection troubleshooting order.
This is a living guide. The IKEA-2026 rollout and platform Matter support are changing fast; we date our claims and revisit them as the ecosystems update.