Announcement

Collapse
No announcement yet.

Not Connecting HS3P -> GEM-3200

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

  • Not Connecting HS3P -> GEM-3200

    I have not been able to establish a connection between the HS3P running on a Home troller unit to a Napco GEM-3200 panel using the 3.0.0.2 plug-in.

    I have the Napco automation chip and a PCI-Mini and a Tripplite/Keyspan USA-19HS adapter.

    I use the same adapter to connect with Quickloader.

    I installed Quickloader on the Home Troller and I can connect to the Napco panel with all the same hardware using Quickloader

    I increased the command timeout values to 100 and the retry to 10, but I still cannot establish a link.

    Any ideas?

  • #2
    napco modem settings

    Here is a screen shot showing the serial interface settings that exist on Quickloader installed on the HomeTroller. This connects without any problems.
    Attached Files

    Comment


    • #3
      Napco Plug in Logs

      5/2/2014 9:54:23 PM ~ Napco Gemini ~ INFO ~ ---------------------------------------------------------------------
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ INFO ~ Starting Up... Napco Gemini plug-in version = 3.0.0.2
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ INFO ~ ---------------------------------------------------------------------
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ INFO ~ hs.Version = 3.0.0.68
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ INFO ~ hs.InterfaceVersion = 4
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ INFO ~ hs.PluginLicenseMode = Registered. Thank you!
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ ---------------------------------------------------------------------
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ INI values from hspi_napco_gemini.ini
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ INI Version = 3.0.0.2
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ ---------------------------------------------------------------------
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ MasterCode=[removed]
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ COMPort=COM9
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ MaxZones=20
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ CmdTimeout=100
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ MaxRetry=10
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ UseIcons=True
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ Log Incoming Status=True
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ Log Outgoing Commands=True
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ Log Debug Info=True
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ WebArmButton=True
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ WebDisarmButton=True
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ WebBypassButton=True
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ WebRelayButtons=True
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ KeypadRefresh=20
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ LogZonesStr=*
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ LogZones =
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ BypassZonesStr=
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ BypassZones =
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ logFileDebug=C:\Program Files\HomeSeer HS3/Logs/NapcoDebug.log
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ logLvl=79 [Always] [Err] [Info] [Incoming] [Outgoing] [Debug]
      5/2/2014 9:54:23 PM ~ Napco Gemini ~ DEBUG ~ ---------------------------------------------------------------------
      5/2/2014 9:56:03 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/2/2014 9:56:03 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/2/2014 9:57:48 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/2/2014 9:57:48 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/2/2014 9:59:33 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/2/2014 9:59:33 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/2/2014 10:01:19 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/2/2014 10:01:19 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/2/2014 10:03:04 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/2/2014 10:03:04 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/2/2014 10:04:49 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/2/2014 10:04:49 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/2/2014 10:06:34 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/2/2014 10:06:34 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/2/2014 10:08:19 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/2/2014 10:08:19 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/2/2014 10:10:04 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/2/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/2/2014 10:11:50 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/2/2014 10:11:50 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check

      5/4/2014 10:10:04 PM ~ Napco Gemini ~ INFO ~ ---------------------------------------------------------------------
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ INFO ~ Starting Up... Napco Gemini plug-in version = 3.0.0.2
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ INFO ~ ---------------------------------------------------------------------
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ INFO ~ hs.Version = 3.0.0.68
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ INFO ~ hs.InterfaceVersion = 4
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ INFO ~ hs.PluginLicenseMode = Registered. Thank you!
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ ---------------------------------------------------------------------
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ INI values from hspi_napco_gemini.ini
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ INI Version = 3.0.0.2
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ ---------------------------------------------------------------------
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ MasterCode=[removed]
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ COMPort=COM9
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ MaxZones=20
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ CmdTimeout=100
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ MaxRetry=10
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ UseIcons=True
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ Log Incoming Status=True
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ Log Outgoing Commands=True
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ Log Debug Info=True
      5/4/2014 10:10:04 PM ~ Napco Gemini ~ DEBUG ~ WebArmButton=True
      5/4/2014 10:10:05 PM ~ Napco Gemini ~ DEBUG ~ WebDisarmButton=True
      5/4/2014 10:10:05 PM ~ Napco Gemini ~ DEBUG ~ WebBypassButton=True
      5/4/2014 10:10:05 PM ~ Napco Gemini ~ DEBUG ~ WebRelayButtons=True
      5/4/2014 10:10:05 PM ~ Napco Gemini ~ DEBUG ~ KeypadRefresh=20
      5/4/2014 10:10:05 PM ~ Napco Gemini ~ DEBUG ~ LogZonesStr=*
      5/4/2014 10:10:05 PM ~ Napco Gemini ~ DEBUG ~ LogZones =
      5/4/2014 10:10:05 PM ~ Napco Gemini ~ DEBUG ~ BypassZonesStr=
      5/4/2014 10:10:05 PM ~ Napco Gemini ~ DEBUG ~ BypassZones =
      5/4/2014 10:10:05 PM ~ Napco Gemini ~ DEBUG ~ logFileDebug=C:\Program Files\HomeSeer HS3/Logs/NapcoDebug.log
      5/4/2014 10:10:05 PM ~ Napco Gemini ~ DEBUG ~ logLvl=79 [Always] [Err] [Info] [Incoming] [Outgoing] [Debug]
      5/4/2014 10:10:05 PM ~ Napco Gemini ~ DEBUG ~ ---------------------------------------------------------------------
      5/4/2014 10:11:45 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/4/2014 10:11:45 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/4/2014 10:13:30 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/4/2014 10:13:30 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/4/2014 10:15:15 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/4/2014 10:15:15 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/4/2014 10:17:00 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/4/2014 10:17:00 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/4/2014 10:18:45 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/4/2014 10:18:45 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/4/2014 10:20:30 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/4/2014 10:20:30 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/4/2014 10:22:15 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/4/2014 10:22:15 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/4/2014 10:24:00 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/4/2014 10:24:00 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/4/2014 10:25:46 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/4/2014 10:25:46 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check
      5/4/2014 10:27:31 PM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
      5/4/2014 10:27:31 PM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for status check

      Comment


      • #4
        It appears to be opening the COM9 port as expected but the signaling isn't working correctly to indicate the panel is ready to talk to the plugin. I have a PCI-MINI around here somewhere so I'll have to break that out and give it a try. I'll be able to test this weekend and get back to you.
        HS 3.0.0.435 (PRO)
        Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
        Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
        Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory
        http://www.kazteel.com/

        Comment


        • #5
          I tested this today. I disconnected my GEM-RS232 from the panel and the USB/DB9 serial port converted. I replaced that with my PCI-MINI.

          Before: Panel -> GEM-RS232 -> USB/DB9 -> USB Hub -> PC/HS3
          After: Panel -> PCI-MINI -> USB/DB9 -> USB Hub -> PC/HS3

          After restarting HS3, I was able to successfully establish the same connectivity via PCI-MINI as with GEM-RS232. The key differences between your and my setup then is the USB to serial converter and the windows driver. You have a 3200 panel and I have a 9600 but I have heard back from others with the 3200 panel and theirs is working.

          It would appear that the CTS/RTS hardware handshaking isn't happening correctly with your setup. This plugin is VB.net 4. It relies on the VB SerialPort class and the underlying windows driver for the serial port hardware. SerialPort.CtsHolding is the property that tracks the state of the CTS line. There is a specific protocol flow that has to happen between the client (HS3 w/plugin) and the Napco Panel. The basic flow is the client checks CTS for true (is panel free), then writes a hail message to the panel, then watches CTS to change to false. It's that last step that the plugin is waiting for and never sees based on your debug log messages.

          I'm using a basic VSCOM USB to DB9 serial port adapter with an FTDI serial port driver that came with it. I've run this on my dev and prod machines with no special changes to the windows port settings. Images below show their settings.







          I've seen significant compatibility issues with other serial devices connected to windows with USB/Serial converters. Often the windows driver is critical to getting them to work correctly. I don't know if that's what you might be facing here? Do you have other USB/Serial converters you could try?
          HS 3.0.0.435 (PRO)
          Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
          Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
          Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory
          http://www.kazteel.com/

          Comment


          • #6
            I'll get a VSCOM adapter and give it a shot. They seem to have about 20 different models. Which model adapter do you have?

            Comment


            • #7
              I can't tell the exact model of this VS COM adapter by the outside packaging. Purchased back in 2005 when I picked up my Napco system. However, I did a google search for VS COM and found what I believe it to be on their main website. The pictures match anyway: http://www.vscom.de/619.htm

              Then looked for US distributors and found they only list one and it's in Canada. They want $49 for a single one of these, ugh.
              http://www.electronicnetwork.ca/en/usb-com-mini.html


              Looking on amazon I can't find VS COM but I do see USB/serial adapters that look cosmetically identical like this USBGear adapter which has a FTDI chipset for $20.


              Looking on other sites like bestbuy.com I see a bunch of other adapters for $10-$20. I wish I knew if any of them were worth purchasing.
              HS 3.0.0.435 (PRO)
              Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
              Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
              Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory
              http://www.kazteel.com/

              Comment


              • #8
                There's also this TrendNET USB/serial for $9. I'm going to get one of these and try it. Claims it supports all the necessary signals.

                TRENDnet Converter

                Install as a standard Windows COM port, full RS-232 modem control signals, RS-232 data signals, TxD, RxD, RTS, CTS, DSR, DTR, DCD, RI, GND
                HS 3.0.0.435 (PRO)
                Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
                Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
                Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory
                http://www.kazteel.com/

                Comment


                • #9
                  Thanks... I purchased the VSCOM USB-COM Mini model 619 from Serial Stuff for $37.88 (includes shipping). I'll give it a shot when it arrives.

                  Comment


                  • #10
                    I received the TrendNet USB to Serial today, plugged it in, change the COM port for the plugin and it worked as expected. Hopefully you have similar luck with the VS COM you purchased.
                    HS 3.0.0.435 (PRO)
                    Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
                    Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
                    Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory
                    http://www.kazteel.com/

                    Comment


                    • #11
                      Plugged in the VSCOM adapter and updated the comm port. No luck. I shutdown HS3 and opened Quickloader. Changed the com port and it worked with the new adapter. shut down Quickloader and restarted HS3. Still no luck.

                      Any ideas?

                      I disabled and reenabled the plug in. Here is the log excerpt:


                      May-27 3:04:00 PM HSTouch Server Debug 03:04:00:1562 ~ Updating device enumerator due to a device change.
                      May-27 3:03:19 PM Plug-In Finished initializing plug-in Napco Gemini
                      May-27 3:03:16 PM Info Plugin Napco Gemini with instance: has disconnected
                      May-27 3:03:16 PM Error Initializing plug-in(1): Napco Gemini Instance::Unable to establish a good connection to the Napco Panel.
                      May-27 3:03:10 PM Napco Gemini TIMEOUT waiting for panel to be ready for our command
                      May-27 3:03:00 PM HSTouch Server Debug 03:03:00:1562 ~ Updating device enumerator due to a device change.
                      May-27 3:03:00 PM Napco Gemini TIMEOUT waiting for panel to be ready for our command
                      May-27 3:02:49 PM Napco Gemini TIMEOUT waiting for panel to be ready for our command
                      May-27 3:02:39 PM Napco Gemini TIMEOUT waiting for panel to be ready for our command
                      May-27 3:02:34 PM Napco Gemini hs.PluginLicenseMode = Registered. Thank you!
                      May-27 3:02:34 PM Napco Gemini hs.InterfaceVersion = 4
                      May-27 3:02:34 PM Napco Gemini hs.Version = 3.0.0.96
                      May-27 3:02:34 PM Napco Gemini ---------------------------------------------------------------------
                      May-27 3:02:34 PM Napco Gemini Starting Up... Napco Gemini plug-in version = 3.0.0.3
                      May-27 3:02:34 PM Napco Gemini ---------------------------------------------------------------------
                      May-27 3:02:33 PM Info Plugin Napco Gemini has connected. IP:127.0.0.1:2384

                      Comment


                      • #12
                        Here is what is listed on the Plug-In Status page:

                        **FATAL**: Failed getting InterfaceStatus from Napco Gemini - the interface was not found in the list of active interfaces.

                        Comment


                        • #13
                          I'm running the Hometroller with Windows XP. Out of the box, COM1-8 were being used by something. The Z-Stick took COM9 and the three USB-Seruial Adapters that I tried took COM10, COM11 and COM12. Does the script support high COM Port Numbers?

                          Comment


                          • #14
                            When I swapped my VS COM for the TrendNet ($9/amazon) it recreated it as COM10. I had to edit my INI file in C:\Program Files (x86)\HomeSeer HS3\Config\hspi_napco_gemini.ini to get this to take. I'll have to look at the plugin to see why the config page didn't present cleanly after a COM port change. Anyway, yes, it works with COM10 so I do not expect any issues due to COM# or COM##

                            I've been doing a lot of google searching trying to find anything to help with your situation. I've found examples where driver issues cause strange behavior, something that works with hyperterminal doesn't work with DotNet code but a windows reboot seemed to fix it LINK. I also came across the FTDI support page. In the section on CTS/RTS they mention some devices could invert the CTS signal. There are some interesting RS232 to USB articles that cover some of the challenges we might face with different chipsets and why the driver layer is so important.

                            What this boils down to is the DotNet4 SerialPort class CtsHolding property isn't behaving as required. The plugin checks CTS to see if the panel is ready for the plugin to send data to it. If the CTS state never changes the plugin issues those timeout warnings that you are seeing.

                            I'll see about working up a debug version with some switches we can add to the hspi_napco_gemini.ini to test inverting the CTS state or to ignore it initially and send the HAIL anyway to see if we can get this working.

                            I understand your frustration as QuickLoader works but the DotNet4 SerialPort based plugin doesn't. I wish I had the HomeTroller hardware you have to test with. I'll post again when I have a debug version for you to test with.

                            Nathan
                            Last edited by nfrobertson; May 29th, 2014, 01:57 PM. Reason: add article link
                            HS 3.0.0.435 (PRO)
                            Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
                            Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
                            Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory
                            http://www.kazteel.com/

                            Comment


                            • #15
                              Related to my testing with that new TrendNet USB/serial adapter ($9/amazon) I just noticed that my Current Cost ENVI was no longer working. Looking in windows device manager it indicated the port could not start. I looked at all my ports and found that the TrendNet also appears to use a Prolific driver and apparently windows had updated to the latest from 10/2013 when I installed the TrendNet adapter. That driver seems incompatible with the Current Cost ENVI (black plug, white cable) which is also an older Prolific.

                              So, I went three rounds with windows and trying to downgrade back to the 2008 era driver that Current Cost provides. What worked was to run the driver install provided by Current Cost which first uninstalled the existing driver, reboot, re-run the install and when windows pops the balloon that it's installing device software click it, and tell it to skip the windows update check, and reboot. This seems to have left the correct older 2008 Prolific driver in place. I'm now back using my VS COM USB/serial as it's an FTDI chipset for the Napco panel and the 2008 Prolific so Current Cost ENVI is happy.

                              My point in all this is that the driver used for a USB/serial adapter is critical to it functioning as desired with hardware.

                              My VS COM is using a 7/12/2013 FTDI driver, screen shot in a previous post. What driver version does your VS COM show?
                              HS 3.0.0.435 (PRO)
                              Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
                              Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
                              Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory
                              http://www.kazteel.com/

                              Comment

                              Working...
                              X