[New Device] Sandberg Firestorm Mech Keyboard
Name of device:
Sandberg Firestorm Mech Keyboard
Link to manufacturer's product page:
https://sandberg.world/en-us/product/FireStorm-Mech-Keyboard-German
Please select what type of device/interface the device uses:
ID information:
lsusb gives ID 0c45:8006 Microdia Dual Mode Camera (8006 VGA)
Please attach screenshots of the device's official control application here:
Please attach device captures here:
Sandberg_Firestorm_ReportDescriptor.pcapng
RGB captured in static mode setting the color (I chose the ones looking most closely like pure RGB).
Sandberg_Firestorm_Static_Red.pcapng Sandberg_Firestorm_Static_Green.pcapng Sandberg_Firestorm_Static_Blue.pcapng
Turned lighting off and on again.
Sandberg_Firestorm_Off_On.pcapng
Going through the modes (selecting both directions when those were available as an option for each mode). Color was white when available, sometimes one could not choose. Some modes use both "basic" and "accent" colors (keyboard is lit red and pressed keys are lit in white for example). Those modes by default only allow to set one color for them, though (either "basic" or "accent" depending on the mode, the other color is usually red then). Maybe there is a way to also set the other color that is just not available through the proprietary ways, but could be made accessible.
Sandberg_Firestorm_Modes.pcapng
Stepping through brightness from off to full.
Sandberg_Firestorm_Brightness_Off_To_Full.pcapng
Stepping through animation speed from low to high.
Sandberg_Firestorm_Speed_Slow_To_Fast.pcapng
Another capture of applying a user defined mode (key specific colors). In that mode unfortunately two keys cannot be selected in the proprietary software on my German keyboard.
Sandberg_Firestorm_Applying_User_Mode.pcapng
The proprietary sofware applies light changes (which work), but shows an error message afterwards every time. Might just be badly programmed.
The keyboard also has side lights. Those can only be changed with Fn keys and not through the proprietary software, though. But maybe they could also be set via USB and are just not exposed in their software.
Checklist for Step2
-
Name of device -
A link to the vendors product page has been included -
The transport bus has been identified and the appropriate label added to the issue. -
The device ID's have been included for USB or PCI -
Screenshots of the OEM Application are included -
There is either, appropriate code examples linked or suitable device captures attached




