8bitdo v2 adapter unable to connect

Submitted by CaptSk1ttles on #1

Hello,

 

I'm having an issue with virtualhere server version 4.5.8 running on a raspberry pi3 with the armpi3build and a windows 11 device running 5.4.9 as a client. The issue appears to be with the 8bitdo v2 usb adapter. Whenever I try to connect a controller to it'll go into a loop because its constantly connecting/disconnecting as different devices likely for the nintendo switch compatibility. The device works fine in my PC directly. I've tried turning on ClaimPorts to no avail. Any tips on how I might be able to resolve this issue. The server log showing the disconnect is below there is only 1 device attached to the hub.

 

May 03 20:08:00 pi vhusbdarmpi3[472]: Found Full speed device [2dc8:3106] "8BitDo, 8BitDo Receiver" at address 1112
May 03 20:08:00 pi vhusbdarmpi3[472]: Unmanaging device 1112 [2dc8:3106]
May 03 20:08:01 pi vhusbdarmpi3[472]: Found Full speed device [045e:028e] "8BitDo, Controller" at address 1112
May 03 20:08:01 pi vhusbdarmpi3[472]: Unmanaging device 1112 [045e:028e]
May 03 20:08:02 pi vhusbdarmpi3[472]: Found Full speed device [2dc8:3106] "8BitDo, 8BitDo Receiver" at address 1112
May 03 20:08:02 pi vhusbdarmpi3[472]: Unmanaging device 1112 [2dc8:3106]
May 03 20:08:03 pi vhusbdarmpi3[472]: Found Full speed device [057e:2009] "Nintendo Co., Ltd., Pro Controller" at address 1112
May 03 20:08:03 pi vhusbdarmpi3[472]: Unmanaging device 1112 [057e:2009]
May 03 20:08:05 pi vhusbdarmpi3[472]: Found Full speed device [045e:028e] "8BitDo, Controller" at address 1112
May 03 20:08:05 pi vhusbdarmpi3[472]: Unmanaging device 1112 [045e:028e]

Submitted by Michael on Thu, 2023/05/04 - 12:09

#2

Im not sure, its almost like its switching modes and then listening for a bit to see if it can hear the controller.

What about if you have "Auto-Use Port" on in the virtualhere client for the 8bit-do device. Does that help?

 

Submitted by CaptSk1ttles on Fri, 2023/05/05 - 22:34

#3

Michael,

I originally had an older version installed and it completely locked up because of Auto-Use port upgrading gave me an error about it. I ended up giving up on it. I just assume it's going to be unsupported due to the nature of the device. It also behaved the same way with the windows server so it's likely just because it works as both a Nintendo Pro Controller and a Wired controller connected to the PC. I'm getting a new Microsoft adapter for my controller in the mail today and based on my experience that should work without any issue. So I think we can safely call this issue "resolved"