Disclaimer

All tutorials on ESP32 Engine are provided for educational and informational purposes only. They are intended to help learners understand ESP32 wiring, code structure, sensor readings, displays, and simple automation patterns.

Electronics projects involve risk. Always verify wiring, use appropriate power supplies, unplug USB before moving jumper wires, and check the exact datasheet or module label for the board you are using. A diagram or wiring table on this site is a learning aid, not a certification that a build is safe for unattended or production use.

Low-voltage learning scope

Most ESP32 tutorials are designed around USB power or regulated low-voltage bench supplies. ESP32 GPIO pins are 3.3 V logic pins and are not 5 V tolerant. Use level shifting, drivers, fuses, enclosures, and separate power where the project requires motors, pumps, LED strips, servos, relays, or other higher-current loads.

Mains, relays, and high-current loads

ESP32 Engine does not provide instructions for unsafe mains wiring. Relay and AC projects are educational control examples only; mains wiring must be handled by qualified adults using correctly rated modules, isolation, strain relief, enclosures, fusing, and local electrical-code compliance. Do not connect exposed mains wiring on a breadboard.

Sensors, calibration, and readings

Sensor values are affected by module quality, placement, noise, supply voltage, calibration, and environment. Thresholds shown in tutorials are starting points for classroom or bench testing. Verify readings with known references before using any project for decisions about irrigation, alarms, safety, air quality, health, or power usage.

Healthcare and life-safety limits

Healthcare projects: Tutorials in the Healthcare category are not medical advice and must not be used for diagnosis, treatment, patient monitoring, or emergency response. Fire, gas, leak, security, and alarm projects are not certified life-safety systems and should not replace commercial detectors or professional installations.

Code and adaptation responsibility

Code samples are starting points. You are responsible for testing and adapting firmware for your exact hardware and use case. See our Testing Methodology, Editorial Policy, and Contact page for how tutorials are prepared and how to report a correction.