Very very occasionally on pressing the key it will spam like 8+ key presses
key presses seem to spam keys very occastionally like every couple of weeks+
2 Replies
Got it — thanks for the details. Since the spamming happens super rarely (every couple of weeks), it’s most likely not a firmware issue but rather a hardware contact issue with that switch/socket. A couple of things you can check:
1. Check the switch itself
- Sometimes debris or dust can cause a jittery contact. You can try swapping the key with another switch and see if the problem follows the switch.
- If it does, that switch is defective and should be replaced.
2. Check the hotswap socket
- If the socket pins aren’t making perfectly solid contact, it can cause “bouncing” that looks like spamming. Gently press the switch down further or reinsert it.
- If needed, you can also reflow a touch of solder on the socket’s joints to ensure it’s solid.
3. Check ZMK debounce settings (optional)
- ZMK handles key debouncing in firmware, so in very rare cases you may want to increase debounce timing slightly in a custom config if cleaning/replacing the switch doesn’t solve it. More on customizing that here: https://zmk.dev/docs/features/keymaps
Most often, it’s a dirty or failing switch, so I’d try swapping the suspect switch first.
Would you like me to walk you through how to adjust the debounce setting in firmware just in case a hardware swap doesn’t solve it?
1. Check the switch itself
- Sometimes debris or dust can cause a jittery contact. You can try swapping the key with another switch and see if the problem follows the switch.
- If it does, that switch is defective and should be replaced.
2. Check the hotswap socket
- If the socket pins aren’t making perfectly solid contact, it can cause “bouncing” that looks like spamming. Gently press the switch down further or reinsert it.
- If needed, you can also reflow a touch of solder on the socket’s joints to ensure it’s solid.
3. Check ZMK debounce settings (optional)
- ZMK handles key debouncing in firmware, so in very rare cases you may want to increase debounce timing slightly in a custom config if cleaning/replacing the switch doesn’t solve it. More on customizing that here: https://zmk.dev/docs/features/keymaps
Most often, it’s a dirty or failing switch, so I’d try swapping the suspect switch first.
Would you like me to walk you through how to adjust the debounce setting in firmware just in case a hardware swap doesn’t solve it?
Keymaps & Behaviors | ZMK Firmware
ZMK uses a declarative approach to keymaps, using devicetree syntax to configure them in a .keymap file.
Closing thread not really a issue atm, just curious to any quick fixes, have already messed around with the debounce so should be alright