r/EasySMX

Hey r/EasySMX — we’re the team behind EasySMX. We just relaunched our site and thought we’d skip the press release and ask what actually matters to you.

What changed:

- Cleaner product pages with full specs front and center

- New flagship showcase (Dune 8K PC, X-Series, M-series, etc.)

- Easier filtering by platform and use case

https://preview.redd.it/y05fr2jn44jh1.jpg?width=1280&format=pjpg&auto=webp&s=93be451e9a48b159663f38299f109a7c6516d47e

Site: https://www.easysmx.com

What we genuinely want to know: what’s missing? Better comparison tool? Setup guides? Something that actually helps you pick the right controller instead of just browsing pretty pictures?

Honest feedback is welcome — we’ll read every comment. The brand is small enough that we can actually act on it.

The X20 ships with no desktop software. You get a manual, a driver, and a firmware updater, and everything else lives in the phone app or behind button combos on the pad. I'm on PC so I pulled the protocol apart and built something for it.

What works right now:

• Macros on all four rear buttons, including chords, sequences and stick directions, with timing per step
• Vibration strength, which the pad's own controls can't set at all
• Stick and trigger deadzones and response curves
• Save files, so you can switch whole setups
• An input tester with a stick trail, and a polling rate meter
• A command line version if you prefer that

The reason I'm posting: I only have one X20. Everything was decoded and tested against my pad. I have no idea if it works on anyone else's. If you have one and you're willing to try it, that's genuinely the most useful thing anyone can do for this right now. If it works, great, tell me. If it doesn't, tell me the error or what the pad did and I'll dig into it.

Two things worth knowing before you try it:

It never touches firmware. Everything it changes goes over Bluetooth to the settings, and holding C for five seconds factory resets that. The firmware path can brick a pad and I deliberately left it alone.

Settings need Bluetooth on, even if you play wired or on the dongle. The pad exposes its config on a separate Bluetooth connection, so both can be live at once. Playing is unaffected.

Windows only for now. Free, open source, no account, no telemetry, no network code in it at all.

The Windows exe may trip your antivirus. It's a PyInstaller build, which sets off heuristics on shape alone, and it's unsigned because I don't have a certificate. There's a SHA-256 on the release and you can build from source instead if you'd rather not trust the binary.

https://github.com/AmjadAAYD/x20ctl

Also curious whether any of this works on other EasySMX models. The protocol belongs to the chip vendor rather than to EasySMX, so it might cover more than the X20. If you have a different one such as X10 , X05 , etc and it connects, I'd like to know.

Im releasing the version 0.2.1 Soon

Edit : 0,2,1 released .

https://preview.redd.it/oxltg1mpwsih1.png?width=1059&format=png&auto=webp&s=26d6d6dd2cc8df47b84cc728c4f1a92cc4dae44f

Hi there my X05 keeps shutting down whenever i use it on dongle mode or wire mode. It works for a couple of minutes and after that the issue remains constant. I tried Bluetooth mode and it's working fine so there's no issue with battery connection etc.

My X20 has no desktop app. The manufacturer ships a manual, a driver, and a firmware updater. Everything else is either a phone app or button combos on the pad itself. I'm on PC, so I spent a weekend pulling the protocol apart.

It turns out the pad exposes a second Bluetooth LE peripheral alongside the gamepad interface, advertising as Xpert2, with a config service nobody has documented publicly. The protocol is "KeyLinker", and it's from the chip vendor (ShenZhen ZhiXu) rather than EasySMX so it probably covers pads from several brands.

What I got working:

• Macros on all four rear buttons: sequences, chords, and stick directions
• Vibration strength 0-100% (the pad's own controls can't set it to zero)
• Battery level
• Save files you can switch between
• A recorder that captures what you press with real timing
• An input tester and a polling-rate meter

What I learned the hard way:

The pad broadcasts its own capability descriptor, and mine reports zero for lighting, turbo, and gyro. Those features exist in the hardware, but they're button-combo-only and genuinely unreachable over the protocol. So no RGB control, no matter how much I wanted it. Other pads on the same chip may well report them as available.

Also, my first macro made both thumbsticks sweep in circles until I killed it. Turned out the analog fields encode "idle" as 0b1000, not 0b0000  zero means direction: up. The encoding was working perfectly on input I'd misunderstood.

What I'm asking:

What would you actually want from controller software? I've deliberately not implemented firmware flashing that path goes through a mass-storage bootloader and is the one thing that can brick the pad, so I'm leaving it to the vendor's tool.

https://preview.redd.it/kycpy3h9qiih1.png?width=1919&format=png&auto=webp&s=384d8c4498eb99f3deb03d564ab5cd321ca01a23

Beyond that I'm open. Stick response curves are next (I can read them, haven't decoded the bytes yet). Someone suggested auto-switching profiles per game. What else is missing from the controller software you use?