Connecting Insteon PLM, 2413U to an RPi 5

I’m moving my HA instance from a Docker to an RPi 5. I tried restoring my HA backup to my RPi 5, but that failed. So im doing a fresh install on my RPi 5. HA installed OK and I’ve added a few devices that it found.

However, when i plugged my USB PLM into my RPi 5 i get, usb 3 - port 2: unable unable to enumerate USB device. Different USB ports produce the same result. When i try to add the Insteon integration, i get the PLM listed as /dev/ttyAMA10, s/n, n/a. This does not seem correct, am i missing a driver?

The 2413 USB driver would be ftdi, and would attach it as a /dev/ttyUSBx.
From just googling around, the RPi should already come with a ftdi driver.
The other thing that may be causing your problem is using it with an external USB Hub.
If this is the case for you, may want to plug it straight into a USB port on the RPi just to confirm.

Thanks, it’s plugged directly into the RPi, so im not sure what the issue might be. I tried my spare PLM, but it still didn’t work. I unplugged my USB keyboard dongle and tried the PLM in all of the holes. It worked fine in my Docker, so I’m not sure what’s up.

My RPi has a touch screen attached, but i can’t see that being an issue. I’m going to try a different RPi and a new cable.

I also tried all the variations of resetting the RPi and PLM in every order. I also tried various device options, but since the RPi is not seeing the PLM, that is not going to help. I saw that the power supply can be an issue for the enumeration issue, but the PS is beefy and was part of the kit. I’ll try a different PS anyway.

I saw a deal on a refurbished i7 Chromebox, so I’m going to try that too.

The output of dmesg looks like this. Hopefully, someone can suggest the cause/fix.

This output is with a different Pi and power supply, so i assume it’s a configuration issue.

[3892.579888] usb usb3-port2: unable to enumerate USB device

[3892.851750] usb 3-2: new full-speed USB device number 83 using xhci-hcd

[3892.979815] usb 3-2: Device not responding to setup address.

[3893.187765] usb 3-2: Device not responding to setup address.

[3893.395733] usb 3-2: device not accepting address 83, error -71

[3893.731724] usb 3-2: new full-speed USB device number 84 using xhci-hcd

[3893.859788] usb 3-2: Device not responding to setup address.

[3894.067740] usb 3-2: Device not responding to setup address.

[3894.275707] usb 3-2: device not accepting address 84, error -71

[3894.275785] usb usb3-port2: attempt power cycle

Just as check, is the 2413U plugged into an AC outlet? If yes, then I don’t know what the problem is (other than Linux can’t talk to the device)

I’m thinking the Docker isn’t talking to Linux, but i don’t know. USB auto recognition is enabled based on the config file.

I was reading that i should monitor the Supervisor when i connect/disconnect the USB device to see if i can see it and what the USB address is.

The dmesg log is what the OS’s kernel sees which indicates there is a problem. If its not working in the OS kernel, then Docker/Supervisor won’t see it either.

I replaced the USB cable:

1000007112

The integration still won’t load though. I get the spinning circle of death. Time to play the restart game i guess.