[Request] Update for 60HE+

[Sparoney]

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

[ShayBox]

They should both support 60he, anything brand new requires the official RGB sdk be updated first. The rust bindings build from the RGB sdk.

[ShayBox]

I'm also not able to update this until tauri-egui updates, this project doesn't compile. tauri-apps/tauri-egui#18

[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+

[ShayBox]

I was able to get a new release out with 60HE+ support
https://github.com/ShayBox/Wooting-Profile-Switcher/releases

I was having issues with Visual Studio's Build Tools, and had to patch tauri-cli@2.0.0-alpha.10 with deflate, but it works. https://github.com/Shays-Forks/tauri

I found a new template that I plan on migrating this project to instead of tauri-egui and to update to the latest Tauri v2 beta. https://github.com/noxware/egui-tauri-template

[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?

[ShayBox]

Try deleting the config file, the program fetches devices from Wootility on new config creation.

[Sparoney]

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

[ShayBox]

If you run the portable debug build in a terminal there are visible logs, what version of Wootility are you using?

[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

[ShayBox]

Can you give me your serial number or a modified version of it, 26 characters is longer than expected

impl From<&Device> for DeviceSerial {
    fn from(device: &Device) -> Self {
        Self(format!(
            "A{:02X}B{:02}{:02}W{:02X}{}H{:05}",
            device.supplier,
            device.year,
            device.week,
            device.product,
            device.production as u8,
            device.product_id
        ))
    }
}

[ShayBox]

Could you send me the Serial Number Buffer line from this debug build
https://gofile.io/d/j2vA8K You can change the numbers I just need to know which bytes are populated past the 15th

Example

Serial Number Buffer: [208, 218, 3, 136, 11, 2, 0, 21, 6, 3, 0, 1, 0, 162, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

[ShayBox]

I also need the device ID from Wootility (Ctrl + Shift + I -> Application -> Local Storage -> file:// -> persist:root