SN30 Pro+ controller's Switch mode isn't recognized at all...?

[Impeta]

It has been crucially like this ever since 5.16. My 8BitDo controller's Switch mode worked like a charm before, provided I would install manually the hid_nintendo module. I could get around it by shifting to its internal Xinput mode, but it lacks the gyro functions, whom exclusive to Switch mode.

I excavated through internet for finding somebody else with similar problem, and as this Reddit thread seems to indicate, this is a real confirmed issue. Although different controller, the description matches as precise my situation, right down into my dmesg reports outlining the LED's brightness failure. Most importantly, a kind user in the replies has brought a great synopsis about it, so be sure to read it before anything else.

https://libreddit.spike.codes/r/archlinux/comments/s3u7aa/sn30_pro_2_missing_from_devinputjs_after_516/

[jason-oliveira]

Current progress on bug: https://bugzilla.kernel.org/show_bug.cgi?id=216940

Kernel 6.1 allows syncing with 8bitdo controllers, and pairing them. The issue now (again?) is that they keep registering a second ID after being paired, which udev/logind has no clue what to do with.

[michaeljhkim]

I am having this exact same issue and I have no idea what to do. Is there some solution that we can perhaps try? I am doing this with the king kong pro 2 controller

[dylanmilesmsu]

Just to add, I have a RetroFighters BattlerGC which has the same problem. Previous, this controller was usable with SteamInput, but now it's completely nonfunctional no matter what configuration you use. It just isn't recognized at all unless you unload hid_nintendo, and doing that causes it to detect but have all the buttons getting pressed like crazy.

[dylanmilesmsu]

This is what shows up when connecting my RetroFighters BattlerGC