So my firmware runs great for long periods of time, then the logs show some anomalies, then it locks up completely with a solid orange LED. Here the sequence I saw today,,,
|particle/device/updates/forced|false|SPP_000001|3/6/20 at 12:30:50 am|
|particle/device/updates/enabled|true|SPP_000001|3/6/20 at 12:30:50 am|
|spark/status|online|SPP_000001|3/6/20 at 12:30:50 am|
Then it recovers. Then a couple hours later....
|spark/device/diagnostics/update|{"device":{"system":{"uptime":18,"memory":{"total":82944,"used":42984}},"network":{"connection":{"status":4,"error":0,"disconnects":0,"attempts":1,"disconnect":0},"signal":{"rssi":-62,"strength":76,"quality":67.74,"qualityv":30,"at":1,"strengthv":-62}},"cloud":{"connection":{"status":1,"error":0,"attempts":1,"disconnect":0},"disconnects":0,"publish":{"rate_limited":0},"coap":{"unack":0}}},"service":{"device":{"status":"ok"},"coap":{"round_trip":158},"cloud":{"uptime":0,"publish":{"sent":2}}}}|SPP_000001|3/6/20 at 1:58:52 am|
|spark/device/last_reset|power_down|SPP_000001|3/6/20 at 1:58:52 am|
|particle/device/updates/forced|false|SPP_000001|3/6/20 at 1:58:52 am|
|particle/device/updates/enabled|true|SPP_000001|3/6/20 at 1:58:52 am|
|spark/status|online|SPP_000001|3/6/20 at 1:58:52 am|
then it recovers again and goes along fine for 5 hours, then fails again....
|spark/status|offline|SPP_000001|3/6/20 at 7:07:24 am|
... this failure locks up the device with a solid amber LED. The documentation only mentions orange here
While connecting to the Cloud, the RGB LED will be blinking cyan followed by:
1 orange blink: Decryption error.
2 orange blinks: Could not reach the internet.
3 orange blinks: Connected to the internet, but could not reach the Particle Device Cloud. This sometimes is seen as yellow or red and indicates bad server keys.
Then later it says...
In most cases, solid colors are the side effect of a bug. If code crashes or infinitely loops with interrupts disabled, it's possible that the LED animation will stop. The color of the LED is the color it last was before failure.
So how do I go about troubleshooting this? Seems like it could be just about anything.
Bob