v1.5.0 – Time Formats, Milestones & Entity UX

v1.5.0 – Time Formats, Milestones & Entity UX

This release adds a major upgrade to time presentation (including human-readable formats), introduces a milestone-based progress mode, and improves entity handling and editor UX across multiple timer sources.

🚀 New Features

• Human-readable time formats: New time_format options allow you to display remaining time as:
  • human_compact, human_short, human_natural
  • Plus numeric formats like hms, hm, ss, and dhms.
• Configurable unit ordering: New time_format_units lets you choose which units to show (and in what order), e.g. years,months,weeks,days,hours,minutes,seconds.
• Milestone-based progress mode: Added progress_mode: milestones (bar styles only), rendering segmented “unit milestones” (with optional pulsing on the active segment).
  • New options: milestone_unit (auto|none|years|months|weeks|days|hours|minutes|seconds) and milestone_pulse (default true).
• New entity mode: minutes_attr: Support timers based on an entity attribute that contains “minutes remaining / minutes to arrival” style data (configurable via minutes_attr).
• Per-entity expired subtitle override: Entity configs can override expired_subtitle so each timer source can show a custom “Time’s up” message.

✨ Improvements

• Better finished/idle handling across sources: Expanded render-state logic supports clearer idle, paused, and finished presentation, including “Time’s up – X ago” style messaging.
• Smarter duration parsing: Improved parsing of timer durations (including support for ISO-like PT#H#M#S parsing via _toMs).
• Expanded localization: Translation keys now cover additional time units and formats (weeks/months/years and short unit labels), enabling better human-readable formatting across languages.
• Editor upgrades: Added UI controls for:
  • Time format
  • Unit order
  • Progress milestones settings (when milestones mode is selected)
  • Minutes attribute configuration for minutes_attr entities
  • Conditional display of relevant fields to reduce clutter

📡 MQTT Events

• Richer event payloads: MQTT events include remaining and duration (milliseconds) at the time of the event, enabling more precise automations.
• Broader event coverage: The card publishes events for key timer interactions (started, expired, cancelled, paused, resumed, snoozed).
• Improved publish consistency: Events can publish even when storage is local, as long as an MQTT sensor (default_timer_entity: sensor.*) is configured.

🐛 Bug Fixes

• Improved auto-detection coverage: Auto mode detection now recognizes attribute-driven minute timers and additional timestamp patterns more reliably.
• More consistent progress rendering: Unified progress handling across bar/fill/circle styles and new modes to avoid mismatched progress visuals.