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 build
What 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.1. 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
From source to something you can finish
What the source provides: The linked touchscreen and receiver tutorial foundations.
What still needs doing: Name the few actions you need, distinguish commands from confirmed device state, and provide a reconnect path.
Your first milestone: Operate one low-voltage demonstration output and visibly confirm its response.
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.
Check the source before buying
Review the source material I supply for Wireless desk remote. Make a table of what is provided, missing, contradictory or dependent on a paid service. Identify exact hardware revisions, firmware files, library versions, CAD files and licences. Separate creator claims from your proposed additions. Do not fill gaps with guessed specifications. Finish with one small test that can resolve the biggest uncertainty before I buy parts. Sources: Random Nerd Tutorials: https://randomnerdtutorials.com/esp32-cyd-esp-now-control-multiple-boards/
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. Sources: Random Nerd Tutorials: 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. Sources: Random Nerd Tutorials: 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. Sources: Random Nerd Tutorials: 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.
- Record the first milestone and unresolved gaps in the build report; do not mark unobserved behaviour as passed.
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…