I’ve been having issues with my controller (ESP32 Mini) rebooting randomly. It’s running WLED 0.15.1 from the web installer. So far I’ve tried moving it to another access point running in 2.4Ghz only mode, and then I tried plugging it into USB without anything else connected. Changing the wi-fi was ineffective, and the USB test only got it to last a few hours at the most before rebooting. I don’t have it connected to HA yet but I did add it to Hubitat via the joyfulhouse driver. Do you think Hubitat has the same issue as HA? Would it be better to just send HTTP commands instead of using a driver? Do you think I have a bad controller? Is there something else that could be causing this? Thanks in advance!
So I disabled the Hubitat integration and it has stayed up for about 9 hours now which is the longest I’ve seen since I noticed the problem. I will leave it over night to see if any more reboots happen and report back. Hopefully it was just the Hubitat driver. I don’t mind just using HTTP commands for my automation.
After hooking the ESP32 back up to the LEDs with the Hubitat integration disabled, it’s been up and running for more than 27 hours so far without any reboots. Looks like HTTP commands are the way to go for using WLED with Hubitat.
How are you powering the device? I don’t know anything about this driver but it’s possible that it’s really power inefficient and spiking a hard current pulse when different actions line up every few hours that’s sagging the voltage line and browning the device out.
From your update it seems more like a bug in the driver, but for the future it’s worth making sure the ESP32 is powered with something that can supply more than 500mA because it can have crazy current spikes with doing high power stuff like wifi or bluetooth while also utilising the main core heavily.
If you really want to look into it, you could recompile WLED and flash it with the fault behavior as “gdb-stub” instead of reboot, and it’ll drop you into a debugger to see what’s going on.
I have a update able box that just closes when I try to update the firmware… it’s hard to update if its trying to download an update from the device it’s trying to update…
When fully hooked up, it is being powered by a Mean Well RS-25-5, which is also powering the LEDs. When I was testing to try to narrow down where the problem was, I used an Anker 20W USB charger and had the EPS32 disconnected from everything else. The problem was definitely the Hubitat driver or something to do with Hubitat. As soon as I disabled the driver, the reboot problem went away. I am now using HTTP commands to control WLED from Hubitat instead, which has been working great so far.
1 Like