The KM Universal Home Controller is a 7-inch ESP32-S3 touchscreen hub built to control digital and dimmable outputs locally, then extend those channels around a building through compact ESP32 Wi-Fi output nodes. Channels can be named, grouped, scheduled and mapped without turning the system into a collection of separate apps.
Rather than using the touchscreen as a simple remote, the controller holds the channel layout, room controls, schedules, network configuration and node mappings. It gives the installation one consistent interface while the actual outputs can be beside the screen or somewhere else on the Wi-Fi network.
Designed around the 800 × 480 Waveshare ESP32-S3 touch platform, giving enough screen area for real controls, status and setup pages rather than a phone-sized menu stretched across a panel.
The UI is organised around channels and rooms, not individual GPIO numbers. A channel can represent a light, LED strip, relay, fan enable or other controlled circuit and can be assigned to the most appropriate local or remote hardware.
A remote output node is a classic ESP32 running the KM node firmware. After Wi-Fi setup it operates as a network output device for the touchscreen hub, allowing a controller in one location to switch or dim hardware in another without running every control cable back to the screen.
Stores the UI, channel assignments, schedules and node mappings. Sends live output commands across the local Wi-Fi network.
Receives channel commands and drives configured digital or PWM outputs beside the equipment being controlled.
The node starts in setup mode until Wi-Fi is configured, then restarts as a station on the installation network. The controller can discover nodes and assign their outputs to channels from the touchscreen.
Add output nodes where more channels are needed. The touchscreen still presents one consistent set of rooms, names and controls, while the physical outputs can be distributed around the property.
The controller produces low-voltage logic/PWM control. The connected interface hardware determines the load: relay or contactor interfaces for switched circuits, MOSFET drivers for DC loads, or other suitable isolated drivers for the equipment being controlled.
Digital channels for relay modules, contactors, enable inputs and other binary loads.
PWM channels for suitable MOSFET drivers, LED strips and other low-voltage dimmable loads.
Use appropriate driver hardware to switch auxiliary devices or provide a variable control signal where supported.
Link related channels so an area can be operated together while retaining individual control.
Up to five timed actions per day, per channel, for automatic switching and level changes through the week.
Assign a channel to local hardware or an output on a discovered Wi-Fi node instead of wiring every load to the hub.
The page now documents what belongs in the controller and what belongs in a node, so firmware installation is tied to the correct hardware rather than presented as two anonymous ESP32 downloads.
More visual coverage of the system: channel control, network/node mapping, scheduling and the hardware itself. These supplied renderings can be replaced one-for-one with real photographs or screenshots later without changing the page layout.
The browser flasher remains available, but it now sits inside the product page. Use Chrome or Edge on a desktop computer, a data-capable USB cable and the installer that matches the device.
Complete touchscreen hub image including bootloader, partition table and controller application.
A clean install can erase stored controller settings.
Complete factory/recovery image for the classic ESP32 node, including bootloader, partition table, OTA boot data and application.
Use this node image only with a classic ESP32 board, not ESP32-S2 or ESP32-S3.
Close serial tools, connect the correct board with a USB data cable and power it from the computer.
Press the matching install button and select the ESP32 serial device shown by the browser.
Keep the cable connected until the installer completes, then allow the controller or node to restart.