Short Answer: One Brain, Several Control Surfaces

The cleanest mixed smart home has one automation brain. For a Home Assistant house, that brain should usually be Home Assistant. That is where timed rules, presence logic, sensor conditions, safety guardrails, and multi-brand scenes belong. Apple Home, Alexa, Google Home, and SmartThings can still be useful, but they should mostly be control surfaces: apps, voice assistants, family dashboards, and simple scenes that send a command to the same underlying devices.

Local control means the automation logic runs on hardware in your home instead of waiting for a vendor server. Home Assistant is built around that local-first idea, but the actual result depends on the devices you choose. A local Zigbee motion sensor turning on a local light can keep working during an internet outage. A cloud-only Wi-Fi bulb or an Alexa routine may not.

The practical rule is simple: use Home Assistant for the rules that would annoy, confuse, or worry you if they failed. Use Apple Home, Alexa, Google Home, and SmartThings for voice commands, simple family scenes, and ecosystem-specific features. When Matter or HomeKit sharing is involved, decide which platform owns the rule before you add the same device everywhere.

Tara's rule: a device can appear in several apps, but the automation should have one owner. Shared control is useful. Shared responsibility is where homes get messy.

Why This Question Keeps Coming Up

The demand signal is coming from real mixed homes. Reddit r/homeassistant threads ask about duplicated Alexa devices, Matter Hub strategies, and whether Apple Home should just be the front end while Home Assistant runs the logic. A recent Alexa helper thread shows the fragility of building Home Assistant workflows around how another platform classifies a helper this month. Home Assistant Community threads ask whether Alexa or Google can trigger automations locally, and migration threads keep landing on the same advice: move the serious routines into Home Assistant, then expose selected controls outward.

This is not a Home Assistant-only problem. A normal 2026 home may have an iPhone household using Apple Home, an Echo in the kitchen, Google displays in bedrooms, SmartThings appliances, Matter plugs, HomeKit accessories, and a Home Assistant hub. The question is no longer "can all the apps see the device?" The better question is "which system is allowed to decide what happens?"

The Terms That Matter in the House

Automation brain means the system that decides: if this happens, and these conditions are true, do that. Home Assistant's automation docs describe this as triggers, optional conditions, and actions. In plain English: something wakes the rule up, Home Assistant checks the situation, then it acts.

Control surface means a place a person presses a button or speaks a command. Apple Home, Alexa, Google Home, SmartThings, dashboards, wall tablets, and voice assistants can all be control surfaces without owning the main logic.

Cloud routine means the rule depends on a platform service outside the house. Google explicitly warns that Google Home Routines can depend on internet, Wi-Fi, and third-party service availability and should not be used for safety-critical behavior. Alexa routines and many voice flows should be treated with the same caution.

Matter is a local smart-home standard for compatible devices. It can let several ecosystems control the same Matter device, but Home Assistant's official Matter integration is a controller, not a bridge that turns every Home Assistant entity into a Matter device.

HomeKit Bridge is Home Assistant's official way to expose selected Home Assistant entities to Apple Home as HomeKit accessories. It is different from HomeKit Device, which brings a HomeKit accessory into Home Assistant, and different from Matter multi-admin, which shares a Matter device with another Matter controller.

Where Each Platform Fits

This table separates official support, local behavior, cloud dependency, Matter/HomeKit paths, and community caveats so the decision is not just a brand preference.

