Announcement

Collapse
No announcement yet.

Bypass status not showing correctly

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bypass status not showing correctly

    I am running the latest version of the plugin 3.0.0.40. I cannot get the bypass status to be reflected correctly on the Device Management page. When I tap the "Bypass" button on the device management page, the Zone correctly bypasses on the alarm panel. The icon for the bypassed device also changes to "Bypassed" on the device management page. When I tap the bypass again, the zone returns to normal, but the icon on the device management page never changes back to "Active". I have restarted the plugin and restarted HS3, but the icon is stuck showing bypassed. Looking at the log when the plugin starts up, it shows that the plugin is recognizing the correct state of the zone.

    May-16 7:34:32 PM EnvisaLink INFO North Hallway Windows status change: Closed
    May-16 7:34:32 PM EnvisaLink INFO Family Room Windows status change: Closed
    May-16 7:34:32 PM EnvisaLink INFO Family Room Slider status change: Closed
    May-16 7:34:32 PM EnvisaLink INFO Nook Windows status change: Closed
    May-16 7:34:32 PM EnvisaLink INFO Kitchen Windows status change: Closed
    May-16 7:34:32 PM EnvisaLink INFO South Hallway Window status change: Closed
    Attached Files

  • #2
    Do you have an EVL3 or EVL4? which firmware?

    Please set the log level to Debug, and capture logs when you try to bypass/unbypass a zone.

    thanks

    Comment


    • #3
      Originally posted by spud View Post
      Do you have an EVL3 or EVL4? which firmware?

      Please set the log level to Debug, and capture logs when you try to bypass/unbypass a zone.

      thanks
      I have an EVL3 - 191 Firmware


      May-17 6:29:39 AM EnvisaLink DEBUG postBackProc data: id=loglevel&loglevel=1
      May-17 6:29:28 AM EnvisaLink DEBUG PartitionNotReady 1
      May-17 6:29:28 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 00
      May-17 6:29:27 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 08
      May-17 6:29:27 AM EnvisaLink DEBUG KeypadLedStatePartition1Only 80
      May-17 6:29:26 AM EnvisaLink DEBUG CommandAcknowledge 071
      May-17 6:29:26 AM EnvisaLink DEBUG Request: SendKeystrokeString 1*138#
      May-17 6:29:26 AM Device Control Device: EnvisaLink Security Family Room Slider to Bypass (-1000) by/from: CAPI Control Handler
      May-17 6:28:45 AM EnvisaLink DEBUG PartitionNotReady 1
      May-17 6:28:45 AM EnvisaLink DEBUG KeypadLedStatePartition1Only 88
      May-17 6:28:45 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 00
      May-17 6:28:44 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 08
      May-17 6:28:44 AM EnvisaLink DEBUG CommandAcknowledge 071
      May-17 6:28:43 AM EnvisaLink DEBUG Request: SendKeystrokeString 1*138#
      May-17 6:28:43 AM Device Control Device: EnvisaLink Security Family Room Slider to Bypass (-1000) by/from: CAPI Control Handler
      May-17 6:28:31 AM EnvisaLink DEBUG CommandAcknowledge 000
      May-17 6:28:31 AM EnvisaLink DEBUG Request: Poll

      Comment


      • #4
        weird, I just tested it again with EVL3 firmware 193 and it works as expected for me (was also working with firmware 182)

        in your case it looks like you don't receive the BypassedZonesBitfieldDump after you bypass/unbypass a zone. But in this case the device should not have its status change the first time you hit bypass.

        Can you restart the plugin a provide a full debug log. A BypassedZonesBitfieldDump is forced at initialization.

        Comment


        • #5
          Originally posted by spud View Post
          weird, I just tested it again with EVL3 firmware 193 and it works as expected for me (was also working with firmware 182)

          in your case it looks like you don't receive the BypassedZonesBitfieldDump after you bypass/unbypass a zone. But in this case the device should not have its status change the first time you hit bypass.

          Can you restart the plugin a provide a full debug log. A BypassedZonesBitfieldDump is forced at initialization.
          Here is the full debug log on plugin startup. "Family Room Slider" is still showing Bypassed

          May-17 7:27:49 AM EnvisaLink DEBUG PartitionNotReady 1
          May-17 7:27:49 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 00
          May-17 7:27:48 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 08
          May-17 7:27:48 AM EnvisaLink DEBUG KeypadLedStatePartition1Only 80
          May-17 7:27:48 AM EnvisaLink DEBUG TroubleLedoff 8
          May-17 7:27:48 AM EnvisaLink DEBUG TroubleLedoff 7
          May-17 7:27:48 AM EnvisaLink DEBUG CommandAcknowledge 071
          May-17 7:27:47 AM EnvisaLink DEBUG TroubleLedoff 6
          May-17 7:27:47 AM EnvisaLink DEBUG TroubleLedoff 5
          May-17 7:27:47 AM EnvisaLink DEBUG TroubleLedoff 4
          May-17 7:27:47 AM EnvisaLink DEBUG TroubleLedoff 3
          May-17 7:27:47 AM EnvisaLink DEBUG TroubleLedoff 2
          May-17 7:27:47 AM EnvisaLink DEBUG TroubleLedoff 1
          May-17 7:27:47 AM EnvisaLink DEBUG PartitionisBusy 8
          May-17 7:27:47 AM EnvisaLink DEBUG PartitionisBusy 7
          May-17 7:27:47 AM EnvisaLink DEBUG PartitionisBusy 6
          May-17 7:27:47 AM EnvisaLink DEBUG PartitionisBusy 5
          May-17 7:27:47 AM EnvisaLink DEBUG PartitionisBusy 4
          May-17 7:27:47 AM EnvisaLink DEBUG PartitionisBusy 3
          May-17 7:27:47 AM EnvisaLink DEBUG PartitionisBusy 2
          May-17 7:27:47 AM EnvisaLink DEBUG Request: SendKeystrokeString 1*1#
          May-17 7:27:47 AM EnvisaLink DEBUG PartitionNotReady 1
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 064
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 063
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 062
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 061
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 060
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 059
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 058
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 057
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 056
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 055
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 054
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 053
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 052
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 051
          May-17 7:27:47 AM EnvisaLink DEBUG ZoneRestored 050
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 049
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 048
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 047
          May-17 7:27:46 AM EnvisaLink INFO Master Bath Windows status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 046
          May-17 7:27:46 AM EnvisaLink INFO Art Niche Windows status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 045
          May-17 7:27:46 AM EnvisaLink INFO Retreat Windows status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 044
          May-17 7:27:46 AM EnvisaLink INFO Mike's Deck Door status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 043
          May-17 7:27:46 AM EnvisaLink INFO Guest Bedroom status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 042
          May-17 7:27:46 AM EnvisaLink INFO Laundry Room Window status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 041
          May-17 7:27:46 AM EnvisaLink INFO North Hallway Windows status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 040
          May-17 7:27:46 AM EnvisaLink INFO Family Room Windows status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 039
          May-17 7:27:46 AM EnvisaLink INFO Family Room Slider status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 038
          May-17 7:27:46 AM EnvisaLink INFO Nook Windows status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 037
          May-17 7:27:46 AM EnvisaLink INFO Kitchen Windows status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 036
          May-17 7:27:46 AM EnvisaLink INFO South Hallway Window status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 035
          May-17 7:27:46 AM EnvisaLink INFO Living Room Door status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 034
          May-17 7:27:46 AM EnvisaLink INFO Living Room Windows Right-3 status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 033
          May-17 7:27:46 AM EnvisaLink INFO Zone 32 status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 032
          May-17 7:27:46 AM EnvisaLink INFO Zone 31 status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 031
          May-17 7:27:46 AM EnvisaLink INFO Zone 30 status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 030
          May-17 7:27:46 AM EnvisaLink INFO Zone 29 status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 029
          May-17 7:27:46 AM EnvisaLink INFO Zone 28 status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 028
          May-17 7:27:46 AM EnvisaLink INFO Zone 27 status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 027
          May-17 7:27:46 AM EnvisaLink INFO Zone 26 status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 026
          May-17 7:27:46 AM EnvisaLink INFO Zone 25 status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 025
          May-17 7:27:46 AM EnvisaLink INFO Zone 24 status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 024
          May-17 7:27:46 AM EnvisaLink INFO Zone 23 status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 023
          May-17 7:27:46 AM EnvisaLink INFO Zone 22 status change: Closed
          May-17 7:27:46 AM EnvisaLink DEBUG ZoneRestored 022
          May-17 7:27:45 AM EnvisaLink DEBUG ZoneRestored 021
          May-17 7:27:45 AM EnvisaLink INFO South Garage Window status change: Closed
          May-17 7:27:45 AM EnvisaLink DEBUG ZoneRestored 020
          May-17 7:27:45 AM EnvisaLink INFO South Garage Side Door status change: Closed
          May-17 7:27:45 AM EnvisaLink DEBUG ZoneRestored 019
          May-17 7:27:45 AM EnvisaLink INFO South Garage Door status change: Closed
          May-17 7:27:45 AM EnvisaLink DEBUG ZoneRestored 018
          May-17 7:27:45 AM EnvisaLink INFO North Garage Window status change: Closed
          May-17 7:27:45 AM EnvisaLink DEBUG ZoneRestored 017
          May-17 7:27:45 AM EnvisaLink INFO North Garage Side Door status change: Closed
          May-17 7:27:45 AM EnvisaLink DEBUG ZoneRestored 016
          May-17 7:27:45 AM EnvisaLink INFO North Garage Door status change: Closed
          May-17 7:27:45 AM EnvisaLink DEBUG ZoneRestored 015
          May-17 7:27:45 AM EnvisaLink INFO South Hallway Smoke status change: Closed
          May-17 7:27:45 AM EnvisaLink DEBUG ZoneRestored 014
          May-17 7:27:45 AM EnvisaLink INFO North Hallway Smoke status change: Closed
          May-17 7:27:45 AM EnvisaLink DEBUG ZoneRestored 013
          May-17 7:27:45 AM EnvisaLink INFO Back Staircase Smoke status change: Closed
          May-17 7:27:45 AM EnvisaLink DEBUG ZoneRestored 012
          May-17 7:27:45 AM EnvisaLink DEBUG ZoneRestored 011
          May-17 7:27:44 AM EnvisaLink INFO Master Bedroom Slider status change: Opened
          May-17 7:27:44 AM EnvisaLink DEBUG ZoneOpen 010
          May-17 7:27:44 AM EnvisaLink INFO Mike's Room Window status change: Opened
          May-17 7:27:44 AM EnvisaLink DEBUG ZoneOpen 009
          May-17 7:27:44 AM EnvisaLink INFO Living Room Windows Left-3 status change: Closed
          May-17 7:27:44 AM EnvisaLink DEBUG ZoneRestored 008
          May-17 7:27:44 AM EnvisaLink INFO Dining Room Windows status change: Closed
          May-17 7:27:44 AM EnvisaLink DEBUG ZoneRestored 007
          May-17 7:27:44 AM EnvisaLink INFO Office Exterior Door+Window status change: Closed
          May-17 7:27:44 AM EnvisaLink DEBUG ZoneRestored 006
          May-17 7:27:44 AM EnvisaLink INFO DSC Repeater status change: Closed
          May-17 7:27:44 AM EnvisaLink DEBUG ZoneRestored 005
          May-17 7:27:44 AM EnvisaLink DEBUG ZoneRestored 004
          May-17 7:27:44 AM EnvisaLink DEBUG ZoneRestored 003
          May-17 7:27:44 AM EnvisaLink INFO Entry Doors status change: Closed
          May-17 7:27:44 AM EnvisaLink DEBUG ZoneRestored 002
          May-17 7:27:44 AM EnvisaLink INFO Fire Sprinkler Flowswitch status change: Closed
          May-17 7:27:44 AM EnvisaLink DEBUG ZoneRestored 001
          May-17 7:27:44 AM EnvisaLink DEBUG CommandAcknowledge 001
          May-17 7:27:44 AM EnvisaLink DEBUG CommandAcknowledge 055
          May-17 7:27:44 AM EnvisaLink DEBUG LoginInteraction 1
          May-17 7:27:44 AM EnvisaLink DEBUG CommandAcknowledge 005
          May-17 7:27:44 AM EnvisaLink DEBUG LoginInteraction 3
          May-17 7:27:44 AM EnvisaLink DEBUG Request: Poll
          May-17 7:27:44 AM EnvisaLink DEBUG Request: StatusReport
          May-17 7:27:44 AM EnvisaLink DEBUG Request: TimeStampControl 1
          May-17 7:27:44 AM EnvisaLink DEBUG Request: NetworkLogin user
          May-17 7:27:44 AM Starting Plug-In Plugin EnvisaLink started successfully in 3763 milliseconds
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:46
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:45
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:44
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:43
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:42
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:41
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:40
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:39
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:38
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:37
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:36
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:35
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:34
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:33
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:32
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:31
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:30
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:29
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:28
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:27
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:26
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:25
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:24
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:23
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:22
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:21
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:20
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:19
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:18
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:17
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:16
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:15
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:14
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:13
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:12
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:11
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:10
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:9
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:8
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:7
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:6
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:5
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:4
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:3
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:2
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:1
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:46
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:45
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:44
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:43
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:42
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:41
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:40
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:39
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:38
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:37
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:36
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:35
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:34
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:33
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:32
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:31
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:30
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:29
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:28
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:27
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:26
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:25
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:24
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:23
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:22
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:21
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:20
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:19
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:18
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:17
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:16
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:15
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:14
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:13
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:12
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:11
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:10
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:9
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:8
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:7
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:6
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:5
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:4
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:3
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:2
          May-17 7:27:44 AM EnvisaLink DEBUG Zone Device Found: Z:1
          May-17 7:27:42 AM EnvisaLink DEBUG Partition Device Found: P:1
          May-17 7:27:41 AM EnvisaLink INFO EnvisaLink version 3.0.0.40
          May-17 7:27:41 AM Starting Plug-In Initializing plugin EnvisaLink ...

          Comment


          • #6
            do you ever see a BypassedZonesBitfieldDump message in your debug logs? for example if you try to bypass another zone?

            Comment


            • #7
              Originally posted by spud View Post
              do you ever see a BypassedZonesBitfieldDump message in your debug logs? for example if you try to bypass another zone?
              No, I never see that in the log. I just tapped Bypass for "Living Room Door". The bypassed icon never changed from "Active". I confirmed on the alarm panel that the zone was bypassed. Here is the log.

              May-17 7:47:48 AM EnvisaLink DEBUG PartitionNotReady 1
              May-17 7:47:48 AM EnvisaLink DEBUG KeypadLedStatePartition1Only 88
              May-17 7:47:48 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 00
              May-17 7:47:45 AM EnvisaLink DEBUG CommandAcknowledge 000
              May-17 7:47:44 AM EnvisaLink DEBUG Request: Poll
              May-17 7:47:01 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 08
              May-17 7:46:59 AM EnvisaLink DEBUG KeypadLedStatePartition1Only 80
              May-17 7:46:46 AM EnvisaLink DEBUG PartitionNotReady 1
              May-17 7:46:46 AM EnvisaLink DEBUG KeypadLedStatePartition1Only 88
              May-17 7:46:46 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 00
              May-17 7:46:45 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 08
              May-17 7:46:44 AM EnvisaLink DEBUG CommandAcknowledge 071
              May-17 7:46:44 AM EnvisaLink DEBUG Request: SendKeystrokeString 1*134#
              May-17 7:46:44 AM Device Control Device: EnvisaLink Security Living Room Door to Bypass (-1000) by/from: CAPI Control Handler

              Comment


              • #8
                ok I will ask the Envisacor developer for what could be causing this. What panel model do you have?

                Could you try one more time with a zone which has a lower id like 1, 2 or 3 (this is the only difference I see with how I test it here)

                Comment


                • #9
                  Originally posted by spud View Post
                  ok I will ask the Envisacor developer for what could be causing this. What panel model do you have?

                  Could you try one more time with a zone which has a lower id like 1, 2 or 3 (this is the only difference I see with how I test it here)
                  I have a DSC PC1864. I just tested with Zone 2. The same behavior - I confirmed that the zone was bypassed on the alarm panel, and the icon never changed from "Active". Sorry about the extra Zone 3 messages in the log. Zone 3 is a motion, and my wife walked by. Here is the log:

                  May-17 8:06:48 AM EnvisaLink DEBUG PartitionNotReady 1
                  May-17 8:06:47 AM EnvisaLink DEBUG KeypadLedStatePartition1Only 88
                  May-17 8:06:47 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 00
                  May-17 8:06:24 AM EnvisaLink DEBUG ZoneRestored 003
                  May-17 8:06:24 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 08
                  May-17 8:06:22 AM EnvisaLink DEBUG ZoneOpen 003
                  May-17 8:06:22 AM EnvisaLink DEBUG KeypadLedStatePartition1Only 80
                  May-17 8:06:14 AM EnvisaLink DEBUG PartitionNotReady 1
                  May-17 8:06:14 AM EnvisaLink DEBUG KeypadLedStatePartition1Only 88
                  May-17 8:06:14 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 00
                  May-17 8:06:13 AM EnvisaLink DEBUG KeypadLedflashStatePartition1Only 08
                  May-17 8:06:12 AM EnvisaLink DEBUG CommandAcknowledge 071
                  May-17 8:06:12 AM EnvisaLink DEBUG Request: SendKeystrokeString 1*102#
                  May-17 8:06:12 AM Device Control Device: EnvisaLink Security Entry Doors to Bypass (-1000) by/from: CAPI Control Handler

                  Comment


                  • #10
                    FYI, I have been having this same issue. But I just updated to firmware 01.12.195 on my EVL3 and everything is working now.

                    Comment


                    • #11
                      Originally posted by gerard927 View Post
                      FYI, I have been having this same issue. But I just updated to firmware 01.12.195 on my EVL3 and everything is working now.
                      AFAIK, the firmware updates are pushed from your online account. How did you get .195?

                      Comment


                      • #12
                        I don't leave my EVL-3 connected to the EyezOn server. No one (besides me) needs to be able to remotely see what state my alarm is in. So from time to time, I add my EVL-3 back to my account to allow any firmware updates to push. Then I remove it again.

                        When I did that this past week I got the new firmware, which fixed the bypass status issue. For me, at least.

                        Comment


                        • #13
                          Originally posted by gerard927 View Post
                          ... So from time to time, I add my EVL-3 back to my account to allow any firmware updates to push. Then I remove it again.

                          When I did that this past week I got the new firmware, which fixed the bypass status issue. For me, at least.
                          OK.

                          I'm still on 01.12.191, so I guess patience until the update kicks in.

                          Comment


                          • #14
                            Good to see that I am not the only one experiencing this. My EVL3 is connected to my online account and stuck at 191. I wonder if there is any way to request a firmware update rather that waiting for it to eventually make it to my device. I will send in a support request to EnvisaLink and see if I get a response.

                            Comment


                            • #15
                              Originally posted by automateme View Post
                              Good to see that I am not the only one experiencing this. My EVL3 is connected to my online account and stuck at 191. I wonder if there is any way to request a firmware update rather that waiting for it to eventually make it to my device. I will send in a support request to EnvisaLink and see if I get a response.
                              You can ask them to force an update, if you give them the mac address of your EVL board.

                              Comment

                              Working...
                              X