Zone Bypass

Thanks for a great plugin.

I am not able to get the bypass state of any Zone recognised:
- whether the zone is bypassed automatically (because stay has been chosen)
- or bypassed manually using the *1
The zone is actually bypassed using these methods but the status of the zone is not shown as bypassed. Curiously the partition recognises that a zone has been bypassed on either method, as the plugin bypass LED indicates that a zone in the partition is bypassed.

I have also tried using the action "Bypass a Zone" and get the error that a code is required. Same error for Clearing bypass. I know I can change the protocols in the DSC to not require the code, however it would be preferable if the plugin used the disarm code set up in the config. That may require an option in the config that a code is required.

Thanks in advance.

Marcus Bleasel


Mac OS 10.12.3
Indigo 7.03
DSC plugin v 2.1.0
Envisalink 3 - Firmware 01.12.180 - MAC
DSC PC1864

What partition are the zones in that do not show bypass status?
Due to limitation of the DSC panel and how it communicates with the Envisalink, only zones in partition 1 will show the bypass status. But zones in all partitions will still be correctly bypassed and the bypass LED will come on for that particular partition.

Regarding the disarm code not being required for bypass, this is something that needs to be programmed on the DSC panel. The plugin currently is not setup to provide this code. I need to see whether this can be done without causing other issues.

Out of curiosity, how does this "bypass code required" error look like?

Thanks for the quick reply

What partition are the zones in that do not show bypass status?

Due to limitation of the DSC panel and how it communicates with the Envisalink, only zones in partition 1 will show the bypass status. But zones in all partitions will still be correctly bypassed and the bypass LED will come on for that particular partition.

All zones are in Partition 1

Regarding the disarm code not being required for bypass, this is something that needs to be programmed on the DSC panel. The plugin currently is not setup to provide this code. I need to see whether this can be done without causing other issues.

Prefer not to disable this option. [022] Ninth System Option. Access code is required for *1, *2, *3.

Out of curiosity, how does this "bypass code required" error look like?

Mar 2017, 12:32:12 pm
Action Group Bypass zone
DSC Alarm Received Zone Bypass Action for Zone 'M-L2 Dining' in Partition 1 'Default'.
DSC Alarm Error Code Required

I checked the code and it is fairly simple to incorporate the feature that a disarm code is sent when required.

However, it is puzzling to me why you do not see the bypass state correctly for zones in partition 1. When you issue the command on theDSC keypad (and enter the disarm code), does the plugin report back "Alarm Zone XYZ Bypassed?
Can you turn debugging on and send me the debug log after a bypass command has been issued.

I checked the code and it is fairly simple to incorporate the feature that a disarm code is sent when required.

However, it is puzzling to me why you do not see the bypass state correctly for zones in partition 1. When you issue the command on theDSC keypad (and enter the disarm code), does the plugin report back "Alarm Zone XYZ Bypassed?
Can you turn debugging on and send me the debug log after a bypass command has been issued.

With intense debugging on, there is no reporting of what Zone has been bypassed. This is an edited version from when the LEDBypass was off and changed to on. (I deleted non DSC debugging and in this case, I bypassed zone 7).
(The trouble led is because the antitheft contact behind the DSC panel moves because the wall is weak. It is on the list of jobs)

DSC Alarm Debug Partition 1 Ready
DSC Alarm Debug Updating state ReadyState for keypad on partition 1 to ready.
DSC Alarm Debug Updating state LEDReady for keypad on partition 1 to on.
DSC Alarm Debug RX: 60900433
DSC Alarm Debug Zone Number 4 Open.
DSC Alarm Alarm Zone 'M-L1 Entertainment' Opened.
DSC Alarm Debug RX: 51090FF
DSC Alarm Debug Updating state LEDReady for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDArmed for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDTrouble for keypad on partition 1 to on.
DSC Alarm Debug Updating state LEDMemory for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDBypass for keypad on partition 1 to off.
DSC Alarm Debug RX: 6511CD
DSC Alarm Debug Partition 1 Not Ready
DSC Alarm Debug Updating state ReadyState for keypad on partition 1 to notready.
DSC Alarm Debug Updating state LEDReady for keypad on partition 1 to off.
DSC Alarm Debug RX: 51080FE
DSC Alarm Debug Updating state LEDReady for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDArmed for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDTrouble for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDMemory for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDBypass for keypad on partition 1 to off.

