Seamless (Zero-Touch) provisioning ignored in favour of QR code on camera-less RK3288 devices: re-register serial numbers under Provisioning Template to resolve

Android

If you're provisioning camera-less Android devices (like RK3288 tablets) and they're defaulting to QR code enrollment instead of seamless enrollment, your device serial numbers may not be correctly registered in your Provisioning Template. This article explains how to fix this issue.

Before you begin

Seamless (zero-touch) enrollment requires that your device serial numbers are pre-registered in the Esper Console. Without this registration, devices without cameras cannot complete provisioning because they cannot scan QR codes.

You'll need:

• Access to the Esper Console with admin privileges
• The serial numbers of the affected devices
• The name of the Provisioning Template you want to use

Step 1: Verify your Provisioning Template

First, identify which Provisioning Template you're using for these devices.

1. In the Esper Console, navigate to Provisioning Templates
2. Locate the template you want to use (for example, Dispensed-Kiosk)
3. Note the exact template name

Step 2: Add serial numbers to your Provisioning Template

1. In Provisioning Templates, select your template
2. Click the three-dot menu (⋮) and select Serial number/IMEI Management
3. Add each affected device serial number to the Seamless Enrollment list
4. Confirm that all serial numbers are saved

How to find your device serial number:

• On the device: go to Settings → About device → Serial number
• Via ADB: run adb shell getprop ro.serialno

Step 3: Remove conflicting Blueprint entries (if applicable)

If any of these serial numbers were previously registered under a Blueprint enrollment entry, you must remove them to prevent conflicts.

1. In the Esper Console, navigate to Blueprints
2. Open the Blueprint that contains your devices
3. Go to Seamless Enrollment
4. Remove any serial numbers you've just added to your Provisioning Template

Why this matters: Blueprint-based enrollment and Template-based enrollment are separate provisioning flows. A device registered under a Blueprint will not use Template configuration, and vice versa.

Step 4: Reboot your devices

Reboot each affected device to trigger a fresh provisioning attempt. The device should now:

• Be identified by its serial number
• Skip the QR code flow entirely
• Proceed with seamless enrollment from your Provisioning Template

Step 5: Verify provisioning succeeded

Navigate to Devices & Groups and check that your devices appear with status Active. If devices are still on provisioning screens, they should move through provisioning stages without stopping at the QR code screen.

If provisioning still fails

Verify the serial number format: The serial number you entered in the Esper Console must exactly match the hardware serial number on the device. Double-check by comparing the Esper Console entry with the device's Settings → About device → Serial number or the ADB output.

Check network connectivity: Seamless enrollment requires the device to connect to Esper's provisioning servers at boot. Verify the device has internet access during provisioning.

Consider the Esper Agent version: If provisioning still fails after correct serial number registration across multiple devices, the Esper Agent version may be the cause. Contact Esper Support to discuss rolling back to a previous agent version or investigating potential issues with the current version.

Important notes

• Camera-less devices require seamless enrollment: Devices without cameras cannot complete QR code provisioning. Seamless enrollment via serial number is the only available method.
• One provisioning method per device: Each device serial number must be registered in either a Blueprint or a Provisioning Template, but not both. If you're using Templates as your standard provisioning method, ensure all serial numbers are registered under Templates.
• Batch provisioning: When provisioning a batch of devices, verify that every serial number has been added to your Provisioning Template before deployment.

Still need help?

If you've followed these steps and provisioning is still failing, submit a support ticket with the following information:

• The affected device serial numbers
• Your Provisioning Template name
• The current Esper Agent version on the devices
• A description of the provisioning failure (does it show the QR code screen, or fail at another stage?)