Announce the Violated Zone - Entry Delay???

[Smarty]

I would like to find a way to determine the zone(s) that cause the Entry Delay to activate.

Here why...
Sometimes, during the middle of the night, we are woke by the "Entrance Delay" beeping of the keypad near the bed (I don't have the system go to full alarm - depending on which sensor has been violated). Usually, I think this is caused by my motions on the screen porch. Even though I have them cross linked, sometimes high winds still trip them (I think).

It would sure be nice to have the system tell me (or it to send serial info to another automation program) which zone(s) cause the keypad to start beeping.

I recall that a recent firmware update will announce the zone(s) that caused the M1 to go into full alarm. As expected, this does not announce anything if only the entry delay is counting down and then de-activated.

I can't figure a way to get this information....serially or otherwise...Ideas???

 

[Smarty]

Bump....

 

[WayneW]

If the entrance delay starts, don't you have to enter a disarm code to prevent a full alarm when the timer expires? Doesn't the log show the zone the violated? Or does that only happen if it goes to full alarm? I have all zone status changes logged in HomeSeer via my.Elk script. There is a stand-alone Elk data decoder that somebody wrote and posted here, but I cannot remember the name right now. If you have a PC available, that would help. Otherwise let the panel go into full alarm once, then see what the log says?

 

[Smarty]

Thanks Wayne,

I do have PowerHome hooked up to my Elk system.

Yes, Powerhome can log all the zone changes (and I do this), but, during the middle of the night when I wake up to my buzzing keypad, I was hoping to have some way of annoucning what zone caused the violation (so I could focus my attention to this area - intruder or otherwise).

The PowerHome Elk log entry shows me the zone changes and shows me when the M1 alarm entry delay trips (all the needed info is there), BUT, there is no way to get PowerHome (or Elk) to announce the zone that caused the M1 to trip (at least not until the M1 goes into full alarm).

 

[WayneW]

The PowerHome Elk log entry shows me the zone changes and shows me when the M1 alarm entry delay trips (all the needed info is there), BUT, there is no way to get PowerHome (or Elk) to announce the zone that caused the M1 to trip (at least not until the M1 goes into full alarm).

If PowerHome knows everything, then you should be able to get it to announce, but I am no PowerHome coding expert. Have you posted on the PH forum?

Might you be able to switch to voice chime mode when armed stay? I don't know if that announces zone changes either when armed, but I can see the logic of wanting to know immediately where the trouble is when something unusual happens when armed & home.

If you think you know which zones it is, you could write Elk rules to talk when those zones are violated when armed.

 

[Smarty]

Yep, I have posted at the PH forum...but I am pretty sure PH can not pull info from the log file (one of the very few things it can't do).

Since I think I do know the affending zones, your rule idea will be useful.

Thanks!

 

[Smarty]

OK, there IS a way to announce the zone that caused the Entry Timer to fire.

I use PowerHome with the Elk (a GREAT combination). See this link:

Powerhome Link

Thanks goes to Dave Howard over at PowerHome