[Bug Report]: Xbox Elite 2 Not Reconnecting about missioncontrol HOT 4 CLOSED

Being paired to multiple devices isn't really a thing. The controller only stores pairing info for the latest device it was connected to. That said, I seem to recall hearing about Xbox One/Elite controllers sometimes having issues when switching between devices and something needing to be done to "flush" out the old pairing data properly. Unfortunately I can't remember the specifics, or where I read that. Maybe it was something that @kakra told me?

In any case, I think this is a controller problem and not a Mission Control issue. Besides tricking the console into thinking it's dealing with a Pro Controller, Mission Control leaves the pairing up to Nintendo. All the pairing data is stored in exactly the same manner, so if there were a problem with that you could expect it to affect other controllers as well.

One potential alternative to your firmware update trick could me taking advantage of Mission Control's host name/address spoofing feature (see here) to spoof your console to look like your PC and inject the pairing data from one device to the other. This way you wouldn't have to re-pair when switching devices. The downside is that you may have issues with the two competing with one another if both devices are active and within range of one another.

One other thing you could try is clearing the bluetooth pairing database on the console if you haven't already. Sometimes that can fix strange issues like this.

from missioncontrol.

Xbox Elite 2 controllers have a quick connect feature so to call it. It will store 2 devices and will swap between by double clicking the sync button. My controller works seamlessly between my xbox/pc but it doesn't reconnect to the switch using this feature.

from missioncontrol.

@toomuchsweat Does this feature exist on the legacy firmware that works with the Switch? As far as I was aware, the quick connect thing came with the new Bluetooth LE firmware to all Xbox controllers. Though I am not so familiar with the Elite 2, so it may have existed on there prior.

from missioncontrol.

Maybe it was something that @kakra told me?

Yes but that is something I've not seen reported in a long time. I'm pretty sure this was fixed with later 5.x firmware versions but unfortunately, those versions cannot be supported by MC currently.

from missioncontrol.