Blueprint Wi-Fi failover broken: secondary AP permanently disabled when Strict Sync + saved networks enabled

Android

If you've configured a Blueprint with two Wi-Fi access points and enabled both Strict Wi-Fi Access Point Synchronization and Use Only Saved Wi-Fi Access Points, you may experience an issue where one access point becomes permanently disabled and your devices cannot fail over to it. This article explains the issue and walks you through diagnostic steps and workarounds.

Understand the issue

When both settings are enabled together on a Blueprint with multiple Wi-Fi networks, the Esper Agent may permanently disable one of your configured access points immediately after provisioning. The disabled network won't be attempted even when it's the only network in range, preventing automatic failover between your access points.

Before you begin

To test the issue safely:

• Clone your Blueprint so you don't affect production devices while troubleshooting
• Assign the cloned Blueprint to a single test device
• Ensure your test device is in Multi-App Mode with the Notification Bar enabled

Step 1: Verify your Blueprint configuration

1. In the Esper Console, navigate to Blueprints → [Your Blueprint Name] → Wi-Fi
2. Confirm that both Strict Wi-Fi Access Point Synchronization and Use Only Saved Wi-Fi Access Points are enabled
3. Confirm that two or more access points are listed in your configuration

Step 2: Clone your Blueprint for testing

1. Navigate to Blueprints → [Your Blueprint Name]
2. Click Clone
3. Assign the cloned Blueprint to a test device only

Step 3: Test by toggling one setting

Try one of these configurations on your test device to see if disabling one setting resolves the issue:

• Option A: Disable Use Only Saved Wi-Fi Access Points while keeping Strict Wi-Fi Access Point Synchronization enabled. Then re-apply or re-provision the Blueprint on your test device.
• Option B: Disable Strict Wi-Fi Access Point Synchronization while keeping Use Only Saved Wi-Fi Access Points enabled.

Step 4: Test failover behavior

1. After applying your test configuration, move your test device out of range of the primary access point
2. Verify that the device either:
   • Successfully connects to the secondary access point, or
   • Fails gracefully without showing the secondary network as permanently disabled

Step 5: Capture a bug report (if the issue persists)

1. Navigate to Devices & Groups → [Your Device Name] → Actions → Request Bug Report
2. Capture the report immediately after you observe the failover failure
3. Note the exact time of the failure

Workaround: Use a single access point

If toggling the settings doesn't resolve the issue, remove the secondary access point from your Blueprint:

1. Navigate to Blueprints → [Your Blueprint Name] → Wi-Fi
2. Remove the secondary access point from your configuration
3. Save and re-apply the Blueprint to your devices

Running with a single access point is confirmed as safe when both Strict Wi-Fi Access Point Synchronization and Use Only Saved Wi-Fi Access Points are enabled.

Gather information for support

If the issue continues after testing, prepare the following information before contacting Esper Support:

• A bug report captured immediately after provisioning (before you made any Blueprint changes)
• Esper Agent logs captured via ADB: adb shell logcat -d -s EsperDPC
• Your exact Blueprint version. Navigate to Blueprints → [Your Blueprint Name] → Version History to find this.
• Device model, Android OS version, and Esper Agent version. Navigate to Devices & Groups → [Your Device Name] → Device Info.

Still need help?

If you've tried these steps and the issue persists, contact Esper Support and include the information from the "Gather information for support" section above.