Back in January I shared a 5‑year technical review of our home automation setup here. At the time, my goal was pretty simple: review the infrastructure that had to change, capture what held up, what didn’t, and what surprised me after living with a fairly complex system day to day.
What I didn’t expect was what writing that post would trigger.
Technically, most of the system worked.
Automations fired. Devices stayed online. Edge cases were mostly handled.
But while writing the review, something uncomfortable became clear:
I was still thinking about the house more than I wanted to.
Not because it was broken — but because it demanded attention:
- checking whether things were behaving as expected
- wondering what would happen during an internet outage
- choreographing guest access
- managing notifications instead of trusting them
- treating privacy as something to actively manage
That post ended up being the moment I stopped asking
“How do I automate this?”
and started asking a different question:
What would it mean for a home to actually behave well?
Not smarter.
Not more clever.
Just calmer, more predictable, and less demanding of attention.
That shift in framing changed very concrete things about the system:
- automation stopped being about clever triggers and started being about policy
- notifications were redesigned so silence actually meant something
- guest access became time‑bound and self‑cleaning
- outages stopped being stressful because behavior was predictable
- privacy became an outcome of architecture, not a setting
I ended up writing a lot of this down, mostly to make sure I wasn’t just rationalizing decisions after the fact.
This was the original post that kicked off that rethinking: 
Technical Pivot 5‑Years Later
I’m not posting this as a how‑to, recommendation, or stack endorsement — just sharing the reflection in case it resonates with anyone else who’s been living with a system long enough to feel both proud of it and a little tired of it at the same time.
Happy to discuss if it’s useful.
