| Posted: Tuesday Mar 31st, 2015 12:03 pm |
|
1st Post |
mikeinnc
Member
| Joined: | Wednesday Mar 18th, 2015 |
| Location: | Perth, Australia |
| Posts: | 73 |
| Status: |
Offline
|
back to top
|
I want to stop my keypad - irritatingly! - announcing that one or two type 18 PIRs in my entry path have triggered after I start AWAY arming. I have specifically defined the PIRs as being in the entry path and they perform as expected on entry ie not triggering an alarm within the defined entry time. I have initially attempted to define logic to turn the announcements off but that didn't work. In desperation, I now have a response with a single line of code - "Skip Announcement" (codes 23, 255) and I have unconditionally attached that response to the two PIRs in question as an 'ON Response'. However, the instant I press the AWAY arm button, the keypad starts announcing that the PIRs have 'fired' regardless of the fact they have that "Skip Announcement" action applied. Well, hello - of course they have activated - I'm in their arc, and I really don't need to be constantly told that as I leave!! Please advise what is wrong? Is the 'Skip Announcement' conditional on something else? (I can't see that it is from the documentation.) I should add that they ONLY start announcing when the AWAY arm button has been pressed - not during 'Security Off'. Many thanks.
|
| Posted: Tuesday Mar 31st, 2015 12:40 pm |
|
2nd Post |
CytechMartin
Cytech
| Joined: | Monday Oct 13th, 2014 |
| Location: | |
| Posts: | 47 |
| Status: |
Offline
|
back to top
|
when you press the AWAY arm button, you are in the detecting range of PIR sensors. The keypad keep announcing the Zone name is to tell you that this zone is open. Just a reminder for you. e.g. when you arm to AWAY mode, the window is open, it will tell you the window is open, this is for safety reason.
I think to solve your problem, you may try to omit those PIR zones in Start Arming Response, it is to ignore those PIR zones, no matter they are open or close will not be announced on keypad when you are arming. Then in AWAY mode, you unbypass the those PIR zones so that it will work as it should be in AWAY mode.
AWAY, Start Arming response can be found in Events-->Miscellaneous Events.
To omit and unbypass zones, you may use "Append new actions"-->"Input"-->'Omit input" or "Unbypass zone"
Last edited on Tuesday Mar 31st, 2015 01:05 pm by CytechMartin
|
| Posted: Tuesday Mar 31st, 2015 12:58 pm |
|
3rd Post |
mikeinnc
Member
| Joined: | Wednesday Mar 18th, 2015 |
| Location: | Perth, Australia |
| Posts: | 73 |
| Status: |
Offline
|
back to top
|
Thanks for your quick reply.
"When you press the AWAY arm button, you are in the detecting range of PIR sensors. The keypad keep announcing the Zone name is to tell you that this zone is open. Just a reminder for you. e.g. when you arm to AWAY mode, the window is open, it will tell you the window is open, this is for safety reason."
I understand this, and it is, of course why I don't want to turn off all announcements. It is important that I know that there are unsecured zones that I may have forgotten. But it still doesn't answer my question. Why does the keypad ignore the "announcement off" response on these specific sensors? I KNOW these sensors are activated - as I said, I'm under them, so of course they will activate! But - I should be able to turn specific announcements off - shouldn't I? Especially as the system is arming ie before it is fully armed. I can see that your reply will probably work - but it seems more like a kludge than an elegant solution. It still seems that it would be far better to just turn the announcements off on SPECIFIC zones ie those in the entry/exit zone. And all the indications in the documentation are that "Skip Announcement" response does that. But it doesn't!Last edited on Tuesday Mar 31st, 2015 01:00 pm by mikeinnc
|
| Posted: Tuesday Mar 31st, 2015 01:30 pm |
|
4th Post |
mikeinnc
Member
| Joined: | Wednesday Mar 18th, 2015 |
| Location: | Perth, Australia |
| Posts: | 73 |
| Status: |
Offline
|
back to top
|
Just another point. The Comfigurator mouse-over help text on the 'Skip Announcement of Zone' action under Keypad says:
"When assigned to a zone response, prevents the zone from being announced when activated. This may be used to stop zone announcements for zones on the entry path, in order to avoid disturbing members of the household who may be sleeping. Entry and exit zones are announced on the keypad by default."
I think that absolutely defines what I would expect the Skip Announcement' action to do - and what I want to do.
|
| Posted: Tuesday Mar 31st, 2015 01:35 pm |
|
5th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5866 |
| Status: |
Offline
|
back to top
|
Skip announcement does not work when arming the system, it works when there is no arming or no anouncement
When the zone is in Entry path, the announcement of the open zone is slower and the beeps are also slow instead of fast compared to non-entry path
Open zones have to be announced during exit arming because it may be possible for the PIR to be faulty thus leading to an Arm Failure
You should not hear many announcements from the PIR during exit. Normaly only 1 announcement unless your exit route is very long
A better alternative to bypassing the zones in security off is to use the Start Arming Response to bypass the zones and unbypass the zones in the Away Mode response
This way the zones are bypased only while arming and not at other times when they may be needed to trigger a Response
|
| Posted: Wednesday Apr 1st, 2015 05:36 pm |
|
6th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5866 |
| Status: |
Offline
|
back to top
|
The skip announcement does not affect the zone announcement during exit arming to away mode. That is because the exit announcement is done by a different task than the normal zone detection, and cannot be disabled except if you bypass the zone in the start arming response as suggested
|
| Posted: Thursday Apr 2nd, 2015 05:29 am |
|
7th Post |
mikeinnc
Member
| Joined: | Wednesday Mar 18th, 2015 |
| Location: | Perth, Australia |
| Posts: | 73 |
| Status: |
Offline
|
back to top
|
Many thanks for that confirmation. I won't deny that I am disappointed by it. It would appear that the 'skip announcement' action has limited application if it can't be used to turn off announcements that do NOT reflect the universal 'announcement turn-off action' in the zone application. Indeed, as I have previously noted (and as you indicated in your earlier response that has now been deleted), the comments in the 'action codes' manual together with the mouse-over help for the action, actually seem to indicate that the 'skip announcements' action is designed to work in exactly that area you claim it doesn't. I think that those comments need revisiting - as they stand, they are clearly confusing, and may even be considered incorrect.
As the zone announcements whilst arming are 'performed by a different task', may I request that you look at a future firmware modification that does, indeed, allow the 'skip announcement' action to work as I suspect it was originally designed to. I'm sure this would make the functionality far better!
Meanwhile, I'll do as you suggest and temporarily bypass the specific zones whilst the system is arming.
|
| Posted: Thursday Apr 2nd, 2015 08:19 am |
|
8th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5866 |
| Status: |
Offline
|
back to top
|
It can certainly be considered. The help text wil be amended
Can you share how the announcement of motion during arming is problematic for you so we can understand the benefits?
How many times does it announce many times in your exit route?
are there many such motion sensors on the exit route?
|
| Posted: Thursday Apr 2nd, 2015 08:43 am |
|
9th Post |
mikeinnc
Member
| Joined: | Wednesday Mar 18th, 2015 |
| Location: | Perth, Australia |
| Posts: | 73 |
| Status: |
Offline
|
back to top
|
I believe that the major issue is an "overload" of information. As Martin indicated in his reply, one of the most important functions of the announcement is to advise the user that a door or window not in the exit path has been left open, so that the user may close it before leaving. However, when that announcement is also being mixed in with - entirely superfluous - announcements that one or two PIRs are activated because they are in the exit path, there is a real chance the 'open' announcement will be ignored, and create a major security breach. I strongly believe that only announcements that indicate a real security breach should be allowed - not 'routine' ones. Users will soon learn to ignore such announcements - and may also overlook an announcement that IS required. That's human nature!
In my system, I have two PIRs in the front door exit path, and three (the two plus one other) in the garage door exit path. If a PIR activates, it will often announce it more than once. In addition, the front door itself also announces when opened - another superfluous announcement since of course it is open - I'm going out!! The garage door isn't a problem - the user is sufficiently far enough away from the keypad for it to not be an issue. In addition, the constant announcements from the activated PIRs essentially stops the - far more meaningful - "please exit" announcement. The user really has no need to be told the 'front door is open' - and, of course, this CAN'T be bypassed!
I trust you see my reasoning? Thanks again for all your help!
|
|
