F3 key turns ON Output 9

v1rtu0s1ty

Senior Member
Please see my rule. Not sure why it is turning on OUTPUT 9 when I press F3 key on keypad.
 
Is there something I missed?
 
Btw, Output 9 to 13 are the ports where my Orbit valves are connected. It's the M1RB board.
 

Attachments

  • Screen Shot 2013-09-01 at 8.59.31 PM.png
    Screen Shot 2013-09-01 at 8.59.31 PM.png
    8.7 KB · Views: 20
  • Screen Shot 2013-09-01 at 9.00.35 PM.png
    Screen Shot 2013-09-01 at 9.00.35 PM.png
    8.7 KB · Views: 18
From the Screen shot of your keypad you have the F3 working an Automation task as well and i suspect its creating a conflict. Try setting the Event Activation to 00 - Disabled and see if it works, or why not include your rule in Automation Task 02 which you already have mapped? Also have you manually tried to activate the output through just the keypad automation menu? Does it work?
 
I'm actually a bit confused with Automation Task. When you said "why not include your rule in automation task 02", where can I find this automation task 02 in RP?
 
I figured it out. :)
 
I tried both solutions and the former worked very well.  That's the one where Event Activation was set to 00 - Disabled.
With the Automation Task 2, it still turned on OUTPUT 9 and OUTPUT 120.
 
I kept the former solution.
 
I'm still having some minor issues with my ELK and it only happened few days ago. I have to press ARM STAY three times before it will get armed.
 
I'd upgrade firmware and do a send-all if it were me - some bits may have gotten crossed in the onboard memory.
 
I've already done that last night, no luck. On my other thread, someone suggested to me to replace the battery. I haven't done it yet.
 
Just following your rules between your two posts, as posted here, they aren't quite finished...  the above was correct - you were triggering the very task you were essentially trying to disable, which you have fixed now.
 
The next thing is to check for output 120 on the start of your Task 2 rules with an "And Output 120 is OFF" then begin watering rules...
 
At this point, the next thing I suspect is too much busy-ness going on with the Elk.  I might consider disabling all rules and sending (you'll start getting the conflict again but that's better than losing your rules) and see how it acts then.
 
Will try that.
 
Btw, I've also fixed the Automation Task. I was wrong with my configuraiton. I put Automation Task #2 while the one I really want is Task #3. I just realized that
2001 Automation is for Task 1
2002 Automation is for Task 2
2003 Automation is for Task 3
 
I wasn't aware until this morning. :)
 
Back
Top