🏷️ Rename-resilient auto-discovery
Renaming your sprinkler entities or device in the Home Assistant UI no longer breaks the card. 🎯 Localize everything into your own language — discovery keeps working.
🔧 What's new
Auto-discovery now matches entities against their original_name (the name defined in your ESPHome YAML) as the primary source, falling back to friendly_name and entity_id. 🌍 Because original_name is immutable from HA's perspective, renaming an entity's display name in the UI — or even renaming the whole device — won't break matching anymore.
Since ESPHome entities expose original_name as undefined in the frontend cache, the card fetches it via the WebSocket entity registry API (config/entity_registry/list) on first load. 🔌 The in-flight request is shared across multiple cards, cached per-device to bound memory, and cleaned up when the card is removed or switches device. 🧹
🩹 Other fixes
- ✅ Status normalization — the status sensor now treats any value other than
idle,paused, orstandbyas running. Zone-specific status text like"running - Sprinklers zone 1"correctly shows Pause/Stop controls instead of hiding them. - 🏠 Device prefix stripping now uses the user-renamed device name (
name_by_user), matching how HA composesfriendly_name. - ⚡ Flash-free rendering — the card suppresses incomplete renders until async discovery completes, so enable switches no longer briefly appear as extra zones on load. On WebSocket failure it falls back to synchronous discovery and retries automatically after 60 seconds.
📚 Documentation
docs/entity-naming.md, docs/esphome-setup.md, and the README were updated to reflect original_name-based matching and the new status normalization behaviour.
🙏 Credits
Big thanks to @Svasek for #14 — a thorough, well-engineered contribution that makes the card far more robust for everyone running localized setups. 🌱