v1.3.11 — Countdown fix + overlay lazy-init fix + rotation + timestamp operators

AlertTicker Card — v1.3.11

Two bug fixes and three community-requested features — all from reports and ideas in the last week.

🐛 Fixes

Countdown / Hourglass bar no longer "slides" between alerts

Reported by @shashankmittal (#220) — when two alerts both used the countdown or hourglass theme, the progress bar smoothly interpolated between their two unrelated remaining-time values each time the card cycled. Looked like the countdown was moving backward or forward. Now the bar jumps straight to the current alert's value on swap and keeps ticking smoothly within each alert.

Global overlay now works without visiting the card's view first

Reported by @ThomDyson (#222) — if your dashboard had the card hidden on a view you don't normally visit, the overlay banner wouldn't fire until you'd visited that view at least once per browser session. Fixed by persisting overlay-enabled registrations to localStorage so the watcher starts immediately on page load, independent of which view is active.

✨ What's new

🧷 Non-dismissible overlay

Thanks to @ThomDyson (discussion #221) — new Allow manual dismissal toggle in the Overlay tab. When off, the banner never auto-hides and shows no close button — it stays until the triggering condition clears. Perfect for kiosk mode, wall panels, or dashboards shared with casual users where you don't want anyone dismissing critical alerts.

🔁 Overlay rotation with 1/N counter

Also from @ThomDyson (discussion #221) — when multiple alerts are active simultaneously, the overlay banner now cycles through them with a 1/3, 2/3, 3/3... counter displayed in the top-right of the toast. Interval configurable from 1-60 seconds (default 5). Rotation list auto-refreshes as alerts become active or clear.

⏳ Timestamp operators: older and newer

Thanks to @sciurius (#223) — two new comparison operators that compare an entity's timestamp value against the current time.

• older than (sec) — fires when the entity's timestamp is more than N seconds in the past. Example: "sensor hasn't updated in 10 minutes" with older + 600.
• newer than (sec) — fires when the entity's timestamp is less than N seconds ago.

Works with ISO 8601 strings (e.g. 2026-10-03T14:00:00+00:00) and unix epoch (seconds or milliseconds). Auto re-evaluates every 30 seconds since the comparison depends on now(), not on entity updates. Available in both the main alert operator dropdown and in extra AND/OR conditions. Translated in all 12 languages.

📥 Upgrade

Update via HACS, then clear browser cache (Ctrl+F5).

🙏 Thanks

• @shashankmittal — for the countdown bar report with such a clear video
• @ThomDyson — for both the overlay lazy-init report and the three overlay feature ideas
• @sciurius — for the timestamp operator request with the nicely-written proposal