help with Envisalink4 and Vista20p
Posted: Wed Feb 07, 2018 9:24 pm
Hi everyone,
new to the forum and dealing with alarm system in general, please be easy on me if I ask a bad question or don't know obvious things, also thank you in advance for reading and posting a reply!
To make it short, I have inherited a Vista20p system (first house) and have installed Envisalink4 with surprising level of success for a first timer. The system works with the mobile app; it lets me arm and disarm and it sends me the alerts I have chosen in the contacts section of the customer logon. A few oddities/deviations from the install instructions however, which I cannot understand yet and am hoping to get help with those. I don't know how to properly identify the touch pad model (sorry about not having this information), all I can say is that its a SafeWatch 3000 Pro (no microphone type). The chip on the board says revision 9.12, but other than that I cannot see anything else that is meaningful, at least to me.
1. *48 is not present on my system, cannot set the value to 77 as per the instructions. Not sure the effect of this.
2. setting *50 to 00 does not seem to remove the delay on alarm events, as no alarm events are reported between the arm and disarm events. I have not let the alarm get past the 15/30/45 seconds thresholds to test if an alarm would be reported since I do not want the delay in reporting. As soon as the alarm trips and the siren goes off I disarm it. To get around this I have programmed zone list 6 with the zones I want alarm events reported on without delay and have set *50 to 11. According to the installer manual the second 1 causes the first 1 (15 seconds delay) to be ignored. After this the alarm events get reported now without any delay, which is perfect, but for some reason I get a double disarm event report. Both customer portal events and phone app events get a double "opening by user code". The events are usually in this sequence: arm, opening by user, alarm, opening by user. I have tested this with every zone being tripped and it is always a double disarm. It is a very minor issue since I am getting the alarm events now and I am willing to live with it, but would like to know what am I doing wrong and what is the potential solution to this.
3. I have seen various settings listed in various instructions for *59. Some say set it to off 0 and some say set it to on 1. What is the reason for this difference, preference only? As far as I understand this is for reporting or not reporting alarm events triggered by a late disarm; when you were too slow to disarm and the alarm went off while you were in the house.
Thanks again for reading and your potential replies. Sorry for the lengthy post!
new to the forum and dealing with alarm system in general, please be easy on me if I ask a bad question or don't know obvious things, also thank you in advance for reading and posting a reply!
To make it short, I have inherited a Vista20p system (first house) and have installed Envisalink4 with surprising level of success for a first timer. The system works with the mobile app; it lets me arm and disarm and it sends me the alerts I have chosen in the contacts section of the customer logon. A few oddities/deviations from the install instructions however, which I cannot understand yet and am hoping to get help with those. I don't know how to properly identify the touch pad model (sorry about not having this information), all I can say is that its a SafeWatch 3000 Pro (no microphone type). The chip on the board says revision 9.12, but other than that I cannot see anything else that is meaningful, at least to me.
1. *48 is not present on my system, cannot set the value to 77 as per the instructions. Not sure the effect of this.
2. setting *50 to 00 does not seem to remove the delay on alarm events, as no alarm events are reported between the arm and disarm events. I have not let the alarm get past the 15/30/45 seconds thresholds to test if an alarm would be reported since I do not want the delay in reporting. As soon as the alarm trips and the siren goes off I disarm it. To get around this I have programmed zone list 6 with the zones I want alarm events reported on without delay and have set *50 to 11. According to the installer manual the second 1 causes the first 1 (15 seconds delay) to be ignored. After this the alarm events get reported now without any delay, which is perfect, but for some reason I get a double disarm event report. Both customer portal events and phone app events get a double "opening by user code". The events are usually in this sequence: arm, opening by user, alarm, opening by user. I have tested this with every zone being tripped and it is always a double disarm. It is a very minor issue since I am getting the alarm events now and I am willing to live with it, but would like to know what am I doing wrong and what is the potential solution to this.
3. I have seen various settings listed in various instructions for *59. Some say set it to off 0 and some say set it to on 1. What is the reason for this difference, preference only? As far as I understand this is for reporting or not reporting alarm events triggered by a late disarm; when you were too slow to disarm and the alarm went off while you were in the house.
Thanks again for reading and your potential replies. Sorry for the lengthy post!