Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.
Building a smart home ecosystem that won't lock you in comes down to one question: who owns the devices and the automations when you're ready to walk away? A no-subscription, local-control starter guide is the right place to begin with the device-level basics; this guide goes deeper and examines the platform architecture underneath.
The stakes got real in 2026. In June, Samsung announced a paid SmartThings API tier — a concrete example of a service dependency changing after builders had invested in it. The right response isn't to pick a brand and hope it behaves. The response is to design the system so that a vendor's future policy shift can't strand your house.
This guide compares Home Assistant, Apple Home, Amazon Alexa, Google Home, Samsung SmartThings, Hubitat Elevation, and Homey Pro on the axis that matters: lock-in. We break the decision into four ownership layers, clear up the Matter-versus-Thread confusion, and give you an exit test you can run before buying anything. We also cover the radios that matter — Matter, Thread, Zigbee, and Z-Wave — because the protocol layer is where your exit options are either built or lost.
This is for anyone choosing a hub today, including HomeKit users weighing Apple's polish against its account pressure, Alexa and Google users who want a safety net for local commands, and Home Assistant builders who want to avoid rebuilding their setup twice.
| Ecosystem | Lock-in posture | What leaves with you |
|---|---|---|
| Home Assistant | Very low at the device layer; dashboard and automation rebuild cost remains | Zigbee, Z-Wave, Matter, Thread devices via replacement radios |
| Apple Home / HomeKit | Account- and hardware-centric; strong local privacy | Matter/HomeKit devices, but not Apple-specific features |
| Amazon Alexa | Cloud-hybrid; routines live in the cloud | Matter/Zigbee devices, not Alexa routines |
| Google Home | Cloud-hybrid; local Matter path is real but limited | Matter/Thread devices, not voice AI or legacy cloud integrations |
| Samsung SmartThings | Medium; API policy is the risk | Zigbee/Matter devices depending on hub generation |
| Hubitat Elevation | Low device lock-in; rules are proprietary | Zigbee and Z-Wave hardware |
| Homey Pro | Low device lock-in; Flows are proprietary | Zigbee, Z-Wave, Matter devices |
What "Lock-In" Actually Means in a Smart Home
Lock-in isn't a binary between cloud and local. It's a question of exit cost: how many hours of re-pairing, how many automations rebuilt, how many features lost, and how much vendor permission is required to leave.
The mistake most buyers make is evaluating ecosystems by marketing features — voice quality, app polish, device count. The better yardstick is the exit test: unplug the WAN and ask which devices and automations keep working; then ask whether another controller could adopt those devices without a factory reset; then ask what you'd have to rebuild anyway.
A relevant detail from the 2026 commercial reality is worth stating plainly. Amazon's Alexa, Google Home, and Apple Home support Matter and Thread on compatible hardware, but that doesn't make them interchangeable. A Matter device paired to an Echo Hub can often be shared into Home Assistant or Apple Home through Matter multi-admin. The Alexa routine that turns on that device does not transfer. One layer improves; the other stays vendor-bound.
The rest of this article uses that separation: device portability, network migration, automation portability, and feature parity. Each layer moves independently, and different ecosystems fail at different layers.
The Four Layers of Smart Home Ownership
The cleanest way to size up a platform is to evaluate four layers separately. Skipping any one of them turns a local-control purchase into a future re-pairing marathon.
Layer 1 — Device portability. Can a motion sensor, plug, lock, or switch pair directly to another controller using Matter, Zigbee, Z-Wave, or Thread? Direct standard-protocol pairing is the strongest form of portability. A proprietary vendor cloud between the device and the hub is the weakest.
Layer 2 — Network portability. Can the controller's network credentials and device database migrate to a new coordinator, or will every device require physical factory reset and manual re-inclusion? Zigbee and Z-Wave migrations depend heavily on coordinator and software support. Re-pairing 30 sensors because the old hub's network couldn't transfer is not a protocol failure — it's a migration-cost failure.
Layer 3 — Automation portability. Can your rules, scenes, scripts, and dashboards export in a reusable format? In most commercial ecosystems, the answer is effectively no. Home Assistant dashboards don't import into Homey; Hubitat rules don't import into Home Assistant; Alexa routines don't leave Amazon. This rebuild cost applies to every platform, including fully local ones.
Layer 4 — Feature parity. Does the generic Matter or Zigbee representation preserve the advanced features you actually use? Home Assistant itself documents cases where a native integration exposes more capability than the same device through Matter. The Matter logo is not a promise that every vendor-specific scene, notification, or tunable parameter travels with the device.
The practical conclusion from this framework: Matter improves Layer 1 dramatically but does not solve Layers 2 through 4. A portable device attached to a non-portable automation database is still a lock-in problem.
The Ecosystems, Compared on Lock-In
Home Assistant — Ownership-First
Home Assistant is the strongest ownership model because the automation engine, device data, and local protocols can all remain inside the home. The platform is open source, keeps core smart-home data locally, and supports direct Zigbee, Z-Wave, Matter, Thread, and ESPHome operation without an internet connection through local integrations. No Home Assistant cloud account is required for core operation.
The trade-off is ownership itself: updates, integration changes, and network configuration demand more operator attention than an appliance-style hub. Matter and Thread troubleshooting in 2026 consistently points to IPv6 reachability, multiple Thread meshes, and border-router topology rather than the Matter application layer alone.
Home Assistant is a Matter controller, not a Matter bridge for arbitrary entities — so the platform doesn't officially expose every existing entity as a Matter device. It also documented Matter 1.5.1 in the June 2026 Matter Server upgrade, with Matter 1.6 still pending implementation. These details matter when you're planning cross-ecosystem sharing.
For hardware, Home Assistant runs on anything from a Raspberry Pi to a dedicated appliance. If you want a prebuilt entry point, the Home Assistant Green is the official dedicated box.
Home Assistant Green
- Specs: Rockchip RK3566, quad-core Arm Cortex-A55 at 1.8 GHz, 4 GB LPDDR4X RAM, 32 GB eMMC storage, Gigabit Ethernet, 2× USB 2.0, 12 V DC power, roughly 1.7 W idle and 3 W under load, 112 × 112 × 32 mm, 340 g.
- Positioning: mid-range, purpose-built Home Assistant OS appliance.
- Crucial spec: no integrated Zigbee, Thread, or Z-Wave radio — you add external radios yourself.
- Verdict: the right prebuilt path into HA without maintaining Pi storage; the missing radios are a feature, because you can upgrade your coordinators independently of the host.
- Perfect for: a Home Assistant beginner who wants a dedicated appliance, not a Raspberry Pi infrastructure project.
- Check Price on Amazon
For the radio layer, two official adapters matter. The Home Assistant Connect ZBT-2 is the second-generation Zigbee/Thread radio built on a Silicon Labs MG24 SoC with an ESP32-S3 USB bridge. It runs Zigbee 3.0 or Thread — one protocol at a time — at a 460800 baud interface. That one-radio, one-protocol design is deliberate: simultaneous Zigbee/Thread operation produced stability problems, so the official adapter doesn't attempt it. Budget for a separate radio if you run both.
The Home Assistant Connect ZWA-2 is the official Z-Wave 800-series adapter, built on a Silicon Labs ZG23 with an ESP32-S3 bridge. It runs conventional Z-Wave mesh and Z-Wave Long Range simultaneously, across 860–930 MHz with a large omnidirectional antenna. Direct USB is the recommended architecture because the adapter-to-Z-Wave JS path is latency-sensitive.
The Home Assistant stack pairs naturally with a replaceable frontend: Apple Home, Alexa, or Google can all sit on top of HA, which keeps the voice assistant swappable rather than foundational. The Home Assistant vs SmartThings comparison covers that architecture in more depth.
Apple Home / HomeKit — Privacy-First, Account-Heavy
Apple Home is built around authenticated local accessory communication, and many automations execute through a local HomePod or Apple TV hub. That local, privacy-first design is the platform's genuine strength. Matter accessories can also be shared into other certified Matter ecosystems through multi-admin, and iOS 18 or later can add and control Matter accessories without a home hub. Apple stores Matter pairing keys in end-to-end-encrypted iCloud Keychain.
The lock-in is on the other side of the ledger: an Apple Account, iCloud, Apple hardware, and the Home app are central to the full experience. Legacy non-Matter HomeKit accessories do not gain multi-admin just because Apple Home also supports Matter. HomeKit Secure Video and other Apple-specific capabilities are not generically portable. Apple remains the gatekeeper for the ecosystem, even though basic local control carries no mandatory subscription.
The HomePod mini is the most practical entry point: it acts as a Matter controller, a home hub, and a Thread Border Router while doubling as a Siri frontend. In a Home Assistant-centered architecture, it can serve as a Thread Border Router even when HA is the Matter controller — owning an Apple border router does not force every Matter device to use Apple's fabric as its only controller.
The strongest privacy-first pattern is to make Home Assistant the backend and Apple Home the family-friendly frontend. That keeps Siri and the Home UI replaceable without making every Zigbee or Z-Wave device depend on Apple's native compatibility catalog. See the Home Assistant HomeKit Bridge setup guide for the local bridge path.
Amazon Alexa — Cloud-Hybrid
Alexa's architecture is hybrid in a precise sense. Traditional smart-home skills commonly connect Alexa's cloud to a manufacturer's cloud — the weakest portability pattern. But supported Echo and eero hardware can also connect devices locally through Matter over Wi-Fi, Matter over Thread, and Zigbee. Amazon itself notes that Zigbee and BLE local capabilities may be more limited than richer Matter or cloud add-on implementations.
The takeaway isn't that Alexa is all cloud. It's that each path must be evaluated separately. A Matter device on a compatible Echo has real local control; an Alexa routine and a manufacturer skill remain cloud dependencies. Z-Wave is not natively coordinated by current Alexa hub hardware at all.
The Echo Hub is the representative device: a wall-and-tabletop Alexa controller with Matter, Thread, and Zigbee local paths on compatible device types, but no Z-Wave coordination. It's better evaluated as an Alexa control surface with useful local radios than as an ownership-first brain.
For anti-lock-in use, the right role for Alexa is the voice-and-UI layer over local devices, not the only automation database. That's covered in the Home Assistant Alexa and Google integration guide.
Google Home — Cloud-Hybrid
Google Home documents local Matter command execution at home over Wi-Fi or Thread — at-home commands don't necessarily traverse vendor clouds. Remote commands still use Google's cloud for authentication. The Google Home Speaker (2026) contains a Thread 1.3 Border Router and acts as a Matter hub for Google Home, with a 58 mm full-range driver, three far-field microphones, Wi-Fi 6, and Bluetooth 5.4.
Two practical cautions apply. First, Google explicitly warns that Matter setup and control can fail if IPv6 is disabled on the home network — a reminder that Matter's reliability bottleneck is often network topology, not the application layer. Second, there is no general native Zigbee coordinator on the current Google Home speaker path; Zigbee devices require bridges. Gemini, remote access, and many non-Matter "Works with Google Home" integrations remain cloud-dependent.
The anti-lock-in pattern is the same as with Alexa: use Google as a replaceable voice frontend over devices owned by a local controller. The smart home hub compatibility guide sketches that layering for Apple, Google, and Alexa.
Samsung SmartThings — Local Edge, API Risk
SmartThings sits in the middle: Edge execution on compatible hubs can run Zigbee devices locally, and Matter multi-admin workflows are supported. But the cloud account, the app, routines, and API-based integrations remain platform-coupled.
The defining 2026 event was the API. Samsung announced a paid SmartThings API plan for non-commercial individual developers in June 2026, while stating that ordinary SmartThings App users don't pay merely to use the app. Free API access continues through September 2026, with phase-out beginning in October. That's a textbook example of platform policy changing after users built integrations around it.
Hub generation also matters. The current Aeotec Smart Home Hub 2 / V4 supports Matter, Zigbee, Thread, Ethernet, and Wi-Fi — but its spec sheet explicitly says "No Z-Wave." That's a critical generational change from the previous SmartThings hardware.
The Aeotec Smart Home Hub V3 retains Zigbee, Z-Wave Plus, and Matter through platform updates, making it arguably more useful for an existing Z-Wave household despite being the older generation.
The caution for SmartThings buyers is the same as for the commercial hubs: a standards-compatible device may be portable, but an automation-and-API dependency can still be monetized later. The Home Assistant vs SmartThings comparison covers the direct migration path.
Hubitat Elevation — Local Appliance
Hubitat is a dedicated local automation appliance: automations execute on the hub and continue during internet disruptions. The standard Hubitat Elevation C-8 Pro ships with Matter 1.5 support, Zigbee 3.0, Z-Wave 800 Series with Z-Wave Long Range, Bluetooth, external Zigbee and Z-Wave antennas, and a claim of compatibility with 1,000+ devices across 100+ brands.
The major 2026 nuance is Thread. The C-8 Pro Thread Special Edition, launched August 20, 2026, adds an integrated Thread radio — but that radio replaces the traditional Zigbee radio rather than sitting alongside it. A buyer choosing the special edition for future-proofing can actually lose direct Zigbee capability versus the standard model. This is a case study in reading the radios, not the logo.
Hubitat's lock-in profile is favorable at the device layer: Zigbee and Z-Wave hardware can typically be re-paired to another controller. The platform-specific layer is the rules, apps, drivers, and backups, which remain Hubitat-specific. Local control does not equal maintenance-free: the 2026 platform releases included beta Matter and a beta Z-Wave firmware path that community feedback pushed the vendor to pull and fix. Backups and cautious firmware updates still matter when no cloud is involved.
Homey Pro — Local-First Premium
Homey Pro is the most polished "many local radios in one box" option. The 2026 model pairs a 1.5 GHz quad-core Arm processor with 4 GB RAM and 8 GB eMMC, and bundles Matter 1.5, a Thread Border Router, Zigbee 3.0, Z-Wave 700 Series, a 433 MHz radio, and infrared in a single appliance. Homey states that Homey Pro processes automation on-premises and remains operational when internet connectivity is lost. Local backups and local API keys are supported, and Homey has formally extended software support through at least June 2031.
The lock-in trade-off is the application layer. Zigbee, Z-Wave, and Matter devices are broadly portable, but Homey Flows, Homey Apps, and backups are Homey-specific — migrating to another platform generally means rebuilding automations. Community migration reports from Homey Pro 2023 to 2026 underscore the point: even when a backup restores, dozens of Zigbee devices can become unstable and require re-pairing, while Z-Wave survives intact. One vendor-acknowledged caution also applies: experimental firmware can be unstable and may require a factory reset to unwind, so a backup before opting in is essential.
Homey's one feature that official Home Assistant doesn't currently provide natively is the Matter Bridge app, which can expose supported Homey devices to other Matter ecosystems. For a certain kind of buyer — someone who wants local radios and a polished UI without running a general-purpose server — that's a meaningful differentiator.
Protocol Ownership: Matter, Thread, Zigbee, and Z-Wave
Matter is not a radio. Matter runs at the application layer over IP transports, typically Wi-Fi, Ethernet, or Thread. It standardizes device control and multi-admin — the ability for multiple certified ecosystems to control the same compatible device. Matter 1.6 released on June 17, 2026, focusing on commissioning, cross-ecosystem coordination, and richer context-driven control. But version adoption is controller-specific: publication of Matter 1.6 does not mean every ecosystem already implements 1.6, and major controllers were still documenting 1.5 or 1.5.1 through mid-2026. Home Assistant explicitly warns that a native integration can expose more capability than the same device through Matter. The Matter explained guide walks through what the standard can and cannot do.
Thread is a transport. Thread is a low-power IPv6 mesh network. A Thread logo alone does not imply Matter; Matter-over-Thread combines Matter at the application layer with Thread as the network. Thread devices reach the ordinary IP LAN through a Thread Border Router. More border routers can improve resilience only when they participate in the same usable Thread network — duplicate Thread datasets and poor LAN IPv6 configuration make a theoretically redundant deployment less reliable. If you're setting up Matter in Home Assistant, the Home Assistant Matter integration guide covers the commissioning specifics, including why retaining Matter QR and setup codes matters.
Zigbee is not dead. Zigbee 3.0 remains the practical compatibility baseline for current Home Assistant, Homey, Hubitat, and SmartThings hardware. The Connectivity Standards Alliance released Zigbee 4.0 on November 18, 2025, adding features aimed at security, interoperability, range, and optional Sub-GHz operation. Matter does not directly speak Zigbee; a Zigbee device requires either a direct Zigbee coordinator or a bridge. Zigbee remains favored for inexpensive sensors and switches because it works entirely locally across HA, Hubitat, and Homey, with mature device variety. The Zigbee vs Z-Wave vs Matter comparison covers the protocol-level trade-offs in depth.
Z-Wave is a separate insurance policy. Z-Wave runs on sub-GHz frequencies, which reduces competition with 2.4 GHz Wi-Fi, Zigbee, and Thread. Conventional Z-Wave is a mesh; Z-Wave Long Range uses a star-style topology and can run alongside conventional Z-Wave with compatible 800-series controllers like the HA Connect ZWA-2. The Z-Wave Alliance updated the certification program for the 2026A specification package on June 30, 2026 — the protocol is actively maintained. Home Assistant's own Z-Wave documentation warns that some 800-series firmware and SDK combinations have stability problems, so firmware quality matters when building.
The Exit Test — 8 Questions to Run Before You Buy
Before committing to any ecosystem, run this test against your intended hardware, not just the marketing page. The answers reveal where your future migration pain will live.
-
Disconnect the WAN. Do switches, sensors, and automations still work? If a cloud account is required for core commands, the device is a tenant, not an owner.
-
Locate the automation logic. Does it run on a local box you control, or in a vendor's cloud? Home Assistant and Hubitat execute locally; Alexa and Google hybrid paths partially do; many proprietary skills do not.
-
Check whether the device pairs directly or hides behind a vendor cloud. Direct Matter, Zigbee, Z-Wave, or Thread pairing is a portable asset. A vendor-specific cloud-to-cloud skill is not.
-
For Matter devices, verify the actual supported clusters and functions. "Matter" on the box is not a promise that every scene, notification, or advanced setting travels with the device.
-
Ask whether a vendor app or account is required after commissioning. If the device can't be re-paired without the original vendor's app, that's a hidden exit dependency.
-
Verify that another controller can adopt or share the device. Matter multi-admin helps here; a non-Matter HomeKit accessory does not gain multi-admin simply because Apple supports Matter.
-
Check whether network credentials and backups can migrate. Zigbee and Z-Wave migration depends on coordinator and software support. Assume a hub change may require re-pairing unless the vendor documents a migration path.
-
Keep the voice assistant replaceable. Treat Alexa, Siri, and Gemini as presentation layers over a local backend, not as the foundation.
The principle underneath all eight: save the pairing codes, prefer protocols where the radio can be upgraded separately from the automation server, and assume that anything proprietary — routines, scripts, drivers, dashboards — is a future rebuild.
Recommended Setups by Profile
| Profile | Recommended stack | Why |
|---|---|---|
| Maximum autonomy | Home Assistant Green + ZBT-2 + ZWA-2, local frontend | Ownership-first; every radio upgradeable; frontend replaceable |
| Apple-first with an exit | Home Assistant backend, Apple Home frontend, HomePod mini as TBR | Local control plus Siri convenience, without Apple-only device dependence |
| Local appliance, no server admin | Hubitat C-8 Pro standard | Zigbee + Z-Wave locally, straightforward install, real device portability |
| Polished local radios | Homey Pro | Broad local radios in one box, local processing, Matter Bridge exposure |
| SmartThings invested | Aeotec V3 if Z-Wave matters | Retains Z-Wave; don't assume V4 is strictly an upgrade |
| Voice-first, minimal upkeep | Echo Hub or Google Home Speaker over local Matter devices | Convenience layer on top of portable Matter hardware |
For most users who want local control without overcommitting to a single vendor's automation database, the two endpoints are clear: Home Assistant when you're willing to operate the system, and Hubitat when you want a local appliance with less server overhead. See the best smart home hubs comparison for a broader look at hub choices across categories.
Frequently Asked Questions
Q: Does Matter eliminate smart home lock-in?
No. Matter improves device-level portability dramatically — a compatible device can be shared or re-paired across certified ecosystems through multi-admin. It does not port your automations, vendor-specific features, firmware dependencies, or cloud-only notifications. Those layers remain platform-specific.
Q: What's the difference between Matter and Thread?
Thread is a low-power IPv6 mesh network transport. Matter is the application layer that standardizes device control and runs over Wi-Fi, Ethernet, or Thread. A Thread logo alone does not imply Matter support, and Matter-over-Thread requires a working Thread Border Router.
Q: Will my devices keep working if the internet goes down?
It depends entirely on architecture. Matter, Zigbee, Z-Wave, and Thread devices paired directly to a local Home Assistant, Hubitat, or Homey controller keep working. Devices dependent on a vendor cloud skill go down with the connection. Check where the device actually pairs.
Q: Is Zigbee obsolete because Matter exists?
No. Zigbee 4.0 released in November 2025, and Zigbee remains the baseline protocol on current Home Assistant, Homey, Hubitat, and SmartThings hardware. Matter and Zigbee operate at different layers; a Zigbee device still requires a direct coordinator or bridge, not Matter adoption.
Q: Can I use Home Assistant with Apple Home?
Yes. You can bring HomeKit-compatible accessories into Home Assistant with HomeKit Device, expose supported HA entities back to Apple Home through HomeKit Bridge, or use Matter multi-admin when the device itself supports it. The HomeKit Bridge setup guide covers the local path.
Q: What's the biggest hidden cost of switching ecosystems?
Re-pairing labor. Community reports show that dozens of Zigbee devices can turn a hub move into hours of re-pairing, recalibration, and troubleshooting, even when both systems nominally "support Zigbee." Automation rebuild is the second cost: rules rarely export between platforms.
Q: Which ecosystem has the least lock-in?
Home Assistant offers the least device-level lock-in because its data, automations, and local protocols can stay inside the home, and its radios are separate from the host. The caveat is that dashboards and automations still require rebuilding if you leave Home Assistant itself. Hubitat and Homey follow close behind on the device layer with more proprietary automation layers.
Conclusion
The smart home ecosystem decision isn't really a brand choice. It's an ownership decision — who controls the device, who owns the automation logic, and what happens to both when the vendor changes its mind. Home Assistant offers the strongest autonomy at the cost of operator effort. Hubitat and Homey deliver local control in appliance form with proprietary rules attached. Apple, Alexa, and Google are best used as replaceable frontends over a local backend, not as the foundation.
If you take one idea from this guide, take the exit test. Disconnect the WAN, check where automations execute, verify whether another controller can adopt the devices, and treat anything that can't export as a future rebuild. Buy the radios and the backend separately when you can, and keep the voice assistant swappable.
For the next layer of decision-making, start with the best smart home hubs for hardware selection, the Matter explained guide for the standard's real boundaries, and the Home Assistant beginner's guide if you're ready to own the backend. If you want a local-control foundation without building it all at once, the no-subscription starter guide is the practical starting point.
