You do not need to replace all your devices at once to escape cloud dependency. Most people can migrate their existing smart home to local control in a single weekend — often without buying any new hardware. Here is the systematic approach that works.
Before You Start: Audit Your Devices
Make a list of every smart device in your home. For each one, note the brand and model, how it currently connects (Wi-Fi, Zigbee, Z-Wave, Bluetooth), whether it has a local API, and whether it requires a cloud account to function. Many devices you think are cloud-dependent actually support local control — they just default to cloud because that is what the manufacturer prefers.
Day 1 Morning: Set Up Your Hub
Install Home Assistant on a Raspberry Pi 4 or mini PC. This takes 30–60 minutes including download, flashing, and initial setup. Install essential add-ons: Mosquitto MQTT broker, File Editor, and Terminal and SSH.
Day 1 Afternoon: Migrate Zigbee and Z-Wave Devices
If you have a Zigbee or Z-Wave hub (SmartThings, Wink, Hubitat, Philips Hue Bridge), add a compatible USB coordinator to your Home Assistant host and pair your devices directly with Home Assistant. Zigbee and Z-Wave devices need to be re-paired to a new hub — plan for 5–10 minutes per device, and work room by room.
Day 1 Evening: Migrate Wi-Fi Devices
Shelly Devices
If you have Shelly relays or switches, they support local REST API and MQTT out of the box. In the Shelly app, enable “Local Control” and optionally set up MQTT pointing to your local Mosquitto broker. Add the Shelly integration in Home Assistant — no cloud required.
Tasmota-Compatible Devices
Many cheap Wi-Fi smart plugs and switches (Gosund, Treatlife, some Sonoff models) can be flashed with Tasmota firmware for completely local control. This transforms a $10 device from cloud-dependent to fully local.
Day 2 Morning: Migrate Lights
Philips Hue bulbs connect locally via the Hue Bridge — the Home Assistant Hue integration communicates directly with the bridge on your local network, no cloud required after initial setup. IKEA TRADFRI and Sengled Zigbee bulbs can be paired directly to Home Assistant ZHA integration, bypassing manufacturer apps entirely.
Day 2 Afternoon: Recreate Your Automations
Home Assistant automation editor can recreate most of what your old hub did, often with more sophistication. Import common automations from the Blueprint Exchange community — many popular automation patterns are available as one-click imports.
What You Probably Cannot Migrate (and Alternatives)
- Ring / Nest cameras: Replace with PoE cameras + Frigate NVR
- Ecobee thermostat: Has a local API — check the Home Assistant Ecobee integration
- Alexa/Google Home voice control: Replace with Wyoming local voice assistant
A realistic time budget
“A weekend” breaks down roughly like this for a typical home with 15–25 devices: 2–3 hours for the device audit and Home Assistant base install (skip if already running), 4–6 hours re-pairing Zigbee/Z-Wave devices to your own coordinator, 2–4 hours rebuilding the automations that mattered most (don’t try to recreate every single one immediately), and 1–2 hours testing everything works with the internet unplugged, using the resilience test covered in our offline guide. Cameras and locks tend to be the slowest individual category, since each one requires a physical visit to the device.
Your rollback plan
Before unpairing anything from its original app, take a screenshot or written note of what each device did and how it was configured — if a migration stalls partway (a device refuses to re-pair, a critical automation isn’t ready), you want the option to temporarily re-add a device to its original app rather than leaving it non-functional over a weekend. This is also why staging the migration by device category (all lights, then all locks, then all sensors) beats doing it room-by-room: if you run out of time, an entire category either works or doesn’t, rather than having a half-migrated mess spread across every room.
A quick post-migration test checklist
Before calling the weekend done, verify explicitly rather than assuming: every re-paired device responds from Home Assistant, your most-used automations (not all of them, just the ones you’d notice breaking) fire correctly, and the offline resilience test from our fully-offline guide passes. Fifteen minutes of deliberate testing catches the one device that silently failed to re-pair correctly — better to find it Sunday evening than the next time you actually needed it.
Free guide — no signup
Trying to cut the cloud out of your smart home? This is the whole map in one place.