-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Joycontrol unable to connect with Switch update 12.0.0 #6
Comments
Thanks for your notice! |
It looks like the original library hasn't been updated in a long time. |
I've tested the new fix, but encountered with some bluetooth issues. |
This is the first time I use this program. With the current problem, is it normal to see the following result with no pairing? Open the pairing menu on switch.
[Errno 98] Address already in use
Fallback: Restarting bluetooth due to incompatibilities with the bluez "input" plugin. Disable the plugin to avoid issues. See https://github.com/mart1nro/joycontrol/issues/8
_ I guess the error mentioned above is caused because I'm using a bluetooth keyboard. But I think it can fix itself by restarting bluetooth, am I right? |
The That's not the problem here mentioned, and even if you passed your issue, the version 12 problem could not be solved currently. Switch needs to recognize the emulated controller (by the address) before updated to version 12+ to continue using it. |
Someone solved the problem. I tested it on Pi 3B and worked perfectly. Maybe you can use this version to solve the problem. |
the repo formatcom/joytransfer mentioned in Poohl/joycontrol/issues/11 maybe worked |
I tried to replace the files of the joycontrol folder with the ones from formatcom/joytransfer but it didn't work as it asks for a joycontrol.debug module. What am I doing wrong, which are the steps to get splatplost working? |
It had been post here and someone give a solution. But I have no time to test whether it can work(just test once and not work), and if it can instead the joycontrol directory in this repositories.
The text was updated successfully, but these errors were encountered: