A custom Lovelace card for displaying battery levels of battery entities in Home Assistant dashboards.
Lovelace Battery Entity is a custom card for Home Assistant's Lovelace dashboard that displays battery levels for battery-powered entities. It visualizes charge percentages with a color-coded battery icon that indicates warning and critical levels, helping users monitor device battery status directly from their dashboard.
Home Assistant users who want to monitor battery levels of smart devices like locks, sensors, or other battery-powered entities directly on their Lovelace dashboards.
It provides a simple, visually intuitive way to track battery health without needing complex configurations, with customizable thresholds and seamless integration into existing Home Assistant setups.
A custom Lovelace component for displaying battery levels for battery entities
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Setup requires only a few lines of YAML with clear required (type, entity) and optional fields (name, warning, critical), as shown in the README example usage.
Users can set warning and critical levels (defaults at 35% and 15%) to tailor battery level indicators, allowing personalized monitoring for different devices.
The card uses color-coded icons that change to yellow for warning and red for critical levels, providing at-a-glance battery health monitoring directly on the dashboard.
It focuses on minimalism with a single JavaScript file, seamlessly integrating into existing Lovelace dashboards without heavy dependencies or complex setups.
Installation involves downloading and copying files manually into the config directory, which is error-prone and less convenient compared to automated methods like HACS.
It only displays current percentage with color coding, lacking features like historical data, time estimates, or advanced analytics that other cards might offer.
Updates require replacing files manually, modifying version numbers in YAML, and clearing browser cache, as noted in the updating section, which can lead to maintenance overhead.