Slow webpage load and Home Assistant

[sco0ts]

Hardware

ESP32

Firmware version

v2.4.7

Application version

v2.4.7

What happened? What did you expect to happen?

I am using a ESP-WROOM-32 board. On initial install, the config webpage with reluctant to take my SSID. Re-flashed and was able to get it working. Now that I have my first blinds setup, the page is very slow to load. Sometimes it just fails.

Weirdly once you get it to respond after some time of not sending commands to the blinds, it will work very consistently.

Also, I setup Home Assistant and most times HA calling for the blinds open does not work. If it first move the blinds from web config, then HA, it works. Almost like we need to wake up the ESP.

Any way to make this more stable? Maybe a different ESP board?

Parts used: ESP: https://www.amazon.com/dp/B08D5ZD528 C1101: https://www.amazon.com/dp/B0D2TMTV5Z

How to reproduce it (step by step)

go to web interface

Logs

[jaarsa]

Avoid using GPIO12 for RX/GDO2 if you experience boot issues or sluggish performance.

Alternatives: Use GPIO4 (pin5 on the right-hand side), GPIO14 (pin5 on the left-hand side), or GPIO27 (pin6 on the left-hand side) instead.

See picture for pinout. https://m.media-amazon.com/images/I/51FzgrVl-cL.AC_SX466.jpg

You also need to correct the GPIO in your radio settings.

[G-eos]

Could you explain a little more, why changing GPIO will go faster ? I have a slow interface too and I use the GPIO12 (as defined in the wiki). As it is soldered I would love to have more info before changing HW :)

[jaarsa]

GPIO 12 can be a bit sensitive during startup on some ESP32 modules (it's used for bootstrapping). If you encounter issues during boot, consider moving GDO2 to another GPIO, such as GPIO 4, 14 or 27.

Bootstrapping refers to how the ESP32 reads certain GPIO pins during startup to determine low-level configurations—such as flash voltage, boot mode, and other system-level settings. These are known as strapping pins, and GPIO12 is one of the more sensitive ones. GPIO12 controls VDD_SDIO, which affects the voltage supplied to the flash memory. If GPIO12 is pulled high (3.3V) at boot, the ESP32 may incorrectly set the flash voltage to 1.8V, which can cause boot failures or read errors from flash.

If the ESP32 struggles to read from flash due to incorrect bootstrapping, it may result in:

• Slow startup or boot loops
• GUI loading issues (if the GUI is stored in flash)
• Unstable command execution, especially if commands rely on flash or SPI data

However, once the ESP32 boots correctly, GPIO12 typically won’t affect performance—unless it's misconfigured and causes instability.

Why GPIO14 Is a Smart Choice for GDO2

• Not a strapping pin, so it won’t interfere with boot.
• Supports interrupts, which is ideal for RX signaling.
• Freely usable in most ESP32 boards without side effects.

Hope this explains well why I recommend changing the last pin.

[G-eos]

Thanks a lot for this clear and detailed explanation.

[jaarsa]

@G-eos Did you manage to change the pin, and did it work out for you?

[G-eos]

Hi, do not have time so far !

[nigels0]

I’m finding that Safari loads extremely slowly while Chrome is much quicker