Latest FW adds: Zones Bypassed to TPI ... what is it?

[Ltek]

In hte most recent EVL3 firmware this shows... "Added Zones Bypassed to TPI" ... what is it and how does it work?

I'm on EVL3 with Ademco 20p. Have been hoping forever to be able to pull in the Zones that are Bypassed to show in my Home Automation.

Is this possible now? If yes, how?

thx!

[GrandWizard]

Its only for DSC panels.

[Ltek]

Its only for DSC panels.

Thx. Not sure why they didn't specify that. It's unfortunate they don't care about Vista users. This has been a feature we've been wanting for years.

[K-Man]

Its not technically possible due to the nature of how Ademco panels work. If it were possible we would have done it.

[Ltek]

Its not technically possible due to the nature of how Ademco panels work. If it were possible we would have done it.

Can't the EVL "see" all commands sent to/from the 20P? When Bypass commands are used, why can't the EVL record, in memory, what zones were bypassed? Thus keeping a record of what was bypassed, or un-bypassed? Then we could query the EVL for that info? Even if it didnt live across reboots (ideally it would be in NVRAM) would be better than nothing.

[K-Man]

We could never guarantee the Envisalink would be in sync with the panel for a variety of reasons: What if the bypass command failed? What about zones that are bypassed without keypad intervention?

We can't offer-up an API command that "may" be correct 60% of the time.

The Honeywell version of the TPI presents all human readable messages destined for a keypad so if you want to do what you describe you can. Whenever you see the BYPASS string with a number after it, that is the zone that is either bypassed or un-bypassed. The zone number is also included in the zone/user field of the 00 command.