# Battery/Hardware Triggers: Automating “Eco-Mode” or service tickets 1. Overview ----------- **Hardware-based automations** in **Hexnode UEM** allow IT teams to monitor physical device telemetry (e.g., battery levels) and automatically execute predefined actions. By responding dynamically to the physical state of **Windows** and **macOS** devices, organizations can reduce manual intervention, extend hardware lifecycles, and shift from reactive troubleshooting to proactive management. ### The Two Primary Workflows **1. Power Management Automation (“Eco-Mode”)** - **Objective:** Automate power conservation so mobile endpoints remain operational for longer periods when battery levels become critically low. - **Mechanism:** The **Automate module** runs recurring **Time-based Automations**, combined with **Target Filters** to identify devices where the battery level has dropped **<20%** at their next sync. - **Action:** When devices match the filter criteria, Hexnode UEM executes an **Associate Policy** action that applies a restrictive Power Management / Energy Saver policy. - **User Communication**(Optional): Administrators can include a user notification using **Broadcast Message** as part of the automated workflow to inform users when a power-saving policy is applied due to low battery conditions. **2. IT Staff Notification (Battery Low Alerts)** - **Objective:** Provide IT teams with visibility into devices experiencing low battery conditions so that administrators can monitor endpoints and assist users if necessary. - **Mechanism:** Hexnode monitors battery telemetry reported during device check-ins. A global battery alert threshold can be configured in **Admin > General Settings > Battery Level Alert**. - **Action:** When a device reports a battery level that reaches the defined threshold, **Alert Profiles** can automatically send email notifications to designated technicians or service desk addresses. 2. Trigger Conditions & Actions Matrix ------------------------------------------ Hardware AttributeHexnode Detection MethodVerified Automated Action**Battery Level <20%****Automate** tab > Time Trigger + Target Filter**Apply Policy**: Associate Energy Saver / Power Management Policy**Battery Level Alert Threshold Reached****Admin > General Settings > Alert Profile > Device-specific event****Notify IT Staff via Email**3. Implementation Steps in Hexnode UEM -------------------------------------- ### Step A: Configure the Power Management Policy 1. Navigate to **Policies > New Policy**. 2. Provide a *Policy Name* (e.g., “Restrictive Power Policy”) and *description*. 3. Configure OS-specific power management policies: - **macOS:** Policies > macOS > Configurations > [Energy Saver](https://www.hexnode.com/mobile-device-management/help/how-to-configure-energy-saver-settings-on-macos-devices/). - Configure **Idle timeout for system sleep** and **Idle timeout for display sleep** settings with lower values so devices enter sleep states quickly and conserve battery power. - **Windows:** Policies > Windows > Configurations > [Power](https://www.hexnode.com/mobile-device-management/help/how-to-configure-power-consumption-settings-for-windows/). - Configure **Turn on Energy Saver when charge level is at** and **Unattended Sleep after** settings to enable Windows Energy Saver mode and reduce idle power usage. 4. Save the policy (do not assign targets; **Automate** will handle assignment). ### Step B: Create the Automation Rule (Time-based + Target Filter) 1. Navigate to [Automate](https://www.hexnode.com/mobile-device-management/help/automate-device-management-tasks/) > **New Automation**. 2. Select platform: **Windows / macOS**. 3. Configure the automation **Action**: - Select **Associate Policy**. - Choose the policy created in Step A (“Restrictive Power Policy”). 4. Configure **Settings & Schedule**: - **Trigger**: Time - **Initiate**: Repeat at desired frequency (hourly/daily) 5. Configure **Target Filters**: Specify the Included Groups to define which device groups should be evaluated and **Filter** devices with battery **< 20%**. - **Select Column**: Battery level - **Select Comparator**: Less than - **Enter Value**: 20 6. Review and save automation. **Result:** At the scheduled interval, Hexnode evaluates the most recent device telemetry reported during device check-ins. If a device within the selected groups reports a battery level below 20%, Hexnode automatically associates the configured power-saving policy to that device. ### Step C: Configure Alerts for IT Staff 1. Navigate to **Admin > General Settings**. 2. Configure the [Battery Level Alert](https://www.hexnode.com/mobile-device-management/help/mdm-settings/#battery-level-alert) threshold according to your organizational requirement. 3. Next navigate to **Admin > Alert Profile** > [New Alert Profile](https://www.hexnode.com/mobile-device-management/help/alert-profiles/). 4. Configure the alert profile: - **Event Source**: Select **Device**. - **Add Event**: Select **Device battery level**. 5. Configure the **Action**: **Notify via Email**. 6. Configure **Targets and Technicians**: Add IT staff or service desk email alias. 7. Save and enable the Alert Profile. **Result:** When a device reports a battery level that reaches the configured alert threshold during its next check-in, Hexnode automatically sends an email notification to the designated recipients. 4. User Experience (UX) & Notifications ------------------------------------------- When automated policies modify device behaviour, notifying users helps prevent confusion and ensures they understand why device settings have changed. - **Automated Notification (Optional):** Administrators can include an **Alert > Broadcast Message** action as part of the automation workflow to notify users when a power-saving policy is applied due to low battery conditions. - **Recommended Message:** “Your device battery is critically low. A power-saving policy has been applied to preserve remaining battery life. Please connect your device to a power source.” When the workflow executes, the system applies the restrictive power policy and simultaneously displays the broadcast message to the end user, ensuring they are aware of the temporary energy-saving configuration. 5. Troubleshooting Guide ------------------------ **Issue: Automation Not Triggering** - **Cause:** Hexnode’s Time-based automations rely on data collected during the last device sync and only execute at their defined scheduled interval. If the battery drops below the threshold after the last sync, the automation will not apply the policy until the next scheduled run. - **Fix:** Verify the device’s last check-in time by navigating to **Manage > Devices > Device Summary**. Initiate a manual **Scan Device** action to force a sync with the Hexnode server, and ensure the device is connected to a network so it can report its updated battery telemetry. **Issue: Target Filter Fails to Capture Devices** - **Cause:** The automation rule executes, but the policy is not assigned because the device falls outside the defined group scope, the filter uses incorrect syntax, or the OS fails to report telemetry. - **Fix:** Verify the device is a member of the specific group selected under **Included Groups** in the automation rule. Ensure the Target Filter **Comparator** is strictly set to **Less than** and the **Value** contains only integers (e.g., 20 without the % symbol). Finally, confirm the device is actively reporting its Battery Level attribute in the **Device Summary**.