> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/blynk.apps/device-management/add-new-device.md).

# Add New Device

### Connect the device with Blynk.Apps

Tap **Add New Device** from the Devices tab.

<figure><img src="https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBFTVMf7L6S67HOuqVC%2Fuploads%2F1lsI0sklB58DEuu21UiY%2Fprepare-your-device.png?alt=media&amp;token=b2a64d69-d7d0-4678-a2ca-0a1026371d10" alt=""><figcaption></figcaption></figure>

If the app doesn't already have the permissions it needs (e.g. Bluetooth, Local Network, Location), it will ask for them at this point.

{% hint style="info" %}
On iOS 18 and later, Blynk uses Apple's **AccessorySetupKit** for device discovery and pairing. Because AccessorySetupKit handles this natively, the permissions screen is skipped entirely on those devices — the system handles access grants as part of the native pairing sheet instead (see below).
{% endhint %}

#### Prepare Your Device

Before searching for the device, the app shows preparation instructions. What's shown here depends on how the device's template is configured:

* **Multiple templates with their own guides** — you're first asked which template the device belongs to, then shown that template's specific instructions.
* **A single template with an installation guide** — an **Install \[Product Name]** link opens the full guide.
* **No guides configured** — generic preparation instructions are shown.

{% hint style="warning" %}
Per-template installation/activation guides are an **Enterprise plan** feature. On other plans, this screen always shows generic preparation instructions, regardless of how many templates a device could match.
{% endhint %}

{% hint style="info" %}
Template owners configure these per-template instructions (Installation Guide, Activation Guide, Troubleshooting link) under User Guides in the template settings. See the full guide-authoring reference here: <https://docs.blynk.io/en/blynk.console/templates/user-guides#device-activation-guide>.
{% endhint %}

Read the instructions, make sure your device is powered on and in pairing mode, then tap **Find Devices**.

#### Finding your device

**On iOS**, the system's own AccessorySetupKit window takes over to search for and pair the device — you won't see Blynk's own search screen.

<figure><img src="https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBFTVMf7L6S67HOuqVC%2Fuploads%2FfSRxgcyoMSDrFOmw1UEY%2Faccessory-setup-kit-ios.png?alt=media&amp;token=054915a3-c71c-4191-ad48-aa43fe3d70d2" alt=""><figcaption></figcaption></figure>

**On Android** (and pre-iOS 18 devices), the system shows its own dialog listing the device's access points found nearby — tap the one you want to connect to, and the app proceeds straight to connecting.

<figure><img src="https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBFTVMf7L6S67HOuqVC%2Fuploads%2FxciRfACOsGCgqzhSOx1x%2Fchoose-your-device-android.png?alt=media&amp;token=9db993cf-f886-4fc6-88b3-8d4f5d48ae28" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If several similar devices might be nearby, set a **Broadcast Name** for the template — the device advertises as `Blynk {broadcast-name}-XXXX` instead of a generic name, so both the AccessorySetupKit sheet and the Android picker above can identify it faster and show its product image and name from this very first step. Configure it under **Template → Template Settings → Device activation & provisioning → Dynamic provisioning**.

**Keep the Broadcast Name to 8 characters or fewer.** Because of a BLE broadcasting limitation, a longer name isn't detected by the iOS app at all — the device falls back to advertising with only the vendor suffix. It stays discoverable, but if your organization has more than one template, the app can't tell which template the device belongs to, so it won't show the correct product image and name.
{% endhint %}

#### Firmware update, if required

If the device needs a firmware update before it can be provisioned, the standard [OTA update screens](/en/blynk.edgent/updating-devices-firmwares-ota.md) are shown at this point, before the connection step continues.

#### Connecting

Once a device is selected, the app connects to it and reads its details. If your device supports more than one connection type (e.g. Wi-Fi and Ethernet), you'll be asked to pick one at this point.

Closing the flow at any point from here on prompts a confirmation — exiting counts as a Canceled session, and you'll need to start over.

### Connect your device to a network

#### Wi-Fi

1. If you've previously saved Wi-Fi credentials on this app (via **Remember this network**), you're offered that saved network directly. Otherwise, the app fetches the list of networks visible to the device and shows them for you to pick from. Only networks compatible with the device are listed — 2.4 GHz, 5 GHz, or both, depending on what the device supports.
2. Networks with a weak signal are marked **Weak signal**; selecting one asks you to confirm you want to proceed (or move closer to the router, or pick a different network).
3. Enter the network password. Advanced connection settings (static IP, etc.) are available here if your device supports them.

<figure><img src="https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBFTVMf7L6S67HOuqVC%2Fuploads%2FNFqCRBjtG74zF1lOm6un%2Fwifi-network-setup.png?alt=media&amp;token=1539f425-b611-455c-8dfa-a1c9d7007597" alt=""><figcaption></figcaption></figure>

Once submitted, credentials are sent to the device, the device reports back whether it connected successfully, and the app waits for cloud confirmation that the device is online before showing the success screen.

#### Cellular

Cellular devices may offer a **Configure APN** step if your carrier requires a custom access point name.

#### Ethernet

The app checks for an active Ethernet connection and proceeds automatically once confirmed.

### Success screen

What you see once the device is online depends on what's already known about this template:

