EVOWORKS Control

An independent, community-built Windows companion for EVOWORKS keyboards. It is not affiliated with, endorsed by, or supported by EVOWORKS, Ticktype, Qwertykeys, VIA, or QMK.

EVOWORKS Control is a lightweight native Windows application for configuring supported EVOWORKS keyboards. It is designed as a desktop alternative to the VIA web configurator: clear device detection, a visual keymap editor, direct supported RGB controls, local profiles, and a tray companion without a driver, keyboard hook, or Windows service.

Current status

This is a beta project. EVO80 is the first verified device. Please read the known limitations before changing firmware or relying on the app for critical workflows.

Device / transport	Detection	Keymap & supported RGB	Battery
EVO80, direct USB/cable (36B0:300E)	Verified	Verified VIA V3 route	No host percentage published by stock firmware
EVO80, 2.4 GHz receiver (36B0:3002)	Verified	Safely unavailable pending a separate receiver protocol	Keyboard-only indicator
EVO80, Bluetooth	Best-effort Windows detection	Safely unavailable	No reliable Windows report observed
Other EVOWORKS keyboards	Detection-only when identified	Not enabled until a definition and transport are verified	Device-specific

The app never guesses at a wireless configuration protocol. Configuration controls become available only after a direct wired, read-only VIA handshake succeeds.

What it does

• Detects known EVOWORKS USB devices and distinguishes the EVO80 wired keyboard from its 2.4 GHz receiver.
• Reads and writes the verified wired EVO80 VIA keymap, layers, macros, and supported Matrix/Logo RGB settings.
• Captures local keyboard snapshots and can optionally apply them for a linked foreground application.
• Starts the installed copy quietly in the Windows notification area; portable copies remain portable and close normally.
• Provides a user-selectable installed close behaviour, local recovery logs, and no background telemetry.
• Installs no driver, service, HID filter, or keyboard hook.

Known limitations

• Stock EVO80 configuration is verified over direct USB/cable only. The 2.4 GHz receiver and Bluetooth transport need their own independently verified protocol.
• The stock definition establishes global Matrix and Logo controls—not arbitrary host-streamed per-key RGB painting.
• The keyboard’s QK_BAT action shows battery on the keyboard. No safe host-readable numeric battery or charging report has been found, so the app does not invent one.
• Firmware flashing and bootloader operations are deliberately out of scope.
• Only EVO80 has been exercised against physical hardware. Contributions for other models must include evidence, definitions, and a non-destructive validation plan.

Screenshots

Home	Devices
Keymap	Lighting
Profiles

See screenshots/README.md for safe capture guidance.

Build from source

Requirements:

• Windows 10/11
• Visual Studio Build Tools or Visual Studio with MSBuild and the .NET Framework 4.8.1 targeting pack
• Inno Setup 6 only when building the installer

git clone https://github.com/devclinic/evoworks-control.git
cd evoworks-control
.\build\Build-Release.ps1
.\build\Test-Beta.ps1 -SkipInstallerChecks

Build the per-user installer:

.\build\Build-Release.ps1 -BuildInstaller
.\build\Test-Beta.ps1 -TestStartupIntegration

Generated executables and ZIPs stay out of Git. Publish signed binaries through GitHub Releases after validating them on a non-development machine.

Repository map

src/Evoworks.Control.App/  WPF application, device detection, HID/VIA protocol, UI
src/.../Services/          Device registry, HID enumeration, VIA, profiles, local logging
src/.../Definitions/       Device registry and unmodified EVO80 vendor VIA definition
installer/                 Inno Setup installer and installed/portable marker
build/                     Reproducible build and beta validation scripts
docs/                      Architecture, hardware research, and release process
.github/                   CI, CodeQL, issue forms, PR template, dependency updates
LICENSES/                  Notices for vendor data and protocol references
screenshots/               Public screenshots only; no personal/local captures

For the technical boundary between detection, HID transport, VIA, UI, and profile storage, read docs/ARCHITECTURE.md.

Contributing

Ideas, device definitions, protocol research, documentation, testing, and code are welcome. Start with CONTRIBUTING.md, use the issue forms, and keep hardware writes explicit, minimal, and reversible.

Please do not submit firmware dumps, personal diagnostic logs, serial numbers, or proprietary vendor tools without clear permission to redistribute them.

Security and privacy

Report vulnerabilities privately as described in SECURITY.md. The app’s local diagnostic logs intentionally omit key presses, HID payloads, and profile contents.

Licence and third-party notices

The EVOWORKS Control source code is available under the MIT License. The bundled EVO80 JSON definition is vendor-supplied data with separate provenance; it is not relicensed by this project. See THIRD_PARTY_NOTICES.md and LICENSES/VENDOR-DEFINITION-NOTICE.md.

EVOWORKS, EVO80, VIA, and QMK are names or marks of their respective owners.