Homebrew RELEASE MissionControl: Use controllers from other consoles natively via Bluetooth

[ndeadly]

https://0bin.net/paste/u9eO92ze#VHVwi8mnpMqCHOmf3GvZ5OlWQjMt4vwWxZyFltxtO90

for the hangs it not a big deal , i don't have emummc on the 2.
i will take a deep look at it ,time to eat

mega link : https://mega.nz/file/659ESYTK#sOzfKqDoLLHgfltqVXgb6x8RPYxHxg72SH8-c2YmTgI

Ok, mega link worked. I can see that the iCade is using regular bluetooth and appears to be using legacy pincode pairing. The switch is attempting to pair with it but is setting the the default pin of 0000. I'm not quite sure how legacy pairing is supposed to work when it comes to entering a code shown on screen. There doesn't seem to be any code sent in the events. Maybe the 0000 set by the switch is the code that would normally be shown. You could try entering that on the controller and see if it succeeds. Unfortunately you wouldn't get any prompts as to when it wants to code so you would just have to try a few times.

I'll work on updating my pairing application to work on latest firmwares so at least you can get some visual prompt about what's happening

 

[mitcha]

ok , when pairing to android/windows it promt you to enter a Random code from 0 to 9.
here is the mapping :


i will try my best for sure to get it working.
it's good i think that the switch is sending 0000 code by default , as for any other devices , the code like i said is every time not the same (random) and have 6 numbers not only 4.

i never test sending code to the switch , just smashing on buttons to evacuate frustration

i will try more test tomorow , cuz here it's time to sleep , ( i'll give it a try right now before going ).

finally, for your pairing application , it's a very good news that you make that , and if updated,. it will be a good app , cuz seeing what happen whould be the best option i will have.
thank you one more time.

don't forget to take some rest

--------------------- MERGED ---------------------------

look like we have a good news here :


the button are Red.

i just enter pairing mode on icade ( the 4 down buttons and the top right one pressed simultanusly ) , when the red led flash's , it's in pairing mode , then i enter 0000 and pressed multiple times the enter buttons ( the top right or the down right ).
it paired well , but nothing works , i'll go read your first post , i saw you talk about the red button's (lack of mapping i guess).

edit : well , now the icade need you to mapp the button's and the stick
on computer ,when i open a text file and move/push the stick/buttons ,it act like a keyboard , for example ;
up = az (azerty keyboard)

 

[ndeadly]

ok , when pairing to android/windows it promt you to enter a Random code from 0 to 9.
here is the mapping :


i will try my best for sure to get it working.
it's good i think that the switch is sending 0000 code by default , as for any other devices , the code like i said is every time not the same (random) and have 6 numbers not only 4.

i never test sending code to the switch , just smashing on buttons to evacuate frustration

i will try more test tomorow , cuz here it's time to sleep , ( i'll give it a try right now before going ).

finally, for your pairing application , it's a very good news that you make that , and if updated,. it will be a good app , cuz seeing what happen whould be the best option i will have.
thank you one more time.

don't forget to take some rest

--------------------- MERGED ---------------------------

look like we have a good new here :


the button are Red.

i just enter pairing mode on icade ( the 4 down buttons and the top right one pressed simultanusly ) , when the red led flash's , it's in pairing mode , then i enter 0000 and pressed multiple times the enter buttons ( the top right or the down right ).
it paired well , but nothing works , i'll go read your first post , i saw you talk about the red button's (lack of mapping i guess)

Looks like it paired with 0000, nice! Yeah red buttons means it's connected but there is no handler for it to map the buttons. If you use this tool to record the values the controller sends for each input and open a controller request on my github page I'll get to work creating the handler for it. Make sure you don't have any other wireless controllers connected when you do this as they will interfere. From what I read, this controller sends one value for a button press and another for a button release, so you'll probably have to record 2 sets of values for each button/stick direction.

 

[VashTS]

ive got this iCade as well would be neat if MC manages to get some use out of it.

 

[ndeadly]

ive got this iCade as well would be neat if MC manages to get some use out of it.

You're welcome to follow the instructions above too if you like. Doesn't matter to me who reports it

 

[mitcha]

Looks like it paired with 0000, nice! Yeah red buttons means it's connected but there is no handler for it to map the buttons. If you use this tool to record the values the controller sends for each input and open a controller request on my github page I'll get to work creating the handler for it. Make sure you don't have any other wireless controllers connected when you do this as they will interfere. From what I read, this controller sends one value for a button press and another for a button release, so you'll probably have to record 2 sets of values for each button/stick direction.

i will do it asap , if i understand well what you said , for example UP , i press it 2 times , same with buttons ?
and i disconect even the joycons ?

edit : done ( pressed each button/stick 2 times )
can i reconect now the joycons ? to exit.
and where the log will be ? in the root i guess or in the switch folder.

 

[ndeadly]

i will do it asap , if i understand well what you said , for example UP , i press it 2 times , same with buttons ?

You don't need to press it twice, but it sounds like there are 3 states - unpressed (no value sent), pressed, and released. So you would record one value for pushing the stick up, and another for letting it return to the center. This post explains it in further detail https://gaming.stackexchange.com/q/24774

