Local-First Smart Home

Overview

An ongoing project to move my house off a patchwork of vendor clouds and onto a local-first smart home built on Home Assistant. The goals are simple to state and harder to deliver: everything critical should keep working without an internet connection, my family and guests should be able to use the house without learning anything, and the automation traffic should stay off the home Wi-Fi instead of congesting it.

It started in December 2025 with research and a deliberate local-first, privacy-first design goal, and has grown one device and one subsystem at a time since. I spent much of the spring researching and refining the design, then turned to active build-out in late May and through June. The platform and several subsystems are live and running daily; others are still being built out or tuned.

This project pairs with my High-Performance Home Network build. That project decongests and hardens the Wi-Fi; this one moves smart-home devices onto dedicated local radio meshes so they are not competing for Wi-Fi airtime in the first place.

Goals

• Local-first and private. Core automations (climate, locks, alerts) run entirely on local hardware, with no dependency on a vendor cloud and no household data leaving the property.
• Cloud-optional, never cloud-dependent. Cloud services are welcome for the conveniences the family enjoys, but nothing essential relies on them. The guiding rule is that even if the cloud is down, everything else just works.
• No lock-in, reversible by design. I avoid installing anything that would not still function as an ordinary "dumb" device without the internet or local Wi-Fi. If we ever move, the next owner or renter inherits working switches, locks, and thermostats, not a broken system they cannot operate or a pile of gear to strip out.
• Effortless for everyone else. Family and guests should be able to operate the house by voice, a phone dashboard, or a wall tablet without instructions. Ease of use is a hard requirement, not a nice-to-have.
• Decongest the Wi-Fi. Push device chatter onto purpose-built Z-Wave and Zigbee meshes so the Wi-Fi stays fast for what the family relies on day to day: home-office work and video calls, every personal compute surface (phones, tablets, laptops, watches), streaming, and gaming.
• Resilient and recoverable. The whole configuration is version-controlled and backed up, so a hardware failure is an inconvenience, not a weekend lost.
• Observable. If something goes offline, a battery dies, or a cost spikes, I want to know before anyone else in the house notices.

The build so far

The project grew the way good systems usually do: one useful thing at a time.

It began with a quick win. A handful of Zigbee smart plugs gave my wife simple, reliable power automation and, just as importantly, seeded the first self-healing mesh. From there I added a Z-Wave radio and the devices that had to be rock-solid: a smart thermostat coordinating a dual-fuel heat pump and propane furnace, and a keypad deadbolt with a personal code for each of us so the house knows who came and went.

With the bones in place, I built outward. An energy layer now tracks power and cost per device and whole-home, across both electricity and propane. A local weather entity blends my backyard station with public forecasts to drive the climate logic and storm alerts. Presence from our phones ties the house together, locking up and shedding load when everyone leaves. And because the house should be reachable from anywhere, Home Assistant Cloud (Nabu Casa) adds secure remote access, so we can check a camera, switch something off, or lock the door from the road. Underneath it all, the entire configuration is versioned in Git and backed up, so a failure is an inconvenience rather than a lost weekend.

The technical specifics live on their own pages, linked below: the architecture and hardware, the systems in detail, and the running change log.

Challenges

• Mesh interference and topology. Running separate Zigbee and Z-Wave radios on a single host means respecting the physical and RF realities of mesh networking: keeping high-frequency components adequately spaced, and placing coordinators and repeaters so signal propagates reliably across a rural property.
• Automation state machines. Overlapping triggers and complex conditional states occasionally conflict and produce surprising behavior. Resolving these has meant isolating logic into self-contained packages and refactoring automations toward predictable, single-purpose execution paths.
• Getting at the data. Not every resource reports cleanly. Electricity arrives through Opower from the utility, and propane only after I extended an open-source integration to scrape it. Water is the open conundrum: on a private well there is no utility meter or monthly bill to read, so tracking household usage means metering the well pump and treatment system myself rather than pulling a number from a provider.

What's Next

• Recorder database. As the device registry grows, audit the recorder include/exclude filters and consider moving from the default SQLite engine to a more robust local database to head off long-term storage I/O bottlenecks.
• Decentralized backups. Extend the local-first principle to automated, encrypted snapshots pushed off-host (a local NAS or isolated storage) so a hardware or database failure can never take the house with it.
• Per-room sensing. Add temperature and comfort sensors throughout the house with a room-based naming scheme, and a per-room comfort view.
• Cloud conveniences, locally anchored. Integrate Spotify and Google services for the conveniences the family likes (multi-room audio chief among them), while building local equivalents so the experience degrades gracefully when the cloud is unavailable.
• Local media server. Stand up a local server for movies, shows, and music, so entertainment does not depend on a streaming service being up.
• Local voice control. Move voice commands on-device so the house can listen and respond without sending audio to the cloud.
• Local LLMs. Use small local language models for basic natural-language control and summaries, backed by cloud models for heavier lifts, keeping the cloud-optional principle intact.
• Deeper energy and resource metering. Today only a handful of devices are individually metered for electricity, and propane is tracked at the tank with an estimated furnace split. The goal is fuller whole-home electricity and propane consumption detail, plus water: on a well, that means tracking the well pump and water-treatment energy and overall usage trends rather than a utility water bill.
• Power resilience. A CyberPower CP850PFCLCD pure sine wave UPS (on the way) will sit in front of the Green and the core network gear. The property has a whole-home propane generator, but outages still happen, so the UPS bridges the gap between an outage and the generator coming online, and its pure sine wave output cleans up both utility and generator power for the sensitive electronics. This piece is shared with my home network build.
• Richer camera alerts. Upgrade snapshot notifications to short recorded clips.

Explore the Details

• Architecture & Hardware - the host, the two radio meshes, ecosystem integration, and the bill of materials.
• Systems in Detail - a closer look at climate, weather, energy, security, and the rest.
• Change Log - how the project has evolved over time.

← Back to all projects