Critical Reliability Issues on ESP32S3 (OV5640, v10.8.4): Failover AP Mode & Software Reboot

[immortal0963]

​Dear s60sc,
​Thank you for developing this excellent project.
​I am using your application on a high-performance setup: an ESP32S3 camera board (with an OV5640 sensor) running firmware v10.8.4. I have encountered two critical issues related to connection reliability and device management, which are particularly relevant in regions with unstable power supply (Ukraine).

​1. Failure to Automatically Switch to Access Point (AP) Mode (Failover Logic)
​In my scenario, the home Wi-Fi router often loses power. The camera fails to reliably switch to or maintain its local Access Point (AP) mode for local access.

​Configuration: The "Allow simultaneous AP" option is enabled on the Network tab.

​Expected Behavior: The camera's own Access Point (ESP-CAM_MJPEG...) should remain active or become active upon losing connection to the main router, allowing access via 192.168.4.1.

​Actual Behavior: After the router is powered down or after the camera loses connection, the camera's AP does not become available. The device appears to be stuck in a continuous reconnection loop (STA Mode) without activating the fallback AP, even with Allow simultaneous AP enabled.

​Workaround: Access is only restored after a physical power cycle (Hard Reset) of the camera.

​Request: Since Allow simultaneous AP is not guaranteeing reliable access via 192.168.4.1 when the router is down, could you advise on:
a) Any hidden parameter or code logic that could be adjusted to force the device into AP Mode if it fails to connect to the STA network within the time specified by "Wifi connect timeout (secs)"?
b) Whether this is a known issue with the implementation of the Allow simultaneous AP feature on the ESP32S3 specifically.

​2. Stability Issues with Software Reboot
​After making and saving configuration changes in the web interface (e.g., on the Motion or Other tabs), I use the mandatory "Reboot ESP" button.

​Problem: The device frequently fails to initialize correctly after a software reboot. Neither the STA client nor the AP Mode activates, rendering the camera completely unreachable on the network. The device is likely experiencing an initialization error upon restart (possibly related to PSRAM or the network stack).

​Workaround: The only way to restore function is by performing a physical power cycle (Hard Reset).
​Request: Is this software reboot instability a known issue with the ESP32S3 / v10.8.4 combination? Are there any recommendations regarding the ESP32 Core version or specific code changes to ensure a stable software restart?

​Hardware: ESP32S3 (with OV5640)
Firmware Version: v10.8.4

​Thank you for your time and continued support.

[s60sc]

Provide the startup log.
It is an environmental rather than software issue.
The AP operates independently of STA.
ESP hardware needs a stable voltage.

[immortal0963]

Dear s60sc,

Thank you for your guidance.

We are acting on your assessment regarding the need for stable voltage. To clarify the power setup, we are using a UPS module powered by two 18650 batteries (5V/3A output), which constantly charges when grid power is available. This means the ESP32S3 is powered by the module's boost converter, making voltage stability the central focus of our troubleshooting, as you suggested.

Updates on Log Analysis:
The provided log was obtained AFTER the device had already crashed/become unavailable (after ~2 days of operation) and was physically power-cycled to regain access. The log successfully showed correct software behavior upon successful startup, but as you noted, it did not capture the crash itself, reinforcing the likelihood of a hard, unlogged failure (hardware/power related).

Our Immediate Action Plan (Hardware Focus):

1. Adding a Capacitor: We will immediately implement voltage stabilization by adding a large electrolytic capacitor (approximately mf470 or mf1000) in parallel to the 5V/GND lines of the ESP32S3 power input. This is intended to mitigate potential voltage issues originating from the UPS boost converter.
2. Rethinking Logging: We will monitor the device until the next crash and attempt to retrieve the serial log right at the moment of the unresponsive state to see if the system manages to log any error before the hard crash.

Requests for Further Assistance:

While we implement the hardware fix, we would appreciate your expert advice on two additional points:

1. Power Supply Recommendations: Do you have specific recommendations for the most stable power supply solution for the ESP32S3 (considering the high current draw of the OV5640 and PSRAM)? We want to ensure we are using the best possible approach.
2. Software Motion Detection Tuning: We are struggling to get reliable performance from the built-in Software Motion Detection. The sensitivity appears inconsistent, and overall detection quality is low. Do you have any recommended starting values for the following parameters on the Motion tab to improve detection quality.

Thank you for your ongoing support. We will update the thread after completing the hardware stabilization and power cycle testing.

log.txt This log does not show any problems related to my issue.

[s60sc]

The device will report brownout on voltage drop but cannot log anything for voltage loss so not point in monitoring for this.
I cannot advise on your power supply it depends entirely on your specific setup, however a large capacitor in the right place should buffer the switching between UPS and grid.
The default motion settings work for most people. Use the Show Motion feature to see how movement is being detected for different settings in your environment.

[immortal0963]

Thanks for replying.
As for the power supply, I will try to fix something, because I would like to use the camera as a surveillance camera in the house, but so that it works when there is no light.
As for Show Motion, I changed various parameters to improve motion detection, but it got even worse. Turn on the stream and see how the detection takes place and whether the recording starts. In most cases, the recording did not start. For me, it is very important that the reaction is from the slightest movement on the screen.
Is it possible to use machine learning?

[s60sc]

making motion detection too sensitive will make it react to camera noise
machine learning is for detecting particular objects, eg people rather than pets
there is a limit to how much a little $5 esp can do

[chizz6-sk]

2. Software Motion Detection

Maybe try connecting a motion sensor?

Our Immediate Action Plan (Hardware Focus):
or

https://aliexpress.ru/item/1005005972076659.html

[immortal0963]

Hello. I agree about the cost and capabilities, but nothing has been established except for detection and telegrams. Well, we will continue to improve your project. By the way, it would be cool if there was a camera access program.

[immortal0963]

As for the motion sensor, I really plan to install it and see how it will work. Thank you for the advice))

[chizz6-sk]

It looks like there's a problem reconnecting the ESP32 after a router power failure.
I had a similar problem. Both the router and the ESP32 were powered off. After the ESP32 S3 recovered, it wouldn't connect to the network.
I set up remote access via KeenDNS - Keenetic. I read this post and decided to install a battery
https://aliexpress.ru/item/1005005972076659.html
into the Esp32 power supply. I ran a quick test, turned everything on, then turned the router off and on again, but the connection to the Esp32 wasn't restored.

Unfortunately, I only have one ESP32 S3 board that works fast, but it doesn't have pinout GND, 3.3v GPIO markings to connect the battery. While I was setting up the other boards, time ran out and I had to go back. I didn't finish the full tests.

[chizz6-sk]

It looks like there's a problem reconnecting the ESP32 after a router power failure.

Everything's fine. When the router's power fails, the watchdog restores the connection. My apologies.