Mission Control homebrew tool adds Switch firmware 23.0.0 and 23.0.1 support

The Bluetooth controller sysmodule for Nintendo Switch catches up to Nintendo's latest firmware, with new DualSense trigger settings and battery reporting fixes.

AI-drafted from 2 sources. This story was written with AI from the outside reporting listed under Sources, and checked by automated tools before it went up. The originals have the full detail.

Mission Control, the homebrew tool that lets third party controllers pair with a Nintendo Switch as if they were official Joy-Cons, now works on firmware 23.0.0 and 23.0.1. Version 0.16.0 landed on the project's GitHub page on 2 October, according to the release notes, and was picked up the same day in a Reddit thread on r/SwitchHacks.

What Mission Control actually does

Mission Control is a sysmodule, a background system process injected into the Switch's firmware, that rewrites parts of the console's Bluetooth stack. Instead of relying on Nintendo's own controller drivers, it intercepts pairing and input requests so that PS4, PS5 DualSense, Xbox and Wii controllers look like native Switch controllers to the system. That is why a DualSense can rumble and light up on a modded Switch without any extra app running, and why the project has to track Nintendo's firmware closely rather than sitting on top of it.

Why a firmware bump breaks a sysmodule

Each time Nintendo ships new system software, the internal functions and memory offsets Mission Control patches can shift, so support has to be added release by release rather than assumed. The 0.16.0 changelog, posted by developer ndeadly on the release page, lists the 23.0.0/23.0.1 support alongside a run of smaller fixes: a new setting for the maximum travel distance of DualSense adaptive triggers, a loosened device class check so JoyconDroid (an app that turns an Android phone into a Joy-Con, used without root access) accepts a wider range of devices, and a reworked battery level reporting system for Sony controllers meant to stop the console firing spurious low battery warnings when the level isn't actually critical.

There are also lower level changes aimed at robustness rather than features: a “mitm” (man in the middle) shim for shortened versions of the system's GetDeviceCondition and GetDeviceInfo Bluetooth functions, and a fix for a bug where the Bluetooth event handling thread was running at a lower priority than intended, which could in theory cause stutter or delay in controller input.

Release notes warn of possible regressions

ndeadly's own notes are unusually candid about the state of testing. The developer writes that “the codebase has undergone some non-trivial refactoring since the previous release” and that testers were recruited through a Discord server but the response was, in the developer's words, “rather underwhelming.” Rather than delay the update indefinitely while waiting on 23.0.0 support, ndeadly released 0.16.0 as is and is now asking users who hit problems to report them, pointing people towards a dedicated testing channel for future releases.

For players, the practical upshot is that anyone on firmware 23.0.0 or 23.0.1 who wants to pair a DualSense, DualShock or Xbox pad over Bluetooth now has a working path again, including the finer grained adaptive trigger control for DualSense owners. What isn't yet clear is whether the internal refactor introduces new bugs that only show up once more people are running it outside ndeadly's own test group. Nothing in the release notes or the Reddit thread points to any specific regression so far, but the developer's own warning suggests the usual advice applies: back up your save data and configuration before updating, and watch the project's GitHub issues if a controller starts behaving oddly.

Sources

Image: Illustration: AI-generated for Gaming World