jamesgrams / gamepad-to-keyboard-mapper

2 stars 1 forks source link

wiimote over bluetooth #1

Open protective1 opened 2 years ago

protective1 commented 2 years ago

Hi - I've connected a Nintendo Wiimote to my chromebook via Bluetooth. However, when I open this extension and Add Mapping, nothing happens when I press buttons on the Wiimote.

jamesgrams commented 2 years ago

I'm not sure Chromium supports Wiimotes - can you test if your Wiimote and button presses show up here: https://gamepad-tester.com/?

protective1 commented 2 years ago

James,Thanks for responding.  I did not get a response from the Wiimote on the page you listed, but I have used it on another page.Specifically, I did not get a response from the Wiimote on gamepad-tester.com.  However, I can see the buttons being pressed when I go to https://wiimote-chrome.vercel.app (which was linked to from GitHub - natel97/wiimote-chrome).  I just had to click the "connect to HID" button when that page opened in my Chrome browser.  Any idea what this means for Wiimote support in Chrome?

|

GitHub - natel97/wiimote-chrome

Contribute to natel97/wiimote-chrome development by creating an account on GitHub. |

|

|

On Wednesday, February 16, 2022, 10:06:41 AM EST, James Grams @.***> wrote:

I'm not sure Chromium supports Wiimotes - can you test if your Wiimote and button presses show up here: https://gamepad-tester.com/?

— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: @.***>

jamesgrams commented 2 years ago

I checked the repository (https://github.com/natel97/wiimote-chrome) and it looks like it is using the HID API to connect rather than the Gamepad API (which my extension and https://gamepad-tester.com/ uses). Chrome is not detecting the Wiimote as a Gamepad, but it is detecting is as a Human Interface Device.

It looks like what you want may be possible. There would more complexity, since the Gamepad API is simple, but the HID API is lower level. I also think you'd have to put your chromebook in developer mode to be able to access /dev/hidraw as specified in the README (Developer mode need based on the following comment: https://support.google.com/chromebook/thread/87657785/how-do-i-access-dev-hidraw0-in-linux-terminal-without-rooting?hl=en).

There's a lot of work here that I don't think I'll be able to get to in the near future, but if you are able to work on it, I would more than happily add your changes to the codebase.