Once paired with My Ps4 Controller Could not pair anything else. about missioncontrol HOT 12 CLOSED

Could you provide further info? Are your controllers official or 3rd party? DS4 v1 or v2? Any other homebrew sysmodules running?

from missioncontrol.

Yeah all the controllers are official the ps4 controller is Model: CUH-ZCT2U so its a DS4. No other homebrew was runnng at the moment. I just recently upgraded to 10.1 so I cleared my atmosphere for the upgrade. it only has the SD Req files for atmosphere the signature pack with fusee-primary.bin. the last thing put in my sd card was the Mission control. before booting my switch. Works perfectly, but then tried to use my original pro switch controller and would not sync, re paired it with the cable and still would not sync. try to reboot the switch and still had the same issue. so I attempted to sync wii u pro controller and would not sync with any other controller. however I could use the joycons attached to it, even removed them from the switch and still be able to use them. I think this is all the info I can Remember XD

from missioncontrol.

Sounds like your setup is good. Firstly, there's an issue with pairing switch controllers via means other than Bluetooth (I just added an FAQ entry about it in the readme). If you do it via the Joycon rails or cable, a garbage hardware ID gets stored to the console and they don't get identified properly by MissionControl. The workaround for now is to use the Disconnect Controllers option in System Settings to clear the database (make sure the controller isn't physically connected to the console in any way) and then re-pair over Bluetooth via the Change Grip/Order screen. Clearing the database may even solve your problem with controllers refusing to sync. You could also try resetting the ps4 controller and see if that helps.

from missioncontrol.

Same exact issue as OP. After pairing DS4 controller(V2), can't use my Pro controller any more. Haven't tried the database clear, just wanted to let you know. Plugging it in to repair it doesn't do anything. However when I go to change grips and press the sync button on the pro controller, it says paired but doesn't actually work. Joycons when attached works no issue. Haven't tried with them unpaired or trying my other joycons.

from missioncontrol.

Try this build with logging enabled. I suggest you do the database wipe first in order to start with a clean slate. Try and replicate the problem and then post the resulting log here. It's named btdrv-mitm.log and will appear on the root of your SD card. Note, that if you reboot the console the log will be wiped on startup.

MissionControl-0.1.0-debug-logging.zip

from missioncontrol.

So after figuring out the logging part, which I just had to restart the console to show the changes, I performed the database wipe and then attempted to pair the Pro controller first, which worked. Then changed grip again, paired the DS4 controller, which worked. And then attempted to repair the Pro controller and then it worked just fine with both the DS4 and Pro controller. Don't know if you changed anything or just clearing database fixed the issue. Here's my log however see if it all looks good.[btdrv-mitm.log](https://github.com/ndeadly/MissionControl/files/5145980/btdrv-mitm.log)

from missioncontrol.

@notShep log looks good. I suspect maybe you had the garbage hardware ID issue with the Pro Controller. I don't know whether connecting via USB can trigger it to overwrite the good hardware ID, but let me know if the issue returns. Hopefully I can improve my controller detection and make it a non-issue in the future

from missioncontrol.

I made this build for another issue that fixes some errors in the DS4 battery level handling code. Give it a try and see if it makes any difference to your situation

MissionControl-0.1.0-ds4-battery-fix.zip

from missioncontrol.

Will do, also I did notice with the debug version, I had hefty lag input. I think I saw someone else start a thread but I'm going to flash this one and mess around. Appreciate the help and the mod!

Edit: Does this still have the logging?

from missioncontrol.

Yeah, lag is to be expected with the logging version. Constantly opening a file and writing to SD is relatively slow. This is why the release version doesn't have any logging at all. You should only use that version for debugging issues.

This new build is based upon the release build and doesn't have the logging in place. Just wanted you to try it to rule out the battery issue. If it doesn't fix it then you should make some logs with the other version.

from missioncontrol.

The latest 0.2.0 release fixes the DS4 battery bug. @DarkLouie can you confirm whether your issue is resolved?

from missioncontrol.

I'm going to assume this issue has since been fixed in the latest releases since nobody else has reported issues. Please re-open if you're still having issues.

from missioncontrol.