Your PowerA controller pairs with Windows without a fight. Windows lists it, maybe a game even responds to it — but BetterJoy never shows it, no matter how many times you re-pair. You are not doing anything wrong: this is one of the best-documented limitations in the project’s tracker, where reports about PowerA models span 2019 to 2025 (issues #63, #83, #163, #606, a long support request in #268, and #1222 in May 2025). This page gives you the realistic checklist, the reason clones are hard, and — just as important — the point at which to stop trying.
The shape of the problem (#1222)
The most recent report is the cleanest: on Windows 11, the PC recognised a PowerA controller while BetterJoy did not list it at all. That split — Windows yes, BetterJoy no — is the signature of this issue and separates it from pairing trouble. If Windows cannot see your controller either, you have a different problem; start with the not-detected guide instead. What follows assumes Windows sees the pad fine.
Why third-party pads are a hard case
BetterJoy was written against Nintendo’s own hardware. It finds controllers by how they present themselves over Bluetooth — their identifiers and behaviour — and third-party manufacturers imitate that presentation to varying degrees: different Bluetooth identifiers and MAC addresses, different polling behaviour, differently scaled sensors. Version 7’s release notes are candid that third-party support “is not perfect,” and the support that exists flows through one feature: the Add Controllers button.
There is a naming problem underneath the identifier problem. Nintendo’s pads announce themselves to Windows in the standard forms BetterJoy was built to expect, while third-party pads announce vendor-specific names and device IDs that vary not just between brands but between models from the same brand in the same year. A detection routine can only match what it knows or is taught — which is why one PowerA model can appear in BetterJoy while its near-identical sibling never does, and why outcomes in the tracker are resolutely model-by-model rather than brand-wide. Keep that in mind while running the checklist: you are testing your specific unit, not the logo on it.
The checklist: what is actually worth trying
- Confirm the pad works as a generic controller first. Open
joy.cpland check that buttons and sticks respond there. If a pad works in joy.cpl but not in BetterJoy, at least you know the hardware and the pairing are sound. - Run the Add Controllers flow properly. With the controller connected to Windows, start BetterJoy and use the Add Controllers button — our third-party controllers tutorial walks the full flow, including what the button can and cannot teach the program about a new device.
- Try USB as well as Bluetooth. Some pads present differently wired than wireless; a model invisible over Bluetooth occasionally registers over a cable (and vice versa). Ten minutes, worth ruling out.
- If it registers but the gyro or sticks feel wrong, calibrate. The v7 feature set includes config-file calibration for third-party pads — the
acc_sensiti/gyr_sensitivalues inBetterJoyForCemu.exe.configexist for exactly the “recognised but misbehaving” case. Recognised-but-weird is fixable; never-recognised is usually not. - Search the tracker for your exact model. With six-plus PowerA threads alone, someone may have posted a model-specific outcome — success or confirmed failure — that saves you an evening.
The honest bottom line on PowerA
Across those years of reports, many PowerA models have simply never been recognised by BetterJoy, and there is no configuration file edit that changes a device’s Bluetooth identity into one the program accepts. (A stronger claim circulates in community posts — that the maintainer confirmed PowerA is unsupported outright — but it is not something we can quote verbatim from a primary source, so we will not print it as fact. The pattern of reports speaks plainly enough on its own.) If you have run the checklist, the rational conclusion is that your model is in the not-recognised group, and your options are: use the pad where it works natively (many third-party pads behave as standard controllers in Steam and in games with their own input support), use it on the console it was built for, or use a genuine Nintendo pad — or a clone with a confirmed success report — for your BetterJoy setup. There are no affiliate links in that advice; it is the same answer the tracker gives, minus the years of scrolling. One adjacent trap: if a pad is recognised but then appears twice in a game, that’s not this issue — it’s double input, and it has a clean fix. The program itself is on the download page, and all the neighbouring fixes are gathered on the troubleshooting hub.
FAQ
My PowerA worked with an older BetterJoy. Did support get removed?
Not deliberately, as far as the record shows — but recognition depends on the specific model’s behaviour, and Windows Bluetooth stack updates over the years have changed how some pads present themselves. Re-run the Add Controllers flow on the current version and check the tracker for your model before assuming a regression.
Will the maintained BetterJoy fork recognise my PowerA?
The community fork’s documented additions are newer hardware families (such as NES/N64-style controllers) and a modernised driver stack — we have no verified source promising PowerA recognition, so we won’t claim it. If you try the fork, treat it as an experiment, not a fix.
Is there a list of third-party models that do work?
There is no official compatibility list — that absence is part of the problem. The practical substitute is the issue tracker itself: model-specific threads with confirmed outcomes, which is why step 5 of the checklist points you there.