Sorry about that. This topic was split from another one which proposed generalizing the Python debounce code used for ADC based virtual buttons to all buttons.
I used “debounce” loosely there, as I’m used to hardware implementations that also act as false trigger mitigation. Which was the main focus of this topic.
That seems a bit too tight, especially when switches like this one have a max 10ms bounce time, per it’s datasheet. Admittedly, that’s a tactile switch, but Würth isn’t exactly a no name company.
Something interesting I noticed while browsing datasheets. Even some Omron microswitches are only rated to 500 m/s^2, with malfunctions at 200 m/s^2. They almost certainly exceed those by a large margin, and that’s real acceleration in one direction. However, it is worth keeping in mind.
Optical switches are the way to go.