Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation.

About

Battery Monitor is a custom integration that gathers every battery entity in Home Assistant into one overview. It finds battery entities automatically by device class, with an optional name-based check for sensors that report a percentage. Summary sensors report the monitored total, how many are low or at zero, the lowest battery, percentages, a traffic-light status and a list of devices below the threshold. Low and critical thresholds are adjustable, and filters can include or exclude entities by domain, selection or name pattern. Unavailable batteries keep their last known value, which can be limited to a set number of hours, and a notification can be created when a battery reads 0%. It works locally and is set up in the UI.

Automatic summary of the README and code of DomoticaFacile/battery_monitor. Something wrong, or are you the maintainer and want your own text here? Get in touch

Supports

  • Works locally Talks to your devices on your own network. No vendor cloud in between.

  • From the Marketplace Installed through the Marketplace, formerly HACS.

  • Actively maintained Its author released or pushed a change in the last six months.

Provides

  • Sensors

Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

Battery Monitor

  • Low battery threshold (%)
  • Critical battery threshold (%)
  • Use heuristic (battery in name/entity_id) in addition to device_class
  • Domains to scan (comma-separated, e.g. sensor, binary_sensor)
  • Include only these entities (multi-select)
  • Exclude these entities (multi-select)
  • Include only entity_id matching (fnmatch, comma-separated)
  • Exclude entity_id matching (fnmatch, comma-separated)
  • Ignore 0% when calculating the lowest battery
  • Treat unavailable batteries as 0% (when no last known value exists)
  • Keep last known value of unavailable batteries for (hours, 0 = until the entity is removed from Home Assistant)
  • Notify when a 0% value appears

After setup

  • Low battery threshold (%)
  • Critical battery threshold (%)
  • Use heuristic (battery in name/entity_id) in addition to device_class
  • Domains to scan (comma-separated, e.g. sensor, binary_sensor)
  • Include only these entities (multi-select)
  • Exclude these entities (multi-select)
  • Include only entity_id matching (fnmatch, comma-separated)
  • Exclude entity_id matching (fnmatch, comma-separated)
  • Ignore 0% when calculating the lowest battery
  • Treat unavailable batteries as 0% (when no last known value exists)
  • Keep last known value of unavailable batteries for (hours, 0 = until the entity is removed from Home Assistant)
  • Notify when a 0% value appears

Texts from the code of DomoticaFacile/battery_monitor.

Entities

  • SensorsStatus, Total, Low, Low Devices, Zero Count, Unavailable Count, Lowest, Low Percent, Zero Percent, Low List, Overview

Troubleshooting

  • DiagnosticsDownloads a diagnostics file to attach to a bug report.

From the README

Perfect for Zigbee setups (ZHA / Zigbee2MQTT), Wi-Fi devices, and any integration that exposes battery sensors.

From the README of DomoticaFacile/battery_monitor, MIT License. Shortened.

Shows in Vulpo

Chart card, Apple Watch.

Information

Installs
529 sharing analytics
GitHub stars
37
Connection
Works locally
Upkeep
Updated in the last 6 months
Version
v1.2.4,
Kind
Marketplace integration
Needs
Needs the Marketplace (HACS on 2026.10 and older)
Domain
battery_monitor

You might also like

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. About these numbers