Building Smart Home Automations That Work Across Ecosystems (Matter/Google/Alexa/Apple) UK

Most people end up with a mixed smart home almost by accident - an Alexa speaker from a Christmas years ago, an iPhone, a couple of Hue bulbs, maybe a Google Nest doorbell from a previous flat. Our Matter explainer covers why this is finally becoming less painful - here’s practically how to build automations that actually work across Google, Alexa and Apple at once, rather than picking one ecosystem and hoping.

The Core Idea: One Source of Truth

The trick to cross-ecosystem automation is picking one “primary” controller that all your devices are added to first via Matter, then exposing that same set of devices to your other assistants as needed. Matter devices can typically be shared across multiple ecosystems simultaneously, so a Matter bulb added to Google Home can also be controlled by Alexa and Apple Home without buying the device twice.

Practical Setup

Step	What to Do
1. Pick a primary hub	Whichever ecosystem matches your main phone (Apple Home for iPhone, Google Home for Android)
2. Add all Matter devices there first	Generates a shareable Matter setup code per device
3. Share devices to secondary ecosystems	Scan the same setup code in Alexa/Google/Apple Home as needed
4. Build routines per-ecosystem	Voice routines still need to be set up separately in each assistant’s app

For the specifics of setting up voice routines once devices are shared, see our guides on Alexa Routines and Google Home Routines.

A Worked Example: A Mixed-Brand Evening Routine

Say your household has a Hue bulb, a Tado thermostat, and a Yale smart lock - three different brands, none of which natively talk to each other. Adding all three as Matter devices to a single primary hub (an iPhone household would use Apple Home) means one “Good Evening” scene can dim the Hue bulb, nudge the Tado thermostat down, and confirm the Yale lock is engaged, all from one routine. Sharing that same Matter setup to Alexa afterwards means “Alexa, good evening” triggers the identical scene, without setting anything up twice in Alexa’s own app - Alexa simply sees the devices as already-configured Matter accessories.

The Fabric Limit Nobody Mentions Upfront

There’s a genuine technical ceiling worth knowing about before sharing a device across every ecosystem you own. Matter devices join each ecosystem as a separate “fabric” - effectively a controller relationship - and most certified devices support a maximum of five concurrent fabrics, though some budget devices cap lower, at three. That sounds generous until you count: Apple Home, Google Home, Amazon Alexa, SmartThings and Home Assistant is already five, leaving no headroom for a secondary phone’s Apple Home, a holiday-home hub, or a guest’s ecosystem. The practical trap is that removing an app from your phone or simply not using an ecosystem anymore doesn’t free up its fabric slot - the device still thinks it’s joined to that controller until it’s explicitly removed from within that ecosystem’s own app. If a device refuses to pair to a new ecosystem with no obvious error, checking whether it’s quietly still attached to an old, unused fabric (and removing it there first) is the fix more often than people expect.

Where This Still Breaks Down

• Complex conditional logic - “if it’s raining AND after 6pm AND someone’s home” style rules generally still need Home Assistant or a single ecosystem’s more advanced automation builder
• Camera and video devices - video feeds are far less consistently shareable across ecosystems than switches, plugs and sensors
• Brand-specific features - manufacturer-specific extras (e.g. a Hue bulb’s exact colour presets) sometimes only fully work inside that brand’s own app

When to Stop Fighting It and Use Home Assistant

If you find yourself constantly hitting the limits above, that’s usually the signal to move to Home Assistant as your actual automation engine, while still keeping Alexa, Google or Apple Home as the voice front-end. Home Assistant sits underneath all three simultaneously and handles the genuinely complex logic none of them are individually built for.

What Happens If You Later Add Home Assistant

If you eventually move to Home Assistant as described above, your existing Matter setup isn’t wasted - Home Assistant can also act as a Matter controller, meaning devices already shared across Apple Home, Google Home and Alexa can be added to Home Assistant too, without any of the other three losing access. This is one of Matter’s genuine practical advantages over the pre-Matter era: adding a new controller to the mix is additive, not a migration that forces you to choose one ecosystem and abandon the others.

Troubleshooting: A Device Goes Offline in One Ecosystem Only

• Works in the primary hub but shows unreachable in a secondary ecosystem - this is almost always a local network issue specific to that ecosystem’s hub hardware (e.g. a HomePod mini acting as the Apple Home hub losing Wi-Fi), not the device itself; check the secondary ecosystem’s own hub is online before assuming the shared device has a problem
• A device stops responding in every ecosystem after a firmware update - some manufacturers push firmware updates that briefly drop and re-establish Matter fabric connections; give it 10-15 minutes after an update before re-pairing, since most resolve themselves once the device finishes reconnecting to each fabric in turn
• Sharing a device to a new ecosystem fails with a generic error - regenerate the Matter setup code from the primary hub rather than reusing an old QR code or number, since some ecosystems invalidate a sharing code after a single use or a set expiry window

Frequently Asked Questions

Do I have to re-buy devices to make them work with a different assistant?

No, as long as the device is Matter-certified - the whole point of Matter is that one physical device can be shared across Apple Home, Google Home, Alexa and SmartThings simultaneously without duplicate hardware.

What if one of my devices isn’t Matter-certified?

Older or non-Matter devices generally still work within their original manufacturer app and can often still be linked to a single other ecosystem via a direct skill/integration (e.g. an Alexa skill), but they won’t get the automatic cross-ecosystem sharing that Matter devices do - this is where the practical limits of a fully mixed setup show up most.

Do voice routines need to be rebuilt in every ecosystem, or just once?

Voice routines (as opposed to the underlying device sharing) currently need setting up separately in each assistant’s own app - Matter standardises device access across ecosystems, but routine/scene building itself is still handled individually by Apple, Google and Amazon.