When using overlay_mode: true globally on a card instance, all triggered alerts are pushed to the overlay canvas. For users who mix highly critical environmental alarms (e.g., severe weather, system outages) with passive household tracking (e.g., motion sensors, appliance cycles), the overlay canvas becomes cluttered with low-urgency events.
It would be ideal to introduce a block-level override parameter for individual alert items—something like overlay: false (defaulting to true if the card has global overlays enabled). Alternatively, a global card property like overlay_min_priority: 2 would allow users to gate overlay popups by their assigned priority levels while still letting low-priority items cycle through the standard inline card ticker loop.
Splitting configurations into multiple distinct alert-ticker-card instances is not ideal, this adds unnecessary dashboard maintenance and overhead.
When using overlay_mode: true globally on a card instance, all triggered alerts are pushed to the overlay canvas. For users who mix highly critical environmental alarms (e.g., severe weather, system outages) with passive household tracking (e.g., motion sensors, appliance cycles), the overlay canvas becomes cluttered with low-urgency events.
It would be ideal to introduce a block-level override parameter for individual alert items—something like overlay: false (defaulting to true if the card has global overlays enabled). Alternatively, a global card property like overlay_min_priority: 2 would allow users to gate overlay popups by their assigned priority levels while still letting low-priority items cycle through the standard inline card ticker loop.
Splitting configurations into multiple distinct alert-ticker-card instances is not ideal, this adds unnecessary dashboard maintenance and overhead.