Home automation is affordable and powerful, but until it’s as boring and reliable as a light switch, there’s still a while to go. Myke Ireland looks into the future.

Home automation has been “just around the corner” for about four decades now. Long enough that it’s worth asking why we’re still talking about it as a future state rather than something that’s already normal.

And just to explain, I don’t mean someone having one or two LED globes that they control with an app. I mean a home with as much control and automation as you’d consider commonplace in a commercial setting.

Despite this, walk into the average home today,        and very little has changed. Lights are still switched manually. There are still multiple remote controls sitting on the coffee table. TVs are left on in empty rooms. Heating and cooling are adjusted reactively, as is opening the garage door. The residential home, for the most part, remains something we actively manage rather than something that quietly manages itself.

That’s what makes the gap between expectation and reality so noticeable. For decades, the idea of an automated home has been presented as an obvious end state, a place where friction is reduced, routines disappear into the background and technology responds without being asked.

And yet, in practice, fully automated homes are still rare enough to feel unusual when you encounter one.

Historically, there was a clear explanation for this. In the 80s and 90s, residential automation existed almost exclusively in the homes of the ultra-wealthy. Early systems were complex, expensive and bespoke, installed by specialists and maintained like any other piece of high-end infrastructure. Automation was aspirational, but fundamentally out of reach. It was easy to look at those homes and assume that one day, when the technology became cheaper, it would trickle down and become commonplace.

Well, that moment has well and truly arrived. The cost barrier has collapsed. Automation hardware is now affordable, widely available and technically capable of far more than those early systems ever were. Lighting, climate control, media, security and energy monitoring can all be automated without requiring a six-figure budget or a dedicated equipment rack. Yet most homes remain only lightly automated, if at all.

Smart devices exist, but they’re often isolated, inconsistently used or abandoned after the novelty wears off. The result is not a cohesive, automated environment, but a collection of disconnected controls that still demand attention.

So, with affordability clearly no longer being an issue, the real question becomes harder to answer. Why hasn’t home automation become normal? What is it about the residential environment, both technically, culturally or behaviourally, that keeps automation on the fringes rather than at the centre of how our homes function?

I have my opinion, and it’s the same opinion I have when it comes to any measure of technology adoption, user experience.

Take something as basic as a light switch. It’s hard to overstate how well the traditional mechanical switch solved the problem it was designed to fix. You walk into a room, you flick the switch and ta-dah, the light turns on. It works essentially every time. There’s no latency, no dependency on anything else, no thought required and it has become so instinctual that we don’t even think about it.

When it does fail, which is rare, it fails very obviously. And in reality, the biggest issue wasn’t the reliability of the switch at all, it was human behaviour. Six-year-old me never turned anything off and Mum reminded me what the power bill was going to cost.

Simple cause, simple effect. That’s what automation was meant to fix.

But, like all technology, automation complicates that equation in ways that aren’t immediately visible to the consumer. A “smart” wall switch might still look like a switch, but now it sits inside a chain of dependencies: Firmware, wireless connectivity, a hub or bridge, a local network, a cloud service, an app and sometimes a second system translating commands so it can talk to something else.

Any one of those things fails and the automation fails, which is one thing, but now the expectation of what happens when you want to turn a light on also fails, and so your brain says: “Urgh, just give me a simple light switch.”

This is where compatibility becomes a quiet yet very powerful deterrent, and we’re reintroduced to that ever so defining technical word of the century, the “ecosystem”. Consumers aren’t irrational for being cautious here; but they are a little under-informed. Most people don’t naturally think in terms of protocols, ecosystems, or interoperability. They think in terms of outcomes. Will this work when I need it to? Will it keep working in five years? And what happens when it doesn’t?

In the 1980s, the problem was that there were too few options and they were inaccessible. Today, the problem is that there are too many options and the consequences of choosing poorly are felt every single day: Alexa vs HomeKit vs Google. iPhone vs Android. Devices that work brilliantly on their own but awkwardly together. Features locked behind apps you didn’t want to install in the first place, and no real roadmap of which device works best with each ecosystem or edge device.

And this is where the real friction starts to appear. Not in the technology itself, but in the cognitive load required to make sense of it. A light switch used to be a decision you made once. Automation turns it into a series of decisions you keep paying for, keep updating and keep managing, because if you don’t, it will stop working at some stage. Just like your PC, just like your printer.

Which leads to an even more important question: If automation introduces more ways for something simple to fail, how much improvement does it need to deliver before people are willing to tolerate that risk?

