I haven’t used any ESP32 gateways for longer time periods until now as I did not had a stable build (all gateways and sensors that I have are based on ESP8266 or Arduino).
However, I didn’t use WifiManager with any of the ESP8266 and this was the sole modification I’ve initially done also for the ESP32 gateway (in order not to have to keep the wifi password on hand after flashing but rather pasting it directly into the sketch).
This morning I’ve disabled manual setup however did not uncommented CleanFS (so that I won’t need to manually input the wifi password). The next step would have been to try to disable multicore but I think there is no need for that since the board works fine now (connected to a 5V USB charger).
The good news is that I’ve checked the LWT topic and it appears there haven’t been any restart since morning…
Maybe ESP32 doesn’t like wifi manual connection after all?
I’ve checked the power meter yesterday and it was constantly indicating 0.11-0.12 A when the board wasn’t working anymore, although the wireless chipset was nearly cold (haven’t looked in the router log in order to see if it was still online and now the log is cleared ).
When working fine there was 0.02 - 0.04 A current draw in normal load and 0.11 - 0.12 A when sending data to MQTT so I think it was trying to reconnect to wifi and kept failing (I think this is consistent with the fact that the current IP lease for ESP32 is active since building it this morning without any downtime and current draw is as observed initially).
I’ll let you know of any development.