pm open, type:0 0 error on NodeMCU board about esp8266-fastled-iot-webserver

[NimmLor]

A friend of mine has noticed this issue too, I'll have to look into it what causes that issue.

[WarDrake]

I haven't figured out what causes the error, but I figured out the crash and random restart issue, it seems they are unrelated

Line 20 :
#define FASTLED_ALLOW_INTERRUPTS 0

if that line is commented out, the pm message shows on the console, but it doesn't affect the system, the nanoleafs have been working flawlessly for 24 hours now.

[NimmLor]

Ok that's weird, without the FASTLED_ALLOW_INTERRUPTS 0 some older LED-Strips flicker and glitch insane. That line fixed all glitching issues for a friend of mine.

[NimmLor]

I've searched a bit and found that it might be crash because the sdk doesn't get enough cpu time. The FASTLED_ALLOW_INTERRUPTS 0 blocks the wifi handling when the LEDs are controlled by the FastLED library.

A possible fix could be to decrease the value of the FRAMES_PER_SECOND variable, this would lead to a larger delays when updating the patterns.

[WarDrake]

Been playing around with the library today

//Serial.setDebugOutput(true);

This removed the pm error, I am not sending it on a pull request because I'm not sure if the visualizer uses it in some way.

but the pm message itself is no longer showing up once this line is commented, leading to no reboots either.

[WarDrake]

This is solved on the newest builds as long as you comment line 20.