v1.3.7

AlertTicker Card — v1.3.7

🩹 Patch Fix

Test mode preview shows wrong alert when config has group: true alerts (#173)

When at least one alert had group: true, the test mode preview selected the wrong card for any alert at priority 2, 3, or 4. Priority-1 alerts appeared correct and all other priorities showed an unrelated alert.

Root cause: The test mode findIndex ran on the pre-grouping active array to find the previewed alert's position. The grouping pass then collapsed N group: true entities into 1 slide, shifting the positions of every alert that came after the grouped entries. Because _currentIndex was set from the pre-grouping index but _activeAlerts was updated to the post-grouping array, the card rendered the wrong alert.

Priority-1 alerts were unaffected only because they sort before the group: true entries and are not shifted.

Fix: The test mode index resolution now runs after the grouping pass on the final _activeAlerts array, keeping _currentIndex always consistent with what is actually displayed.

No configuration changes needed.

---

✨ New Features

assist action — open the HA voice assistant from any tap/hold slot (#180)

You can now set action: assist on any action slot to open the Home Assistant voice assistant dialog directly from the card.

Supported slots: tap_action, hold_action, double_tap_action, snooze_action, clear_tap_action, clear_hold_action, clear_double_tap_action, group_tap_action, group_hold_action.

YAML example:

tap_action:
  action: assist
  pipeline_id: ""          # optional — leave empty for the HA-preferred pipeline
  start_listening: true    # optional — true opens the mic immediately

Parameters:

Parameter	Type	Default	Description
pipeline_id	string	"" (preferred)	ID of the voice pipeline to use. Leave empty to use the HA-preferred pipeline.
start_listening	boolean	false	When true, the microphone opens immediately without requiring a tap on the mic button.

Both parameters are also available in the visual editor action dropdowns for all supported action slots, with full translations in all 12 languages (it, en, fr, de, nl, vi, ru, da, cs, pt, es, tr).

---

{area} placeholder in alert messages (#166)

You can now use {area} in any message field to display the Home Assistant area name the entity (or its parent device) belongs to.

Example:

alerts:
  - entity: binary_sensor.motion_kitchen
    message: "Motion detected in {area} — {name} is {state}"

Result: Motion detected in Kitchen — Motion Kitchen is on

How it resolves:

1. Checks if the entity itself has an area assigned in HA
2. Falls back to the parent device's area if the entity has none
3. Returns an empty string if no area is assigned

Supported fields: message, secondary_text, tts_message, push_notify_title, push_notify_message, group_expanded_message — and any field that accepts placeholders. The overlay banner engine also resolves {area} correctly.

---

📦 Update Instructions

1. Download alert-ticker-card.js and alert-ticker-card-editor.js
2. Replace both files in your www/ folder (or the path you set in Resources)
3. Hard-reload the browser: Ctrl+Shift+R / Cmd+Shift+R

HACS users: update from the HACS panel — no manual steps needed.

---

Full changelog: CHANGELOG.md

---

☕ If this card saves you time, consider buying me a coffee — it keeps the updates coming!