DSC Alarm Debug RX: 51108FF
DSC Alarm Debug RX: 6100042B
DSC Alarm Debug Zone Number 4 Closed.
DSC Alarm Alarm Zone 'M-L1 Entertainment' Closed.


DSC Alarm Debug RX: 51100F7
DSC Alarm Debug RX: 5109908
DSC Alarm Debug Updating state LEDReady for keypad on partition 1 to on.
DSC Alarm Debug Updating state LEDArmed for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDTrouble for keypad on partition 1 to on.
DSC Alarm Debug Updating state LEDMemory for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDBypass for keypad on partition 1 to on.
DSC Alarm Debug RX: 6501CC
DSC Alarm Debug Partition 1 Ready
DSC Alarm Debug Updating state ReadyState for keypad on partition 1 to ready.

hmm, there is a critical command not being sent from the DSC panel.

How exactly are you bypassing your zones?

Can you try *1# without specifying a zone.
Also, does this command ask for the disarm code too?

hmm, there is a critical command not being sent from the DSC panel.

How exactly are you bypassing your zones?

Can you try *1# without specifying a zone.
Also, does this command ask for the disarm code too?

I use: [*][1][mastercode][2-digit zone number] .... bypass icon is now solid, waiting for arming. Also tried arming.

Tried *1# without specifying a zone. No zones bypassed

