New Blynk.Air is now in the Blynk.Console. It’s the new version of our over-the-air (OTA) firmware update service, built around fleets you set up once, rollouts that go out in stages, and a clear reason for every device that doesn’t update.
Below is what’s new, and what happens to the existing Shipments page.
You now create a Fleet once and ship to it as many times as you need. You can build a fleet from a device segment, one or more templates, a hand-picked list of up to 1,000 devices, or the All segment, which covers every device in your organization and its sub-organizations.
New devices join a fleet automatically as soon as they match. Units you manufacture later are in the fleet when they come online. You can also create a fleet before any matching devices exist.
You can edit a fleet’s target while a shipment is running. Devices you add are enrolled in the oldest active release. Removing devices doesn’t stop an update that has already reached them.
You can now split a fleet into 2 to 5 stages, for instance 10%, 30% and 60%. Blynk assigns devices to stages at random when the shipment starts and ships to stage 1 first.
The next stage opens only when the current one passes a gate you set. By default, at least 90% of the stage has to report success and the error rate has to be below 5%. If a stage doesn’t pass, the rollout stops and no more devices get that build. A banner shows the failure rate, with buttons to review that stage’s failed devices or resume. Full release skips the remaining gates.
To send the update to your test units or beta customers first, turn on Update tagged devices first and pick a tag. Stage 1 is then every device with that tag.
Shipping to everyone at once is still an option. Large fleets now get the update in batches of 1,000 online devices, a minute apart.
Each shipment page starts with counters for Updated, In progress, Pending and Failed, plus average update time and average attempts. Clicking one of the first four filters the device table, which also has search, status filters and sortable columns.
Failed devices now show what went wrong:
Devices the shipment hasn’t reached yet show as Pending if they’re connected and Offline if they’re not.
You set how long to wait after an update, from 1 minute to 7 days (60 minutes by default). A device that sends no data in that time is marked Not reporting, not counted as a success.
From each row you can exclude a device from the shipment or reset its attempts. Opening a device shows its update history by attempt, with each step timestamped.
Update conditions now include a firmware version range, for instance only devices from 1.2.0 to 1.4.7. That helps when a new build needs a minimum earlier version.
Local OTA lets the Blynk mobile app update a device during provisioning, before it connects to the cloud. It’s for devices that leave the factory with older firmware. It needs a shipment that targets a template or all devices, with a version-based condition.
For one-off updates on the bench, you can open a device, go to Developer Tools and drop a .bin file onto it.
The Reporting panel, in the shipment header, has three options:
A shipment that has reached every device it currently can shows as Awaiting devices. It stays live, so devices that match later are still picked up.
Until November 30, you can still create new shipments on the existing Shipments page, now Blynk.Air (Legacy). After that, the New shipment button will be disabled, and a notice will point you to the new Blynk.Air. Nothing is deleted.
Some things aren’t in this release. The staged-rollout gate already stops a stage that starts failing, but a breakdown of a rollout’s failures by reason, and an AI summary of a rollout, are still to come. We’re also planning anomaly detection, charts that show firmware versions across a fleet over time, and support for shipping files other than firmware, such as config files.
In the Blynk console, go to Developer Zone, then Blynk.Air (New). Create a fleet, add a firmware file, choose Rollout policy and press Start. Blynk.Air in the documentation.