Jump to content

Notification of alarms - has anyone done this yet?


Traditore

Recommended Posts

Posted

...

If

        Elk Area 'Home' 'Alarm State' is Fire Alarm

     Or Elk Area 'Home' 'Alarm State' is Medical Alarm

     Or Elk Area 'Home' 'Alarm State' is Police Alarm

     Or Elk Area 'Home' 'Alarm State' is Burglar Alarm

     Or Elk Area 'Home' 'Alarm State' is Carbon Monoxide Alarm

     Or Elk Area 'Home' 'Alarm State' is Emergency Alarm

     Or Elk Area 'Home' 'Alarm State' is Freezer Alarm

     Or Elk Area 'Home' 'Alarm State' is Gas Alarm

     Or Elk Area 'Home' 'Alarm State' is Heat Alarm

     Or Elk Area 'Home' 'Alarm State' is Water Alarm

    And $Active_Alarm is 0

 

Then

        Send Notification to 'Phone' content 'Alarm'

...

 

Here is the notification. I tried both methods without luck.

 

ACTIVE ALARM. ${sys.time12} ${alert.date}

${alert.control} : ${alert.action}

${elk.zone.#.name}. ${elk.zone.#.status}.

${elk.area.1.alarmState}

 

Hi NHWA,

 

The conditions you are testing for are Area conditions, not Zone conditions.  Therefore, the ${elk.zone.....} variables will evaluate to nothing.

 

In this case, I think you are looking for ${elk.area.#.alarmState}.  In fact, you wouldn't even need to use the '#', you could just specify the area number for 'Home' e.g. ${elk.area.1.alarmState}

Posted

To answer Michel and to echo what NHWA is saying;

When I use # in the notification and an alarm trips, the message returns a blank

Eg. ${elk.zone.#.name} = null

 

When I substitute the # with an appropriate number, the message returns the correct zone name

Eg. ${elk.zone.1.name} = "Frt Door"

 

 

 

 

Sent from my iPhone using Tapatalk

Posted

tandar

 

The post immediately before yours from UDI indicates why NHWA Program is not working.   The Program is triggered by Area alarms rather than a Zone alarms.  This is why a Zone number of # is not resolved.

 

an you post the Program that is not working. 

Posted

Thanks Lee and Chris.

That makes more sense.  What's throwing me (and I think NHWA) is that WayneW posted a reply on 28 April that shows a program that passes the zone based on an area alarm.

WayneW - if you are still monitoring this, would you mind confirming that the program you posted actually passes the alarmed zone?

 

Thanks,

Tandar

Posted

I apoligize for the confusion folks.  In post #3, I posted what I have.  Unfortunately, I don't recall where I got it and apparently I never tested it.  I also get alarm notifications via HomeSeer & NextAlarm, so I never noticed that the resulting message from the ISY was NOT what I was expecting.  I have edited post #3 to avoid further confusion.  shannong sort-of confirmed my post in #4.  Then we got sidetracked with ISY version differences as a possibility. In my post #17, I ruled out the ISY firmware version as a difference.

 

In my post #14, I tried to clarify that I wasn't 100% sure of my original post #3, but I wasn't in a position to test it then.  I did post some specific samples of glass break zone reporting, but I now realize that is like apples and oranges as the trigger programs are totally different.

 

JSchumann then mentioned the use of ${alert.control} : ${alert.action}, which is apparently undocumented?  Does anybody know more about those?

 

So, my known working program (for zones that are 24/7) is

If
        Elk Zone 'GlassBrk-Family' is not Normal
     Or Elk Zone 'GlassBrk-Guest1' is not Normal
     Or Elk Zone 'GlassBrk-Guest2' is not Normal
     Or Elk Zone 'GlassBrk-Living' is not Normal
     Or Elk Zone 'GlassBrk-MastBed' is not Normal
     Or Elk Zone 'GlassBrk-Office' is not Normal
 
Then
        Send Notification to 'email & cell' content 'Elk Glass Break'
 
Else
   - No Actions - (To add one, press 'Action')

if we tweak that to something like

*** UNTESTED PSEUDOCODE ***
If
        (Elk Zone 'GlassBrk-Family' is not Normal
     Or Elk Zone 'GlassBrk-Guest1' is not Normal
     Or Elk Zone 'GlassBrk-Guest2' is not Normal
     Or Elk Zone 'GlassBrk-Living' is not Normal
     Or Elk Zone 'GlassBrk-MastBed' is not Normal
     Or Elk Zone 'GlassBrk-Office' is not Normal
     Or etc, etc for each zone)  - a PITA to setup, but it only requires one program instead of 50 programs
AND
        (Elk Area 'Home' 'Alarm State' is Fire Alarm
     Or Elk Area 'Home' 'Alarm State' is Medical Alarm
     Or Elk Area 'Home' 'Alarm State' is Police Alarm
     Or Elk Area 'Home' 'Alarm State' is Burglar Alarm
     Or Elk Area 'Home' 'Alarm State' is Carbon Monoxide Alarm
     Or Elk Area 'Home' 'Alarm State' is Emergency Alarm
     Or Elk Area 'Home' 'Alarm State' is Freezer Alarm
     Or Elk Area 'Home' 'Alarm State' is Gas Alarm
     Or Elk Area 'Home' 'Alarm State' is Heat Alarm
     Or Elk Area 'Home' 'Alarm State' is Water Alarm)
 
Then
        Send Notification to 'email & cell' content 'Elk ALARM'
 
Else
   - No Actions - (To add one, press 'Action')

will that pass the zone number?
 
 

 

 

 
 

Posted

Wayne,

Thanks for clearing this up.  

I just have to dig in now and learn the difference between the status:  "is not Normal", "Violated", "Trouble", etc

 

 

 
 

  • 2 weeks later...
Posted

I am not familiar with that syntax and cannot find it in the wiki.  Can you provide more details please?

 

What would the pros & cons be versus ${elk.zone.#.name}. ${elk.zone.#.status}.

I found them in the WIKI during a search, but can't find them anymore.  Michael says they are documented in the WIKI variables area, but I don't see them.  I think they got overwritten.

 

Anyway, after more extensive testing, they only work to identify the area (not the zone in the area).

 

What I ended up doing was putting this into my e-mail customization:

${sys.time12}

${elk.zone.2.name} - ${elk.zone.2.status}

${elk.zone.3.name} - ${elk.zone.3.status}

${elk.zone.4.name} - ${elk.zone.4.status}

${elk.zone.5.name} - ${elk.zone.5.status}

${elk.zone.6.name} - ${elk.zone.6.status}

${elk.zone.7.name} - ${elk.zone.7.status}

${elk.zone.9.name} - ${elk.zone.9.status}

${elk.zone.10.name} - ${elk.zone.10.status}

${elk.zone.11.name} - ${elk.zone.11.status}

${elk.zone.193.name} - ${elk.zone.193.status}

 

And looking for the tripped zone status on the e-mail.  I know, brute force, but until we can figure out how to pass the parameter we are stuck.

Posted

You can have the ISY insert the violated zone with a variable, and I do it almost exactly the same as WayneW instead of writing a program for each zone. It's working for me.

OK, send an example program, thanks!

  • 2 weeks later...
Posted

 

if we tweak that to something like

*** UNTESTED PSEUDOCODE ***
If
        (Elk Zone 'GlassBrk-Family' is not Normal
     Or Elk Zone 'GlassBrk-Guest1' is not Normal
     Or Elk Zone 'GlassBrk-Guest2' is not Normal
     Or Elk Zone 'GlassBrk-Living' is not Normal
     Or Elk Zone 'GlassBrk-MastBed' is not Normal
     Or Elk Zone 'GlassBrk-Office' is not Normal
     Or etc, etc for each zone)  - a PITA to setup, but it only requires one program instead of 50 programs
AND
        (Elk Area 'Home' 'Alarm State' is Fire Alarm
     Or Elk Area 'Home' 'Alarm State' is Medical Alarm
     Or Elk Area 'Home' 'Alarm State' is Police Alarm
     Or Elk Area 'Home' 'Alarm State' is Burglar Alarm
     Or Elk Area 'Home' 'Alarm State' is Carbon Monoxide Alarm
     Or Elk Area 'Home' 'Alarm State' is Emergency Alarm
     Or Elk Area 'Home' 'Alarm State' is Freezer Alarm
     Or Elk Area 'Home' 'Alarm State' is Gas Alarm
     Or Elk Area 'Home' 'Alarm State' is Heat Alarm
     Or Elk Area 'Home' 'Alarm State' is Water Alarm)
 
Then
        Send Notification to 'email & cell' content 'Elk ALARM'
 
Else
   - No Actions - (To add one, press 'Action')

will that pass the zone number?

 

the example program at the bottom of

http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:ELK_Security_Module#Program_Examples

implies that this can be done.  I will try to get time to test it soon.  It has to be when I am home and the dog is not as the siren or a smoke alarm drives him crazy.

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Forum Statistics

    • Total Topics
      37k
    • Total Posts
      371.4k
×
×
  • Create New...