iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can run a smart home without a vendor cloud or monthly fee by hosting Home Assistant on hardware in your home and choosing devices that communicate over local protocols. Home Assistant’s official FAQ says: “Yes. Home Assistant runs on your own hardware in your home, so it can keep working when the internet is down.” Zigbee, Z-Wave, Matter, Thread and ESPHome devices can continue working locally when configured correctly. Cloud-only devices cannot.
The Home Assistant software itself is free and open source, with no subscription and no features locked behind a paywall. You still pay for a hub or computer, radio adapters where needed, and any optional cloud services such as remote access or cloud voice control.
What “local control” means
A locally controlled device sends commands directly across your home network or a dedicated radio mesh to Home Assistant. A light turning on, a motion sensor triggering an automation, or a thermostat changing temperature does not need to contact the manufacturer’s internet servers.
Cloud control uses a different path: your phone or Home Assistant sends a request to the vendor’s servers, which then tell the device what to do. That path stops working when your internet connection fails, the vendor has an outage, the account expires, or the product is discontinued. A device can appear in Home Assistant and still be cloud-dependent, so the integration method matters more than the logo on the hardware.
#1 Best Overall
- Powered by SmartThings: Connect, monitor, and automate your home through the SmartThings app. Build a reliable, unified smart home using Samsung's proven ecosystem
- Matter + Zigbee Smart Home Hub: Supports the newest Matter standard plus Zigbee for lighting, sensors, plugs, switches, thermostats, and more - thousands of compatible devices. PLEASE NOTE: Z-Wave not supported
- Easy Setup with Wi-Fi or Ethernet: Get started in minutes using Wi-Fi or a wired Ethernet connection for apartments, houses, and expanding smart home systems - Z-Wave not supported
- Automations That Work for You: Create custom routines for security, lighting, comfort, and energy savings. Many local automations continue working even if your internet goes offline
- Wide Device Compatibility: Connect compatible smart devices from Aeotec and many other brands to build a unified system for lighting, voice control, energy management, and climate settings
Which protocols work without the internet?
| Protocol or connection | What it needs inside the home | Offline behavior | Important limitation |
|---|---|---|---|
| Zigbee | A Zigbee coordinator connected to Home Assistant, such as Connect ZBT-2 | Devices and automations can continue operating locally | Pairing and device support depend on the coordinator and integration |
| Z-Wave | A Z-Wave controller, such as Connect ZWA-2 | Local device commands and automations continue during an internet outage | Radio-region compatibility and inclusion procedures matter |
| Matter | A local IP network and a Matter integration or controller | Local control is possible when the Matter setup is local | Some commissioning, updates or optional vendor features can still require internet |
| Thread | A Thread network, border-router function and local integration | Thread devices can remain reachable locally | Thread is the transport; the controller and border-router arrangement determine how it is managed |
| ESPHome | Home Assistant and the device on the same local network | Commands and sensor data can stay on the LAN | Firmware installation and some updates may need an internet connection |
| Wi-Fi devices | A local integration that talks to the device without a vendor server | Only genuinely local integrations continue offline | “Wi-Fi” alone does not prove local operation; many Wi-Fi products are cloud-only |
Zigbee
Zigbee uses a dedicated low-power mesh rather than your Wi-Fi network. Home Assistant needs a coordinator radio to create and manage that mesh. Connect ZBT-2 is the official USB adapter for Zigbee and Thread. Once devices are paired through a local integration, switches, sensors and bulbs can trigger one another without internet access.
Z-Wave
Z-Wave also uses a dedicated local radio and mesh. Connect ZWA-2 is the official Z-Wave adapter. Z-Wave devices are not automatically local just because they use Z-Wave; Home Assistant must have the controller and the correct integration, and the device must be included successfully. Check the radio frequency region before buying hardware.
Matter and Thread
Matter is the device-control standard; Thread is one possible network transport. A Matter-over-Thread device needs a working Thread network and a controller or border-router path that Home Assistant can use locally. Matter-over-Wi-Fi devices need the local IP network. Neither label guarantees that every setup step, firmware update or optional feature works without internet, so inspect the specific integration before purchase.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →ESPHome
ESPHome devices communicate directly with Home Assistant over your local network. They are useful for custom sensors, buttons, relays and displays because the device logic and data path can stay inside the house. Plan for internet access during initial firmware installation or later updates even if normal operation is local.
Wi-Fi products: verify the integration, not the radio
A Wi-Fi device may be fully local, partly local or entirely cloud-based. Read the Home Assistant integration documentation and look for a local API, local push events or local polling. If setup requires signing into a vendor account and the integration sends every command through that account’s servers, it will not meet an offline-control requirement.
Rank #2
- Echo Hub — An easy-to-use smart home control panel redesigned for your home. Arrange controls on your dashboard to quickly adjust devices, view cameras, start routines, and more.
- Customize your dashboard — Arrange devices into sections and resize them to focus on what matters most. Create a personalized layout that matches how your family uses their connected devices.
- Reimagined for your home - With an Alexa+ and compatible Ring subscription (sold separately), get Ring camera event summaries to stay in the know. Search your Ring footage using simple voice commands. Create routines by voice, activate modes to manage multiple devices at once, and chat with Alexa to easily control your smart home.
- Home security for the whole family — Use Echo Hub to easily arm and disarm your compatible security system, making it easy for everyone in your family to manage home security. Use the Alexa app and compatible cameras, locks, alarms, and sensors to check in while you're out.
- Works with thousands of Alexa compatible devices — WiFi, Bluetooth, Zigbee, Matter, Sidewalk, and Thread devices sync seamlessly with the built-in smart home hub.
What you pay for—and what you do not
| Component | Payment model | Why you might need it |
|---|---|---|
| Home Assistant Core | Free and open source; no subscription | The automation and integration platform |
| Home Assistant host | One-time hardware purchase or an existing computer | Runs Home Assistant inside your home |
| Zigbee/Thread coordinator | One-time adapter purchase | Connects those radio devices to Home Assistant |
| Z-Wave controller | One-time adapter purchase | Connects Z-Wave devices to Home Assistant |
| Home Assistant Cloud | Optional paid service | Simplifies remote access and cloud voice-assistant connections; it is not required for local automations |
| Vendor cloud plan | Optional or required, depending on the device | May provide remote access, notifications, storage or proprietary features; cloud-only products still depend on it |
Home Assistant’s FAQ states: “There is no subscription to use it, and no features are locked behind a paywall.” That describes the core platform. Hardware, electricity, replacement storage and optional services remain separate costs.
Choose a Home Assistant host
Home Assistant Green: the simplest route
Home Assistant Green is the easiest official plug-and-play choice. It ships with Home Assistant preinstalled, so you connect it to your network, complete setup in the browser and add the radios required by your devices. Choose it when you want the fewest operating-system and installation decisions.
Raspberry Pi or Odroid
A Raspberry Pi or Odroid can run Home Assistant when you already own one or want a small, upgradeable computer. You supply the storage, power and installation, and you are responsible for keeping the host reliable. Use a suitable, dependable storage device and keep a backup of your Home Assistant configuration.
x86-64 computer
An x86-64 mini-PC, desktop or repurposed computer provides another dedicated host. It can be useful when you need more storage or capacity for many integrations, but it consumes more power and requires more setup than an appliance-style hub.
Container or virtual machine
Home Assistant can run in a container or virtual machine on an existing server. This saves another physical box, but USB radio adapters must be passed through to the guest, and network discovery can require additional configuration. Select this route only if you are comfortable maintaining the host platform as well as Home Assistant.
Rank #3
- [Multi-Protocol Hub with Matter Bridge] The M3 is a versatile hub supporting Aqara Zigbee and Thread devices. It integrates third-party devices into the Aqara Home app. Supports advanced Matter bridge functionality, enabling Aqara-exclusive scenes and signals to sync with Matter ecosystems such as Home Assistant for seamless integration. Supports up to 127 Aqara Zigbee devices （** Not third-party Zigbee devices) and 127 Thread devices (Repeaters are needed).
- [Edge Compatibilities and Local Automations] The M3 serves as an Edge Hub, prioritizing local control and automation. Upon integration, it supersedes existing Aqara hubs, shifting the automations among them to local operation (Some cloud-based notifications still require internet). Upgrade-friendly, it supports migrating Zigbee devices from older Aqara hubs.
- [Smart IR Blaster with Feedback and Learning] The 360°IR blaster not only sends commands but also provides accurate status updates by detecting traditional remote use. It connects IR air conditioning units to Matter, functioning as an AC thermostat when paired with an Aqara Temperature and Humidity Sensor. (Note: Only one AC device can be exposed to Matter. Functionality may vary based on the Matter integration app. For Apple Home exposure, use Matter integration instead of HomeKit.)
- [Optimal Wired and Wireless Connectivity] Offering both wired and wireless solutions, the smart home hub M3 provides dual-band Wi-Fi (2.4/5 GHz) with advanced WPA3 security, and a Power over Ethernet (PoE) port. The addition of a USB-C port allows for mini-UPS and power bank connections, delivering unparalleled stability. (2A USB power adapter is not included. ) . Note: To ensure a stable connection, place the Hub M3 between 6 to 19 feet from the router.
- [Privacy-Focused with Encrypted Storage, Easy Setup and Versatile Placement] The M3 prioritizes privacy by excluding microphone or camera components. It boasts 8GB end-to-end encrypted local storage, for device lists, configuration parameters, and automation configuration data. Additionally, it includes a mount and screws for flexible placement on flat surfaces, walls, or ceilings. Magic Pair technology ensures effortless detection by the Aqara Home app upon power-up.
Set up a local-only system
- List the devices you need. Separate products by protocol and mark any device that requires a vendor account, internet connection or subscription. Do this before buying hardware.
- Install Home Assistant on a local host. With Home Assistant Green, connect power and Ethernet, then open the setup page shown by the device. On another host, install a supported Home Assistant installation method for that computer, container or virtual machine.
- Connect the required radios. Plug Connect ZBT-2 into the host for Zigbee or Thread, or Connect ZWA-2 for Z-Wave. Position USB radios away from noisy USB 3 ports and metal enclosures where practical, then confirm that Home Assistant detects the adapter.
- Open the integrations screen. In Home Assistant, go to Settings > Devices & services, choose Add Integration, and select the protocol or device integration. Follow its pairing or commissioning flow. Exact prompts can differ by integration and Home Assistant release.
- Pair devices close to the coordinator first. Add mains-powered routers before distant battery sensors when building a Zigbee or Z-Wave mesh. Give each device a clear name and room immediately so later automations do not depend on ambiguous entity names.
- Create an automation that has no cloud dependency. Go to Settings > Automations & scenes, choose Create Automation, select a local trigger such as a motion sensor, and choose a local action such as switching a light. Avoid actions that call a vendor cloud service.
- Test the normal path. Turn the light or actuator on from the Home Assistant dashboard, trigger the sensor, and confirm the event appears in the device’s history. If the command takes a detour through a vendor account, the integration is not fully local.
- Perform an outage test. Disconnect the home’s internet connection while leaving the local network and Home Assistant host powered. Run the dashboard locally, trigger the sensor and verify the automation. Restore internet before attempting updates or cloud-dependent functions.
- Add remote access only if you need it. Local control does not automatically provide access from outside the home. Remote dashboards, cloud voice assistants and vendor notification services generally require internet and may use an optional cloud service or another remote-access design.
How to evaluate a device before buying it
- Find the exact Home Assistant integration. A manufacturer may offer several models with different local capabilities. Check the model number and whether the integration communicates locally.
- Check Works with Home Assistant listings. The Works with Home Assistant program highlights products tested for local control. Treat the listing as a useful starting point, then read the integration details for the exact device.
- Ask what happens after setup. Determine whether the first pairing, firmware update, account login or region selection needs internet. A product can operate locally after an internet-assisted setup.
- Separate required and optional cloud features. Remote control, cloud recording, vendor voice services and off-site notifications may remain cloud features even when basic switching and sensing are local.
- Confirm protocol hardware. Zigbee and Z-Wave need their respective coordinators. Matter-over-Thread needs a Thread network and controller path. Buying the device without the required radio leaves it unusable in Home Assistant.
- Check recovery and replacement options. Look for documented reset, re-pairing and firmware procedures. A device that cannot be recovered without a vendor server is a poor fit for a long-term offline design.
Design for internet outages
Keep the local network and host running
“Internet down” and “home network down” are different failures. Home Assistant and local devices need power and a functioning LAN or radio mesh. If your router, access point, host or coordinator loses power, local automations stop even though no cloud service is involved.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsUse local names and clear dependencies
Build automations from local entities, local events and local services. Avoid actions that send webhooks to an outside service or depend on a vendor’s account token. Record which automations are safety-critical and test them after changing integrations or firmware.
Plan updates separately
Normal operation can be local while updates still need internet. Schedule Home Assistant, radio and device firmware updates when connectivity is available, and do not begin an update during an outage. Keep a configuration backup so you can recover from a failed update or host replacement.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What will not work offline
- Cloud-only integrations: Commands and state updates stop when the vendor’s servers or your internet connection are unavailable.
- Remote access: A phone outside your home cannot reach a private local network without an internet path and remote-access method.
- Cloud voice assistants: Voice processing and account services hosted online require internet.
- Some onboarding flows: Account creation, product activation, Matter commissioning through a particular ecosystem, or downloading firmware may require connectivity.
- Vendor cloud extras: Off-site video storage, online history, proprietary scenes and vendor notifications remain unavailable if they are not implemented locally.
These limitations do not prevent local automations; they define which features must wait until connectivity returns.
Troubleshoot a device that fails the local test
The device is visible but commands fail without internet
Check whether the integration is using a cloud API rather than a local API. Review its configuration for an account token, remote endpoint or “cloud” mode. If the vendor offers no local path, replace the integration or choose a different device rather than trying to conceal the dependency.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #4
- Home Assistant provides a professional and reliable platform for home automation, designed to run continuously 24/7.
- Powered by a 64-bit Quad-Core Cortex-A53 processor, delivering smooth and efficient performance for smart home automations.
- Includes 4GB SDRAM for reliable multitasking and 64GB eMMC
- Features a Mali-450 MP2 GPU for responsive visual interfaces, housed in a compact 85 × 85 × 15mm (3.35" × 3.35" × 0.59") design that fits easily in any space.
- Typical power consumption is under 10W, with fanless operation for quiet performance suitable for any room in your home.
A Zigbee or Z-Wave device will not pair
Confirm that the correct coordinator is connected and selected, move the device near the coordinator for initial pairing, put the device into its documented inclusion mode, and remove stale entries before retrying. For Z-Wave, verify that the adapter and device use the same radio region.
A Matter or Thread device disappears
Check that the local IP network is operating, the Thread network and border-router path are available, and Home Assistant still has access to the relevant integration. If only commissioning or firmware download fails, restore internet temporarily for that step and retest ordinary local commands afterward.
An ESPHome device is unavailable
Confirm that the device and Home Assistant are on the same reachable local network, that its power supply is stable and that its address or discovery entry has not changed. If a firmware update is required, perform it while internet access is available, then repeat the outage test.
Automations run but notifications do not arrive
The trigger and action may be local while the notification service is cloud-based. Test the physical action separately from the phone alert. Keep a local siren, light or dashboard indication for events that must work during an outage.
Quick Recap
Choose an architecture that fits your priorities
| Your priority | Practical choice | Trade-off |
|---|---|---|
| Fastest installation | Home Assistant Green plus the required USB radio | Less flexibility than managing your own computer |
| Use hardware you already own | Raspberry Pi, Odroid or an x86-64 computer | You handle installation, storage and maintenance |
| Small custom sensors and controls | ESPHome on the local network | Firmware work and update planning are part of ownership |
| Existing server infrastructure | Container or virtual machine with USB pass-through | More complex radio and networking configuration |
| Large mixed-device installation | Home Assistant with separate Zigbee, Z-Wave, Matter or Thread integrations as needed | More coordinators and compatibility checks to maintain |
A practical local-control checklist
- Home Assistant runs on hardware that remains powered in the home.
- Every device has a documented local integration or local protocol path.
- Zigbee, Z-Wave and Thread devices have the required coordinator or border-router hardware.
- Automations use local triggers and actions rather than vendor cloud calls.
- You know which remote, voice, notification and storage features need internet.
- You have tested a real internet outage while keeping the LAN and Home Assistant powered.
- You can update and back up the system when internet access is available.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
