I have a fairly simple app that has been running for a few days now. I left it running to monitor the cloud overhead while it was idle (not sending any data via web hooks). Today I added a bit of code (using VS Code) to disconnect from the cloud when there was a long idle period. Two things were observed. First, VS code can’t find the device (for local flash) even though the serial port hasn’t changed and the Boron has continued to log heartbeat messages to the serial monitor. Second, when I use Particle identify I get the message “Your device id is undefined”. The Boron and the serial monitor and VS Code have all been running unchanged from a few days ago. The message from VS Code:
_dfu-util: No DFU capable USB device available
make: *** [program-dfu] Error 74
make: *** [modules/boron/user-part] Error 2
make: *** [flash-user] Error 2
… and yet the Boron continues to execute its application code and log info correctly to the same serial port. Why would a device that has been and remains operational have an undefined device ID? How can I get it back, but as importantly, why would VS Code (with Particle WB) now decide that it can’t find the device?