Well, less of chance of software issue but not eliminated.
You don’t by any chance have overlapping segments in your presets, 2 different segments referring to the same LED(s)?
If you happen to have them linked to Home Assistant that has been known to poll the controller too frequently and cause it to reboot.
How did you update the firmware? From 13.x to anything 14 or 15 it would be best to update over the USB port vs OTA.
Future reference for the others that have this topic going in 2 directions. please in the future make your own topic as it gets confusing.
I don’t have Home Assistant, I do have a Homey Pro Hub. I did add them to my hub but I deleted the any connection between the two to see if that would solve my problems. No luck
I’m talking about segment definitions that you may have for use with presets, etc.
Do you have any buttons defined?
How about anything in Time&Macros?
In the first Controller i have only 10 LEDs no presets no buttons no time¯os.
So i flashed a another ESP32 with WLED tha same way i have been flashing the other ones and i did not add it to my wifi and so far that one hasn’t had any reboots, so far the “uptime” on that one has been way more than the ones i have in my wifi network. Could I possibly have some settings in my router conflicting with the ESP32? I have a Atlas Max 6E mesh system.
Interesting, does that router handle 5G/6G as well as 2.4G?
Might be worthwhile to try and disable handover/autonetwork switching functions in the router and/or setup a static IP address for your ESP’s.
Worst case scenario, get another basic AP router for your IOT devices and dedicate a simple WiFi network for them. Should be pretty simple to allow access from your “main” WiFi net to the IOT devices.
That way the IOT devices can have a “clean” WiFi net of their own.
Ok so far i have tried these steps and so far nothing seems to help.
-Static ip address for devices
-Remove wled integration from Homey Hub
-Turned off wifi router client steering
-Split 2g 5g 6g bands
Any other ideas? I tried turning on the guest wifi and adding the ESP32 to it, the down side on that is that i have to constantly switch wifi to control my smart home and the ESP32. Thanks for the help by the way really appreciate it.
Hi i got 25 displays in use all 100t o 150 WS2811 eatch display is full on WEMOS D1 board powerd by usb or 12V the ESP8266 flashed with WLED 14.b2
never got any reboot at all only on programming as they loose WIFI at SAVE offen i had to Reload to se new preset but as it is programmed it never faild even in very hard envirerments -10Celsus and storm
in a shielded box
SET some presets like chase male a playlist and set this to trhe startup
I’m not familiar with your particular router (and/or Homey Hub, home network setup, etc.) but I can pass on what I’ve gleaned from other setups using WLED.
The WiFi implementation in WLED is operational and very useful for configuring the device.
That said, compared to what many of us are used to from our phones, TV’s, sound boxes, play stations, etc, it is a web page built into a very basic physical device with limited memory and CPU resources.
You’ll find the developers do a fantastic job of shoehorning all the effects and capabilities into these tiny devices, but in the end “something’s gotta give”.
Part of that is the error/overloaded/retry portions of the Web interface code. There have been a number of people who have reported reboots/odd behaviour from Home Assistant connects as it tends to poll the WLED devices too frequently and causes crashes. The solutions to date have been disconnect from HA or try and find a simpler interface.
In your setup I’m getting the impression of a more fully fledged Home Automation setup (Homey Hub?).
It’s very possible that WLED won’t react well to some or all of the pieces you have co-existing, especially a modern self-repairing mesh WiFi network.
That’s sort of what I was implying by suggestion you get a dedicated cheap AP just for the WLED devices. You should be able to put them on their own WiFi subnet, physically wire that AP to the main router and setup the main router to handle traffic to and from your usual subnet to the WLED subnet.
That will get your WLED devices on their own subnet and reduce “noise” traffic that they see to almost nothing. I know it sounds like a bunch of hassle, but it’s a very common network problem and almost any modern device will have tools to deal with this type of issue.
Given your comment about using the guest WiFi to remedy your problems, you might be able to use that as well if you can get your main AP to route traffic to/from that subnet.
So I was able to fix my issue, kinda. I figured it had to do something with my wifi since the ESP32 that i have not connected to my wifi has not been having any rebooting issues. So since one of your suggestions was to just set up a connection just for the ESPs, I went and i purchased a new mesh router that has a dedicated IOT channel and a guest channel. The difference between the two is that the IOT channel keeps my smart home devices separated but i can still manage them without having to switch WIFIs. So far i have had no reboots and uptimes on my devices have been far more than with the other one. Its not a clear solution but im no longer having this issues.
Glad you managed to get things under control.
As I mentioned, I’m not shocked that the ESP devices might not be as robust in a “dynamic” mesh WiFi network.
Hopefully the segregation will allow you to manage things a little more reliably.
Are you using WLED Native on your phone? When I downloaded it I had the same problem start. I got suspicious and quit using it and force-closed it days ago. No problems since.
ROLSTARX is your ESP32 working better still? Not cycling
Hi @Rokstarx
I am having exactly the same issue as you. I have 3 controllers, and all reboot (randomly) at the same time.
I deduced it had to be something to do with my wifi, and found this thread.
Were you able to find out any more about what was causing your issue? A device conflict? Or anything like that?
I saw your solution, but I don’t have that option on my router settings, so trying to get to the bottom of what the underlying issue is.
Thanks
They were working right for a while, but after a storm my power went out and they are back doing the same.