Skip to content
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

Pro Controller Issue #27

Closed
werd10101 opened this issue Aug 29, 2020 · 14 comments
Closed

Pro Controller Issue #27

werd10101 opened this issue Aug 29, 2020 · 14 comments
Labels
bug Something isn't working

Comments

@werd10101
Copy link

After getting the Wii U Pro controller working my Switch Pro controller won't pair wirelessly. It does the small vibrate to indicate pairing and the switch pairing notification pops up but nothing happens after that

@ekayey
Copy link

ekayey commented Aug 29, 2020

Go into System Settings > Controllers and Sensors and select Disconnect Controllers. After you disconnect all controllers from the console, go back into Change Grip Order and try pairing the Pro Controller to the system.

@ndeadly
Copy link
Owner

ndeadly commented Aug 29, 2020

The fact that you get the pairing notification suggests that the controller is being identified correctly, but the connection process isn't completing, so I doubt the fix suggested by @ekayey will help in this case.

I've had another user report a similar issue. I think it has to do with the firmware version on your Pro Controller being older and causing the Switch to make some different requests that I don't handle, so the connection process never completes. If you don't mind holding out, I'd like to create a build with logging enabled later today to try and get to the bottom of the issue. Otherwise, updating your controller firmware will probably fix it.

@ndeadly ndeadly added the bug Something isn't working label Aug 29, 2020
@werd10101
Copy link
Author

I can wait to fix it

@ndeadly
Copy link
Owner

ndeadly commented Aug 29, 2020

Here's a build with logging enabled. It will create a log file on the root of your sd card btdrv-mitm.log. The logging will impact system performance, so you probably don't want to leave this build in place if you're actually playing games.
Note that if you reboot the system, the log will be wiped upon startup.

I suggest that you follow the instructions of @ekayey to wipe your controller database just to start with a clean slate. Do your thing to replicate the issue, then post the logfile here for me to take a look at.

MissionControl-0.1.0-debug-logging.zip

@werd10101
Copy link
Author

You were right that disconnecting all controllers wouldn't work
btdrv-mitm.log

@werd10101
Copy link
Author

Also there's no update for my controller. It pairs fine on a different switch and also says there's no update

@ndeadly
Copy link
Owner

ndeadly commented Aug 29, 2020

So first thing that I notice is your Pro Controller has an unrecognised hardware ID. This can mean one of two things. Either you have a third party clone, or you paired via USB and got assigned a garbage ID. If it's a legit controller, you need to make sure it's not connected to the console in any way when you wipe the database, and then pair it over bluetooth. If it's a 3rd party controller, it likely has a random ID that I can't whitelist. This is a known issue that I'm trying to come up with a solution for.

Looks like you also paired a Wii U Pro Controller? Did that work? Looks as though it got through the process.

Anyway, seems like it's getting hung up trying to set a set home light command to one of the controllers. I don't currently handle this so this is likely your main issue. I'll try and add a fix for it before I have to go out today.
I've never seen this command sent on my Switch, any idea where it might be coming from? I didn't think it was actually used by stock HOS

@Lust33
Copy link

Lust33 commented Aug 29, 2020

Same problem, work perfect with my xbox and ps4 controller but impossible synchro my controller pro. No problem when i play with xbox or ps4 controller. Congratulation and good luck for the future

@ndeadly
Copy link
Owner

ndeadly commented Aug 29, 2020

@Lust33 read the above discussion. You might not have exactly the same problem as the OP. You probably either have a 3rd party clone controller, or it's been paired via USB. Run the above debug logging build and post your log

@werd10101
Copy link
Author

It was because it was plugged in when clearing. Thank you. The Wii U Pro Controller also works perfectly

@Lust33
Copy link

Lust33 commented Aug 29, 2020

@ndeadly I have disconnect Controllers, and paired without usb, and it work, thx
How run "debug logging build"?

@ndeadly
Copy link
Owner

ndeadly commented Aug 29, 2020

@Lust33 it sounds like you just had the garbage hardware ID issue then. Eventually I might be able to work around it in the future and you won't need to worry about how you paired.

I posted the build above #27 (comment)
You can install it just like the release. Though it sounds like you don't really need it if your controller is now working

@Lust33
Copy link

Lust33 commented Aug 29, 2020

Ok thx. I keep trying, again well done for your work

@ndeadly
Copy link
Owner

ndeadly commented Aug 29, 2020

Sounds like everything is working for both of you now. Closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants