Home Automation Setup

Hub selection is the most consequential decision in home automation. Choose wrong and you spend months fighting the platform instead of building automation. Home Assistant: open-source, locally hosted, runs on your hardware. Supports 3,000+ integrations, full local control (your automations run even without internet), unlimited customization. Learning curve is real -- expect 10+ hours to build a working system. But it's the right choice for anyone serious about home automation who isn't locked into Apple. The Home Assistant Green ($99) is a purpose-built device and removes the Pi complexity. SmartThings (Samsung): cloud-based, easier setup, decent device support. Runs from a hub or the Samsung SmartThings Hub v3. Works well for Samsung appliances and many Zigbee/Z-Wave devices. Disadvantage: cloud-dependent automations add latency and fail when Samsung's servers are down (which happens). Less customizable than Home Assistant. Apple HomeKit: if your household is entirely Apple devices and you want tight Siri integration, HomeKit is extremely reliable and private. Uses your iPad or Apple TV as the hub (it's automatic if you have one at home). Disadvantage: fewer compatible devices and limited automation logic compared to Home Assistant. Matter/Thread: the new interoperability standard -- most new smart home devices in 2024 support Matter, which means they'll work with Home Assistant, Apple Home, Google Home, and SmartThings simultaneously. If you're buying new devices, choose Matter-compatible when possible. Decision shortcut: Own Apple devices exclusively and want something that just works? HomeKit. Want full control and don't mind a setup weekend? Home Assistant. Want easy cloud setup with okay flexibility? SmartThings.

Before buying anything new, catalog what you already own. Every smart device speaks one or more protocols: Wi-Fi: connects directly to your home network. Easy setup, no hub required. Downside: fills up your Wi-Fi with dozens of low-quality devices, and if the manufacturer's cloud server shuts down, the device may stop working (Wemo, Insteon, and others have had this happen). Zigbee: low-power mesh protocol. Requires a Zigbee coordinator/hub. Devices include: Philips Hue, IKEA Tradfri, Sengled, Aqara, many SmartThings sensors. Mesh means each device also relays signals -- your network gets more reliable as you add more devices (with some exceptions -- battery-powered devices don't route signals). Z-Wave: similar mesh protocol to Zigbee, different frequency (908MHz in US), less interference from Wi-Fi. Preferred for door locks (Schlage, Kwikset), smoke/CO detectors (First Alert Onelink), and security sensors. More expensive devices than Zigbee. Bluetooth: short-range, fine for switches and sensors near your hub. August locks, some LIFX bulbs, Eve sensors. Limited range is a real constraint. Thread/Matter: newest standard. Thread is the network layer; Matter is the application layer. Requires a Thread border router (Apple TV 4K, HomePod mini, Nanoleaf Thread devices, or Amazon Echo 4th gen serve this role). Create a spreadsheet: device name, brand, protocol, app it currently uses. This becomes your roadmap.

This step is optional but strongly recommended if you care about security. IoT devices are notoriously poorly secured -- budget smart plugs and cheap sensors often have no security updates, outdated firmware, and in some cases phone home to servers in regions with poor privacy laws. Network segmentation means putting your IoT devices on a separate virtual network (VLAN) that cannot initiate connections to your main network where your computers, phones, and personal data live. IoT devices can still access the internet and receive commands from your hub, but they can't reach your laptop. What you need: a router and/or switch that supports VLANs. Common options: Asus routers with Merlin firmware, Ubiquiti UniFi (the gold standard, used in enterprise networking), TP-Link Omada, or pfSense/OPNsense on a mini PC. Basic setup (Asus router example): Advanced Settings → LAN → VLAN → Create a new VLAN → assign it a subnet (e.g., 192.168.20.0/24) → create a guest network or dedicated SSID called "IoT" that uses that VLAN → set firewall rule to block traffic from IoT VLAN to your main LAN. Your Home Assistant hub lives on your main network (or a separate management VLAN) and has firewall rules permitting it to send commands to IoT devices but preventing IoT devices from initiating connections back to your main network. This is genuinely intermediate networking. If VLANs are new to you, the Home Assistant community (community.home-assistant.io) has excellent setup guides specific to your router model.

Home Assistant on a Raspberry Pi 4 (most common setup): 1. Download the Home Assistant OS image from home-assistant.io/installation/raspberrypi 2. Flash it to your microSD card using the Raspberry Pi Imager (free, from raspberrypi.com/software). Select "Raspberry Pi OS" in the picker, then "Use custom" and select the HA image you downloaded. 3. Insert the SD card into the Pi, connect Ethernet to your router, plug in power. 4. Wait 5--10 minutes for first boot. Open a browser and go to homeassistant.local:8123 5. Create your Home Assistant account and walk through onboarding. Home Assistant will automatically discover many devices on your network -- especially Philips Hue, Sonos, Chromecast, and any other devices that broadcast on your local network. Accept the ones you want. For Zigbee: plug in your USB Zigbee coordinator before starting HA. In HA: Settings → Devices & Services → Add Integration → Zigbee Home Automation (ZHA) → select your USB device. ZHA is built into HA and supports most coordinators. For SmartThings: go to home-assistant.io/integrations/smartthings and follow the OAuth integration steps. SmartThings connects via their API and all your existing SmartThings devices will import. For HomeKit (running HA alongside HomeKit): HA includes a HomeKit Bridge integration that exposes HA entities to Apple Home. Settings → Integrations → HomeKit Bridge.

