Smart home enthusiasts are increasingly turning to self-hosted hardware to reclaim control over their living spaces. As major technology companies continue to lock local device functionality behind subscription-based paywalls, developers are responding with open-source hardware projects that operate entirely without cloud dependency.
The latest addition to this movement is a compact, Zigbee touch keypad created by a developer known as 2dom. The device is built to integrate directly with platforms like Home Assistant, allowing users to execute smart home commands without relying on third-party servers that can be decommissioned or restricted at any time.
Hardware Specifications and Design
The keypad features a slim form factor, comparable in size to a common candy dispenser, making it suitable for discreet wall mounting. Under the hood, the device is powered by an ESP32-C6 microcontroller paired with an MPR121 touch controller. This combination enables the keypad to support a 2×6 button grid, which includes numeric digits alongside dedicated clear and enter functions.
Efficiency was a primary design goal for the project. The unit utilizes an aggressive deep-sleep mode, drawing minimal power while idle. When a user touches the surface, the device wakes up in milliseconds to register the input. According to the technical project documentation, this optimization allows the hardware to function for up to six months on a single charge using a 1300-mAh LiPo battery.
Building an Offline Network
By communicating over the Zigbee protocol, the keypad creates an entirely local mesh network. This setup ensures that smart home automation triggers remain functional even if the home internet connection goes offline. The project is fully documented on GitHub, providing the necessary firmware and integration guides for users to replicate the hardware.
Why It Matters
The surge in demand for local-first hardware is largely a reaction to ongoing industry shifts. In 2026, many consumers have faced restrictions on their existing smart home setups. For instance, companies have increasingly moved to place local API integrations behind monthly subscription fees, creating friction for users who prefer to host their own automation controllers.
This follows a broader historical trend in the industry. Years prior, when manufacturers like Chamberlain decided to remove local API access for garage door controllers, it sparked a significant exodus of users toward open-source alternatives. Projects like this touch keypad represent the community’s push toward a “local-first” ecosystem where hardware ownership is not subject to the evolving business models of parent corporations.