ndeadly

There you go. Let me know if you find anything interesting. I haven't made a handler for DS3 yet, so don't expect it to connect with the console just yet....

Also, I think the DS3 uses Bluetooth legacy pairing like the Wii controllers. From memory it uses the default 0000 pincode but you might want to check that. If it's...

Where are you trying this? MissionControl will only send 0000 (Wii controllers excepted) for now FYI.

It's possible, but there's no point. Nothing interesting will happen if you fake it, as the database stores the link key which is negotiated between the controller and the host...

I tried sixpair.c earlier today myself. No luck with getting it connected, it didn't even show up in device discovery logs. This gives me a bad feeling the bluetooth driver...

@KAMELCOLTD the controller still needs to complete the pairing process with the console via Bluetooth to exchange link keys. The problem is that the DS3 is currently not even showing...

I don't think the mac address is the problem. I set it successfully using a modified sixpair.c where I manually inserted my console mac. I think the issue is that...

The Switch stores the controller address alongside other info to the database after successfully pairing with it. As I said earlier in this thread, manually inserting the controller mac address...

@KAMELCOLTD this one whitelists the dualshock3, so it should show up as connected if you were to somehow find a way to make it work. [MissionControl-0.2.1-ds3-experimental.zip](https://github.com/ndeadly/MissionControl/files/5250305/MissionControl-0.2.1-ds3-experimental.zip)

@brenodantas10 this version is not intended to "work", it simply provides a handler that recognises the ds3 hardware ID so the controller would show up as connected to the switch...