Automated offline-device reports: only daily schedule supported; custom intervals and offline-duration triggers not available

Android

Title: Automated offline-device reports limited to daily schedule — workarounds and API alternative

When you need automated offline-device reports on a weekly, custom, or duration-based schedule, Esper delivers only a daily report option, with no way to set custom intervals or trigger reports based on how long a device has been offline.

Why this happens

Automated report subscriptions in the Esper Console are built around a fixed daily recurrence. There is currently no configuration option to change the delivery interval, set a minimum offline-duration threshold, or save a custom date-range report as a recurring subscription. This most commonly affects fleets where devices check in infrequently — such as field equipment, seasonal hardware, or shared-use devices.

Option 1: Set up a daily automated report

A daily subscription is the only supported automated schedule. Use it as your baseline monitoring signal.

1. Open the Esper Console and navigate to Reports.
2. Create a new report and add Device Status as a column or filter so offline devices are clearly visible in the output.
3. Select Subscribe and choose Daily as the delivery schedule — this is the only available recurrence option.
4. Confirm the subscription email arrives and that the Device Status column correctly reflects the online/offline state for your target device groups.

Verify: You should receive your first report email within 24 hours of subscribing. The Device Status column should clearly distinguish offline devices from online ones.

Option 2: Generate ad-hoc reports for custom date ranges

When a daily report is not sufficient, you can manually pull an offline-device report for any time period you choose.

1. In the Esper Console, navigate to Reports → Custom Date Range.
2. Select your desired start and end dates.
3. Apply an offline-device filter or include the Device Status column to isolate the devices you need to review.
4. Download or view the report immediately.

Note that these custom date-range reports cannot be saved as recurring subscriptions — they must be generated manually each time.

Verify: The downloaded report reflects the correct date range and shows Device Status for all devices in your selected groups.

Option 3: Build custom monitoring with the Esper API

If your workflow requires non-daily automation, offline-duration thresholds, or alert logic that the Console does not support, the Esper REST API gives you full control.

1. Use the GET /v0/enterprise/{enterprise_id}/device/ endpoint to retrieve the status and last_seen timestamp for every device in your fleet. The last_seen value lets you calculate exactly how long a device has been offline.
2. Schedule your script or automation tool — such as a cron job, Zapier, or Make — to poll this endpoint at whatever interval your operations require (hourly, every three days, weekly, and so on).
3. Add logic to your script to generate alerts, custom reports, or notifications based on offline duration or any other condition you define.
4. Refer to the Esper API documentation for endpoint references, authentication details, and code examples.

Verify: Your script should return a JSON response containing a status field and a last_seen timestamp for each device. Test against a known offline device to confirm the values are accurate before deploying to production.

If this doesn't resolve it

If none of the options above meet your monitoring requirements, contact Esper Support with the following information:

• The reporting interval or offline-duration threshold your fleet requires
• Your typical device check-in frequency and fleet size
• Whether you are using the API option and any errors or unexpected responses you are seeing

If weekly schedules, custom intervals, or offline-duration triggers are critical to your deployment, submit a feature request through the Esper Console under Help → Submit Feedback and include your fleet's check-in patterns and operational requirements.

Still need help?

If you need offline-device reports with custom intervals or offline-duration triggers, submit a support ticket and include your specific reporting requirements and desired schedule frequency.