Nobody asked for this.
Nobody asked for a smart home that needs a firmware update before you can turn on the kitchen lights. Nobody asked for a thermostat with a six-tap menu to change the temperature. Nobody asked for a speaker that requires a Google account, a privacy policy acknowledgment, and three app permissions just to play a song.
And yet here we are.
I've been in homes my whole career — twenty years building and managing construction across everything from residential houses to data centers and transit stations. I've seen building systems evolve. Some of that evolution was genuinely good. Spray foam insulation. Hybrid heat pumps. Smart panels with arc-fault protection. Real improvements that made the physical plant of a house better, safer, more efficient.
Then there's the other kind of 'smart' — the kind that adds a touchscreen to your refrigerator, puts your HVAC controls behind a cloud server in California, and calls it innovation. That's not improvement. That's a tech company's revenue model dressed up as a feature.
Why I Pulled Google Out of My House
The breaking point for me was the same one it is for most people: the system I'd built to make my life simpler kept requiring more of my attention. Software updates that reset preferences. Routines that stopped working after a policy change. Devices that went 'legacy' eighteen months after I bought them.
I'm a single dad with two kids and a full plate. I don't have time to be the IT department for my own house.
So I started pulling things out. Not dramatically — not all at once. Just quietly replacing, one system at a time, with things that work the way a good building system is supposed to work: reliably, without supervision, and without phoning home to a server farm to decide whether to turn the porch light on.
Here's what actually changed, and what I replaced it with.
---
What I Replaced and What I Use Now
Thermostat. Pulled the Nest. Replaced it with an Ecobee — not because Ecobee is some radical departure, but because it doesn't require a Google account to function and the local API is documented and accessible. If the internet goes down, my HVAC still runs on schedule. That's the minimum viable feature for a building system in my house. HVAC is one of the five critical systems in any structure. It should not be dependent on a company's cloud uptime.
Speakers. Gone. Replaced with a Sonos setup using local playback — no voice assistant, no always-on microphone, no skill ecosystem to manage. Music plays when I want it to play. It doesn't ask me if I meant something else.
Lighting. This one was the most satisfying swap. Replaced Philips Hue (which requires a hub that pings their servers) with Lutron Caseta switches. Caseta runs on its own local hub with a clear, documented protocol. The switches feel like switches. They work when the internet is down. They'll work in ten years. That's what a light switch is supposed to do.
Doorbell / cameras. Replaced Ring (Amazon) with a locally-stored system — Reolink cameras writing to a local NAS. Nobody has access to footage of my front door except me. That felt like a thing that should have been obvious from the start.
---
The Actual Principle Here
This isn't a Luddite take. I'm not telling you to rip out your smart home and go back to incandescent bulbs and a rotary phone.
I'm telling you what twenty years working on building systems taught me about how to evaluate anything you put in a house: does it perform its function independently, or does it require an external dependency to operate?
A furnace should heat the house. A light switch should control the light. A door lock should lock the door. The moment any of those core functions require a subscription, a server, or a working internet connection, you've introduced a failure mode into a building system that didn't used to have one.
I've seen $800,000 commercial buildings go dark because a 'smart' lighting controller lost its license key. I've seen residential HVAC systems lock out homeowners because the controlling app was deprecated. These aren't edge cases anymore — they're the predictable consequence of building home infrastructure on top of a tech company's business model.
Your house is a physical asset. It should run on physical systems that behave predictably. Layer convenience on top of that if you want — but the foundation should work without Wi-Fi.
---
The Short Version
If you're building a smart home or retrofitting one, here's the checklist I use now:
- Does it have local control? Can it run without the manufacturer's cloud?
- Is the protocol documented? Can someone else support it if the company goes under?
- Does it still work when the internet is down? If no, it's a convenience layer, not a building system.
- What happens in ten years? Nest is already pulling features from older hardware. Plan for that.
Good building systems run for decades with minimal intervention. That's the standard. Everything in your home should be measured against it.
If you're renovating, building new, or just frustrated with your current setup and want a second set of eyes — text me. I'll tell you what's worth keeping, what to rip out, and what to replace it with that'll actually hold up.