Platform Best role Official support path Local and cloud behavior Main caveat
Home Assistant Primary automation brain for local, multi-brand, condition-heavy rules. Native automations, scripts, helper buttons, troubleshooting history, integrations, Matter controller, HomeKit Bridge, and HomeKit Device. Automation logic runs on your Home Assistant hardware. The result is strongest when the devices and integrations are also local. Home Assistant can expose selected devices outward, but official Matter does not make Home Assistant a Matter bridge for all existing entities.
Apple Home Family app, Siri, simple Apple-first scenes, and Apple-only accessories. Apple documents scenes and automations in the Home app and says a home hub is required before creating automations. Good fit inside an Apple household. Remote access, hub selection, Apple-only features, and HomeKit Secure Video remain Apple ecosystem concerns. Use HomeKit Bridge from Home Assistant to Apple Home when Apple should see Home Assistant entities. Do not duplicate Home Assistant's real rules in Apple Home.
Alexa Voice convenience, announcements, Echo screens, and simple household routines. Nabu Casa documents the supported Home Assistant Cloud path for exposing selected Home Assistant entities to Alexa. Good voice layer, but routine and voice behavior should be treated as cloud-service behavior. Home Assistant should hold the dependable logic. Community reports show helper-button and device behavior can change. Use Alexa routines for convenience, not for hidden lock, garage, alarm, heating/cooling, or leak logic.
Google Home Google household control, Nest displays, voice, and simple Google Home routines. Nabu Casa documents exposing Home Assistant entities to Google Assistant; Google documents advanced Home automations and routine limitations. Google's own docs warn routines can depend on internet, Wi-Fi, and third-party services. Treat Google routines as convenience, not your outage plan. Manual Google Assistant setup exists, but the easy UI path is Home Assistant Cloud. Keep critical logic in Home Assistant either way.
SmartThings Samsung appliances, SmartThings hub-connected devices, and family control for an existing SmartThings home. SmartThings documents Routines and Edge hub-connected devices for Matter, Zigbee, Z-Wave, and LAN paths. Some hub-connected SmartThings devices can run locally through Edge. App, account, service, device, and integration behavior still vary. Do not assume every SmartThings automation is local. Check whether the devices, drivers, hub, and routine path support local execution.
Community Matter bridge projects Advanced local sharing from Home Assistant to Matter-capable ecosystems when official paths do not fit. Community projects can simulate a Matter bridge, but this is not the same as Home Assistant Core's official Matter controller support. Can reduce cloud exposure for some voice/control paths when it works, but support depends on the project and fork. The original Home-Assistant-Matter-Hub repository says it stopped active maintenance in January 2026 and was archived on March 11, 2026. Treat this as an advanced caveat, not a default homeowner path.

Use Home Assistant as the source of truth. Bring devices into Home Assistant through their best local path first. Zigbee and Z-Wave are local low-power radio networks. Matter and HomeKit Device are local smart-home pairing paths for compatible devices. MQTT, ESPHome, Shelly local control, and Hue local integration are Home Assistant-friendly ways to keep supported devices talking inside the house. Then expose only what the family actually needs outward.

For Apple Home, use Home Assistant's HomeKit Bridge when the Home app should show selected Home Assistant lights, switches, covers, thermostats, scenes, or sensors. This keeps Home Assistant in charge while Apple stays a friendly family interface.

For Alexa and Google Home, the supported easy path is Home Assistant Cloud from Nabu Casa. Expose a curated list of entities, which are the individual lights, switches, sensors, scenes, or helper buttons Home Assistant can show to another app. Do not expose every sensor and diagnostic object. If a routine just says "good night" and calls one Home Assistant scene, that is reasonable. If the routine contains the actual security, heating/cooling, or leak logic, move that logic back to Home Assistant.

For Matter devices, use Matter multi-admin when the same physical Matter device should appear in more than one platform. That is different from exposing all of Home Assistant as Matter. It is usually fine for a Matter plug to be visible in Home Assistant and Apple Home. It is not fine for both systems to run competing motion schedules for that plug.

When It Is Fine to Keep a Routine Outside Home Assistant

Not every rule needs to be moved. Keep a routine in Apple Home, Alexa, Google Home, or SmartThings when the action is harmless, platform-specific, and obvious to the family.

  • Voice announcements: Alexa or Google can announce school pickup reminders, bedtime cues, or calendar prompts.
  • Speaker and media behavior: music, timers, alarms, and display behavior often belong in the voice ecosystem.
  • Family scenes: a simple "movie night" scene in Apple Home can be fine if it only calls a Home Assistant scene or controls a few non-critical lights.
  • SmartThings-only appliances: if a washer, refrigerator, TV, or appliance feature only exists cleanly in SmartThings, leave that narrow routine there and document it.
  • Vendor maintenance: firmware updates, meaning device software updates, calibration, and special settings may stay in the vendor app even when daily automations live in Home Assistant.

What to Move Into Home Assistant

Move a routine into Home Assistant when it needs multiple conditions, several device brands, repeatable troubleshooting, or local behavior during an internet outage.

  • Lighting with presence: motion or presence, time of day, illuminance, sleep mode, and manual override all in one place.
  • Locks and garage doors: one authority, clear notifications, manual fallback, and no duplicate unlock or open rules in voice platforms.
  • Heating, cooling, and comfort: occupancy, windows, weather, utility rates, and temperature limits should be traceable and easy to disable.
  • Water leaks and shutoffs: use local sensors where possible, keep manual shutoff clear, and test alerts before relying on automation.
  • Cameras and privacy: decide where recording, detection, notifications, and retention happen. Do not let three apps define three different privacy policies.
  • Presence and away mode: combine phones, sensors, locks, and schedules in one system so the home does not arm, disarm, or turn lights off from conflicting rules.

