How Device Configs works

Device Configs is a Wi-Fi setup app that many device makers share. Your customers install it once. When they scan the QR code on your product, it shows your product’s name, picture and colours, and puts the device on their Wi-Fi. You don’t build or maintain an app: you add a firmware kit to your device, give each unit a label at the factory, and pay for each device that gets online.

What your customer does

1. Scans the code on the device. Their phone’s camera opens your product in the Device Configs app, with your name, picture and colours.
2. Plugs it in. The app finds that exact unit over Bluetooth, even if several identical devices are nearby, and opens an encrypted session using the unit’s own setup code.
3. Chooses a network. The device lists the Wi-Fi networks it can see from where it sits.
4. Types the password. The device joins and reports back: online, wrong password, or network not found. If the password was mistyped, your customer can fix it without starting over.

What you do

Add the kit (ESP-IDF)One component and one call: dc_start().

Add the kit (Arduino)One library and one call: DeviceConfigs.begin().

Label each unitA serial, a setup code and a QR label per unit, from one command.

Your product recordThe name, picture and colour your customers see.

What runs where

• On the device: the kit, built on Espressif’s own provisioning (ESP-IDF 5.1 or later, Arduino-ESP32 3.x). It speaks Espressif’s protocol plus one Device Configs endpoint for the token and label: the protocol.
• On the phone: the Device Configs app (Android today; iPhone is coming). It reads your product record, never your customer’s data.
• On your servers: nothing new. After setup the device has a signed token that says which product and unit it is; send it to your own service.