Wi-Fi re-enables itself after being disabled via Blueprint: expected fallback behavior and backend override option
Android
If Wi-Fi re-enables itself on your device even after you've disabled it in a Blueprint, this is expected Esper platform behavior. Your device has a built-in connectivity safeguard that automatically re-enables Wi-Fi when it's your only available network connection. This article explains why this happens and how to control it.
Why Wi-Fi re-enables automatically
When you disable the Allow Wi-Fi option in a Blueprint, the setting prevents users from manually toggling Wi-Fi in the device's native Settings app. However, if your device has no alternative network connection (such as cellular or Ethernet), the Esper management agent includes a failsafe that automatically re-enables Wi-Fi after approximately 10 seconds.
This happens because the device needs to maintain a network connection to stay reachable to the Esper Console. Without this safeguard, devices at locations with poor cellular coverage could become permanently offline and unmanageable.
Before you begin
Check whether your device has an alternative network connection available:
- Active cellular/SIM connection
- Ethernet connection
If your device has one of these connections, the Wi-Fi re-enable behavior may not apply. If Wi-Fi is your device's only network option, the safeguard will remain active unless you apply the override option below.
Option 1: Accept the default behavior
If you want to keep Wi-Fi available as a fallback for devices at locations with weak cellular signal, no action is required. The default behavior protects your devices from going offline while still restricting user-initiated Wi-Fi changes through the Blueprint setting.
Option 2: Force Wi-Fi to remain disabled
If you need Wi-Fi to stay disabled and prevent the safeguard from re-enabling it, you can request a backend configuration change from Esper Support. Follow these steps:
- Determine whether you want to disable Wi-Fi across your entire account or only on specific devices.
- If you're targeting specific devices, collect the Device ID for each device:
- Go to Devices & Groups → [Device Name] → Device Details
- Copy the Device ID
-
Contact Esper Support and provide:
- Whether you want the change applied tenant-wide or per-device
- Device IDs (if specific devices)
- Confirmation that your devices have a stable alternative network connection (cellular or Ethernet)
- Esper Support will apply the backend configuration flag that suppresses the Esper Agent Wi-Fi re-enable safeguard. This cannot be done from the Esper Console UI.
- After the configuration is applied, test by disabling Wi-Fi on your device and confirming it does not re-enable after 10–15 seconds.
Important considerations before requesting the override
Before you apply the backend override, keep these points in mind:
- Verify your device has a reliable alternative network connection (cellular or Ethernet). If you apply this override without an alternative connection, your device may go offline permanently and become unreachable to the Esper Console.
- The override is a backend-level operation and cannot be undone by you through the Esper Console. If you need to revert it, contact Esper Support again.
- If Wi-Fi still re-enables after the backend configuration is applied, verify that your alternative network connection is actually active and stable.
If the override isn't working
If Wi-Fi continues to re-enable after the backend configuration has been applied, check the following:
- Confirm your device has an active and stable alternative network connection (cellular or Ethernet). The safeguard may still trigger if the connection is unreliable.
- Collect device logs to share with Esper Support. You can pull Esper Agent logs via ADB or a system bugreport to show the Wi-Fi re-enable event and the network state at that time.
Still need help?
If you continue to experience issues with Wi-Fi re-enabling or need assistance with the backend override, submit a support ticket. include your device IDs and whether you want the change applied to your entire account or specific devices.
Please sign in to leave a comment.
Comments
0 comments