I could probably figure out the values from that post, but I also need to see the report format anyway. There will be an initial value to indicate the report type, and the report will be a certain number of bytes long. There may also be other information sent along with the controls.

You don't need to rush though, as it's getting late here for me too. I won't be able to do it until the morning.

 

[mitcha]

edit : i read the behavior of the icade on your link , and i see Dr Fish post ,sound logic and great , is it possible to blind by a patch, one of the command of the icade to let it send 1(press) and not 2 (press and release) ?

 

[ndeadly]

edit : i read the behavior of the icade on your link , and i see Dr Fish post ,sound logic and great , is it possible to blind by a patch, one of the command of the icade to let it send 1(press) and not 2 (press and release) ?

We shouldn't need to worry about patching anything, as I have full control over how the inputs are handled. I just need to know the values it sends. These people complaining about the scheme being strange are trying to make it work with existing drivers that may not be as flexible

 

[mitcha]

We shouldn't need to worry about patching anything, as I have full control over how the inputs are handled. I just need to know the values it sends. These people complaining about the scheme being strange are trying to make it work with existing drivers that may not be as flexible

i'm too tired to get throu git capcha ,dice count at late night make me see double, and make me crazy.

edit : done , will pull a request soon.

 

[ndeadly]

i'm too tired to get throu git capcha ,dice count at late night make me see double, and make me crazy.

It's no problem, get some sleep. I should too, it's 04:30 here

 

[mitcha]

It's no problem, get some sleep. I should too, it's 04:30 here

here too , and the happy part is i work today

 

[VashTS]

We shouldn't need to worry about patching anything, as I have full control over how the inputs are handled. I just need to know the values it sends. These people complaining about the scheme being strange are trying to make it work with existing drivers that may not be as flexible

i got the same problem here - it sync'd up but when i use HID report viewer, it just shows

0000 | 01 00 00 00 00 00 00 00 00 00

pressing buttons while it shows this does nothing more. only the icade is connected wireless, joycons are on the switch.

 

[ndeadly]

i got the same problem here - it sync'd up but when i use HID report viewer, it just shows

0000 | 01 00 00 00 00 00 00 00 00 00

pressing buttons while it shows this does nothing more. only the icade is connected wireless, joycons are on the switch.

Hmm, ok it might be sending constant updates rather than just when the state changes, and the state changes are being quickly overwritten. Out of interest do you notice any change or flickering if you quickly mash some of the buttons?

I posted a build on mitcha's issue on github if you'd like to try it out https://github.com/ndeadly/MissionControl/issues/211#issuecomment-798907624

 

[mitcha]

Hmm, ok it might be sending constant updates rather than just when the state changes, and the state changes are being quickly overwritten. Out of interest do you notice any change or flickering if you quickly mash some of the buttons?

I posted a build on mitcha's issue on github if you'd like to try it out https://github.com/ndeadly/MissionControl/issues/211#issuecomment-798907624

for my previous test , no flickering , nothing happen , i just pluged in the joycons and push home button.

im barrely sure that the azerty , qwzerty change someting , since when i push up in windows it register "az" and not "wz" , same with another button.

can't test for now , need some max 3hours to get in.

 

[mitcha]

@ndeadly here is the btdb

Spoiler

the icade does not work with the github build , but the buttons are grey.

idk why , nothing works for now , the switch reconized the icade since it paired one's , but i do reboot the console multiple time and it still reconized.
i read in one post, if we reboot/shut down ghe switch , the pairing method need to be REperformed.

edit :
when in btdb app , i push some icade button and i have a message : device condition event (3times).
no message when joycon's are pressed !

 

[VashTS]

Hmm, ok it might be sending constant updates rather than just when the state changes, and the state changes are being quickly overwritten. Out of interest do you notice any change or flickering if you quickly mash some of the buttons?

I posted a build on mitcha's issue on github if you'd like to try it out https://github.com/ndeadly/MissionControl/issues/211#issuecomment-798907624

no changes at all. just updated to the icade build from github, rebooted my switch and while the buttons are not red, it still has no response in the HID test nor the settings Test Input Devices

and no flashes at all when buttons are pressed. just solid 0000 | 01 00 00 00 00 00 00 00 00

using btdb.nro -

00:12:a1:6d:15:d7 15e4:0132 ION iCade Game Controller

no changes when i press buttons while this is loaded.

edit: just grabbed that last posted on github and it worked

 

[mitcha]

working well with the latest build (ead0e7a) here :
https://github.com/ndeadly/MissionControl/issues/211
thank you very much @ndeadly , you can add the ion icade to the list
there is an icade v2 wich is exactly the same with same mapped buttons ,for those who have it and it should work like this one.


you are quick and determinated, thank you. (PM)

 

[VashTS]

working well with the latest build (ead0e7a) here :
https://github.com/ndeadly/MissionControl/issues/211
thank you very much @ndeadly , you can add the ion icade to the list
there is an icade v2 wich is exactly the same with same mapped buttons ,for those who have it and it should work like this one.


you are quick and determinated, thank you. (PM)

now to make a mount for the Switch inside the iCade

 

[kisamesama]

thx for your work man! seems to work great with my gamesir g3s. My gamesir t2a gets paired but the buttons don't work; any idea how to the buttons work?