A hobbyist solved what Sony won't
When a company's official ecosystem leaves users with an incomplete experience, the maker community often steps in to fill the silence. A developer known as SlaveKnightSoman built a Raspberry Pi Pico 2W dongle that restores the full haptic and adaptive trigger functionality of Sony's DualSense controller on PC — features that Windows Bluetooth quietly discards due to bandwidth limitations Sony has never moved to address. The solution costs a fraction of what a commercial product would, works better than anything Sony currently offers, and asks an old question in a new register: what does it mean when a hobbyist's weekend project outpaces a corporation's product roadmap?
- Windows Bluetooth cannot carry the four-channel audio bandwidth the DualSense needs, silently stripping away haptics and adaptive triggers the moment a user goes wireless on PC.
- Sony has never released an official dongle to close this gap, leaving PC gamers to choose between a tethered cable and a diminished wireless experience.
- A developer called SlaveKnightSoman refused that compromise and built a hardware bridge using a Raspberry Pi Pico 2W and custom firmware called DS5Dongle.
- The dongle restores full DualSense functionality wirelessly, runs on an overclocked Pico 2W, and costs a fraction of any commercial alternative.
- The maker community has once again outpaced an official solution — not because the problem was hard, but because no corporation had sufficient incentive to solve it.
A PlayStation 5 controller connected to a PC by cable delivers the full experience — haptic feedback, adaptive triggers, the works. Switch to wireless via Windows Bluetooth, and those features disappear. The operating system simply lacks the bandwidth the DualSense needs to transmit its richer sensory data alongside standard inputs.
Sony has never released a dongle to fix this. The company supports its controller on PlayStation hardware and leaves PC users to negotiate the trade-off themselves. For developer SlaveKnightSoman, that was unacceptable. After a long search for a proper wireless solution, they built one: a Raspberry Pi Pico 2W acting as a hardware bridge between the controller and the computer, running firmware called DS5Dongle on an overclocked board. The result is full DualSense functionality, wirelessly, with no cables and no compromises.
What makes the solution stand out is its accessibility. The Pico 2W is inexpensive and widely used by hobbyists, and the setup is manageable even without deep hardware expertise. The maker community identified the gap between what Sony offers and what users actually need — and filled it with ingenuity.
The uncomfortable truth the project surfaces is this: the problem was never technically unsolvable. A hobbyist solved it in their spare time. Sony simply had no commercial reason to. That a DIY project now outperforms the official ecosystem is less a triumph of engineering than a quiet indictment of where corporate incentives end and user needs begin.
A PlayStation 5 controller works fine on a PC—until you try to actually use it wirelessly. Plug it in with a cable and you get the full experience: the haptic feedback that lets you feel a gun's recoil, the adaptive triggers that resist when you're drawing a bow. Go wireless through Windows Bluetooth and those features vanish. The operating system simply doesn't support the four-channel audio bandwidth that the DualSense controller needs to transmit all that sensory information alongside the standard button inputs.
Sony has never released an official dongle to bridge this gap. The company sells the controller, supports it on PlayStation hardware, and leaves PC users to choose: tether yourself to a three-meter cable or accept a diminished experience. For one developer who goes by SlaveKnightSoman, that compromise was unacceptable. After spending far too long chasing a proper wireless solution, they found something better than what Sony offers: a Raspberry Pi Pico 2W sitting between the controller and the computer, acting as a hardware translator that restores everything Windows Bluetooth strips away.
The Pico 2W is a small, inexpensive microcontroller board—the kind of thing hobbyists have been using for years to solve connectivity problems that official manufacturers won't touch. In this case, it works as a wireless bridge, receiving the full signal from the DualSense and passing it to the PC in a way that preserves the haptics and adaptive triggers. The firmware, called DS5Dongle, runs on an overclocked Pico 2W and handles the translation seamlessly. No cables. No loss of features. No waiting for Sony to release hardware that may never come.
What makes this solution remarkable isn't just that it works—it's that it works cheaply and easily. The Pico 2W costs a fraction of what a commercial dongle would, and the setup process is straightforward enough that someone without deep hardware experience can manage it. This is the maker community doing what it does best: identifying a gap between what companies offer and what users actually need, then filling it with ingenuity and accessible technology.
The broader implication is harder to ignore. Sony controls one of the world's most popular gaming ecosystems. It makes excellent controllers. Yet it has chosen not to provide a simple wireless solution for PC gamers who want the full feature set. That gap exists not because the problem is unsolvable—it clearly isn't—but because there's no commercial incentive for Sony to solve it. A hobbyist with a Raspberry Pi and some firmware knowledge solved it in their spare time. The DIY solution now works better than anything Sony offers for PC, which raises an uncomfortable question: why should it have taken this long for someone outside the company to build what should have been an obvious product?
Citas Notables
I've spent way too much time trying to get the PS5 experience on PC without being tethered by a 3 meter cable. Windows Bluetooth strips away the haptic feedback and adaptive triggers because it doesn't support the 4 channel audio bandwidth the DualSense requires.— SlaveKnightSoman, developer
La Conversación del Hearth Otra perspectiva de la historia
Why does Windows Bluetooth strip away these features in the first place? It seems like an arbitrary limitation.
It's not arbitrary—it's a bandwidth constraint. The DualSense needs four channels of audio to send haptic and trigger data alongside the normal controller signals. Windows Bluetooth just doesn't allocate that much space. Sony's own wireless protocol on PlayStation does, but they never extended that to PC.
So Sony could have solved this themselves with an official dongle?
Absolutely. They have the hardware expertise, the controller design, everything. They just haven't made it a priority. A Pico 2W costs a few dollars. An official Sony dongle would cost more and generate less profit than selling another controller.
Does the DIY solution feel like a workaround, or does it actually feel like the intended experience?
That's the thing—it feels like what the PC experience should have been from the start. You get wireless freedom without sacrificing any of the sensory feedback. It's not a compromise; it's the full feature set.
How accessible is this for someone who isn't a hardware tinkerer?
More accessible than you'd think. The firmware is ready to go, the Pico is cheap and widely available, and the setup is straightforward. It's not plug-and-play, but it's close enough that the barrier to entry is low.
What does it say about the gaming industry that a hobbyist had to solve this?
That there's still space for makers to outpace official solutions. Companies optimize for profit margins and mass appeal. Sometimes the best answer comes from someone who just wanted their controller to work properly.