WiFi turns on automatically despite "Allow Wi-Fi" disabled in Blueprint: expected failsafe behavior

Android

If Wi-Fi is turning on automatically on your device even though you've disabled the Allow Wi-Fi setting in your Blueprint, this is expected failsafe behavior. Esper automatically re-enables Wi-Fi if your device loses its cellular or Ethernet connection to keep your device reachable and manageable. This article explains why this happens and how to troubleshoot it.

Understanding the Wi-Fi failsafe behavior

Esper includes a built-in connectivity failsafe: if your device cannot connect to a cellular network or Ethernet for approximately 10 seconds, Wi-Fi will automatically turn back on—even if your Blueprint has Allow Wi-Fi disabled. This prevents your device from becoming permanently unreachable and unmanageable.

This behavior is by design and is documented in the Blueprint configuration interface itself.

Before you begin

Verify which Blueprint is currently applied to your device:

1. In the Esper Console, go to Devices & Groups → [Device Name] → Blueprint.
2. Note the name of the applied Blueprint.
3. Open that Blueprint and check the Network or Wi-Fi settings section.
4. Confirm the current value of the Allow Wi-Fi toggle.

Check your device's cellular connection

The most common cause of Wi-Fi turning on is that your device doesn't have an active cellular connection. Even if your SIM is inserted and Data Roaming is enabled, your device must have a working cellular data session.

1. In the Esper Console, go to Devices & Groups → [Device Name] → Device Details → Network.
2. Verify that cellular data is actively connected (not just roaming-enabled).
3. Check that your SIM is recognized, your carrier network is available, and your APN configuration is correct.

If your cellular connection is not active, the failsafe will trigger and re-enable Wi-Fi after approximately 10 seconds. This is expected behavior and cannot be suppressed.

Verify your Blueprint setting is applied

1. Confirm the Allow Wi-Fi toggle in your Blueprint is set to the state you intend.
2. Allow time for the Blueprint to converge on the device (typically a few minutes).
3. After confirming your cellular connection is active and stable, check the device's Wi-Fi state again under Devices & Groups → [Device Name] → Device Details → Network.

If your cellular connection is healthy, Wi-Fi should remain off per your Blueprint policy.

If Wi-Fi still turns on despite an active cellular connection

If your cellular data is actively connected and Wi-Fi is still turning on, this may indicate an issue with the Esper agent or Blueprint convergence.

• Collect diagnostic logs by running adb shell logcat -s Esper Agent on your device.
• Check whether any secondary automation, script, or device OEM setting is independently re-enabling Wi-Fi outside of Esper's control.
• Contact Esper Support and provide your device details and the collected logs.

Still need help?

If you've followed these steps and still need assistance, submit a support ticket. Include your device name, the Blueprint name, your cellular connection status, and any relevant diagnostic logs.