Get low battery alerts for smart home devices
Get a notification when a battery-powered device drops below a set level, so it can be replaced before the device stops working silently.
Best for: Any platform that reports battery percentage or a low-battery state for its connected sensors, locks, or buttons.
Not for: A device that does not report battery status at all; nothing can be automated against a reading that is not available.
Why this exists
A dead battery in a motion sensor, door sensor, or lock does not usually announce itself. It just stops reporting, and the automations relying on it quietly stop working. A proactive alert catches this before it turns into a missed automation or, worse, a lock that will not open.
Logic
- Trigger: A monitored device’s battery level drops below its set threshold, or reports a “low battery” state.
- Conditions: The device has not already been flagged within the last several days, to avoid repeat alerts for the same drop.
- Action: Send a notification naming the device and its battery level.
- Wait / timeout: None; the notification is sent once the condition is met.
- Stop condition: The alert resets once the battery is replaced and reports a normal level again.
- Manual override: Battery levels can always be checked directly in the platform regardless of the automation.
What I used
Detect low battery levels
No personally verified recommendation yet. This depends on the platform reporting battery data for each device, not on any single piece of hardware.
See recommended gear for the job-first checklist. Product recommendations and any future affiliate relationships are explained in the disclosure.
Setup notes
- Confirm which devices actually report battery data in the platform; some devices only expose a simple low-battery flag rather than a percentage.
- Set a threshold, such as 20 to 25 percent, as a starting point, and adjust based on how quickly a specific device’s battery tends to drop.
- Add a cooldown so the same device does not send repeat alerts every time its reading is checked while still below the threshold.
- Identify a small set of critical devices, such as locks and water leak sensors, and consider giving them a lower threshold or higher-priority notification.
- Keep a small stock of the common battery types used across devices so a replacement does not require an extra trip.
Platform notes
Battery reporting depends on both the device integration and the platform. Confirm whether each device exposes a percentage, a simple low-battery state, or nothing before building a threshold rule. See the platform guides for broader fit and maintenance tradeoffs.
Amazon Alexa
I could not verify a universal Alexa routine trigger for battery percentage across connected sensors, locks, and buttons. Use the device manufacturer’s battery notification when available, and do not assume a battery value visible in Alexa can also trigger a routine.
SmartThings
Use a percentage threshold only when the device exposes the standard battery capability. Available Routine choices come from the device’s SmartThings capabilities. For several devices, an advanced SmartThings Rule can evaluate selected battery attributes, but every included device still needs to report useful data.
Hubitat
Use Hubitat Rule Machine to alert when selected devices report battery below their tested thresholds. Include only devices whose drivers expose a battery value, add repeat suppression, and create a separate stale or inactive-device check because a dead device may stop reporting before crossing the threshold.
Home Assistant
Home Assistant is a technical fit for collecting battery entities and producing a consolidated report, but I have not personally run it. Verify which integrations expose battery data and distinguish missing or unavailable entities from healthy batteries.
Advanced features
Tiered alert levels
Use two thresholds, such as 25 percent for an early notice and 10 percent for an urgent one, so the household gets more time to plan a replacement before it becomes critical.
Daily consolidated report
Instead of a separate notification per device, send one daily summary listing every device currently below its threshold, to reduce notification fatigue on days with several low devices.
Failure modes
- Battery reading jumps from fine to dead with no warning: Some devices only report a simple low-battery state rather than a percentage; treat that state itself as the trigger instead of expecting a gradual decline.
- Battery percentage fluctuates and causes repeat alerts: Add a cooldown, or require the drop to hold for a period before alerting, rather than reacting to every reading.
- A device is missing from monitoring: Confirm it actually reports battery data to the platform; not every device type does.
- Too many notifications arrive: Raise the threshold slightly, add a longer cooldown, or switch to a consolidated daily report.
FAQ
What battery percentage should trigger a warning?
Around 20 to 25 percent is a reasonable starting point for most sensors, giving a few weeks of remaining life to plan a replacement. A smart lock is worth a slightly higher threshold, since running out unexpectedly is more disruptive.
Why does a device’s battery sometimes jump straight from fine to dead?
Some devices only report a simple “ok” or “low” state instead of a percentage, or their battery chemistry drops voltage quickly near the end of its life. Where only a state is available, treat “low” as the trigger instead of a percentage threshold.
Should every device get the same alert priority?
No. A water leak sensor or smart lock losing power is more urgent than a motion sensor, so it is worth treating a small set of critical devices as higher priority than the rest.