-
|
Hi! 👋 Quick note to say I love what you've built here. Found AlertTicker via Smart Home I'm the developer of PositionGuard, a privacy-first
(Open source if you're curious about the entity structure: I plugged AlertTicker into my dashboard pointing at the binary sensors and got One question I'd love your take on, since this is your domain: AlertTicker's model is "alert persists while the entity is in the trigger How would you approach using AlertTicker for transition events — "someone Genuinely curious what the right design pattern is for moment-style alerts — Chris |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Hi @clundin, great use case and thanks for the detailed question! You're right that AlertTicker's default model is "sustained state" — the alert stays visible as long as the entity is active. But you can get moment-based / arrival-only notifications today without any helper variable, using auto_dismiss_after: alerts:
Sensor goes off → on — alert fires and shows for 30 seconds If you also want a departure notification, combine it with on_change: alerts:
No separate automation or helper variable needed. |
Beta Was this translation helpful? Give feedback.
Hi @clundin, great use case and thanks for the detailed question!
You're right that AlertTicker's default model is "sustained state" — the alert stays visible as long as the entity is active. But you can get moment-based / arrival-only notifications today without any helper variable, using auto_dismiss_after:
alerts:
state: "on"
message: "🏠 Alice just arrived home"
theme: success
auto_dismiss_after: 30 # alert disappears after 30 s even if sensor stays "on"
How it behaves:
Sensor goes off → on — alert fires and shows for 30 seconds
After 30 s — alert auto-dismisses, even though Alice is still home
Sensor goes on → off (she leaves) — no alert (stat…