I made an [alarm clock using two Qwiic Arcade Buttons as the snooze and stop buttons. The debounce time on these buttons is set to 150ms, but I still frequently get bounce on the buttons when the weather is cold and dry. What strategies and timings have you found for debouncing these buttons that works well?](https://github.com/kbloom/7-day-alarm-clock/blob/main/alarm_clock/alarm_clock.ino)
I don’t know how our engineers determined what value to use for debounce time, I would imagine they experimented with different times and stuck to what seemed to work the best. You may need to play around with the values in the library too see what works best for your application.
To clarify, I set the debounce time to 150ms myself. I feel that that’s pushing the boundaries of what you can get away with if you want the user (namely, me) to feel that the button is responsive to actual double-clicks, and yet it’s not enough to eliminate bounce in the kind of cold, dry weather were having now. So I was curious how someone might these two objectives in general, especially since double-clicking would seem to be common if someone were actually using the arcade button in an arcade type device.
I think I came up with a solution for my use case, however: the stop/skip button gets 1000ms debounce time, because intentional double-clicks should be rare, given its function. The snooze button (which increases the snooze length with each subsequent click) got extended to 200ms. I’ll keep testing to see how well this works for me.
That’s a really long bounce time. Have you tested it with other button types or even just some wire to make sure it’s actually bounce that you’re seeing?