OTA not working about spark-server

[jlkalberer]

Try running node ./node_modules/spark-protocol/dist/scripts/update-firmware-binaries from the root folder.

I don't have a great idea why it's not working but that is a first step. I'll try debugging this tomorrow.

[lilyannh]

Tried running that script as instructed and still no luck. Here's the output when trying to OTA, might be more helpful than the previous dump (that one was just a snippet from the error logs). Thanks for looking into this.

On a side note, is there a folder where we can place a binary on the server that would automatically push out the firmware to connected devices - and would that work differently than flashing the firmware from the particle CLI?

flash device started! - sending api event { deviceID: '25001c001547343231323438'                                                                             }
fast ota enabled!  { cache_key: '_1', deviceID: '25001c001547343231323438' }
fast ota enabled!  { cache_key: '_1', deviceID: '25001c001547343231323438' }
fast ota enabled!  { cache_key: '_1', deviceID: '25001c001547343231323438' }
releasing flash ownership  { deviceID: '25001c001547343231323438' }
flash device failed! - sending api event { deviceID: '25001c001547343231323438',
  error:
   Error: Request timed out
       at Timeout._onTimeout (/root/node_modules/spark-server/node_modules/spark-protocol/dist/clients/Device.js:494:28)
       at ontimeout (timers.js:365:14)
       at tryOnTimeout (timers.js:237:5)
       at Timer.listOnTimeout (timers.js:207:5) }
::ffff:76.126.13.74 - - [22/May/2017:04:54:56 +0000] "PUT /v1/devices/25001c001547343231323438?access_token=xxxxxxx HTTP/1.1" 400 55 "-" "-"
(node:21936) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Request timed out
1 : Device disconnected: socket timeout { cache_key: '_1',
  deviceID: '25001c001547343231323438',
  duration: 84.408 }
Session ended for device with ID: 25001c001547343231323438 with connectionKey: _1

[lilyannh]

OK, maybe a false alarm. It's a little unclear exactly what the issue was because we had tried/changed so many things in the course of troubleshooting. But we think it was related to the last version of our firmware essentially bricking future updates, and potentially some weirdness with compiling the new firmware.

Thanks for your quick response!

[jlkalberer]

Yeah.. that's what the error looked like :)