Hi folks, so I'm experimenting with an ESP32 with WLED. A great piece of kit!
However, each time the Esp32 loses power, it then loses WiFi connection and won't reconnect to WiFi once power is regained.
I have to go through the installation process again to get things working. How do I enable the ESP32 to reconnect to WiFi automatically after power failure?
It can't be that good a kit if it can't reconnect. Every piece of ESP32 software I've used attempts to create WIFI connection at power up. Key word: "Attempts". Not all routers like constant logins. Not all software will keep trying when a router refuses. You should be able to create a serial port and log to see what the firmware is doing. Nothing to do with Hubitat.
Hi, yeah, I know this is nothing to do with Hubitat but I'm curious to see if anyone else has had the same issue and come up with a resolution. There are 1000s of Esp32 users out there, so I assume many can help.
Regards it being a great piece of kit, I mean that the functionality is great.
Do you have the source code for the firmware? Are there instructions for how to get a logging serial port? Do you have a link to the manufacturer or the github page?
Yes I've seen firmware that fail to reconnect (because I mistyped the password or the host name or the wifi network name) and the router who throttles too many connections from one device. And the mqtt broker who really hates two devices with the same ID
At this stage, I'm gonna take a punt and assume it's a poor ESP32 chip. I'll buy from a different supplier and hope for the best. The above suggestions are a bit out of my league in terms of my technical capability. @djh_wolf have you had any issues when your ESP32's lose and regain power. Any pointers?
No, but my esp32 is a little flaky. Been on my to do list for a while.
At the moment I'm not sure if it's a power issue (likely, since I'm powering 2 x nodes and 1x esp from a single 12v->5v brick), or if it's a dodgy chip.
All my nodes are fine. The esp32 is the only one I've had issues with. It's flashed with wled.
(to be clear, the issue I have is the chip seems to reboot occasionally, but reconnects fine)
I cannot help you with your problem but I have near 30 ESP32-based different devices and neither one exhibit any connectivity related problem. Since this is WLED make sure you have adequate power supply. It could be a significant voltage drop when LEDs are turning on resulting in the ESP32 reboot.
Hi, it doesn't drop off the WiFi when in use. It's just that when I pull the power, it then won't reconnect. Albeit this will be rare in the real world, it will happen on occasion when there's a power cut or I trip the RCD. I've ordered another chip so hopefully it'll be fine. I'll keep you posted on my steep learning curve.
I have 18 Pixelblase (it is very nice ESP32-based controller for the addressable LEDs with excellent HE driver). Overnight power for all 18 controllers is turned Off. They don't have any single problem reconnecting to the WiFi (router is Asus RT-AX88U plus two mesh nodes) when power is restored sometime at morning.
Something must be wrong with WLED firmware.
PS.
There are many more different devices based on ESP32 in my setup.
Neither one has a connectivity problems.
Hmmm yes. I have a new ESP controller from a different manufacturer. Same problem though! It's fine until I remove and reconnect power. The only way I can get it to reconnect to WiFi is by redownloading the WLED software onto the chip again and then starting from scratch. I'm surely missing something simple here, is there a manual way to attempt WIFI reconnection of the chip? How frustrating that I can't get an automatic reconnection upon power re-instatement.weird!
Sorry to here the problem is still persist.
I am not using WLED (my controller is PixelBlaze) but there are few active WLED users on this forum. Try to search forum for the "WLED", contact someone and ask specifically which WLED Image they are using.
I'm pleased to say that I've resolved the issue by creating reserving and IP on my router. This video gave me the information and understanding required. Thanks all and Merry Christmas