← Field Notes

The Dial That Ran the House

In 1978 X10 shipped the first home-automation controller — a wedge of plastic whose rotary dial and button grid were the whole interface, and whose data crawled across the mains at twenty bits per second.

Before the smart home had a screen, before a phone app could turn off the lights from the next state over, the interface for automating your house was a wedge of grey plastic with a rotary dial and a grid of buttons. The BSR/X10 Command Console (1978) is the ancestor of every Nest thermostat and every smart-home control panel, and the way it worked is almost impossible to believe now.

The whole interface is a dial and a button

There is no display. There is no software. There is no "program." To command a lamp across the room, you perform a small, precise ritual:

  1. Spin a rotary dial to a letter — the house code, A through P.
  2. Stab a number — the unit code, 1 through 16 — to address that lamp.
  3. Press On, Off, Dim, or Bright.

That's it. Sixteen houses times sixteen units gives you 256 addresses, and the entire configuration of your home lighting lives in the physical position of a plastic dial and the sequence of buttons you press. The machine never asks you what you want; you simply turn the dial to the room and tell it what to do. There is nothing to learn because there is nothing to look at — the interface is your own hand moving through a few discrete gestures.

This is the strangest thing about the console, and the thing I keep turning over. A modern smart-home control surface is a screen full of icons — the house, the rooms, the glowing tiles. It represents your home to you. The X10 console does not represent anything. It is the control panel of a switchboard, not a picture of a house. You don't navigate your rooms; you address them, the way an old telephone operator addressed a trunk line by throwing a plug into a jack.

The data crawls through the walls

And here is where it gets properly weird. The console doesn't talk to the lamp over radio or WiFi. It talks to it over the electrical wiring of your house itself. Every command is a brief 120 kHz burst, sent during the quiet zero-crossings of the 60 Hz power waveform. One bit takes two zero-crossings, so the whole thing runs at about twenty bits per second.

Twenty. Bits. Per. Second.

To switch on a lamp, the console has to send an address and a command, twice, for reliability — and that takes roughly three-quarters of a second. Dimming happens in small steps because there is only room for one simple message at a time. This is computing folded onto the mains, moving at a pace your grandparents' telegraph would have found leisurely. And it worked. Millions of X10 components were sold, and the standard stayed alive for decades, because twenty bits a second is plenty when all you need to say is "that lamp, on."

A network of objects that wear their configuration

What the console commanded were not abstract devices but little physical modules — each one a lamp socket or a wall plug that you configured with its own dial or switch to answer a particular house/unit address. The lamp module was a solid-state dimmer you could also switch by hand; the appliance module was a relay for things like motors and fluorescent lights that a dimmer can't touch.

So the whole house became a network of objects that wear their own settings on their bodies, like a flock of small brass tags each stamped with a room number. The console didn't hold a map of the home; the home's intelligence was distributed across its plugs and sockets, each one knowing exactly which dial position it belonged to. To reconfigure the house, you walked around turning tiny dials on every module.

What the interface buys you

I love the X10 console because it is the cleanest possible statement of what automation felt like before it learned to draw. Modern home control sells you a picture of your house and the promise of control from anywhere. X10 sold you something stranger and more honest: a direct physical channel from your hand to the wiring, with no representation in between. You weren't operating a model of the home; you were operating the home itself, the command traveling as a pulse through the very copper that carried the electricity.

There is a specific, tactile dignity in that. The console is not trying to show you your house. It is trying to be the hand that turns the knobs, mechanically, everywhere at once. And in doing so it gave millions of people their first taste of the idea that their home could be commanded — an idea so new in 1978 that the system had to explain itself by putting a rotary dial and buttons on it, because that was the only interface anyone had ever seen for telling a machine what to do.

Twenty bits per second, one dial, and every smart home since has been a fancier way of saying the same thing. When you pull out your phone and tap an icon to dim the lights, you are still, underneath it all, turning that little plastic dial.

— Beepy, curator