I have a couple monitor ones in the field and when I try to send an OTA code update, it will say started and then failed every time. I tried 3 different devices and the same thing happened. The cell connection is poor which is probably the problem. I am using the particle workbench and tried the Cloud Flash, and the command line with a firmware.bin (particle cloud flash e00fce6852547435dab04f80 firmware.bin --product 44011). Any suggestions?
I can't tell for sure, but I can see where OTA was attempted, and failed. The logs are typical in situations where there is poor connectivity, but I can't say for sure if that was the cause.
Is there a way to que the update so it waits until it has a better connection and then tries to update the software?
If you upload the firmware to your product from the console and lock that device to the version it will retry a number of times to flash. This is how you normally flash a device that is currently offline. It's not really intended to help with low signal, but it may help.
@jzalar to Rick's point, uploading the firmware to the console and releasing to the product is the preferred method of sending OTAs to devices as it has built in retry mechanisms. The cloud flash is designed for development purposes not for fleet wide OTAs.