Program not working as expected

[mikek]

I originally posted this in the Elk board, but it seems like the problem is actually ISY related. 

What I want to do is receive an email alert when any of my Elk wireless zones report status as "trouble" (not "violated"). Simple code, looks like this (for one of the zones):

If
        Elk Zone 'Office-WestWind' is Trouble
 Then
        Send Notification to 'Me'
 Else
        Wait  0 seconds
 

However, instead of receiving a "trouble" alert I get this:

Security Zone 'Office-WestWind' Violated 

Any ideas?

 

[oberkc]

The syntax does not look familiar to me, but the first thing I would look at is the content of your notification called out in THEN action.  What notification are you sending?

As an aside, why are you waiting zero seconds in the ELSE action?

[jfai]

What is the configuration of the notification?

[mikek]

2 hours ago, jfai said:

What is the configuration of the notification?

Since I'm just trying to see if this concept ("trouble" notification) works, I'm simply using the default subject (${alert.subject) and body (${alert.body}) for now.

My programs and notifications work fine for a true "violated" status. But 'trouble" and "violated" are two unique statuses. 

[oberkc]

unfortunately, I don't use an elk.  Were this me, however, I would be experimenting a bit.  I would have two programs: one triggered by "trouble" and a second triggered by "violated".  I would watch to see when each program is triggered and whether it is consistent with actual elk status.  If so, then I would simply create specific notifications for each type of occurrence and be happy.

[mikek]

20 minutes ago, oberkc said:

unfortunately, I don't use an elk.  Were this me, however, I would be experimenting a bit.  I would have two programs: one triggered by "trouble" and a second triggered by "violated".  I would watch to see when each program is triggered and whether it is consistent with actual elk status.  If so, then I would simply create specific notifications for each type of occurrence and be happy.

Thanks for your input. But I've already done that. According to Elk itself, status is trouble. According to ISY, status is trouble. According to alert, status is violated.

[oberkc]

10 hours ago, mikek said:

Thanks for your input. But I've already done that. According to Elk itself, status is trouble. According to ISY, status is trouble. According to alert, status is violated.

Yes, but you also said you use the "default" alerts.  (Unfortunately, you have not shown the notification or program.)

Rather than using the default text, why not create your own notification, using whatever language you desire?  Trigger this notification from a "trouble" condition.

[larryllix]

I don't use an Elk either but from the alarm panels I have used "Trouble" means the circuit is broken (EoL resistor is not connected or loop is broken)  and "Violated" means the circuit has been tripped.

[mikek]

46 minutes ago, larryllix said:

I don't use an Elk either but from the alarm panels I have used "Trouble" means the circuit is broken (EoL resistor is not connected or loop is broken)  and "Violated" means the circuit has been tripped.

Yes, a low battery in a wireless sensor also reports as trouble. That's what I'm trying to accomplish with my notifications - a low battery alert. I already have my "violated" programs running and notifying as they should.

[MrBill]

Configuration Tab > EMails/Notifications tab > Customization.

Create your own specific trouble email.  Using Elk Variable substitution (or non-elk for that matter--also on the same wiki page) as needed.

Use your new custom content in the program.

[mikek]

2 hours ago, MrBill said:

Configuration Tab > EMails/Notifications tab > Customization.

Create your own specific trouble email.  Using Elk Variable substitution (or non-elk for that matter--also on the same wiki page) as needed.

Use your new custom content in the program.

? That did it! Thanks very much!