Setup is the first thing your customer does with your product. The new provisioning flow tells them what's happening at each step, and gives you a record of every setup attempt in the console.
We put it into beta in August, and it's now live in the Blynk apps for iOS and Android. White-label apps built on Blynk get it with their next regular app update, and your account manager will get in touch about it. Update the app and add a device to try it.
Native pairing means fewer taps and fewer permission prompts. On iOS 18 and later, setup uses Apple's AccessorySetupKit, so discovery and pairing happen in a native system sheet. On Android, the system device picker handles selection.
The device tells the app what's happening. With BLE-assisted provisioning, the Bluetooth connection stays open for the whole setup, and the device reports each stage as it goes. When something goes wrong, the app says what: "Wrong Wi-Fi password" or "This network requires a login page." Your customer fixes it and carries on from that step instead of starting again.
Setting up several units goes faster. The app lists only Wi-Fi networks your device can actually join. Saved configurations and saved Wi-Fi credentials carry over from one device to the next, so installers don't re-enter the same details for each unit.
You can see every setup attempt. Provisioning Sessions in the Blynk web console (Developer Zone → Debugging) logs each attempt across your organization and sub-organizations. You get success rate, average duration and the most common error, split by iOS and Android, plus a step-by-step timeline for every session.
You don't need to update firmware to get the new app flow. The updated examples add the live status over BLE.
For the full walkthrough, with screenshots, the hardware table and the session timeline explained, read The new Blynk provisioning experience.
We'd like to hear how it works with your hardware and your customers. Share on our community forum, or, if you're on Enterprise plan, talk to your account manager.
If a setup fails, the Session ID is the most useful thing you can send. Turn on Developer Mode in your profile, and error screens on BLE-assisted devices show a Reason and a Session ID, so we can pull up that exact attempt with its full timeline.
.png)
