A Home Assistant Lovelace card that automatically populates entity lists based on dynamic filters and criteria.
Auto Entities is a custom Lovelace card for Home Assistant that automatically populates dashboard cards with entities based on dynamic filters, templates, and matching criteria. It solves the problem of manually managing entity lists in dashboards by allowing users to define rules that automatically include or exclude entities as conditions change.
Home Assistant users and dashboard designers who want to create dynamic, automated Lovelace interfaces that adapt to entity states, attributes, and other smart home conditions without manual updates.
Developers choose Auto Entities because it dramatically reduces dashboard maintenance overhead, enables highly contextual and adaptive interfaces, and provides powerful filtering capabilities beyond Home Assistant's built-in card options, all while integrating seamlessly with the existing Lovelace ecosystem.
🔹Automatically populate the entities-list of lovelace cards
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically updates card contents based on real-time entity states and attributes, eliminating manual list maintenance. For example, filters can show only lights that are 'on' or devices with low battery, as demonstrated in the README.
Supports wildcards, regex, numerical comparisons, and time-based filters for precise entity selection. The README shows filtering by battery level '<= 50' or last updated '< 20m ago', enabling complex criteria.
Uses Jinja templates to generate entity lists programmatically, allowing for nearly limitless customization. Examples include iterating over all lights or customizing entity names based on device attributes.
Works as a drop-in custom card compatible with any Lovelace card type by populating the entities parameter, ensuring easy adoption in existing dashboards without modifying core Home Assistant.
Requires writing and maintaining detailed YAML with filter rules, which is error-prone and daunting for users without programming experience. The README is extensive but assumes familiarity with YAML syntax and logic.
Dynamic filtering and template evaluation add processing overhead, potentially slowing down dashboard updates, especially with large numbers of entities or complex Jinja templates, as hinted by the sorting and filtering logic.
Lacks a graphical interface, forcing all configuration through code, which increases the learning curve and makes real-time adjustments cumbersome compared to Home Assistant's built-in card editors.