Using the Alarm.com app to arm my system to “Arm Stay” at night the “Night Arming” toggle is off, the system automatically arms in “Night Stay” mode. I think I understand that this mode enables internal motion sensors, which for my setup can’t be on at night. I don’t see any automation other than an auto arm to “Stay” after 11pm. Is there a setting somewhere that I’m missing to disable whatever functionality is forcing Night mode?
The only way I’ve found to arm in standard “Stay” mode is to arm via the physical keypad. Also to note, arming with the app during the day arms with standard “Stay”.
So struggling here a bit, still learning this system. An issue I’m having with understanding programming is viewing programmed info. No exception here, I might just not be fully understanding how data is presented.
I enter programming mode - + 800
I enter *81
I’m prompted to enter zone list no I enter - 05*
I’m prompted for zn no, the following entries give the following result
00 - displayed at start
01* = 02
02* = 00
03* = 00
04* = 00
I’m not sure how to interpret that information.
Apologies for the ignorance, I don’t have the fundamentals down just yet.
If you are at the “Enter Zn Num.” prompt in programming and you enter zone numbers, you are adding those numbers to that list, not checking them. The zones your panel is reporting to ADC appear to begin at Zone 7 however, 1-6 are not reported in your sensor list as being used.
If you are trying to make sure the motion detector is not a night zone list sensor, you would move on to the DELETE ZONE? prompt, press 1*, then at the ZN TO DELETE? prompt and enter 12* (that is the motion detector zone number I see reported by your system.)
Hmm ok, guess I need to unwind the zones I added too.
So to try and comprehend some:
Under Zone list, zone 5 is a “night mode list”?
So to I should go into programming, then 81, enter 05, then (to clean up) 01*, 00 to continue, then 1 to delete * to continue?
Then repeat for motion on 12 - enter programming, then 81, enter 05, then 12*, 00 to continue, 1 to delete, * to continue
Lastly, how do I actually view configurations without adding/changing?
Edit: Looks like pressing (*) after entering the zone list will cycle through programmed zones. I only see 02,03,04, I assume from adding them earlier. So I’ll clean those up.
When prompted for Zone List Number, yes #5 is the Night Zone list. Adding zones to it makes them night mode zones.
So to I should go into programming, then 81, enter 05, then (to clean up) 01*, 00 to continue, then 1 to delete * to continue?
It has been a while since I used night settings on a Vista, but based on the manual I would think you would hit * 81 - 05* - 00 - 0* - 1* - then each zone you want to delete from the list, so, for example 02* - 03* - 04*. Then 00
Honeywell Vista is not the most user friendly in terms of programming feedback.
Before I go too deep into adding zones to be used in night mode (I think I understand this now), need to remove what I mistakenly added, and add zones that need to trigger in night mode.
Is there a way to prevent the system from dropping into night mode?
If there are no Night Zones, then Night mode on the Vista has no impact, since the zones must be added to the list to be armed during Stay.
Interior zones would be bypassed as normal, and perimeter/entry exit zones would function as normal.
Motion detectors or other interior zones that should be armed in Night -Stay arming mode need to be added to the Night zone list. If none should be, no need to add any.
Is there a way to prevent the system from dropping into night mode?
It shouldn’t unless Night mode is selected during arming. Can you test and see roughly when that starts happening without selecting Night mode when sending the arming command?
I can, it happens on the mobile app, I haven’t tested from the website, I’ll try and nail down details. I think it starts at 11pm, I’ll try and verify.
Ok, so i’m not fully understanding this mode yet. So “Night Stay” arming would include any zone normally in stay PLUS anything in zone list 5 that isnt’ normally included?
Ok, so i’m not fully understanding this mode yet. So “Night Stay” arming would include any zone normally in stay PLUS anything in zone list 5 that isnt’ normally included?
Correct. I am adding a table from the manual below:
I’m pretty sure the night arming issue is a bug. It isn’t time related.
So, to reproduce the issue. I arm to stay without any toggles. Sometimes it arms correctly to stay. Other times it will occasionally hang after arming, the status never updates. it just says “arming” indefinitely. If I listen to my panel it’ll initially say armed stay, but then after a moment say night stay in the same action, I’ll then get a notification from the alarm.com app that it was armed Night Stay. The app will continue to say arming. If I kill the app and re-open it will show armed night mode. When it works without going into night mode, the armed status in the app pretty quickly switches to armed and stays in normal stay mode.
Hope that makes sense, I did take a screen recording of the issue I’d be glad to share, but I’d rather not here due to some personal information being displayed. If there is a more private way for me to share I’d be happy to.
That’s interesting regarding the way the panel responds. The panel itself is changing the mode after Stay is enabled.
On a 6160 I believe night mode is engaged with pressing the stay key twice. The SEM communicates with the board as though it were a keypad, across the BUS terminals. I bet if it retries a Stay command that wasn’t acknowledged this might happen. I am not sure it is actually programmed to do that, just that the mechanism for how that could happen appears to be there and would make sense given how you describe it.
I’ll let ADC know what is happening and see if they can recreate it.
Night mode won’t be different from normal Stay if you have no night list sensors.
Ah, the double stay tap makes perfect since if the app isn’t getting a message back and retries.
Correct, so overall this has been worked around. Just wanted to post if there was an issue. Although I think you’ve landed on what is happening. Before I share this video, based on your explanation on what might be happening, I’m going to troubleshoot my network and make sure communication isn’t being blocked somewhere. This might not be a bug, it might be “by design” if it doesn’t get an affirmative response that the system armed it might just try again.
I experience the same thing spuriously with a vista-20p.
If you give the panel another stay command from a keypad while it’s in the exit delay for the first stay command it’ll switch over to night stay. I have a feeling the SEM isn’t waiting long enough for the exit delay and is re-sending the arm command causing it to drop. The weird thing is it doesn’t happen consistently, sometimes it will and sometimes it won’t.
Yea sounds familiar . The inconsistent nature is what initially made me think it was time related. But once I started testing it’s pretty easy to reproduce. Within I’d say four arm/disarm cycles it’ll arm in night mode at least once.
. The inconsistent nature is what initially made me think it was time related. But once I started testing it’s pretty easy to reproduce. Within I’d say four arm/disarm cycles it’ll arm in night mode at least once.