Hey everyone,
We’ve been working on a big update to device provisioning, and it’s ready for testing. It’s faster, the setup flow is clearer, and it gives you a lot more insight into what’s happening on the device while it connects.
We’d love your help putting it through its paces before it goes out to everyone.
What’s new
-
A reworked setup flow. Permissions are requested up front and device search starts when you tap “Find Devices,” so the preparation instructions get your full attention. iOS 18+ uses Apple’s native AccessorySetupKit for pairing, Android uses the system device picker. Only Wi-Fi networks your device can actually join are listed, weak networks are flagged before you pick them, and saved credentials carry over between devices.
-
Live device feedback over BLE. Devices that keep a Bluetooth connection open during setup now report their status in real time — and if something needs attention, you get a specific message like “wrong Wi-Fi password” or “this network requires a login page,” and you continue from that step rather than starting over. There are also proximity warnings if the signal between phone, device, and router gets weak.
-
Provisioning Sessions in the console. A new section under Developer Zone → Debugging that logs every provisioning attempt, with success rates split by iOS/Android, average setup duration, the most common error, and a full step-by-step timeline of each attempt showing what the device reported at every stage.
Full write-up with screenshots.
How to join the beta
Android (Play Store beta) to join from web or press “Join Beta” on Blynk’s Play Store page to join from mobile
For the live BLE feedback specifically, you’ll want to be running the BlynkEdgent example from a new standalone BlynkEdgent library available in Arduino IDE LibraryManager
Supported for dynamic provisioning right now:
-
Arduino: ESP32 series, ESP8266, Seeed WIO Terminal
-
Particle Gen 3: Muon, Argon, Boron, Photon 2, Tracker, P2, BSOM, MSOM
-
MicroPython: ESP32 series, Raspberry Pi Pico W
-
Blynk.NCP: ESP32 series
What we’d love you to try
Anything is useful, but these areas would help us most:
-
Set up a brand-new device. Were the preparation instructions clear? Did you always know what to do next?
-
Try the new error handling. This is the hardest part to test by accident, so please break things on purpose — enter a wrong Wi-Fi password, walk out of range mid-setup, try a network with a captive portal. Was the message specific enough to act on, and could you pick up from that step?
-
Set up several devices in a row. Does “Apply saved configuration” save you real time?
-
Check Provisioning Sessions afterwards. Blynk.Console → Developer Zone → Debugging. Do the logged sessions match what you experienced? Is anything missing that you’d want to see?
-
Static Token / QR claiming, if you use it — including the manual code entry option.
Sharing feedback
Reply in this thread, or send us a note via this form.
If you hit something unexpected, the most useful thing you can send us is the Session ID. Enable Developer Mode in your profile and error screens will show both a Reason and a Session ID — paste those in and we can pull up that exact session with its full timeline on our side.
Also handy to include:
- Platform and OS version (e.g. iOS 18.7, Android 16)
- Board / hardware
- Whether it was a first-time setup or a reconfigure
- App logs (make sure they are enabled in application settings before you start a new provisioning)
Thanks in advance — your feedback shapes where this goes next!
Cheers!
The Blynk Team
