Announcement

Collapse
No announcement yet.

Ademco Vista Plug-In Version 1.1.1

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

    Ademco Vista Plug-In Version 1.1.1

    Version 1.1.1

    Fixes
    - System status changed from Alarm mode to Disarmed
    - Unencrypt panel code returned too many digits
    - Do not send panel code with "Hit * for faults" msgs
    - Turn off Monitor status (device 99) if com port did not open
    - Set system status to Faulted when disarming and faults exist

    New Features
    - Added a * Disarmed * System Trigger that only fires when the panel changes from any Armed state to a Disarmed state

    Please reply to this message with issues and bugs

    Installation Instructions:
    You may install this new version over any existing version. The old version will be uninstalled. Your settings and devices will be retained.

    Note for Vista users: I have attempted to make this install package compatible with Windows Vista, but can't test it. If you receive an error installing this package, try the following:
    1. right click on a CMD icon and select run as Administrator
    2. Enter msiexec /i HomeSeerPluginVistaAlarm_1_1_1_0.msi (note: you will need to be in the directory where the msi file exists to run this.)

    Enjoy!
    Last edited by mnsandler; November 5, 2009, 10:21 PM.
    Mark

    HS3 Pro 4.2.19.5
    Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
    Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
    Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

    #2
    Installed 1.1.1 a week ago because i was having troubles with some "spurious" activity in my log... (looked like it was trying to arm in response to the "Hit * for faults".. and i saw in hte discription of the patch/upgrade

    "Do not send panel code with "Hit * for faults" msgs"

    Took care of my problem

    Thanks again for writing this plugin.. I thought i would have to change my alarm system in order to get Homeseer integration... (house came with a vista 20P panel)..

    Now.. i have everything i need..

    Thank you again
    Regards,

    Andrew B.

    Comment


      #3
      Delays

      I have a Vista 10se, and recently bought & installed the AD2USB and Vista plugin. I'm seeing that momentary open/close of zones doesn't cause any updates in HS at all. Is this normal?

      My first guess is that something isn't right, since the physical keypad with Chime on .. chimes .. which makes me think the AD2USB should also see/hear/do this, yet HS doesn't update the zones at all. (Last Changed stays the same, old)

      Thoughts?

      Comment


        #4
        Originally posted by dhayner View Post
        I have a Vista 10se, and recently bought & installed the AD2USB and Vista plugin. I'm seeing that momentary open/close of zones doesn't cause any updates in HS at all. Is this normal?

        My first guess is that something isn't right, since the physical keypad with Chime on .. chimes .. which makes me think the AD2USB should also see/hear/do this, yet HS doesn't update the zones at all. (Last Changed stays the same, old)

        Thoughts?
        If you are seeing a msg at the keypad, then what is happening is that the system is faulting and immediately going back to ready. let try the following...

        turn on debugging, and turn off 'suppress dup msgs' and run your momentary open/close on the zone. Then please post the log here so i can analyze what is captured/happening. If a zone fault msg is captured, then the plugin should be updating the device.
        Mark

        HS3 Pro 4.2.19.5
        Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
        Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
        Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

        Comment


          #5
          Ok, after a warm reboot, this is what I see at the end of the log as HS2 starts:

          11/3/2009 11:46:01 PM Vista Alarm 11111100 00000000 00010000 00101000, DISARMED+CHIME+Ready+to+Arm
          11/3/2009 11:46:05 PM Vista Alarm 11111100 00000000 00011100 00101000, COMM.+FAILURE
          11/3/2009 11:46:09 PM Vista Alarm 11111100 00000000 00010000 00101000, DISARMED+CHIME+Ready+to+Arm
          11/3/2009 11:46:10 PM Z-Wave Battery level report for sensor Front Yard Front Screen Door Sensor=82%
          11/3/2009 11:46:13 PM Vista Alarm 11111100 00000000 00011100 00101000, COMM.+FAILURE
          11/3/2009 11:46:17 PM Vista Alarm 11111100 00000000 00010000 00101000, DISARMED+CHIME+Ready+to+Arm
          11/3/2009 11:46:21 PM Vista Alarm 11111100 00000000 00011100 00101000, COMM.+FAILURE

          This is new. I rebooted moments ago because when I went to turn off the Chime, I got no response. I was trying this to quietly run some tests, but got no further and figured a reboot would fix whatever interface issue I was having. Apparently I'm wrong.

          Comment


            #6
            Originally posted by dhayner View Post
            Ok, after a warm reboot, this is what I see at the end of the log as HS2 starts:

            11/3/2009 11:46:01 PM Vista Alarm 11111100 00000000 00010000 00101000, DISARMED+CHIME+Ready+to+Arm
            11/3/2009 11:46:05 PM Vista Alarm 11111100 00000000 00011100 00101000, COMM.+FAILURE
            11/3/2009 11:46:09 PM Vista Alarm 11111100 00000000 00010000 00101000, DISARMED+CHIME+Ready+to+Arm
            11/3/2009 11:46:10 PM Z-Wave Battery level report for sensor Front Yard Front Screen Door Sensor=82%
            11/3/2009 11:46:13 PM Vista Alarm 11111100 00000000 00011100 00101000, COMM.+FAILURE
            11/3/2009 11:46:17 PM Vista Alarm 11111100 00000000 00010000 00101000, DISARMED+CHIME+Ready+to+Arm
            11/3/2009 11:46:21 PM Vista Alarm 11111100 00000000 00011100 00101000, COMM.+FAILURE

            This is new. I rebooted moments ago because when I went to turn off the Chime, I got no response. I was trying this to quietly run some tests, but got no further and figured a reboot would fix whatever interface issue I was having. Apparently I'm wrong.
            what keypad sequence to do you use to turn chime on and off? The plugin sends a [Code]+9 to change the chime.

            The COMM.+FAILURE msg is just logged right now. The plugin takes no action on it. If you don't have your alarm connected to a phone line/monitored, then i would suggest either disabling the Telco monitoring setting (field *92 on a 20se) so the alarm will stop trying to call out. Or you may need to remove the phone number for fields (*41 or *42 on a 20se)
            Mark

            HS3 Pro 4.2.19.5
            Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
            Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
            Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

            Comment


              #7
              I think I've fixed the Comm Failure now. I hadn't thought of that being for the Telco -- I thought it was for the comms to the AD2USB. I removed the numbers in *41 & *42 and I think shut off the test call feature too.

              So I went from this:
              11/4/2009 7:46:32 AM Vista Alarm 11111100 00000000 00010000 00101000, DISARMED+CHIME+Ready+to+Arm
              11/4/2009 7:46:36 AM Vista Alarm 11111100 00000000 00011100 00101000, COMM.+FAILURE
              11/4/2009 7:46:41 AM Vista Alarm Setting System to Faulted <<< This is all that happened with the front door opened <<<
              11/4/2009 7:46:41 AM Vista Alarm 11111100 00000011 00000000 00101000, COMM.+FAILURE
              11/4/2009 7:46:44 AM Vista Alarm 11111100 00000000 00010000 00101000, DISARMED+CHIME+Ready+to+Arm

              To this:
              11/4/2009 8:06:45 AM Vista Alarm 00000001 00000001 00011100 00101000, DISARMED+CHIME+Ready+to+Arm
              11/4/2009 8:06:48 AM Vista Alarm Setting System to Faulted
              11/4/2009 8:06:48 AM Vista Alarm Zone changed. Set device ^1 to Value=Fault
              11/4/2009 8:06:48 AM Vista Alarm 00000001 00000011 00000000 00101000, FAULT+01+ZONE+01
              11/4/2009 8:06:52 AM Vista Alarm Setting System to Disarmed-Ready
              11/4/2009 8:06:52 AM Vista Alarm Clearing all zones for Ready mode.
              11/4/2009 8:06:52 AM Vista Alarm Zone changed. Set device ^1 to Value=Normal
              11/4/2009 8:06:52 AM Vista Alarm 00000001 00000000 00011100 00101000, DISARMED+CHIME+Ready+to+Arm

              How's that look to you? I didn't test each zone yet but looks like they'll probably all respond & show properly now. I turned debugging back off & turned on Suppress Duplicate Messages. That should unclutter the log right?

              Thanks for your SPEEDY help with this!

              Comment


                #8
                Originally posted by dhayner View Post
                I think I've fixed the Comm Failure now. I hadn't thought of that being for the Telco -- I thought it was for the comms to the AD2USB. I removed the numbers in *41 & *42 and I think shut off the test call feature too.

                So I went from this:
                11/4/2009 7:46:32 AM Vista Alarm 11111100 00000000 00010000 00101000, DISARMED+CHIME+Ready+to+Arm
                11/4/2009 7:46:36 AM Vista Alarm 11111100 00000000 00011100 00101000, COMM.+FAILURE
                11/4/2009 7:46:41 AM Vista Alarm Setting System to Faulted <<< This is all that happened with the front door opened <<<
                11/4/2009 7:46:41 AM Vista Alarm 11111100 00000011 00000000 00101000, COMM.+FAILURE
                11/4/2009 7:46:44 AM Vista Alarm 11111100 00000000 00010000 00101000, DISARMED+CHIME+Ready+to+Arm

                To this:
                11/4/2009 8:06:45 AM Vista Alarm 00000001 00000001 00011100 00101000, DISARMED+CHIME+Ready+to+Arm
                11/4/2009 8:06:48 AM Vista Alarm Setting System to Faulted
                11/4/2009 8:06:48 AM Vista Alarm Zone changed. Set device ^1 to Value=Fault
                11/4/2009 8:06:48 AM Vista Alarm 00000001 00000011 00000000 00101000, FAULT+01+ZONE+01
                11/4/2009 8:06:52 AM Vista Alarm Setting System to Disarmed-Ready
                11/4/2009 8:06:52 AM Vista Alarm Clearing all zones for Ready mode.
                11/4/2009 8:06:52 AM Vista Alarm Zone changed. Set device ^1 to Value=Normal
                11/4/2009 8:06:52 AM Vista Alarm 00000001 00000000 00011100 00101000, DISARMED+CHIME+Ready+to+Arm

                How's that look to you? I didn't test each zone yet but looks like they'll probably all respond & show properly now. I turned debugging back off & turned on Suppress Duplicate Messages. That should unclutter the log right?

                Thanks for your SPEEDY help with this!
                this looks correct. did you retry changing the chime from the plugin?

                Also, Zone 1 should have updated on the status page since it was faulted

                the settings you mentioned will 'unclutter' the log
                Mark

                HS3 Pro 4.2.19.5
                Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
                Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
                Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

                Comment


                  #9
                  Hi Mark,

                  I just upgraded to 1.1.1 and I'm now seeing weird issues in my events.

                  I have one even that supposed to trigger on the vista burglar alarm status but I now have to set it at fire alarm for HS to display burglar alarm in the event

                  I tried saving it as the Burglar Alarm trigger but then I do that, the event screen shows as armed-instant...huh?

                  so now I'm worried because I don't know what the plugin is really set at.

                  see the 2 attached pics..weird

                  First pics show it set at Fire Alarm




                  BUT now the same event shows as Burglar Alarm on the event screen


                  help
                  thanks

                  Comment


                    #10
                    Eeeck! How did that get through Testing?

                    Let me see if i can get you revision, should be easy to fix. i think it is just a display problem on the event page.
                    Mark

                    HS3 Pro 4.2.19.5
                    Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
                    Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
                    Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

                    Comment


                      #11
                      Originally posted by mnsandler View Post
                      Eeeck! How did that get through Testing?

                      Let me see if i can get you revision, should be easy to fix. i think it is just a display problem on the event page.
                      hehe, great

                      Comment


                        #12
                        Hey All,
                        I posted v1.1.2 based on a bug Raven found. I thought it was significant enough to go ahead and post a fix/update right away.

                        See the new thread for an explanation and to download the new version. I have pulled v1.1.1.

                        http://forums.homeseer.com/showthread.php?p=893860
                        Mark

                        HS3 Pro 4.2.19.5
                        Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
                        Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
                        Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

                        Comment


                          #13
                          I see the same thing to. I was in a hurry when I upgraded and did not poke around. Good catch Raven.

                          Comment


                            #14
                            Originally posted by mnsandler View Post
                            Hey All,
                            I posted v1.1.2 based on a bug Raven found. I thought it was significant enough to go ahead and post a fix/update right away.

                            See the new thread for an explanation and to download the new version. I have pulled v1.1.1.

                            http://forums.homeseer.com/showthread.php?p=893860
                            Mark,
                            Thank you for the rapid response. I just upgraded to ver. 1.1.2.

                            I edited & saved all events that use System Triggers to make sure everything is synced as you suggested.

                            Events using system triggers display the correct name now.

                            Again thank you for outstanding plug-in support.

                            Cheers
                            Jim

                            Comment


                              #15
                              Originally posted by jkarney View Post
                              Mark,
                              Thank you for the rapid response. I just upgraded to ver. 1.1.2.

                              I edited & saved all events that use System Triggers to make sure everything is synced as you suggested.

                              Events using system triggers display the correct name now.

                              Again thank you for outstanding plug-in support.

                              Cheers
                              Jim
                              Great! thanks Mark for the fix and Jim for testing it out

                              I'll update now to 1.1.2

                              Comment

                              Working...
                              X