LimeWorksWith — the Apple Home compatibility deskDoes X work with Apple Home? · verified

Guides Apple Home, Alexa and Google together: does it actually work?

Apple Home, Alexa and Google — at the same time

Yes, it works — if the device speaks Matter. A Matter accessory can be paired to several ecosystems at once (the standard calls it multi-admin), so the same lamp can answer Siri, Alexa and Google. What does not travel with it: scenes, automations, room names and the Apple-only features.

The short answer

What “multi-admin” actually means

Matter calls each ecosystem's controller an admin, and the set of devices an admin manages a fabric. Multi-admin lets one accessory belong to several fabrics: every ecosystem holds its own credentials for the same device.

The shared part is the device state. Turn the lamp off in Apple Home and Alexa sees it off, because the change is written to the accessory, not to one app's database. The separate part is everything above that: names, rooms, scenes, routines, history and ecosystem-specific features.

Shared across ecosystemsNot shared
On/off, brightness, colour, lock state, sensor readingsDevice and room names
The device itself (one pairing, several admins)Scenes and automations
Basic capability set exposed by MatterApple Home Key, HomeKit Secure Video, Adaptive Lighting
Firmware stateWho performs firmware updates (usually the maker's app)

What each ecosystem needs

EcosystemMatter controllerNotes
Apple HomeHomePod mini, HomePod (2nd gen) or Apple TV 4K (2nd/3rd gen)The iPhone can commission a device, but remote access and away-automations need the hub
AlexaEcho (4th gen) or newer, a recent Echo Show, or a recent eeroAmazon maintains a Matter controller list — check your exact model before buying
Google HomeNest Hub (2nd gen), Nest Hub Max, a Google TV device or Nest Wifi ProOlder Nest Hubs and Nest Minis are not Matter controllers

Without a controller in an ecosystem you can still add the device in the maker's app, but not into that ecosystem's voice and automation layer.

Same device, three apps — the order that works

  1. Pair the device in the ecosystem you use most, normally Apple Home, by scanning the Matter code on the device.
  2. Open the second app and choose “add Matter device”. You usually cannot reuse the original code: the first ecosystem has to open a pairing window and issue a new one. In Apple Home that is the accessory's settings → Turn on Pairing Mode.
  3. Repeat for the third ecosystem while the window is still open.
  4. Rename the device in every app. Matter does not sync names, so “Hallway lamp” in one app is “Matter Light 3” in the next.

If an app only offers “scan the code from the box”, it is expecting a fresh device. Look for “pair with another app”, “more options” or the pairing-mode entry instead.

Where it still breaks

Thread is the weak spot

Thread accessories live on a Thread mesh, and each ecosystem builds its own. Thread 1.4 added credential sharing so border routers can join forces, but real-world support depends on hub model and firmware. A Thread sensor added to a second ecosystem can appear in the app and then fail to respond, because that ecosystem has no route into the mesh it sits on.

The practical split: devices you genuinely want in two or three ecosystems should be Matter over Wi-Fi. Battery devices you keep in one ecosystem are still better on Thread — see Thread vs Wi-Fi.

Voice assistants do not merge

Siri, Alexa and Google Assistant stay in their own lanes. Each can control the device, none can control the others. A “good night” scene in Apple Home is invisible to Alexa unless you rebuild it as a routine.

Two automation engines, one lamp

Both ecosystems will automate the same bulb and they will not coordinate. A Siri scene that dims to 10% and an Alexa routine that turns the lamp off will fight each other every evening. Pick one ecosystem to own scheduling and keep the others for voice control.

Matter is the floor, not the ceiling

A Matter device exposes a defined feature set. Vendor extras — zone settings on a presence sensor, energy tariffs on a plug, doorbell chimes — often live only in the maker's app. That is not a multi-admin problem, but it explains why a device can look “thinner” in a second app.

When mixing is worth it

When it is not worth it

If everyone in the house is on iPhone and you own no legacy gear, a second ecosystem buys you a second app, a second set of names and a second place for automations to go wrong. Spend that money on sensors instead: Apple Home sensor automations.

Checklist before you buy

The compatibility matrix lists the protocol of every device we have checked — filter for Matter and you are looking at exactly the pool that can do this. Not sure whether your device is Matter or HomeKit? Read 'Works with Apple Home' vs Matter.

FAQ

Can one device work with Apple Home and Alexa at the same time?

Yes, if it speaks Matter. Matter supports multi-admin, so the same accessory can be paired to Apple Home, Alexa and Google in parallel. A HomeKit-only device cannot: it only works with Apple Home.

Do I need a hub for each ecosystem?

You need a Matter controller in each ecosystem — an Apple home hub (HomePod or Apple TV) for Apple Home remote access, an Echo or eero for Alexa, and a Nest Hub, Google TV device or Nest Wifi Pro for Google. Without one you can still control the device in that ecosystem's app while at home, but not remotely or in automations.

Do automations and scenes sync between Apple Home and Alexa?

No. Only the device state is shared. Names, rooms, scenes, routines and automations are per ecosystem, so you rebuild them in each app.

Why does my Thread sensor show up in Alexa but not respond?

Each ecosystem builds its own Thread network. Thread 1.4 introduced credential sharing, but support varies by hub and firmware, so a Thread device added to a second ecosystem can appear without a working route. Matter-over-Wi-Fi devices avoid the problem entirely.

Can I add a HomeKit-only device to Alexa or Google?

No. HomeKit-only accessories have no Matter interface, so Alexa and Google cannot commission them. The only exception is when the manufacturer exposes them through its own hub or cloud service, which is a separate integration, not Matter.