I would like to know if anybody has experience similar to the following.
I ““upgraded”” one of my remote sites (2.5 hour drive both ways) last week with a v2.0.0-rc1 Boron.
I have already highlighted the stupidity of this choice, being that Particle has ruined the Boron’s cellular reconnection stability sometime after 1.3.1-rc1, in this post:
But this is different and even worse. Instead of finding flashing-green Boron, I found a DEAD Boron with no light at all.
However, with a power cycle, it rebooted and flashed green.
The code was tested for weeks at my house in good cellular. The software watchdog was also in use.
The power supply was +5V into VUSB. I know there were no supply issues because my Teensy 3.5 was working just fine on the same board.
Why did this happen?
Why is Particle’s flagship product habitually so fragile, sensitive, and unpredictable as to whether it will work or not?
Does anybody have any ideas how the Boron could randomly go dead, but then reboot after a power cycle?