A Safe Migration Plan

  1. List every routine by app. Write down Apple Home automations, Alexa routines, Google Home routines, SmartThings routines, vendor app schedules, and Home Assistant automations.
  2. Mark the risky ones. Locks, garage doors, alarms, cameras, heating/cooling, water, exterior lighting, and anything that affects safety or privacy go first.
  3. Choose the owner. For a Tara-style local setup, Home Assistant owns the real rule unless a platform-specific reason says otherwise.
  4. Create the Home Assistant version. Use clear names, areas, helpers, and traces. Test it manually before disabling the old routine.
  5. Disable duplicates, do not delete immediately. Turn off the old Alexa, Apple, Google, SmartThings, or vendor routine for a week so rollback is easy.
  6. Expose only the final controls. Share scenes, buttons, switches, or selected entities outward after the rule works in Home Assistant.
  7. Test outage behavior. Unplug internet from the modem, not power from the whole rack, and verify which local automations still work. Keep manual controls available.

What Works When the Internet Is Down?

Home Assistant can keep running without internet if the hub, router, Wi-Fi, radios, and devices still have power and the involved integrations are local. That is why a UPS for the hub and network gear matters more than another app shortcut.

Alexa and Google voice routines should be treated as internet-dependent. Even if a device command eventually lands on a local Matter device, spoken voice recognition, routine evaluation, account state, and assistant behavior are not a local-only Tara-style foundation.

Apple Home can be strong inside an Apple household, but Apple automations still depend on a properly set up home hub and Apple ecosystem behavior. SmartThings can run some hub-connected devices locally through Edge, but the local answer changes by device, driver, hub, region, and routine type. For both, the homeowner-safe answer is the same: test the actual automation you depend on.

Matter, HomeKit, and Bridge Caveats

Use Matter multi-admin when one Matter device should be controlled by multiple Matter ecosystems. For example, a Matter plug can be added to Home Assistant and then shared to Apple Home or Google Home so the family sees it in a familiar app.

Use HomeKit Bridge when Apple Home should see selected Home Assistant entities. This is often the cleanest Apple-family path because Home Assistant stays the automation owner while Apple Home gets switches, lights, thermostats, covers, scenes, or helpers.

Use Home Assistant Cloud for the easiest supported Alexa and Google exposure. Manual configurations and community local bridges can be useful for advanced users, but they should not become an undocumented dependency in a homeowner handoff.

Be especially careful with community Matter bridge projects. The idea is attractive: publish Home Assistant entities to Matter so Alexa, Apple Home, or Google Home can see them locally. The caveat is support. Home Assistant's official Matter docs say Home Assistant is not a bridge for existing entities, and the original Home-Assistant-Matter-Hub repository is now archived. Use maintained forks only when you are comfortable owning that support burden.

Tara Recommendation

For a normal homeowner, start with this policy: Home Assistant runs the house; family apps control the house. That gives you local logic, cleaner troubleshooting, fewer duplicate routines, and a handoff that another person can understand later.

Keep Alexa and Google for voice, announcements, displays, and quick commands. Keep Apple Home for the family Home app, Siri, and Apple-first accessories. Keep SmartThings where Samsung or hub-connected devices make it useful. Keep vendor apps for firmware and special settings. But do not let each of those apps quietly become another automation brain.

If you are planning a fresh install, decide this before pairing the first devices. It is much easier to expose a clean Home Assistant setup outward than to untangle five years of routines after the lights start doing three different things.

FAQ

Should Home Assistant or Alexa run my automations?

Use Home Assistant for automations that should keep working locally and need conditions from several devices. Use Alexa routines for simple voice convenience, announcements, or Alexa-only features, not as the hidden brain for the house.

Can Alexa or Google trigger Home Assistant automations locally?

Not in the normal supported voice-assistant flow. Alexa and Google voice processing depend on their services. You can expose Home Assistant entities through Home Assistant Cloud or manual integrations, but the serious logic should still run in Home Assistant.

Should Apple Home or Home Assistant run automations?

Use Home Assistant when the automation depends on non-Apple devices, detailed conditions, traces, or local hub ownership. Use Apple Home for simple family-facing scenes, Siri convenience, and Apple-only devices when that is the cleanest supported path.

Does Matter replace Home Assistant Cloud for Alexa or Google?

No, not by itself. Matter can help share Matter devices across ecosystems, but official Home Assistant does not turn every Home Assistant entity into a Matter device. Community Matter bridge projects exist, but they are advanced paths with support caveats.

What works during an internet outage?

Home Assistant automations can keep running if Home Assistant, the router, Wi-Fi, and the controlled devices are powered and local. Alexa and Google voice routines should be treated as internet-dependent. SmartThings local behavior depends on hub-connected devices and Edge support.