Setup Ecosystems
Sharing SmartThings devices with Google Home, Alexa or Apple Home
SmartThings hands a Matter device to another platform happily. It will not republish the Zigbee and Z-Wave gear already on its hub as Matter devices, and that is the half people get wrong.
SmartThings is unusually generous in one direction and closed in the other, and the gap between the two is where households come unstuck. It will hand a Matter device to another platform happily. It will not republish the Zigbee and Z-Wave devices sitting on its own hub, which is exactly the thing most people assume it does.
A Matter controller, not a Matter bridge
A Matter controller commissions Matter devices and controls them. A Matter bridge is a different job: it takes devices speaking some other radio and presents them outward to a Matter controller as though they were Matter devices themselves. A Philips Hue Bridge is the familiar example of the second kind, and it is the reason people expect a SmartThings hub to behave the same way.
SmartThings does the first job and not the second. The consensus across the SmartThings community is that there is no bridge function and no announced plan for one, and we have found nothing from Samsung that contradicts it. The practical effect is blunt: a household with thirty Zigbee sensors and a dozen Z-Wave switches on a SmartThings hub cannot republish any of them to another ecosystem as Matter devices.
What each platform actually gets
Two of the three big platforms have a second route that does not involve Matter at all. Google Home and Alexa each link to SmartThings at the account level, a cloud-to-cloud connection separate from anything Matter does. Apple Home has no such route: Matter or a third-party bridge, and nothing else. That is why the missing bridge bites hardest on the Apple side.
Account linking is a different mechanism with different rules, and the missing Matter bridge does not govern it. Which of your SmartThings devices actually turn up in Google Home or Alexa once the accounts are linked is not something either company publishes a definitive list for, and it has moved over time. So link the accounts and look. The device list in the second app is the only answer that is true for your house today, and it takes a minute to check before you build automations on top of it.
| Platform | How it connects | What you give up |
|---|---|---|
| Google Home | Account linking, plus Matter multi-admin for Matter devices | SmartThings-specific automations, modes and device attributes do not map cleanly |
| Amazon Alexa | Account linking, plus Matter multi-admin for Matter devices | The same as Google Home: SmartThings-only concepts have nowhere to land |
| Apple Home | Matter multi-admin, or a third-party bridge. No native HomeKit support | Anything that is not a Matter device, unless you run a bridge yourself |
| Philips Hue | Works in both directions | Pairing Hue bulbs straight to SmartThings, rather than keeping the Hue Bridge, gives up the Hue-specific features |
Sharing a Matter device out of SmartThings
This is the easy half. Reviewers credit SmartThings as the first platform to support Matter multi-admin, the feature that lets one physical device belong to several ecosystems at once, each controlling it from its own app.
- Check the device is genuinely a Matter device
Only Matter devices share this way. A Zigbee or Z-Wave device on your SmartThings hub has no path out by this route, however similar it looks in the app.
- Open the device in the SmartThings app and choose to share it
The exact wording and its position move between app versions, so look for the option to share the device with another service or ecosystem rather than following a fixed menu path.
- Take the pairing code SmartThings gives you
Sharing works by handing a pairing code from SmartThings to the second platform. That code is what the other app needs, so keep it to hand for the next step.
- Add a Matter device in the second platform's app and enter the code
In Google Home, Alexa or Apple Home, start the normal add-a-Matter-device flow and enter the code when it asks for one.
- Give it the same name in both places
Each ecosystem tends to keep its own name, room and automations for the device. Matching the names now saves the household arguing about it later.
Two things do not travel with the device. Automations stay where they were written, because each platform holds its own separate relationship with it, so do not expect a SmartThings Routine to fire an Alexa routine through a shared plug. And manufacturer-specific behaviour, the brand scenes and proprietary effects and richer configuration screens, generally does not survive the trip to a second platform, which is the same trade Matter makes everywhere else.
Running SmartThings alongside another ecosystem
This gets talked about as though it were a compromise. It is not. SmartThings as the device backend with Google Home or Alexa as the voice layer is a common and sensible arrangement, and we recommend it over forcing everything into one app. SmartThings handles the devices and the radios; the voice assistant you already own does the talking.
The cost is complexity rather than capability. You are maintaining an account link, the same device turns up in two apps with two sets of state, and there are more points where something can break. When a cloud path changes at either end, troubleshooting starts with working out which of the two systems moved.
The household this does not solve is the Apple-first one. There is no native HomeKit support and no bridge to stand in for it, so an Apple Home household running SmartThings is limited to Matter devices shared across, or to a third-party bridge they run and maintain themselves. If you are coming at this from the Apple side instead, we have written up sharing an accessory out of Apple Home separately.
For everyone else the shape to aim at is the one above: SmartThings holds the devices and the radios, and the assistant you already talk to holds the voice. Share the Matter devices across, link the accounts, then check what actually turned up before you build automations on top of it.
Frequently asked questions
Will SmartThings work with Google Home?
Yes. Google Home connects to SmartThings by linking the two accounts, a cloud route that does not involve Matter, and Matter devices can additionally be shared directly with a pairing code. Which of your other devices cross the account link is worth checking in the Google Home app rather than assumed. What does not carry across is the SmartThings automations, modes and device attributes, which have no clean equivalent on the Google side.
Do my Zigbee and Z-Wave SmartThings devices show up in Google Home?
Linking your SmartThings and Google Home accounts is a separate path from Matter, so the missing Matter bridge does not apply to it. We will not claim a device list, because neither company publishes one and it has changed over time. Link the two accounts and read the device list in Google Home. That is the only answer that is current and true for your setup.
Can I share my SmartThings Zigbee or Z-Wave devices with Apple Home?
Not from SmartThings itself. SmartThings is a Matter controller, and on the available evidence not a Matter bridge, so it does not republish the Zigbee and Z-Wave devices on its hub as Matter devices. Apple Home has no account-linking path either, so the only routes are buying Matter devices or running a third-party bridge yourself.
Does SmartThings work with Apple Home?
Only through Matter or a third-party bridge. There is no native HomeKit support, and the workarounds people describe are all bridge-based.
How many ecosystems can one Matter device join?
No figure is published, so we will not quote one. The sensible approach is to add the platforms your household actually uses rather than every platform available.
Is running SmartThings and Google Home together a bad idea?
No. SmartThings as the device backend with Google Home or Alexa as the voice layer is a common and sensible setup. The cost is complexity: you maintain an account link, the same device exists in two apps with two sets of state, and there are more places for something to break.
Still need a hand?
We answer most messages within one business day. If your question is about an existing order, have your order number ready. It speeds things up.
Contact us