Tried *1[mastercode] (without #). Bypass icon flashes waiting for input.

Tried *1[mastercode]#. No Zones bypassed. No bypass icon.






(LCD5511)
Mastercode allows bypassing.

*1[mastercode]#

activates a security email

Security Event: [*][1] By Access Master
Location: .....
Time: 2017-03-03 20:52:52
Partition: 1


Curiously nothing is shown in the intense debug log which shows that this is happening.

At this point I am suspecting that the DSC panel is not sending the critical 616 command for bypassed zones since you enter the master code together with the bypass command.. You did not specify the # key but I assume you press this at the keypad:
[*][1][mastercode][2-digit zone number][#]

Can you bypass a zone on the keypad and then followup with the [*][1][#] command. I want to see whether this triggers the 616 command and updates the bypass status of the previously bypassed zone.

Just to be sure this is the cause of the problem, if it is not too much trouble, can you turn off the requirement for the master code temporarily and test things both from the keypad and the plugin. It should work with the plugin commands and [*][1][2-digit zone number][#] from the keypad.

And by the way, the email you got is from EyezOn since they monitor [*][1] events.

At this point I am suspecting that the DSC panel is not sending the critical 616 command for bypassed zones since you enter the master code together with the bypass command.. You did not specify the # key but I assume you press this at the keypad:
[*][1][mastercode][2-digit zone number][#]

Can you bypass a zone on the keypad and then followup with the [*][1][#] command. I want to see whether this triggers the 616 command and updates the bypass status of the previously bypassed zone.

Done. Used the [#]. The zone that I bypassed is still showing its state as "nobypass" although the LEDbypass recognises that a zone is bypassed. The bypass works in that the zone will not set off the alarm when triggered.

Just to be sure this is the cause of the problem, if it is not too much trouble, can you turn off the requirement for the master code temporarily and test things both from the keypad and the plugin. It should work with the plugin commands and [*][1][2-digit zone number][#] from the keypad.

And by the way, the email you got is from EyezOn since they monitor [*][1] events.

Will take off master code requirement and try, but won't be able to do this for 20hrs. (Cooking for a dinner party and the Fixed LCD panel is a PIA for programming).

Running through my notes on the programming sheets of options, and at this stage I don't know which may affect the reporting:
[015] 5 - Code required for bypassing
[016] 7 - Bypass Status not displayed while armed (default)
[022] 1 - Access Code Required for *1, *2, *3
[320]-[323] Alarm reporting codes. The default is chosen - that is "FF" for all zones.


Sorry for the delay. Thanks for assisting. Will report further tomorrow, Sydney time.

Thanks for troubleshooting. These are the options to toggle. If you just want to protect the bypass command, option [015] 5 is enough.
[015] 5 - Code required for bypassing (*1 only)
[022] 1 - Access Code Required for *1, *2, *3

However, I turned on those options on my system and I still get proper bypass status updates in the plugin. I have an EVL-4, but I doubt this will make a difference on the problem you are having on your system.

Just to make sure, did you assign the zones in partition 1 to the correct partition in the plugin?

Thanks for troubleshooting. These are the options to toggle. If you just want to protect the bypass command, option [015] 5 is enough.
[015] 5 - Code required for bypassing (*1 only)
[022] 1 - Access Code Required for *1, *2, *3

However, I turned on those options on my system and I still get proper bypass status updates in the plugin. I have an EVL-4, but I doubt this will make a difference on the problem you are having on your system.

Just to make sure, did you assign the zones in partition 1 to the correct partition in the plugin?

Changed the options.
All zones are assigned to partition 1 (if you mean the edit settings for each zone). To make sure I changed them to partition 2 and then changed back to partition 1.
This is the intense debug log after using the plugin to bypass the front door.

Action Group Bypass zone
DSC Alarm Received Zone Bypass Action for Zone 'M-L2 FrontDoor' in Partition 1 'Default'.
DSC Alarm Debug TX: 0711*107#AE

DSC Alarm Debug RX: 5000712D
DSC Alarm Debug ACK for cmd 071.
DSC Alarm Debug RX: 51080FE
DSC Alarm Debug Updating state LEDReady for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDArmed for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDTrouble for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDMemory for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDBypass for keypad on partition 1 to off.
DSC Alarm Debug RX: 51108FF
DSC Alarm Debug RX: 8411CE
DSC Alarm Trouble Status Restore (LED OFF). (Partition 1)
DSC Alarm Debug Updating state LEDTrouble for keypad on partition 1 to off.
DSC Alarm Debug RX: 51100F7
DSC Alarm Debug RX: 5109908
DSC Alarm Debug Updating state LEDReady for keypad on partition 1 to on.
DSC Alarm Debug Updating state LEDArmed for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDTrouble for keypad on partition 1 to on.
DSC Alarm Debug Updating state LEDMemory for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDBypass for keypad on partition 1 to on.
DSC Alarm Debug RX: 6501CC
DSC Alarm Debug Partition 1 Ready
DSC Alarm Debug Updating state ReadyState for keypad on partition 1 to ready.
DSC Alarm Debug Updating state LEDReady for keypad on partition 1 to on.
DSC Alarm Debug RX: 8401CD
DSC Alarm Trouble Status (LED ON). (Partition 1 'Default')
DSC Alarm Debug Updating state LEDTrouble for keypad on partition 1 to on.


The Zone state for M-L2 Front Door is still showing no bypass

Using the Keypad [*][1] [07] [#]


the log shows:

DSC Alarm Debug RX: 6501CC
DSC Alarm Debug Partition 1 Ready
DSC Alarm Debug Updating state ReadyState for keypad on partition 1 to ready.
DSC Alarm Debug Updating state LEDReady for keypad on partition 1 to on.
DSC Alarm Debug RX: 51080FE
DSC Alarm Debug Updating state LEDReady for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDArmed for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDTrouble for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDMemory for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDBypass for keypad on partition 1 to off.
DSC Alarm Debug RX: 8411CE
DSC Alarm Trouble Status Restore (LED OFF). (Partition 1)
DSC Alarm Debug Updating state LEDTrouble for keypad on partition 1 to off.
DSC Alarm Debug RX: 51108FF
DSC Alarm Debug RX: 51100F7
DSC Alarm Debug RX: 5109908
DSC Alarm Debug Updating state LEDReady for keypad on partition 1 to on.
DSC Alarm Debug Updating state LEDArmed for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDTrouble for keypad on partition 1 to on.
DSC Alarm Debug Updating state LEDMemory for keypad on partition 1 to off.
DSC Alarm Debug Updating state LEDBypass for keypad on partition 1 to on.
DSC Alarm Debug RX: 6501CC
DSC Alarm Debug Partition 1 Ready
DSC Alarm Debug Updating state ReadyState for keypad on partition 1 to ready.
DSC Alarm Debug Updating state LEDReady for keypad on partition 1 to on.
DSC Alarm Debug RX: 8401CD


Zone status still shows no bypass (although both Bypass icon and LED are on.)
(Checked all zones in case there is some cross match, but all are showing no bypass)

Monstergerm


Just a thought. Are you using the PC1864 panel, and if not is the 616 code different for different panels. Just looking at programming options [403]-[404]. Not sure if relevant.

I am using the PC1864 panel with EVL-4.

For whatever reasons, your panel is not sending command 616 after a bypass command is issued, or just *1# sent.

So, your zones will still be bypassed and the bypass LED will come on, but zone status will not update correctly. At this point I have no idea why your panel is not sending this command.