1 year ago
Consider the following scenario:
1. You install a Honeywell Vista 20P system, including finishing all programming.
2. Months later, you return for whatever reason and attempt to access programming using the installer code + 800. Instead of entering program, you get the long high-pitched error beep disallowing programming mode entry. The only solution is to cuss the original installer for exiting with *98, cycle power, and re-entering program with * & #.
Only, it turns out that the installer, in fact, used *99 as normal, and it turns out that a random fair amount of Vista 20P's since firmware version 9.12 display this (errant ?) behavior.
I have run into this randomly over the past years. Each time it happens, I want to cuss the installers. But, really, they don't even know about exiting program with *98... they are hardwired to use *99 as normal, for decades, because they are sheep-like.
The more reasonable explanation is that there is some kind of bug in the Vista firmware that is disallowing re-entry into program, as if last exit from programming was with *98. (It wasn't -- they used *99)
I am forced to wonder, what are the situations that would disallow entry into the program using installer code + 800. I can think of two situations:
1. Previous use of programming mode was exited with *98.
2. Auto-arm is used, and a schedule is programmed to use it.
Are there other configurations where installer code + 800 is specifically disabled forgood reason, or is this a bug I have run into for quite a while now?
This is a potential problem beecause certain devices, like the Alarm.com SEM, cannot function properly if they can't readily access the Vista 20P system programming.