I purchased a USB to Serial OIKWAN cable and connected it to my HA and my 2413S. Does not seem to want to complete setup in HA.
Any thoughts?
Is it loading drivers? What does the system log say? Have you configured it?
Do you have any yaml code to share [properly formatted for the forums in </> format]?
Is it loading drivers? Using HA green not PC.
What does the system log say? It keeps searching for devices
Do you have any yaml code to share [properly formatted for the forums in </> format]? Where can i find the file you are referencing?
Thank you in advance. New to HA, but i do have a techinca background.
Could it be your cable?
When I moved from ISY994i to HA and moved my 2413S PLM I made my own cable from a USB-to-Serial adapter and half an ethernet cable: Pin 3: TTL Output (TX from PLM) to RX of adapter, Pin 6: TTL Input (RX from PLM) to TX of adapter, Pin 7: Common Ground to GND of adapter.
I had no problems.
(plus I now had another invaluable USB to TTL serial to which I can connect things like ESP-12F 
)
ok i will give your solution a try. cheaper than replacing all my devices.
Linux has device drivers too. Yes, a lot, like Windoze also does, are built in, but not all. Maybe yours is one where it doesn’t.
The Insteon website mentions “third-party drivers” need to be loaded. Have you done this?
I understand that Linux has drivers. I am accessing HA Green via web UI. I do not have it connected to keyboard, mouse, monitor.
Not sure sure how i would add drivers using the web UI. I have added devices and integration for all my other devices using Wifi, zwave. Trying to add insteon plm.
Thinking this is more of a hardware issue with the cable interface, oldsurferdude is referencing.
Maybe the USB to Serial OIKWAN cable is drawing too much power from your USB port from the green and you may have to consider an external powered USB hub?
Is it doing RX to TX and TX to RX? Serial RS232 with negative 12volts, or just a simple positive 5 volts swing that proper RS232 device choke on?
If you have a serial port, you may need to configure speed, parity etc on the device before it can talk to your other devices. Have you done that?
Welcome to Linux internals, and headless operations. SSH and Samba may be entering your life!
My understanding is that USB/Serial Adapters that are based on the FTDI chipset (ftdi_sio) have drivers built into the HA Green. Shopping for one of those might be simpler than trying command line and configuration surgery
Even FTDI based serial devices need to have baud rate etc set before they will connect.
Maybe the setup documentation is missing something? A system restart at some critical stage to recognise a newly connected device maybe?
1 Like
My thoughts exactly. That is why I recommended a configuration that works.
The HA Insteon Integration sets the parameters to match the PLM. This is just one of many parts of the integration that has been done for us.
Once the cable issue is resolved, the Insteon devices are automatically integrated into HA. Some of the more esoteric Insteon devices may have some challenges.
@IOT7712 I am not sure why you brought up things not germane to the discussion. It also appears that you have to been through this process before. Your input is appreciated, but when you don’t have that experience, research your ideas and bring back the links that helped you formulate your advice.
1 Like
one of the first things i did was restart HA once the connection was made.
ok, HA is picking up the FTDI chip serial cable, as shown in the picture, but will not detect the PLM connected to it when i run integration.
Does it still work with the vendor software?
Maybe double check this.
Easy on the shade. I am not a bot. I am not using AI. You are experiencing a generic solution approach to a common interfacing problem, one I have solved many times with decades of experience, and it appears you have too, at least once. Do you want me to regale you with the tales of my first time I swapped the wires and it magically worked, over half a century ago?
Yes, cheap Chinese RS232 adapters commonly only swing TTL voltages. Yes, the documentation is often incorrectly translated. Yes it is easy to swap connections on the back of plugs if you are making a custom cable by hand. Yes, some interfaces need the CTS/RTS connections as well to correctly handshake. Yes, home grown integrations sometime don’t initialise parameters, such as stop bits and parity, relying on vendor software that is often used beforehand to magically make things good, or making assumptions about the environment they are running under.
Yes, linux can recognised different devices as different types and load default parameters that may need changing before use.
Yes, adding extra devices to a Green’s USB port can make things unstable.
Enough rationale for you why the questions are asked?
Did I pass your steep Turing Test?
Back to our regular channel: It would appear that a step by step approach to problem elimination might be the most reliable path to solving the issue. Once the devices are communicating, then take the next step with troubleshooting.
Has Zooz grabbed the tty serial port definition that your integration is expecting?
Maybe @OldSurferDude could check if the Linux discovered (FTDI style) USB port and his Insteon integration tty serial port details match what he has on his system, or do we have to delve into the integration source code to look there?
zooz for my zwave adapter working perfectly.
FTDI is the chipset that is used in ttl to usb adapters.
Decided to dump the Insteon PLM Serial adapter and opt to replacing my Insteon Switches with Zwave which has no issues.
Thank you for everyone’s help!
Yes, both recognised as dev/serial style devices by Linux.
Two issues: first is hardware - are they communicating at the signal level?
Second: are the devices recognised by linux and the device expected by the Insteon integration matching?
You may have discovered a software bug, and a hardware replacement approach may be an unnecessary expense.
Go back and check the PLM screen (truncated on your last screen shot) - does it show your OIKWAN USB FTDI device as a choice?
Yes it does.
First image without cable. Second image with cable connected. Note, the Insteon PLM makes no difference if connected to cable or not. Below is the Hardware Info.
Subsystem:
tty
Device path:
/dev/ttyUSB0
ID:
/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9BID1I2-if00-port0
Attributes:
DEVLINKS: >-
/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9BID1I2-if00-port0
/dev/serial/by-path/platform-fd8c0000.usb-usb-0:1:1.0-port0
/dev/serial/by-path/platform-fd8c0000.usb-usbv1-0:1:1.0-port0
DEVNAME: /dev/ttyUSB0
DEVPATH: /devices/platform/fd8c0000.usb/usb7/7-1/7-1:1.0/ttyUSB0/tty/ttyUSB0
ID_BUS: usb
ID_MODEL: FT232R_USB_UART
ID_MODEL_ENC: FT232R\x20USB\x20UART
ID_MODEL_ID: '6001'
ID_PATH: platform-fd8c0000.usb-usb-0:1:1.0
ID_PATH_TAG: platform-fd8c0000_usb-usb-0_1_1_0
ID_PATH_WITH_USB_REVISION: platform-fd8c0000.usb-usbv1-0:1:1.0
ID_REVISION: '0600'
ID_SERIAL: FTDI_FT232R_USB_UART_A9BID1I2
ID_SERIAL_SHORT: A9BID1I2
ID_TYPE: generic
ID_USB_DRIVER: ftdi_sio
ID_USB_INTERFACES: ':ffffff:'
ID_USB_INTERFACE_NUM: '00'
ID_USB_MODEL: FT232R_USB_UART
ID_USB_MODEL_ENC: FT232R\x20USB\x20UART
ID_USB_MODEL_ID: '6001'
ID_USB_REVISION: '0600'
ID_USB_SERIAL: FTDI_FT232R_USB_UART_A9BID1I2
ID_USB_SERIAL_SHORT: A9BID1I2
ID_USB_TYPE: generic
ID_USB_VENDOR: FTDI
ID_USB_VENDOR_ENC: FTDI
ID_USB_VENDOR_ID: '0403'
ID_VENDOR: FTDI
ID_VENDOR_ENC: FTDI
ID_VENDOR_ID: '0403'
MAJOR: '188'
MINOR: '0'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '4237416513'
I share your frustrations @byteman59
I went to my system to get a screen shot of how my PLM is connected:
I’m running HA in linux on a virtual box.
@IOT7712 makes two suggestions which I had assumed you already did: check the wiring; check to see if the PLM is still working in the original installation.
I would suspect a wiring issue and go to great lengths to confirm. I would build another cable that is the female version. An RJ45 female connector connected to the other USB/serial adapter. Plug both adapters into my windows or linux computer, run two instances of PuTTY at the same BAUD rate. If the cable is good, then typing in one instance of PuTTY will result in the output appearing in the other. (I offer this advice because, just yesterday, I built up a long ethernet cable only to find that I had miswired it. grrrr)
But, if the cable is good, I hear ya, go to something that works for you.