Voice assistants and smartphones are often the go-to interfaces for modern smart home systems. However, if you fancy more direct physical controls, you can go that route as well. To that end, [Salim Benbouziyane] whipped up a nifty keypad to work with his Home Assistant setup.
The build is based on an ESP32 microcontroller, which has wireless hardware onboard to communicate with the rest of [Salim’s] Home Assistant setup. Using the ESPHome firmware framework as a base, the microcontroller is connected to a four-by-three button keypad array, built using nice clicky key switches. There’s also an indicator light on top as a system status indicator. A fingerprint scanner provides an easy way for users to authenticate when disarming the alarm.
Security and speed were the push for [Salim] to whip up this system. He found it difficult to disarm his alarm in a hurry when fumbling with his phone, and the direct keypad entry method was far more desirable.
Sometimes, the easiest route to the smart home of your dreams is to just build the exact solutions you need. Video after the break.
I’m glad I’m not the only one who’s less keen on phone controls for this stuff! Of course, the ideal is that the system is truly smart and turns stuff on/off based on timers, sensors, etc, but there always remains stuff that you need to switch. Using a phone seems like such a hassle compared to a button.
Also, just a note on using HA for security – it’ll be better than nothing, but it’s susceptible to WiFi/BT jamming, which apparently is becoming more common in break-ins (at least here in the UK). A proper wired security system isn’t, and even a professional wireless system is fairly resistant. Also your insurance company will not give a discount.
I’ve been using a combination of wireless remotes and WLED setups to interface with Home Assistant beyond the web/app. It’s neat to see something purpose-built.
The more things change, the more they stay the same. Some things that keep changing, while keep staying the same, is the need for – 1- pushbuttons – 2 – switchbuttons – 3 – dials – 4 – non-blinky lights indicating the pushbutton has been pushed (or switchbutton has been switched on) – 5 – status indicators (red/green/purple/yellow/etc).
It WILL keep coming back. Because UI/User-Interface (graphical or not) is a UI, and hiding gazillion menus with gazillion sub-menus with all kinds of hidden (but not critical) buttons, that are bundled with critically needed buttons, was a terrible idea to start with.
Translation – look at a 1980s boombox and admire how pretty much ALL of the functionality/functionalities can be figured out mostly by looking at the controls (and indicators). (spoiler, I own a small collection of 1980s boomboxes, but it is unrelated, just bring it up as an example of very, very, VERY simple UI that served its function quite well without the need for RTFM – unless it is some kind of fancy-schmancy kind of boombox that also has a clock, a timer, a TV and other doodas that don’t go with 1980s music, just an add-on).