WLED turns ON itself from st-by on ESP8266 @ 0.15.0

Hi, I don’t know why, after abut 3-5 min from turnng off manually it starts on again itself. I’ve cheched on timers, all is disabled, apparently on LAN there are no other device that can turn it on, how can I debug that?
Thanks

check if its rebooting. if it is, may be a power issue.
check you have no buttons defined, especially touch.

1 Like

I’m not in front of ESP now to check, I’ll have a look. Does it has a log? I haven’t seen it, how can I know when last time it rebooted? I don’t thnk it’s am issue with power, it works nicely 24h without changing effect, aka reboot doesn’t occour when it’s working (else the default preset will be loaded and I’ll notice it). About bittons, I haven’t defined any, the ESP is new, I fleshed it from factory to 0.15.0 and just set the number of LEDs and some effects. What is touch?

What type is the ESP board? The cheap chinese evaluation boards do have the absolute minimum capacity at electrolytic capacitors. The 3,3V rail should have 330 or 470 µF short as possible from ESP “stamp-module”.
Wmos D1 mini with 10µF is a bad joke. Enough for short demonstrations, but to poor for a serious job. :wink:

1 Like

if it is not rebooting (i.e. not showing the bootup preset) but turns back on to the previous state, it must have received a command to do so. the code does not randomly decide to do that. So options are that buttons turn it on (check you have all buttons set to disabled), touch is touch buttons, but not available on 8266 (I missed that bit). there is also options to load presets on a predefined time. if it is non of that, you can install a DEBUG version and monitor the serial output for information.

1 Like

Thank you mates, in the evening I’ll make test, I’ll watch if it will turn on with latest effect or the boot one, I’ll disable the NTP and see it it can help
Yes it’s a cheap chinese Wemos mini powered with 5V (so I take advance of the internal regulator to 3,3v), but I have one at home for long time, and never suffered such problem (with previous versions). Thanks for saying it, I’ll add a 330uF 10v right on the +3,3v pin

Hi mates, I can’t find the post that indicated the NTP client problem, I’ve disabled it and the 8266 keeps OFF as it should.
In my opinion the problem is located on new version 0.15.0, and it’s not related to power issues, or poor chinese board. Can somebody advice please the author? How can I notify him about that? Thanks

check if there is an issue (open or closed) about it open on github, open one if there is not and provide details on how to reproduce it, posting error-logs is also helpful.

ok, thanks. SInce bug was reported here but I can’t find it open I’ve asked about that. Eventually I’ll open it

I’ve made some tests, zthe LED turn on even if NTP is unselected, and it start witha reboot (the boot preset is chosen). Activate NTP just reduces the time on the next turn on/reboot, it can be only one minute if selected and offset time is set high. In my opinion the but is on the offline part of the program, somehow a mistake happens and it reboots.
I also noticed that if I unselect the scedules (I’ve never touched/set them) on the next reboot they are selected again, why?
I would add, chosing the time zone between CEEST and EEST is complicated and has no sense in my opinion, I don’t know what they are and I can’t find my time zone which is GMT+3h, so I leave GMT and I add 10800seconds, but it’ not that smart. Why don’t you indicate here just offset hours instead of those labels?
Thank you

I can not reproduce your issue, everything works as intended, so you’d need to post more details on your setup, like I said before. config file(s), board type, chip revision, connected peripherals etc.

the schedules are selected because if you set it to preset zero it is already disabled and I am guessing a disabled state is not saved explicitly to not waste memory.

CEEST and EEST are international standards for time zones and are well defined.

Unfortunately there is not +3 GMT on the list, I can get it only with time offset. I really suggest you to improve this time list, and give classical -12 … +12 offset, then you can add labels if you like. Most of people doesn’t know these labels, sorry

It is Wemos D1 mini Type-C ESP-8266EX, maybe it has a different bootloader than yours? I?ve connected 4 leds WS2812B on default D4, nothing special.
I may try to upload an old wled version and test if the problem still
When I’ll flash I’ll try to get the data of the board

when you flash, make sure to use the official web installer.

the time zones are well known and easy to look up. they are not the same as UTC+3 as they also do automatic summertime/wintertime adjustment. if your country does not use any of the time zones, you have the option to do as you did.

about web installer, you mean the Wled web interface OTA update? And can I install 15.0 over 15.0 now?
To install from virgin Wemos I used ESPHome-Flasher-1.4.0-Windows-x64, can it be this the cause?

very highly likely. use https://install.wled.me/

Hi mate, I confirm you flashing with web installer did the job, thank you for assisting me!
For who get in the same trouble I say you need to backup config and presets before, you may flash the same version with web installer using Chrome browser.

For the staff I would recomend to help users adding a line on the download page “please use web installer available at https://install.wled.me/ as other flashers will not guarantee proper functioning”, I haven’t read it and I’ve lost time to understand a so simple important thing.

glad you found a solution.
when following the official guide, this is all documented:
https://kno.wled.ge/basics/install-binary/

where exactly would you like to add this info?


I would recomend you to make it visible here :slight_smile:

I forgot to ask, on time schedule ho can I defined “show nothing” or “go back on st-by”? Should I select preset 0?
Thanks