If we’re looking for the things that are actively preventing home automation from becoming normal, compatibility is still the obvious place to start, even if it’s improved dramatically in recent years. A few years ago, we started to hear talk of Matter and Thread, and with it, the promise of finally solving the ecosystem problem.

The pitch was compelling: Buy devices from any manufacturer, use whatever phone/app/PC you like, choose the control layer that suits you and everything would just work together. Lights from one brand, switches from another, locks from a third – all interoperable, all abstracted away from vendor lock-in.

In theory, this was the missing piece. In practice, it hasn’t quite delivered on that promise.

Matter and Thread-compatible devices do exist, and in controlled environments, they work well, particularly when everything in the system adheres to the same standards. But that’s the catch. Are most people prepared to replace perfectly functional devices just to achieve protocol consistency? And how confident can anyone be that today’s compatibility guarantees will still hold five or ten years from now, once firmware updates slow down, and support for Windows quietly closes?

Rather than breaking down ecosystems, what we’re seeing instead is manufacturers doubling down on them. Every brand wants to offer a unified experience, as long as you stay entirely within their product range. That works right up until you need something they don’t make, or don’t make well. At that point, the promise of seamless automation gives way to compromises, workarounds and additional layers of complexity, and right here is where everything starts to become out of reach.

In my own home, the only way this complexity becomes manageable is by introducing a translation layer, in my case, Home Assistant running on a Raspberry Pi. It sits quietly on the network and does exactly what it’s designed to do: translate between ecosystems. Wall switches from one vendor. TVs from another. Lighting controllers, solar, appliances, security, all speaking different languages, all made synchronous through a single control plane. Once it’s set up, it’s stable, flexible and genuinely powerful. But that setup works only because I’m comfortable maintaining it.

Small firmware updates, integration changes, automation tweaks, none of that feels intimidating to me, but for someone without a technical background, it’s a very different proposition. Home Assistant is by no means a plug-and-play experience; it’s closer to a level of system management, and that gap in technical confidence is still one of the biggest barriers to adoption.

The comparison I keep coming back to is the domestic technology of the past. Buying a VCR in the 1990s and expecting anyone in the household over the age of 30 to confidently use it was a fantasy. In fact, the commonality of not knowing how to use a VCR was so widespread that a whole scene was dedicated to it in the Hollywood smash hit, City Slickers, still one of my favourite movies.

Home automation today isn’t all that different. On the surface, it works, but until either a single manufacturer offers a genuinely complete ecosystem or vendors become truly comfortable opening their platforms so others can integrate cleanly, there is almost no chance you’ll get all your controls in one place.

You see, automation works in commercial environments because it’s maintained. There’s a budget for it, there’s people for it, if you’re really lucky, there’s even an IT support email that goes to the wrong person for it. The point is, it’s all expected and paid for.

In a home, that model simply doesn’t translate. Even modest monthly maintenance costs feel unreasonable to most households, regardless of the benefits.

So perhaps the more uncomfortable truth is this: Home automation hasn’t failed because the technology isn’t good enough. It’s struggled because the home is an unforgiving environment. Expectations are absolute. When something stops working, there’s no tolerance for excuses, no appetite for troubleshooting and no desire to become a system administrator just to turn a light on.

In the commercial world, complexity is hidden behind contracts and support agreements. In the home, it lands squarely on the person who just wanted things to be easier. That difference has become the straw that’s going to consistently break the camel’s back. Automation promises to remove effort, but with the current state of the technology, it’s still adding far more effort than most people have time for.

In reality, until automation can truly disappear into the background, it will continue to feel like a project rather than a utility. Something you opt into because you’re interested, curious or technically inclined, not because it’s fun, easy or exciting. The moment automation demands ongoing attention, it undermines the very value it claims to deliver, and that’s what kills user experience every day.

So, while you can get your home to do a handful of funky, cool things with a few bucks and a bit of YouTube, unless you have the time and energy to become your own system administrator, you may want to stick to those one or two LED globes.

It’s true that compatibility is better than it’s ever been, and the tools are cheaper and more flexible, but power alone isn’t what makes technology stick. Reliability does. Predictability does. Trust does. And right now, the residential automation story still asks too much of the people it’s meant to serve.

Maybe that’s the real reason home automation remains “just around the corner”. Not because we can’t build it, but because we haven’t yet learned how to make it boring enough. Until it works as quietly and reliably as a light switch, the home will remain a place, unfortunately, where you still have to get up to turn the lights on.