Summary
Voice control sounds like the easiest way to run a smart home until you realize how often you’re repeating yourself. Turning off the lights still requires a decision, a command, and a quick peek to check whether anything happened. An actual smart home should know what to do in these situations instead of waiting for a command from you. So I started moving those decisions into Home Assistant automations. My phone leaving home, the position of the sun, and a quick NFC scan now handle jobs I used to ask for. The result isn’t a completely hands-off smart home yet, but it’s closer to what I wanted from a smart home. Stop telling your house what it already knows Voice commands are the fallback, not the plan The biggest change was treating voice commands as a fallback instead of the default. If I perform the same action under the same conditions, I’d rather define those conditions once than keep announcing my intentions. My AC shutoff is the simplest example of this. When my phone leaves home Wi-Fi, and GPS confirms I’ve been away for longer than 10 minutes, Home Assistant switches off all my AC smart plugs and disarms my climate control system. The delay keeps a disconnect or a quick walk outside from triggering a shutdown. So instead of remembering to tell my assistant to turn off air conditioning when I’m leaving, I just leave, and Home Assistant takes care of the rest. Sunsets and NFC tags do the talking now Two sunset routines, one NFC sticker, and nobody shouting at a speaker Lighting is another job I no longer wanted to narrate. At sunset, an automation already turns ambient lights in my office and bedroom on. At sunrise, another turns them back off. Neither routine needs a conversation. The trigger already describes when I want the action to happen, and since the routine triggers at sunrise or sunset, I don’t have to worry about tweaking time settings as seasons change. My bedtime routine is slightly different because I don’t always go to bed at the same time. So instead of forcing a schedule, I placed an NFC tag on my phone charger at my bedside table. I tap the tag, and an automation automatically turns off all lights in the bedroom, turns on the air conditioning, and arms my climate control system to maintain the perfect temperature. That is an intentional interaction, but it’s a quiet, repeatable one. I’m not trying to eliminate every button or gesture. I’m trying to stop issuing several separate instructions when one action can express what I want. The tag also doesn’t need every device to remain online to work. If my AC isn’t plugged in or the climate control unit I made isn’t functional, tapping the tag still controls every device that’s online and supposed to be run in that automation. The boring automations are the ones doing real work Rent math and an LED strip that taps me on the shoulder Some of my best automations aren’t particularly impressive to read, but they do real things that remove small friction points from throughout my day. For example, Home Assistant now takes care of my rent calculation. It automatically captures each AC’s monthly electricity consumption, just before its monthly counter resets, and uses that to calculate how much electricity my flatmates and I consumed. It then converts that into a utility bill, adds everything up, splits it evenly, and gives me each person’s share. I also use automations to get notifications, without ever having to touch my phone or read a banner on my laptop. The idea is simple: I’ve got an LED strip running around my office’s ceiling, run by an ESP32 connected to Home Assistant. Anytime something happens that needs my attention, like my 3D printers starting or finishing a print, an internet dropout, someone ringing the doorbell, or one of my Docker containers going down, my LED strip flashes in a particular color to notify me before going back to its original state. These aren’t things I should need to ask aloud. They’re predictable jobs with predictable timing that a smart home should know about, and Home Assistant does that job reliably. Silent automations fail silently, which is the problem Offline ESP32s don’t file complaints Moving away from actively controlling your smart home does have one major drawback, though: failures can disappear into the background just as easily as successful actions. When you tell Home Assistant to turn a light off, you know when it’s going to be turned off, and if it doesn’t, you immediately know something is wrong. Automations can fail silently unless all required devices are online and connected to Home Assistant. Home Assistant skips unavailable devices with just a log warning. I had a network connectivity problem with my ESP32 ESPHome devices that would cause them to drop off my network automatically. While I worked that issue out, any automations controlling these devices would silently run and fail, without me ever realizing what happened. A simple solution to the problem is to have Home Assistant monitor all entities and send a notification to your phone when an important device has been offline for a significant period of time. That is, however, an extra setup for each automation I build. Regardless, it’s important to know when your automations aren’t working as expected before you find that out by surprise. Fewer commands, more maintenance I traded repeating myself for babysitting automations. Worth it. In the end, I didn’t replace voice commands with a home that magically understands everything. I’ve replaced repetitive requests with specific rules, and those rules still require periodic maintenance. Offline ESP32s, network drops, and the random network hiccup have made that painfully obvious. But I prefer improving a routine once to repeating the same instruction every day, and that’s the smart home I’m working toward. One that quietly handles predictable chores and gets my attention when there’s actually something I need to decide or fix.