Scheduled nightly reboots not in Blueprints — configure via API

Android

When you need devices to reboot automatically on a recurring schedule, the Esper Console's Blueprints and provisioning settings do not include a scheduled reboot option. The only way to configure recurring reboots is through the Esper API.

Why this happens

Blueprints manage static device configuration — kiosk mode, network settings, app assignments, and permissions. Scheduled reboots are runtime operational commands, not configuration states, and require a scheduling mechanism that only the Esper API provides. Because they are not stored in a Blueprint, scheduled reboot commands are also lost if a device is re-provisioned or its Blueprint is reapplied and must be reconfigured manually.

Before you begin

Confirm you have the following before proceeding:

• Devices running the Esper Agent and online during the intended reboot window
• Access to the Esper API via the Esper Console or the Esper Developer Dashboard
• The Device ID or Group ID for the devices you want to target

Schedule a recurring nightly reboot via the Esper API

1. Open the Esper Console and navigate to the API explorer, or open the Esper Developer Dashboard directly.
2. Locate the Reboot command endpoint in the API reference.
3. Target your devices by supplying either:
   • A single Device ID to reboot one device, or
   • A Group ID to reboot all devices in a group simultaneously
4. Set the recurrence to nightly and choose a time zone:
   • Device local time — recommended when devices span multiple time zones, so every device reboots at the same local hour
   • Console time (UTC) — use this when all devices are in a single time zone or when a fixed UTC window matters for your operations
5. Select a low-activity window — for example, 02:00–03:00 local time — to avoid interrupting active sessions. Keep the window short to prevent timing drift across executions.
6. Submit the API request. The API returns a command ID; save this for verification.

Verify the scheduled reboot is active

After submitting, confirm the command was accepted and later executed:

1. Navigate to Devices & Groups → [Device Name] → Commands in the Esper Console.
2. Confirm the scheduled command appears with the status Scheduled. This confirms the API accepted the request and the command is queued for the next window.
3. After the first execution window passes, return to Devices & Groups → [Device Name] → Commands and confirm the status has changed to Success.
4. Check the device's last-seen and last-reboot timestamps under Devices & Groups → [Device Name] to confirm the restart occurred at the expected time.

Verify: The command status should show Success and the device's last-reboot timestamp should match your scheduled window within a few minutes of the configured time.

If this doesn't resolve it

Use the following to diagnose specific failure modes before contacting support:

Command shows Queued or Failed:

1. Navigate to Devices & Groups → [Device Name] → Activity Feed.
2. Check the Activity Feed for the scheduled window to confirm whether the device was online at execution time.
3. If the device was offline during the entire window, Esper does not queue the reboot for retry. The device must wait for the next scheduled occurrence. Ensure devices are powered on and connected to the internet during your chosen window.

Device was online but the command did not execute:

1. Navigate to Devices & Groups → [Device Name] and check the installed Esper Agent version. Older agent versions may not support scheduled command execution.
2. Update the Esper Agent via Esper Software Updates if the version is outdated.
3. Re-submit the scheduled reboot command after updating the agent.

Device was re-provisioned and reboots stopped:

1. Re-provisioning and Blueprint reapplication erase all scheduled commands. Return to the API and resubmit the scheduled reboot configuration for the affected device or group.

If the device was confirmed online, the Esper Agent is current, and the command still did not execute, contact Esper Support with the following information:

• Device ID
• Esper Agent version installed on the device
• Command ID returned when the schedule was created
• Screenshot or export of the Activity Feed from the scheduled window

Still need help?

If you need assistance configuring scheduled nightly reboots via the Esper API, please submit a support ticket and include your API endpoint, the reboot schedule parameters you're attempting to set, and any error messages you're receiving.