Home Assistant on your NAS

A friend bought smart bulbs, the cheap ones, and had them for about three years before the manufacturer shut down the service that operated them. Not the company — just that product line, discontinued with a notice nobody reads. The bulbs still lit up when you flicked the wall switch. Everything that made them smart stopped, permanently, because the intelligence had never been in the bulb.

This is the defining problem with consumer smart home equipment and it is structural rather than a matter of picking better brands. The device in your wall is usually a thin client. The logic — the schedules, the automations, the app you actually interact with — lives on a server owned by a company whose interest in your lightbulb has a commercial lifespan.

What Home Assistant inverts

It moves the brain into the building. A machine in your house talks to the devices directly, holds the automations, and provides the interface. The manufacturer's cloud becomes optional, and for many device types it can be removed from the arrangement entirely.

The consequences are the ones you would predict. Things work when the internet is down, which matters more than people expect the first time a router dies and the heating cannot be adjusted. Commands happen immediately rather than travelling to a data centre and back. And devices from manufacturers who despise each other end up in the same automation, because the integration is happening on your machine rather than requiring two companies to agree on a partnership.

That last one is the practical selling point in most houses. Nobody sets out to own equipment from six manufacturers; it accumulates. A thermostat bought with the boiler, bulbs from a sale, a doorbell chosen by somebody else, sensors picked up over two years. Each brand's own app handles its own devices and none of them speak to each other. One local system that talks to all of them turns six disconnected gadgets into something that behaves like a house.

The protocol question, which decides everything

Before buying anything else for a smart home, this is the thing worth understanding, because it determines whether a device can ever be freed from its manufacturer.

Devices that communicate over open local radio standards can be controlled directly by your own hub — no account, no cloud, no permission. Devices that only speak to their maker's servers over the internet can sometimes be adapted and sometimes cannot, and when a manufacturer changes their system, whatever adaptation existed breaks.

So the buying rule is short: prefer devices that work on a local radio standard, and treat cloud-only equipment as rented rather than owned. It costs slightly more at purchase and it is the difference between hardware that outlives its manufacturer and hardware that does not. My friend's bulbs were the second kind, which is why they are now ordinary bulbs.

What it costs you, honestly

This is the service in the whole self-hosted set that I am most cautious about recommending, and I want to explain why rather than skip past it.

It has a genuine learning curve. Not the installation — that is the same container pattern as everything else and takes minutes. The automations are where the time goes, and they are a kind of programming even when the interface hides that fact. "When the last phone leaves the house, and it is after sunset, and nobody has set the away switch, turn off everything except the hall" is a piece of logic with branches, and writing logic with branches is a skill.

It also updates frequently, and updates occasionally break an integration with a device whose manufacturer changed something. This is a project moving fast, which is good for capability and bad for anybody wanting a thing they never think about. If your household tolerance for "the lights did something odd this morning" is low, be aware of that before you move the heating onto it.

And a rule I apply to my own house and recommend to everybody: anything safety-relevant keeps a dumb fallback. Lights still work from the wall switch. The boiler still has its own thermostat. The door still opens with a key. Automation is a convenience layer on top of a house that functions without it, and a smart home where the failure of a computer means you cannot get in is not a clever house, it is a fragile one.

Why it belongs on a server you already have

The nice structural thing about this one is that it needs almost nothing. A home automation system spends most of its life idle, waiting for a sensor to say something. It is a tiny workload sitting on hardware that is already running for other reasons — the file server, the photo library — and adding it costs no additional machine, no additional electricity worth counting, and no additional box in the hallway.

Which means the decision is not really about hardware at all. It is about whether you want the logic of your house to live in your house. For my friend with the bulbs, that question had already been answered for him by somebody in a meeting he was not invited to, three years after he paid for them.