My Electron enters this state where the LED is solid cyan, and the Electron is non-responsive. This only happens after I leave it my device on overnight - it’s working fine (breathing cyan) when I go to bed, and when I wake up it’s zombified (solid cyan). I can push the reset button, and everything goes back to normal, but I had to at least ask the question:
What the heck does solid cyan mean? Can’t find it anywhere in the docs or community.
Solid cyan is not an “official” state–it’s usually that the device locked up or stopped running firmware after some period of time. What firmware are you running on the device? Do you see any red colors from the RGB LED on the Electron?
If you’d be willing to post the code that’s running on the device, that’d be most helpful.
I’d understand if you decided that wading through this code is not worth it. But if you want more color on what we’re trying to do, feel free to shoot me an email: leo3 at linbeck dot com.
Actually, when I don’t use SYSTEM_THREAD(ENABLED), I have a different problem: I keep losing connection to the cloud and it stops execution while reconnecting. There are a number of situation where I have long-running tasks, and stopping execution to reconnect to the cloud is not a good thing. This problem went away when I enabled the system thread. I may keep the system thread for now - it runs just fine during the day, and I can simply restart each morning.
Ah, thanks so much for the link. Didn’t know that about the Electron and multithreading. The stack size issue now makes perfect sense - it’s the kind of problem you’d expect in this set of circumstances:
Problem emerges after running for a long time.
Big, complex user code.
Second-rate hacker (i.e. me).
I look forward to the 0.5.0 release with baited breath. All the best,