Update: Upgrade any 1.2.1+ boards to 1.4.4 as a priority to avoid this critical bug
npm install -g particle-cli to get 1.53.0+ version of particle-cli and then particle update! More info:
** WARNING, particularly to commercial customers **
Friendly heads up to anyone like me who got tape and reels over the past few months and they came with 1.2.1 from factory.
If you upgrade from 1.2.1 (possibly others!) to 1.4.2 or 1.4.3 (the “latest and greatest”) and then supply wifi credentials that do not match the environment then it will red SOS.
particle identify; # validate 1.2.1, maybe others! particle update; particle identify; # validate 1.4.2 particle serial wifi --file yourwificredentialsthatdontmatchanything.json
This means if you provision at factory, then ship to a customer who does not have matching details, it will red SOS within 9 seconds of being turned on. Fun!
The team have been sitting on it for a fortnight: https://github.com/particle-iot/device-os/issues/1968
They should have been emailing and calling folk, but not even a fix as yet.
The way we’ve been remediating 500 units of ours is to run a wifi network matching our factory. We have a script watching the devices come online with a specific version that was used for this batch at the factory and then flash a new version (so that the script isn’t triggered again later on). We then call a cloud function that sits in the firmware that does a wifi.clearcredentials. About 25% of the boards don’t go online at all and require manual button pressing to clear creds, then we issue wifi creds over serial, and wait for it to do the prior process. Even worse is we’ve got about 40/500 that don’t even respond to serial anymore, for DFU or serial.
Hope you haven’t sold too many of those devices to folk for Black Friday…