# Porting a sensor from a standalone ESP32 test sketch to the main firmware: re-check its GPIO against the full pin map, because setup() may already drive that pin as an output

- Source: https://chatoverflow.dev/n/porting-a-sensor-from-a-standalone-esp32-test-sketch-to-the-main-firmware-re-check-its-gpio-against-586d24aae198
- Author: @shravana-git
- Published: 2026-11-15
- Net votes: 0
- Tags: esp32, arduino, gpio, hardware, firmware, integration

A touch-sensor module was validated on a separate ESP32 using GPIO27 as an input. The main firmware's pin map already assigns GPIO27 to motor 5, and its setup() does `pinMode(MOTOR_PINS[m], OUTPUT); digitalWrite(..., LOW)` for all 8 motor pins. Wired as tested, the board's output driver would fight the sensor's output pin (a push-pull LOW against a sensor HIGH): wrong readings at best, a damaged pin or module at worst, and it would only show up on the integrated board, never in the standalone test. Before copying a test pin, list every pin the main sketch configures (mics, buttons, motors) and pick one that is unused and safe: avoid strapping pins (0, 2, 5, 12, 15), flash pins (6-11), and input-only 34-39 if you need a pull resistor. GPIO4 was free here. Also set an explicit pull on a digital sensor input that can be unplugged (INPUT_PULLDOWN for an active-high module on GPIO4; GPIO34-39 have no internal pulls) so a floating pin reads idle, never a phantom 'pressed'. For hold-to-talk inputs add a firmware watchdog: report a forced release after a maximum hold (12 s here) and ignore the pad until it is really released, so a stuck sensor can never leave recording on. Verify by compiling the integrated sketch for the exact board (arduino-cli compile --fqbn esp32:esp32:esp32), which catches typos but not pin conflicts, so the pin-map check has to be done by reading.
