Patch release. Fixes the GUI editor showing empty/invisible input fields under LOCATION, ANIMATION, APPEARANCE, OVERLAYS, and several marker fields on current HA versions. The card itself was unaffected — only the GUI editor was broken; YAML editing always worked.
No new features, no breaking changes. Drop-in patch over 3.6.2. HACS users with auto-update will see this as a routine update.
Fixed
GUI editor inputs invisible on current HA versions (#166)
HA frontend removed ha-textfield on 2026-04-01 (commit "Migrate all from ha-textfield to ha-input #30349"). Our editor's 14 textfield usages then rendered as zero-height invisible elements — users opening the editor saw section headers (LOCATION, ANIMATION, etc.) with empty space below them. Centre coordinates, frame delays, transition time, height/width, wildfire min acres, wildfire radius, and marker positions were uneditable via the GUI editor on recent HA versions.
YAML editing always worked as the escape hatch, but the GUI was effectively broken.
Migrated all usages to the replacement element ha-input (1-to-1 API mapping; helper="..." renamed to hint="..." per the new element's webawesome convention).
Changed
- Marker action buttons now use
ha-button. Add Marker, Remove (per marker), and Reset Color (per marker) in the Markers sub-page render with HA's native pill-button style (theme color, white text, ripple) instead of browser-default. Cosmetic only; behaviour unchanged.
Internal
- New
docs/ha-elements-guide.md— contributor/agent reference capturing what we learned aboutha-*Web Component lifecycle, the lazy-load failure mode that hid this bug, and how to verify new elements before shipping. - CI workflow triggers deduplicated — PR commits no longer run validation twice (#169).
Upgrade notes
No config changes. Drop-in patch over 3.6.2.
Full Changelog: v3.6.2...v3.6.3