The moment Gemini for Home landed as the default assistant on Nest speakers, our group chat lit up with the same message: time to leave. The XDA piece calling it “the nail in the coffin” wasn’t hyperbole for the self-hosting crowd. Routines broke, latency crept in, and the assistant started answering questions we didn’t ask. If your smart home has been living rent-free in Google’s cloud, this is the push to finally take control of it.
We tested seven Android apps that can replace the Google Home app on your phone, from full local-first controllers to third-party ecosystems that don’t rely on Google at all. Some are drop-in replacements. Others are bridges you use alongside your existing hardware while you migrate device by device. These are the best apps for moving off Google Home on Android without ripping every bulb out of the ceiling on day one.
What to look for in a replacement
Not every Google Home refugee wants the same thing, but the shortlist of things that matter is short.
- Local control. Devices should keep working when your internet dies. If a smart-home app still needs a cloud round-trip to turn on a light, you’ve traded one dependency for another.
- Matter and Thread support. The new standards let you pull a device out of one ecosystem and into another without factory resetting anything. Any 2026 replacement should speak both.
- Backups and export. Google Takeout for smart homes doesn’t exist. Whatever you pick should let you snapshot your setup and restore it on new hardware.
- Community integrations. Google Home only supports what Google chooses to support. Your next platform should let the community add the weird devices Google forgot.
- Mobile UX that survives daily use. Dashboards, quick tiles, widgets, and a lock-screen shortcut you can hit with one thumb while carrying groceries.
Quick comparison
| App | Best for | Local control | Matter | Free | Setup effort |
|---|---|---|---|---|---|
| Home Assistant Companion | Full migration, power users | Yes | Yes | Yes | High |
| openHAB | Java-native, rules-driven homes | Yes | Yes | Yes | High |
| Domoticz | Low-resource setups, older Pi hardware | Yes | Partial | Yes | Medium |
| SmartThings | Samsung households, Matter-first buyers | Partial | Yes | Yes | Low |
| Amazon Alexa | Voice-first users who want out of Google | No | Yes | Yes | Low |
Apps 6 and 7 are companion tools rather than standalone controllers: HomeKit bridging works through Home Assistant, and the Node-RED dashboard is a browser app you pin to your Android home screen.
1. Home Assistant Companion – Best for a full local-first migration
Home Assistant is the answer most of the self-hosting community landed on years ago, and Gemini for Home is only accelerating that. You run the server on a Pi, an old mini PC, or a NAS. The Android app is the mobile face of it: dashboards, notifications, presence detection, sensor uploads from your phone’s radios, and Wear OS tiles. It talks to more than 2,000 integrations, including every Nest device Google still ships, so you can pull existing hardware in without buying new gear.
Where it falls short: the initial setup is a project, not an afternoon. Expect to read docs, edit YAML at least once, and pick between Home Assistant OS, Container, or Supervised installs.
Pricing:
- Free and open source. Home Assistant Cloud is optional at a low monthly fee for remote access and Alexa/Google Assistant exposure without port forwarding.
Platforms: Android, iOS, Wear OS, web dashboard. Server runs on Linux, Docker, and dedicated hardware.
Bottom line: if you’re leaving Google Home for real, this is the destination. Everything else is either a bridge or a compromise.
2. openHAB – Best for rules-heavy setups and Java shops
openHAB is the other serious open-source contender, and the Android app has quietly gotten very good. The engine underneath is Java, which sounds like a downside until you realise how mature the rules engine is. If your household runs on scenes like “past 10 pm and someone’s still in the office, dim everything else to 20 percent,” openHAB expresses that cleanly. The mobile app renders your sitemap or the newer main UI pages, sends voice commands, and handles push notifications from rules.
Where it falls short: the community is smaller than Home Assistant’s, which means fewer plug-and-play integrations for niche brands. The UI feels a generation older too.
Pricing:
- Free and open source. No paid tier.
Platforms: Android, iOS, web. Server runs on Linux, Windows, macOS, Docker, and dedicated distros.
Bottom line: pick openHAB if you’re already fluent in Java or you want a rules engine that reads like code, not a wizard.
3. Domoticz – Best for low-resource hardware
Domoticz is the veteran that still runs happily on a first-generation Raspberry Pi with 512 MB of RAM. That’s the point. If you kept a Pi in a drawer for exactly this reason, Domoticz gives you a usable smart-home hub without spinning up a container stack. The Android app by Robert Godlewski (community-maintained but effectively official) covers dashboards, floorplans, camera feeds, and Google Assistant migration through IFTTT-style workflows.
Where it falls short: Matter support lags behind Home Assistant and openHAB. Some integrations still expect Domoticz-specific plugins rather than the newer generic protocols.
Pricing:
- Free and open source.
Platforms: Android, web. Server runs on Linux, Windows, macOS, Synology, and Raspberry Pi.
Bottom line: the right pick if your hub is a decade-old Pi you don’t want to replace. Skip it if you own a lot of Matter-over-Thread gear.
4. SmartThings – Best for Samsung households and low-effort Matter
SmartThings is the smoothest exit ramp for anyone who doesn’t want to run a server. Samsung has quietly turned it into the most complete Matter and Thread controller on Android, and it works with plenty of non-Samsung hardware too. The app is polished, the automations are visual, and adding a Matter device is a QR-code scan away. It’s still a cloud service at heart, so it doesn’t tick the local-first box, but for a big chunk of ex-Google Home users that’s an acceptable trade.
Where it falls short: local execution is limited to a subset of routines, and if Samsung’s cloud has a bad day, so does your house. Non-Samsung Thread border routers still work better than they used to but aren’t seamless.
Pricing:
- Free. No paid tier.
Platforms: Android, iOS. Hub hardware is optional if you have Samsung TVs or fridges that already act as one.
Bottom line: the easiest landing spot for households that want to leave Google without adopting a homelab hobby.
5. Amazon Alexa – Best if voice is what you’re really replacing
Say what you like about Amazon, but Alexa on Android is the mature voice ecosystem that isn’t Google. The app pairs Echo hardware, runs Routines, and now handles Matter devices directly. If the thing you actually miss about Google Home is the “hey speaker, turn off the kitchen” gesture, moving your voice layer to Alexa is a lot less work than moving your entire hub. You can leave the smart plugs and bulbs alone and just re-onboard them under Alexa.
Where it falls short: it’s another cloud, another account, and another company with a microphone on your counter. Local voice is limited to a small set of Echo hardware, and privacy is a very different story than Home Assistant’s local wake word.
Pricing:
- Free app. Optional Alexa+ subscription for the newer LLM-driven assistant.
Platforms: Android, iOS, web console.
Bottom line: the quickest way to keep talking to your house without Gemini in the loop. Weakest choice if privacy is the reason you’re leaving.
6. HomeKit-adjacent bridging – Best for pulling Apple gear onto Android
Because Apple’s own Home app is iOS-only, Android users bridge HomeKit accessories through Home Assistant’s HomeKit Controller integration. Install Home Assistant from the picks above and add HomeKit-only devices from there. Once paired, those devices show up in your Home Assistant dashboards and automations exactly like everything else, and the traffic stays on your local network. It’s the cleanest way to inherit a household with mixed HomeKit and non-HomeKit gear without buying an iPad to sit in a drawer as a hub.
Bottom line: not a standalone app, but the reason a lot of Android switchers pick Home Assistant in the first place.
7. Node-RED Dashboard – Best for a browser-first control surface
Node-RED is a flow-based automation engine that pairs beautifully with Home Assistant or openHAB. Its dashboard runs in a browser, and there’s no maintained native Android client, so the right move is to open the dashboard in Chrome and pin it to your home screen as a PWA. You get a full-screen custom control panel, no app store dependency, and the flexibility to design exactly the tiles you want. It’s not a replacement for a hub, it’s the front-end you build when the default dashboards don’t fit your household’s habits.
Bottom line: worth the setup effort if you already run Home Assistant or openHAB and want a mobile control surface that’s yours end to end.
How to pick the right one
If you want a real exit from Google’s smart home and you’re willing to spend a weekend on setup, install Home Assistant and never look back. It’s the answer for most of the people the XDA piece was written for.
If you want the same control philosophy but prefer Java, older-school rules, and a smaller community, openHAB is the honest alternative. Both live on the same shelf.
If your hub is a first-gen Raspberry Pi and RAM is the constraint, Domoticz still delivers where the newer tools bog down.
If you don’t want to run a server at all and your gear is mostly Matter, SmartThings is the softest landing. Just accept the cloud dependency going in.
If the only piece of Google Home you actually miss is the voice command, put Alexa on your phone and Echo hardware on your counter. That single swap fixes 80 percent of the pain for people who never used Google Home for anything beyond “turn off the lights.”
And if your household straddles ecosystems, plan on Home Assistant plus the HomeKit Controller integration plus a Node-RED dashboard for the family-facing tiles. That combination absorbs almost anything.
FAQ
Is Home Assistant really free? Yes. The software itself is open source and there’s no paid tier. Home Assistant Cloud is an optional low-cost subscription for remote access and Alexa/Google Assistant exposure without opening ports on your router, but every core feature works without it.
Can I keep my Nest thermostat after moving off Google Home? Yes. Home Assistant, openHAB, and SmartThings all support Nest devices through their cloud APIs. You lose some of Google’s proprietary features like Home/Away sensing tied to Google accounts, but temperature control, schedules, and automations keep working.
Will my routines break during the switch? Some will. Anything that relied on the Google Home app to trigger a routine needs to be rebuilt in the new platform. Most controllers on this list have visual automation builders that make the port straightforward, but budget an evening for it.
Do I need to buy new smart bulbs and plugs? Almost never. If your devices already work with Matter, Zigbee, Z-Wave, or standard Wi-Fi, any of these platforms can adopt them. The only common exception is gear that’s locked to a single vendor cloud.
What about voice control if I ditch Google Assistant? Alexa is the easiest voice swap. Home Assistant supports its own local voice assistant that runs entirely on-device with Wyoming satellites and open speech models, which is the answer for anyone leaving Google over privacy rather than pricing.