Announcement

Collapse

Contacting HomeSeer This Week

HomeSeer is open and operational this week. All orders are being processed and shipped as usual. However, some staff are working from home. If you need to contact HomeSeer for support or customer service, please use our Email or Chat options. https://homeseer.com/contact-us/
See more
See less

iTach IP2SL ALWAYS shows up as Disconnected

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

  • iTach IP2SL ALWAYS shows up as Disconnected

    I have your plugin installed. I have two Ztrollers. One is connected to an iTach IP2SL. The Ztroller (connected to the iTach) works fine but your plugin shows it as "Disconnected". Any thoughts?

    Device Properties page shows:
    Module: iTachIP2SL
    Revision: 710-1009-02
    Module Type: SERIAL
    Module Address: 1:1
    IP Address: 192.168.1.70
    TCP Port: 4999
    Network Status: Disconnected

    For the second Ztroller (on the setup->interfaces tab), I listed the interface type as "Ethernet", the IP address as "192.169.1.70", and the port as "4999".

    Am I configuring something wrong? Like I said, everything seems to work correctly but the "Disconnected" status bothers me.

    Thanks in advance for your help.

  • #2
    In case it matters, let me add that I also have a GC-100-6 and the serial module correctly shows up as "Connected".
    Module: GC-100-06
    Revision: 1.0.0
    Module Type: SERIAL
    Module Address: 1:1
    IP Address: 192.168.1.101
    TCP Port: 4999
    Network Status: Connected

    Comment


    • #3
      I also created a virtual com port and forwarded the TCP commands from 192.168.1.70:4999 to the virtual com port. Then I set the second Ztroller to use the new virtual com port (COM port 9).

      Again, everything works correctly -> HomeSeer is able to connect the second Ztroller to the virtual com port but the IP2SL serial device (created by your plugin and shown above) still shows disconnected.

      Just to be more clear, your plugin creates two devices for the IP2SL. One for the ethernet connection (port 4998) and one for the serial connection (port 4999). The ethernet device (port 4998) shows connected. It is the serial device (port 4999) that shows disconnected.

      Below are my HS logs showing the second Ztroller connecting to the new virtual com port

      :- :- :- :- :- :- :- :- Initializing Remote Z-Wave Interface -: -: -: -: -: -: -: -:
      5/3/2013 8:56:59 PM Z-Wave Initializing remote Z-Wave interface 1 (Master Bdrm) on COM port 9
      5/3/2013 8:56:59 PM Z-Wave Getting node information from controller...
      5/3/2013 8:57:01 PM Z-Wave Z-Wave Serial API version: 4
      5/3/2013 8:57:01 PM Z-Wave Z-Wave interface node ID: 22, Home ID: xxx
      5/3/2013 8:57:01 PM Z-Wave Found 43 Z-Wave nodes in interface node ID 22
      5/3/2013 8:57:01 PM Z-Wave Controller Manufacturer: HomeSeer Tech, ID=0x2, Type=0x1
      5/3/2013 8:57:01 PM Z-Wave Controller firmware version: 1.16
      5/3/2013 8:57:02 PM Z-Wave This Z-Wave PC Controller Library Version is: Z-Wave 2.78 (ZDK Version 5.02 Patch 3)
      5/3/2013 8:57:02 PM Z-Wave This Z-Wave PC Controller is Type: ZW_LIB_INSTALLER
      5/3/2013 8:57:02 PM Z-Wave -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

      And here is my HS logs showing the second Ztroller connecting directly to the IP2SL (before I created the virtual com port):

      5/3/2013 11:09:43 AM ~!~Z-Wave~!~ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
      5/3/2013 11:09:43 AM ~!~Z-Wave~!~ :- :- :- :- :- :- :- :- Initializing Remote Z-Wave Interface -: -: -: -: -: -: -: -:
      5/3/2013 11:09:43 AM ~!~Z-Wave~!~Initializing remote Z-Wave interface 1 (Master Bdrm) on Ethernet at 192.168.1.70
      5/3/2013 11:09:43 AM ~!~Z-Wave~!~Z-Wave Ethernet at IP 192.168.1.70, connected to interface ok.
      5/3/2013 11:09:43 AM ~!~Z-Wave~!~Getting node information from controller...
      5/3/2013 11:09:45 AM ~!~Z-Wave~!~Z-Wave Serial API version: 4
      5/3/2013 11:09:45 AM ~!~Z-Wave~!~Z-Wave interface node ID: 22, Home ID: xxx
      5/3/2013 11:09:45 AM ~!~Z-Wave~!~Found 43 Z-Wave nodes in interface node ID 22
      5/3/2013 11:09:45 AM ~!~Z-Wave~!~Controller Manufacturer: HomeSeer Tech, ID=0x2, Type=0x1
      5/3/2013 11:09:45 AM ~!~Z-Wave~!~Controller firmware version: 1.16
      5/3/2013 11:09:46 AM ~!~Z-Wave~!~This Z-Wave PC Controller Library Version is: Z-Wave 2.78 (ZDK Version 5.02 Patch 3)
      5/3/2013 11:09:46 AM ~!~Z-Wave~!~This Z-Wave PC Controller is Type: ZW_LIB_INSTALLER
      5/3/2013 11:09:46 AM ~!~Z-Wave~!~ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

      Is it possible that only one connection to the serial port can be made? So, when HS connects at startup, it doesn't allow your plugin to connect?

      I am able to connect to the IP2SL with my browser at IP 192.168.1.70.

      Any thoughts or ideas?

      Comment


      • #4
        If you don't have Global Cache device connected to the serial port (like a GC-IRE IR Extender), then a disconnected status is normal. You can add the IP address of your IP2SL to the UltraGCIR > Options > Global Cache Ignore List so the plug-in doesn't create a device for it.

        Regards,
        Ultrajones
        Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

        Comment

        Working...
        X