Scenes: a saved state for a group of devices. "Movie Night Scene" = living room lights at 20%, TV on, soundbar on input 1. Scenes are manually triggered -- you activate them via an app tap, voice command, or as an action inside an automation. Scenes themselves have no triggers. Automations: trigger → condition → action. An automation fires when a trigger event occurs, optionally checks a condition, and then performs actions (which can include activating a scene). Example: - Trigger: Sun sets - Condition: Mode is "Home" - Action: Activate "Evening" scene Building automations in Home Assistant: Settings → Automations & Scenes → Create Automation. The visual editor is straightforward for basic automations. For complex logic, YAML mode gives you full control. SmartThings: Menu → Automations → Create Automation → similar trigger/condition/action structure. Apple Shortcuts / HomeKit Automations: open the Home app → Automation → Create → choose trigger (time, sensor, person arriving, etc.) → select actions. Common automation mistakes: no conditions. If your "arrive home" automation runs when you leave AND return (because geofencing is imprecise), add a condition checking if lights are already on. Infinite loop automations -- an automation that turns on a light that triggers another automation that turns off the same light. Think through the full chain before saving.

Presence-aware automation is the biggest upgrade over simple timer-based automation. There are two levels: Room-level occupancy: Motion sensors in each room. Lights turn on when someone enters, off after X minutes of no motion. Zigbee motion sensors (Aqara, IKEA, Philips Hue) work best for this -- they update every 10 seconds and have multi-year battery life. Important: motion sensors detect motion, not presence. A person sitting still on a couch watching TV will not trigger a motion sensor after the motion timeout. For living rooms and bedrooms, supplement with: mmWave presence sensors (detect breathing and micro-movement -- Aqara FP2, Tuya mmWave), or use manual override logic (when someone turns on the TV, keep lights on regardless of motion). Home-level presence: Who is home? Methods in order of reliability: 1. Phone presence via Home Assistant Companion app: your phone's GPS location is reported to HA. Create person entities with their phones. HA tracks home/away state. Very reliable when the phone is outside -- less reliable for "just arrived" due to GPS accuracy. 2. Unifi Presence Detection (if using Ubiquiti network): HA detects when your phone's MAC address connects to Wi-Fi. Near-instant detection. 3. Ping-based detection: HA periodically pings your phone's local IP address. Works on all networks. Unreliable because phones sleep and stop responding to pings. Use multiple methods combined: HA's "person" entity can track multiple device trackers and use a priority system.

Geofencing uses your phone's GPS location to trigger automations when you cross a defined boundary around your home. In Home Assistant: the Companion app for iOS and Android reports your location to HA. The onboarding creates a "Home" zone automatically. You can create additional zones (work, gym, school) and use them in automations. Arrival automation example: - Trigger: Person enters zone "Home" - Condition: Sun is below horizon (don't turn lights on mid-afternoon) - Action: Unlock front door, turn on entry lights, set thermostat to 70°F, turn off "away" scene Departure automation example: - Trigger: All persons leave zone "Home" - Delay: 10 minutes (confirm it wasn't a false detection) - Action: Turn off all lights, lock doors, set thermostat to 65°F, enable security cameras Geofencing accuracy: GPS zones work best when set to 200+ meter radius. Smaller zones miss arrival events because GPS drifts. A zone too small around your house means the automation fires as you pull into the street -- fine -- but also sometimes fires incorrectly when GPS wanders while you're asleep. Multiple household members: in HA, use the person entity which tracks multiple trackers per person. For "all persons away," use a template condition that checks every person's state. The HA documentation has the exact template. Apple Shortcuts: create an automation triggered by "I arrive" at your home location. More limited than HA but works without any extra setup if you're using HomeKit.

This is the step nobody does until their SD card fails or they need to rebuild after a power surge. Do it now. Home Assistant backup: Settings → System → Backups → Create Backup. For automatic backups, install the "Google Drive Backup" or "Dropbox Backup" add-on from the HA Add-on Store. Set daily backups, keep 7 copies. The backup includes your full configuration, automations, scenes, and integrations. For Raspberry Pi: the SD card is the single point of failure. After getting your system stable, install the "HAOS SD card to USB" backup method or move your installation to a USB SSD entirely (faster and far more reliable than SD). Amazon search: "USB SSD for Raspberry Pi 4" -- about $30 for a Samsung T7 1TB. Documentation: open a plain text file or Notion page and write down: - Every device, its protocol, what hub it's connected to, and its Home Assistant entity ID - Every automation's purpose in plain English - The IP addresses of your hub and key devices (use static DHCP reservations in your router so they never change) - Your IoT VLAN SSID and password - Where your hub is physically located and how to access it This sounds like overkill. It is not. Six months from now you will forget how your heating automation works and be very glad you wrote it down. Every automation system that someone built and then abandoned was abandoned because they couldn't maintain it. Documentation is the maintenance plan.