Wireless desk remote
A touchscreen with a few named buttons controlling low-voltage demonstration outputs on two ESP32 receivers.
A staged completion guide and prompts. The parts and finished result still need physical validation.
Share your buildWhat you will work towards
Use a small touchscreen to control two nearby low-voltage devices.
CAIBI’s proposed addition: Choose real actions; add acknowledgements, connection state and a stand.
Guide version 1.0. AI can help explain, adapt and debug; you still measure, assemble and test the physical result.
Start with the original
Tutorial foundation
Primary tutorial read; hardware and current dependency compatibility untested
See the original source for its photos and demonstrations. We have not copied imagery without confirmed reuse rights. A source prototype is not a photo of this proposed CAIBI build.
Parts to confirm before buying
- Source-compatible ESP32 CYD touchscreen
- Two ESP32 receivers and low-voltage LED test outputs
- Appropriate resistors, protected power and wiring
- Measured tabletop enclosure
Use the source wiring and bill of materials as the starting point. Confirm exact variants, availability, tools and complete cost before ordering.
The completion route
- Run the source example with LEDs only and write down which receiver responds to each control.
- Replace raw pin commands with a fixed list of named actions. Validate packets, handle acknowledgements and make missed commands visible.
- Design four large touch targets with clear on/off and connection states.
- Measure the finished assembly, make the case and test touches with it fitted.
Prompts to move it forward
Copy a prompt into your AI tool with the source material and your actual parts. Work through one small step at a time and check the output before using it. Choose an AI tool or practise the skills first.
Plan the next step
Turn the linked CYD ESP-NOW example into a four-button desk remote. Use a fixed action-ID allowlist rather than accepting arbitrary GPIO numbers. Add packet length/version checks, acknowledgements, timeout handling and duplicate-command protection. Start with LEDs only. Ask for my core version before changing callbacks. Source: https://randomnerdtutorials.com/esp32-cyd-esp-now-control-multiple-boards/
Design a measured enclosure
Design an angled desk case around my measured CYD board. Keep the active touch area unobstructed, allow access to USB/reset and provide strain relief and stable feet. Ask for display depth and connector positions. Source: https://randomnerdtutorials.com/esp32-cyd-esp-now-control-multiple-boards/
Check and document the result
Create a test log for Wireless desk remote. Intended outcome: Use a small touchscreen to control two nearby low-voltage devices. Separate expected behaviour from observed results. Include power restart, disconnected inputs, communication failure and the actual physical use. Ask me to provide results, firmware versions, changes, photos and unresolved problems. Never mark a test passed without my evidence. Source: https://randomnerdtutorials.com/esp32-cyd-esp-now-control-multiple-boards/
What to test and record
- Press each button and check the correct receiver and output.
- Disconnect a receiver; the screen must not falsely report success.
- Repeat a command and confirm its intended final state.
- Restart all devices and confirm a predictable output state.
Keep photos, exact parts and software versions with the test log. Failed or incomplete attempts are useful evidence too.
A possible next version
Replace demonstration actions with one documented home integration after the command path is proven.
What builders are contributing
Suggest something useful, improve a route or share what you made. Contributions are reviewed before publication. Community builds remain attributed to their builders.
Loading reviewed contributions…