Key Takeaways
- Your smart home, your data. Home Assistant processes all automations locally. Your motion sensors, door locks, cameras, and energy data never leave your home network unless you explicitly set up remote access.
- 3,000+ device integrations. If it is a smart home device — Zigbee, Z-Wave, Matter, Wi-Fi, Bluetooth, proprietary cloud — Home Assistant can almost certainly integrate with it.
- No cloud dependency. Works fully offline. Your automations still run during an internet outage. No subscription required. No account to create with a third party.
- Local AI in 2026. Home Assistant’s Assist feature now supports local LLMs via Ollama — control your home with natural language without any query leaving your network.
Why “Smart Home” Doesn’t Have to Mean “Surveillance Home”
The smart home industry has a sovereignty problem. Amazon Echo listens for wake words and processes audio on Amazon servers. Google Nest sends your home’s temperature, presence, and schedule data to Google. Ring cameras upload footage to Amazon Web Services. Samsung SmartThings routes device commands through Samsung’s cloud — meaning your light switch does not work if Samsung’s servers are down.
In 2026, an entire parallel ecosystem exists. Home Assistant is the open-source platform built on a different principle: your home’s intelligence should run in your home.
Home Assistant is installed on a local machine — Raspberry Pi, old PC, NAS, dedicated hardware — and communicates directly with your smart home devices over your local network. No cloud intermediary. No account required. No subscription. Your automations run whether or not the internet is working.
Direct Answer: What is Home Assistant and why should I use it? Home Assistant is an open-source home automation platform that runs locally on your home network. Unlike Amazon Alexa, Google Home, or Apple HomeKit (which route commands through cloud servers), Home Assistant processes all automations on a local machine — typically a Raspberry Pi. It supports over 3,000 device integrations, works fully offline, requires no subscription or cloud account, and keeps all your home data private. In 2026, it includes local AI voice control via Ollama integration. It is the sovereign alternative to commercial smart home platforms.
Hardware: What to Run Home Assistant On
Option 1: Home Assistant Green ($99) — Recommended for beginners Plug-and-play dedicated hardware. Comes with Home Assistant OS pre-installed. Just plug in ethernet and power, follow the setup wizard. No technical knowledge required. Based on a quad-core ARM processor with 32GB eMMC storage.
Option 2: Raspberry Pi 5 ($80 + case + SD card = ~$120) More flexible — you can also use it for other things. Recommended specs: 4GB or 8GB RAM, 32GB+ SD card or SSD for reliability. Install Home Assistant OS via the Raspberry Pi Imager.
Option 3: Home Assistant Yellow (~$130) Includes built-in Zigbee and Thread/Matter radio. Eliminates the need for a separate Zigbee coordinator dongle. Best choice if you use Zigbee devices heavily.
Option 4: Existing PC or NAS (Docker) If you already run a home server, Home Assistant runs cleanly in Docker:
docker run -d \
--name homeassistant \
--privileged \
--restart=unless-stopped \
-e TZ=Europe/London \
-v /home/user/homeassistant:/config \
--network=host \
ghcr.io/home-assistant/home-assistant:stableInstallation on Raspberry Pi 5 (20 Minutes)
Step 1: Download the Home Assistant OS image Go to home-assistant.io/installation/raspberrypi and download the Home Assistant OS image for Raspberry Pi 5.
Step 2: Flash to SD card Download Raspberry Pi Imager. Select “Use Custom” → choose the downloaded .img.xz file → select your SD card → Write.
Step 3: First boot Insert the SD card into your Raspberry Pi 5. Connect ethernet (Wi-Fi can be configured later). Power on.
Step 4: Access the setup wizard
After 2–5 minutes, open a browser and go to http://homeassistant.local:8123
You will see the Home Assistant onboarding wizard. Create a local admin account (no external account required) and complete the location setup.
That is it. Home Assistant is running.
First Integrations to Set Up
Zigbee (if you use Philips Hue, IKEA Tradfri, or other Zigbee devices):
Zigbee is the most common protocol for smart bulbs, sensors, and switches. You need a Zigbee USB coordinator dongle (ConBee II, HUSBZB-1, or Sonoff Zigbee 3.0 dongle — ~£15–25).
Settings → Devices & Services → Add Integration → Zigbee Home Automation (ZHA)
Select your USB coordinator
Put devices in pairing mode and add themHome Assistant’s ZHA integration communicates directly with your Zigbee devices — no Philips Hue bridge, no IKEA gateway, no cloud account required.
Matter (for newer smart home devices): Matter is the new universal smart home standard supported by Apple, Google, Amazon, and Samsung. Home Assistant has native Matter support via Thread radio or your Wi-Fi network.
Settings → Devices & Services → Add Integration → Matter (BETA)Existing smart home devices: Most commercial smart home platforms (Philips Hue, IKEA, Sonos, Nest, Ring, Tuya) have Home Assistant integrations that pull your existing devices in — even if those devices normally require a cloud account. You can keep using the same hardware while routing control through Home Assistant locally.
Building Your First Automations
Home Assistant’s automation builder is visual — no coding required for most tasks.
Example 1: Turn lights off when everyone leaves home
Settings → Automations → Create Automation
Trigger: Device tracker → Everyone leaves home
Action: Turn off → All lights in home
# Save. Done.Example 2: Morning routine
Trigger: Time → 7:00 AM (weekdays only)
Condition: Weekday = Monday to Friday
Action:
- Turn on: Kitchen lights (50% brightness)
- Set: Thermostat to 20°C
- Play: Morning playlist on SonosExample 3: Presence-based heating
Trigger: Device tracker → Person arrives home
Condition: Current temperature < 18°C
Action: Set thermostat → 20°C
Delay: 10 minutes (to avoid false triggers)Device tracking uses your phone’s Home Assistant companion app, your router’s connected device list, or Bluetooth beacons — entirely local, no external service involved.
Local AI Voice Control in 2026
Home Assistant’s Assist feature added local LLM support in 2025. Combined with Ollama running on your home server, you can control your home with natural language — entirely offline.
Setup:
# 1. Install Ollama on a machine on your network
curl -fsSL https://ollama.com/install.sh | sh
ollama pull llama3.2:3b # Small model works well for home control
# 2. In Home Assistant:
Settings → Voice Assistants → Add Assistant
Name: Local AI
Language model: Ollama
Endpoint: http://[your-ollama-machine-ip]:11434
Model: llama3.2:3b
# 3. Enable on Home Assistant companion appOnce configured, you can say:
- “Turn off all the lights in the bedroom”
- “What’s the temperature in the living room?”
- “Is the front door locked?”
- “Set the heating to 21 degrees for 2 hours”
All processing happens on your local Ollama instance. No query leaves your home network.
Remote Access Without Cloud (Tailscale Method)
One legitimate limitation of local-only Home Assistant: you cannot access it when away from home without some form of remote access.
The sovereign solution is Tailscale — a VPN that creates a direct encrypted connection between your devices without routing through any cloud intermediary (it uses a coordination server for connection setup but all traffic is peer-to-peer).
# Install Tailscale on your Home Assistant machine
# (Available as a Home Assistant add-on if using HA OS)
Settings → Add-ons → Tailscale → Install → Start
# Once active, your Home Assistant is accessible at its Tailscale IP
# from any device where you have Tailscale installed
# e.g. http://100.x.x.x:8123This gives you full remote access to your Home Assistant without exposing it to the public internet and without routing through Nabu Casa (Home Assistant’s commercial cloud service, which is a legitimate but non-sovereign option).
What Not to Do: The Cloud Trap
Home Assistant offers Nabu Casa ($6.50/month) — a commercial cloud service that provides remote access and Google Assistant/Alexa integration. It is run by the Home Assistant founders and is legitimate.
However, if sovereignty is your goal:
- Use Tailscale for remote access instead of Nabu Casa
- Use the local Assist + Ollama for voice control instead of Google/Alexa integration
- Keep all automations running locally
Nabu Casa is the one optional cloud dependency in an otherwise fully local setup. Skip it for maximum sovereignty.
Common First-Week Issues
“homeassistant.local:8123 not found”
Try the IP address directly: http://192.168.1.x:8123 — find the IP in your router’s connected devices list.
Device not being detected For Zigbee: make sure the device is in pairing mode when you add it. For Wi-Fi devices: they must be on the same network subnet as Home Assistant.
Automation not triggering Check: Settings → Automations → click the automation → Traces — shows exactly why it did or did not trigger.
Sluggish performance on Raspberry Pi If using an SD card, the card is your bottleneck. Switch to a USB SSD — dramatically improves performance and reliability. Verbatim, Samsung, or SanDisk SSDs work well.
FAQ
Does Home Assistant replace my existing smart home app? It can, but does not have to. You can run Home Assistant alongside the Philips Hue app, for example. Gradually migrate control to Home Assistant as you get comfortable with it.
Does Home Assistant work with Alexa and Google Home? Yes, with the Nabu Casa cloud service or with manual configuration of local Amazon Alexa or Google Home skill (complex but possible). If you want voice control without these platforms, use Home Assistant’s Assist + local Ollama as described above.
What happens to my smart home if Home Assistant goes down? Devices continue to function normally — your Philips Hue lights still turn on via their app, your Nest thermostat still works. Home Assistant’s automations stop running, but device control is not lost. Smart home devices with cloud dependencies still work via their original apps.
Can I use Home Assistant with Apple HomeKit? Yes. Home Assistant has a HomeKit integration that exposes your Home Assistant devices to the Apple Home app. You get the Apple UX on iPhone while Home Assistant handles the local processing.
Is Home Assistant difficult to learn? The initial setup takes 20–30 minutes. Building simple automations (time-based, presence-based) is straightforward via the visual editor. Complex automations using YAML or scripts have a learning curve. Most users start simple and gradually learn more over months.
