[Request] Update for 60HE+

[Sparoney]

Any chance of updating this plus the Rust SDK bindings for the 60HE+? Thanks!

[Sparoney]

The Official SDK was updated on Feb 1 for the 60HE+.

Unfortunate about tarui-egui though that's annoying.

Reason why I assume this needed an update is because the program unfortunately doesn't detect my 60HE+

[Sparoney]

You're a legend thank you!

[Sparoney]

Hey, I've installed the new update and it doesn't seem to be detecting my 60HE+ for some reason. I completely uninstalled and reinstalled, trying both the user and system versions.

In the config json file, devices is empty so the profiles indices in the program say -1. I did notice however when I open the program, my RGB on my keyboard pauses/flickers for a split second. Wootility is closed.

Do you have any idea what could be causing this?

[Sparoney]

Yeah I tried that, still doesn't work unfortunately. Does your program have logs at all?

[Sparoney]

I ended up checking those logs, there were no errors just it saying whenever the active window changed. I am using Wootility v4.6.15 and the Analog SDK v0.7.5, both of which are the latest

My keyboard shows up as:
Wooting 60HE Plus
Firmware: v2.7.2

and the serial number is 26 characters long

[Sparoney]

Amazing it works perfectly! Thanks so much for the quick fixes as well

[aminesemlalidev]

Hello, with the versions 2.3.3 and 2.3.4, I'm still having the same issue: devices are empty (Wooting 60HE+)
I also have a 26 digits Serial Number, (A02B2409W05T02100S02H11694), Product ID: 4896 (Not sure about that, I found it in the wootility log file, but maybe it's 11694)
But thank you for proposing this feature, much appreciated <3 I really want this to work

[Sparoney]

FWIW, I actually think 2.3.4 has broken the 60HE+ again. I'm still on 2.3.3 and it's working fine for me. Have you deleted your config file and tried again?