Announcement

Collapse
No announcement yet.

Frequent Serial Disconnects

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

  • Frequent Serial Disconnects

    For many years, I've had some problems with my GC-100-06 randomly disconnecting. It sometimes reconnects on its own, but sometimes requires me to manually reconnect (using the Device List "Disconnect/Reconnect" pull down). Lately, however, disconnects have become extremely frequent. Here are some examples of the log entries:
    Mar-12 9:19:34 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
    Mar-12 9:19:34 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
    Mar-12 9:19:32 AM Informational Watchdog Timer reconnect attempt succeeded.
    Mar-12 9:19:32 AM Informational Ethernet connection established to 192.168.2.70:4999
    Mar-12 9:19:32 AM Warning Watchdog Timer indicates TCP connection to Global Cache device [192.168.2.70] was lost.. Attempting to reconnect ...
    Mar-12 9:19:06 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
    Mar-12 9:19:04 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
    How can I figure out what is causing the disconnects?

    Thanks,
    Mike
    Last edited by Mike Johnson; March 12th, 2019, 09:36 AM. Reason: Remove irrelevant log entries.

  • #2
    From what I've seen with my GC-100's that disconnects like that are typically related to network connectivity issues. How are these connected?
    HS 3.0.0.548: 1965 Devices 1146 Events
    Z-Wave 3.0.1.262: 122 Nodes on one Z-Net

    Comment


    • #3
      Hardwired gigabit ethernet.

      It seems to be the serial port on the GC-100 only, or at least that's the notable offender. It does not show 'disconnected' on the HS Device List, but applying a Disconnect, then Reconnect to the GlobalCache SERIAL (GC001:1:1) seems to clear up the issue, for a time, anyway.

      Mike

      Comment


      • #4
        I guess I didn't do a great job describing the details. The symptoms are that the GC-100 stops responding to received IR commands sent to the GC-IRE, which is plugged into the serial port on the GC-100. When in the failure mode, HS can still send IR commands to the GC-100, which are executed properly through the GC-100 and on to the Xantech system. it's just the received IR commands that fail.

        Mike

        Comment


        • #5
          Originally posted by sparkman View Post
          From what I've seen with my GC-100's that disconnects like that are typically related to network connectivity issues. How are these connected?
          Do yours stay connected and responsive?

          Mike

          Comment


          • #6
            Originally posted by Mike Johnson View Post

            Do yours stay connected and responsive?

            Mike
            For the most part they do, but I do have one connected with ethernet over powerline and it drops off every once in a while and I see the same kind of error messages for it.
            HS 3.0.0.548: 1965 Devices 1146 Events
            Z-Wave 3.0.1.262: 122 Nodes on one Z-Net

            Comment


            • #7
              Something just isn't working correctly. It's getting worse and I'm not sure how to troubleshoot it.
              Mar-21 10:56:28 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:56:28 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:55:56 AM Informational Watchdog Timer reconnect attempt succeeded.
              Mar-21 10:55:56 AM Informational Ethernet connection established to 192.168.2.70:4999
              Mar-21 10:55:52 AM Warning Watchdog Timer indicates No response response from the Global Cache device [192.168.2.70] for 330 seconds.. Attempting to reconnect ...
              Mar-21 10:55:27 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:55:25 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:54:56 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:54:54 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:54:26 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:54:24 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:53:56 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:53:54 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:53:26 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:53:24 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:52:56 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:52:54 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:52:26 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:52:24 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:51:56 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:51:54 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:51:26 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:51:24 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:50:56 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
              Mar-21 10:50:54 AM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'

              Comment


              • #8
                And some new warnings:

                Mar-21 5:30:04 PM Informational Watchdog Timer reconnect attempt succeeded.
                Mar-21 5:30:04 PM Informational Ethernet connection established to 192.168.2.70:4999
                Mar-21 5:30:04 PM Warning Watchdog Timer indicates TCP connection to Global Cache device [192.168.2.70] was lost.. Attempting to reconnect ...
                Mar-21 5:30:04 PM Informational Ethernet connection established to 192.168.2.70:4999
                Mar-21 5:30:03 PM Warning No response/improper response from GC-100-06 [192.168.2.70] to command 'get_IR,2:2'
                Mar-21 5:30:01 PM Warning No response/improper response from GC-100-06 [192.168.2.70] to command 'get_IR,2:2'
                Mar-21 5:29:59 PM Warning No response/improper response from GC-100-06 [192.168.2.70] to command 'get_IR,2:1'
                Mar-21 5:29:57 PM Warning No response/improper response from GC-100-06 [192.168.2.70] to command 'get_IR,2:1'
                Mar-21 5:29:55 PM Warning No response/improper response from GC-100-06 [192.168.2.70] to command 'get_SERIAL,1:1'
                Mar-21 5:29:55 PM Warning No response/improper response from GC-100-06 [192.168.2.70] to command 'get_SERIAL,1:1'
                Mar-21 5:29:50 PM Informational Watchdog Timer reconnect attempt succeeded.
                Mar-21 5:29:50 PM Informational Ethernet connection established to 192.168.2.70:4998
                Mar-21 5:29:47 PM Warning Watchdog Timer indicates TCP connection to Global Cache device [192.168.2.70] was lost.. Attempting to reconnect ...
                Mar-21 5:24:53 PM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'
                Mar-21 5:24:53 PM Warning No response/improper response from SERIAL [192.168.2.70] to command 'id'

                Comment


                • #9
                  From your HomeSeer system, run the command ping 192.168.2.70 -n 500, then let me know if you're seeing any packet loss.
                  Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

                  Comment


                  • #10
                    Indeed some packet loss. I didn't need to wait for 500 requests to see the trend. Here's the report for 100 and then 20 requests. So what does that suggest?

                    Mike


                    Ping statistics for 192.168.2.70:
                    Packets: Sent = 100, Received = 85, Lost = 15 (15% loss),
                    Approximate round trip times in milli-seconds:
                    Minimum = 2ms, Maximum = 15ms, Average = 4ms

                    Ping statistics for 192.168.2.70:
                    Packets: Sent = 20, Received = 17, Lost = 3 (15% loss),
                    Approximate round trip times in milli-seconds:
                    Minimum = 2ms, Maximum = 3ms, Average = 2ms

                    Comment


                    • #11
                      Originally posted by Mike Johnson View Post
                      Indeed some packet loss. I didn't need to wait for 500 requests to see the trend. Here's the report for 100 and then 20 requests. So what does that suggest?

                      Mike
                      It suggests there is an issue on your network. How is the GC-100 connected network wise to your HS computer? Could be a bad port on the switch, a bad cable, etc.
                      HS 3.0.0.548: 1965 Devices 1146 Events
                      Z-Wave 3.0.1.262: 122 Nodes on one Z-Net

                      Comment


                      • #12
                        It’s been so long since I installed it, I don’t remember exactly, but I think it goes through a couple of switches and between 1st and 3rd floor, so plenty of opportunity for failing connections.

                        I will check connections and maybe try temporarily moving it closer to my HS machine to see if I can improve ping results.

                        Thanks for for the guidance.

                        Mike

                        Comment

                        Working...
                        X