Homebrew Project Testers wanted: BtEmbedded, a new bluetooth stack

[niuus]

About the Wii U Pro Controller, I definitely want it to work (but again, I don't own one ). Are you able to configure Dolphin to use the Bluetooth passthrough? If you do, then you can run these programs in Dolphin, and then you'll see the program logs, which would help me to debug the issue. I can make a build with the most recent changes, and with full BT logging enabled.

So if I undertstand right, I would need to sync the Wii U Pro Controller to the PC, and then use your app through Dolphin? The only thing I have never tried again is syncing the controller to the PC, I did try once many years ago when using Windows 7, but it never worked. I use Windows 10 now, not sure what the current, reliable methods are.

 

[radicalten]

Good work Mardy!

 

[mudrik]

So if I undertstand right, I would need to sync the Wii U Pro Controller to the PC, and then use your app through Dolphin? The only thing I have never tried again is syncing the controller to the PC, I did try once many years ago when using Windows 7, but it never worked. I use Windows 10 now, not sure what the current, reliable methods are.

You don't have to pair your controller with Windows: just follow the steps from the Dolphin wiki (I posted the link above), and the new driver will take full control of your BT controller, meaning also that it doesn't matter if you previously paired any device on Windows, since now Windows won't touch your controller (until you have the alternative driver running).

For pairing, start the Wii System Menu from Dolphin -> Tools, open the controller settings, and press the Sync button from there (and on your controller, of course).

Post automatically merged: Aug 18, 2026

Post automatically merged: Aug 18, 2026

Tested your 3 builds with my Wii U Pro Controller.

VisualControllerTest = Doesn't connect.
EgcSdlTest 0.1 = Doesn't connect. Only a grey screen.
EgcSdlTest 0.2 = Doesn't connect. Only a grey screen.

Hi @niuus, I just realized that the EgcSdlTest builds you tried were released before I added wiimote support to EGC. I now tagged a new 0.3 version, which supports wiimotes and hopefully the Wii U Pro Controller too. Can you please give it a try?

https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3

 

[niuus]

Hi @niuus, I just realized that the EgcSdlTest builds you tried were released before I added wiimote support to EGC. I now tagged a new 0.3 version, which supports wiimotes and hopefully the Wii U Pro Controller too. Can you please give it a try?

https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3

0.3 tested! It disconnects when the app opens (Wii U Pro Controller), and doesn't connect again. Grey screen only.

 

[mudrik]

0.3 tested! It disconnects when the app opens (Wii U Pro Controller), and doesn't connect again. Grey screen only.

At that point, can you set the controller in search mode (on a regular wiimote that is done pressing 1 and 2 at the same time, I don't know how that's for the Wii U pro controller) and then press the Sync button on the Wii (not long press, just a regular press)? It should try to connect, then.

 

[niuus]

At that point, can you set the controller in search mode (on a regular wiimote that is done pressing 1 and 2 at the same time, I don't know how that's for the Wii U pro controller) and then press the Sync button on the Wii (not long press, just a regular press)? It should try to connect, then.

The Wii U Pro Controller has a sync button, same as the Wiimote.

On the grey screen, pressed Sync on the controller, and then on the console. Nothing. Tried this 4 times, just in case.

The controller works fine in any other supported homebrew.

 

[mudrik]

On the grey screen, pressed Sync on the controller, and then on the console. Nothing. Tried this 4 times, just in case.

Indeed it could not work, it's expansion ID wasn't even checked in the code. I made some changes, can you see if things are better now? It should at least connect. Keys are most likely all wrong; if it connects, please tell me which keys are misbehaving (and how): https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu0

 

[niuus]

Indeed it could not work, it's expansion ID wasn't even checked in the code. I made some changes, can you see if things are better now? It should at least connect. Keys are most likely all wrong; if it connects, please tell me which keys are misbehaving (and how): https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu0

Sure, give me some minutes and I'll check this version.

Post automatically merged: Friday at 8:53 PM

Same results, dead.

It crashed once when I pressed Sync on the console, but I couldn't reproduce it later.

Can you make Reset a return to loader? I have to power off the console every time.

 

[mudrik]

Sure, give me some minutes and I'll check this version.

Post automatically merged: Friday at 8:53 PM

Can you make Reset a return to loader? I have to power off the console every time.

Hi! I made a new version, the previous one was checking that the Product Id advertised over BT was 0x0306, which is the wiimote, whereas the Wii U Pro is (AFAIU) 0x0330. I also made it possible to quit using the Reset button: https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu1

I'm trying to get the logging information shown onto the screen, but I'm hitting some lockups with it, so that part is not ready yet.

 

[niuus]

Hi! I made a new version, the previous one was checking that the Product Id advertised over BT was 0x0306, which is the wiimote, whereas the Wii U Pro is (AFAIU) 0x0330. I also made it possible to quit using the Reset button: https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu1

I'm trying to get the logging information shown onto the screen, but I'm hitting some lockups with it, so that part is not ready yet.

I think this is the closest to a response from the app we have gotten.

While it is not working yet, it looks like it is going to get a connection. If I press a button so the controller turns on and connect, while it is flashing, it will show a virtual controller model on screen for less than a second, then disappear, while the controller also turns off immediately. You can repeat this many times (it did eventually stopped happening).

 

[mudrik]

I think this is the closest to a response from the app we have gotten.

While it is not working yet, it looks like it is going to get a connection. If I press a button so the controller turns on and connect, while it is flashing, it will show a virtual controller model on screen for less than a second, then disappear, while the controller also turns off immediately. You can repeat this many times (it did eventually stopped happening).

Mmm... after reading https://wiiubrew.org/wiki/Pro_Controller:

Note that the Wii U Pro Controller does not have the 0x1700 bytes of accessible EEPROM memory normally found in wiimotes, any attempt to read from this area will cause the controller to disconnect.

That is indeed the area of memory where I was reading the calibration data from. I've now modified the driver to skip this step, so it should go a little further: https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu2

Thanks for your help, by the way!

 

[niuus]

Mmm... after reading https://wiiubrew.org/wiki/Pro_Controller:



That is indeed the area of memory where I was reading the calibration data from. I've now modified the driver to skip this step, so it should go a little further: https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu2

Thanks for your help, by the way!

Glad to help!

Okey, this one went a bit further. Not working yet, but closer.

After pressing a button or trying to sync, a virtual controller appears and stays on-screen, upside down, showing the back. The Wii U Pro controller flashes the 4 LEDs continuously and won't turn off, and that's it, no response to any input. Returning to HBC will sync it again as normal.

 

[mudrik]

Okey, this one went a bit further. Not working yet, but closer.

Hi again! Here's a new build: https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu3

It will not work, as the functionality is exactly the same as the previous version, but I've added logging. It would be great if you could take a photo of the screen (a video might be better) and send it to me. The font is very small so that more information can fit on the screen; if it turns out not to be legible, I'll have to make another build with a bigger font.

 

[niuus]

Hi again! Here's a new build: https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu3

It will not work, as the functionality is exactly the same as the previous version, but I've added logging. It would be great if you could take a photo of the screen (a video might be better) and send it to me. The font is very small so that more information can fit on the screen; if it turns out not to be legible, I'll have to make another build with a bigger font.

Got some good news for you:

When you start 0.3-wiiu3, the controller stays connected. It won't flash the LEDs, but it has a permanent connection. Now, a ton of numbers start crossing the screen, never stopping. The news: since the small text reflects the buttons pressing in real time, I could verify every single button works. Even L3 and R3! (which is a first for any homebrew, as they were never recognized as extra buttons). The controller never disconnects, until I exit.

My suggestion: since there is way too much info and I'm guessing you want a clear reading of it, why not make it log to a txt file? I could press every button individually, and make a circle with the sticks, so it gets logged. Then attach the txt here.

 

[Extrems]

Even L3 and R3! (which is a first for any homebrew, as they were never recognized as extra buttons).

What do you mean? They've been mapping options in Not64 and Enhanced mGBA for years.

 

[niuus]

What do you mean? They've been mapping options in Not64 and Enhanced mGBA for years.

Ah, sure, except those, for which I have never configured buttons before (and when I did, it was pre-december 2016 builds, without WUPC support), as I don't use Not64 regularly except for comparison tests against Wii64, which tends to be much better for playing extensively. Wii64 I do use and prefer it, and that one doesn't have support for L3/R3. I don't even use emGBA on the Wii, so who would have guessed. Cool, for you!

Are you also helping with BtEmbedded code, now?

 

[mudrik]

My suggestion: since there is way too much info and I'm guessing you want a clear reading of it, why not make it log to a txt file? I could press every button individually, and make a circle with the sticks, so it gets logged. Then attach the txt here.

Why didn't I think of that before Here's a new build, it saves to egc-sdl-test.log in your SD card: https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu4
Everytime you restart the app, the log file is created anew -- previous contents are lost.

Please press only one button at once, and write down the order in which you press the buttons, so that I can correlate with the logs. AFAIU, this controller should also have an accelerometer and a gyroscope: did you see a set of bytes continuosly changing there values, while moving the controller? If not, there's probably some more commands we need to send to it in order to enable them.

 

[Extrems]

AFAIU, this controller should also have an accelerometer and a gyroscope: did you see a set of bytes continuosly changing there values, while moving the controller?

It does not, and there's an infamous hidden feature in Splatoon that involves strapping a Wii Remote Plus to it.

 

[niuus]

Why didn't I think of that before Here's a new build, it saves to egc-sdl-test.log in your SD card: https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu4
Everytime you restart the app, the log file is created anew -- previous contents are lost.

Please press only one button at once, and write down the order in which you press the buttons, so that I can correlate with the logs. AFAIU, this controller should also have an accelerometer and a gyroscope: did you see a set of bytes continuosly changing there values, while moving the controller? If not, there's probably some more commands we need to send to it in order to enable them.

But you disabled the on-screen feedback with the data, why...

Anyway, 28 USB drive connections back and forth later, here goes the files! I waited until the controller model shows up, and pressed every button (individually) 3 times, with one second distance approx. I also circled the stick clockwise, just in case.

If you need another round, it would be cool if you could make it so I can create a new log file pressing eject (which should append a new number and doesn't overwrite the previous one), so the controller is always on and I can help you more efficiently.