Announcement

Collapse
No announcement yet.

Communication freeze

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

    #46
    As I mentioned, I have both plugins and only this one locks up. The PLM has been rock solid.

    Also, still working fine throughout the night! No crash or log warning.

    -BD

    Comment


      #47
      Spoke too soon!

      The device locked up just like it used to - following the light being turned off. So maybe the loss of communication yesterday was different, and I have had two different crashes show up - one is hard and the other soft? Dunno. As before, following this crash, cycling the monitor will not solve the problem. I will probably need to install the filter or change the ballast. Not a huge deal.

      The good news is that your watchdog worked. Here is the log:

      -----
      6/16/2012 10:23:38 AM Device Control Device: Laundry Room Lights (\38) OFF
      6/16/2012 10:23:38 AM Event Event Trigger "Lights (delayed action)"
      6/16/2012 10:22:14 AM Device Update Device: Power Energy Monitor Electric Meter kW Hours value set to 106332 (1063.322 kW Hours)
      6/16/2012 10:22:13 AM Device Update Device: Power Energy Monitor Electric Meter Watts value set to 539664 (5396.64 Watts)
      6/16/2012 10:21:41 AM Vista Alarm Could not restart the port. The monitor was shutdown.
      6/16/2012 10:21:38 AM Device Control Device: Laundry Room Lights (\38) ON
      6/16/2012 10:21:38 AM Event Event Trigger "Laundry Lights Test"
      6/16/2012 10:21:32 AM Vista Alarm Error opening COM port 4 to Vista Alarm
      6/16/2012 10:21:22 AM Vista Alarm Error opening COM port 4 to Vista Alarm
      6/16/2012 10:21:12 AM Vista Alarm Error opening COM port 4 to Vista Alarm
      6/16/2012 10:21:03 AM Insteon Received \6 (Master Bath Bathroom - Dusk/Dawn) Go OFF
      6/16/2012 10:21:02 AM Vista Alarm Error opening COM port 4 to Vista Alarm
      6/16/2012 10:21:00 AM Insteon Received \27 (Master Bath Shower - Dusk/Dawn) Go OFF
      6/16/2012 10:20:52 AM Vista Alarm Error opening COM port 4 to Vista Alarm
      6/16/2012 10:20:42 AM Vista Alarm Error opening COM port 4 to Vista Alarm
      6/16/2012 10:20:40 AM Insteon Received \34 (Upstairs East Hallway Motion Sensor 4 - Dusk/Dawn Sensor) Go OFF
      6/16/2012 10:20:32 AM Vista Alarm Error opening COM port 4 to Vista Alarm
      6/16/2012 10:20:22 AM Vista Alarm Error opening COM port 4 to Vista Alarm
      6/16/2012 10:20:12 AM Vista Alarm Error opening COM port 4 to Vista Alarm
      6/16/2012 10:20:02 AM Vista Alarm Error opening COM port 4 to Vista Alarm
      6/16/2012 10:20:00 AM Event Running script in background: ElectricCostCalc.vb
      6/16/2012 10:20:00 AM Event Event Trigger "Power Cost Calculator"
      6/16/2012 10:19:52 AM Vista Alarm Error opening COM port 4 to Vista Alarm
      6/16/2012 10:19:42 AM Vista Alarm Error opening COM port 4 to Vista Alarm
      6/16/2012 10:19:35 AM Vista Alarm Monitor terminated...
      6/16/2012 10:19:35 AM Vista Alarm Closed COM port 4
      6/16/2012 10:19:35 AM Vista Alarm Warning! Communications lost. Attempting to reset the port & monitor...
      6/16/2012 10:18:38 AM Event Deleting event after run: "Delayed Actions Lights (delayed action)"
      6/16/2012 10:18:38 AM Device Control Device: Laundry Room Lights (\38) OFF
      6/16/2012 10:18:38 AM Event Event Trigger "Lights (delayed action)"
      6/16/2012 10:18:35 AM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
      6/16/2012 10:18:35 AM Vista Alarm Processing msg on Partition 1
      6/16/2012 10:18:25 AM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
      6/16/2012 10:18:25 AM Vista Alarm Processing msg on Partition 1

      -BD
      -----
      Last edited by BrunDog; June 16, 2012, 05:20 PM.

      Comment


        #48
        well, that stinks. I was hoping the new driver would recovery the port...FTDI thought it would.

        so did you have to restart HS to get it going again, or did you have to restart the box?
        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


          #49
          Well, I tried to disable and re-enable the ports in Device Manager and it crashed the PC. So, it effectively was re-booted. Usually I plug and unplug, and that does it.

          Obviously I have a hardware problem. The laundry light ballast must be dumping some nasty load that is affecting something related to the AD2USB. It is hard to determine what, because the PC is unaffected, and the alarm is unaffected (and the PLM is too!). As you know, the PC is on a UPS and I tried powering the alarm off another circuit - no luck. I could try powering the UPS off another circuit, but I think I am just going to address the light ballast and make all the problems go away.

          On the other hand, when communications soft-froze earlier, restarting the port worked fine. So this is increasing the level of reliability IMO.

          I have turned off my light on/off automatic routine, and I am back on the motion sensor, so the number of events will be small anyway. Thanks again!

          -BD

          Comment


            #50
            Thanks for the info. while you're getting the ballast replaced, would you mind dropping in this version. I added a set of triggers called Vista Alarm Interface Trigger that will let you know when the connection is disconnected or reconnected, or non operational. I also revised the recovery process a little.
            Attached Files
            Last edited by mnsandler; June 17, 2012, 08:59 AM.
            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


              #51
              Nutech suggested I install an old fluorescent light near my test alarm power adapter in order to trigger a usb disconnect; and sure enough; i can (when the light turns off). but it really makes the ftdi connection very unhappy and it causes the drivers to unload from memory (similar to when you disconnect the physical usb cable).

              there is no way the plugin can recover from this as far as i know.

              I think I'm going to just raise a trigger when the plugin stops receiving msgs from the ad2usb. trying to restart the port/monitor seems futile. From there you can just restart hs or the box to recover; this seems to work for users who have this problem with the insteon/plm.

              I'll be interested to hear if the filter or ballast change resolves your issue.
              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


                #52
                Hi Mark,

                I am back from vacation... The system received messages and worked properly all week. Of course, the light was never turned on or off...

                Anyway, glad to hear you could duplicate the problem... I s'pose I ain't crazy then. I will orderthe filter or replace the ballast and will report back once installed.

                I installed the latest version, and can see there are new triggers. Please note that restarting HS will NOT fix the problem - only restarting the box or unplugging/replugging the USB connection will do it.

                Thanks again for all your help!

                -BD

                Comment


                  #53
                  Originally posted by BrunDog View Post
                  Hi Mark,

                  I am back from vacation... The system received messages and worked properly all week. Of course, the light was never turned on or off...

                  Anyway, glad to hear you could duplicate the problem... I s'pose I ain't crazy then. I will orderthe filter or replace the ballast and will report back once installed.

                  I installed the latest version, and can see there are new triggers. Please note that restarting HS will NOT fix the problem - only restarting the box or unplugging/replugging the USB connection will do it.

                  Thanks again for all your help!

                  -BD
                  well if you can use the trigger to restart the box, then we've made a little progress.

                  I'm still working on a sw solution to restart the port but nothing yet. Even calls to the FTDI .net library won't reestablish the port.

                  please let me know which solution (the filter or new ballast) fixes the problem
                  Last edited by mnsandler; June 25, 2012, 06:12 AM.
                  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


                    #54
                    Not sure what is happened, but... all of a sudden I cannot send commands to the alarm. It reads messages fine as you see, but my "Disarm" or other commands go ignored?!? The only thing I did was turn on "Suppress duplicate messages" after creating an event warning me via email when the interface could not be restarted. I checked the box and clicked "Save Changes". Now, no response! Any thoughts?

                    I see there is an "interface address" in the setup that was not there prior - what should it be set for? I have a Vista 15.

                    6/25/2012 11:43:00 PM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                    6/25/2012 11:43:00 PM Vista Alarm Processing msg on Partition 1
                    6/25/2012 11:43:00 PM Vista Alarm !Sending.....done
                    6/25/2012 11:42:52 PM Vista Alarm Sending [code]+1
                    6/25/2012 11:42:49 PM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                    6/25/2012 11:42:49 PM Vista Alarm Processing msg on Partition 1
                    6/25/2012 11:42:39 PM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                    6/25/2012 11:42:39 PM Vista Alarm Processing msg on Partition 1
                    6/25/2012 11:42:29 PM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                    6/25/2012 11:42:29 PM Vista Alarm Processing msg on Partition 1
                    6/25/2012 11:42:19 PM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                    6/25/2012 11:42:19 PM Vista Alarm Processing msg on Partition 1
                    6/25/2012 11:42:09 PM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                    6/25/2012 11:42:09 PM Vista Alarm Processing msg on Partition 1
                    6/25/2012 11:41:59 PM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                    6/25/2012 11:41:59 PM Vista Alarm Processing msg on Partition 1
                    6/25/2012 11:41:52 PM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                    6/25/2012 11:41:52 PM Vista Alarm Processing msg on Partition 1
                    6/25/2012 11:41:52 PM Vista Alarm !Sending.....done
                    6/25/2012 11:41:44 PM Vista Alarm Sending [code]+1
                    6/25/2012 11:41:40 PM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                    6/25/2012 11:41:40 PM Vista Alarm Processing msg on Partition 1

                    Comment


                      #55
                      BTW, restarting the box didn't resolve this (as expected).

                      I shutdown the monitor and ran AD2USBGUI. It read the panel messages fine but was not able to send commands either. Weird, huh... so I know it is not your plug-in. I used the "read settings" button, then exited and it started working. So I shut it down, restarted your monitor, and all is working fine again. So, I am unsure what happened this time?!? Probably a unique event, but it clearly happened when I clicked the save settings button. Thinking that "interface address" is the issue...

                      Here is the log now:
                      6/26/2012 12:02:32 AM Vista Alarm [1001000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                      6/26/2012 12:02:32 AM Vista Alarm Processing msg on Partition 1
                      6/26/2012 12:02:28 AM Vista Alarm !AUI:1606000000006563024543f531fb456cf5ec03010101
                      6/26/2012 12:02:28 AM Vista Alarm [1001010110000000----],008,[f700003f1008011c28020000000000]," DISARMED CHIME Ready to Arm "
                      6/26/2012 12:02:28 AM Vista Alarm Processing msg on Partition 1
                      6/26/2012 12:02:28 AM Vista Alarm !AUI:120600000000646c02456cf5ec0101010000
                      6/26/2012 12:02:28 AM Vista Alarm !Sending.done
                      6/26/2012 12:02:27 AM Vista Alarm Sending [code]+1
                      6/26/2012 12:02:26 AM Vista Alarm [1001000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                      6/26/2012 12:02:26 AM Vista Alarm Processing msg on Partition 1

                      -BD

                      Comment


                        #56
                        Originally posted by BrunDog View Post
                        Not sure what is happened, but... all of a sudden I cannot send commands to the alarm. It reads messages fine as you see, but my "Disarm" or other commands go ignored?!? The only thing I did was turn on "Suppress duplicate messages" after creating an event warning me via email when the interface could not be restarted. I checked the box and clicked "Save Changes". Now, no response! Any thoughts?

                        I see there is an "interface address" in the setup that was not there prior - what should it be set for? I have a Vista 15.
                        The plugin can now configure the ad2usb for you (so you don't have to use the ! cmd from hyperterminal/putty).

                        The interface address needs to be selected. this should be the unique keypad address you configured in your panel. My guess is the plugin reconfig'ed the ad2usb which may have caused the cmds to stop working

                        Just select the correct address and click Save again
                        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


                          #57
                          Originally posted by BrunDog View Post
                          BTW, restarting the box didn't resolve this (as expected).

                          I shutdown the monitor and ran AD2USBGUI. It read the panel messages fine but was not able to send commands either. Weird, huh... so I know it is not your plug-in. I used the "read settings" button, then exited and it started working. So I shut it down, restarted your monitor, and all is working fine again. So, I am unsure what happened this time?!? Probably a unique event, but it clearly happened when I clicked the save settings button. Thinking that "interface address" is the issue...

                          -BD
                          ok,
                          the attached exe seems to be able to recover the usb ports once hs is shutdown. Put it into your hs folder with the plugin.

                          So the next time you have comm issues, shutdown hs, and run this utility (there is some output to a console window, but its not very important). Then restart hs and see if the monitor will start.

                          I have a couple of emails into FTDI about all this, but they don't seem to be very responsive
                          Attached Files
                          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


                            #58
                            Originally posted by mnsandler View Post
                            The plugin can now configure the ad2usb for you (so you don't have to use the ! cmd from hyperterminal/putty).

                            The interface address needs to be selected. this should be the unique keypad address you configured in your panel. My guess is the plugin reconfig'ed the ad2usb which may have caused the cmds to stop working

                            Just select the correct address and click Save again
                            Oh, so you are saying my panel address (in my case, 20), should be entered in the Interface Address box? I already have (had) it in the Device Address field, next to Partition 1 in the Partitions tab. I thought that was enough. Now I have it in both places - saved settings and all seems well. Here is the log from that maneuver:

                            6/26/2012 9:30:50 AM Vista Alarm !AUI:120600000000626c02456cf5ec0101010000
                            6/26/2012 9:30:50 AM Vista Alarm !Sending.done
                            6/26/2012 9:30:50 AM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                            6/26/2012 9:30:50 AM Vista Alarm Processing msg on Partition 1
                            6/26/2012 9:30:50 AM Vista Alarm Sending [code]+1
                            6/26/2012 9:30:48 AM Vista Alarm !CONFIGADDRESS=20&CODE=0000&LRR=N&EXP=NNNNN&REL=NNNN&MASK=ff ffffff&DEDUPLICATE=N
                            6/26/2012 9:30:41 AM Vista Alarm !setting ADDRESS 20
                            6/26/2012 9:30:41 AM Vista Alarm !ADDRESS=20
                            6/26/2012 9:30:40 AM Vista Alarm Updating the configuration on the interface...
                            6/26/2012 9:30:40 AM Vista Alarm Settings page submitted
                            6/26/2012 9:30:38 AM Vista Alarm [1000000110000000----],008,[f700003f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
                            6/26/2012 9:30:38 AM Vista Alarm Processing msg on Partition 1

                            -BD

                            Comment


                              #59
                              Originally posted by mnsandler View Post
                              ok,
                              the attached exe seems to be able to recover the usb ports once hs is shutdown. Put it into your hs folder with the plugin.

                              So the next time you have comm issues, shutdown hs, and run this utility (there is some output to a console window, but its not very important). Then restart hs and see if the monitor will start.

                              I have a couple of emails into FTDI about all this, but they don't seem to be very responsive
                              You quoted my post regarding this "new" issue of me not being able to send messages to the system. I am convinced this is due to the addition of interface address dropdown. It came up as '0' (default?), and when I hit Save Settings, thats when things went wrong. As I said in the post immediately above this one, I corrected it and everything works now.

                              Therefore, I assume you are telling me to run this utility the next time the room light OFF causes the interface to lockup? If so, I can turn on my light on/off loop to force a crash and test this exe. Is that what you want me to do? If it works, I assume I can have an HS event, triggered by your communication loss trigger, run the exe, but you said HS needs to be shutdown, obviating the possibility of automatically launching it. Why does HS need be shut down?

                              -BD

                              Comment


                                #60
                                Originally posted by BrunDog View Post
                                You quoted my post regarding this "new" issue of me not being able to send messages to the system. I am convinced this is due to the addition of interface address dropdown. It came up as '0' (default?), and when I hit Save Settings, thats when things went wrong. As I said in the post immediately above this one, I corrected it and everything works now.
                                Yes, the send cmd issues was related to the ad2usb address being set to 0. Glads it working again.

                                The partition addresses can be completely different than the ad2usb address so it is necessary to enter the correct address everywhere (even if if appears redundant).

                                Originally posted by BrunDog View Post
                                Therefore, I assume you are telling me to run this utility the next time the room light OFF causes the interface to lockup? If so, I can turn on my light on/off loop to force a crash and test this exe. Is that what you want me to do? If it works, I assume I can have an HS event, triggered by your communication loss trigger, run the exe, but you said HS needs to be shutdown, obviating the possibility of automatically launching it. Why does HS need be shut down?
                                For some reason the usb port isn't being released while hs is running and the port is crashed. so we can't recovery while hs is running and thus a hs event is no help other than to start an external vbscript. if the manual recovery process (i outlined above) works, we can automate if using vbscript. a vbscript can shutdown hs, run the utlity, and then restart hs. and voila, hs is running again without intervention.
                                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

                                Working...
                                X