Posts: 60
Threads: 17
Joined: Aug 2008
Reputation:
0
I have noticed that if I arm remotely (phone or via app) and later enter the building to disarm locally, there are no warning blips to indicate a disarm is needed. In fact the keypad makes no announcements on disarm.
I cannot find much in the manuals about how remote disarms work, other than Action Code 73,14 which detects a remote access.
1) does remote arming just reproduce the action of pressing a keypad key activating any attached response ?
2) Why no blips to indicate disarm needed ??
Comfort II Ultra v7.116 UCM 10 v7.096
Posts: 5,880
Threads: 865
Joined: Apr 2006
Reputation:
0
There should be no difference in remote arming and local arming, when you return and open the entry door. There should be an Entry warning which causes the beeps on the keypad. I suspect that the programming is supresing the beeps in some way
Posts: 60
Threads: 17
Joined: Aug 2008
Reputation:
0
Thanks Chiu
To see if there is a programming glitch I need to understand how the remote arming works. Remote arming doesn\'t need an exit door to activate the arming (as in keyswitch arm) it must use \"autoarm\" where no exit signal is required. The response currently attached to my Away key uses \"keyswitch arm\".
Does Comfort automatically recognise a remote connection and execute a \"keyswitch arm\" in the response as \"autoarm\" or does it use a different process/response entirely?
In terms of no entry warning blips, I can\'t see any obvious errors. The entry warning alarm is attached to the non-detector alarms. The only variance I found was the entry door was not ticked to be on the entry path. I\'ll have to see if that makes a difference.
Posts: 5,880
Threads: 865
Joined: Apr 2006
Reputation:
0
If the connection is remote eg by phone call or app with \"Network Remote\" connection then Comfort knows to autoarrm and npt ask for exit. Arm by keypad is always local arm. Anyway whichever way tou arm does not affect the entry alrt beeps when you re-enter the house. Camn you send your cclx file to support@cytech.biz so we can take a look
Posts: 60
Threads: 17
Joined: Aug 2008
Reputation:
0
I will thanks.
Digging deeper, my remote arming does not appear to activate the SystemSet alarm either. I have a few responses attached to this which are not executed from remote arming. I have also re-purposed the \"Day\" button to create by-passes to allow a pet zone in the house. If remote arming is actioned by means other than executing the button\'s responses, then the by-passes will not be created - which is important to know.
Posts: 60
Threads: 17
Joined: Aug 2008
Reputation:
0
My learning points from this thread:
There is a subtle difference in arming from keypad and by remote control (i.e. home phone, remote dial-in and App). This is because the keypad executes a response attached to the arming button. Unless the response is changed, the default is no different to remote arming and a keypad button uses \"keyswitch arm\" to set the arm mode associated with that button.
However, I re-purposed the DAY button with a response which armed to AWAY mode but bypassed some internal sensors to create a pet zone. Remote arming does not execute this response and just armed to the standard DAY mode which was confusing. The answer was to change the Zone type properties (disabled, alert, immediate etc) for doorbell, doors and sensors in DAY mode which has pretty much achieved the same. My DAY mode now matches AWAY but without internal sensors.
I suspect one could achieve the same using coding the non-detector alarm \"systemset\" to switch alarm modes and do the bypasses but that\'s for another day.