1. **Apply saved configuration** — if a device from the same template was provisioned before with metadata, you're offered a button to open a drawer of recent configurations and apply one directly to the new device.
2. **Configure device** — first device from this template with provisioning [metadata](https://docs.blynk.io/en/blynk.console/templates/metadata) enabled: continues into the [device profiling flow](#device-profiling) below.
3. **Nothing further to configure** — if the template has no provisioning metadata enabled, you're done: continue to the device dashboard, or add another device.

### Device profiling

If the template has provisioning metadata enabled, you'll be guided through a short setup wizard for that device (name, location, contact info, unit preferences, or whatever fields the template defines), then a **Review** screen to confirm everything before finishing.

<figure><img src="https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBFTVMf7L6S67HOuqVC%2Fuploads%2F0mCCqLfKM2Fq9EAubYbs%2Fdevice-profiling-and-recent-profiles.png?alt=media&amp;token=5ab09ce0-8740-4a28-9675-f858984edcf0" alt=""><figcaption></figcaption></figure>

If you've provisioned devices on this template before, you can skip re-entering the same details: press **Apply saved configuration**, choose a previous configuration, and tap **Review and Apply**.

### Error handling

Provisioning is one of the trickiest moments for a new IoT product, so the app tries to be as specific as possible about what went wrong and what to do next. For the full list of error codes and what each one means, see [Provisioning Error IDs](/en/blynk.console/developers/debugging/provisioning-sessions.md#provisioning-error-ids) in Provisioning Sessions.

#### Devices with a live (BLE-assisted) connection

Some devices keep their Bluetooth connection to the phone alive throughout setup. For these, the app can show the *exact* error the device reported, plus recovery instructions, and lets you resume from the failed step instead of starting over.

<figure><img src="https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBFTVMf7L6S67HOuqVC%2Fuploads%2F2lkToAWUsAm0R4PCTC7A%2Fprovisioning-error.png?alt=media&amp;token=22c8d60e-cd8a-4404-aba9-9d7300bf4ef7" alt="" width="375"><figcaption></figcaption></figure>

The recovery instructions and the **See Troubleshooting** link come from the template's [User Guides](/en/blynk.console/templates/user-guides.md) troubleshooting link, if one is configured, or a generic Blynk documentation link otherwise.

Two additional fields appear below the instructions, visible only in **Developer Mode** — regular end users don't see these:

* **Reason** — the specific error identifier.
* **Session ID** — developers can look this up in [Provisioning Sessions](/en/blynk.console/developers/debugging/provisioning-sessions.md) in the console to see the full step-by-step timeline for that attempt.

{% hint style="success" %}
BLE-assisted provisioning is supported by the basic Blynk.Edgent examples found in the [Blynk.Edgent overview](/en/blynk.edgent/overview.md) — exact support depends on your hardware type.
{% endhint %}

**Wi-Fi-specific errors** send you straight back to the relevant step — the network list if it was the wrong network, or the password screen (with the previously entered password still visible) if it was a wrong password.

#### Devices without a live connection

If the device isn't BLE-assisted, the connection is simply lost on error and the cause isn't known right away. On your next attempt, the device reports whatever error it last hit, and it's surfaced as a snackbar on the Wi-Fi screen with a link to details.

#### Proximity warnings

The app can detect a weak connection between your phone and the device, or between the device and your router, and will warn you to move closer. The warning clears automatically once the connection improves.

#### Escalation

If the same error happens on the same device three times in a row, the app stops suggesting you just try again and instead opens an escalation drawer:

<div align="center"><figure><img src="https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBFTVMf7L6S67HOuqVC%2Fuploads%2FHFdXmzWkNiGXVye5Wn7W%2Fprovisioning-escalation-drawer.png?alt=media&amp;token=63aebaf5-ceae-4dfb-ac08-b2e4907a684e" alt="" width="375"><figcaption></figcaption></figure></div>

From here you can **Contact Support**, **Send Logs** (attaches app logs, if logging is enabled), or **Try Again**.

### Claiming a device with a Static Token

Devices that ship with a pre-flashed **Static Token** (cellular, Ethernet, or other non-Wi-Fi hardware) are added the same way — tap **Add New Device** — but instead of Wi-Fi setup you'll claim the device using its QR code:

<figure><img src="https://1839001309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBFTVMf7L6S67HOuqVC%2Fuploads%2FwdidIWpy1yoMU0bKux7w%2Fstatic-token-claim-flow.png?alt=media&amp;token=2a6e3126-1b9d-44a4-aa1a-bf08dc80f47c" alt=""><figcaption></figcaption></figure>

1. On the same template-driven **Prepare Your Device** screen described above, choose **Scan QR Code**, or **Enter Manually** if the code is printed as text instead of (or alongside) a QR code.
2. Scanning opens a QR scanner in a bottom drawer; manual entry validates the code length as you type and flags it if it's incomplete.
3. Once accepted, the device is claimed to your account and ready to use.

See [Static Token](/en/getting-started/activating-devices/blynk-edgent-static-authtoken.md) for how these tokens are generated and deployed by manufacturers.

### Reconfiguring an existing device

Use **Reconfigure** from the device's actions menu when a device needs new network credentials — the most common reasons are moving it to a new place or updating your Wi-Fi setup (new router, new password, switching networks). It also works for connecting a new or factory-reset device while keeping the data and settings of a previously set-up device. Either way, this starts the provisioning flow described at the top of this page again for that device slot. For the physical button/LED behavior used to reset a device before reconfiguring it, see [Re-provisioning new WiFi credentials](/en/getting-started/activating-devices/blynk-edgent-wifi-provisioning.md#re-provisioning-new-wifi-credentials).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.blynk.io/en/blynk.apps/device-management/add-new-device.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.