Announcement

Collapse
No announcement yet.

Event trigger using Keypad Code or manual / keypad Arm or Disarm?

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

  • Event trigger using Keypad Code or manual / keypad Arm or Disarm?

    @Spud
    I need to trigger Events based on when the physical keypad is used to Arm or Disarm the system.

    my goal is to have a manual entry at a physical keyboard to run different actions than an event triggered by a non-manual input.

    Is there a way to do this?

    thx!

  • #2
    bump

    Comment


    • #3
      No, I don't think that's possible.

      Comment


      • #4
        Originally posted by spud View Post
        No, I don't think that's possible.
        Awhile back I too wanted to be able to do this. I armed and disarmed my alarm while having the plugin in debug for logs.

        Thought I found the user bin numbers in the text string.

        I'll look for the debug logs over the weekend and post what I think is the user codes.

        Spud - maybe you'll be able to extract the codes from the text?

        Thanks,

        Jim

        Comment


        • #5
          Spud,

          Below are examples from the debug log.

          Armed alarm in Away - from Debug log:

          Code:
          Jul-02 09:02:23 DEBUG RealtimeCIDEvent 3401010030
          Breakdown:

          Code:
          Q = Qualifier. 3 = Restoral
          XXX = 3 digit CID code  401 'OPEN/CLOSE BY USER'
          PP = 2 digit Partition  01
          ZZZ = Zone or User (depends on CID code)  in this case User 003
          0 = Always 0 (padding)
          ------------------------------------------------------------------

          Armed alarm in Stay - from Debug log:

          Code:
          Jun-30 08:32:39 DEBUG RealtimeCIDEvent 3441010030
          Breakdown:

          Code:
          Q = Qualifier. 3 = Restoral
          XXX = 3 digit CID code  441 'Armed in STAY mode'
          PP = 2 digit Partition  01
          ZZZ = Zone or User (depends on CID code)  in this case User 003
          0 = Always 0 (padding)
          ------------------------------------------------------------------

          Disarmed - from Debug log:

          Code:
          Jun-30 08:48:39 DEBUG RealtimeCIDEvent 1401010040
          Breakdown:

          Code:
          Q = Qualifier. 1 = Event
          XXX = 3 digit CID code  401 'OPEN/CLOSE BY USER'
          PP = 2 digit Partition  01
          ZZZ = Zone or User (depends on CID code)  in this case User 004
          0 = Always 0 (padding)
          ------------------------------------------------------------------

          Example from 'EnvisaLinkTPI-ADEMCO-1-03.pdf' (see attached)

          Code:
          Realtime CID Event
          When a system event happens that is signaled to either the Envisalerts
          servers or the central monitoring station, it is also presented through this
          command. The CID event differs from other TPI commands as it is a
          binary coded decimal, not HEX.
          QXXXPPZZZ0
          Where:
          Q = Qualifier. 1 = Event, 3 = Restoral
          XXX = 3 digit CID code
          PP = 2 digit Partition
          ZZZ = Zone or User (depends on CID code)
          0 = Always 0 (padding)
          NOTE: The CID event Codes are ContactID codes. Lists of these codes
          are widely available but will not be reproduced here.  (see attached 'ADEMCO CONTACT ID REPORTING')
          Example:
          3441010020
          3 = Restoral (Closing in this case)
          441 = Armed in STAY mode
          01 = Partition 1
          002 = User 2 did it
          0 = Always 0
          The 'RealtimeCIDEvent' doesn't give much detail about how the system was armed, but paired with how you identify the arming now, this could be used to identify the user that activated the event.

          If you can parse this from the info being sent from Envisalink, could you have the plugin create virtual devices to represent the user codes that we could name? We could use the virtual devices to trigger events or insert into alerts sent by email or Pushover plugin.

          See what you can find or if you need any other info.

          Thanks,

          Jim
          Attached Files

          Comment


          • #6
            Jim, nice find. I was pretty sure it could be done because the eyezon web site posts that info, pulled from the evl3

            Sent from my SAMSUNG-SM-G935A using Tapatalk

            Comment


            • #7
              Hi Spud,

              Was wondering if you had a chance to look at this and whether or not it can be done?

              Thanks,

              Jim

              Comment


              • #8
                Originally posted by AutomatedJim View Post
                Hi Spud,

                Was wondering if you had a chance to look at this and whether or not it can be done?

                Thanks,

                Jim
                @Spud ?

                Comment


                • #9
                  yep it looks like it can be done, but I'm going to need your help for testing.

                  Comment


                  • #10
                    Originally posted by spud View Post
                    yep it looks like it can be done, but I'm going to need your help for testing.
                    Not a problem, I can test whatever you need.

                    A side note, I have alerts via Pushover and email to show that the alarm was disarmed from Away and Max. When disarming from Away, both my alerts for Away and Max are sent. I was hoping to test tomorrow morning in debug to send you logs.

                    See if you happen to see anything in that regard.

                    Thanks,

                    Jim

                    Comment


                    • #11
                      Originally posted by spud View Post
                      yep it looks like it can be done, but I'm going to need your help for testing.
                      ... I'm in, of course!

                      Comment


                      • #12
                        Originally posted by spud View Post
                        yep it looks like it can be done, but I'm going to need your help for testing.
                        Hi Spud, any ETA on this?

                        Comment


                        • #13
                          Originally posted by Ltek View Post
                          Hi Spud, any ETA on this?
                          Let's say before end of October...

                          Comment


                          • #14
                            in version 3.0.0.27 available here I have added a User Settings section in the config page, where you can assign one or several Ademco ids to each HS user:

                            Click image for larger version

Name:	usersettings.png
Views:	1
Size:	5.6 KB
ID:	1192452

                            and I have added a "User Access" device for each partition that shows the name or the id of the user that last armed or disarmed the partition

                            Click image for larger version

Name:	useraccess.png
Views:	1
Size:	30.1 KB
ID:	1192453

                            Please test and let me know.

                            Comment


                            • #15
                              Originally posted by spud View Post
                              in version 3.0.0.27 available here I have added a User Settings section in the config page, where you can assign one or several Ademco ids to each HS user:

                              [ATTACH]63572[/ATTACH]

                              and I have added a "User Access" device for each partition that shows the name or the id of the user that last armed or disarmed the partition

                              [ATTACH]63573[/ATTACH]

                              Please test and let me know.
                              Hi Spud,

                              One request.

                              Do we need to tie the HS3 users to the alarm users or make it optional so that we can fill in a name tied to the alarm user. Reason for it, my Dad has an alarm code but is not an HS3 user.

                              So far what I have found is that the new device updates correctly, Armed or Disarmed by <USER>, but if I reference the device in a Pushover using $$DSR:xxx:, it always shows Armed by <USER> regardless of arming or disarming.

                              Maybe just for the user access device, just show the user's name in the status and possibly another virtual device for the type of action, ie:

                              Armed Stay
                              Armed Night Stay
                              Armed Away
                              Armed Max
                              Disarmed

                              Other status types of action if available:

                              Chime On
                              Chime Off
                              Zone <NAME> Bypassed

                              Is this a possibility? If so, messages sent by email or Pushover could reference 'Type of Action' device and 'User Access' Device to include all types, ie:

                              'Zone <NAME> bypassed' by '<USER ACCESS>'
                              'Armed Stay' by '<USER ACCESS>'

                              I can also do a debug for the status, may not be until the weekend.

                              Thanks,

                              Jim

                              Comment

                              Working...
                              X