Hi All. Still pretty green to HA. Have a hardware question.
Using a rPi 4 4GB using the HassIO official
Bought a StarTech.com USB to RS232 4 port hub (ICUSB2324I).
Home Assistant 2021.8.6
Pop this hub in and HassIO picks it up right away.
Here’s how they list in the Hardware view …/hassio/system - Hardware
Looks pretty straight forward - use tty/USB2 to access Serial port 3 on the device
ttyUSB0/dev/serial/by-id/usb-FTDI_USB__-__Serial_Cable_FT5QQC0I-if00-port0
ttyUSB1/dev/serial/by-id/usb-FTDI_USB__-__Serial_Cable_FT5QQC0I-if01-port0
ttyUSB2/dev/serial/by-id/usb-FTDI_USB__-__Serial_Cable_FT5QQC0I-if02-port0
ttyUSB3/dev/serial/by-id/usb-FTDI_USB__-__Serial_Cable_FT5QQC0I-if03-port0
Details of the ttyUSB0 (I can provide the rest, but it looks redundant):
Subsystem: tty
Device path: /dev/ttyUSB0
ID: /dev/serial/by-id/usb-FTDI_USB__-__Serial_Cable_FT5QQC0I-if00-port0
Attributes:
DEVLINKS: >-
/dev/serial/by-id/usb-FTDI_USB__-__Serial_Cable_FT5QQC0I-if00-port0
/dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.2:1.0-port0
DEVNAME: /dev/ttyUSB0
DEVPATH: >-
/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0
ID_BUS: usb
ID_MODEL: USB__-__Serial_Cable
ID_MODEL_ENC: USB\x20\x3c-\x3e\x20Serial\x20Cable
ID_MODEL_ID: '6011'
ID_PATH: platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.2:1.0
ID_PATH_TAG: platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_2_1_0
ID_REVISION: '0800'
ID_SERIAL: FTDI_USB__-__Serial_Cable_FT5QQC0I
ID_SERIAL_SHORT: FT5QQC0I
ID_TYPE: generic
ID_USB_DRIVER: ftdi_sio
ID_USB_INTERFACES: ':ffffff:'
ID_USB_INTERFACE_NUM: '00'
ID_VENDOR: FTDI
ID_VENDOR_ENC: FTDI
ID_VENDOR_ID: '0403'
MAJOR: '188'
MINOR: '0'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '3328715986'
So, all looks good so far
When I try to add the Insteon PLM integration (to test this out) there seems to be a mapping issue
My guess is there is a confusion on how to map, likely need to make some changes here
Only thing I can seem to find is the Windows Driver and no mentions of the implementation in a Linux based system
Here’s what happens (LED indicators for Rx/Tx):
If I reference ttyUSB0 → Port 1 Tx fires
If I reference ttyUSB1 → Port 1 & 2 Tx fire
If I reference ttyUSB2 → Port 1, 2 & 3 Tx fire
If I reference ttyUSB3 → Port 1, 2, 3 & 4 Tx fire
For example, I have the config setup to use ttyUSB2 and the Insteon PLM is connected to port 1, works and communication is good.
I did find some non-device document that was discussing FTDI and that the mapping not directly usable in the Linux world. Was not able to get this working. Wasn’t recognizing the
dmesg | grep FTDI
This runs and I get a list of ports
Then
rmmod ftdi_sio
rmmod: can’t unload module ‘ttdi_soi’: Operation not permitted
rmmod usbserial
rmmod: can’t unload module ‘usbserial’: Operation not permitted
Document also mentions that this will need to be done anytime the module is unplugged and plugged back in (suggests scripting to auto run). This does not strike me a very stable or reliable solution
Just wondering if anyone has a solution here or perhaps I should return this and get something else?
Thanks in advance!