Had to read up on debouce, but it doesn't seem so complicated. https://www.arduino.cc/en/Tutorial/Buil ... s/Debounce
explains it well.
I guess the theory here is that the larger button causes spurious open/close transitions when pressed, for a longer period compared to the smaller button, so although it causes the transition to wake the board, at time of checking high pins it reads low. Have I understood what you're saying correctly?
Is there any way to modify the debounce behaviour of the chipset? Or is this unavoidable. (e.g that demo link above is writing it's own debounce method, but I suppose the debounce (if any) implemented on wake is not modifiable? I am very out of my depth here
The theory sounds very plausible, although it is 100% reproducible, that is, I never once get the correct pin (or anything other than 0) returned from
with the large button and always get pin 32 with the small button.
I have a project that sends a different mqtt message for different button presses and would very much like to not resort to using 1 ESP32 per button..