Web page hangs after install

[MainWire]

Hardware

ESP32-C3

Firmware version

v2.4.6

Application version

v2.4.6

What happened? What did you expect to happen?

I installed the binary file the first time on my esp32C3, it worked and I set my wifi credentials. There I was stuck because it would connect to the wifi but wouldn't let me access the UI after saving my credentials. Then I reflashed it, and now it won't work anymore, the webui hangs when connected to the AP, and doesn't show up any informations. I'm using ESPhome.IO to flash it. I tried erasing the flash with vscode but it still doesn't work. Haven't found another issue on this, any thoughts on that ?

Thanks in advance.

How to reproduce it (step by step)

1. Install firmware with esphome
2. Attempt to reach the IP address given in the docs
3. the UI hangs and never finishes loading

Logs

[sitexw]

Hi,

I’m running an ESP32-S3-Zero (dual-core, 512 KB SRAM, 2 MB PSRAM, 4 MB Flash), and the project works for me at first. However, after a few uses (opening/closing shutters several times), the interface eventually crashes and the ESP restarts. So it’s not exactly the same as your case (mine works at the beginning), but it really reminded me of what you’re experiencing.

I also noticed that the web interface loading can be problematic, especially because the JavaScript file is quite large. When I load that file locally (from my PC instead of from the ESP), it works better. But even then, after a while, I still get crashes. This makes me wonder if the issue could be related to available memory (SRAM/PSRAM).

So I’m curious: 👉 Could you share the exact ESP32-C3 model you’re using (with reference if possible), and how much memory it has (Flash, RAM/PSRAM)? That would help compare our setups and see if this is a hardware limitation or something else.

Thanks!

---

PS: I’m a web developer by background, and I was thinking it might be useful to open a small PR that would:

• compress the JavaScript file (it’s currently uncompressed, so that would reduce its size),
• and maybe add an option to load the assets either from the ESP itself (like today) or directly from an external source (e.g. a GitHub RAW link).

That way the ESP wouldn’t have to serve such a big file, saving RAM and making things more stable. Not sure if others would find this helpful, but I’m putting the idea out here.