Creator Micro V2: all keys double-fire (chatter) — persists after factory reset AND firmware 0.6.1

Environment: Creator Micro V2 / Input 0.18.0 / firmware flashed 0.4.0 to 0.6.1 / macOS over Bluetooth, also seen on Windows 11.

A single physical key press registers as two or more presses. It affects every key, not one switch.

THE DECISIVE TEST: after the problem survived the firmware update, I ran a full “Reset settings” from the Setup tab, leaving the device factory-blank (no custom layers, no macros, no Multi keys). I then assigned a single plain letter A to one key via Basic, opened a plain text editor, and tapped it slowly ten times. I still get doubled characters (aa) from single presses.

That rules out everything on my end: not my keymap (device was wiped), not Multi-key logic (none existed), not macro complexity (a single unmodified keystroke).

TIMING DETAIL: before the reset I built a Multi key to characterise it (tap types 1, double-tap types 2, hold types 3).

• One quick tap: expected 1, got 1 or 2

• - Deliberate double-tap: expected 2, got 2, 22, or 21

• - Hold ~1 second: expected 3, sometimes got 31

A single tap yielding 2 means one press bounces into two contacts inside the 250ms tap window. Hold yielding 31 means the RELEASE bounces too: the hold fires, then letting go registers as a fresh tap. So the board chatters on both make and break.

This also corrupts ordinary single-action keys, not just Multi keys. A Delete key can remove two items from one press, which makes the pad risky to use in Outlook.

ALSO: since flashing 0.6.1, the Firmware version field in Setup displays blank. Device model and Input version populate normally. It read 0.4.0 before the update. Possibly unrelated, possibly a sign the flash did not complete cleanly.

I saw the report here about a corrupted keymap.json surviving a firmware update and producing repeated key input (“endless K”). Mine looked similar, which is why I tried the reset, but the reset did not resolve it.

QUESTIONS:

1. Is this known on this hardware revision or firmware line?

2. 2. Is there a debounce / tapping-term setting, or a firmware build with a longer debounce window?

3. 3. Should the Firmware version field be blank after a successful 0.6.1 flash?

4. 4. If this is a hardware fault, what is the warranty process?

Happy to run any diagnostic or reflash. My profile is exported, so wiping the device again costs me nothing.