Android Last Check-In not updating every 15 minutes in HexnodeSolved

Hi @eduardo,

Keeping the Hexnode portal open should not prevent the Last Check-In timestamp from updating. The portal updates the value when the Hexnode server receives communication from the device, so a manual browser refresh is not normally required.

The important distinction is between Device Inactivity and the actual device check-in behavior:

– Device Inactivity is a compliance monitoring threshold.
– Setting Device Inactivity to 15 minutes does not force the device to check in every 15 minutes.
– It means the device can be marked Non-Compliant if it remains silent for longer than that threshold.

On Android, scheduled background communication can also be delayed by OS-level battery management such as idle state or Doze Mode. Because of this, a device may not always check in at an exact fixed interval like every 15 minutes.

A manual command from the Hexnode portal can trigger an immediate sync attempt. For recurring syncs, you have two options:

1. Scheduled Device Scan:
Navigate to Admin > General Settings > Scheduled Device Scan. This lets devices run an automatic scan at a preset time. However, the native Scheduled Device Scan option runs once per day at a single selected time.

2. Scheduled Scan Device action:
You can configure an automation to run the Scan Device action more frequently, such as every 15 minutes. This is the closer option if you need repeated scans throughout the day.

Even then, if a device is powered off, has no internet connection, or has a dead battery, it cannot respond until it is back online.

Regards,
Sienna Carter
Hexnode UEM

We want to stay ahead of this for every tablet. We already use a high battery threshold so we know when a tablet starts discharging, not just when it is nearly dead. What’s the best alert setup for the whole fleet?

Hi @eduardo,

Use an Alert Profile with both battery and inactivity events enabled.

Recommended setup:

1. Configure the battery threshold:
Go to Admin > General Settings > Battery Level Alert and set the percentage that should trigger the alert. A higher threshold, such as 90%, can be used if you want to know as soon as a tablet starts discharging.

2. Create an Alert Profile:
Go to Admin > Alerts > New Alert Profile and add these events: Device battery level and Device Inactive.

3. Configure recipients:
Add the email addresses of the technicians who should receive notifications.

4. Choose targets carefully
– Leave Targets blank if the alert should apply to all enrolled devices. This is usually best for full-fleet monitoring because newly enrolled tablets are included automatically.
– Add specific target devices only if the alert should apply to a limited subset. This requires manual updates whenever tablets are added or removed.

Regards,
Sienna Carter
Hexnode UEM