Programing F-key to alert of zone activity

So I am trying to set up rules to set up an function key to alert me of motion in a part of the house.
 
Here is what i have:
 
Whenever f4 key on any keypad activates
  and output 001 state is off
    then turn output 001 on for 2 hrs
 
Whenever f4 key on any keypad activates
  and output 001 state is on
   then turn output 001 off
 
Whenever motion XXX becomes not secure
  and output 001 state is on
    then announce say time (vm238) (For example)
 
In outputs, output 001, the show box is checked. No voice description (not sure what voice description is for).
 
I am a little confused as to what to program the f4 key to on the keypad drop down menu. I tried various options there.
 
For some reason it is not working. Any ideas?
 
 
 

Have you tried an output other than Output 1?  Say a phantom output like Output 128?  I don't know for sure if using Output 1 has anything to do with your problem, but it might be a special case in that Output 1 is the audio output and I'm thinking it might not be treated like other "normal" outputs.
 
 
Some other things to check... the volume levels for Out1 and various Global System settings G14 through G25.

I put it on output 100 instead. But still now working. I will check volumes.
 
Do you know what the setting on keypad should be?

You taught me something new by pointing out the rule "Whenever f4 key on any keypad activates".
I've always dealt with f-keys by assigning tasks to each f-key in the keypad programming, then having a rule saying "whenever task x acvitates...".
I suppose both methods work the same.
But now you've got me wondering why I would use one method over the other.

rexwilson said:

You taught me something new by pointing out the rule "Whenever f4 key on any keypad activates".
I've always dealt with f-keys by assigning tasks to each f-key in the keypad programming, then having a rule saying "whenever task x acvitates...".
I suppose both methods work the same.
But now you've got me wondering why I would use one method over the other.

Click to expand...

 
You can do things either way.  Think of a task as similar to a macro or subroutine.   If you have a set of actions that you want to trigger in several different situations, then defining them as a task allows you to list them just once in the task definition, rather than over and over again in each rule that you want to trigger them.