Home automation is the personal domain I have the most ambivalent relationship with. Done well, it's invisible — the lights come on at the right brightness when you walk into a room, the thermostat respects what the house actually does, the locks behave predictably. Done poorly, which is most of the time in most installations, it's a slow-motion negotiation between your enthusiasm for the technology and the rest of the household's patience for it.
A few things I think are worth attention in this space:
The WAF principle is the hardest constraint, and it's almost always underestimated. Wife Acceptance Factor — the hobbyist's name for "would my spouse actually use this without grumbling, on a bad day, in a power outage" — is the single most useful design check I know of for home-automation work. Nearly every clever automation I've ever built that violated it ended up disabled within a month. The technology problem is solvable; the household-acceptance problem is what separates systems people live with from systems people quietly unplug. It's the first principle I reason from in everything else here — I make the full case for it, disco bulbs and all, in The Wife Acceptance Factor Is the Only Spec That Matters.
Local-first vs cloud-tethered is the durable architectural question. Devices that depend on a vendor's cloud to function are renting their behavior from a company that may pivot, get acquired, or simply stop running the service. Local-first systems — Home Assistant, Hubitat, anything with on-device logic — survive vendor outages and survive vendors. The premium you pay for local-first (more setup, more responsibility for updates and backups) is worth it for any device whose failure mode would be more than a minor inconvenience.
Protocol fragmentation is real, and Matter hasn't fixed it yet. Zigbee, Z-Wave, Wi-Fi, BLE, Thread, and a long tail of vendor-proprietary stacks all coexist in a typical installation. Matter was supposed to be the unification layer — and may yet be — but for now it's another protocol added to the pile rather than the consolidation it was sold as. Architects are used to this pattern; standards rarely arrive ahead of the fragmentation they're meant to clean up.
The crossover with the rest of this site is real. IoT and consumer-device security touches everything I think about in ICS Security. Local on-device inference is starting to connect to AI. Demand response and behind-the-meter generation push directly into GridTech. Home automation is where a lot of the patterns I work with at scale show up at one-house scale, with the same tradeoffs and a much faster feedback loop.
Posts under this section will be a mix: build notes when I get something working that actually meets the WAF bar, opinionated takes on the protocol-and-platform landscape, and the occasional cross-pollination piece where a household-scale problem mirrors something I've seen at enterprise scale.
Recent posts
The Wife Acceptance Factor Is the Only Spec That Matters
Home automation's hardest problem was never the technology. It's the people who never opted into your project and have to live inside it anyway — told through six bulbs doing a rainbow disco.