BK Home Ops

The origin

It started with one light turning on.

On January 2, 2015, I bought my first Wink Hub and two GE Link light bulbs while I was still living with my dad.

I still remember pairing the first bulb and feeling genuinely skeptical that when I hit the button on my phone, the light would actually turn on.

It did.

It felt like magic. And with that, it felt like almost anything might be possible.

Across competing ecosystems

More than a decade learning how smart-home systems fail together.

I became a power user pretty quickly, moving from simple app control into voice assistants, connected switches, shades, locks, sensors, garage doors, security, cameras, and dashboards.

At first, the goal was mostly control. But control is the easy part. The harder question is whether all those systems can behave like one coherent home.

Then I moved to Hubitat and started building rules with real conditional logic. The house began reacting to motion, doors, presence, time of day, security state, and what people were actually doing.

AlexaGoogle HomeHarmony HubZ-Wave switchesPhilips HueNest thermostatsHunter Douglas PowerView shadesAugust locksLutrongarage doorssecuritycamerassensors

What it became

The house became increasingly automated.

Lights could gradually shift from cooler daylight tones to warmer evening light.

Kitchen accent lights could change color when the washer or dryer finished.

Getting into bed could shut down TVs, lights, fans, locks, security, and more.

The problem

But everything was always just bolted on.

Rules lived everywhere: Hubitat, Alexa, Google, Lutron, MyQ, and other platforms. If something stopped working, I might have to relearn how I had set it up months or years earlier, figure out which system actually owned the rule, and then trace through how everything interacted.

That is the part most homeowners should never have to carry in their head. A house can have impressive technology and still feel fragile if the systems are not designed to work as one.

Eventually I knew it was not sustainable. After talking it through with a friend who had experience in software and product development, I realized the house did not need more automations.

It needed an architecture.

How I think now

A smart home should never fight the people who live in it.

If someone manually changes a light, the automation should respect that. If someone pauses a rule, the system should not leave them wondering days later why something is suddenly broken. If something fails, the house should recover gracefully whenever possible.

I am no longer interested in seeing how many things I can connect. I am interested in making all of the technology disappear into the experience of living in the house.

One system should own the logic.
Other platforms should do the jobs they are good at without becoming competing brains.
Devices should be able to come and go without breaking everything.
Automations should be understandable, maintainable, and able to recover when something changes.
Manual choices should always be respected by the house.

BK Home Ops

What this is becoming.

Lately, I have started wondering whether the things I learned the hard way in my own home could help other homeowners avoid some of the same mistakes.

I do not know exactly what BK Home Ops becomes yet. What I do know is that most people probably do not need more smart-home gadgets. They need the technology they already have, and whatever they add next, to behave like one thoughtfully designed system.

Your home should work for you. Not the other way around.