pcdiks
commented
6 years ago Happens to me too, it works fine for a couple of minutes and then it crashes and becomes not responsive. I have to powercycle it to come back online.
Closed xBiohazardx closed 6 years ago
pcdiks
commented
6 years ago Happens to me too, it works fine for a couple of minutes and then it crashes and becomes not responsive. I have to powercycle it to come back online.
ddtmax
commented
6 years ago unfortunately it happens to me too, after 2 minutes with some effects
nickboucher
commented
6 years ago This happens to me too -- I have a suspicion that the culprit is how FastLED interacts with the architecture of the NodeMCU as discussed in #60. I will be testing in a week and will report back if any of the proposed fixes in that thread work.
Also, for reference, I believe the issue being discussed in #73 is the same as this thread.
xBiohazardx
commented
6 years ago It seems that changing the line "FastLed.delay(1000 / TransitionTime);" in function show Leds, to just "delay(1000 / TansitionTime);" fixed this issue for me.
bacumings
commented
6 years ago Curious how many total LEDs you guys have connected? I am having similar issues and just discovered that there are several places in the code that use 8-bit functions on the NUM_LEDS variable. I have three connected strips with a total of 272 addressable LEDs and am wondering if this isn't causing issues.
xBiohazardx
commented
6 years ago I have got 60 of them connected. But my issue on two of my strips i got a loose connection. (I am a very good engineer xD) sry for the late answer I am closing the issue if you still need help please open another one.
Hello there, This code is pretty awsome, but as mentioned before my node mcu crashes after a few minutes. After crashing it restarts and is available in the network (pingable), but doesn't react to the mqtt messages. After pressing the reset button everything works fine for about 5 minutes again. Thanks for your help.