wdeertz
Active Member
I have an OP2 4.0b with 2 LV33A001 keypads. In PC Access I have both consoles set "yes" for "enable audit exit delay" and in areas section "yes" for "audible exit alarm". In the console "sounder" is set to "yes" and I know the keypad sounder works as the keys click when I press the button.
When I arm my garage area "away" the keypad used to "beep, beep, beep... and then beep faster the last few seconds before arming, but recently this has stopped. I don't recall changing any settings before this stopped working. Now when I arm my garage the keypad is silent and when it arms itself the siren makes one quick whoop sound. I rebooted the entire system to see if this would help but no change. Any ideas what may have gone wrong? I don't think its a hardware issue as the keypad keys click when pressed so the sounder appears to be working.
Also, on the garage I have an extra long delay to allow me to deactivate the alarm when arriving home. The keypad used to beep to warn me the alarm is active. Now I only get a red flashing light on the keypad and no sound that a delayed alarm is imminent. Any ideas what's going on here.
No hardware, software or firmware changes prior to this weird behavior (so far as I am aware).
When I arm my garage area "away" the keypad used to "beep, beep, beep... and then beep faster the last few seconds before arming, but recently this has stopped. I don't recall changing any settings before this stopped working. Now when I arm my garage the keypad is silent and when it arms itself the siren makes one quick whoop sound. I rebooted the entire system to see if this would help but no change. Any ideas what may have gone wrong? I don't think its a hardware issue as the keypad keys click when pressed so the sounder appears to be working.
Also, on the garage I have an extra long delay to allow me to deactivate the alarm when arriving home. The keypad used to beep to warn me the alarm is active. Now I only get a red flashing light on the keypad and no sound that a delayed alarm is imminent. Any ideas what's going on here.
No hardware, software or firmware changes prior to this weird behavior (so far as I am aware).