Unable to connect insteon PLM to raspberry pi 4

Third party integrations
1

I am in the process of evaluating HA as a replacement for my existing indigo setup. I have a large number of insteon devices and want to see what the HA experience would be like with them.

Today I moved my PLM from my Mac running indigo to the RPI (Home Assistant OS) with the intent of importing the linked database. When I plug the PLM into the USB port it see in the “host” logs:

[  127.047706] usb 1-1.4: new full-speed USB device number 3 using xhci_hcd
[  127.193961] usb 1-1.4: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[  127.193981] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  127.193999] usb 1-1.4: Product: FT232R USB UART
[  127.194015] usb 1-1.4: Manufacturer: FTDI
[  127.194032] usb 1-1.4: SerialNumber: A60333M5
[  127.231728] usbcore: registered new interface driver ftdi_sio
[  127.231797] usbserial: USB Serial support registered for FTDI USB Serial Device
[  127.231926] ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
[  127.232055] usb 1-1.4: Detected FT232RL
[  127.239028] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0

I then attempt to install the insteon integration, select PLM and then /dev/ttyUSB0 as the port and get a “Failed to connect” error. I have power cycled both the PLM and the pi just for the fun of it with no change in messages or success.

I have this log error as well:

Logger: pyinsteon.protocol.serial_transport
Source: /usr/local/lib/python3.8/site-packages/pyinsteon/protocol/serial_transport.py:24 
First occurred: 2:32:47 PM (2 occurrences) 
Last logged: 2:34:37 PM

Unable to connect to /dev/ttyUSB0: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0'

When I connected to the host via SSH and ran ha hardware info, /dev/ttyUSB0 is listed under the serial key as well.

I must be missing something simple, can someone point me the right way?

2

Not familiar with Home Assistant OS, but I do know that it is based on Docker containers. Processes in containers do not have access to the host‘s devices unless explicitely „granted“.

Normally, you would need to start the container with the parameter —device="/dev/ttyUSB0:/dev/ttyUSB0“, but again: I don‘t know the proper way to realize this when using Home Assistant OS.

1 Like
3

Shutting down the pi, plugging in the PLM, and then turning it back on seems to have made it work. I think the rule with HA is - if you change something try restarting the supervisor. If that doesn’t work, restart the computer.