Announcement

Collapse
No announcement yet.

Trouble in message reading from AD2USB under check and bypass situations

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

  • Trouble in message reading from AD2USB under check and bypass situations

    After slowly diving into a Vista-20P integration we are finding two issues coming up:

    1) When any zone is bypassed any future zone that is faulted (even if restored) will show bypassed in HomeSeer.

    2) When any zone is in check condition, HomeSeer will report that zone correctly as a check condition but any other faulted zone will fault, then immediately restore (even if it stays faulted). Also motion zones will not report at all during a check condition. (example below)

    The end result is, if we bypass or have any zone in check condition our events that tie to the Vista zones stop working. But, if the system is running normally with no bypasses or check conditions all works well.

    Here are some debug messages when the "bad things" are happening:

    This example shows when a zone is already bypassed in the system and one gets faulted that HomeSeer (the plugin, really) is setting the faulted zone to bypass incorrectly:
    Jan-22 7:53:56 AM Vista Alarm Updated Cleared Zones, System is Faulted
    Jan-22 7:53:56 AM Vista Alarm [0001031110000000----],002,[f70200ff1002030038020000000000],"FAULT 02 GARAGE UPSTAIRS DOOR "
    Jan-22 7:53:56 AM Vista Alarm Processing msg on Partition 1
    Jan-22 7:53:56 AM Vista Alarm Zone changed. Set device Vista Zone 2 to Value=Bypass
    Jan-22 7:53:55 AM Vista Alarm Updated Cleared Zones, System is Faulted
    Jan-22 7:53:54 AM Vista Alarm !Sending.done

    Another example, it does not matter which zone gets faulted:
    Jan-22 7:39:21 AM Vista Alarm [0000031110000000----],012,[f70200ff1012030038020000000000],"FAULT 12 MASTER BEDROOM DOOR "
    Jan-22 7:39:21 AM Vista Alarm Processing msg on Partition 1
    Jan-22 7:39:21 AM Vista Alarm Zone changed. Set device Vista Zone 12 to Value=Bypass
    Jan-22 7:39:20 AM Vista Alarm !EXP:07,04,01

    Example of a system with at least one zone reporting CHECK, and another zone is faulted. In this example zone 12 never restored, the door stayed open but it returned immediately back to normal:

    Jan-22 8:01:25 AM Vista Alarm Updated Cleared Zones, System is Faulted
    Jan-22 8:01:25 AM Vista Alarm Zone changed. Set device Vista Zone 12 to Value=Normal
    Jan-22 8:01:14 AM Vista Alarm [0000030110000000----],012,[f70200ff1012030028020000000000],"FAULT 12 MASTER BEDROOM DOOR "
    Jan-22 8:01:14 AM Vista Alarm Processing msg on Partition 1
    Jan-22 8:01:14 AM Vista Alarm Zone changed. Set device Vista Zone 12 to Value=Fault
    Jan-22 8:01:13 AM Vista Alarm !EXP:07,04,01
    Jan-22 8:01:03 AM Vista Alarm !EXP:07,04,00
    Jan-22 7:59:32 AM Vista Alarm !EXP:07,03,00
    Jan-22 7:59:25 AM Vista Alarm !EXP:07,03,01

    I hope these debug logs can help get these two issues fixed. Or, if you feel we have a setting wrong please let me know. The problem now is we have to avoid using any bypasses for the automation system to work correctly and if a check condition ever occurs (like if a wireless transmitter battery goes low or dies) we have to fix fast, or everything stops working until resolved.

    On our system, this is easily re-creatable every time. If you need anything else from me to help, let me know. I am an IT professional and have intimate knowledge of the Vista line of programming.

  • #2
    what version of the plugin are you running? and curious if you know the fw of the vista 20p panel (it's usually on the main IC in the center of the panel; mine is 7.0)
    Mark

    HS3 Pro 3.0.0.534
    Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
    Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
    Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

    Comment


    • #3
      Hi Mark, panel is a newer version because we have a Tuxedo on it, 9.18. The Vista module is 3.0.0.15.

      We have a new 3rd problem, but not exactly related. I am finding that the AD2USB port is moving by itself. One minute we are on ttyUSB0 then I notice everyhting stops working. I check the logs and find the addin cannot open ttyUSB0. I go to the manage module, and find the AD2USB moved to ttyUSB1. I change to that port, stop and start the module all is OK again. A few hours go by, then it all starts over again and I find it moved back to ttyUSB0. Have you seen this before? This is on the HS3-sel Pro.

      So we have the bypass issue, the check issue, and now the serial issue. Happy to troubleshoot this. When it is working, all is perfect!

      Phil

      Comment


      • #4
        would you mind trying .10 on the following post. i made some changes between .10 and .15 regarding bypass and maybe broke it.

        http://forums.homeseer.com/showthread.php?t=165994

        just install the exe and nothing from the zip

        I am also having a feeling that different vista panels (and maybe even vista firmwares) handle events differently in terms of priority for displaying msgs. if this is the case. I'll never be able to account for all of this.
        Mark

        HS3 Pro 3.0.0.534
        Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
        Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
        Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

        Comment


        • #5
          Mark, this is an HoneTroller-Sel-Pro (so it's Linux based). Can you give me instructions for running this on that environment? Happy to downgrade ASAP.

          I have been really watching the behavior. Seems when a zone is faulted and a bypass exists anywhere on the system the fault does show correctly. But, then when the zone is restored it comes to show Bypass instead of normal. So it's part of the code where clearing from Fault to Normal occurs when some other zone is really bypassed for whatever reason. I am guessing the "check" problem is exactly the same or similar.

          The 9.18 chip I have will be the most common found as it is what is sold now on new systems (for the past year or two+?), and more importantly anyone who has a Tuxedo or Total Control subscription will need.

          Phil

          Comment


          • #6
            do you have remote access to the os? if so, you just need to remote in and go to the homeseer root folder and replace the exe from the zip i mentioned earlier.

            otherwise i have no idea.
            Mark

            HS3 Pro 3.0.0.534
            Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
            Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
            Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

            Comment


            • #7
              I was able to get in, and downgrade the EXE but the plugin won't load anymore when I install it at the point the COM port is opened. It is trying to convert a varchar to an Interger it seems. If I put back .15 it works again.

              .10 -> -rw-r--r-- 1 root root 178688 Feb 22 2014 HSPI_VistaAlarm.exe
              .15 -> -rw-r--r-- 1 root root 180736 May 1 2015 HSPI_VistaAlarm.exe.old

              Error is:

              Error: System.InvalidCastException: Conversion from string "v/ttyUSB0" to type 'Integer' is not valid. ---> System.FormatException: Input string was not in the correct format at System.Int32.Parse (System.String s) [0x00000] in :0 at Microsoft.VisualBasic.CompilerServices.IntegerType.FromStrin g (System.String Value) [0x00000] in :0 --- End of inner exception stack trace --- at Microsoft.VisualBasic.CompilerServices.IntegerType.FromStrin g (System.String Value) [0x00000] in :0 at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger (System.String Value) [0x00000] in :0 at HSPI_VistaAlarm.HSPI.InitIO (System.String Port) [0x00000] in :0 [3.0.0.10]

              On the new version, it works as:
              Opened COM port /dev/ttyUSB0

              Comment


              • #8
                ok. try this version. this includes the logic i wanted you to test

                again, just load the .exe from the zip
                Attached Files
                Mark

                HS3 Pro 3.0.0.534
                Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
                Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
                Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

                Comment


                • #9
                  No change in behavior, here is the log of the test on .18. The fault is good, but the restore to normal does not happen, instead it restores to an incorrect bypass message. So, when I restored zone 12 back to normal, HomeSeer shows it as "Bypass".

                  Jan-25 10:39:42 AM Vista Alarm MessageKey=DISARMED BYPASS Ready to Arm 1
                  Jan-25 10:39:38 AM Vista Alarm Updated Cleared Zones, System is Bypass-Ready
                  Jan-25 10:39:38 AM Vista Alarm [1000001110000000----],008,[f70200ff1008001c38020000000000],"DISARMED BYPASS Ready to Arm "
                  Jan-25 10:39:38 AM Vista Alarm Processing msg on Partition 1
                  Jan-25 10:39:38 AM Vista Alarm MessageKey=DISARMED BYPASS Ready to Arm 1
                  Jan-25 10:39:38 AM Vista Alarm Setting System to Bypass-Ready

                  Jan-25 10:39:38 AM Vista Alarm Zone changed. Set device Vista Zone 12 to Value=Bypass

                  Jan-25 10:39:38 AM Vista Alarm Clearing all zones for Ready-Bypass mode.
                  Jan-25 10:39:38 AM Vista Alarm Setting Partition 1 to Bypass-Ready
                  Jan-25 10:39:37 AM Vista Alarm !EXP:07,04,00
                  Jan-25 10:39:14 AM Vista Alarm MessageKey=FAULT-12
                  Jan-25 10:39:10 AM Vista Alarm Updated Cleared Zones, System is Faulted
                  Jan-25 10:39:10 AM Vista Alarm [0000001110000000----],012,[f70200ff1012000038020000000000],"FAULT 12 MASTER BEDROOM DOOR "
                  Jan-25 10:39:10 AM Vista Alarm Processing msg on Partition 1
                  Jan-25 10:39:10 AM Vista Alarm MessageKey=FAULT-12
                  Jan-25 10:39:10 AM Vista Alarm Zone changed. Set device Vista Zone 12 to Value=Fault

                  Comment


                  • #10
                    i'm getting lost with the sequence of events for this scenario. can you post back a 1,2,3 set of steps you execute that are provide the unexpected results
                    Mark

                    HS3 Pro 3.0.0.534
                    Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
                    Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
                    Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

                    Comment


                    • #11
                      Sure Mark, no problem.

                      1) Bypass any zone on the system
                      a. Note that the zone is showing correctly as bypassed in HS.

                      2) Fault any other zone(s) on the system
                      a. Note that the zone(s) is showing correctly as faulted in HS.

                      3) Restore the faulted zone(s) back to normal.
                      a. Note that the zone(s) is/are showing as Bypassed (not Normal) in HS. Problem is seen.

                      4) (optionally) Restore the bypassed zone from step #1 back to normal or faulted.
                      a. Any zone from step #2 will resume back to normal status in HS.

                      If you want to have a TeamViewer/join.me session I can demo this all in realtime.

                      Phil

                      Comment


                      • #12
                        Phil, i believe you are seeing what you are seeing on your setup. i just need be able to recreate it on my end so i can figure out the issue in the code.

                        what are you doing in #3 above to 'restore the faulted zone'
                        Mark

                        HS3 Pro 3.0.0.534
                        Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
                        Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
                        Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

                        Comment


                        • #13
                          Originally posted by mnsandler View Post
                          what are you doing in #3 above to 'restore the faulted zone'
                          Closing the door

                          Phil

                          Comment


                          • #14
                            Phil,

                            thanks. I'm starting to see the issue. what would trigger the plugin to change the zone state from bypass to normal? do you get a specific panel msg?

                            these panels don't send 'normal' state msgs. they only way the plugin knows everything is normal is when it receives a 'disarm-ready to arm' msg. The disarm-bypass msg doesn't tell the plugin which zones are normal and which are in bypass.

                            can you provide any additional info
                            Mark

                            HS3 Pro 3.0.0.534
                            Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
                            Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
                            Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

                            Comment


                            • #15
                              I discovered something in the logs I missed before. When the fault occurs on a door when the system has a bypass somewhere the zone goes to bypass for a few seconds before going to fault. Then, when the same zone returns back to normal it goes to the broken bypass state.

                              What I did not see is the bypass happens very fast, before the fault when the zone is faulted in a system when a bypass exists somewhere else. Below are the logs broken out when we are in and then when we are not in a bypass condition. I did it this way to compare the results good vs. bad.

                              The new info here is when a zone faults it goes to bypass then faulted very fast. I almost missed it, because it's a fraction of a second. Take note of the bypass at "Jan-25 3:40:18 PM" then the fault at "Jan-25 3:40:22 PM" 4 seconds later. All I did was fault the zone (i.e. open the door).

                              System has no bypasses / Door opened:
                              Jan-25 3:35:19 PM Vista Alarm !EXP:07,04,00
                              Jan-25 3:35:14 PM Vista Alarm [0001030110000000----],012,[f70200ff1012030028020000000000],"FAULT 12 MASTER BEDROOM DOOR "
                              Jan-25 3:35:14 PM Vista Alarm Processing msg on Partition 1
                              Jan-25 3:35:14 PM Vista Alarm MessageKey=FAULT-12
                              Jan-25 3:35:14 PM Vista Alarm Zone changed. Set device Vista Zone 12 to Value=Fault
                              Jan-25 3:35:14 PM Vista Alarm !EXP:07,04,01

                              System has no bypasses / Door closed:
                              Jan-25 3:35:27 PM Vista Alarm Updated Cleared Zones, System is Faulted
                              Jan-25 3:35:27 PM Vista Alarm Zone changed. Set device Vista Zone 12 to Value=Normal

                              System has a bypass / Door opened:
                              Jan-25 3:40:29 PM Vista Alarm MessageKey=FAULT-12
                              Jan-25 3:40:25 PM Vista Alarm Updated Cleared Zones, System is Faulted
                              Jan-25 3:40:25 PM Vista Alarm MessageKey=FAULT-12
                              Jan-25 3:40:22 PM Vista Alarm Updated Cleared Zones, System is Faulted
                              Jan-25 3:40:22 PM Vista Alarm [0001001110000000----],012,[f70200ff1012000038020000000000],"FAULT 12 MASTER BEDROOM DOOR "
                              Jan-25 3:40:22 PM Vista Alarm Processing msg on Partition 1
                              Jan-25 3:40:22 PM Vista Alarm MessageKey=FAULT-12
                              Jan-25 3:40:22 PM Vista Alarm Zone changed. Set device Vista Zone 12 to Value=Fault
                              Jan-25 3:40:18 PM Vista Alarm Updated Cleared Zones, System is Faulted
                              Jan-25 3:40:18 PM Vista Alarm [0001031110000000----],012,[f70200ff1012030038020000000000],"FAULT 12 MASTER BEDROOM DOOR "
                              Jan-25 3:40:18 PM Vista Alarm Processing msg on Partition 1
                              Jan-25 3:40:18 PM Vista Alarm MessageKey=FAULT 12 MASTER BEDROOM DOOR 1
                              Jan-25 3:40:18 PM Vista Alarm Zone changed. Set device Vista Zone 12 to Value=Bypass
                              Jan-25 3:40:18 PM Vista Alarm Setting System to Faulted
                              Jan-25 3:40:18 PM Vista Alarm Setting Partition 1 to Faulted
                              Jan-25 3:40:17 PM Vista Alarm !EXP:07,04,01

                              System has a bypass / Door closed:
                              Jan-25 3:40:34 PM Vista Alarm Updated Cleared Zones, System is Bypass-Ready
                              Jan-25 3:40:34 PM Vista Alarm MessageKey=DISARMED BYPASS Ready to Arm 1
                              Jan-25 3:40:34 PM Vista Alarm Setting System to Bypass-Ready
                              Jan-25 3:40:34 PM Vista Alarm Zone changed. Set device Vista Zone 12 to Value=Bypass
                              Jan-25 3:40:34 PM Vista Alarm Clearing all zones for Ready-Bypass mode.
                              Jan-25 3:40:34 PM Vista Alarm Setting Partition 1 to Bypass-Ready
                              Jan-25 3:40:33 PM Vista Alarm !EXP:07,04,00

                              Comment

                              Working...
                              X