Zone bypass at HONEYWELL panels

[Tasosgi]

Is there any way to bypass zones with Honeywell panels?

[ufodone]

There is currently no built-in way. If Honeywell panels accept a keystroke sequence to bypass a zone then you could use this integrations alarm_keypress service call to send the appropriate key strokes.

I don't have a Honeywell panel myself so am not very familiar with them but when I looked at the EVL documentation I didn't see anything that allowed me to determine which zones are currently bypass which is why I did not expose bypass switches for the Honeywell panels.

[SmithAdamL]

I don't do any coding so can't help with designing this application but am very aware of the Vista HW panels.

To bypass a specific zone it is a keying sequence of .usercode. 6 .zonenumber.

To view the current list of bypassed zones it is a keying sequence of .usercode. 6#

There is no way to turn off individual zone bypasses (that I am aware of) and you must "disarm" the system (even though it is not armed) using the keying sequence of .usercode. 1

Not sure if any of this information helps and makes this possible to add the the integration.

[Lou-Der]

There is command 616 to pull the bypassed zones via the Enivsalink TPI api:

1.09 TPI

Bypassed Zones Bitfield Dump
This command is issued upon leaving Zone Bypass programming (*1 on
the keypad). It is a 16 character HEX string representing an 8 byte bitfield.
This bitfield indicates which zones are currently in bypass. A “1” indicates
the zone is in bypass. The lower 8 zones are in the first position of the
bitfield. The developer can force this dump by using the keystring
commands to enter and leave zone bypassing. i.e. “*1#”

Enivsalink 3 vs Envisalink 4 Difference
This command is currently only available on the Envisalink 3 with firmware revision 1.12.182 and higher.

Keypad sequence to set a Honeywell vista panel bypass is <user code>+6+<zone id>

Hope this helps! :)

[ufodone]

Those docs are for the TPI interface for EVL devices connected to DSC panels. The TPI interface for Honeywell panels is completely different and doesn't expose the same capabilities unfortunately.

I think querying the state of the currently bypassed zones is likely the biggest barrier. Maybe the .usercode. 6# noted by @SmithAdamL would be sufficient but I don't have a Honeywell panel and so don't know what the translates to into updates on the TPI interface. It would also have to not interfere with the physical keypads.

[Lou-Der]

Ah, so sorry as I didn't catch the distinction in the TPI docs. Seems a crazy way to do a panel but I'm stuck with it for now.

From what I've reviewed the best you can see is a "02 – Ready to Arm (Zones are Bypasses)" partition state from command 02 when all faulted zones are bypassed and system is ready for arming.

When I bypass a faulted zone not even Eyezon's app/web page knows its bypassed and shows the zone as normal and ready to arm. When doing a "off" sequence to clear the bypass the zone becomes faulted again. These results are consistent at both the keypad and via their app.

Reading through the honeywell programming manual there is the option:

**Forced (Quick) Bypass** To automatically bypass all faulted zones, use the “Quick Bypass” method. 
Enter code + BYPASS + [#], then wait for all open zones to be displayed.    Arm when display indicates “ZONE 
BYPASSED” and “READY TO ARM”.   

This is the user code + 6 + # sequence @SmithAdamL mentioned. It isn't just a query, but an actual bypass of all faulted zones. It does display all the zones in the keypad status before switching to ready state. Not sure if you could parse that as it happens though.

I've confirmed this works on my system and there will be a status of "Bypass" for the keypad after triggered. Doing a "off" or disarm sequence clears the bypass states of all.

Create a "Bypass All" toggle perhaps? On - send "Forced (Quick) Bypass" sequence, Off - send "disarm/off". Query state would be the bypassed keypad status from command 0 or the partition state on command 02 on the TPI.

Note: The "Forced (Quick) Bypass" can be disabled in the Honeywell programming. A switch in your advanced options to disable "bypass all" is probably appropriate.

I am a retired programmer but as you can tell I'm new to Envisalink and HA. I'll try to help when I get more familiar with everything.

Thanks again!