Don't repeat chime messages for x amount of time.

[rayzor]

Hi,
 
I don't mind the voice messages 'Garage Door', 'Front Door', 'Basement Door', etc..
 
The only time they are annoying to me is when I have to run into the garage to grab something, and it says it as I go out and as I come back in. Same goes with the front door.
 
I would like to set it up so that after announcing the zone/door that it doesn't repeat it for 1 minute (customizable).
 
Any idea how to accomplish that?

 

[Desert_AIP]

On an HAI I'd define a flag for each zone, e.g., Garage Door Voice Flag.
When the door opens it would check if the flag was off, if it was off it would make the announcement and turn the flag on for the period of time I wanted, e.g., 30 minutes.

The next time the door opened, if the flag was on the announcement wouldn't be made.

You could also have the flag timer reset each time the announcement was made by splitting up the voice and flag/timer blocks.

 

[BraveSirRobbin]

I'm hoping one of our forum members can think of a way easier than the one I'm about to describe.
 
First hand, it's not a pretty solution by any extent, but here it goes.
 
You name an output that isn't in use with hardware (Say Front Door Timer).
 
Write a rule so when that zone is violated and the system is not armed, turn on Front Door Timer for One Minute (Restart if already started option checked).
 
Create a custom voice greeting that says something like 'Front Door Open', Call it Front Door Msg
 
Write a rule that when the front door is violated, and the system is not armed, and the Front Door Timer is not on, Then speak 'Front Door Msg'.

 

[Del91574]

I was looking at a the extreme opposite, which would be to drive outputs via tasks and then have the rules look at those to determine whether or not to chime.
 
It's not going to be an easy affair.

 

[BraveSirRobbin]

I was looking at a the extreme opposite, which would be to drive outputs via tasks and then have the rules look at those to determine whether or not to chime.
 
It's not going to be an easy affair.

Details?

 

[Del91574]

The down and dirty way is to use hardwired outputs on certain points or the speakers themselves to inhibit. The software methods I'm thinking of would need a bunch of testing before I'd toss them out

 

[drvnbysound]

I was understanding this thread to ask the same question:
 
http://cocoontech.com/forums/topic/26720-limiting-repetitive-door-chimes-elk-m1/

 

[rayzor]

I was understanding this thread to ask the same question:
 
http://cocoontech.com/forums/topic/26720-limiting-repetitive-door-chimes-elk-m1/

 
Great minds think alike! Doesn't seem like their question was answered either. I see a couple of methodologies above so I will play around with them and see what seems to be easiest/cleanest to setup.

 

[BraveSirRobbin]

Hmmm, I'm not sure my method will work, will have to play with this re-reading this thread.
 
The main problem is the timer and the comparison rule start with the same trigger, so this most likely will not work
 
Man, in HomeSeer this is so easy, you just say do not run event after xx minutes of triggering (I have my announcements through HomeSeer as the voice engine of the PC is clearer than the Elk's and I do this very same thing with not repeating door opens after five minutes of the first one announcing).