Good morning Travis,
I just had an interesting experience to share:
I un-commented your two lines of code related to PaperTrail, i.e. “// #include <papertrail.h” and “// PapertrailLogHandler paperpapertrailHandler(“logs7.papertrailapp.com”, 45358,“PumpStatus”);” and re-flashed the file to the Electron at the well. It flashed OK. But some time thereafter (maybe immediately; I wasn’t watching) that Electron lost connection to the Particle Cloud. The Electron flashed cyan continuously ever since until this AM (I was thinking that cell service simply sucked and I was waiting to see if things improved on their own).
This morning I decided to revert to the previous version of the app firmware in case there was something in the PaperTrail code that was responsible (maybe hogging the CPU). I couldn’t flash it over the air, of course, so I downloaded a binary version via Particle Build and flashed it to the board via USB. In the process, I got the responses you can see in the attached screenshot (note that I changed the file name). Although I had to ‘force’ the upload to the board, I was told that it was successful.
I then re-installed the Electron at the well and after a minute or two flashing green, the thing went into safe mode, implying that the app firmware would not run or otherwise wasn’t playing nice with the OS (Particle’s own firmware).
Since it was again reconnected to the cloud, I flashed the previous non-PaperTrail version of the app OTA from within Particle Build and now everything is again (finally) back to normal, stable operation.
Any idea what is in the PaperTrail code that hosed everything up?