ESP32-S3 Randomly Rebooting During WiFi and Sensor Activity

[jovelyngentallan02]

Hello everyone,

I'm currently developing an ESP32-S3 based monitoring device that collects sensor data, displays status information locally, and periodically uploads readings over WiFi.

The prototype works well most of the time, but during extended testing I'm occasionally seeing unexpected reboots. Sometimes the device runs for days without issues, while other times it may restart several times within a few hours.

Current setup:

* ESP32-S3
* WiFi connectivity
* Multiple I2C sensors
* Small OLED display
* External 12V power supply with onboard regulation
* Data logging and MQTT communication

The symptoms include:

* Unexpected resets during network activity
* Occasional watchdog messages
* Rare sensor communication failures before reboot
* No obvious hardware faults found so far

I've checked memory usage, power supply stability, and task timing, but I'm still trying to determine whether the issue is software-related, EMI-related, or something else.

A few questions for those with ESP32 experience:

1. Have you encountered intermittent reboot issues that only appear after long periods of operation?
2. Are there common ESP32-S3 pitfalls related to WiFi, MQTT, or I2C devices?
3. How do you typically diagnose problems that are difficult to reproduce consistently?
4. Have you found hardware design issues to be a common cause of random resets?

PCB Design Question:

The current prototype is built from development hardware, but I'm preparing a custom PCB revision that integrates the ESP32-S3, power management circuitry, and sensor interfaces. The board will likely be manufactured through PCBWay.

For those who have taken ESP32 designs into production:

* What PCB layout practices have had the biggest impact on stability?
* How important is RF layout compared to power supply design?
* Is additional ESD protection worthwhile for sensor and communication interfaces?
* Which PCB fabrication or testing options have provided the best reliability improvements?

Power Plug Connector Question:

The final product will be powered from an external 12V supply, and I'm currently evaluating different power plug connector options for reliability and ease of installation.

For those deploying ESP32-based products:

* What power plug connector types have worked best in real-world installations?
* Have you experienced failures due to loose barrel connectors or poor power connections?
* Do you prefer locking connectors for field-installed devices?
* How much consideration do you give to connector current rating versus mechanical retention?

Mechanical Enclosure Question:

The electronics will eventually be housed in a custom enclosure with provisions for connectors, cable routing, and service access.

I'm considering CNC-machined and rapid-prototyped enclosure options through JustWay.

For those who have moved ESP32 projects from prototype to production:

* What enclosure design mistakes caused the most rework?
* How much clearance do you typically allow around power connectors and cable entry points?
* Have thermal issues become a concern once the electronics were enclosed?
* Any recommendations regarding materials, mounting methods, or long-term serviceability?

I'd appreciate hearing from anyone who has taken ESP32-based products from bench prototypes into real-world deployments.

[MicroController]

3. How do you typically diagnose problems that are difficult to reproduce consistently?

Capture the log output around the time of the unexpected reboot, ideally multiple times. Check if you can determine the issue from that. If not, post the logs here.

Stable power supply is of course essential, including during quick current spikes; buck converters may need more output caps for a smooth ride.