ndeadly

Everything is working normally on the latest controller firmware so I'm not sure what's up there. Can you show me the patterns your controller is showing? Might just be easier...

This info isn't all that useful without knowing which firmware version your controller has. Run this build, connect the controller and post the log it creates (`sdmc:/mc-mitm.log`) [MissionControl-0.9.0-debug-logging-1a589da.zip](https://github.com/ndeadly/MissionControl/files/11250959/MissionControl-0.9.0-debug-logging-1a589da.zip)

I may have misremembered regarding what you can and can't do with a licensed controller, but the point remains the same - that we likely lose features by telling the...

The issue is pretty much understood, needs nfc communication to be emulated correctly. That's still not done.

Hmm, interesting. Mission Control _should_ just pass through traffic from official controllers. I will investigate. Not sure if I've updated my Pro Controller recently or not.

Seems all my controllers are up to date. Do you remember what happened on failure? Was there an error message displayed? If so there might be some logs in `/atmosphere/erpt_reports`

> it might be that emuiibo (1.0) was still on my system so that could be a culprit as well It's possible. I'll ask around on my discord server if...

Confirmed that this seems to be an issue for Pro Controllers at least (Joycons can be updated in handheld mode bypassing Bluetooth). Will investigate a fix with the help of...

I make no guarantees for 3rd party clone controllers. Sometimes they can behave unexpectedly. That said, the only scenarios I've seen to date with them is either they just work,...

It seems like it's trying to connect but something is failing during the secure pairing procedure. This sometimes happens with official controllers and can be resolved by resetting the controller...