I’m having an issue with the automatic update Product tool. When updating a fleet of devices some of them will get stuck in an automatic update loop, as shown in the screenshot below.
In the screenshot you can see my device tries to update 4 times before I stop it by putting it in Development Mode. You can see in the screenshot that device OS is sending a version 3500 to the cloud (which is causing this automatic update to start) but my user application firmware also sends the version to the cloud, version 3501, which is the correct version.
If I put the device in development mode and wait 5 minutes to 5 days, the cloud will recognize my device is on the newer firmware, then I can take it out of development mode.
I’ve dealt with Particle support on the issue, and their response is to power cycle the device. Power cycling the device works, but isn’t really an option for remote devices. For remote devices I just leave them in development mode for a week, then move them back later.
I see this on around 5% of my devices in the field. So if I update 200 devices, I’ll have between 5 and 15 that I have to put in development mode. Not a huge problem, but definitely annoying to set myself a reminder to move a device back and forth between development mode.
I’m posting this to see if anyone else has the same issue and if anyone has a better way to solve the problem. I’m considering implement a method to power cycle devices remotely.
Other info – this has happened to me for about a year. I’ve experienced it on 0.6.1 + Electron all the way to 1.1.0rc-2 Boron.