Replies: 3 comments 2 replies
-
Are you looking for the last zone faulted before the alarm was tripped or the last zone faulted? I think those two might be different since theoretically I'd imagine it's possible for other zones to fault while the alarm is active. |
Beta Was this translation helpful? Give feedback.
-
I was thinking about this a bit more and think it might be better to just implement it with an automation and store the state in something like a text helper. Something like:
That would also allow you to tune it to your needs. E.g., use a condition to only update it if the zone is faulted when the alarm is armed. |
Beta Was this translation helpful? Give feedback.
-
Doing this as a template should work. I've edited this post like 4 times now but here's a generic solution that should work for everyone: {{
expand(integration_entities('envisalink_new')) |
selectattr('attributes.last_tripped_time','defined') |
rejectattr('attributes.last_tripped_time','none') |
sort(attribute='attributes.last_tripped_time', reverse=true) |
map(attribute='name') |
first
}}
This returns the friendly name. If you want entity id just change that map line and replace name with entity_id |
Beta Was this translation helpful? Give feedback.
-
I have been trying to set up a notification that tells me what zone tripped the alarm. The problem I am running into is that it's pretty difficult to keep track of what zone was tripped since there could be entry delay or the zone could've been closed before the alarm actually goes off. Would be nice to have an attribute that states whatever last zone was opened so that it can be used in automations in the event of an alarm.
Beta Was this translation helpful? Give feedback.
All reactions