Announcement

Collapse
No announcement yet.

hs insteon error

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

    hs insteon error

    I have a raspberry pi version of hs4 set up for several years. Recently I think the insteon signal was intermittent. I rebooted the pi and now hs4 can not find the insteon. The error I get is:

    1/2/2022 4:23:46 PM

    Legacy-Plugin
    HSInsteon
    ERROR Cannot connect to port: /dev/ttyUSB0

    1/2/2022 4:23:46 PM

    Legacy-Plugin
    HSInsteon
    DEBUG ERROR: Could not connect to 'Serial: /dev/ttyUSB0'. Failed to open port, timeout waiting for response from port.

    Any help would be appreciated.

    Rkshack

    #2
    Is there anything else plugged into your USB port. Seems like whatever it is it’s grabbed usb0. In the configuration section of your plugin change the port to usb1. You could of course disable that plugin and re enable it again.

    Comment


      #3
      Originally posted by concordseer View Post
      Is there anything else plugged into your USB port. Seems like whatever it is it’s grabbed usb0. In the configuration section of your plugin change the port to usb1. You could of course disable that plugin and re-enable it again.
      I have 2 USB devices plugged into the raspberry pi. The z-stick which is on port /dev/ttyACM0. The insteon 2413u is on port /dev/ttyUSB0 .

      I have disabled the zwave plug-in and removed the zwave USB controller from the raspberry pi. I moved the insteon USB cable to another port and it still does not work. The homeseer log says: ERROR Cannot connect to port: /dev/ttyUSB0 .

      Any suggestions?

      rkshack

      Comment


        #4
        With both the ZWave stick and the Insteon connected to the RPI If you SSH into the RPI using something like PuTTY what results does the following command give

        lsusb


        Comment


          #5
          Have you tried an LSUSB command in the root to list all the connected USB devices and their assigned ports?

          Comment


            #6
            Here is what my lsusb command shows:


            Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
            Bus 001 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
            Bus 001 Device 004: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
            Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
            Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

            rkshack

            Comment


              #7
              If your ZWave stick is on /usb4 have you tried /usb5 for the Insteon controller. /dev and /usb are interchangable as one is a device pointer while the /usb is a hard pointer to the port.

              Comment


                #8
                The Zwave is on /dev/ttyACM0
                The options under HSInsteon on the plug in is /dev/ttyUSB0, /dev/ttyS0 and /dev/ttyACM0.

                rkshack

                Comment


                  #9
                  Ok, I don't run it under Linux so that's what I know about finding stuff in Linux. Not sure where it's getting the dropdowns you are seeing.

                  Comment


                    #10
                    Ok with your ZWave stick and Insteon connected to the RPI, stop HS. You can shut it down from the Web UI and stop it in your PuTTY session using the following command

                    sudo systemctl stop homeseer.service

                    Once HS is shutdown remove both the ZWave stick and the Insteon controller from the RPI. Immediately plug them back in and after doing this enter the following command in your PuTY session before doing anything else.

                    dmesg

                    Copy/paste the last 20 lines from the output here. It will give me an idea how your system is handling those devices.

                    Once you’ve completed the above reboot your RPI to restart your system.


                    Comment


                      #11
                      Here is what I got:

                      [155457.713193] usb 1-1.1: USB disconnect, device number 3
                      [155458.737282] usb 1-1.4: USB disconnect, device number 4
                      [155458.737963] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnec ted from ttyUSB0
                      [155458.738065] ftdi_sio 1-1.4:1.0: device disconnected
                      [155463.811074] usb 1-1.4: new full-speed USB device number 5 using xhci_hcd
                      [155463.957291] usb 1-1.4: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
                      [155463.957306] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumbe r=3
                      [155463.957319] usb 1-1.4: Product: FT232R USB UART
                      [155463.957332] usb 1-1.4: Manufacturer: FTDI
                      [155463.957343] usb 1-1.4: SerialNumber: A603338Y
                      [155463.964005] ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
                      [155463.964168] usb 1-1.4: Detected FT232RL
                      [155463.967254] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyU SB0
                      [155467.851104] usb 1-1.1: new full-speed USB device number 6 using xhci_hcd
                      [155467.991902] usb 1-1.1: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
                      [155467.991918] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumbe r=1
                      [155467.991931] usb 1-1.1: SerialNumber: 01FFFFFF-FFFF-FFFF-FFFF-020615104337
                      [155467.996797] cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device

                      rkshack

                      Comment


                        #12
                        What Raspberry Pi model are you using.

                        Comment


                          #13
                          I can’t spend much time replying here. On the little information you have supplied on your setup and the fact that the Insteon controller appeared to be failing the first thing I would do is replace the serial to usb cable. This would help to eliminate a bad serial to usb cable.

                          It really would help if you supplied more info on your setup.

                          Comment


                            #14
                            Here is my raspberry pi info:


                            Date/time=1/29/2022 5:31:42 PM EST
                            Version=HomeSeer HS4 Pi (F) Edition 4.2.0.0 (Linux)
                            MONO Version=Mono JIT compiler version 6.8.0.123 (tarball Tue May 12 15:31:43 UTC 2020)

                            License=Registered
                            License ID=
                            MyHS Subscription=Basic
                            MyHS Subscription Backup Interval=No Backup
                            MyHS Subscription Max Cameras=1
                            Confguration File=/usr/local/HomeSeer/Data/HomeSeerData.json
                            Uptime=10 Days 3 Hours 7 Minutes 46 Seconds
                            User/Access=Rkshack@gmail.com (Admin)
                            Lan IP=192.168.10.52 (HS4PiV3)
                            Client IP=192.168.10.2 (192.168.10.2)
                            WAN IP=24.99.116.83 ()
                            Device Count=60
                            Event Count=21
                            Last Event Ran=Garage : Close leaf door after 10 minutes, Ran at 1/29/2022 4:25:18 PM
                            # of unique event scripts=0
                            Plugins Enabled=HSInsteon:,Z-Wave:
                            Modules/Threads=77 Modules, 44 Threads
                            Available Threads=399
                            HomeSeer Memory Used=98 Mbytes
                            Plugins Installed=Harmony Hub 4.0.13.0,HSInsteon 1.0.0.9,Philips Hue 4.0.17.0,Z-Wave 3.0.2.0
                            Disk Size=29.81GB

                            Comment


                              #15
                              Did you see my previous post. Did you try changing out the cable.

                              Comment

                              Working...
                              X