Status and Display code Analysis

[ghost]

STATUS CODES.xlsx

Attached is the the cope analysis I have done for both Display and Status json. The Bypass-On is when a zone is set to Bypass to all arming even if open. This is not standard and most will use the Bypass-Closed.

In review all the codes, I have think the logic on the Display codes are good and all testing matched up to expected results. For the Status, the logic did not match up for me.
Status Bit 19 / Armed / True = Yes and False = No
In all my testing the Armed Bit was always True and never changed to false in any of my testing. What testing results turned that to False?

Status Bit 22 0x02 / Json was both "exit_delay" and "ignore_faults". Bit seems to match up in testing as exit_delay but since it is for both exit and entry delay, exit delay may not be the correct name. Maybe alarm_delay might be a better name for it. What is strange is that just opening any zone in ready mode also turns that to True/yes.

Status Bit 21 / Bypass /
I did not have that in the output. What testing did you see that triggered that true or false? How is it used? I need to get that in the output and test more but curious if you did that already. I reused the ignore_faults section and will use that for the bypass bit since we dont need ignore_faults in json.

Not finding any solid login in the Status codes. There does not seem to be any solid status that is for System is Armed for instance. That same combination of values when system is armed is also found in other scenarios. Seems you can get some things like Alarm Tripped from it as that is consistent but with Bypass on, there is little value from it. I think I will focus on using just the display codes to get status and change in status.

[markkimsal]

I'm not sure if your bypass is actually on. When a zone is bypassed the display indicates a bypassed zone.

{"type":"display", "kp17": "active", "kp18": "active", "kp19": "active", "kp20": "active", "kp21": "active", "kp22": "active", "kp23": "active", "ARMED_STAY": "true", "low_batt": "true", "READY": "false", "chime": "off", "bypass_zone": true, "ac_power": "on", "ARMED_AWAY": "false","msg": "ARMED STAY ZONE BYPASSED "}

When a bypassed zone is triggered, no status messages are sent, armed or disarmed.

exit_delay is just short for entry/exit delay, but I don't think that bit matches up to entry/exit delay. It only seems to turn on for me when a zone is faulted in a disarmed state.

When I tripped an interior follower in away mode I get:
{"type":"status","armed": "yes", "mode": "stay", "ignore_faults": "no", "faulted": "yes", "panic": "no"}
{"type": "alarm"}

It's interesting that your ARMED flag is always true/yes. Perhaps there's a firmware difference. I have a Vista 10psia (pretty sure) and when i first power it up I get "Busy - Standby v8.1 D1" on the keypad. Perhaps F2 messages are totally unreliable wrt different panels and different firmware versions.

You can always ignore the F2 messages and go straight to F9 report codes. Enable IP/GSM with *29, don't program, don't diag, then flip the report code priority to ECP bus before telco bus with *55 set to 1. Lastly, set the report code format to Ademco 4 digit + contact ID by setting field *48 to 7,7.

F9 report codes are what all the central monitoring stations use.

(enter programming mode with [installer code 800], exit programming mode with *99)

[markkimsal]

Correction: When I bypass zone 1 and I trip zone 1 I get no F2. When zone 1 gets restored (I let go of the button/switch), I do get an F2 message.

Other zones get an F2 when I depress the switch and when I release the switch. So, for me, bypassed zones only generate F2 messages on fault restore.

[ghost]

My fault, should not have used the word ByPass for my setup. The Bypass as you test if the manual bypassing of a zone. What I have is a hard programmed function of the zone, no manual bypassing of the zone required, it is hard coded. I was not able to program it myself but I had to call the alarm company who had to program the zone for this function which was specifically designed for portable AC on the window. If Window close, zone is active. If Window is open, alarm will arm and that zone is inactive only for that arm event. I have read through the manual but could not find what the proper word is for that function yet.

[ghost]

So I believe the programming for this is called a Vent Zone(as in AC Vent) or Bypass When Armed, Programming manual yes set to 0=No (default) and 8=Yes for vent zone.

[ghost]

As for the other status flags, I have tried everything to get the ARMED status to change to No and it is always at Yes with AC Vent open/closed or any other combination. My panel is a Vista 20P so it is very standard.

For the Exit/Delay status flag, it goes True for me during

• Opening a Zone
• Arming
• Arming Failed with Zone Open
• Opening Door While Alarm is On in Delay-Entry

So I think you are right, this bit is not for Exit/Entry Delay. When the AV/Vent Bypass is on, that flag is True a lot of the times so this does seem to be more of a zone fault issue. So based on what you see, I have to agree, this is a Ignore Fault and not a Exit//Entry Delay. So really the status fields in the end are
Armed (does not work in my case)
Away
Bypass (manual bypass not Vent Bypass)
Ignore_Fault(labeled as exit_delay in json so need to change that)
Fault
Panic

[markkimsal]

You have the Chime feature enabled, don't you?

[ghost]

I do yes

[ghost]

alarmcode.txt
alarmcodes2alarm.txt
Some of my sample outputs in case you are interested.

[markkimsal]

That bit is flipped when chime is on. It's almost like some kind of perimeter zones are active type of bit, but instead of alarming they chime. Just compare faulted and not ignore_faults for alarm conditions. I'll see if there's another bit in F2 messages that indicates armed status. There might not be.

[markkimsal]

Here are the F2 message bodies that I get when I set the alarm to away, wait for exit delay, then disarm (while chime is enabled). M 1, 5, and 9 seem to contain little to no information. 3 is one byte longer than 7 (arm, then after exit delay)

Message 1

02  45  6C  F5  EC  01  01  7F  00  00  15

Message 3

02  45  43  F5  31  FB  45  6C  F5  EC  02  01  01  02  13  D7

Message 5

02  45  6C  F5  EC  01  01  7F  00  00  13

Message 7

02  45  43  F5  31  FB  45  6C  F5  EC  02  01  01  01  EA

Message 9

02  45  6C  F5  EC  01  01  7F  00  00  11

Message 11

 02  45  43  F5  31  FB  45  6C  F5  EC  03  01  01  01  E7

[ghost]

More I dig into this the more I relaize for what I want to do, the status code is really not relevent so I am going to skip over it and focus on the display code.